RFC 4158: Internet X.509 Public Key Infrastructure: Certification Path Building
In plain English — editorial summary, not part of the RFC
This document provides guidance and recommendations to developers building X.509 public-key certification paths within their applications. By following the guidance and recommendations defined in this document, an application developer is more likely to develop a robust X.509 certificate-enabled application that can build valid certification paths across a wide range of PKI environments. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4158
- Published
- September 2005
- Authors
- M. Cooper; Y. Dzambasow; P. Hesse; S. Joseph; R. Nicholas
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 81
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4178The Simple and Protected Generic Security Service Application Program Interface (GSS-API) Negotiation MechanismCurrent
October 2005
- RFC 4134Examples of S/MIME MessagesCurrent
July 2005
- RFC 4132Addition of Camellia Cipher Suites to Transport Layer Security (TLS)Obsoleted
July 2005
- RFC 4121The Kerberos Version 5 Generic Security Service Application Program Interface (GSS-API) Mechanism: Version 2Updated
July 2005
- RFC 4120The Kerberos Network Authentication Service (V5)Updated
July 2005
- RFC 4210Internet X.509 Public Key Infrastructure Certificate Management Protocol (CMP)Obsoleted
September 2005
- RFC 4106The Use of Galois/Counter Mode (GCM) in IPsec Encapsulating Security Payload (ESP)Current
June 2005
- RFC 4211Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)Updated
September 2005
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?