RFC 5447: Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC5447
- Published
- February 2009
- Authors
- J. Korhonen; J. Bournelle; H. Tschofenig; C. Perkins; K. Chowdhury
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5624Quality of Service Parameters for Usage with DiameterCurrent
August 2009
- RFC 5777Traffic Classification and Quality of Service (QoS) Attributes for DiameterCurrent
February 2010
- RFC 5866Diameter Quality-of-Service ApplicationCurrent
May 2010
- RFC 6733Diameter Base ProtocolUpdated
October 2012
- RFC 7075Realm-Based Redirection In DiameterCurrent
November 2013
- RFC 7678Attribute-Value Pairs for Provisioning Customer Equipment Supporting IPv4-Over-IPv6 Transitional SolutionsCurrent
October 2015
- RFC 7944Diameter Routing Message PriorityCurrent
August 2016
- RFC 7966Security at the Attribute-Value Pair (AVP) Level for Non-neighboring Diameter Nodes: Scenarios and RequirementsCurrent
September 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?