[rfc-dist] RFC 4843 on An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers (ORCHID)

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Thu Apr 26 18:39:41 PDT 2007


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4843

        Title:      An IPv6 Prefix for Overlay 
                    Routable Cryptographic Hash Identifiers (ORCHID) 
        Author:     P. Nikander, J. Laganier,
                    F. Dupont
        Status:     Experimental
        Date:       April 2007
        Mailbox:    pekka.nikander at nomadiclab.com, 
                    julien.ietf at laposte.net, 
                    Francis.Dupont at fdupont.fr
        Pages:      14
        Characters: 32483
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-laganier-ipv6-khi-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4843.txt

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.  This memo defines an 
Experimental Protocol for the Internet community.


EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet 
community. It does not specify an Internet standard of any kind. 
Discussion and suggestions for improvement are requested.  Distribution 
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...




More information about the rfc-dist mailing list