IETF Logo Mail Archive

[Rtg-yang-coord] FW: Fwd: New Version Notification for draft-ietf-netmod-routing-cfg-20.txt

"Acee Lindem (acee)" <acee@cisco.com> Fri, 16 October 2015 23:39 UTC

Return-Path: <acee@cisco.com>
X-Original-To: rtg-yang-coord@ietfa.amsl.com
Delivered-To: rtg-yang-coord@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7FD41A1A80 for <rtg-yang-coord@ietfa.amsl.com>; Fri, 16 Oct 2015 16:39:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 0oXSxaEpVLBl for <rtg-yang-coord@ietfa.amsl.com>; Fri, 16 Oct 2015 16:39:49 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B8A01A1A25 for <rtg-yang-coord@ietf.org>; Fri, 16 Oct 2015 16:39:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3354; q=dns/txt; s=iport; t=1445038789; x=1446248389; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=p81s88uMnGVtkqSLiI9KbR9tcOOi90Zi34I09c+z6O0=; b=IKGt/kt5SyVT7WYwqFIEt7CIjkmxiGSzEAFN3XL9X3DRbfpmyvkh74QX pNbpdF9Je1qtUYJlAqX02eP1kIiit1b6kIkuZR1IwsuYfVx9x4YYpQLco sKFOXNpR/LHWfps1N74nhio75bdHv2vyOtL5G1WgUl4T+4rwRrysjqmxx I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D3AQC3iSFW/5pdJa1egzVUbwa9awENgVkXDIV7AhyBHDgUAQEBAQEBAYEKhCgBAQEEAQEBIBE6CRICAQgRAwECAwImAgICJQsVBgEBBQMCBBOIMA2wapMHAQEBAQEBAQEBAQEBAQEBAQEBAQEZgSKKU4RyIgaCY4FFBY0SiFBAAYUYiASBWEiDdJYBAR8BAUKCRIE/cgGEYIEGAQEB
X-IronPort-AV: E=Sophos;i="5.17,691,1437436800"; d="scan'208";a="198740109"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-5.cisco.com with ESMTP; 16 Oct 2015 23:39:48 +0000
Received: from XCH-RCD-014.cisco.com (xch-rcd-014.cisco.com [173.37.102.24]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id t9GNdmd1002686 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <rtg-yang-coord@ietf.org>; Fri, 16 Oct 2015 23:39:48 GMT
Received: from xch-rcd-015.cisco.com (173.37.102.25) by XCH-RCD-014.cisco.com (173.37.102.24) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 16 Oct 2015 18:39:32 -0500
Received: from xch-rcd-015.cisco.com ([173.37.102.25]) by XCH-RCD-015.cisco.com ([173.37.102.25]) with mapi id 15.00.1104.000; Fri, 16 Oct 2015 18:39:32 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Routing YANG <rtg-yang-coord@ietf.org>
Thread-Topic: [Rtg-yang-coord] Fwd: New Version Notification for draft-ietf-netmod-routing-cfg-20.txt
Thread-Index: AQHRCGvou/cK1uuXcEeEQqZLDV0qNg==
Date: Fri, 16 Oct 2015 23:39:32 +0000
Message-ID: <D247028E.36BD7%acee@cisco.com>
References: <20151016152212.4503.6696.idtracker@ietfa.amsl.com> <125FBB52-A0C6-4893-B017-1D646291571D@nic.cz>
In-Reply-To: <125FBB52-A0C6-4893-B017-1D646291571D@nic.cz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.199]
Content-Type: text/plain; charset="utf-8"
Content-ID: <BE4C0D0A79B7954F9C226B7272ABD671@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/_MZpcoOsyxpHuyDZXGr2lGsud_w>
Subject: [Rtg-yang-coord] FW: Fwd: New Version Notification for draft-ietf-netmod-routing-cfg-20.txt
X-BeenThere: rtg-yang-coord@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "\"List to discuss coordination between the Routing related YANG models\"" <rtg-yang-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-yang-coord/>
List-Post: <mailto:rtg-yang-coord@ietf.org>
List-Help: <mailto:rtg-yang-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Oct 2015 23:39:50 -0000

I believe that this is the version that we should advance (and I believe
Lada agrees). It represents the basic routing model for a host/router and
will be a strong foundation for future augmentation.

Thanks, 
Acee 


On 10/16/15, 11:26 AM, "Rtg-yang-coord on behalf of Ladislav Lhotka"
<rtg-yang-coord-bounces@ietf.org on behalf of lhotka@nic.cz> wrote:

>
>
>> Begin forwarded message:
>> 
>> From: internet-drafts@ietf.org
>> Date: 16 October 2015 at 17:22:12 GMT+2
>> To: "Ladislav Lhotka" <lhotka@nic.cz>, "Acee Lindem" <acee@cisco.com>,
>>"Ladislav Lhotka" <lhotka@nic.cz>, "Acee Lindem" <acee@cisco.com>
>> Subject: New Version Notification for
>>draft-ietf-netmod-routing-cfg-20.txt
>> 
>> 
>> A new version of I-D, draft-ietf-netmod-routing-cfg-20.txt
>> has been successfully submitted by Ladislav Lhotka and posted to the
>> IETF repository.
>> 
>> Name:		draft-ietf-netmod-routing-cfg
>> Revision:	20
>> Title:		A YANG Data Model for Routing Management
>> Document date:	2015-10-16
>> Group:		netmod
>> Pages:		69
>> URL:            
>>https://www.ietf.org/internet-drafts/draft-ietf-netmod-routing-cfg-20.txt
>> Status:         
>>https://datatracker.ietf.org/doc/draft-ietf-netmod-routing-cfg/
>> Htmlized:       
>>https://tools.ietf.org/html/draft-ietf-netmod-routing-cfg-20
>> Diff:           
>>https://www.ietf.org/rfcdiff?url2=draft-ietf-netmod-routing-cfg-20
>> 
>> Abstract:
>>   This document contains a specification of three YANG modules.
>>   Together they form the core routing data model which serves as a
>>   framework for configuring and managing a routing subsystem.  It is
>>   expected that these modules will be augmented by additional YANG
>>   modules defining data models for routing protocols, route filters and
>>   other functions.  The core routing data model provides common
>>   building blocks for such extensions - routing instances, routes,
>>   routing information bases (RIB), and routing protocols.
>> 
>> 
>> 
>> 
>> Please note that it may take a couple of minutes from the time of
>>submission
>> until the htmlized version and diff are available at tools.ietf.org.
>> 
>> The IETF Secretariat
>> 
>
>--
>Ladislav Lhotka, CZ.NIC Labs
>PGP Key ID: E74E8C0C
>
>
>
>
>_______________________________________________
>Rtg-yang-coord mailing list
>Rtg-yang-coord@ietf.org
>https://www.ietf.org/mailman/listinfo/rtg-yang-coord

v2.23.0 | Report a Bug | By Email