RFC 5217: Memorandum for Multi-Domain Public Key Infrastructure Interoperability
In plain English — editorial summary, not part of the RFC
The objective of this document is to establish a terminology framework and to suggest the operational requirements of Public Key Infrastructure (PKI) domain for interoperability of multi-domain Public Key Infrastructure, where each PKI domain is operated under a distinct policy. This document describes the relationships between Certification Authorities (CAs), provides the definition and requirements for PKI domains, and discusses typical models of multi-domain PKI. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5217
- Published
- July 2008
- Authors
- M. Shimaoka; N. Hastings; R. Nielsen
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 29
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5272Certificate Management over CMS (CMC)Obsoleted
June 2008
- RFC 5758Internet X.509 Public Key Infrastructure: Additional Algorithms and Identifiers for DSA and ECDSACurrent
January 2010
- RFC 6010Cryptographic Message Syntax (CMS) Content Constraints ExtensionCurrent
September 2010
- RFC 6024Trust Anchor Management RequirementsCurrent
October 2010
- RFC 4387Internet X.509 Public Key Infrastructure Operational Protocols: Certificate Store Access via HTTPUpdated
February 2006
- RFC 4386Internet X.509 Public Key Infrastructure Repository Locator ServiceUpdated
February 2006
- RFC 4211Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)Updated
September 2005
- RFC 4210Internet X.509 Public Key Infrastructure Certificate Management Protocol (CMP)Obsoleted
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?