Network Mobility (NEMO) Basic Support Protocol
RFC 3963
Document | Type | RFC - Proposed Standard (January 2005; No errata) | |
---|---|---|---|
Authors | Pascal Thubert , Alexandre Petrescu , Ryuji Wakikawa , Vijay Devarapalli | ||
Last updated | 2013-03-02 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 3963 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Margaret Cullen | ||
Send notices to | (None) |
Network Working Group V. Devarapalli Request for Comments: 3963 Nokia Category: Standards Track R. Wakikawa Keio University A. Petrescu Motorola P. Thubert Cisco Systems January 2005 Network Mobility (NEMO) Basic Support Protocol 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 This document describes the Network Mobility (NEMO) Basic Support protocol that enables Mobile Networks to attach to different points in the Internet. The protocol is an extension of Mobile IPv6 and allows session continuity for every node in the Mobile Network as the network moves. It also allows every node in the Mobile Network to be reachable while moving around. The Mobile Router, which connects the network to the Internet, runs the NEMO Basic Support protocol with its Home Agent. The protocol is designed so that network mobility is transparent to the nodes inside the Mobile Network. Devarapalli, et al. Standards Track [Page 1] RFC 3963 NEMO Basic Support Protocol January 2005 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology. . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Overview of the NEMO Protocol. . . . . . . . . . . . . . . . 4 4. Message Formats. . . . . . . . . . . . . . . . . . . . . . . 7 4.1. Binding Update. . . . . . . . . . . . . . . . . . . . . 7 4.2. Binding Acknowledgement . . . . . . . . . . . . . . . . 7 4.3. Mobile Network Prefix Option. . . . . . . . . . . . . . 8 5. Mobile Router Operation. . . . . . . . . . . . . . . . . . . 9 5.1. Data Structures . . . . . . . . . . . . . . . . . . . . 10 5.2. Sending Binding Updates . . . . . . . . . . . . . . . . 10 5.3. Receiving Binding Acknowledgements. . . . . . . . . . . 11 5.4. Error Processing . . . . . . . . . . . . . . . . . . . 12 5.4.1. Implicit Mode. . . . . . . . . . . . . . . . . . 12 5.4.2. Explicit Mode. . . . . . . . . . . . . . . . . . 12 5.5. Establishment of Bi-directional Tunnel . . . . . . . . 13 5.6. Neighbor Discovery for Mobile Router . . . . . . . . . 13 5.7. Multicast Groups for Mobile Router . . . . . . . . . . 14 5.8. Returning Home . . . . . . . . . . . . . . . . . . . . 14 6. Home Agent Operation . . . . . . . . . . . . . . . . . . . . 15 6.1. Data Structures . . . . . . . . . . . . . . . . . . . . 15 6.1.1. Binding Cache. . . . . . . . . . . . . . . . . . 15 6.1.2. Prefix Table . . . . . . . . . . . . . . . . . . 15 6.2. Mobile Network Prefix Registration . . . . . . . . . . 16 6.3. Advertising Mobile Network Reachability . . . . . . . . 17 6.4. Establishment of Bi-directional Tunnel . . . . . . . . 18 6.5. Forwarding Packets . . . . . . . . . . . . . . . . . . 18 6.6. Sending Binding Acknowledgements . . . . . . . . . . . 19 6.7. Mobile Network Prefix De-Registration . . . . . . . . . 19 7. Modifications to Dynamic Home Agent Address Discovery. . . . 20 7.1. Modified Dynamic Home Agent Discovery Request . . . . . 20 7.2. Modified Dynamic Home Agent Discovery Address Request . 20 7.3. Modified Home Agent Information Option . . . . . . . . 21 8. Support for Dynamic Routing Protocols. . . . . . . . . . . . 22 9. Security Considerations. . . . . . . . . . . . . . . . . . . 23 10. IANA Considerations. . . . . . . . . . . . . . . . . . . . . 24 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 25 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 25 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 A. Examples of NEMO Basic Support Operation. . . . . . . . . 27 B. Running Link State Routing Protocol with NEMO Basic Support . . . . . . . . . . . . . . . . . . . . . . . . . 30Show full document text