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

Qin Wu <bill.wu@huawei.com> Thu, 23 February 2017 14:39 UTC

Return-Path: <bill.wu@huawei.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 5CF6A12988F for <l3sm@ietfa.amsl.com>; Thu, 23 Feb 2017 06:39:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, 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 W9JfxDDza_Kk for <l3sm@ietfa.amsl.com>; Thu, 23 Feb 2017 06:39:45 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C284129891 for <l3sm@ietf.org>; Thu, 23 Feb 2017 06:39:38 -0800 (PST)
Received: from 172.18.7.190 (EHLO LHREML714-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DHQ20214; Thu, 23 Feb 2017 14:39:35 +0000 (GMT)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by LHREML714-CAH.china.huawei.com (10.201.108.37) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 23 Feb 2017 14:39:34 +0000
Received: from NKGEML513-MBS.china.huawei.com ([169.254.2.43]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0235.001; Thu, 23 Feb 2017 22:39:30 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: [L3sm] RFC 8049 on YANG Data Model for L3VPN Service Delivery
Thread-Index: AdKNvXn61ktCgLtlTmqZK3F2acEsSwAJQRPg
Date: Thu, 23 Feb 2017 14:39:29 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA9A7824E1@nkgeml513-mbs.china.huawei.com>
References: <066b01d28dbd$d30e22a0$792a67e0$@olddog.co.uk>
In-Reply-To: <066b01d28dbd$d30e22a0$792a67e0$@olddog.co.uk>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.109.108.115]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090201.58AEF428.0098, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.2.43, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: c28f1eadcaf6e892c0beaf84a60edd2f
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/UvIR897INCDk1U3RASnZWi7ldik>
Subject: Re: [L3sm] RFC 8049 on YANG Data Model for L3VPN Service Delivery
X-BeenThere: l3sm@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 23 Feb 2017 14:39:48 -0000

Congratulations on authors and thank you to all involved to help achieve this milestone.

-Qin
_____________________________________
发件人: L3sm [l3sm-bounces@ietf.org] 代表 Adrian Farrel [adrian@olddog.co.uk]
发送时间: 2017年2月23日 18:15
收件人: l3sm@ietf.org
主题: [L3sm] RFC 8049 on YANG Data Model for L3VPN Service Delivery

Thanks to all of you for helping to complete this work.
Special thanks (of course) to the authors and contributors.
And massive thanks to Stephane who was relentless in making the minor edits for
the many different phases of "final" review.

Adrian

> -----Original Message-----
> From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of rfc-editor@rfc-
> editor.org
> Sent: 23 February 2017 00:26
> To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
> Cc: l3sm@ietf.org; drafts-update-ref@iana.org; rfc-editor@rfc-editor.org
> Subject: [L3sm] RFC 8049 on YANG Data Model for L3VPN Service Delivery
>
> A new Request for Comments is now available in online RFC libraries.
>
>
>         RFC 8049
>
>         Title:      YANG Data Model for L3VPN
>                     Service Delivery
>         Author:     S. Litkowski, L. Tomotaki, K. Ogaki
>         Status:     Standards Track
>         Stream:     IETF
>         Date:       February 2017
>         Mailbox:    stephane.litkowski@orange.com,
>                     luis.tomotaki@verizon.com,
>                     ke-oogaki@kddi.com
>         Pages:      157
>         Characters: 272974
>         Updates/Obsoletes/SeeAlso:   None
>
>         I-D Tag:    draft-ietf-l3sm-l3vpn-service-model-19.txt
>
>         URL:        https://www.rfc-editor.org/info/rfc8049
>
>         DOI:        10.17487/RFC8049
>
> 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 is a product of the L3VPN Service Model 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
>
>
> _______________________________________________
> L3sm mailing list
> L3sm@ietf.org
> https://www.ietf.org/mailman/listinfo/l3sm

_______________________________________________
L3sm mailing list
L3sm@ietf.org
https://www.ietf.org/mailman/listinfo/l3sm