[Netconf] STD 91, RFC 8341 on Network Configuration Access Control Model

rfc-editor@rfc-editor.org Fri, 16 March 2018 21:29 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 902E612D94A; Fri, 16 Mar 2018 14:29:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ylAjth2N5Xq9; Fri, 16 Mar 2018 14:29:22 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BE17126BF0; Fri, 16 Mar 2018 14:29:15 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 1A2E2B80C97; Fri, 16 Mar 2018 14:29:12 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, netconf@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180316212912.1A2E2B80C97@rfc-editor.org>
Date: Fri, 16 Mar 2018 14:29:12 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/gRcwT1abtWfHbwm75ybHCsthoy4>
Subject: [Netconf] STD 91, RFC 8341 on Network Configuration Access Control Model
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2018 21:29:31 -0000

A new Request for Comments is now available in online RFC libraries.

        STD 91        
        RFC 8341

        Title:      Network Configuration Access Control Model 
        Author:     A. Bierman,
                    M. Bjorklund
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Mailbox:    andy@yumaworks.com, 
                    mbj@tail-f.com
        Pages:      58
        Characters: 109849
        Obsoletes:  RFC 6536
        See Also:   STD 91

        I-D Tag:    draft-ietf-netconf-rfc6536bis-09.txt

        URL:        https://www.rfc-editor.org/info/rfc8341

        DOI:        10.17487/RFC8341

The standardization of network configuration interfaces for use with
the Network Configuration Protocol (NETCONF) or the RESTCONF protocol
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 or RESTCONF protocol
access for particular users to a preconfigured subset of all
available NETCONF or RESTCONF protocol operations and content.  This
document defines such an access control model.

This document obsoletes RFC 6536.

This document is a product of the Network Configuration Working Group of the IETF.

This is now an Internet Standard.

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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

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