Host Identity Protocol Certificates
RFC 8002
| Document | Type |
RFC - Proposed Standard
(October 2016; No errata)
Obsoletes RFC 6253
Updates RFC 7401
|
|
|---|---|---|---|
| Authors | Tobias Heer , Samu Varjonen | ||
| Last updated | 2018-12-20 | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats | plain text html pdf htmlized (tools) htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Gonzalo Camarillo | ||
| Shepherd write-up | Show (last changed 2015-11-08) | ||
| IESG | IESG state | RFC 8002 (Proposed Standard) | |
| Action Holders |
(None)
|
||
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Terry Manderson | ||
| Send notices to | "Gonzalo Camarillo" <gonzalo.camarillo@ericsson.com> | ||
| IANA | IANA review state | IANA OK - Actions Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) T. Heer
Request for Comments: 8002 Albstadt-Sigmaringen University
Obsoletes: 6253 S. Varjonen
Updates: 7401 University of Helsinki
Category: Standards Track October 2016
ISSN: 2070-1721
Host Identity Protocol Certificates
Abstract
The Certificate (CERT) parameter is a container for digital
certificates. It is used for carrying these certificates in Host
Identity Protocol (HIP) control packets. This document specifies the
certificate parameter and the error signaling in case of a failed
verification. Additionally, this document specifies the
representations of Host Identity Tags (HITs) in X.509 version 3 (v3).
The concrete use cases of certificates, including how certificates
are obtained and requested and which actions are taken upon
successful or failed verification, are specific to the scenario in
which the certificates are used. Hence, the definition of these
scenario-specific aspects is left to the documents that use the CERT
parameter.
This document updates RFC 7401 and obsoletes RFC 6253.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc8002.
Heer & Varjonen Standards Track [Page 1]
RFC 8002 HIP CERT October 2016
Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. CERT Parameter . . . . . . . . . . . . . . . . . . . . . . . 3
3. X.509 v3 Certificate Object and Host Identities . . . . . . . 5
4. Revocation of Certificates . . . . . . . . . . . . . . . . . 6
5. Error Signaling . . . . . . . . . . . . . . . . . . . . . . . 7
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
7. Security Considerations . . . . . . . . . . . . . . . . . . . 8
8. Differences from RFC 6253 . . . . . . . . . . . . . . . . . . 8
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
9.1. Normative References . . . . . . . . . . . . . . . . . . 9
9.2. Informative References . . . . . . . . . . . . . . . . . 10
Appendix A. X.509 v3 Certificate Example . . . . . . . . . . . . 11
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
Heer & Varjonen Standards Track [Page 2]
RFC 8002 HIP CERT October 2016
1. Introduction
Digital certificates bind pieces of information to a public key by
means of a digital signature and thus enable the holder of a private
key to generate cryptographically verifiable statements. The Host
Identity Protocol (HIP) [RFC7401] defines a new cryptographic
namespace based on asymmetric cryptography. The identity of each
host is derived from a public key, allowing hosts to digitally sign
data and issue certificates with their private key. This document
specifies the CERT parameter, which is used to transmit digital
certificates in HIP. It fills the placeholder specified in
Section 5.2 of [RFC7401] and thus updates [RFC7401].
1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
RFC 2119 [RFC2119].
2. CERT Parameter
The CERT parameter is a container for certain types of digital
Show full document text