Browse Prior Art Database

An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers Version 2 (ORCHIDv2) (RFC7343) Disclosure Number: IPCOM000238833D
Original Publication Date: 2014-Sep-01
Included in the Prior Art Database: 2014-Sep-20
Document File: 28 page(s) / 29K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Laganier: AUTHOR [+2]


This document introduces Overlay Routable Cryptographic Hash Identifiers (ORCHID), a new class of identifiers that are like IP addresses. These identifiers are intended to be globally unique in a statistical sense (see Appendix A), non-routable at the IP layer, and routable at some overlay layer. The identifiers are securely bound, via a secure hash function, to the concatenation of an input bitstring and a context tag. Typically, but not necessarily, the input bitstring will include a suitably encoded public cryptographic key.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 10% of the total text.

Internet Engineering Task Force (IETF)                       J. Laganier Request for Comments: 7343                       Luminate Wireless, Inc. Obsoletes: 4843                                                F. Dupont Category: Standards Track                    Internet Systems Consortium ISSN: 2070-1721                                           September 2014

                            An IPv6 Prefix for   Overlay Routable Cryptographic Hash Identifiers Version 2 (ORCHIDv2)


   This document specifies an updated Overlay Routable Cryptographic    Hash Identifiers (ORCHID) format that obsoletes that in RFC 4843.    These identifiers are intended to be used as endpoint identifiers at    applications and Application Programming Interfaces (APIs) 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    perspective, 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 RFC 4843 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 is an Internet Standards Track document.

   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).  Further information on    Internet Standards is available in 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

Laganier & Dupont            Standards Track                    [Page 1]
 RFC 7343                        ORCHIDv2                  September 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    (