RFC 7950
E39000
RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 7950 canonical | 5 |
How this entity was disambiguated
This entity first appeared as the object of triple T300493 — 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.
Target entity: RFC 7950 Context triple: [YANG modeling language, definedInRFC, RFC 7950]
-
A.
RFC 7919
RFC 7919 is an Internet standard that specifies the use of predefined Diffie–Hellman groups for secure key exchange in TLS and related protocols.
-
B.
RFC 6557
RFC 6557 is an Internet Engineering Task Force (IETF) document that defines procedures and guidelines for the maintenance and distribution of the IANA time zone database.
-
C.
RFC 9112
RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
-
D.
RFC 9113
RFC 9113 is the Internet standards document that specifies the HTTP/2 protocol, defining its framing, semantics, and operational behavior on the web.
-
E.
RFC 9114
RFC 9114 is the Internet standard that specifies HTTP/3, the version of the Hypertext Transfer Protocol that runs over the QUIC transport protocol.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: RFC 7950 Target entity description: RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
-
A.
RFC 7919
RFC 7919 is an Internet standard that specifies the use of predefined Diffie–Hellman groups for secure key exchange in TLS and related protocols.
-
B.
RFC 6557
RFC 6557 is an Internet Engineering Task Force (IETF) document that defines procedures and guidelines for the maintenance and distribution of the IANA time zone database.
-
C.
RFC 9112
RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
-
D.
RFC 9113
RFC 9113 is the Internet standards document that specifies the HTTP/2 protocol, defining its framing, semantics, and operational behavior on the web.
-
E.
RFC 9114
RFC 9114 is the Internet standard that specifies HTTP/3, the version of the Hypertext Transfer Protocol that runs over the QUIC transport protocol.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard
ⓘ
Request for Comments ⓘ YANG specification ⓘ |
| area | Operations and Management ⓘ |
| category | Standards Track ⓘ |
| defines |
YANG modeling language
ⓘ
surface form:
YANG 1.1
|
| definesConcept |
YANG RPCs
ⓘ
YANG XPath usage ⓘ YANG actions ⓘ YANG built-in types ⓘ YANG conformance ⓘ YANG constraints ⓘ YANG containers ⓘ YANG data types ⓘ YANG deviations ⓘ YANG extensions ⓘ YANG features ⓘ YANG groupings ⓘ YANG identities ⓘ YANG leaf-lists ⓘ YANG leafs ⓘ YANG lists ⓘ YANG module versioning model (1.1) ⓘ YANG modules ⓘ YANG namespaces ⓘ YANG notifications ⓘ YANG statements ⓘ |
| language | English ⓘ |
| obsoletes | RFC 6020 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedStandard |
RFC 6241
ⓘ
RFC 8040 ⓘ |
| relatedTo |
data modeling
ⓘ
network configuration ⓘ network state monitoring ⓘ |
| specifies |
YANG
ⓘ
surface form:
YANG 1.1 data modeling language
|
| standardizes |
YANG
ⓘ
surface form:
YANG 1.1
|
| status | Internet Standard ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title |
YANG modeling language
ⓘ
surface form:
The YANG 1.1 Data Modeling Language
|
| updates |
YANG modeling language
ⓘ
surface form:
YANG 1.0
|
| usedFor |
modeling configuration data
ⓘ
modeling network management data ⓘ modeling state data ⓘ |
| usedIn | network management protocols ⓘ |
| usedWith |
NETCONF
ⓘ
RESTCONF ⓘ |
| workingGroup | NETMOD ⓘ |
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.
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.
Subject: RFC 7950 Description of subject: RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
Referenced by (5)
Full triples — surface form annotated when it differs from this entity's canonical label.