RFC 3584
E837945
RFC 3584 is an IETF standard that specifies coexistence and transition mechanisms between SNMPv1, SNMPv2c, and SNMPv3, including definitions such as the SNMP-COMMUNITY-MIB.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 3584 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T10035269 — 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 3584 Context triple: [SNMP-COMMUNITY-MIB, definedIn, RFC 3584]
-
A.
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.
-
B.
RFC 3445
RFC 3445 is an earlier Internet Engineering Task Force (IETF) specification related to DNS security that was later superseded by RFC 4033.
-
C.
RFC 4954
RFC 4954 is an Internet standard that specifies the SMTP Authentication (SMTP AUTH) extension, enabling secure client authentication when sending email.
-
D.
RFC 3652
RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
-
E.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
- 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 3584 Target entity description: RFC 3584 is an IETF standard that specifies coexistence and transition mechanisms between SNMPv1, SNMPv2c, and SNMPv3, including definitions such as the SNMP-COMMUNITY-MIB.
-
A.
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.
-
B.
RFC 3445
RFC 3445 is an earlier Internet Engineering Task Force (IETF) specification related to DNS security that was later superseded by RFC 4033.
-
C.
RFC 4954
RFC 4954 is an Internet standard that specifies the SMTP Authentication (SMTP AUTH) extension, enabling secure client authentication when sending email.
-
D.
RFC 3652
RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
-
E.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard
ⓘ
Request for Comments ⓘ |
| abbreviation | RFC3584 NERFINISHED ⓘ |
| area | Network Management NERFINISHED ⓘ |
| category | Standards Track ⓘ |
| defines |
SNMP-COMMUNITY-MIB
NERFINISHED
ⓘ
coexistence mechanisms between SNMPv1, SNMPv2c, and SNMPv3 ⓘ mechanisms for coexistence of community-based and user-based security models ⓘ mechanisms for mapping SNMPv1 and SNMPv2c community-based access to SNMPv3 ⓘ objects for configuring community strings in SNMP-COMMUNITY-MIB ⓘ objects for configuring notification targets across SNMP versions ⓘ objects for configuring proxy relationships between SNMP entities ⓘ objects for mapping community strings to SNMPv3 securityLevels ⓘ objects for mapping community strings to SNMPv3 securityModels ⓘ objects for mapping community strings to SNMPv3 securityNames ⓘ objects for mapping community strings to contextEngineIDs and contextNames ⓘ objects for mapping community strings to transport endpoints ⓘ procedures for command generators and responders across SNMP versions ⓘ procedures for notification originators between SNMP versions ⓘ procedures for proxy forwarders between SNMP versions ⓘ transition mechanisms between SNMPv1, SNMPv2c, and SNMPv3 ⓘ |
| definesMIB | SNMP-COMMUNITY-MIB NERFINISHED ⓘ |
| focusesOn |
coexistence of Internet-standard Network Management Framework versions
ⓘ
transition from community-based SNMP to SNMPv3 ⓘ |
| intendedAudience |
network management protocol implementers
ⓘ
network operators using SNMP ⓘ |
| language | English ⓘ |
| obsoletes | RFC 2576 NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedProtocol |
SNMPv1
NERFINISHED
ⓘ
SNMPv2c NERFINISHED ⓘ SNMPv3 NERFINISHED ⓘ |
| specifies |
behavior of SNMP engines acting as proxies between versions
ⓘ
behavior of SNMP engines handling notifications across versions ⓘ behavior of SNMP engines handling requests and responses across versions ⓘ |
| standardizes |
community-based to SNMPv3 context mapping
ⓘ
community-based to SNMPv3 securityName mapping ⓘ community-based to SNMPv3 transport mapping ⓘ |
| status | Internet Standard framework coexistence specification ⓘ |
| title | Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework ⓘ |
| updates |
SNMPv1
NERFINISHED
ⓘ
SNMPv2c NERFINISHED ⓘ SNMPv3 NERFINISHED ⓘ |
| usesSecurityModel |
SNMPv1 community-based security
ⓘ
SNMPv2c community-based security ⓘ SNMPv3 User-based Security Model 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 3584 Description of subject: RFC 3584 is an IETF standard that specifies coexistence and transition mechanisms between SNMPv1, SNMPv2c, and SNMPv3, including definitions such as the SNMP-COMMUNITY-MIB.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.