RFC 4806: Online Certificate Status Protocol (OCSP) Extensions to IKEv2

In plain English — editorial summary, not part of the RFC

While the Internet Key Exchange Protocol version 2 (IKEv2) supports public key based authentication, the corresponding use of in-band Certificate Revocation Lists (CRL) is problematic due to unbounded CRL size. The size of an Online Certificate Status Protocol (OCSP) response is however well-bounded and small. This document defines the "OCSP Content" extension to IKEv2. A CERTREQ payload with "OCSP Content" identifies zero or more trusted OCSP responders and is a request for inclusion of an OCSP response in the IKEv2 handshake. A cooperative recipient of such a request responds with a CERT payload containing the appropriate OCSP response. This content is recognizable via the same "OCSP Content" identifier. When certificates are used with IKEv2, the communicating peers need a mechanism to determine the revocation status of the peer's certificate. OCSP is one such mechanism. This document applies when OCSP is desired and security policy prevents one of the IKEv2 peers from accessing the relevant OCSP responder directly. Firewalls are often deployed in a manner that prevents such access by IKEv2 peers outside of an enterprise network. [STANDARDS-TRACK]

Document record

Document ID

RFC4806

Published

February 2007

Authors

M. Myers; H. Tschofenig

Status

PROPOSED STANDARD

Stream

IETF

Area

—

Pages

11

Also known as

—

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC4806

Topics

• internet key exchange version 2

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 7670Generic Raw Public-Key Support for IKEv2Current

  January 2016

Also filed under

• PROPOSED STANDARD
• 2007
• IETF stream