BCP 203, RFC 7803 on Changing the Registration Policy for the NETCONF Capability URNs Registry

rfc-editor@rfc-editor.org Wed, 24 February 2016 22:34 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 (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 13C321A01D8 for <ietf-announce@ietfa.amsl.com>; Wed, 24 Feb 2016 14:34:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.908
X-Spam-Status: No, score=-106.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.006, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id YXuV9jO0T5yB for <ietf-announce@ietfa.amsl.com>; Wed, 24 Feb 2016 14:34:25 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 618881A01A2 for <ietf-announce@ietf.org>; Wed, 24 Feb 2016 14:34:25 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id D89CE180013; Wed, 24 Feb 2016 14:33:49 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 203, RFC 7803 on Changing the Registration Policy for the NETCONF Capability URNs Registry
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160224223349.D89CE180013@rfc-editor.org>
Date: Wed, 24 Feb 2016 14:33:49 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/XkXKCFIKFzLUG_Css5Pf2eIdYPI>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 24 Feb 2016 22:34:27 -0000

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

        BCP 203        
        RFC 7803

        Title:      Changing the Registration Policy for 
                    the NETCONF Capability URNs Registry 
        Author:     B. Leiba
        Status:     Best Current Practice
        Stream:     IETF
        Date:       February 2016
        Mailbox:    barryleiba@computer.org
        Pages:      3
        Characters: 5133
        Updates:    RFC 6241
        See Also:   BCP 203

        I-D Tag:    draft-leiba-netmod-regpolicy-update-02.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7803

The registration policy for the "Network Configuration Protocol
(NETCONF) Capability URNs" registry, set up by RFC 6241, has turned
out to be unnecessarily strict.  This document changes that
registration policy to "IETF Review", allowing registrations from
certain well-reviewed Experimental RFCs, in addition to Standards
Track RFCs.

BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

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