RFC 1716
E1047317
RFC 1716 is an early Internet standards document that provided guidelines and requirements for IP routers before being superseded by RFC 1812.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1716 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T13551722 — 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 1716 Context triple: [RFC 1812, obsoletes, RFC 1716]
-
A.
RFC 1771
RFC 1771 is an early specification of the Border Gateway Protocol (BGP-4) used for inter-domain routing on the Internet, later superseded by RFC 4271.
-
B.
RFC 1657
RFC 1657 is an early Internet standards document that defined SNMPv2 Management Information Base (MIB) extensions for managing BGP-4 routing protocol implementations.
-
C.
RFC 1667
RFC 1667 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
D.
RFC 1661
RFC 1661 is the original specification of the Point-to-Point Protocol (PPP), defining a standard method for transporting multi-protocol datagrams over point-to-point links.
-
E.
RFC 1652
RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
- 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 1716 Target entity description: RFC 1716 is an early Internet standards document that provided guidelines and requirements for IP routers before being superseded by RFC 1812.
-
A.
RFC 1771
RFC 1771 is an early specification of the Border Gateway Protocol (BGP-4) used for inter-domain routing on the Internet, later superseded by RFC 4271.
-
B.
RFC 1657
RFC 1657 is an early Internet standards document that defined SNMPv2 Management Information Base (MIB) extensions for managing BGP-4 routing protocol implementations.
-
C.
RFC 1667
RFC 1667 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
D.
RFC 1661
RFC 1661 is the original specification of the Point-to-Point Protocol (PPP), defining a standard method for transporting multi-protocol datagrams over point-to-point links.
-
E.
RFC 1652
RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
Request for Comments ⓘ |
| area | Internet NERFINISHED ⓘ |
| author |
A. Fredette
NERFINISHED
ⓘ
C. Partridge NERFINISHED ⓘ E. Brunner NERFINISHED ⓘ Fred Baker NERFINISHED ⓘ H. Braun NERFINISHED ⓘ J. Davin NERFINISHED ⓘ J. Moy NERFINISHED ⓘ J. Nagle NERFINISHED ⓘ J. Wroclawski NERFINISHED ⓘ M. Steenstrup NERFINISHED ⓘ P. Almquist NERFINISHED ⓘ R. Callon NERFINISHED ⓘ Y. Rekhter NERFINISHED ⓘ |
| category | Informational ⓘ |
| countryOfOrigin |
United States of America
ⓘ
surface form:
United States
|
| defines |
guidelines for Internet Protocol router behavior
ⓘ
requirements for IP routers ⓘ |
| describes |
requirements for forwarding IP datagrams
ⓘ
router management considerations ⓘ routing protocol interactions ⓘ |
| focusesOn |
IP routing
ⓘ
Internet architecture ⓘ router requirements ⓘ |
| hasURL | https://www.rfc-editor.org/rfc/rfc1716 ⓘ |
| intendedFor |
network operators
ⓘ
router designers ⓘ router implementers ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 1812 NERFINISHED ⓘ |
| obsoletes | RFC 1009 NERFINISHED ⓘ |
| organizationContext | Internet Architecture Board NERFINISHED ⓘ |
| predecessor | RFC 1009 NERFINISHED ⓘ |
| protocolFamily | TCP/IP NERFINISHED ⓘ |
| publicationMonth | November ⓘ |
| publicationYear | 1994 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ Internet Society NERFINISHED ⓘ |
| RFCNumber | 1716 ⓘ |
| series | RFC series NERFINISHED ⓘ |
| standardsTrack | no ⓘ |
| status | Obsoleted ⓘ |
| successor | RFC 1812 NERFINISHED ⓘ |
| title | Towards Requirements for IP Routers NERFINISHED ⓘ |
| updates | RFC 1009 ⓘ |
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 1716 Description of subject: RFC 1716 is an early Internet standards document that provided guidelines and requirements for IP routers before being superseded by RFC 1812.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.