Mobile Node Identifier Option for Mobile IPv6 (MIPv6)
RFC 4283
Document | Type | RFC - Proposed Standard (December 2005; Errata) | |
---|---|---|---|
Authors | Alpesh Patel , Kent Leung , Haseeb Akhtar , Mohamed Khalil , Kuntal Chowdhury | ||
Last updated | 2015-10-14 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 4283 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Margaret Cullen | ||
Send notices to | mkhalil@nortelnetworks.com |
Network Working Group A. Patel Request for Comments: 4283 K. Leung Category: Standards Track Cisco Systems M. Khalil H. Akhtar Nortel Networks K. Chowdhury Starent Networks November 2005 Mobile Node Identifier Option for Mobile IPv6 (MIPv6) Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2005). Abstract Mobile IPv6 (MIPv6) defines a new Mobility header that is used by mobile nodes, correspondent nodes, and home agents in all messaging related to the creation and management of bindings. Mobile IPv6 nodes need the capability to identify themselves using an identity other than the default home IP address. Some examples of identifiers include Network Access Identifier (NAI), Fully Qualified Domain Name (FQDN), International Mobile Station Identifier (IMSI), and Mobile Subscriber Number (MSISDN). This document defines a new mobility option that can be used by Mobile IPv6 entities to identify themselves in messages containing a mobility header. Patel, et al. Standards Track [Page 1] RFC 4283 Mobile Node Identifier Option for MIPv6 November 2005 Table of Contents 1. Introduction ....................................................2 2. Terminology .....................................................3 3. Mobile Node Identifier Option ...................................3 3.1. MN-NAI Mobility Option .....................................4 3.2. Processing Considerations ..................................4 4. Security Considerations .........................................4 4.1. General Considerations .....................................4 4.2. MN-NAI Considerations ......................................4 5. IANA Considerations .............................................5 6. Acknowledgements ................................................5 7. Normative References ............................................5 8. Informative Reference ...........................................6 1. Introduction The base specification of Mobile IPv6 [RFC3775] identifies mobility entities using an IPv6 address. It is essential to have a mechanism wherein mobility entities can be identified using other identifiers (for example, a Network Access Identifier (NAI) [RFC4282], International Mobile Station Identifier (IMSI), or an application/ deployment specific opaque identifier). The capability to identify a mobility entity via identifiers other than the IPv6 address can be leveraged for performing various functions, for example, o authentication and authorization using an existing AAA (Authentication, Authorization, and Accounting) infrastructure or via an HLR/AuC (Home Location Register/Authentication Center) o dynamic allocation of a mobility anchor point o dynamic allocation of a home address This document defines an option with a subtype number that denotes a specific type of identifier. One instance of subtype, the NAI, is defined in Section 3.1. It is anticipated that other identifiers will be defined for use in the mobility header in the future. This option SHOULD be used when Internet Key Exchange (IKE)/IPsec is not used for protecting binding updates or binding acknowledgements as specified in [RFC3775]. It is typically used with the authentication option [RFC4285]. But this option may be used independently. For example, the identifier can provide accounting and billing services. Patel, et al. Standards Track [Page 2] RFC 4283 Mobile Node Identifier Option for MIPv6 November 2005 2. Terminology The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 3. Mobile Node Identifier Option The Mobile Node Identifier option is a new optional data field that is carried in the Mobile IPv6-defined messages that includes the Mobility header. Various forms of identifiers can be used toShow full document text