Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Obsoletes:

RFC 4843

Updated by:

RFC 9374

Authors:

J. Laganier
F. Dupont

Stream:

IETF

Source:

hip (int)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC7343

Discuss this RFC: Send questions or comments to the mailing listhipsec@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 7343

Abstract

This document specifies an updated Overlay Routable CryptographicHash Identifiers (ORCHID) format that obsoletes that in RFC 4843.These identifiers are intended to be used as endpoint identifiers atapplications and Application Programming Interfaces (APIs) and not asidentifiers for network location at the IP layer, i.e., locators.They are designed to appear as application-layer entities and at theexisting IPv6 APIs, but they should not appear in actual IPv6headers. To make them more like regular IPv6 addresses, they areexpected to be routable at an overlay level. Consequently, whilethey are considered non-routable addresses from the IPv6-layerperspective, all existing IPv6 applications are expected to be ableto use them in a manner compatible with current IPv6 addresses.

The Overlay Routable Cryptographic Hash Identifiers originallydefined in RFC 4843 lacked a mechanism for cryptographic algorithmagility. The updated ORCHID format specified in this documentremoves this limitation by encoding, in the identifier itself, anindex to the suite of cryptographic algorithms in use.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.