Re: [netmod] RFC 6991 on Common YANG Data Types

Benoit Claise <bclaise@cisco.com> Thu, 01 August 2013 12:24 UTC

Return-Path: <bclaise@cisco.com>
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 8AA7421F9DC6 for <netmod@ietfa.amsl.com>; Thu, 1 Aug 2013 05:24:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.243
X-Spam-Level:
X-Spam-Status: No, score=-10.243 tagged_above=-999 required=5 tests=[AWL=-0.244, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7FNGpJATd1lz for <netmod@ietfa.amsl.com>; Thu, 1 Aug 2013 05:24:47 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id D57CB21E819E for <netmod@ietf.org>; Thu, 1 Aug 2013 05:20:42 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r71CKZaX018582 for <netmod@ietf.org>; Thu, 1 Aug 2013 14:20:35 +0200 (CEST)
Received: from [10.61.99.120] (dhcp-10-61-99-120.cisco.com [10.61.99.120]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r71CKKcP009445 for <netmod@ietf.org>; Thu, 1 Aug 2013 14:20:30 +0200 (CEST)
Message-ID: <51FA5280.2050505@cisco.com>
Date: Thu, 01 Aug 2013 14:20:16 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: NETMOD Working Group <netmod@ietf.org>
References: <20130731141356.E17E46212E@rfc-editor.org>
In-Reply-To: <20130731141356.E17E46212E@rfc-editor.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [netmod] RFC 6991 on Common YANG Data Types
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 01 Aug 2013 12:25:19 -0000

Just in time!
Congrats the author, chairs, and entire WG.

Regards, Benoit
> A new Request for Comments is now available in online RFC libraries.
>
>          
>          RFC 6991
>
>          Title:      Common YANG Data Types
>          Author:     J. Schoenwaelder, Ed.
>          Status:     Standards Track
>          Stream:     IETF
>          Date:       July 2013
>          Mailbox:    j.schoenwaelder@jacobs-university.de
>          Pages:      30
>          Characters: 60242
>          Obsoletes:  RFC6021
>
>          I-D Tag:    draft-ietf-netmod-rfc6021-bis-03.txt
>
>          URL:        http://www.rfc-editor.org/rfc/rfc6991.txt
>
> This document introduces a collection of common data types to be used
> with the YANG data modeling language.  This document obsoletes RFC
> 6021.
>
> This document is a product of the NETCONF Data Modeling Language 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 Internet
> Official Protocol Standards (STD 1) 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
>    http://www.ietf.org/mailman/listinfo/ietf-announce
>    http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>
> For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php
> For downloading RFCs, see http://www.rfc-editor.org/rfc.html
>
> 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
>
>
>