RFC 1908
E275764
RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1908 canonical | 9 |
How this entity was disambiguated
This entity first appeared as the object of triple T1814063 — 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 1908 Context triple: [RFC 3410, obsoletes, RFC 1908]
-
A.
RFC 1668
RFC 1668 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specifications evolved.
-
B.
RFC 1904
RFC 1904 is an Internet standards document that originally defined the textual conventions for SNMPv2 before later being superseded by RFC 3410.
-
C.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
D.
RFC 1906
RFC 1906 is an Internet standard that specifies the transport mappings for SNMPv2, detailing how SNMP messages are carried over various network protocols.
-
E.
RFC 1659
RFC 1659 is an early Internet standards document that specified the Simple Network Management Protocol (SNMP) version 2 over OSI transport mappings 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 1908 Target entity description: RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
-
A.
RFC 1668
RFC 1668 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specifications evolved.
-
B.
RFC 1904
RFC 1904 is an Internet standards document that originally defined the textual conventions for SNMPv2 before later being superseded by RFC 3410.
-
C.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
D.
RFC 1906
RFC 1906 is an Internet standard that specifies the transport mappings for SNMPv2, detailing how SNMP messages are carried over various network protocols.
-
E.
RFC 1659
RFC 1659 is an early Internet standards document that specified the Simple Network Management Protocol (SNMP) version 2 over OSI transport mappings before being superseded by later revisions.
- F. None of above. chosen
Statements (42)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
Request for Comments ⓘ |
| area | Network Management ⓘ |
| BCPNumber | BCP 12 ⓘ |
| category | Best Current Practice ⓘ |
| defines | coexistence rules for SNMPv1 and SNMPv2 ⓘ |
| focusesOn |
Internet-standard Network Management Framework version 1
ⓘ
linked to:
An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks
Internet-standard Network Management Framework version 2 ⓘ
linked to:
SNMPv2 standards suite
|
| format | Text ⓘ |
| hasSuccessor | RFC 3410 ⓘ |
| intendedStatus | Best Current Practice ⓘ |
| isPartOf | Internet Standard Network Management Framework ⓘ |
| language | English ⓘ |
| obsoletedBy |
BCP 57
ⓘ
RFC 3410 ⓘ |
| publicationMonth | January ⓘ |
| publicationYear | 1996 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo |
SNMPv1
ⓘ
SNMPv2 ⓘ
linked to:
SNMPv2 standards suite
|
| RFCNumber | 1908 ⓘ |
| standardizes | coexistence between SNMP protocol versions ⓘ |
| status | Obsoleted ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title | Coexistence between Version 1 and Version 2 of the Internet-standard Network Management Framework ⓘ |
| updates |
RFC 1157
ⓘ
RFC 1441 ⓘ RFC 1442 ⓘ RFC 1443 ⓘ RFC 1444 ⓘ RFC 1450 ⓘ RFC 1451 ⓘ RFC 1452 ⓘ RFC 1453 ⓘ RFC 1901 ⓘ RFC 1902 ⓘ RFC 1903 ⓘ RFC 1904 ⓘ RFC 1905 ⓘ RFC 1906 ⓘ RFC 1907 ⓘ |
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 1908 Description of subject: RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
Referenced by (9)
Full triples — surface form annotated when it differs from this entity's canonical label.