RFC 2252
E826111
RFC 2252 is an earlier LDAP specification that defines attribute syntax and matching rules, later revised and superseded by RFC 4517.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2252 canonical | 3 |
How this entity was disambiguated
This entity first appeared as the object of triple T9865287 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2252 Context triple: [RFC 4517, updates, RFC 2252]
-
A.
RFC 2572
RFC 2572 is an earlier IETF specification that defined the Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) before being superseded by RFC 3412.
-
B.
RFC 2254
RFC 2254 is an earlier Internet standard that defined the string representation of LDAP search filters before being superseded by RFC 4515.
-
C.
RFC 2440
RFC 2440 is the Internet Engineering Task Force (IETF) specification that defines the OpenPGP message format for encrypted and signed data.
-
D.
RFC 2573
RFC 2573 is an IETF standard that specifies the SNMPv3 applications, including command generator and responder, notification originator and receiver, and proxy forwarder functionality for network management.
-
E.
RFC 2571
RFC 2571 was an earlier specification in the Simple Network Management Protocol (SNMP) framework that was later superseded and updated by RFC 3411.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2252 Target entity description: RFC 2252 is an earlier LDAP specification that defines attribute syntax and matching rules, later revised and superseded by RFC 4517.
-
A.
RFC 2572
RFC 2572 is an earlier IETF specification that defined the Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) before being superseded by RFC 3412.
-
B.
RFC 2254
RFC 2254 is an earlier Internet standard that defined the string representation of LDAP search filters before being superseded by RFC 4515.
-
C.
RFC 2440
RFC 2440 is the Internet Engineering Task Force (IETF) specification that defines the OpenPGP message format for encrypted and signed data.
-
D.
RFC 2573
RFC 2573 is an IETF standard that specifies the SNMPv3 applications, including command generator and responder, notification originator and receiver, and proxy forwarder functionality for network management.
-
E.
RFC 2571
RFC 2571 was an earlier specification in the Simple Network Management Protocol (SNMP) framework that was later superseded and updated by RFC 3411.
- F. None of above. chosen
Statements (36)
| Predicate | Object |
|---|---|
| instanceOf |
LDAP specification
ⓘ
Request for Comments ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines |
LDAP attribute syntaxes
ⓘ
LDAP matching rules ⓘ LDAP object identifier (OID) assignments for syntaxes ⓘ binary and string encodings for attribute values ⓘ equality matching rules ⓘ ordering matching rules ⓘ string representation of attribute values ⓘ substring matching rules ⓘ syntax for directory schema definitions ⓘ syntax for distinguished name components ⓘ |
| language | English ⓘ |
| obsoletedBy |
Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching Rules
ⓘ
RFC 4517 ⓘ |
| protocolFamily |
LDAP
ⓘ
Lightweight Directory Access Protocol ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| publishedIn |
RFC series
ⓘ
linked to:
RFC Series Working Group
|
| relatedTo |
RFC 2251
ⓘ
RFC 2253 ⓘ RFC 2254 ⓘ RFC 2255 ⓘ RFC 2256 ⓘ |
| RFCNumber | 2252 ⓘ |
| scope | LDAPv3 attribute syntax and matching rules ⓘ |
| standardizes | schema elements used in LDAP directories ⓘ |
| status | Obsoleted ⓘ |
| successor | RFC 4517 ⓘ |
| title | Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions ⓘ |
| type | Internet Standard specification ⓘ |
| updatesProtocol |
LDAPv3
ⓘ
linked to:
Lightweight Directory Access Protocol
|
| usedWith |
X.500 directory model
ⓘ
linked to:
X.500
|
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: RFC 2252 Description of subject: RFC 2252 is an earlier LDAP specification that defines attribute syntax and matching rules, later revised and superseded by RFC 4517.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.