RFC 6241: Network Configuration Protocol (NETCONF)

The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network…

Read RFC 6241 on the RFC Editor

Outgoing relationships (14 related RFCs)

Obsoletes, Informative reference — RFC 4741: NETCONF Configuration Protocol
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 3986: Uniform Resource Identifier (URI): Generic Syntax
Normative reference — RFC 3629: UTF-8, a transformation format of ISO 10646
Normative reference — RFC 3688: The IETF XML Registry
Normative reference — RFC 6020: YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)
Normative reference — RFC 6242: Using the NETCONF Protocol over Secure Shell (SSH)
Normative reference — RFC 3553: An IETF URN Sub-namespace for Registered Protocol Parameters
Normative reference — RFC 6021: Common YANG Data Types
Normative reference — RFC 5717: Partial Lock Remote Procedure Call (RPC) for NETCONF
Informative reference — RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2
Informative reference — RFC 2865: Remote Authentication Dial In User Service (RADIUS)
Informative reference — RFC 4251: The Secure Shell (SSH) Protocol Architecture
Informative reference — RFC 3470: Guidelines for the Use of Extensible Markup Language (XML) within IETF Protocols

Incoming relationships (130 related RFCs)

Showing 50 of 130 related RFCs.

Updated by — RFC 8526: NETCONF Extensions to Support the Network Management Datastore Architecture
Updated by, Normatively referenced by — RFC 7803: Changing the Registration Policy for the NETCONF Capability URNs Registry
Normatively referenced by — RFC 7950: The YANG 1.1 Data Modeling Language
Normatively referenced by — RFC 8341: Network Configuration Access Control Model
Normatively referenced by — RFC 6242: Using the NETCONF Protocol over Secure Shell (SSH)
Normatively referenced by — RFC 8342: Network Management Datastore Architecture (NMDA)
Normatively referenced by — RFC 8349: A YANG Data Model for Routing Management (NMDA Version)
Normatively referenced by — RFC 7951: JSON Encoding of Data Modeled with YANG
Normatively referenced by — RFC 8177: YANG Data Model for Key Chains
Normatively referenced by — RFC 8345: A YANG Data Model for Network Topologies
Normatively referenced by — RFC 8299: YANG Data Model for L3VPN Service Delivery
Normatively referenced by — RFC 7317: A YANG Data Model for System Management
Normatively referenced by — RFC 9182: A YANG Network Data Model for Layer 3 VPNs
Normatively referenced by — RFC 9640: YANG Data Types and Groupings for Cryptography
Normatively referenced by — RFC 9645: YANG Groupings for TLS Clients and TLS Servers
Normatively referenced by — RFC 8783: Distributed Denial-of-Service Open Threat Signaling (DOTS) Data Channel Specification
Normatively referenced by — RFC 8969: A Framework for Automating Service and Network Management with YANG
Normatively referenced by — RFC 7589: Using the NETCONF Protocol over Transport Layer Security (TLS) with Mutual X.509 Authentication
Normatively referenced by — RFC 9291: A YANG Network Data Model for Layer 2 VPNs
Normatively referenced by — RFC 9641: A YANG Data Model for a Truststore
Normatively referenced by — RFC 9642: A YANG Data Model for a Keystore
Normatively referenced by — RFC 8344: A YANG Data Model for IP Management
Normatively referenced by — RFC 8795: YANG Data Model for Traffic Engineering (TE) Topologies
Normatively referenced by — RFC 8960: A YANG Data Model for MPLS Base
Normatively referenced by — RFC 8995: Bootstrapping Remote Secure Key Infrastructure (BRSKI)
Normatively referenced by — RFC 9181: A Common YANG Data Model for Layer 2 and Layer 3 VPNs
Normatively referenced by — RFC 9644: YANG Groupings for SSH Clients and SSH Servers
Normatively referenced by — RFC 8022: A YANG Data Model for Routing Management
Normatively referenced by — RFC 8695: A YANG Data Model for the Routing Information Protocol (RIP)
Normatively referenced by — RFC 8071: NETCONF Call Home and RESTCONF Call Home
Normatively referenced by — RFC 8242: Interface to the Routing System (I2RS) Ephemeral State Requirements
Normatively referenced by — RFC 9130: YANG Data Model for the IS-IS Protocol
Normatively referenced by — RFC 9633: Deterministic Networking (DetNet) YANG Data Model
Normatively referenced by — RFC 9907: Guidelines for Authors and Reviewers of Documents Containing YANG Data Models
Normatively referenced by — RFC 8049: YANG Data Model for L3VPN Service Delivery
Normatively referenced by — RFC 8346: A YANG Data Model for Layer 3 Topologies
Normatively referenced by — RFC 8808: A YANG Data Model for Factory Default Settings
Normatively referenced by — RFC 9020: YANG Data Model for Segment Routing
Normatively referenced by — RFC 9067: A YANG Data Model for Routing Policy
Normatively referenced by — RFC 9127: YANG Data Model for Bidirectional Forwarding Detection (BFD)
Normatively referenced by — RFC 8348: A YANG Data Model for Hardware Management
Normatively referenced by — RFC 9105: A YANG Data Model for Terminal Access Controller Access-Control System Plus (TACACS+)
Normatively referenced by — RFC 9128: YANG Data Model for Protocol Independent Multicast (PIM)
Normatively referenced by — RFC 9196: YANG Modules Describing Capabilities for Systems and Datastore Update Notifications
Normatively referenced by — RFC 9363: A YANG Data Model for Static Context Header Compression (SCHC)
Normatively referenced by — RFC 9648: YANG Data Model for TCP
Normatively referenced by — RFC 9826: A YANG Data Model for the Path Computation Element Communication Protocol (PCEP)
Normatively referenced by — RFC 6470: Network Configuration Protocol (NETCONF) Base Notifications
Normatively referenced by — RFC 7846: Peer-to-Peer Streaming Tracker Protocol (PPSTP)
Normatively referenced by — RFC 8072: YANG Patch Media Type