RFC 2575
E211678
RFC 2575 is an earlier IETF standard that defined the View-based Access Control Model (VACM) for SNMP before being superseded by RFC 3415.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2575 canonical | 4 |
How this entity was disambiguated
This entity first appeared as the object of triple T1896834 — 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 2575 Context triple: [RFC 3415, obsoletes, RFC 2575]
-
A.
RFC 2572
RFC 2572 is an earlier IETF specification that defined the Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) before being superseded by RFC 3412.
-
B.
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.
-
C.
RFC 2571
RFC 2571 was an earlier specification in the Simple Network Management Protocol (SNMP) framework that was later superseded and updated by RFC 3411.
-
D.
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.
-
E.
RFC 875
RFC 875 is an early Internet standard document that refines and extends the Telnet protocol specifications to improve interoperability and functionality in remote terminal connections.
- 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 2575 Target entity description: RFC 2575 is an earlier IETF standard that defined the View-based Access Control Model (VACM) for SNMP before being superseded by RFC 3415.
-
A.
RFC 2572
RFC 2572 is an earlier IETF specification that defined the Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) before being superseded by RFC 3412.
-
B.
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.
-
C.
RFC 2571
RFC 2571 was an earlier specification in the Simple Network Management Protocol (SNMP) framework that was later superseded and updated by RFC 3411.
-
D.
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.
-
E.
RFC 875
RFC 875 is an early Internet standard document that refines and extends the Telnet protocol specifications to improve interoperability and functionality in remote terminal connections.
- F. None of above. chosen
Statements (28)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard
ⓘ
Request for Comments ⓘ |
| abbreviation | VACM ⓘ |
| appliesTo |
SNMPv2
ⓘ
linked to:
SNMPv2 standards suite
SNMPv3 ⓘ |
| area | Network Management ⓘ |
| category | Standards Track ⓘ |
| defines | View-based Access Control Model ⓘ |
| definesConcept |
SNMP access policies
ⓘ
SNMP groups ⓘ SNMP views ⓘ view-based access control ⓘ |
| documentType | Internet Standard specification ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 3415 ⓘ |
| protocolContext |
SNMP
ⓘ
Simple Network Management Protocol ⓘ
linked to:
SNMP
|
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| publisher | RFC Editor ⓘ |
| relation | part of the SNMPv3 security framework ⓘ |
| series |
RFC series
ⓘ
linked to:
RFCs
|
| specifies |
access control model for SNMP
ⓘ
mechanisms for controlling access to SNMP management information ⓘ |
| standardizes | view-based access control for SNMP ⓘ |
| status | Obsoleted ⓘ |
| successorStandard | RFC 3415 ⓘ |
| title |
View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)
ⓘ
linked to:
VACM
|
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 2575 Description of subject: RFC 2575 is an earlier IETF standard that defined the View-based Access Control Model (VACM) for SNMP before being superseded by RFC 3415.
Referenced by (4)
Full triples — surface form annotated when it differs from this entity's canonical label.