2002
DOI: 10.17487/rfc3377
|View full text |Cite
|
Sign up to set email alerts
|

Lightweight Directory Access Protocol (v3): Technical Specification

Abstract: 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.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
41
0
1

Year Published

2003
2003
2008
2008

Publication Types

Select...
6
3
1

Relationship

0
10

Authors

Journals

citations
Cited by 61 publications
(42 citation statements)
references
References 1 publication
0
41
0
1
Order By: Relevance
“…The Lightweight Directory Access Protocol (LDAP) [RFC3377] provides an Abandon operation [RFC2251] which clients may use to cancel other operations. The Abandon operation does not have a response and requires no response from the abandoned operation.…”
Section: Background and Intent Of Usementioning
confidence: 99%
“…The Lightweight Directory Access Protocol (LDAP) [RFC3377] provides an Abandon operation [RFC2251] which clients may use to cancel other operations. The Abandon operation does not have a response and requires no response from the abandoned operation.…”
Section: Background and Intent Of Usementioning
confidence: 99%
“…Since its publication, a number of inadequacies in the specification have been discovered. LDAPv3 [RFC3377] 2) RFC 1777 requires use of the textual string associated with AttributeType in the X.500 Directory standards. However, existing implementations use the NAME associated with the AttributeType in the LDAPv3 schema [RFC2252].…”
Section: Ldapv2 (Lightweight Directory Access Protocol Version 2) [Rmentioning
confidence: 99%
“…The LDAP technical specification [RFC4510] has obsoleted the previously defined LDAP technical specification [RFC3377], which included RFC 2251. The binary option was not included in the revised LDAP technical specification for a variety of reasons including implementation inconsistencies.…”
Section: Introductionmentioning
confidence: 99%