RFC 1771
E708267
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.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1771 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T7928549 — 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 1771 Context triple: [RFC 4271, obsoletes, RFC 1771]
-
A.
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.
-
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 1670
RFC 1670 is an early Internet standards document related to network protocols that was later superseded by RFC 1901.
-
E.
RFC 1497
RFC 1497 is an early Internet standards document that defined vendor-specific extensions for the BOOTP protocol, laying groundwork later incorporated into DHCP.
- 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 1771 Target entity description: 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.
-
A.
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.
-
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 1670
RFC 1670 is an early Internet standards document related to network protocols that was later superseded by RFC 1901.
-
E.
RFC 1497
RFC 1497 is an early Internet standards document that defined vendor-specific extensions for the BOOTP protocol, laying groundwork later incorporated into DHCP.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard specification
ⓘ
Request for Comments ⓘ |
| abbreviation | BGP-4 NERFINISHED ⓘ |
| applicationDomain |
Internet routing
ⓘ
inter-domain routing ⓘ |
| area | Routing ⓘ |
| category | Standards Track ⓘ |
| defines |
BGP-4 KEEPALIVE message
ⓘ
BGP-4 NOTIFICATION message ⓘ BGP-4 OPEN message ⓘ BGP-4 TCP usage ⓘ BGP-4 UPDATE message NERFINISHED ⓘ BGP-4 error handling ⓘ BGP-4 finite state machine ⓘ BGP-4 message formats ⓘ BGP-4 path attributes ⓘ BGP-4 route selection rules ⓘ BGP-4 session establishment ⓘ |
| definesConcept |
AS_PATH attribute
ⓘ
BGP path vector routing ⓘ BGP peer ⓘ BGP session ⓘ BGP speaker ⓘ LOCAL_PREF attribute ⓘ MULTI_EXIT_DISC attribute ⓘ NEXT_HOP attribute ⓘ ORIGIN attribute ⓘ autonomous system ⓘ route aggregation ⓘ route flap damping ⓘ |
| focusesOn | routing between autonomous systems ⓘ |
| intendedUse |
Internet backbone routing
ⓘ
inter-AS routing ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 4271 NERFINISHED ⓘ |
| protocolSpecified | Border Gateway Protocol version 4 NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publishedBySeries | Request for Comments series NERFINISHED ⓘ |
| standardizes |
exchange of network reachability information
ⓘ
policy-based routing between autonomous systems ⓘ |
| status | Obsoleted ⓘ |
| successorSpecification | RFC 4271 NERFINISHED ⓘ |
| tcpPort | 179 ⓘ |
| title | A Border Gateway Protocol 4 (BGP-4) NERFINISHED ⓘ |
| transportProtocol | TCP NERFINISHED ⓘ |
| updatesProtocol | Border Gateway 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 1771 Description of subject: 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.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.