%% You should probably cite rfc5447 instead of this I-D. @techreport{ietf-dime-mip6-integrated-12, number = {draft-ietf-dime-mip6-integrated-12}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-dime-mip6-integrated/12/}, author = {Jouni Korhonen and Julien Bournelle and Hannes Tschofenig and Kuntal Chowdhury and Charles E. Perkins}, title = {{Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction}}, pagetotal = 17, year = 2009, month = jan, day = 9, abstract = {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{]}}, }