RFC 6611: Mobile IPv6 (MIPv6) Bootstrapping for the Integrated Scenario
In plain English — editorial summary, not part of the RFC
Mobile IPv6 bootstrapping can be categorized into two primary scenarios: the split scenario and the integrated scenario. In the split scenario, the mobile node's mobility service is authorized by a different service authorizer than the network access authorizer. In the integrated scenario, the mobile node's mobility service is authorized by the same service authorizer as the network access service authorizer. This document defines a method for home agent information discovery for the integrated scenario. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6611
- Published
- May 2012
- Authors
- K. Chowdhury; A. Yegin
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 12
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6610DHCP Options for Home Information Discovery in Mobile IPv6 (MIPv6)Current
May 2012
- RFC 6612Interactions between Proxy Mobile IPv6 (PMIPv6) and Mobile IPv6 (MIPv6): Scenarios and Related IssuesCurrent
May 2012
- RFC 6607Virtual Subnet Selection Options for DHCPv4 and DHCPv6Current
April 2012
- RFC 6606Problem Statement and Requirements for IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) RoutingCurrent
May 2012
- RFC 6605Elliptic Curve Digital Signature Algorithm (DSA) for DNSSECCurrent
April 2012
- RFC 6604xNAME RCODE and Status Bits ClarificationCurrent
April 2012
- RFC 6618Mobile IPv6 Security Framework Using Transport Layer Security for Communication between the Mobile Node and Home AgentCurrent
May 2012
- RFC 6603Prefix Exclude Option for DHCPv6-based Prefix DelegationCurrent
May 2012
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?