Flow Bindings in Mobile IPv6 and Network Mobility (NEMO) Basic Support
RFC 6089
Document | Type |
RFC - Proposed Standard
(January 2011; No errata)
Updates RFC 5648
|
|
---|---|---|---|
Authors | Nicolas Montavont , George Tsirtsis , Koojana Kuladinithi , Gerardo Giaretta , Hesham Soliman | ||
Last updated | 2015-10-14 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 6089 (Proposed Standard) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Jari Arkko | ||
Send notices to | (None) |
Internet Engineering Task Force (IETF) G. Tsirtsis Request for Comments: 6089 Qualcomm Updates: 5648 H. Soliman Category: Standards Track Elevate Technologies ISSN: 2070-1721 N. Montavont IT/TB G. Giaretta Qualcomm K. Kuladinithi University of Bremen January 2011 Flow Bindings in Mobile IPv6 and Network Mobility (NEMO) Basic Support Abstract This document introduces extensions to Mobile IPv6 that allow nodes to bind one or more flows to a care-of address. These extensions allow multihomed nodes to instruct home agents and other Mobile IPv6 entities to direct inbound flows to specific addresses. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6089. Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must Tsirtsis, et al. Standards Track [Page 1] RFC 6089 Flow Binding January 2011 include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Requirements Notation . . . . . . . . . . . . . . . . . . . . 4 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Mobile IPv6 Extensions . . . . . . . . . . . . . . . . . . . . 5 4.1. Definition Update for Binding Identifier Mobility Option . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4.2. Flow Identification Mobility Option . . . . . . . . . . . 5 4.2.1. Flow Identification Sub-Options Definition . . . . . . 7 4.2.2. Flow Summary Mobility Option . . . . . . . . . . . . . 11 4.3. Flow Bindings Entries List and Its Relationship to Binding Cache . . . . . . . . . . . . . . . . . . . . . . 12 5. Protocol Operations . . . . . . . . . . . . . . . . . . . . . 14 5.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 14 5.1.1. Preferred Care-of Address . . . . . . . . . . . . . . 15 5.2. Mobile Node Considerations . . . . . . . . . . . . . . . . 15 5.2.1. Sending BU with BID Options . . . . . . . . . . . . . 15 5.2.2. Sending BU with Flow Identification Mobility Options . . . . . . . . . . . . . . . . . . . . . . . 16 5.2.3. Sending BU with a Flow Summary Option . . . . . . . . 17 5.2.4. Removing Flow Bindings . . . . . . . . . . . . . . . . 18 5.2.5. Returning Home . . . . . . . . . . . . . . . . . . . . 18 5.2.6. Receiving Binding Acknowledgements . . . . . . . . . . 19 5.2.7. Return Routability Procedure . . . . . . . . . . . . . 19 5.3. HA, MAP, and CN Considerations . . . . . . . . . . . . . . 19 5.3.1. Handling Binding Identifier Mobility Options . . . . . 20 5.3.2. Handling Flow Identification Mobility Options . . . . 20 5.3.3. Handling Flow Summary Mobility Option . . . . . . . . 23 5.3.4. Flow Binding Removals . . . . . . . . . . . . . . . . 23 5.3.5. Sending Binding Acknowledgements . . . . . . . . . . . 24 5.3.6. Packet Processing . . . . . . . . . . . . . . . . . . 24 6. MTU Considerations . . . . . . . . . . . . . . . . . . . . . . 25 7. Security considerations . . . . . . . . . . . . . . . . . . . 26 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 28Show full document text