Host Identity Protocol Certificates
RFC 6253

Document Type RFC - Experimental (May 2011; No errata)
Obsoleted by RFC 8002
Updates RFC 5201
Last updated 2015-10-14
Replaces draft-varjonen-hip-cert
Stream IETF
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state RFC 6253 (Experimental)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Ralph Droms
IESG note Gonzalo Camarillo ( is the document shepherd.
Send notices to (None)
Internet Engineering Task Force (IETF)                           T. Heer
Request for Comments: 6253                COMSYS, RWTH Aachen University
Updates: 5201                                                S. Varjonen
Category: Experimental     Helsinki Institute for Information Technology
ISSN: 2070-1721                                                 May 2011

                  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
   CERT parameter and the error signaling in case of a failed
   verification.  Additionally, this document specifies the
   representations of Host Identity Tags in X.509 version 3 (v3) and
   Simple Public Key Infrastructure (SPKI) certificates.

   The concrete use of certificates, including how certificates are
   obtained, requested, and which actions are taken upon successful or
   failed verification, is 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

   This document updates RFC 5201.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for examination, experimental implementation, and

   This document defines an Experimental Protocol for the Internet
   community.  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).  Not
   all documents approved by the IESG are a candidate for any level of
   Internet Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at

Heer & Varjonen               Experimental                      [Page 1]
RFC 6253                        HIP CERT                        May 2011

Copyright Notice

   Copyright (c) 2011 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
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

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) [RFC5201] 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 [RFC5201] and thus updates [RFC5201].

1.1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "OPTIONAL" in this document are to be interpreted as described in
   RFC 2119 [RFC2119].

Heer & Varjonen               Experimental                      [Page 2]
RFC 6253                        HIP CERT                        May 2011
Show full document text