Email us :

NETCONF details


NETCONF is an IETF defined configuration management protocol to “install, manipulate, and delete the configuration of network devices”. NETCONF operations are conveyed in a Remote Procedure Call (RPC) layer using XML encoding to provide a basic set of operations to edit and query configurations on a network device.

  • next generation Internet services configuration and management
  • transactions allow all or nothing deployment of services
  • configuration and operational data are identified separately
  • has sets of configuration rather than sequences making backup and restore easier and more robust
  • multiple configurations (running, startup, candidate)
  • filtering allowing retrieval of only the data requested
  • uses standard security and encryption mechanisms
  • can augment or replace legacy CLI & SNMP
  • decreases:
    • downtime
    • service degradation
    • expensive failure analysis

YumaWorks’ YumaPro SDK implements the NETCONF standard fully, including optional requirements.

Key features of YumaPro SDK’s NETCONF implementation:

  • high performance
  • keeps current with evolving standard’s features
  • configuration can be tested and validated
  • uses standard security and access control models
  • event notifications

Key IETF NETCONF RFCs and YumaPro SDK support:

Expand All Collapse All

NETCONF Standards
RFC 4741 (version 1.0)

The first version of the NETCONF protocol is fully supported. View the RFC.
RFC 4742 (SSH transport v1)

The first version of the NETCONF over SSH transport is fully supported. View the RFC.
RFC 5277 (notifications)

NETCONF Notifications are fully supported. View the RFC.
RFC 5717 (partial locking)

Partial configuration sub-tree locking is fully supported to allow concurrent editing transactions on different parts of the configuration. View the RFC.
RFC 6022 (monitoring)

The standard NETCONF monitoring data is fully supported. View the RFC.
RFC 6241 (base:1.1)

The second version of the NETCONF protocol is fully supported. View the RFC.
RFC 6242 (SSH transport v2)

The second version of the NETCONF over SSH transport is fully supported. View the RFC.
RFC 6243 (defaults filtering)

The with-defaults capability to retrieve default leaf information is fully supported. View the RFC here.
RFC 6470 (notification events)

The NETCONF base notification events that allow clients to know when the server configuration or capabilities have changed. View the RFC.
RFC 6536 (access control)

The NETCONF Access Control Model (NACM) provides role-based access control for all server database content, operations, and notifications. View the RFC.
RFC 7230 (HTTP/1.1 Message Syntax and Routing)

Provides an overview of HTTP architecture and its associated terminology, defines the “http” and “https” Uniform Resource Identifier (URI) schemes, defines the HTTP/1.1 message syntax and parsing requirements, and describes related security concerns for implementations. View the RFC.
RFC 7231 (HTTP/1.1 Semantics and Content)

Defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation. View the RFC.
RFC 7232 (HTTP/1.1 Conditional Requests)

Defines HTTP/1.1 conditional requests, including metadata header fields for indicating state changes, request header fields for making preconditions on such state, and rules for constructing the responses to a conditional request when one or more preconditions evaluate to false. View the RFC.

Describes an HTTP-based protocol that provides a programmatic interface for accessing data defined in YANG, using the datastore concepts defined in the Network Configuration Protocol (NETCONF). View the RFC.
RFC 8071 (Call Home)

NETCONF Call Home and RESTCONF Call Home, which enable a NETCONF or RESTCONF server to initiate a secure connection to a NETCONF or RESTCONF client, respectively. View the RFC.