RFC 2255
E846654
RFC 2255 is an early Internet standard that defined the URL format for accessing LDAP directory services before being superseded by RFC 4516.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2255 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T10158291 — 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 2255 Context triple: [RFC 4516, obsoletes, RFC 2255]
-
A.
RFC 2595
RFC 2595 is an Internet standard that originally defined the use of TLS to secure email-related protocols such as IMAP, POP3, and ACAP.
-
B.
RFC 2575
RFC 2575 is an earlier IETF standard that defined the View-based Access Control Model (VACM) for SNMP before being superseded by RFC 3415.
-
C.
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.
-
D.
RFC 2256
RFC 2256 is an earlier LDAP (Lightweight Directory Access Protocol) schema specification that was later superseded by RFC 4517.
-
E.
RFC 1655
RFC 1655 is an early Internet standards document that specified the original Simple Network Management Protocol (SNMP) version 2 framework before being superseded by later revisions.
- 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 2255 Target entity description: RFC 2255 is an early Internet standard that defined the URL format for accessing LDAP directory services before being superseded by RFC 4516.
-
A.
RFC 2595
RFC 2595 is an Internet standard that originally defined the use of TLS to secure email-related protocols such as IMAP, POP3, and ACAP.
-
B.
RFC 2575
RFC 2575 is an earlier IETF standard that defined the View-based Access Control Model (VACM) for SNMP before being superseded by RFC 3415.
-
C.
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.
-
D.
RFC 2256
RFC 2256 is an earlier LDAP (Lightweight Directory Access Protocol) schema specification that was later superseded by RFC 4517.
-
E.
RFC 1655
RFC 1655 is an early Internet standards document that specified the original Simple Network Management Protocol (SNMP) version 2 framework before being superseded by later revisions.
- F. None of above. chosen
Statements (43)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| appliesTo |
LDAPv2
ⓘ
linked to:
Lightweight Directory Access Protocol
LDAPv3 ⓘ
linked to:
Lightweight Directory Access Protocol
|
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| context | Internet directory access ⓘ |
| defines |
LDAP URL format
ⓘ
URL format for accessing LDAP directory services ⓘ URL scheme ldap: ⓘ components of LDAP URLs such as host, port, dn, attributes, scope, filter, extensions ⓘ default port handling for LDAP URLs ⓘ extension mechanism for LDAP URLs ⓘ percent-encoding rules for LDAP URLs ⓘ query components for LDAP URLs ⓘ |
| documentType | Standards-track RFC ⓘ |
| hasSuccessor | RFC 4516 ⓘ |
| intendedAudience |
LDAP implementers
ⓘ
application developers using LDAP URLs ⓘ protocol designers ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 4516 ⓘ |
| obsoletes | earlier informal LDAP URL descriptions ⓘ |
| partOf | LDAP specifications corpus ⓘ |
| protocol | LDAP ⓘ |
| publishedBy | Internet Engineering Task Force ⓘ |
| relatedTo | Lightweight Directory Access Protocol ⓘ |
| replacedBy | RFC 4516 ⓘ |
| specifies |
semantics of LDAP URLs
ⓘ
syntax of LDAP URLs ⓘ |
| standardizes |
use of URLs to reference LDAP directory entries
ⓘ
use of URLs to reference LDAP searches ⓘ |
| status | Obsoleted ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| supersededBy | LDAP URL format defined in RFC 4516 ⓘ |
| title | The LDAP URL Format ⓘ |
| topic |
Uniform Resource Locators
ⓘ
application-layer protocols ⓘ directory services ⓘ |
| updates | LDAP-related specifications prior to its publication ⓘ |
| usedWith |
LDAP client software
ⓘ
directory user agents ⓘ directory-enabled applications ⓘ |
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 2255 Description of subject: RFC 2255 is an early Internet standard that defined the URL format for accessing LDAP directory services before being superseded by RFC 4516.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.