RFC 6536: Network Configuration Protocol (NETCONF) Access Control Model
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8341.
Current version: RFC 8341 — Network Configuration Access Control Model
In plain English — editorial summary, not part of the RFC
The standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) requires a structured and secure operating environment that promotes human usability and multi-vendor interoperability. There is a need for standard mechanisms to restrict NETCONF protocol access for particular users to a pre-configured subset of all available NETCONF protocol operations and content. This document defines such an access control model. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6536
- Published
- March 2012
- Authors
- A. Bierman; M. Bjorklund
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 49
- Also known as
- —
- Obsoleted by:
- RFC 8341
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6087Guidelines for Authors and Reviewers of YANG Data Model DocumentsObsoleted
January 2011
- RFC 6022YANG Module for NETCONF MonitoringCurrent
October 2010
- RFC 6991Common YANG Data TypesObsoleted
July 2013
- RFC 6021Common YANG Data TypesObsoleted
October 2010
- RFC 6020YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)Updated
October 2010
- RFC 7224IANA Interface Type YANG ModuleCurrent
May 2014
- RFC 5277NETCONF Event NotificationsCurrent
July 2008
- RFC 7950The YANG 1.1 Data Modeling LanguageUpdated
August 2016
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?