draft-ietf-hip-cert-11.txt   draft-ietf-hip-cert-12.txt 
Host Identity Protocol Heer Host Identity Protocol Heer
Internet-Draft Communication and Distributed Internet-Draft Communication and Distributed
Updates: 5201 (if approved) Systems, RWTH Aachen University Updates: 5201 (if approved) Systems, RWTH Aachen University
Intended status: Experimental Varjonen Intended status: Experimental Varjonen
Expires: September 10, 2011 Helsinki Institute for Information Expires: September 15, 2011 Helsinki Institute for Information
Technology Technology
March 9, 2011 March 14, 2011
Host Identity Protocol Certificates Host Identity Protocol Certificates
draft-ietf-hip-cert-11 draft-ietf-hip-cert-12
Abstract Abstract
The CERT parameter is a container for digital certificates. It is The CERT parameter is a container for digital certificates. It is
used for carrying these certificates in Host Identity Protocol (HIP) used for carrying these certificates in Host Identity Protocol (HIP)
control packets. This document specifies the certificate parameter control packets. This document specifies the certificate parameter
and the error signaling in case of a failed verification. and the error signaling in case of a failed verification.
Additionally, this document specifies the representations of Host Additionally, this document specifies the representations of Host
Identity Tags in X.509 version 3 (v3) and SPKI certificates. Identity Tags in X.509 version 3 (v3) and SPKI certificates.
skipping to change at page 1, line 47 skipping to change at page 1, line 47
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 September 10, 2011. This Internet-Draft will expire on September 15, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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
skipping to change at page 5, line 7 skipping to change at page 5, line 7
The next sections outline the use of Host Identity Tags (HITs) in The next sections outline the use of Host Identity Tags (HITs) in
X.509 v3 and in Simple Public Key Infrastructure (SPKI) certificates. X.509 v3 and in Simple Public Key Infrastructure (SPKI) certificates.
X.509 v3 certificates and the handling procedures are defined in X.509 v3 certificates and the handling procedures are defined in
[RFC5280]. The wire format for X.509 v3 is Distinguished Encoding [RFC5280]. The wire format for X.509 v3 is Distinguished Encoding
Rules format as defined in [X.690]. The SPKI, the handling Rules format as defined in [X.690]. The SPKI, the handling
procedures, and the formats are defined in [RFC2693]. procedures, and the formats are defined in [RFC2693].
Hash and Uniform Resource Locator (URL) encodings (3 and 4) are used Hash and Uniform Resource Locator (URL) encodings (3 and 4) are used
as defined in [RFC5996] Section 3.6. Using hash and URL encodings as defined in [RFC5996] Section 3.6. Using hash and URL encodings
results in smaller HIP control packets, but requires the receiver to results in smaller HIP control packets than by including the
resolve the URL or check a local cache against the hash. certificate(s), but requires the receiver to resolve the URL or check
a local cache against the hash.
LDAP URL encodings (5 and 6) are used as defined in [RFC4516]. Using LDAP URL encodings (5 and 6) are used as defined in [RFC4516]. Using
LDAP URL encoding results in smaller HIP control packets but requires LDAP URL encoding results in smaller HIP control packets but requires
the receiver to retrieve the certificate or check a local cache the receiver to retrieve the certificate or check a local cache
against the URL. against the URL.
Distinguished name (DN) encodings (7 and 8) are used as defined in Distinguished name (DN) encodings (7 and 8) are represented by the
string representation of the certificate's subject DN as defined in
[RFC4514]. Using the DN encoding results in smaller HIP control [RFC4514]. Using the DN encoding results in smaller HIP control
packets, but requires the receiver to retrieve the certificate or packets, but requires the receiver to retrieve the certificate or
check a local cache against the DN. check a local cache against the DN.
3. X.509 v3 Certificate Object and Host Identities 3. X.509 v3 Certificate Object and Host Identities
HITs can represent an issuer, a subject, or both in x.509 v3. HITs If needed, HITs can represent an issuer, a subject, or both in x.509
are represented as IPv6 addresses as defined in [RFC4843]. When Host v3. HITs are represented as IPv6 addresses as defined in [RFC4843].
Identifier ( HI ) is used to sign the certificate the respective HIT When Host Identifier ( HI ) is used to sign the certificate the
MUST be placed in to the Issuer Alternative Name (IAN) extension respective HIT MUST be placed in to the Issuer Alternative Name (IAN)
using the GeneralName form iPAddress as defined in [RFC5280]. When extension using the GeneralName form iPAddress as defined in
the certificate is issued for a HIP host, identified by a HIT and HI, [RFC5280]. When the certificate is issued for a HIP host, identified
the respective HIT MUST be placed in to the Subject Alternative Name by a HIT and HI, the respective HIT MUST be placed in to the Subject
(SAN) extension using the GeneralName form iPAddress and the full HI Alternative Name (SAN) extension using the GeneralName form iPAddress
is presented as the subjects public key info as defined in [RFC5280]. and the full HI is presented as the subjects public key info as
defined in [RFC5280].
The following examples illustrate how HITs are presented as issuer The following examples illustrate how HITs are presented as issuer
and subject in the X.509 v3 extension alternative names. and subject in the X.509 v3 extension alternative names.
Format of X509v3 extensions: Format of X509v3 extensions:
X509v3 Issuer Alternative Name: X509v3 Issuer Alternative Name:
IP Address:hit-of-issuer IP Address:hit-of-issuer
X509v3 Subject Alternative Name: X509v3 Subject Alternative Name:
IP Address:hit-of-subject IP Address:hit-of-subject
skipping to change at page 6, line 7 skipping to change at page 6, line 10
X509v3 Subject Alternative Name: X509v3 Subject Alternative Name:
IP Address:2001:1C:5a14:26de:a07C:385b:de35:60e3 IP Address:2001:1C:5a14:26de:a07C:385b:de35:60e3
Appendix B shows a full example X.509 v3 certificate with HIP Appendix B shows a full example X.509 v3 certificate with HIP
content. content.
As another example, consider a managed Public Key Infrastructure As another example, consider a managed Public Key Infrastructure
(PKI) environment in which the peers have certificates that are (PKI) environment in which the peers have certificates that are
anchored in (potentially different) managed trust chains. In this anchored in (potentially different) managed trust chains. In this
scenario, the certificates issued to HIP hosts are signed by scenario, the certificates issued to HIP hosts are signed by
intermediate Certificate Authorities (CAs) up to a root CA. In this intermediate Certification Authorities (CAs) up to a root CA. In
example, the managed PKI environment is neither HIP aware, nor can it this example, the managed PKI environment is neither HIP aware, nor
be configured to compute HITs and include them in the certificates. can it be configured to compute HITs and include them in the
certificates.
When HIP communications are established, the HIP hosts not only need When HIP communications are established, the HIP hosts not only need
to send their identity certificates (or pointers to their to send their identity certificates (or pointers to their
certificates), but also the chain of intermediate CAs (or pointers to certificates), but also the chain of intermediate CAs (or pointers to
the CAs) up to the root CA, or to a CA that is trusted by the remote the CAs) up to the root CA, or to a CA that is trusted by the remote
peer. This chain of certificates MUST be sent in a Cert group as peer. This chain of certificates MUST be sent in a Cert group as
specified in Section 2. The HIP peers validate each other's specified in Section 2. The HIP peers validate each other's
certificates and compute peer HITs based on the certificate public certificates and compute peer HITs based on the certificate public
keys. keys.
skipping to change at page 10, line 14 skipping to change at page 11, line 10
Appendix B. X.509.v3 certificate example Appendix B. X.509.v3 certificate example
This section shows a X.509 v3 certificate with encoded HITs. This section shows a X.509 v3 certificate with encoded HITs.
Certificate: Certificate:
Data: Data:
Version: 3 (0x2) Version: 3 (0x2)
Serial Number: 0 (0x0) Serial Number: 0 (0x0)
Signature Algorithm: sha1WithRSAEncryption Signature Algorithm: sha1WithRSAEncryption
Issuer: CN=2001:1e:d709:1980:5c6a:bb0c:7650:a027 Issuer: CN=Example issuing host, DC=example, DC=com
Validity Validity
Not Before: Jun 22 13:39:32 2010 GMT Not Before: Mar 11 09:01:39 2011 GMT
Not After : Jul 2 13:39:32 2010 GMT Not After : Mar 21 09:01:39 2011 GMT
Subject: CN=2001:1c:5a14:26de:a07c:385b:de35:60e3 Subject: CN=Example subject host, DC=example, DC=com
Subject Public Key Info: Subject Public Key Info:
Public Key Algorithm: rsaEncryption Public Key Algorithm: rsaEncryption
RSA Public Key: (1024 bit) RSA Public Key: (1024 bit)
Modulus (1024 bit): Modulus (1024 bit):
00:b9:5e:cc:d5:d9:7b:39:c2:42:3e:79:49:ad:7f: 00:c0:db:38:50:8e:63:ed:96:ea:c6:c4:ec:a3:36:
0c:bd:0f:12:98:4e:b0:9d:ee:62:76:7a:7b:55:f0: 62:e2:28:e9:74:9c:f5:2f:cb:58:0e:52:54:60:b5:
cc:a2:57:ac:b6:e2:6a:bc:1e:bd:cf:75:30:95:5b: fa:98:87:0d:22:ab:d8:6a:61:74:a9:ee:0b:ae:cd:
92:af:75:55:69:0b:c3:48:0f:b5:e4:15:30:79:89: 18:6f:05:ab:69:66:42:46:00:a2:c0:0c:3a:28:67:
22:b3:fd:7e:51:59:d2:0d:d7:12:5d:44:f3:e8:05: 09:cc:52:27:da:79:3e:67:d7:d8:d0:7c:f1:a1:26:
13:1f:5b:4f:89:fa:1e:6d:83:e9:e2:cf:bd:5c:6f: fa:38:8f:73:f5:b0:20:c6:f2:0b:7d:77:43:aa:c7:
ef:02:1e:c8:db:9a:48:9a:35:b8:b8:be:89:be:ab: 98:91:7e:1e:04:31:0d:ca:94:55:20:c4:4f:ba:b1:
c8:dd:60:44:df:ac:01:b7:76:66:ab:5d:a1:a5:d0: df:d4:61:9d:dd:b9:b5:47:94:6c:06:91:69:30:42:
3c:8d:22:04:d4:24:59:60:0f 9c:0a:8b:e3:00:ce:49:ab:e3
Exponent: 65537 (0x10001) Exponent: 65537 (0x10001)
X509v3 extensions: X509v3 extensions:
X509v3 Issuer Alternative Name: X509v3 Issuer Alternative Name:
IP Address:2001:1e:d709:1980:5c6a:bb0C:7650:a027 IP Address:2001:13:8D83:41C5:DC9F:38ED:E742:7281
X509v3 Subject Alternative Name: X509v3 Subject Alternative Name:
IP Address:2001:1c:5a14:26de:a07c:385b:de35:60e3 IP Address:2001:1C:6E02:D3E0:9B90:8417:673E:99DB
Signature Algorithm: sha1WithRSAEncryption Signature Algorithm: sha1WithRSAEncryption
48:a1:25:fb:01:31:d9:80:76:1b:1a:2d:00:f1:26:22:3c:3b: 83:68:b4:38:63:a6:ae:57:68:e2:4d:73:5d:8f:11:e4:ba:30:
20:a0:cb:b2:28:d2:0c:21:d3:9e:3b:4a:ab:3d:f6:ea:ad:46: a0:19:ca:86:22:e9:6b:e9:36:96:af:95:bd:e8:02:b9:72:2f:
f6:f5:c4:4f:71:ce:3e:7b:65:8d:58:75:2e:99:25:82:5f:73: 30:a2:62:ac:b2:fa:3d:25:c5:24:fd:8d:32:aa:01:4f:a5:8a:
10:c6:c2:f0:4b:35:ff:5c:65:ac:fc:a4:a7:76:50:ab:62:50: f5:06:52:56:0a:86:55:39:2b:ee:7a:7b:46:14:d7:5d:15:82:
b8:86:21:e6:83:e1:c1:3d:20:c9:8e:13:ab:d7:4b:d4:ab:2d: 4d:74:06:ca:b7:8c:54:c1:6b:33:7f:77:82:d8:95:e1:05:ca:
72:9d:f0:9f:5f:e0:6f:95:fa:a1:95:64:3f:74:63:e5:a8:1d: e2:0d:22:1d:86:fc:1c:c4:a4:cf:c6:bc:ab:ec:b8:2a:1e:4b:
f7:e6:48:98:33:53:7b:91:6d:b0:cb:af:32:15:8c:e0:01:a0: 04:7e:49:9c:8f:9d:98:58:9c:63:c5:97:b5:41:94:f7:ef:93:
a0:b8 57:29
Appendix C. Change log Appendix C. Change log
Changes from version 00 to 01: Changes from version 00 to 01:
o Revised text on DN usage. o Revised text on DN usage.
o Revised text on Cert group usage. o Revised text on Cert group usage.
Changes from version 01 to 02: Changes from version 01 to 02:
skipping to change at page 13, line 5 skipping to change at page 13, line 42
o IANA considerations updated based on the IANA review. o IANA considerations updated based on the IANA review.
o Updates based on the hip-chairs review. o Updates based on the hip-chairs review.
o Updates based on the Gen-ART review. o Updates based on the Gen-ART review.
Changes from version 10 to 11: Changes from version 10 to 11:
o Fixed the nits. o Fixed the nits.
Changes from version 11 to 12:
o Updates based on the PKIX WG review.
Authors' Addresses Authors' Addresses
Tobias Heer Tobias Heer
Communication and Distributed Systems, RWTH Aachen University Communication and Distributed Systems, RWTH Aachen University
Ahornstrasse 55 Ahornstrasse 55
Aachen Aachen
Germany Germany
Phone: +49 241 80 20 776 Phone: +49 241 80 20 776
Email: heer@cs.rwth-aachen.de Email: heer@cs.rwth-aachen.de
 End of changes. 15 change blocks. 
42 lines changed or deleted 50 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/