RFC 4274
E851099
RFC 4274 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces earlier specifications related to SNMP-based management of BGP-4.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 4274 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T10216659 — 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 4274 Context triple: [RFC 1657, obsoletedBy, RFC 4274]
-
A.
RFC 4954
RFC 4954 is an Internet standard that specifies the SMTP Authentication (SMTP AUTH) extension, enabling secure client authentication when sending email.
-
B.
RFC 3414
RFC 3414 is an Internet standard that specifies the User-based Security Model (USM) for securing SNMPv3 communications, including authentication and privacy mechanisms.
-
C.
RFC 3947
RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
-
D.
RFC 4741
RFC 4741 is the original IETF specification that defines the NETCONF network configuration protocol for managing network devices.
-
E.
RFC 2467
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
- 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 4274 Target entity description: RFC 4274 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces earlier specifications related to SNMP-based management of BGP-4.
-
A.
RFC 4954
RFC 4954 is an Internet standard that specifies the SMTP Authentication (SMTP AUTH) extension, enabling secure client authentication when sending email.
-
B.
RFC 3414
RFC 3414 is an Internet standard that specifies the User-based Security Model (USM) for securing SNMPv3 communications, including authentication and privacy mechanisms.
-
C.
RFC 3947
RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
-
D.
RFC 4741
RFC 4741 is the original IETF specification that defines the NETCONF network configuration protocol for managing network devices.
-
E.
RFC 2467
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
- F. None of above. chosen
Statements (31)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
standards-track document ⓘ |
| appliesTo |
BGP-4 speaking systems
ⓘ
Internet routers ⓘ |
| area | Operations and Management ⓘ |
| category | Standards Track ⓘ |
| defines |
BGP-4 MIB module
NERFINISHED
ⓘ
Management Information Base for BGP-4 NERFINISHED ⓘ |
| definesFor |
Internet routing infrastructure
ⓘ
network management ⓘ |
| documentType | Standards-track RFC ⓘ |
| focusesOn |
controlling BGP-4
ⓘ
monitoring BGP-4 ⓘ |
| intendedFor |
network management systems
ⓘ
network operators ⓘ router vendors ⓘ |
| language | English ⓘ |
| obsoletes |
BGP-4 MIB (RFC 1657)
NERFINISHED
ⓘ
RFC 1657 NERFINISHED ⓘ |
| partOf | Internet Standards process NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedToProtocol |
BGP-4
NERFINISHED
ⓘ
Border Gateway Protocol version 4 NERFINISHED ⓘ |
| standardizes | objects for managing BGP-4 via SNMP ⓘ |
| standardsBody | IETF NERFINISHED ⓘ |
| status | Proposed Standard ⓘ |
| title | BGP-4 MIB NERFINISHED ⓘ |
| updatesSpecificationFor | SNMP-based management of BGP-4 ⓘ |
| uses |
SNMP
NERFINISHED
ⓘ
Simple Network Management 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 4274 Description of subject: RFC 4274 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces earlier specifications related to SNMP-based management of BGP-4.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.