An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers Version 2 (ORCHIDv2)
draft-ietf-hip-rfc4843-bis-02

The information below is for an old version of the document
Document Type Active Internet-Draft (hip WG)
Last updated 2012-09-19
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        J. Laganier
Internet-Draft                                          Juniper Networks
Obsoletes: 4843 (if approved)                                  F. Dupont
Intended status: Standards Track             Internet Systems Consortium
Expires: March 23, 2013                               September 19, 2012

   An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers
                          Version 2 (ORCHIDv2)
                     draft-ietf-hip-rfc4843-bis-02

Abstract

   This document specifies an updated Overlay Routable Cryptographich
   Hash Identifiers format that obsoletes the earlier format defined in
   [RFC4843].  These identifiers are intended to be used as endpoint
   identifiers at applications and Application Programming Interfaces
   (API) and not as identifiers for network location at the IP layer,
   i.e., locators.  They are designed to appear as application layer
   entities and at the existing IPv6 APIs, but they should not appear in
   actual IPv6 headers.  To make them more like vanilla IPv6 addresses,
   they are expected to be routable at an overlay level.  Consequently,
   while they are considered non-routable addresses from the IPv6 layer
   point-of-view, all existing IPv6 applications are expected to be able
   to use them in a manner compatible with current IPv6 addresses.

   The Overlay Routable Cryptographic Hash Identifiers originally
   defined in [RFC4843] lacked a mechanism for cryptographic algorithm
   agility.  The updated ORCHID format specified in this document
   removes this limitation by encoding in the identifier itself an index
   to the suite of cryptographic algorithms in use.

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 March 23, 2013.

Laganier & Dupont        Expires March 23, 2013                 [Page 1]
Internet-Draft  Cryptographic Hash IDentifiers(ORCHIDv2)  September 2012

Copyright Notice

   Copyright (c) 2012 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 . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Rationale and Intent . . . . . . . . . . . . . . . . . . .  3
     1.2.  ORCHID Properties  . . . . . . . . . . . . . . . . . . . .  4
     1.3.  Expected use of ORCHIDs  . . . . . . . . . . . . . . . . .  5
     1.4.  Action Plan  . . . . . . . . . . . . . . . . . . . . . . .  5
     1.5.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  5
   2.  Cryptographic Hash Identifier Construction . . . . . . . . . .  5
   3.  Routing Considerations . . . . . . . . . . . . . . . . . . . .  7
     3.1.  Overlay Routing  . . . . . . . . . . . . . . . . . . . . .  7
   4.  Collision Considerations . . . . . . . . . . . . . . . . . . .  8
   5.  Design Choices . . . . . . . . . . . . . . . . . . . . . . . . 10
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 10
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 11
   8.  Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 12
   9.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 12
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
     10.1. Normative references . . . . . . . . . . . . . . . . . . . 12
     10.2. Informative references . . . . . . . . . . . . . . . . . . 12
   Appendix A.  Changes from RFC 4843 . . . . . . . . . . . . . . . . 13

Laganier & Dupont        Expires March 23, 2013                 [Page 2]
Internet-Draft  Cryptographic Hash IDentifiers(ORCHIDv2)  September 2012
Show full document text