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

The information below is for an old version of the document
Document Type Active Internet-Draft (hip WG)
Last updated 2014-06-23 (latest revision 2013-12-10)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Gonzalo Camarillo
Shepherd write-up Show (last changed 2014-03-20)
IESG IESG state IESG Evaluation
Consensus Boilerplate Yes
Telechat date
Needs a YES. Needs 5 more YES or NO OBJECTION positions to pass.
Responsible AD Ted Lemon
Send notices to hip-chairs@tools.ietf.org, draft-ietf-hip-rfc4843-bis@tools.ietf.org
IANA IANA review state IANA - Not OK
IANA action state None
Network Working Group                                        J. Laganier
Internet-Draft                                   Luminate Wireless, Inc.
Obsoletes: 4843 (if approved)                                  F. Dupont
Intended status: Standards Track             Internet Systems Consortium
Expires: June 14, 2014                                 December 11, 2013

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

Abstract

   This document specifies an updated Overlay Routable Cryptographic
   Hash Identifiers format that obsoletes 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 regular 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 June 14, 2014.

Laganier & Dupont         Expires June 14, 2014                 [Page 1]
Internet-Draft  Cryptographic Hash IDentifiers(ORCHIDv2)   December 2013

Copyright Notice

   Copyright (c) 2013 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
     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 and Forwarding Considerations . . . . . . . . . . . .   7
   4.  Design Choices  . . . . . . . . . . . . . . . . . . . . . . .   8
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   7.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   9
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  10
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     9.1.  Normative references  . . . . . . . . . . . . . . . . . .  10
     9.2.  Informative references  . . . . . . . . . . . . . . . . .  10
   Appendix A.  Collision Considerations . . . . . . . . . . . . . .  11
   Appendix B.  Changes from RFC 4843  . . . . . . . . . . . . . . .  11

1.  Introduction

   This document introduces Overlay Routable Cryptographic Hash
   Identifiers (ORCHID), a new class of IP address-like identifiers.
   These identifiers are intended to be globally unique in a statistical
Show full document text