draft-ietf-csi-send-name-type-registry-01.txt   draft-ietf-csi-send-name-type-registry-02.txt 
Network Working Group R. Gagliano Network Working Group R. Gagliano
Internet-Draft LACNIC Internet-Draft LACNIC
Updates: 3971 (if approved) S. Krishnan Updates: 3971 (if approved) S. Krishnan
Intended status: Standards Track Ericsson Intended status: Standards Track Ericsson
Expires: August 8, 2010 A. Kukec Expires: September 7, 2010 A. Kukec
University of Zagreb University of Zagreb
February 04, 2010 March 06, 2010
SEND Name Type field Registry SEND Name Type field Registry
draft-ietf-csi-send-name-type-registry-01 draft-ietf-csi-send-name-type-registry-02
Abstract Abstract
SEcure Neighbor Discovery (SEND) defines the Name Type field in the SEcure Neighbor Discovery (SEND) defines the Name Type field in the
Trust Anchor option. This document request to IANA the creation and Trust Anchor option. This document requests to IANA the creation and
management of a registry for this field. This document also management of a registry for this field. This document also
specifies a new Name Type field based on a certificate Subject Key specifies a new Name Type field based on a certificate Subject Key
Identifier (SKI). Identifier (SKI).
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at page 1, line 43 skipping to change at page 1, line 43
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 8, 2010. This Internet-Draft will expire on September 7, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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 3, line 9 skipping to change at page 3, line 9
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Requirements notation . . . . . . . . . . . . . . . . . . . . . 3 1. Requirements notation . . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. SEND SKI trust anchor Name Type field. . . . . . . . . . . . . 5 3. SEND SKI trust anchor option Name Type field . . . . . . . . . 5
3.1. Processing Rules for Router . . . . . . . . . . . . . . . . 5 3.1. Processing Rules for Router . . . . . . . . . . . . . . . . 5
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 7
6. Normative References . . . . . . . . . . . . . . . . . . . . . 8 6. Normative References . . . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9
1. Requirements notation 1. Requirements notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Introduction 2. Introduction
SEcure Neighbor Discovery [RFC3971] (SEND) utilizes X.509v3 SEcure Neighbor Discovery [RFC3971] (SEND) utilizes X.509v3
certificates that include [RFC3779] extension for IPv6 addresses to certificates that include the [RFC3779] extension for IPv6 addresses
certify a router authority over an IPv6 prefix for NDP (Neighbor to certify a router authority over an IPv6 prefix for NDP (Neighbor
Discovery Protocol). The Trust Anchor Option in section 6.4.3 of RFC Discovery Protocol). The Trust Anchor Option in section 6.4.3 of RFC
3971 allows the identification of the Trust Anchor (TA) selected by 3971 allows the identification of the Trust Anchor (TA) selected by
the host. In that section, two name types were defined, the DER the host. In that same section, two name types were defined: the DER
Encoded X.501 Name and a Fully Qualified Domain Name (FQDN). This Encoded X.501 Name and a Fully Qualified Domain Name (FQDN). This
document request to IANA the creation and management of a registry document request to IANA the creation and management of a registry
for this field. for this field.
In any Public Key Infrastructure, the subject name of a certificate In any Public Key Infrastructure, the subject name of a certificate
is only unique within each CA. Consequently, a new option to is only unique within each CA. Consequently, a new option to
identify TAs across CAs is needed. identify TAs across CAs is needed.
In [I-D.ietf-csi-send-cert] the certificate profile described in In [I-D.ietf-csi-send-cert] the certificate profile described in
[I-D.ietf-sidr-res-certs] is adopted for SEND. In these documents, [I-D.ietf-sidr-res-certs] is adopted for SEND. In these documents,
the Subject field in the certificates are declared to be meaningless the Subject field in the certificates are declared to be meaningless
and the subjectAltName field is not allowed. On the other hand, the and the subjectAltName field is not allowed. On the other hand, the
Subject Key Identifier (SKI) extension for the X.509 certificates is Subject Key Identifier (SKI) extension for the X.509 certificates is
defined as mandatory and non-critical. defined as mandatory and non-critical.
This document specifies a new Name Type field in the SEND TA option This document specifies a new Name Type field in the SEND TA option
that allows to use of the SKI X.509 extension to identify TA X.509 that allows to use of the SKI X.509 extension to identify TA X.509
certificates. certificates.
3. SEND SKI trust anchor Name Type field. 3. SEND SKI trust anchor option Name Type field
Name Type Name Type
3 SHA-1 Subject Key Identifier (SKI) 3 SHA-1 Subject Key Identifier (SKI)
The Key Identifier used here is the 160-bit SHA-1 hash of the value The Key Identifier used here is the 160-bit SHA-1 hash of the value
of the DER-encoded ASN.1 bit string of the subject public key, as of the DER-encoded ASN.1 bit string of the subject public key, as
described in Section 4.2.1.2 of [RFC5280]. described in Section 4.2.1.2 of [RFC5280].
3.1. Processing Rules for Router 3.1. Processing Rules for Router
As described in RFC 3971, a TA is identified by the SEND TA option. As specified in [RFC3971] , a TA is identified by the SEND TA option.
If the TA option is represented as a SHA-1 SKI, then the SKI must be If the TA option is represented as a SHA-1 SKI, then the SKI must be
equal to the SKI extension in the trust anchor's certificate equal to the SKI extension in the trust anchor's certificate
calculated as described in [draft-ietf-sidr-res-certs-17]. The calculated as described in [draft-ietf-sidr-res-certs-17]. The
router SHOULD include the TA option(s) in the advertisement for which router SHOULD include the TA option(s) in the advertisement for which
the certification path was found. the certification path was found. Also, following [RFC3971]
specification, if the router is unable to find a path to the
If the router is unable to find a path to the requested anchor, it requested anchor, it SHOULD send an advertisement without any
SHOULD send an advertisement without any certificate. In this case, certificate. In this case, the router SHOULD include the TA options
the router SHOULD include the TA options that were solicited. that were solicited.
4. IANA Considerations 4. IANA Considerations
IANA will maintains the registry of Name Type field in the ICMP Trust IANA will maintains the registry of Name Type field in the ICMP Trust
Anchor option. The registry records Name Type fields for the ICMP Anchor option. The registry records Name Type fields for the ICMP
Trust Anchor option (15) defined in the RFC 3971. Trust Anchor option (15) defined in the RFC 3971.
The following Name Type fields are defined: The following Name Type fields are defined:
1 DER Encoded X.501 Name (RFC 3971). 1 DER Encoded X.501 Name (RFC 3971).
 End of changes. 11 change blocks. 
16 lines changed or deleted 16 lines changed or added

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