RFC 8294 on Common YANG Data Types for the Routing Area

rfc-editor@rfc-editor.org Thu, 14 December 2017 21:31 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25286126CE8; Thu, 14 Dec 2017 13:31:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 2YU-gpcAJ-Dk; Thu, 14 Dec 2017 13:31:37 -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 502F51200C1; Thu, 14 Dec 2017 13:31:37 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 505A6B80C33; Thu, 14 Dec 2017 13:31:10 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDgyOTQgb24gQ29tbW9uIFlBTkcgRGF0YSBUeXBlcyBmb3IgdGhlIFJvdXRpbmcgQXJlYQ==?=
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, rtgwg@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20171214213110.505A6B80C33@rfc-editor.org>
Date: Thu, 14 Dec 2017 13:31:10 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/KEfpdAFhQwjLCqqVCb6D6ZlCAF8>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2017 21:31:39 -0000

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

        
        RFC 8294

        Title:      Common YANG Data Types for 
                    the Routing Area 
        Author:     X. Liu, Y. Qu,
                    A. Lindem, C. Hopps,
                    L. Berger
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2017
        Mailbox:    xufeng_liu@jabil.com, 
                    yingzhen.qu@huawei.com, 
                    acee@cisco.com,
                    chopps@chopps.org, 
                    lberger@labn.net
        Pages:      43
        Characters: 66851
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtgwg-routing-types-17.txt

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

        DOI:        10.17487/RFC8294

This document defines a collection of common data types using the
YANG data modeling language.  These derived common types are designed
to be imported by other modules defined in the routing area.

This document is a product of the Routing Area Working Group 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