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

"Aijun Wang" <> Tue, 25 August 2015 01:18 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 6789F1A8793 for <>; Mon, 24 Aug 2015 18:18:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 3.644
X-Spam-Level: ***
X-Spam-Status: No, score=3.644 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FH_RELAY_NODNS=1.451, J_CHICKENPOX_12=0.6, RDNS_NONE=0.793] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 92o0wQVhPtV6 for <>; Mon, 24 Aug 2015 18:18:09 -0700 (PDT)
Received: from (unknown []) by (Postfix) with ESMTP id 492001A3B9B for <>; Mon, 24 Aug 2015 18:18:07 -0700 (PDT)
Received: from ctbriwangaij (unknown []) by app1 (Coremail) with SMTP id Z0GX06CLaAOYwdtVxVHvDQ==.28801S2; Tue, 25 Aug 2015 09:15:19 +0800 (CST)
From: Aijun Wang <>
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>
Date: Tue, 25 Aug 2015 09:17:52 +0800
Message-ID: <001201d0ded3$e6f8b8b0$b4ea2a10$>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHQzdyhsnaNIULvEkejKqX38Ehzhp36HZIAgCC4CFA=
Content-Language: zh-cn
X-Coremail-Antispam: 1U3129KBjvJXoW3GFy5uFWxZF48Jw1kKrWUXFb_yoW7WrW3pF WjqrW3Kr4rtw18Gw4kXr1YqryrZrZ5G3y3CF15Jw1DZa45GF1vgryIkr1YvayDGrn5Xw4j vr4F9r1UW3WrXrJanT9S1TB71UUUUUUv73VFW2AGmfu7bjvjm3AaLaJ3UjIYCTnIWjBvb7 Iv0xC_Jr1l5I8CrVACY4xI64kE6c02F40Ex7xfM7kC6x804xWl14x267AKxVWUJVW8JwAF xVCF77xC6IxKo4kEV4yl1I0EscIYIxCEI4klw4CSwwAv7VCjz48v1sIEY20_GF1lx4CE17 CEb7AF67AKxVWUXVWUAjIFyTuYvjfUojjgDUUUU
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, 25 Aug 2015 01:18:12 -0000

Hi, stephane:

It seems that the current version of the Yang Model is more
structured/moduled and organized reasonable. 

Here I have some questions for the revised version:
1. What is the scenario where the leaf "customer-nat-address" will be used?
If the customer being provided one public address, why use NAT? if use NAT,
why allocate such "customer-nat-address"?
2. What is the main reason that define grouping "vpn-svc-cfg"? you have
defined grouping "site-service-mpls", "site-service-multicast" etc. Is it
possible to define for example "site-service-cloudaccess" and use them later
directly within the container "l3vpn-svc"?
3. There are some overlapping contents between grouping
"site-attachment-ip-connection" and
"site-customer-routing-specific-information", and the latter is more vague
and hard to understand. Can it be merged into the grouping

Aijun Wang

China Telecom Corporation Limited Beijing Research Institute 
Intelligent Network Product Line

-----Original Message-----
From: L3sm [] On Behalf Of
Sent: Monday, August 03, 2015 7:11 PM
Subject: 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
 This draft is a work item of the L3VPN Service Model  Working Group of the

        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