RFC 6243: With-defaults Capability for NETCONF
In plain English — editorial summary, not part of the RFC
The Network Configuration Protocol (NETCONF) defines ways to read and edit configuration data from a NETCONF server. In some cases, part of this data may not be set by the NETCONF client, but rather a default value known to the server is used instead. In many situations the NETCONF client has a priori knowledge about default data, so the NETCONF server does not need to save it in a NETCONF configuration datastore or send it to the client in a retrieval operation reply. In other situations the NETCONF client will need this data from the server. Not all server implementations treat this default data the same way. This document defines a capability-based extension to the NETCONF protocol that allows the NETCONF client to identify how defaults are processed by the server, and also defines new mechanisms for client control of server processing of default data. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6243
- Published
- June 2011
- Authors
- A. Bierman; B. Lengyel
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 26
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6242Using the NETCONF Protocol over Secure Shell (SSH)Current
June 2011
- RFC 6244An Architecture for Network Management Using NETCONF and YANGCurrent
June 2011
- RFC 4742Using the NETCONF Configuration Protocol over Secure SHell (SSH)Obsoleted
December 2006
- RFC 4741NETCONF Configuration ProtocolObsoleted
December 2006
- RFC 5607Remote Authentication Dial-In User Service (RADIUS) Authorization for Network Access Server (NAS) ManagementCurrent
July 2009
- RFC 5381Experience of Implementing NETCONF over SOAPCurrent
October 2008
- RFC 6241Network Configuration Protocol (NETCONF)Updated
June 2011
- RFC 6248RFC 4148 and the IP Performance Metrics (IPPM) Registry of Metrics Are ObsoleteCurrent
April 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?