RFC 1903
E729708
RFC 1903 is an older Internet standards document related to SNMP that was later superseded by RFC 2572.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1903 canonical | 4 |
How this entity was disambiguated
This entity first appeared as the object of triple T8375599 — 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 1903 Context triple: [RFC 2572, obsoletes, RFC 1903]
-
A.
RFC 1907
RFC 1907 is an earlier Internet standard that defined the Management Information Base (MIB) for SNMPv2, later superseded by RFC 3418.
-
B.
RFC 1901
RFC 1901 is an IETF standards document that specifies the community-based version of the Simple Network Management Protocol, commonly known as SNMPv2c.
-
C.
RFC 1305
RFC 1305 is an Internet standards document that specifies version 3 of the Network Time Protocol (NTP) for synchronizing computer clocks over packet-switched, variable-latency data networks.
-
D.
RFC 3412
RFC 3412 is an Internet standard that specifies the message processing and dispatching procedures for the Simple Network Management Protocol (SNMP) within the SNMPv3 framework.
-
E.
RFC 2580
RFC 2580 is an Internet Engineering Task Force (IETF) standards document that defines conformance statements for the Structure of Management Information Version 2 (SMIv2) used in network management protocols like SNMP.
- 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 1903 Target entity description: RFC 1903 is an older Internet standards document related to SNMP that was later superseded by RFC 2572.
-
A.
RFC 1907
RFC 1907 is an earlier Internet standard that defined the Management Information Base (MIB) for SNMPv2, later superseded by RFC 3418.
-
B.
RFC 1901
RFC 1901 is an IETF standards document that specifies the community-based version of the Simple Network Management Protocol, commonly known as SNMPv2c.
-
C.
RFC 1305
RFC 1305 is an Internet standards document that specifies version 3 of the Network Time Protocol (NTP) for synchronizing computer clocks over packet-switched, variable-latency data networks.
-
D.
RFC 3412
RFC 3412 is an Internet standard that specifies the message processing and dispatching procedures for the Simple Network Management Protocol (SNMP) within the SNMPv3 framework.
-
E.
RFC 2580
RFC 2580 is an Internet Engineering Task Force (IETF) standards document that defines conformance statements for the Structure of Management Information Version 2 (SMIv2) used in network management protocols like SNMP.
- F. None of above. chosen
Statements (25)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
Request for Comments ⓘ |
| area | Network Management ⓘ |
| category | Standards Track ⓘ |
| defines | textual conventions for SNMPv2 ⓘ |
| documentType | Standards Track RFC ⓘ |
| focusesOn |
SNMPv2 MIB textual conventions
ⓘ
management information base design ⓘ |
| intendedAudience |
MIB designers
ⓘ
network management application developers ⓘ network protocol designers ⓘ |
| isPartOfFamily | SNMP-related RFCs ⓘ |
| language | English ⓘ |
| networkLayer | application layer ⓘ |
| obsoletedBy | RFC 2578 NERFINISHED ⓘ |
| partOf | SNMPv2 core specifications NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedToProtocol |
SNMPv2
NERFINISHED
ⓘ
Simple Network Management Protocol version 2 NERFINISHED ⓘ |
| series | STD 58 NERFINISHED ⓘ |
| standardizes | data representation conventions for SNMPv2 MIB modules ⓘ |
| status | Obsoleted ⓘ |
| title | Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2) NERFINISHED ⓘ |
| updates | SNMPv2 management information definitions 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 1903 Description of subject: RFC 1903 is an older Internet standards document related to SNMP that was later superseded by RFC 2572.
Referenced by (4)
Full triples — surface form annotated when it differs from this entity's canonical label.