RFC 3377
E845097
RFC 3377 is an Internet Engineering Task Force (IETF) document that previously specified Lightweight Directory Access Protocol (LDAP) version 3 technical details before being superseded by later standards.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 3377 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T10158211 — 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 3377 Context triple: [RFC 4510, obsoletes, RFC 3377]
-
A.
RFC 3207
RFC 3207 is the Internet standard that specifies the STARTTLS extension for upgrading plain text email connections to use TLS encryption in SMTP.
-
B.
RFC 3977
RFC 3977 is the Internet standard that defines the Network News Transfer Protocol (NNTP), updating and replacing the earlier specification in RFC 977.
-
C.
RFC 3727
RFC 3727 is an Internet Engineering Task Force (IETF) document that defined earlier specifications for LDAP-related schema or matching rules, later superseded by RFC 4517.
-
D.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
-
E.
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.
- 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 3377 Target entity description: RFC 3377 is an Internet Engineering Task Force (IETF) document that previously specified Lightweight Directory Access Protocol (LDAP) version 3 technical details before being superseded by later standards.
-
A.
RFC 3207
RFC 3207 is the Internet standard that specifies the STARTTLS extension for upgrading plain text email connections to use TLS encryption in SMTP.
-
B.
RFC 3977
RFC 3977 is the Internet standard that defines the Network News Transfer Protocol (NNTP), updating and replacing the earlier specification in RFC 977.
-
C.
RFC 3727
RFC 3727 is an Internet Engineering Task Force (IETF) document that defined earlier specifications for LDAP-related schema or matching rules, later superseded by RFC 4517.
-
D.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
-
E.
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.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard-track document
ⓘ
Request for Comments ⓘ |
| abbreviation | RFC 3377 NERFINISHED ⓘ |
| appliesTo | Internet NERFINISHED ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines | LDAPv3 technical specification ⓘ |
| definesProtocol | Lightweight Directory Access Protocol version 3 NERFINISHED ⓘ |
| definesVersion | LDAP version 3 ⓘ |
| format | Text ⓘ |
| isAbout |
LDAPv3
NERFINISHED
ⓘ
Lightweight Directory Access Protocol NERFINISHED ⓘ |
| language | English ⓘ |
| obsoletedBy |
RFC 4510
NERFINISHED
ⓘ
RFC 4511 NERFINISHED ⓘ RFC 4512 NERFINISHED ⓘ RFC 4513 NERFINISHED ⓘ RFC 4514 NERFINISHED ⓘ RFC 4515 NERFINISHED ⓘ RFC 4516 NERFINISHED ⓘ RFC 4517 NERFINISHED ⓘ RFC 4518 NERFINISHED ⓘ RFC 4519 NERFINISHED ⓘ |
| obsoletes |
RFC 2251
NERFINISHED
ⓘ
RFC 2252 ⓘ RFC 2253 NERFINISHED ⓘ RFC 2254 ⓘ RFC 2255 ⓘ RFC 2256 ⓘ RFC 2829 NERFINISHED ⓘ RFC 2830 NERFINISHED ⓘ |
| organization | Internet Society NERFINISHED ⓘ |
| protocolFamily | Directory access protocol ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedStandard | X.500 directory services NERFINISHED ⓘ |
| series | Request for Comments NERFINISHED ⓘ |
| shortName | LDAPv3 Technical Specification NERFINISHED ⓘ |
| standardsBody | Internet Engineering Task Force NERFINISHED ⓘ |
| status | Obsoleted ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| supersededBy | LDAPv3 RFC 4510 series NERFINISHED ⓘ |
| title | Lightweight Directory Access Protocol (v3): Technical Specification NERFINISHED ⓘ |
| topic |
Authentication
ⓘ
Directory services ⓘ Network protocols ⓘ |
| updatesSpecificationOf | Lightweight Directory Access Protocol NERFINISHED ⓘ |
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 3377 Description of subject: RFC 3377 is an Internet Engineering Task Force (IETF) document that previously specified Lightweight Directory Access Protocol (LDAP) version 3 technical details before being superseded by later standards.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.