draft-ietf-csi-send-name-type-registry-04.txt   draft-ietf-csi-send-name-type-registry-05.txt 
Network Working Group R. Gagliano Network Working Group R. Gagliano
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Updates: 3971 (if approved) S. Krishnan Updates: 3971 (if approved) S. Krishnan
Intended status: Standards Track Ericsson Intended status: Standards Track Ericsson
Expires: November 19, 2010 A. Kukec Expires: December 4, 2010 A. Kukec
University of Zagreb University of Zagreb
May 18, 2010 June 2, 2010
Subject Key Identifier (SKI) SEND Name Type fields. Subject Key Identifier (SKI) SEND Name Type fields.
draft-ietf-csi-send-name-type-registry-04 draft-ietf-csi-send-name-type-registry-05
Abstract Abstract
SEcure Neighbor Discovery (SEND) defines the Name Type field in the SEcure Neighbor Discovery (SEND) defines the Name Type field in the
ICMPv6 Trust Anchor option. This document specifies new Name Type ICMPv6 Trust Anchor option. This document specifies new Name Type
fields based on certificate Subject Key Identifiers (SKI). fields based on certificate Subject Key Identifiers (SKI).
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 November 19, 2010. This Internet-Draft will expire on December 4, 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3 1. Requirements notation . . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Name Type fields in the ICMPv6 TA option defined in this 3. Name Type fields in the ICMPv6 TA option defined in this
document . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 document . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Processing Rules for Routers . . . . . . . . . . . . . . . . . 6 4. Processing Rules for Routers . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
6. Security Considerations . . . . . . . . . . . . . . . . . . . 8 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
7. Normative References . . . . . . . . . . . . . . . . . . . . . 9 7. Normative References . . . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
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
skipping to change at page 5, line 25 skipping to change at page 4, line 21
7 SHA-512 Subject Key Identifier (SKI). 7 SHA-512 Subject Key Identifier (SKI).
253-254 Experimental 253-254 Experimental
255 Reserved 255 Reserved
Name Type field values 0 and 255 are marked as reserved. This means Name Type field values 0 and 255 are marked as reserved. This means
that they are not available for allocation. that they are not available for allocation.
When the Name Type field is set to 3, the Name Type field contains a When the Name Type field is set to 3, the Name Type field contains a
160-bit SHA-1 hash of the value of the DER-encoded ASN.1 bit string 160-bit SHA-1 hash of the value of the DER-encoded ASN.1 bit string
of the subject public key, as described in Section 3.9.2 of of the subject public key, as described in Section 3.9.2 of
[I-D.ietf-sidr-res-certs]. Implementations MAY support SHA-1 SKY [I-D.ietf-sidr-res-certs]. Implementations MAY support SHA-1 SKI
name type. name type.
When the Name Type field is set to 4,5,6 or 7, the hash function will When the Name Type field is set to 4,5,6 or 7, the hash function will
respectively be: SHA-224, SHA-256, SHA-284 or SHA-512. respectively be: SHA-224, SHA-256, SHA-384 or SHA-512.
Implementations MAY support SHA-224, SHA-256, SHA-284 and SHA-512 Implementations MAY support SHA-224, SHA-256, SHA-284 and SHA-512 SKI
name types. name types.
Name Type fields 253 and 254 are marked as experimental, following Name Type fields 253 and 254 are marked as experimental, following
[RFC3692]. [RFC3692].
4. Processing Rules for Routers 4. Processing Rules for Routers
As specified in [RFC3971], 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 SKI, then the SKI MUST be equal If the TA option is represented as a SKI, then the SKI MUST be equal
to the X.509 SKI extension in the trust anchor's certificate. The to the X.509 SKI extension in the trust anchor's certificate. The
skipping to change at page 7, line 14 skipping to change at page 5, line 9
5. IANA Considerations 5. IANA Considerations
IANA is requested to update the Name Type field in the ICMPv6 Trust IANA is requested to update the Name Type field in the ICMPv6 Trust
Anchor option registry by adding the following values: Anchor option registry by adding the following values:
+---------+----------------------------------------------------+ +---------+----------------------------------------------------+
| Value | Description | | Value | Description |
+---------+----------------------------------------------------+ +---------+----------------------------------------------------+
| 0 | Reserved ( Section 3 ) | | 0 | Reserved ( Section 3 ) |
| | |
| 3 | SHA-1 Subject Key Identifier (SKI) ( Section 3 ) | | 3 | SHA-1 Subject Key Identifier (SKI) ( Section 3 ) |
| | |
| 4 | SHA-224 Subject Key Identifier (SKI) ( Section 3 ) | | 4 | SHA-224 Subject Key Identifier (SKI) ( Section 3 ) |
| | |
| 5 | SHA-256 Subject Key Identifier (SKI) ( Section 3 ) | | 5 | SHA-256 Subject Key Identifier (SKI) ( Section 3 ) |
| | |
| 6 | SHA-384 Subject Key Identifier (SKI) ( Section 3 ) | | 6 | SHA-384 Subject Key Identifier (SKI) ( Section 3 ) |
| | |
| 7 | SHA-512 Subject Key Identifier (SKI) ( Section 3 ) | | 7 | SHA-512 Subject Key Identifier (SKI) ( Section 3 ) |
| | |
| 253-254 | Experimental use ( Section 3 ) | | 253-254 | Experimental use ( Section 3 ) |
| | |
| 255 | Reserved ( Section 3 ) | | 255 | Reserved ( Section 3 ) |
+---------+----------------------------------------------------+ +---------+----------------------------------------------------+
Table 1: New Name Type field values in the ICMPv6 TA option Table 1: New Name Type field values in the ICMPv6 TA option
IANA is also requested to modify the registration procedures for the IANA is also requested to modify the registration procedures for the
Name Type field in the ICMPv6 Trust Anchor option registry to Name Type field in the ICMPv6 Trust Anchor option registry to
Standard Action or IESG Approval. Standard Action or IESG Approval.
6. Security Considerations 6. Security Considerations
 End of changes. 15 change blocks. 
22 lines changed or deleted 15 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/