RFC 4273
E850695
RFC 4273 is an Internet Engineering Task Force (IETF) standards document that defines the Management Information Base (MIB) for the Border Gateway Protocol version 4 (BGP-4), updating and replacing earlier BGP MIB specifications.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 4273 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T10216658 — 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 4273 Context triple: [RFC 1657, obsoletedBy, RFC 4273]
-
A.
RFC 4787
RFC 4787 is an IETF standards document that specifies behavioral requirements for network address translation (NAT) devices handling unicast UDP traffic.
-
B.
RFC 4033
RFC 4033 is an Internet standard that specifies the security extensions for the Domain Name System (DNSSEC), defining mechanisms for authenticating DNS data.
-
C.
RFC 2573
RFC 2573 is an IETF standard that specifies the SNMPv3 applications, including command generator and responder, notification originator and receiver, and proxy forwarder functionality for network management.
-
D.
RFC 4172
RFC 4172 is an IETF standards document that specifies the Internet Fibre Channel Protocol (iFCP), enabling the transport of Fibre Channel frames over IP networks.
-
E.
RFC 4303
RFC 4303 is an IETF standard that defines the Encapsulating Security Payload (ESP) protocol used to provide confidentiality, integrity, and authentication services in IPsec.
- 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 4273 Target entity description: RFC 4273 is an Internet Engineering Task Force (IETF) standards document that defines the Management Information Base (MIB) for the Border Gateway Protocol version 4 (BGP-4), updating and replacing earlier BGP MIB specifications.
-
A.
RFC 4787
RFC 4787 is an IETF standards document that specifies behavioral requirements for network address translation (NAT) devices handling unicast UDP traffic.
-
B.
RFC 4033
RFC 4033 is an Internet standard that specifies the security extensions for the Domain Name System (DNSSEC), defining mechanisms for authenticating DNS data.
-
C.
RFC 2573
RFC 2573 is an IETF standard that specifies the SNMPv3 applications, including command generator and responder, notification originator and receiver, and proxy forwarder functionality for network management.
-
D.
RFC 4172
RFC 4172 is an IETF standards document that specifies the Internet Fibre Channel Protocol (iFCP), enabling the transport of Fibre Channel frames over IP networks.
-
E.
RFC 4303
RFC 4303 is an IETF standard that defines the Encapsulating Security Payload (ESP) protocol used to provide confidentiality, integrity, and authentication services in IPsec.
- F. None of above. chosen
Statements (45)
| Predicate | Object |
|---|---|
| instanceOf |
BGP-4 MIB specification
ⓘ
IETF Request for Comments ⓘ |
| accessMethod |
SNMP
NERFINISHED
ⓘ
Simple Network Management Protocol NERFINISHED ⓘ |
| area | Operations and Management ⓘ |
| category | Standards Track ⓘ |
| defines |
MIB modules under the BGP4-MIB
ⓘ
Management Information Base for BGP-4 NERFINISHED ⓘ SNMP MIB objects for BGP-4 ⓘ |
| documentType | technical specification ⓘ |
| focusesOn |
inter-domain routing
ⓘ
management of BGP-4 routers ⓘ |
| identifier | RFC 4273 NERFINISHED ⓘ |
| intendedFor |
SNMP-based monitoring of BGP-4
ⓘ
network management ⓘ |
| language | English ⓘ |
| obsoletes |
RFC 1269
NERFINISHED
ⓘ
RFC 1657 NERFINISHED ⓘ RFC 1749 NERFINISHED ⓘ RFC 1772 NERFINISHED ⓘ RFC 1773 NERFINISHED ⓘ RFC 1774 ⓘ RFC 1863 ⓘ RFC 1965 NERFINISHED ⓘ RFC 1997 ⓘ RFC 2858 ⓘ RFC 2918 NERFINISHED ⓘ RFC 3065 NERFINISHED ⓘ RFC 3392 NERFINISHED ⓘ |
| organization | IETF IDR Working Group NERFINISHED ⓘ |
| partOf | Internet Standards process NERFINISHED ⓘ |
| protocol |
BGP-4
NERFINISHED
ⓘ
Border Gateway Protocol version 4 NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| standardizes |
objects for configuring BGP-4
ⓘ
objects for monitoring BGP-4 sessions ⓘ objects for reporting BGP-4 errors ⓘ |
| status | Proposed Standard ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| targetProtocolLayer | routing layer ⓘ |
| title | Definitions of Managed Objects for BGP-4 NERFINISHED ⓘ |
| updates | BGP-4 Management Information Base NERFINISHED ⓘ |
| uses |
SMIv2
NERFINISHED
ⓘ
Structure of Management Information Version 2 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 4273 Description of subject: RFC 4273 is an Internet Engineering Task Force (IETF) standards document that defines the Management Information Base (MIB) for the Border Gateway Protocol version 4 (BGP-4), updating and replacing earlier BGP MIB specifications.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.