RFC 2559:Internet X.509 Public Key Infrastructure ...
RFC-Ref

RFC - 2559

Internet X.509 Public Key Infrastructure Operational Protocols - LDAPv2

Original: ftp://ftp.isi.edu/in-notes/rfc2559.txt
Authors: S. Boeyen [Entrust], T. Howes [Netscape], P. Richard [Xcert]
Date: April 1999
Category: Informational
 
This specification has been !!! obsoleted !!!
 
This specification has been assigned to Historic level (A specification that has been superseded by a more recent specification or is for any other reason considered to be obsolete.)



Obsoleted by:
RFC-3494 Lightweight Directory Access Protocol version 2 (LDAPv2) to Historic Status

Updates:
RFC-1778hist The String Representation of Standard Attribute Syntaxes (Obsoleted by RFC-3494) (Updated by RFC-2559hist)

Referred by: 13 RFC
Refers to: 3 RFC

Status

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (1999). All Rights Reserved.

Abstract

The protocol described in this document is designed to satisfy some of the operational requirements within the Internet X.509 Public Key Infrastructure (IPKI). Specifically, this document addresses requirements to provide access to Public Key Infrastructure (PKI) repositories for the purposes of retrieving PKI information and managing that same information. The mechanism described in this document is based on the Lightweight Directory Access Protocol (LDAP) v2, defined in RFC 1777hist(-> 3494), defining a profile of that protocol for use within the IPKI and updates encodings for certificates and revocation lists from RFC 1778hist(-> 3494). Additional mechanisms addressing PKIX operational requirements are specified in separate documents.

The key words 'MUST', 'REQUIRED', 'SHOULD', 'RECOMMENDED', and 'MAY' in this document are to be interpreted as described in RFC 2119.


About Resource

Google
Web
RFC-Ref