RFC 6536 on Network Configuration Protocol (NETCONF) Access Control Model
rfc-editor@rfc-editor.org Thu, 08 March 2012 01:43 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2914F21E8034; Wed, 7 Mar 2012 17:43:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.165
X-Spam-Level:
X-Spam-Status: No, score=-102.165 tagged_above=-999 required=5 tests=[AWL=-0.165, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OYMFs9H3lNZo; Wed, 7 Mar 2012 17:43:04 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id B2A8221E8033; Wed, 7 Mar 2012 17:43:04 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 7D99372E00C; Wed, 7 Mar 2012 17:42:54 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6536 on Network Configuration Protocol (NETCONF) Access Control Model
From: rfc-editor@rfc-editor.org
Message-Id: <20120308014254.7D99372E00C@rfc-editor.org>
Date: Wed, 07 Mar 2012 17:42:54 -0800
Cc: netconf@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Mar 2012 01:43:05 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6536
Title: Network Configuration Protocol (NETCONF) Access
Control Model
Author: A. Bierman, M. Bjorklund
Status: Standards Track
Stream: IETF
Date: March 2012
Mailbox: andy@yumaworks.com,
mbj@tail-f.com
Pages: 49
Characters: 90803
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-netconf-access-control-07.txt
URL: http://www.rfc-editor.org/rfc/rfc6536.txt
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]
This document is a product of the Network Configuration Working Group of the IETF.
This is now a Proposed Standard Protocol.
STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements. Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC