RFC 8002: Host Identity Protocol Certificates
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8002
- Published
- October 2016
- Authors
- T. Heer; S. Varjonen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8003Host Identity Protocol (HIP) Registration ExtensionCurrent
October 2016
- RFC 8004Host Identity Protocol (HIP) Rendezvous ExtensionCurrent
October 2016
- RFC 8005Host Identity Protocol (HIP) Domain Name System (DNS) ExtensionCurrent
October 2016
- RFC 8021Generation of IPv6 Atomic Fragments Considered HarmfulCurrent
January 2017
- RFC 8025IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) Paging DispatchCurrent
November 2016
- RFC 8026Unified IPv4-in-IPv6 Softwire Customer Premises Equipment (CPE): A DHCPv6-Based Prioritization MechanismCurrent
November 2016
- RFC 8028First-Hop Router Selection by Hosts in a Multi-Prefix NetworkCurrent
November 2016
- RFC 7973Assignment of an Ethertype for IPv6 with Low-Power Wireless Personal Area Network (LoWPAN) EncapsulationCurrent
November 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?