Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-01.txt

Qin Wu <> Tue, 18 August 2015 09:57 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 572881B32EF for <>; Tue, 18 Aug 2015 02:57:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.822
X-Spam-Status: No, score=-0.822 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CN_BODY_35=0.339, J_CHICKENPOX_12=0.6, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 82boSj8BsUxt for <>; Tue, 18 Aug 2015 02:57:05 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3DE781A89A5 for <>; Tue, 18 Aug 2015 02:57:05 -0700 (PDT)
Received: from (EHLO ([]) by (MOS 4.3.7-GA FastPath queued) with ESMTP id CAA09786; Tue, 18 Aug 2015 09:57:02 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Tue, 18 Aug 2015 10:57:01 +0100
Received: from ([]) by ([]) with mapi id 14.03.0235.001; Tue, 18 Aug 2015 17:56:55 +0800
From: Qin Wu <>
To: "" <>, "" <>
Thread-Topic: I-D Action: draft-ietf-l3sm-l3vpn-service-model-01.txt
Thread-Index: AQHQzdygsDz6w/A2DkKjxohuK3utf535mGcAgBf9jUA=
Date: Tue, 18 Aug 2015 09:56:54 +0000
Message-ID: <>
References: <> <4893_1438600279_55BF4C57_4893_13767_1_9E32478DFA9976438E7A22F69B08FF92166BD47F@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
In-Reply-To: <4893_1438600279_55BF4C57_4893_13767_1_9E32478DFA9976438E7A22F69B08FF92166BD47F@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-01.txt
X-Mailman-Version: 2.1.15
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, 18 Aug 2015 09:57:08 -0000

Thanks for update, 1st level of modularization sounds good, especially separating site template as a separate list make a lot of sense to me 
although separating site template from site introduces a lot of duplicated data nodes that occur in both site and site template list, it greatly facilitates service automation (i.e., building more new site using site template) and also the modular component enclosed in the grouping statement in the service model can be reused when other new service model can be developed.

Regarding removal of native vpn, I will raise a issue in the separate email.

发件人: L3sm [] 代表
发送时间: 2015年8月3日 19:11
主题: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-01.txt

Hi WG,

Here is a new version of our draft fitting some comments received on the list or during IETF meeting.
- First level of modularization has been done , is it enough ?
- Site templates putted as a separate list
- More abstracted VPN policy and removal of native VPN
- Add MPLS leaf in vpn-svc for the CsC case
- some renaming

Multicast comments are not addressed yet.

Please provide your comments on this new proposal.

-----Original Message-----
From: I-D-Announce [] On Behalf Of
Sent: Monday, August 03, 2015 13:08
Subject: I-D Action: draft-ietf-l3sm-l3vpn-service-model-01.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the L3VPN Service Model  Working Group of the IETF.

        Title           : YANG Data Model for L3VPN service delivery
        Authors         : Stephane Litkowski
                          Rob Shakir
                          Luis Tomotaki
                          Kevin D'Souza
	Filename        : draft-ietf-l3sm-l3vpn-service-model-01.txt
	Pages           : 94
	Date            : 2015-08-03

   This document defines a YANG data model that can be used to deliver a
   Layer 3 Provider Provisioned VPN service.  The document is limited to
   the BGP PE-based VPNs as described in RFC4110 and RFC4364.  This
   model is intended to be instantiated at management system to deliver
   the overall service.  This model is not a configuration model to be
   used directly on network elements.  This model provides an abstracted
   view of the Layer 3 IPVPN service configuration components.  It will
   be up to a management system to take this as an input and use
   specific configurations models to configure the different network
   elements to deliver the service.  How configuration of network
   elements is done is out of scope of the document.

The IETF datatracker status page for this draft is:

There's also a htmlized version available at:

A diff from the previous version is available at:

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at

Internet-Drafts are also available by anonymous FTP at:

I-D-Announce mailing list
Internet-Draft directories: or


Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

L3sm mailing list