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.
[1]
Marcelo Bagnulo,et al.
Cryptographically Generated Addresses (CGA) Extension Field Format
,
2006,
RFC.
[2]
Gabriel Montenegro,et al.
A Simple Privacy Extension for Mobile IPV6
,
2004,
MWCN.
[3]
Stephen Farrell,et al.
Naming Things with Hashes
,
2013,
RFC.
[4]
Donald E. Eastlake,et al.
US Secure Hash Algorithm 1 (SHA1)
,
2001,
RFC.
[5]
Stephen E. Deering,et al.
IP Version 6 Addressing Architecture
,
1995,
RFC.
[6]
Yakov Rekhter,et al.
Address Allocation for Private Internets
,
1994,
RFC.
[7]
Paul E. Hoffman,et al.
Attacks on Cryptographic Hashes in Internet Protocols
,
2005,
RFC.
[8]
Pekka Nikander,et al.
An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers (ORCHID)
,
2007,
RFC.
[9]
Scott O. Bradner,et al.
Key words for use in RFCs to Indicate Requirement Levels
,
1997,
RFC.
[10]
Brian Haberman,et al.
Special-Purpose IP Address Registries
,
2013,
RFC.