Host Identity Protocol-Based Overlay Networking Environment (HIP BONE) Instance Specification for REsource LOcation And Discovery (RELOAD)
RFC 7086
Document | Type | RFC - Experimental (January 2014; No errata) | |
---|---|---|---|
Authors | Ari Keränen , Gonzalo Camarillo , Jouni Maenpaa | ||
Last updated | 2015-10-14 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | WG Document | |
Document shepherd | Miika Komu | ||
Shepherd write-up | Show (last changed 2013-07-09) | ||
IESG | IESG state | RFC 7086 (Experimental) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Ted Lemon | ||
Send notices to | (None) | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) A. Keranen Request for Comments: 7086 G. Camarillo Category: Experimental J. Maenpaa ISSN: 2070-1721 Ericsson January 2014 Host Identity Protocol-Based Overlay Networking Environment (HIP BONE) Instance Specification for REsource LOcation And Discovery (RELOAD) Abstract This document is the HIP-Based Overlay Networking Environment (HIP BONE) instance specification for the REsource LOcation And Discovery (RELOAD) protocol. The document provides the details needed to build a RELOAD-based overlay that uses HIP. 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/rfc7086. Keranen, et al. Experimental [Page 1] RFC 7086 HIP BONE Instance Spec for RELOAD January 2014 Copyright Notice Copyright (c) 2014 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 3. Peer Protocol . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Node ID Generation . . . . . . . . . . . . . . . . . . . . . 3 5. Mapping between Protocol Primitives and HIP Messages . . . . 3 5.1. Forwarding Header . . . . . . . . . . . . . . . . . . . . 4 5.2. Security Block . . . . . . . . . . . . . . . . . . . . . 4 5.3. Replaced RELOAD Messages . . . . . . . . . . . . . . . . 5 6. Securing Communication . . . . . . . . . . . . . . . . . . . 5 7. Routing HIP Messages via the Overlay . . . . . . . . . . . . 5 8. Enrollment and Bootstrapping . . . . . . . . . . . . . . . . 6 9. NAT Traversal . . . . . . . . . . . . . . . . . . . . . . . . 7 10. RELOAD Overlay Configuration Document Extension . . . . . . . 7 11. Security Considerations . . . . . . . . . . . . . . . . . . . 8 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 14.1. Normative References . . . . . . . . . . . . . . . . . . 8 14.2. Informative References . . . . . . . . . . . . . . . . . 9 1. Introduction The HIP-Based Overlay Networking Environment (HIP BONE) specification [RFC6079] provides a high-level framework for building HIP-based [RFC5201] overlays. The HIP BONE framework does not address the specification of the details on how to combine a particular peer protocol with HIP to build an overlay. It leaves this up to documents referred to as HIP BONE instance specifications. As discussed in [RFC6079], a HIP BONE instance specification needs to define, minimally: Keranen, et al. Experimental [Page 2] RFC 7086 HIP BONE Instance Spec for RELOAD January 2014 o the peer protocol to be used. o what kind of Node IDs are used and how they are derived. o which peer protocol primitives trigger HIP messages. o how the overlay identifier is generated. This document addresses all the previous items and provides additional details needed to build RELOAD-based HIP BONEs, referred to here as RELOAD HIP BONEs. The details on how different RELOAD modules would be integrated to a HIP implementation and what kind ofShow full document text