RFC 3112
E826113
RFC 3112 is an Internet Engineering Task Force (IETF) standard that originally specified an authentication mechanism for the Lightweight Directory Access Protocol (LDAP).
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 3112 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T9865290 — 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 3112 Context triple: [RFC 4517, obsoletes, RFC 3112]
-
A.
RFC 3410
RFC 3410 is an informational RFC that provides an overview, framework, and goals for the Simple Network Management Protocol version 3 (SNMPv3) and its related specifications.
-
B.
RFC 3413
RFC 3413 is an Internet standard that specifies the Simple Network Management Protocol (SNMPv3) applications, including notification, proxy, and command generator/receiver functions used for network management.
-
C.
RFC 3232
RFC 3232 is an IETF document that provides the current list of assigned Internet protocol numbers and related parameters, updating and replacing earlier registries.
-
D.
RFC 1812
RFC 1812 is an Internet standards document that defines the requirements and behavior for IPv4 routers in the Internet protocol suite.
-
E.
RFC 1452
RFC 1452 is an early Internet standards document that was later superseded by RFC 1901 as part of the evolution of network protocols.
- 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 3112 Target entity description: RFC 3112 is an Internet Engineering Task Force (IETF) standard that originally specified an authentication mechanism for the Lightweight Directory Access Protocol (LDAP).
-
A.
RFC 3410
RFC 3410 is an informational RFC that provides an overview, framework, and goals for the Simple Network Management Protocol version 3 (SNMPv3) and its related specifications.
-
B.
RFC 3413
RFC 3413 is an Internet standard that specifies the Simple Network Management Protocol (SNMPv3) applications, including notification, proxy, and command generator/receiver functions used for network management.
-
C.
RFC 3232
RFC 3232 is an IETF document that provides the current list of assigned Internet protocol numbers and related parameters, updating and replacing earlier registries.
-
D.
RFC 1812
RFC 1812 is an Internet standards document that defines the requirements and behavior for IPv4 routers in the Internet protocol suite.
-
E.
RFC 1452
RFC 1452 is an early Internet standards document that was later superseded by RFC 1901 as part of the evolution of network protocols.
- F. None of above. chosen
Statements (25)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard
ⓘ
Request for Comments ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| concerns |
authentication
ⓘ
directory services ⓘ network security ⓘ |
| definesMechanismFor |
LDAP authentication
ⓘ
linked to:
LDAP
|
| documentType | Standards-track RFC ⓘ |
| focusesOn | authentication mechanism for LDAP ⓘ |
| hasNumber | 3112 ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 4513 ⓘ |
| organization | Internet Engineering Task Force ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatesToProtocol |
LDAP
ⓘ
Lightweight Directory Access Protocol ⓘ |
| series |
RFC series
ⓘ
linked to:
RFC Series Working Group
|
| standardizes | use of SASL for LDAP authentication ⓘ |
| status | Proposed Standard ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title |
LDAP Authentication Using SASL
ⓘ
linked to:
LDAP
|
| usesFramework |
SASL
ⓘ
Simple Authentication and Security Layer ⓘ
linked to:
SASL
|
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 3112 Description of subject: RFC 3112 is an Internet Engineering Task Force (IETF) standard that originally specified an authentication mechanism for the Lightweight Directory Access Protocol (LDAP).
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.