[Netconf] Fw: RFC 6536 on Network Configuration Protocol (NETCONF)Access Control Model

Congrats to the WG for another good RFC.
Soecial thanks go of course to Andy and Martin.

Bert Wijnen
co-chair and document shepherd
----- Original Message ----- 
From: <rfc-editor@rfc-editor.org>
To: <ietf-announce@ietf.org>; <rfc-dist@rfc-editor.org>
Cc: <netconf@ietf.org>; <rfc-editor@rfc-editor.org>
Sent: Thursday, March 08, 2012 2:42 AM
Subject: [Netconf] RFC 6536 on Network Configuration Protocol (NETCONF)Access 
Control Model

>
> 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
>
>
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf 