Re: [L3sm] FW: RFC 8299 on YANG Data Model for L3VPN Service Delivery

Benoit Claise <bclaise@cisco.com> Sat, 20 January 2018 16:34 UTC

Return-Path: <bclaise@cisco.com>
X-Original-To: l3sm@ietfa.amsl.com
Delivered-To: l3sm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CED8612700F for <l3sm@ietfa.amsl.com>; Sat, 20 Jan 2018 08:34:04 -0800 (PST)
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 autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 gA5JQWFydRBH for <l3sm@ietfa.amsl.com>; Sat, 20 Jan 2018 08:34:02 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3C5A120726 for <l3sm@ietf.org>; Sat, 20 Jan 2018 08:34:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4052; q=dns/txt; s=iport; t=1516466041; x=1517675641; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=ZdTNnHyDBarCd90wUjyrMwWAV3e4Tt7aTyX4Mv2mvEc=; b=NbNtmr7dMAMf9UtJtyq7JfgGAIYignrm18jPS55JztX00FmcQV2ISnr9 e9plrTcFeuZ1AiyBq73PzAZBnuTEyvcqwIy0M6IMRkhhHfesjo2Dil7F0 gFPAroj8fGr+i6/aezEfy7Vlv6/NX/skoMcuJ+AyG1lmJmGKd2uLDCh4P A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0B5AQBabmNa/xbLJq1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYQodCeDXYsYj0cnlz4VggIKGAuFGAKFIxYBAQEBAQEBAQFrKIU?= =?us-ascii?q?jAQEBBAEBIRUWKwwECxEDAQEBAwIIGwMCAicKFQgBCAYBDAYCAQEQBwIEiXoDF?= =?us-ascii?q?RCvTIInii4BAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYEPgzqDbIIRDIJ5gUmBIkQ?= =?us-ascii?q?BAQKBMxUFgzmCZQWKYxSHOpFJhw2BBoN2DIlGghuGH4Nxh3SKdYJcgWaIEIE8J?= =?us-ascii?q?gwmgVAyGggbFRmCToJZBxCBaEA3iQIPGIIkAQEB?=
X-IronPort-AV: E=Sophos;i="5.46,386,1511827200"; d="scan'208";a="1506802"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Jan 2018 16:33:59 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id w0KGXxRG006948; Sat, 20 Jan 2018 16:33:59 GMT
To: adrian@olddog.co.uk, "'l3sm'" <l3sm@ietf.org>
Cc: "'Jan Lindblad'" <janl@tail-f.com>, Alissa Cooper <alissa@cooperw.in>
References: <20180120003441.F0216B816CE@rfc-editor.org> <022e01d391f7$bfd89c30$3f89d490$@olddog.co.uk>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <4e774262-2070-21a5-2f3a-e702854d3819@cisco.com>
Date: Sat, 20 Jan 2018 17:33:59 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <022e01d391f7$bfd89c30$3f89d490$@olddog.co.uk>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/tBZbXvjgpWRFuKxF1UbFSoaXjvo>
Subject: Re: [L3sm] FW: RFC 8299 on YANG Data Model for L3VPN Service Delivery
X-BeenThere: l3sm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: L3VPN Service YANG Model discussion group <l3sm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3sm>, <mailto:l3sm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l3sm/>
List-Post: <mailto:l3sm@ietf.org>
List-Help: <mailto:l3sm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3sm>, <mailto:l3sm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Jan 2018 16:34:05 -0000

Yes, thanks to all.
Glad this one is finally delivered.

Regards, Benoit
> Thanks to Qin and the other authors for their tireless (?) work to get this revision out.
>
> Thanks, too, to Jan for his excellent and helpful reviews, and thanks to our two ADs (yes, it took two ADs!) for pushing to get this published this year.
>
> We hope to apply all the lessons learned to the L2SM work that is approaching WG last call in the L2SM working group.
>
> Best,
> Adrian
>
>> -----Original Message-----
>> From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org] On Behalf Of rfc-
>> editor@rfc-editor.org
>> Sent: 20 January 2018 00:35
>> To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
>> Cc: drafts-update-ref@iana.org; rfc-editor@rfc-editor.org
>> Subject: RFC 8299 on YANG Data Model for L3VPN Service Delivery
>>
>> A new Request for Comments is now available in online RFC libraries.
>>
>>
>>          RFC 8299
>>
>>          Title:      YANG Data Model for L3VPN
>>                      Service Delivery
>>          Author:     Q. Wu, Ed.,
>>                      S. Litkowski,
>>                      L. Tomotaki,
>>                      K. Ogaki
>>          Status:     Standards Track
>>          Stream:     IETF
>>          Date:       January 2018
>>          Mailbox:    bill.wu@huawei.com,
>>                      stephane.litkowski@orange.com,
>>                      luis.tomotaki@verizon.com,
>>                      ke-oogaki@kddi.com
>>          Pages:      188
>>          Characters: 344738
>>          Obsoletes:  RFC 8049
>>
>>          I-D Tag:    draft-wu-l3sm-rfc8049bis-11.txt
>>
>>          URL:        https://www.rfc-editor.org/info/rfc8299
>>
>>          DOI:        10.17487/RFC8299
>>
>> This document defines a YANG data model that can be used for
>> communication between customers and network operators and to deliver
>> a Layer 3 provider-provisioned VPN service.  This document is limited
>> to BGP PE-based VPNs as described in RFCs 4026, 4110, and 4364.  This
>> model is intended to be instantiated at the management system to
>> deliver the overall service.  It is not a configuration model to be
>> used directly on network elements.  This model provides an abstracted
>> view of the Layer 3 IP VPN service configuration components.  It will
>> be up to the management system to take this model as input and use
>> specific configuration models to configure the different network
>> elements to deliver the service.  How the configuration of network
>> elements is done is out of scope for this document.
>>
>> This document obsoletes RFC 8049; it replaces the unimplementable
>> module in that RFC with a new module with the same name that is not
>> backward compatible.  The changes are a series of small fixes to the
>> YANG module and some clarifications to the text.
>>
>> 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
>
> .
>