Host Identity Protocol (HIP) Multi-Hop Routing Extension
RFC 6028
Document | Type |
RFC - Experimental
(October 2010; No errata)
Was draft-ietf-hip-via (hip WG)
|
|
---|---|---|---|
Authors | Gonzalo Camarillo , Ari Keränen | ||
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 6028 (Experimental) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Ralph Droms | ||
Send notices to | (None) |
Internet Engineering Task Force (IETF) G. Camarillo Request for Comments: 6028 A. Keranen Category: Experimental Ericsson ISSN: 2070-1721 October 2010 Host Identity Protocol (HIP) Multi-Hop Routing Extension Abstract This document specifies two extensions to the Host Identity Protocol (HIP) to implement multi-hop routing. The first extension allows implementing source routing in HIP. That is, a node sending a HIP packet can define a set of nodes that the HIP packet should traverse. The second extension allows a HIP packet to carry and record the list of nodes that forwarded it. Status of This Memo This document is not an Internet Standards Track specification; it is published for examination, experimental implementation, and evaluation. This document defines an Experimental Protocol for the Internet community. 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). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see 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/rfc6028. Camarillo & Keranen Experimental [Page 1] RFC 6028 HIP Multi-Hop Routing Extension October 2010 Copyright Notice Copyright (c) 2010 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 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 ....................................................2 2. Terminology .....................................................3 2.1. Requirements Language ......................................3 2.2. Definitions ................................................3 3. Protocol Definitions ............................................3 3.1. Creating and Processing Via Lists ..........................4 3.2. Creating Destination Lists .................................4 3.3. Processing Destination Lists ...............................5 3.4. Fragmentation Considerations ...............................5 4. Packet Formats ..................................................5 4.1. Source and Destination Route List Parameters ...............6 5. IANA Considerations .............................................7 6. Security Considerations .........................................8 6.1. Forged Destination and Via Lists ...........................8 6.2. Forwarding Loops ...........................................8 7. Acknowledgments .................................................9 8. References ......................................................9 8.1. Normative References .......................................9 8.2. Informative References .....................................9 1. Introduction When the Host Identity Protocol (HIP) [RFC5201] is used in certain contexts, nodes need the ability to perform source routing. That is, a node needs the ability to send a HIP signaling packet that will traverse a set of nodes before reaching its destination. Such features are needed, e.g., in the HIP-Based Overlay Networking Environment (HIP BONE) [HIP-BONE] or if two nodes wish to keep a third, or more, HIP nodes on the signaling path. This document defines an extension that provides HIP with this functionality. Camarillo & Keranen Experimental [Page 2] RFC 6028 HIP Multi-Hop Routing Extension October 2010 Additionally, when HIP signaling packets are routed through multiple nodes, some of these nodes (e.g., the destination host) need the ability to know the nodes that a particular packet traversed. This document defines another extension that provides HIP with this functionality. These two extensions enable multi-hop routing in HIP. Before these extensions were specified, there were standardized ways for supporting only a single intermediate node (e.g., a rendezvous serverShow full document text