RFC 8819 on YANG Module Tags

rfc-editor@rfc-editor.org Mon, 04 January 2021 23:06 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 279FC3A0A0B; Mon, 4 Jan 2021 15:06:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[SPF_PASS=-0.001, URIBL_BLOCKED=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 IYwfgxwrRSEl; Mon, 4 Jan 2021 15:06:12 -0800 (PST)
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 7460F3A09E9; Mon, 4 Jan 2021 15:06:12 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 954B2F40754; Mon, 4 Jan 2021 15:06:10 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8819 on YANG Module Tags
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: <20210104230610.954B2F40754@rfc-editor.org>
Date: Mon, 04 Jan 2021 15:06:10 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/qCDIFPqs96Q1l5F6HB9F1q8aOkE>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
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: <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: Mon, 04 Jan 2021 23:06:15 -0000

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

        
        RFC 8819

        Title:      YANG Module Tags 
        Author:     C. Hopps,
                    L. Berger,
                    D. Bogdanovic
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2021
        Mailbox:    chopps@chopps.org, 
                    lberger@labn.net, 
                    ivandean@gmail.com
        Pages:      19
        Updates:    RFC 8407

        I-D Tag:    draft-ietf-netmod-module-tags-10.txt

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

        DOI:        10.17487/RFC8819

This document provides for the association of tags with YANG modules.
The expectation is for such tags to be used to help classify and
organize modules. A method for defining, reading, and writing modules
tags is provided. Tags may be registered and assigned during module
definition, assigned by implementations, or dynamically defined and
set by users. This document also provides guidance to future model
writers; as such, this document updates RFC 8407.

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

This is now a Proposed 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