RFC 4516
E233825
RFC 4516 is an Internet standard that specifies the LDAP (Lightweight Directory Access Protocol) Uniform Resource Locator (URL) format used to locate and access directory entries over a network.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 4516 canonical | 13 |
How this entity was disambiguated
This entity first appeared as the object of triple T2114355 — 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 4516 Context triple: [LDAP, definedInRFC, RFC 4516]
-
A.
RFC 3416
RFC 3416 is an Internet standard that specifies the protocol operations for the Simple Network Management Protocol (SNMP), defining how management data is exchanged between network devices and management systems.
-
B.
RFC 6145
RFC 6145 is an IETF standard that specifies the stateless translation mechanism between IPv4 and IPv6 packet headers used in NAT64 environments.
-
C.
RFC 6146
RFC 6146 is an IETF standard that specifies the behavior and requirements for NAT64, enabling IPv6-only clients to communicate with IPv4 servers through protocol translation.
-
D.
RFC 1651
RFC 1651 is an early Internet standards document that defined extensions to the Simple Mail Transfer Protocol (SMTP) to support enhanced email functionality.
-
E.
RFC 5661
RFC 5661 is the Internet Engineering Task Force (IETF) standard that specifies version 4.1 of the Network File System (NFS) protocol, detailing its architecture, operations, and extensions for distributed file access.
- 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 4516 Target entity description: RFC 4516 is an Internet standard that specifies the LDAP (Lightweight Directory Access Protocol) Uniform Resource Locator (URL) format used to locate and access directory entries over a network.
-
A.
RFC 3416
RFC 3416 is an Internet standard that specifies the protocol operations for the Simple Network Management Protocol (SNMP), defining how management data is exchanged between network devices and management systems.
-
B.
RFC 6145
RFC 6145 is an IETF standard that specifies the stateless translation mechanism between IPv4 and IPv6 packet headers used in NAT64 environments.
-
C.
RFC 6146
RFC 6146 is an IETF standard that specifies the behavior and requirements for NAT64, enabling IPv6-only clients to communicate with IPv4 servers through protocol translation.
-
D.
RFC 1651
RFC 1651 is an early Internet standards document that defined extensions to the Simple Mail Transfer Protocol (SMTP) to support enhanced email functionality.
-
E.
RFC 5661
RFC 5661 is the Internet Engineering Task Force (IETF) standard that specifies version 4.1 of the Network File System (NFS) protocol, detailing its architecture, operations, and extensions for distributed file access.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| appliesTo |
URI schemes
ⓘ
directory services ⓘ network protocols ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| concerns | directory access over TCP-IP networks ⓘ |
| defines |
LDAP URL format
ⓘ
default values for omitted LDAP URL components ⓘ handling of IPv6 addresses in LDAP URLs ⓘ ldap URL scheme ⓘ ldapi URL scheme ⓘ ldaps URL scheme ⓘ percent-encoding rules for LDAP URLs ⓘ |
| definesComponent |
attributes list in LDAP URL
ⓘ
distinguished name part of LDAP URL ⓘ extensions in LDAP URL ⓘ filter in LDAP URL ⓘ host and port part of LDAP URL ⓘ scope in LDAP URL ⓘ |
| definesSyntaxFor |
ldap: URI scheme
ⓘ
ldapi: URI scheme ⓘ ldaps: URI scheme ⓘ |
| intendedAudience |
application developers using LDAP
ⓘ
directory service developers ⓘ protocol implementers ⓘ |
| obsoletes | RFC 2255 ⓘ |
| partOf | LDAP technical specification ⓘ |
| protocol | LDAP ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo |
LDAPv3
ⓘ
linked to:
Lightweight Directory Access Protocol
|
| relationship | part of the LDAPv3 core specifications set ⓘ |
| RFCNumber | 4516 ⓘ |
| specifies |
how LDAP URLs are used to access directory entries
ⓘ
semantics of LDAP URLs ⓘ syntax of LDAP URLs ⓘ |
| standardizes | use of URLs to locate LDAP directory entries ⓘ |
| status | Internet Standard ⓘ |
| title | Lightweight Directory Access Protocol (LDAP): Uniform Resource Locator ⓘ |
| updatesProtocol | Lightweight Directory Access Protocol ⓘ |
| usedFor |
locating LDAP directory entries over a network
ⓘ
specifying LDAP search operations in URLs ⓘ |
| uses |
URI syntax as defined in generic URI specifications
ⓘ
Uniform Resource Locator ⓘ
linked to:
Persistent Uniform Resource Locator
|
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 4516 Description of subject: RFC 4516 is an Internet standard that specifies the LDAP (Lightweight Directory Access Protocol) Uniform Resource Locator (URL) format used to locate and access directory entries over a network.
Referenced by (13)
Full triples — surface form annotated when it differs from this entity's canonical label.