Host Identity Protocol-Based Overlay Networking Environment (HIP BONE) Instance Specification for REsource LOcation And Discovery (RELOAD)
draft-ietf-hip-reload-instance-09

The information below is for an old version of the document
Document Type Active Internet-Draft (hip WG)
Last updated 2013-10-10 (latest revision 2013-10-01)
Stream IETF
Intended RFC status Experimental
Formats plain text pdf html
Stream WG state WG Document
Consensus Yes
Document shepherd Miika Komu
Shepherd write-up Show (last changed 2013-07-09)
IESG IESG state IESG Evaluation::Revised I-D Needed
Telechat date
Needs a YES.
Responsible AD Ted Lemon
Send notices to hip-chairs@tools.ietf.org, draft-ietf-hip-reload-instance@tools.ietf.org, miika.komu@hiit.fi
IANA IANA review state IANA OK - Actions Needed
IANA action state None
HIP Working Group                                             A. Keranen
Internet-Draft                                              G. Camarillo
Intended status: Experimental                                 J. Maenpaa
Expires: April 04, 2014                                         Ericsson
                                                        October 01, 2013

 Host Identity Protocol-Based Overlay Networking Environment (HIP BONE)
  Instance Specification for REsource LOcation And Discovery (RELOAD)
                   draft-ietf-hip-reload-instance-09

Abstract

   This document is the Host Identity Protocol-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 Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 04, 2014.

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Keranen, et al.          Expires April 04, 2014                 [Page 1]
Internet-Draft      HIP BONE Instance Spec for RELOAD       October 2013

   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  . . . . . . . . . . . .   6
   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  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     14.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     14.2.  Informational References . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   The Host Identify Protocol-Based Overlay Networking Environment (HIP
   BONE) specification [RFC6079] provides a high-level framework for
   building HIP-based [RFC5201] overlays.  The HIP BONE framework leaves
   the specification of the details on how to combine a particular peer
   protocol with HIP to build an overlay up to documents referred to as
   HIP BONE instance specifications.  As discussed in [RFC6079], a HIP
   BONE instance specification needs to define, minimally:

   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.

Keranen, et al.          Expires April 04, 2014                 [Page 2]
Internet-Draft      HIP BONE Instance Spec for RELOAD       October 2013

   o  how the overlay identifier is generated.
Show full document text