RFC 2559(Site not responding. Last check: 2007-10-11)
For this reason, these attributes MUST be encoded using a syntax similar to the syntax "Undefined" from section 2.1 of RFC1778: values of these attributes are encoded as if they were values of type "OCTET STRING", with the string value of the encoding being the DER- encoding of the value itself.
RFC 2559 PKIX Operational Protocols - LDAPv2 April 1999 style is consistent with the encoding scheme proposed for LDAPv3, which is now being defined within the IETF.
Note that certificates and revocation lists will be transferred using this mechanism rather than the string encodings in RFC1778 and client systems which do not understand this encoding may experience problems with these attributes.
In accordance with RFC 2026, section 4.4.1, this specification is being approved by IESG as a Proposed Standard despite this limitation, for the following reasons: a.
Standards Track [Page 11] RFC 2252 LADPv3 Attributes December 1997 A client could then make use of this matching rule by sending a search operation in which the filter is of the extensibleMatch choice, the matchingRule field is "soundAlikeMatch", and the type field is "2.5.4.41" or "2.5.4.15".
The BNF notation in RFC1778 for "Certificate Pair" is not recommended to be used.
Abstract This document is a revision to [RFC 1632]: A Revised Catalog of Available X.500 Implementations and is based on the results of data collection via a WWW home page that enabled implementors to submit new or updated descriptions of currently available implementations of X.500, including commercial products and openly available offerings.
This URL Apple and Rossen Informational [Page 2] RFC 2116 X.500 Implementations Catalog-96 April 1997 (http://www.internic.net/projects/x500catalog/catalogtop.html) was advertised on the following directory-related mailing lists: iso@nic.ddn.mil, isode@nic.ddn.mil, osi-ds@cs.ucl.ac.uk, ids@merit.edu, ietf-asid@umich.edu, mhs-ds@mercury.udev.cdc.com, nadf-l@ema.org, and dssig@nist.gov. Readers are encouraged to submit comments regarding both the forms and content of this memo.
Apple and Rossen Informational [Page 50] RFC 2116 X.500 Implementations Catalog-96 April 1997 NAME DE ABSTRACT DE (Directory Enquiries) is intended to be a simple-to-use DUA interface, suitable for the naive user, and suitable for running as a public access dua.
www.packetizer.com /rfc/rfc2116 (9312 words)
RFC1778(Site not responding. Last check: 2007-10-11)
RFC1778 Syntax Encoding March 1995 third wherever possible.
That is, in encoding object identifiers, object descriptors (where assigned and known by the implementation) should be used in preference to numeric oids to the greatest extent possible.
RFC1778 Syntax Encoding March 1995 The syntactic component has the same definition as in the BNF for the userCertificate attribute syntax.
RFC1778 is The String Representation of Standard Attribute Syntaxes for LDAP, the Lightweight Directory Access Protocol.
RFC1778 describes the formats for use in LDAPv2 for some of the more common attribute types, like mail or jpegPhoto.
LDAPv2 is considered obsolete in favor of version 3 of LDAP specified in RFC 4510.
en.wikipedia.org /wiki/RFC_1778 (190 words)
RFC 2116 - X.500 Implementations Catalog-96. C. Apple, K. Rossen.(Site not responding. Last check: 2007-10-11)
RFC 2116 X.500 Implementations Catalog-96 April 1997 (http://www.internic.net/projects/x500catalog/catalogtop.html) was advertised on the following directory-related mailing lists: iso@nic.ddn.mil, isode@nic.ddn.mil, osi-ds@cs.ucl.ac.uk, ids@merit.edu, ietf-asid@umich.edu, mhs-ds@mercury.udev.cdc.com, nadf-l@ema.org, and dssig@nist.gov. Readers are encouraged to submit comments regarding both the forms and content of this memo.
RFC 2116 X.500 Implementations Catalog-96 April 1997 AVAILABILITY A statement regarding the availability of the software (free or commercially available), a description of how to obtain the software, and (optionally) a statement regarding distribution conditions and restrictions.
RFC 2116 X.500 Implementations Catalog-96 April 1997 NAME DE ABSTRACT DE (Directory Enquiries) is intended to be a simple-to-use DUA interface, suitable for the naive user, and suitable for running as a public access dua.
This RFC specifies criteria related to mobility for consideration in design and selection of the Next Generation of IP.
As required by Routing Protocol Criteria (RFC 1264), this report defines the applicability of the RIP-2 protocol within the Internet.This report is a prerequisite to advancing RIP-2 on the standards track.
RFC 1243 defines a set of MIB objects for managing the lower layers of the AppleTalk protocol stack, up to the Network layer.
RFC 2559 - Internet X.509 Public Key Infrastructure Operational Protocols - LDAPv2(Site not responding. Last check: 2007-10-11)
Standards Track [Page 4] RFC 2559 PKIX Operational Protocols - LDAPv2 April 1999 An application providing a LDAP repository read service MAY implement other aspects of the SearchRequest as well.
Standards Track [Page 9] RFC 2559 PKIX Operational Protocols - LDAPv2 April 1999 style is consistent with the encoding scheme proposed for LDAPv3, which is now being defined within the IETF.
Standards Track [Page 10] RFC 2559 PKIX Operational Protocols - LDAPv2 April 1999 The CA MUST have access control permissions allowing it to: For CA entries: - add, modify and delete all PKI attributes for its own directory entry; - add, modify and delete all values of these attributes.
RFC2559(Site not responding. Last check: 2007-10-11)
RFC 2559 PKIX Operational Protocols - LDAPv2 April 1999
The full LDAPv2 BindResponse is described in RFC 1777.
When conveyed in LDAP requests and results, attributes defined in X.500 are to be encoded using string representations defined in RFC1778, The String Representation of Standard Attribute Syntaxes.
rfc.net /rfc2559.html (2200 words)
Common LDAP RFCs(Site not responding. Last check: 2007-10-11)
RFC1778 - The String Representation of Standard Attribute Syntaxes (http://www.cse.ohio-state.edu/cgi-bin/cis-redirect/htbin/rfc/rfc1778.html)
This document defines the requirements that must be satisfied by encoding rules used to render X.500 directory attribute syntaxes into a form suitable for use in the LDAP, and then goes on to define the encoding rules for the standard set of attribute syntaxes.
This document replaces RFC 1960 (http://www.cse.ohio-state.edu/cgi-bin/cis-redirect/htbin/rfc/rfc1960.html), extending the string LDAP filter definition to include support for LDAP version 3 extended match filters, and including support for representing the full range of possible LDAP search filters.
This document is a revision to [RFC 1632]: A Revised Catalog of Available X.500 Implementations and is based on the results of data collection via a WWW home page that enabled implementors to submit new or updated descriptions of currently available implementations of X.500, including commercial products and openly available offerings.
Implementation supports [RFC1778]: Howes, T., Kille, S., Yeong, W., and Robbins, The String Representation of Standard Attribute Syntaxes, March 1995.
Implementation supports [RFC 1801]: Kille, S., MHS Use of the X.500 Directory to support MHS Routing, June 1995.
In particular, encoding rules for attribute syntaxes defining non-binary values should produce strings that can be displayed with little or no translation by clients implementing the lightweight directory protocols.
Case Exact String The encoding of a string of type caseExactStringSyntax is the string value itself.
When encoding values of type objectIdentifierSyntax, the first encoding option should be used in preference to the second, which should be used in preference to the Howes, Kille, Yeong & Robbins [Page 4] RFC1778 Syntax Encoding March 1995 third wherever possible.
www.ietf.org /rfc/rfc1778.txt (1458 words)
RedIRIS - RFCs e Internet-Drafts sobre LDAP/X500(Site not responding. Last check: 2007-10-11)
RFC1778 - The String Representation of Standard Attribute Syntaxes
RFC 1838 - Use of the X.500 Directory to support mapping between X.400 and RFC 822 Addresses - 2164
RFC 2256 - A Summary of the X.500(96) User Schema for use with LDAPv3
An application providing a LDAP repository read service MAY implement other aspects of the SearchRequest as well.
An application providing a LDAP repository search service MAY implement other aspects of the SearchRequest as well.
For example, when writing a userCertificate to the repository, the CA generates a DER-encoding of the certificate and uses that encoding as the value of the userCertificate attribute in the LDAP Modify request.This encoding
