From nobody Wed Feb 22 16:25:53 2017 Return-Path: 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 0D203129BDF; Wed, 22 Feb 2017 16:25:52 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.202 X-Spam-Level: X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-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 eJ4kWz1hxBvx; Wed, 22 Feb 2017 16:25:50 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B23B812943E; Wed, 22 Feb 2017 16:25:50 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id A9449B812DF; Wed, 22 Feb 2017 16:25:50 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20170223002550.A9449B812DF@rfc-editor.org> Date: Wed, 22 Feb 2017 16:25:50 -0800 (PST) Archived-At: 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 X-BeenThere: l3sm@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: L3VPN Service YANG Model discussion group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Feb 2017 00:25:52 -0000 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 From nobody Thu Feb 23 02:16:03 2017 Return-Path: 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 76941129576 for ; Thu, 23 Feb 2017 02:16:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.619 X-Spam-Level: X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 rO6zGsLdJRzE for ; Thu, 23 Feb 2017 02:16:00 -0800 (PST) Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA07A12940F for ; Thu, 23 Feb 2017 02:15:59 -0800 (PST) Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id v1NAFuCm023770 for ; Thu, 23 Feb 2017 10:15:56 GMT Received: from 950129200 ([176.241.250.3]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id v1NAFqBF023700 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 23 Feb 2017 10:15:55 GMT From: "Adrian Farrel" To: Date: Thu, 23 Feb 2017 10:15:53 -0000 Message-ID: <066b01d28dbd$d30e22a0$792a67e0$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdKNvXn61ktCgLtlTmqZK3F2acEsSw== Content-Language: en-gb X-TM-AS-MML: disable X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-22902.006 X-TM-AS-Result: No--18.686-10.0-31-10 X-imss-scan-details: No--18.686-10.0-31-10 X-TMASE-MatchedRID: GlfY9sJwYjWUTHcBIlpNjQArNgt5xpQY9mnDjfUPq57VI4jqKuL4kcLm p4jPUF8t7REE2YVnJbtXuyMnZpCFt4LSdZH87OpgFUp+lByZqyZXLUapz6y7gbV5fSMRD1zqB8X dQRbt5oWIgdy5F01wFYQnmACSkDXTmDtCGf5o8p/GpnII6axD8/x3eAlFiEvxfeB8ZkBTx8tpgr Yvic2QdZ6Ss6O2bihGn5u7YzlPkLdP7jC0dUY+fXBRIrj8R47F0vlakDvxh7zJC2Vrkbq/8WeaW IM6JItDpSrtOw6hEDsFmLWhahf/7odzDiQgvDoahrs6JAEL1u5QCOsAlaxN7z3BZApXJkDbHSf8 mOmG69wyibtO+RP0k5AIDb/C+6edy89ZiJ9C0P2RGzV8Bxg0cYLsLasl5ROhW6o+Yr9x1kUuLLr hEK94BgNfuNNfQvFEpjFa8odGvnWODEe7Fi7H8qrxFQMz0ixcQqkzn0LWK14M82iMq1bjvCXxJz PjY49CoTxITPicBVy4fMIiODWrIk1+zyfzlN7y/sToY2qzpx7qSTqi4vLijtRnEQCUU+jzjoczm uoPCq3T0yznlKet5lRCAn5MAufviRYo3nosdXcYyIb8QjZvSepqb1kBNYxm Archived-At: Subject: [L3sm] RFC 8049 on YANG Data Model for L3VPN Service Delivery X-BeenThere: l3sm@ietf.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: adrian@olddog.co.uk List-Id: L3VPN Service YANG Model discussion group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Feb 2017 10:16:02 -0000 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 From nobody Thu Feb 23 02:59:26 2017 Return-Path: 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 9C7AF1296A3 for ; Thu, 23 Feb 2017 02:59:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.521 X-Spam-Level: X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, 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 H8RZmq6-Jnfd for ; Thu, 23 Feb 2017 02:59:22 -0800 (PST) Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE31A129480 for ; Thu, 23 Feb 2017 02:59:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9553; q=dns/txt; s=iport; t=1487847561; x=1489057161; h=subject:references:to:from:message-id:date:mime-version: in-reply-to; bh=+esBM0H+sLOlRst3d1KAtq2m8vYClo0QoK3ziMnJXbg=; b=ZLxjI5/2XGU2ysrZGgTtXUNj60NXpFYAT4rRLngF905DFMPl3iMhLIju C8RbU12+YW8/JQYODfeN3nh/vZgSyRxHH/XzvJ5Tt6X2Qf5TkdOzCo6Vx PqHzBkYb3BJ81xO5bmBcGlZw4f9xZ8Sgzu7v255G7zltiLeHwUc+DMX2T 4=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DUAwCdv65Y/xbLJq1dGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBhDEDgQaNY3KQSR+QCIUsgg0fAQqFeAKDVxgBAgEBAQEBAQFiHQuEcAE?= =?us-ascii?q?CBAEBTCAbHAMBAg0iJwocAggGDQYCAQEQBwIEh2cDgVIDFQ6waiuLFwEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEaBYZMggUIgmKBPIEVgV8FP4VFBZwThnSDHAyIB4F7hRy?= =?us-ascii?q?DLoZLiDaCaYgHHziBACEUCBcVGCaEUAgQgWI/NYkJDxeCFwEBAQ?= X-IronPort-AV: E=Sophos;i="5.35,197,1484006400"; d="scan'208,217";a="649907410" Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Feb 2017 10:59:19 +0000 Received: from [10.61.240.233] ([10.61.240.233]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v1NAxISf014512 for ; Thu, 23 Feb 2017 10:59:18 GMT References: <20170223002550.A9449B812DF@rfc-editor.org> To: "l3sm@ietf.org" From: Benoit Claise X-Forwarded-Message-Id: <20170223002550.A9449B812DF@rfc-editor.org> Message-ID: <9906f790-7763-20e9-88b4-04daa741004f@cisco.com> Date: Thu, 23 Feb 2017 11:59:18 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 In-Reply-To: <20170223002550.A9449B812DF@rfc-editor.org> Content-Type: multipart/alternative; boundary="------------B41E1951F0EC39E98BBBB528" Archived-At: Subject: [L3sm] Fwd: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Feb 2017 10:59:24 -0000 This is a multi-part message in MIME format. --------------B41E1951F0EC39E98BBBB528 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Great achievement. Thanks to operators who drove this, and to everybody who helped. Regards, Benoit -------- Forwarded Message -------- Subject: [L3sm] RFC 8049 on YANG Data Model for L3VPN Service Delivery Date: Wed, 22 Feb 2017 16:25:50 -0800 (PST) From: rfc-editor@rfc-editor.org To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org CC: l3sm@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org 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 . --------------B41E1951F0EC39E98BBBB528 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 7bit Great achievement.
Thanks to operators who drove this, and to everybody who helped.

Regards, Benoit


-------- Forwarded Message --------
Subject: [L3sm] RFC 8049 on YANG Data Model for L3VPN Service Delivery
Date: Wed, 22 Feb 2017 16:25:50 -0800 (PST)
From: rfc-editor@rfc-editor.org
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
CC: l3sm@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org 


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
.
--------------B41E1951F0EC39E98BBBB528-- From nobody Thu Feb 23 06:39:49 2017 Return-Path: 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 ; 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 ; 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 ; 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 To: "adrian@olddog.co.uk" , "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: 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: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Feb 2017 14:39:48 -0000 Q29uZ3JhdHVsYXRpb25zIG9uIGF1dGhvcnMgYW5kIHRoYW5rIHlvdSB0byBhbGwgaW52b2x2ZWQg dG8gaGVscCBhY2hpZXZlIHRoaXMgbWlsZXN0b25lLg0KDQotUWluDQpfX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fDQq3orz+yMs6IEwzc20gW2wzc20tYm91bmNlc0BpZXRmLm9y Z10gtPqx7SBBZHJpYW4gRmFycmVsIFthZHJpYW5Ab2xkZG9nLmNvLnVrXQ0Kt6LLzcqxvOQ6IDIw MTfE6jLUwjIzyNUgMTg6MTUNCsrVvP7IyzogbDNzbUBpZXRmLm9yZw0K1vfM4jogW0wzc21dIFJG QyA4MDQ5IG9uIFlBTkcgRGF0YSBNb2RlbCBmb3IgTDNWUE4gU2VydmljZSBEZWxpdmVyeQ0KDQpU aGFua3MgdG8gYWxsIG9mIHlvdSBmb3IgaGVscGluZyB0byBjb21wbGV0ZSB0aGlzIHdvcmsuDQpT cGVjaWFsIHRoYW5rcyAob2YgY291cnNlKSB0byB0aGUgYXV0aG9ycyBhbmQgY29udHJpYnV0b3Jz Lg0KQW5kIG1hc3NpdmUgdGhhbmtzIHRvIFN0ZXBoYW5lIHdobyB3YXMgcmVsZW50bGVzcyBpbiBt YWtpbmcgdGhlIG1pbm9yIGVkaXRzIGZvcg0KdGhlIG1hbnkgZGlmZmVyZW50IHBoYXNlcyBvZiAi ZmluYWwiIHJldmlldy4NCg0KQWRyaWFuDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0N Cj4gRnJvbTogTDNzbSBbbWFpbHRvOmwzc20tYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9m IHJmYy1lZGl0b3JAcmZjLQ0KPiBlZGl0b3Iub3JnDQo+IFNlbnQ6IDIzIEZlYnJ1YXJ5IDIwMTcg MDA6MjYNCj4gVG86IGlldGYtYW5ub3VuY2VAaWV0Zi5vcmc7IHJmYy1kaXN0QHJmYy1lZGl0b3Iu b3JnDQo+IENjOiBsM3NtQGlldGYub3JnOyBkcmFmdHMtdXBkYXRlLXJlZkBpYW5hLm9yZzsgcmZj LWVkaXRvckByZmMtZWRpdG9yLm9yZw0KPiBTdWJqZWN0OiBbTDNzbV0gUkZDIDgwNDkgb24gWUFO RyBEYXRhIE1vZGVsIGZvciBMM1ZQTiBTZXJ2aWNlIERlbGl2ZXJ5DQo+DQo+IEEgbmV3IFJlcXVl c3QgZm9yIENvbW1lbnRzIGlzIG5vdyBhdmFpbGFibGUgaW4gb25saW5lIFJGQyBsaWJyYXJpZXMu DQo+DQo+DQo+ICAgICAgICAgUkZDIDgwNDkNCj4NCj4gICAgICAgICBUaXRsZTogICAgICBZQU5H IERhdGEgTW9kZWwgZm9yIEwzVlBODQo+ICAgICAgICAgICAgICAgICAgICAgU2VydmljZSBEZWxp dmVyeQ0KPiAgICAgICAgIEF1dGhvcjogICAgIFMuIExpdGtvd3NraSwgTC4gVG9tb3Rha2ksIEsu IE9nYWtpDQo+ICAgICAgICAgU3RhdHVzOiAgICAgU3RhbmRhcmRzIFRyYWNrDQo+ICAgICAgICAg U3RyZWFtOiAgICAgSUVURg0KPiAgICAgICAgIERhdGU6ICAgICAgIEZlYnJ1YXJ5IDIwMTcNCj4g ICAgICAgICBNYWlsYm94OiAgICBzdGVwaGFuZS5saXRrb3dza2lAb3JhbmdlLmNvbSwNCj4gICAg ICAgICAgICAgICAgICAgICBsdWlzLnRvbW90YWtpQHZlcml6b24uY29tLA0KPiAgICAgICAgICAg ICAgICAgICAgIGtlLW9vZ2FraUBrZGRpLmNvbQ0KPiAgICAgICAgIFBhZ2VzOiAgICAgIDE1Nw0K PiAgICAgICAgIENoYXJhY3RlcnM6IDI3Mjk3NA0KPiAgICAgICAgIFVwZGF0ZXMvT2Jzb2xldGVz L1NlZUFsc286ICAgTm9uZQ0KPg0KPiAgICAgICAgIEktRCBUYWc6ICAgIGRyYWZ0LWlldGYtbDNz bS1sM3Zwbi1zZXJ2aWNlLW1vZGVsLTE5LnR4dA0KPg0KPiAgICAgICAgIFVSTDogICAgICAgIGh0 dHBzOi8vd3d3LnJmYy1lZGl0b3Iub3JnL2luZm8vcmZjODA0OQ0KPg0KPiAgICAgICAgIERPSTog ICAgICAgIDEwLjE3NDg3L1JGQzgwNDkNCj4NCj4gVGhpcyBkb2N1bWVudCBkZWZpbmVzIGEgWUFO RyBkYXRhIG1vZGVsIHRoYXQgY2FuIGJlIHVzZWQgZm9yDQo+IGNvbW11bmljYXRpb24gYmV0d2Vl biBjdXN0b21lcnMgYW5kIG5ldHdvcmsgb3BlcmF0b3JzIGFuZCB0byBkZWxpdmVyDQo+IGEgTGF5 ZXIgMyBwcm92aWRlci1wcm92aXNpb25lZCBWUE4gc2VydmljZS4gIFRoaXMgZG9jdW1lbnQgaXMg bGltaXRlZA0KPiB0byBCR1AgUEUtYmFzZWQgVlBOcyBhcyBkZXNjcmliZWQgaW4gUkZDcyA0MDI2 LCA0MTEwLCBhbmQgNDM2NC4gIFRoaXMNCj4gbW9kZWwgaXMgaW50ZW5kZWQgdG8gYmUgaW5zdGFu dGlhdGVkIGF0IHRoZSBtYW5hZ2VtZW50IHN5c3RlbSB0bw0KPiBkZWxpdmVyIHRoZSBvdmVyYWxs IHNlcnZpY2UuICBJdCBpcyBub3QgYSBjb25maWd1cmF0aW9uIG1vZGVsIHRvIGJlDQo+IHVzZWQg ZGlyZWN0bHkgb24gbmV0d29yayBlbGVtZW50cy4gIFRoaXMgbW9kZWwgcHJvdmlkZXMgYW4gYWJz dHJhY3RlZA0KPiB2aWV3IG9mIHRoZSBMYXllciAzIElQIFZQTiBzZXJ2aWNlIGNvbmZpZ3VyYXRp b24gY29tcG9uZW50cy4gIEl0IHdpbGwNCj4gYmUgdXAgdG8gdGhlIG1hbmFnZW1lbnQgc3lzdGVt IHRvIHRha2UgdGhpcyBtb2RlbCBhcyBpbnB1dCBhbmQgdXNlDQo+IHNwZWNpZmljIGNvbmZpZ3Vy YXRpb24gbW9kZWxzIHRvIGNvbmZpZ3VyZSB0aGUgZGlmZmVyZW50IG5ldHdvcmsNCj4gZWxlbWVu dHMgdG8gZGVsaXZlciB0aGUgc2VydmljZS4gIEhvdyB0aGUgY29uZmlndXJhdGlvbiBvZiBuZXR3 b3JrDQo+IGVsZW1lbnRzIGlzIGRvbmUgaXMgb3V0IG9mIHNjb3BlIGZvciB0aGlzIGRvY3VtZW50 Lg0KPg0KPiBUaGlzIGRvY3VtZW50IGlzIGEgcHJvZHVjdCBvZiB0aGUgTDNWUE4gU2VydmljZSBN b2RlbCBXb3JraW5nIEdyb3VwIG9mIHRoZQ0KPiBJRVRGLg0KPg0KPiBUaGlzIGlzIG5vdyBhIFBy b3Bvc2VkIFN0YW5kYXJkLg0KPg0KPiBTVEFOREFSRFMgVFJBQ0s6IFRoaXMgZG9jdW1lbnQgc3Bl Y2lmaWVzIGFuIEludGVybmV0IFN0YW5kYXJkcyBUcmFjaw0KPiBwcm90b2NvbCBmb3IgdGhlIElu dGVybmV0IGNvbW11bml0eSwgYW5kIHJlcXVlc3RzIGRpc2N1c3Npb24gYW5kIHN1Z2dlc3Rpb25z DQo+IGZvciBpbXByb3ZlbWVudHMuICBQbGVhc2UgcmVmZXIgdG8gdGhlIGN1cnJlbnQgZWRpdGlv biBvZiB0aGUgT2ZmaWNpYWwNCj4gSW50ZXJuZXQgUHJvdG9jb2wgU3RhbmRhcmRzIChodHRwczov L3d3dy5yZmMtZWRpdG9yLm9yZy9zdGFuZGFyZHMpIGZvciB0aGUNCj4gc3RhbmRhcmRpemF0aW9u IHN0YXRlIGFuZCBzdGF0dXMgb2YgdGhpcyBwcm90b2NvbC4gIERpc3RyaWJ1dGlvbiBvZiB0aGlz DQo+IG1lbW8gaXMgdW5saW1pdGVkLg0KPg0KPiBUaGlzIGFubm91bmNlbWVudCBpcyBzZW50IHRv IHRoZSBJRVRGLUFubm91bmNlIGFuZCByZmMtZGlzdCBsaXN0cy4NCj4gVG8gc3Vic2NyaWJlIG9y IHVuc3Vic2NyaWJlLCBzZWUNCj4gICBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3Rp bmZvL2lldGYtYW5ub3VuY2UNCj4gICBodHRwczovL21haWxtYW4ucmZjLWVkaXRvci5vcmcvbWFp bG1hbi9saXN0aW5mby9yZmMtZGlzdA0KPg0KPiBGb3Igc2VhcmNoaW5nIHRoZSBSRkMgc2VyaWVz LCBzZWUgaHR0cHM6Ly93d3cucmZjLWVkaXRvci5vcmcvc2VhcmNoDQo+IEZvciBkb3dubG9hZGlu ZyBSRkNzLCBzZWUgaHR0cHM6Ly93d3cucmZjLWVkaXRvci5vcmcvcmV0cmlldmUvYnVsaw0KPg0K PiBSZXF1ZXN0cyBmb3Igc3BlY2lhbCBkaXN0cmlidXRpb24gc2hvdWxkIGJlIGFkZHJlc3NlZCB0 byBlaXRoZXIgdGhlDQo+IGF1dGhvciBvZiB0aGUgUkZDIGluIHF1ZXN0aW9uLCBvciB0byByZmMt ZWRpdG9yQHJmYy1lZGl0b3Iub3JnLiAgVW5sZXNzDQo+IHNwZWNpZmljYWxseSBub3RlZCBvdGhl cndpc2Ugb24gdGhlIFJGQyBpdHNlbGYsIGFsbCBSRkNzIGFyZSBmb3INCj4gdW5saW1pdGVkIGRp c3RyaWJ1dGlvbi4NCj4NCj4NCj4gVGhlIFJGQyBFZGl0b3IgVGVhbQ0KPiBBc3NvY2lhdGlvbiBN YW5hZ2VtZW50IFNvbHV0aW9ucywgTExDDQo+DQo+DQo+IF9fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fDQo+IEwzc20gbWFpbGluZyBsaXN0DQo+IEwzc21AaWV0 Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9sM3NtDQoNCl9f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpMM3NtIG1haWxp bmcgbGlzdA0KTDNzbUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0 aW5mby9sM3Nt From nobody Tue Feb 28 02:49:44 2017 Return-Path: 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 3C0EF129501 for ; Tue, 28 Feb 2017 02:49:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.902 X-Spam-Level: X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 ueMQg-7-H1OA for ; Tue, 28 Feb 2017 02:49:41 -0800 (PST) Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 2443F1294FE for ; Tue, 28 Feb 2017 02:49:41 -0800 (PST) Received: from [10.147.40.137] (unknown [173.38.220.34]) by mail.tail-f.com (Postfix) with ESMTPSA id 14E831AE02A7; Tue, 28 Feb 2017 11:49:37 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) From: Jan Lindblad In-Reply-To: <066b01d28dbd$d30e22a0$792a67e0$@olddog.co.uk> Date: Tue, 28 Feb 2017 11:49:36 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <066b01d28dbd$d30e22a0$792a67e0$@olddog.co.uk> To: adrian@olddog.co.uk X-Mailer: Apple Mail (2.3259) Archived-At: Cc: l3sm@ietf.org 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Feb 2017 10:49:43 -0000 A great achievement that I have long awaited, for sure! I have some concerns with the resulting model, however, and I now = (obviously) regret not looking at this earlier and taking part in the = review process. At ietf-l3vpn-svc.yang:2053 I find: grouping site-devices { container devices { must "/l3vpn-svc/sites/site/management/type =3D "+ "'provider-managed' or "+ "/l3vpn-svc/sites/site/management/type =3D "+ "'co-managed'" { description "Applicable only for provider-managed or co-managed device."; } To me, it appears that the author intended to say that the "container = device" configuration is only applicable when the current site = management type is 'provider-managed' or 'co-managed'. That would make = sense.=20 The use of "must" and the use of the absolute paths above changes the = meaning in YANG to "as soon as any l3vpn is configured, there must be at = least one l3vpn (not necessarily the current one) that is = 'provider-managed' or 'co-managed'." One implication would be that it = would not be legal to have a collection of only 'customer-managed' vpns. = What would be legal, though, is to have one 'provider-managed' l3vpn = with no device configuration and another 'customer-managed' with devices = configured. I expect this was not the intention. This was something I noticed after spending a few minutes reading the = model. Perhaps a YANG doctor review would be appropriate? Best Regards, /jan > On 23 Feb 2017, at 11:15, Adrian Farrel wrote: >=20 > 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. >=20 > Adrian >=20 >> -----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 >>=20 >> A new Request for Comments is now available in online RFC libraries. >>=20 >>=20 >> RFC 8049 >>=20 >> 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 >>=20 >> I-D Tag: draft-ietf-l3sm-l3vpn-service-model-19.txt >>=20 >> URL: https://www.rfc-editor.org/info/rfc8049 >>=20 >> DOI: 10.17487/RFC8049 >>=20 >> 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. >>=20 >> This document is a product of the L3VPN Service Model Working Group = of the >> IETF. >>=20 >> This is now a Proposed Standard. >>=20 >> 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. >>=20 >> 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 >>=20 >> For searching the RFC series, see https://www.rfc-editor.org/search >> For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk >>=20 >> 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. >>=20 >>=20 >> The RFC Editor Team >> Association Management Solutions, LLC >>=20 >>=20 >> _______________________________________________ >> L3sm mailing list >> L3sm@ietf.org >> https://www.ietf.org/mailman/listinfo/l3sm >=20 > _______________________________________________ > L3sm mailing list > L3sm@ietf.org > https://www.ietf.org/mailman/listinfo/l3sm >=20