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

"xiechf.bri@chinatelecom.cn" <xiechf.bri@chinatelecom.cn> Mon, 22 January 2018 07:13 UTC

Return-Path: <xiechf.bri@chinatelecom.cn>
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 26063126C83 for <l3sm@ietfa.amsl.com>; Sun, 21 Jan 2018 23:13:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 29c3wl_wH-YS for <l3sm@ietfa.amsl.com>; Sun, 21 Jan 2018 23:13:55 -0800 (PST)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.221]) by ietfa.amsl.com (Postfix) with ESMTP id EC6FF1243FE for <l3sm@ietf.org>; Sun, 21 Jan 2018 23:13:52 -0800 (PST)
HMM_SOURCE_IP: 172.18.0.48:7046.981591294
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-219.142.69.76 (unknown [172.18.0.48]) by chinatelecom.cn (HERMES) with ESMTP id 1B85F2800A1; Mon, 22 Jan 2018 15:13:45 +0800 (CST)
Received: from ip<219.142.69.76> ([172.18.0.48]) by App0024 with ESMTP id a90107f0-a201-4b84-a067-2687e427ce6b for bclaise@cisco.com; Mon Jan 22 15:13:50 2018
0/X-Total-Score: 0:
X-Real-From: xiechf.bri@chinatelecom.cn
X-Receive-IP: 172.18.0.48
X-MEDUSA-Status: 0
Date: Mon, 22 Jan 2018 15:13:44 +0800
From: "xiechf.bri@chinatelecom.cn" <xiechf.bri@chinatelecom.cn>
To: bclaise <bclaise@cisco.com>, "adrian@olddog.co.uk" <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>, <4e774262-2070-21a5-2f3a-e702854d3819@cisco.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 8, 379[cn]
Mime-Version: 1.0
Message-ID: <2018012211084965285019@ctbri.com.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart052857804068_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/EpHJyPTE57MH0FA9iBIFy5NbuPw>
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: Mon, 22 Jan 2018 07:13:59 -0000

Congratulations to the team of RFC8299. :-)

Chongfeng



xiechf@ctbri.com.cn
 
From: Benoit Claise
Date: 2018-01-21 00:33
To: adrian; 'l3sm'
CC: 'Jan Lindblad'; Alissa Cooper
Subject: Re: [L3sm] FW: RFC 8299 on YANG Data Model for L3VPN Service Delivery
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
>
> .
>
 
_______________________________________________
L3sm mailing list
L3sm@ietf.org
https://www.ietf.org/mailman/listinfo/l3sm