draft-ietf-hip-rfc4843-bis-06.txt   draft-ietf-hip-rfc4843-bis-07.txt 
Network Working Group J. Laganier Network Working Group J. Laganier
Internet-Draft Luminate Wireless, Inc. Internet-Draft Luminate Wireless, Inc.
Obsoletes: 4843 (if approved) F. Dupont Obsoletes: 4843 (if approved) F. Dupont
Intended status: Standards Track Internet Systems Consortium Intended status: Standards Track Internet Systems Consortium
Expires: December 25, 2014 June 23, 2014 Expires: December 27, 2014 June 25, 2014
An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers
Version 2 (ORCHIDv2) Version 2 (ORCHIDv2)
draft-ietf-hip-rfc4843-bis-06 draft-ietf-hip-rfc4843-bis-07
Abstract Abstract
This document specifies an updated Overlay Routable Cryptographic This document specifies an updated Overlay Routable Cryptographic
Hash Identifiers format that obsoletes RFC4843. These identifiers Hash Identifiers format that obsoletes RFC4843. These identifiers
are intended to be used as endpoint identifiers at applications and are intended to be used as endpoint identifiers at applications and
Application Programming Interfaces (API) and not as identifiers for Application Programming Interfaces (API) and not as identifiers for
network location at the IP layer, i.e., locators. They are designed network location at the IP layer, i.e., locators. They are designed
to appear as application layer entities and at the existing IPv6 to appear as application layer entities and at the existing IPv6
APIs, but they should not appear in actual IPv6 headers. To make APIs, but they should not appear in actual IPv6 headers. To make
skipping to change at page 1, line 49 skipping to change at page 1, line 49
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 25, 2014. This Internet-Draft will expire on December 27, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 6, line 9 skipping to change at page 6, line 9
An ORCHID is generated using the ORCHID Generation Algorithm (OGA) An ORCHID is generated using the ORCHID Generation Algorithm (OGA)
below. The algorithm takes a bitstring and a context identifier as below. The algorithm takes a bitstring and a context identifier as
input and produces an ORCHID as output. The hash function used in input and produces an ORCHID as output. The hash function used in
the ORCHID Generation Algorithm is defined for each OGA identifier by the ORCHID Generation Algorithm is defined for each OGA identifier by
the specification for the respective usage context (e.g., HIPv2). the specification for the respective usage context (e.g., HIPv2).
Input := any bitstring Input := any bitstring
OGA ID := 4-bits Orchid Generation Algorithm identifier OGA ID := 4-bits Orchid Generation Algorithm identifier
Hash Input := Context ID | Input Hash Input := Context ID | Input
Hash := Hash_function( Hash Input ) Hash := Hash_function( Hash Input )
ORCHID := Prefix | Encode_96( Hash ) ORCHID := Prefix | OGA ID | Encode_96( Hash )
where: where:
| : Denotes concatenation of bitstrings | : Denotes concatenation of bitstrings
Input : A bitstring that is unique or statistically unique Input : A bitstring that is unique or statistically unique
within a given context. The bitstring is intended within a given context. The bitstring is intended
to be associated with the to-be-created ORCHID in to be associated with the to-be-created ORCHID in
the given context. the given context.
Context ID : A randomly generated value defining the expected Context ID : A randomly generated value defining the expected
usage context for the particular ORCHID and the usage context for the particular ORCHID and the
hash function to be used for generation of ORCHIDs hash function to be used for generation of ORCHIDs
in this context. These values are allocated out of in this context. These values are allocated out of
the namespace introduced for CGA Type Tags; see RFC the namespace introduced for CGA Type Tags; see RFC
3972 and 3972 and
http://www.iana.org/assignments/cga-message-types. http://www.iana.org/assignments/cga-message-types.
OGA ID : A 4-bit long identifier for the Hash_function OGA ID : A 4-bit long identifier for the Hash_function
in use within the specific usage context. in use within the specific usage context.
Hash_function : The one-way hash function (i.e., hash function Hash_function : The one-way hash function (i.e., hash function
with pre-image resistance and second pre-image with pre-image resistance and second pre-image
resistance) to be used as identified by the resistance) to be used as identified by the
value for the OGA ID according document value for the OGA ID according document
defining the context usage identified by the defining the context usage identified by the
Context ID. For example, the version 2 of the Context ID. For example, the version 2 of the
HIP specification defines SHA1 [RFC3174] as HIP specification defines SHA1 [RFC3174] as
the hash function to be used to generate the hash function to be used to generate
ORCHIDv2 used in the HIPv2 protocol when the ORCHIDv2 used in the HIPv2 protocol when the
 End of changes. 5 change blocks. 
5 lines changed or deleted 5 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/