<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-dime-mip6-integrated" target="https://datatracker.ietf.org/doc/html/draft-ietf-dime-mip6-integrated-12">
   <front>
      <title>Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction</title>
      <author initials="J." surname="Korhonen" fullname="Jouni Korhonen">
         <organization>Nokia Siemens Networks</organization>
      </author>
      <author initials="J." surname="Bournelle" fullname="Julien Bournelle">
         <organization>Orange Labs</organization>
      </author>
      <author initials="H." surname="Tschofenig" fullname="Hannes Tschofenig">
         <organization>Nokia Siemens Networks</organization>
      </author>
      <author initials="K." surname="Chowdhury" fullname="Kuntal Chowdhury">
         <organization>Starent Networks</organization>
      </author>
      <author initials="C. E." surname="Perkins" fullname="Charles E. Perkins">
         <organization>WiChorus</organization>
      </author>
      <date month="January" day="9" year="2009" />
      <abstract>
	 <t>A Mobile IPv6 node requires a home agent address, a home address, and a security association with its home agent before it can start utilizing Mobile IPv6.  RFC 3775 requires that some or all of these parameters be statically configured.  Mobile IPv6 bootstrapping work aims to make this information dynamically available to the mobile node.  An important aspect of the Mobile IPv6 bootstrapping solution is to support interworking with existing Authentication, Authorization, and Accounting (AAA) infrastructures.  This document describes MIPv6 bootstrapping using the Diameter Network Access Server to home AAA server interface. [STANDARDS-TRACK]
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-dime-mip6-integrated-12" />
   
</reference>
