[Hipsec] I-D ACTION:draft-ietf-hip-rfc4843-bis-00.txt

Internet-Drafts@ietf.org Fri, 20 August 2010 16:45 UTC

Return-Path: <root@core3.amsl.com>
X-Original-To: hipsec@ietf.org
Delivered-To: hipsec@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id E95BB3A6964; Fri, 20 Aug 2010 09:45:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100820164501.E95BB3A6964@core3.amsl.com>
Date: Fri, 20 Aug 2010 09:45:01 -0700
Cc: hipsec@ietf.org
Subject: [Hipsec] I-D ACTION:draft-ietf-hip-rfc4843-bis-00.txt
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Aug 2010 16:45:02 -0000

A New Internet-Draft is available from the on-line Internet-Drafts 
This draft is a work item of the Host Identity Protocol Working Group of the IETF.

	Title		: An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers (ORCHID)
	Author(s)	: J. Laganier, F. Dupont
	Filename	: draft-ietf-hip-rfc4843-bis-00.txt
	Pages		: 13
	Date		: 2010-8-20
This document introduces Overlay Routable Cryptographic Hash
   Identifiers (ORCHID) as a new, experimental class of IPv6-address-
   like identifiers.  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.

   This document requests IANA to allocate a temporary prefix out of the
   IPv6 addressing space for Overlay Routable Cryptographic Hash
   Identifiers.  By default, the prefix will be returned to IANA in
   2014, with continued use requiring IETF consensus.

A URL for this Internet-Draft is:

Internet-Drafts are also available by anonymous FTP at:

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the