NETCONF
E6187
NETCONF is a network management protocol standardized by the IETF that provides mechanisms to install, manipulate, and delete configuration data on network devices using a structured, XML-based approach.
All labels observed (6)
| Label | Occurrences |
|---|---|
| NETCONF canonical | 20 |
| Network Configuration Protocol | 3 |
| NETCONF Configuration Protocol | 2 |
| NETCONF RPCs | 1 |
| NETCONF network configuration protocol | 1 |
| Network Configuration Protocol (NETCONF) | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T73493 — 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: NETCONF Context triple: [IEEE 802.1Qcp, relatedTo, NETCONF]
-
A.
IEEE 802.1Qcp YANG data model standard
The IEEE 802.1Qcp YANG data model standard defines a structured, machine-readable configuration and management model for VLAN and bridging features in Ethernet networks, enabling interoperable network automation and control.
-
B.
IEEE 802.1Qcx YANG data model for bridge management standard
The IEEE 802.1Qcx YANG data model for bridge management standard defines a structured, machine-readable configuration and management model for Ethernet bridges to support automated and interoperable network management.
-
C.
Network Control Center
The Network Control Center is a centralized facility responsible for monitoring, managing, and coordinating the operation of a computer or communications network.
-
D.
TCP/IP
TCP/IP is the fundamental communication protocol suite that enables data transmission and networking across the internet and most modern computer networks.
-
E.
FCS
FCS is the NCAA Division I Football Championship Subdivision, the tier of top-level college football that determines its national champion through a playoff system rather than traditional bowl games.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: NETCONF Target entity description: NETCONF is a network management protocol standardized by the IETF that provides mechanisms to install, manipulate, and delete configuration data on network devices using a structured, XML-based approach.
-
A.
SNMP
SNMP (Simple Network Management Protocol) is a standard Internet protocol used to monitor, manage, and configure network devices such as routers, switches, and servers.
-
B.
Network Control Protocol
Network Control Protocol was an early host-to-host communication protocol that formed the basis of data transmission on the ARPANET before the adoption of TCP/IP.
-
C.
IEEE 802.1Qcp YANG data model standard
The IEEE 802.1Qcp YANG data model standard defines a structured, machine-readable configuration and management model for VLAN and bridging features in Ethernet networks, enabling interoperable network automation and control.
-
D.
IEEE 802.1Qcx YANG data model for bridge management standard
The IEEE 802.1Qcx YANG data model for bridge management standard defines a structured, machine-readable configuration and management model for Ethernet bridges to support automated and interoperable network management.
-
E.
NCP
NCP (Network Control Protocol) was an early host-to-host communication protocol suite that enabled data exchange between computers on the ARPANET before the adoption of TCP/IP.
- F. None of above. chosen
Statements (50)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard
ⓘ
network management protocol ⓘ |
| dataModelingLanguage | YANG ⓘ |
| definedInRFC | RFC 6241 ⓘ |
| extensionMechanism | capabilities ⓘ |
| fullName |
NETCONF
self-linksurface differs
ⓘ
surface form:
Network Configuration Protocol
|
| primaryPurpose | configuration management of network devices ⓘ |
| relatedStandard | RESTCONF ⓘ |
| standardizedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| status | Internet Standard ⓘ |
| supports |
candidate configuration datastore
ⓘ
configuration locking ⓘ deletion of configuration data ⓘ event notifications ⓘ filtering of retrieved data ⓘ installation of configuration data ⓘ manipulation of configuration data ⓘ partial configuration edits ⓘ retrieval of configuration data ⓘ retrieval of state data ⓘ running configuration datastore ⓘ startup configuration datastore ⓘ transactional configuration changes ⓘ |
| supportsCapability |
:candidate
ⓘ
:confirmed-commit ⓘ :startup ⓘ :url ⓘ :validate ⓘ :writable-running ⓘ :xpath ⓘ |
| supportsOperation |
close-session
ⓘ
commit ⓘ copy-config ⓘ delete-config ⓘ discard-changes ⓘ edit-config ⓘ get ⓘ get-config ⓘ kill-session ⓘ lock ⓘ unlock ⓘ validate ⓘ |
| transportProtocol |
BEEP
ⓘ
SOAP ⓘ SSH ⓘ TLS ⓘ |
| uses |
XML-encoded RPC messages
ⓘ
remote procedure calls ⓘ |
| usesDataEncoding | XML ⓘ |
| workingGroup | IETF NETCONF Working Group ⓘ |
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: NETCONF Description of subject: NETCONF is a network management protocol standardized by the IETF that provides mechanisms to install, manipulate, and delete configuration data on network devices using a structured, XML-based approach.
Referenced by (28)
Full triples — surface form annotated when it differs from this entity's canonical label.