Browse Prior Art Database

Host Identity Protocol Certificates (RFC8002) Disclosure Number: IPCOM000248001D
Original Publication Date: 2016-Oct-01
Included in the Prior Art Database: 2016-Oct-15
Document File: 26 page(s) / 27K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

T. Heer: AUTHOR [+2]


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].

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 10% of the total text.

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


   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

 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    ( 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   ...