RFC 1657
E242461
RFC 1657 is an early Internet standards document that defined SNMPv2 Management Information Base (MIB) extensions for managing BGP-4 routing protocol implementations.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1657 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1777487 — 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 1657 Context triple: [RFC 1901, obsoletes, RFC 1657]
-
A.
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.
-
B.
RFC 1655
RFC 1655 is an early Internet standards document that specified the original Simple Network Management Protocol (SNMP) version 2 framework before being superseded by later revisions.
-
C.
RFC 1457
RFC 1457 is an early Internet standards document that specified guidelines and mechanisms related to network management within the SNMP framework before being superseded by later updates.
-
D.
RFC 1651
RFC 1651 is an early Internet standards document that defined extensions to the Simple Mail Transfer Protocol (SMTP) to support enhanced email functionality.
-
E.
RFC 1725
RFC 1725 was an early Internet standard that originally defined the Post Office Protocol version 3 (POP3) for retrieving email from a mail server.
- 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 1657 Target entity description: RFC 1657 is an early Internet standards document that defined SNMPv2 Management Information Base (MIB) extensions for managing BGP-4 routing protocol implementations.
-
A.
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.
-
B.
RFC 1655
RFC 1655 is an early Internet standards document that specified the original Simple Network Management Protocol (SNMP) version 2 framework before being superseded by later revisions.
-
C.
RFC 1457
RFC 1457 is an early Internet standards document that specified guidelines and mechanisms related to network management within the SNMP framework before being superseded by later updates.
-
D.
RFC 1651
RFC 1651 is an early Internet standards document that defined extensions to the Simple Mail Transfer Protocol (SMTP) to support enhanced email functionality.
-
E.
RFC 1725
RFC 1725 was an early Internet standard that originally defined the Post Office Protocol version 3 (POP3) for retrieving email from a mail server.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
Request for Comments ⓘ |
| appliesTo |
Internet backbone routers
ⓘ
autonomous system border routers ⓘ |
| area | Routing Area ⓘ |
| category | Standards Track ⓘ |
| defines |
Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)
ⓘ
surface form:
Management Information Base (MIB) extensions for BGP-4
SNMPv2 MIB objects for BGP-4 ⓘ managed objects for the Border Gateway Protocol version 4 ⓘ objects for BGP-4 path attributes ⓘ objects for BGP-4 peer state ⓘ objects for BGP-4 routing information ⓘ objects for BGP-4 system configuration ⓘ |
| definesMIBFor | BGP-4 routing protocol implementations ⓘ |
| documentType | Standards Track RFC ⓘ |
| focusesOn |
control of BGP-4 sessions
ⓘ
management of BGP-4 routing information ⓘ monitoring of BGP-4 peers ⓘ |
| intendedFor |
network management systems
ⓘ
operators of BGP-4 routers ⓘ |
| language | English ⓘ |
| obsoletedBy |
RFC 4273
ⓘ
RFC 4274 ⓘ RFC 4277 ⓘ |
| obsoletes | RFC 1269 ⓘ |
| protocol |
BGP
ⓘ
surface form:
BGP-4
BGP ⓘ
surface form:
Border Gateway Protocol version 4
|
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
SNMPv2 standards suite
ⓘ
surface form:
SNMPv2
SNMPv2 standards suite ⓘ
surface form:
Simple Network Management Protocol version 2
|
| RFCNumber | 1657 ⓘ |
| series |
RFCs
ⓘ
surface form:
Request for Comments
|
| shortTitle | BGP-4 MIB using SMIv2 ⓘ |
| standardsBody | Internet Engineering Task Force ⓘ |
| status | Proposed Standard ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title |
Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)
ⓘ
surface form:
Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2
|
| topic |
BGP
ⓘ
Internet routing ⓘ Management Information Base (MIB) for the Simple Network Management Protocol (SNMP) ⓘ
surface form:
Management Information Base
Management Information Base (MIB) for the Simple Network Management Protocol (SNMP) ⓘ
surface form:
SNMP MIB
network management ⓘ |
| updates | RFC 1519 ⓘ |
| uses |
SMIv2
ⓘ
Structure of Management Information ⓘ
surface form:
Structure of Management Information Version 2
|
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 1657 Description of subject: RFC 1657 is an early Internet standards document that defined SNMPv2 Management Information Base (MIB) extensions for managing BGP-4 routing protocol implementations.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.