RFC 4809: Requirements for an IPsec Certificate Management Profile
In plain English — editorial summary, not part of the RFC
This informational document describes and identifies the requirements for transactions to handle Public Key Certificate (PKC) lifecycle transactions between Internet Protocol Security (IPsec) Virtual Private Network (VPN) Systems using Internet Key Exchange (IKE) (versions 1 and 2) and Public Key Infrastructure (PKI) Systems. These requirements are designed to meet the needs of enterprise-scale IPsec VPN deployments. It is intended that a standards track profile of a management protocol will be created to address many of these requirements. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4809
- Published
- February 2007
- Authors
- C. Bonatti; S. Turner; G. Lebovitz
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 45
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4555IKEv2 Mobility and Multihoming Protocol (MOBIKE)Current
June 2006
- RFC 5386Better-Than-Nothing Security: An Unauthenticated Mode of IPsecCurrent
November 2008
- RFC 3602The AES-CBC Cipher Algorithm and Its Use with IPsecCurrent
September 2003
- RFC 3585IPsec Configuration Policy Information ModelCurrent
August 2003
- RFC 3566The AES-XCBC-MAC-96 Algorithm and Its Use With IPsecCurrent
September 2003
- RFC 2857The Use of HMAC-RIPEMD-160-96 within ESP and AHCurrent
June 2000
- RFC 2451The ESP CBC-Mode Cipher AlgorithmsCurrent
November 1998
- RFC 2410The NULL Encryption Algorithm and Its Use With IPsecCurrent
November 1998
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?