[netmod] BCP 216, RFC 8407 on Guidelines for Authors and Reviewers of Documents Containing YANG Data Models

rfc-editor@rfc-editor.org Thu, 18 October 2018 04:55 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E4C01277CC; Wed, 17 Oct 2018 21:55:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 sgdjPqewOKKb; Wed, 17 Oct 2018 21:55:11 -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 89E6D127332; Wed, 17 Oct 2018 21:55:11 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 561F5B80E97; Wed, 17 Oct 2018 21:54:45 -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, netmod@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20181018045445.561F5B80E97@rfc-editor.org>
Date: Wed, 17 Oct 2018 21:54:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/BPjebvApxv8z18H4r3r2EDyXSa4>
Subject: [netmod] BCP 216, RFC 8407 on Guidelines for Authors and Reviewers of Documents Containing YANG Data Models
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2018 04:55:13 -0000

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

        BCP 216        
        RFC 8407

        Title:      Guidelines for Authors and Reviewers 
                    of Documents Containing YANG Data Models 
        Author:     A. Bierman
        Status:     Best Current Practice
        Stream:     IETF
        Date:       October 2018
        Mailbox:    andy@yumaworks.com
        Pages:      63
        Characters: 123260
        Obsoletes:  RFC 6087
        See Also:   BCP 216

        I-D Tag:    draft-ietf-netmod-rfc6087bis-20.txt

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

        DOI:        10.17487/RFC8407

This memo provides guidelines for authors and reviewers of
specifications containing YANG modules.  Recommendations and
procedures are defined, which are intended to increase
interoperability and usability of Network Configuration Protocol
(NETCONF) and RESTCONF protocol implementations that utilize YANG
modules.  This document obsoletes RFC 6087.

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


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
  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