
From nobody Wed Jun  1 02:05:46 2016
Return-Path: <liushucheng@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 EBD7512B04E for <l3sm@ietfa.amsl.com>; Wed,  1 Jun 2016 02:05:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.647
X-Spam-Level: 
X-Spam-Status: No, score=-5.647 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=-1.426, 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 I2YfUfE2OaJT for <l3sm@ietfa.amsl.com>; Wed,  1 Jun 2016 02:05:43 -0700 (PDT)
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 23A7512B009 for <l3sm@ietf.org>; Wed,  1 Jun 2016 02:05:43 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml705-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CLE58329; Wed, 01 Jun 2016 09:05:40 +0000 (GMT)
Received: from SZXEMA417-HUB.china.huawei.com (10.82.72.34) by lhreml705-cah.china.huawei.com (10.201.5.168) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 1 Jun 2016 10:05:39 +0100
Received: from SZXEMA509-MBS.china.huawei.com ([169.254.2.111]) by SZXEMA417-HUB.china.huawei.com ([10.82.72.34]) with mapi id 14.03.0235.001; Wed, 1 Jun 2016 17:05:26 +0800
From: "Liushucheng (Will)" <liushucheng@huawei.com>
To: "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-06.txt
Thread-Index: AQHRpE7Zqn5jXoq3+kasZhsAdthjXp/ScHGQ
Date: Wed, 1 Jun 2016 09:05:26 +0000
Message-ID: <C9B5F12337F6F841B35C404CF0554ACB89759A6E@SZXEMA509-MBS.china.huawei.com>
References: <20160502084407.23732.51331.idtracker@ietfa.amsl.com>
In-Reply-To: <20160502084407.23732.51331.idtracker@ietfa.amsl.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.78.84]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A0B0201.574EA565.002B, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.2.111, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 6e7a9fb2ddc474836ea25c1f5d63b429
Archived-At: <http://mailarchive.ietf.org/arch/msg/l3sm/dg-r0Bj9TFQEs2li2OuffMs4BzQ>
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-06.txt
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: Wed, 01 Jun 2016 09:05:46 -0000

Hi authors,

I am reading your draft. First question is, what content is delivered on th=
e link between orchestration and config manager, and what type of protocol =
is used here?

L3VPN-SVC |
              MODEL   |
                      |
                   +------------------+         +-----+
                   |   Orchestration  | < --- > | OSS |
                   +------------------+         +-----+
                      |            |
              +----------------+   |
              | Config manager |   |
              +----------------+   |
                      |            |
                      | Netconf/CLI ...
                      |            |
        +------------------------------------------------+
                             Network

                           +++++++
                           + AAA +
                           +++++++
Regards,
Will (Shucheng LIU)

> -----Original Message-----
> From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of
> internet-drafts@ietf.org
> Sent: Monday, May 02, 2016 4:44 PM
> To: i-d-announce@ietf.org
> Cc: l3sm@ietf.org
> Subject: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-06.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
> This draft is a work item of the L3VPN Service Model  of the IETF.
>=20
>         Title           : YANG Data Model for L3VPN service delivery
>         Authors         : Stephane Litkowski
>                           Rob Shakir
>                           Luis Tomotaki
>                           Kenichi Ogaki
>                           Kevin D'Souza
> 	Filename        : draft-ietf-l3sm-l3vpn-service-model-06.txt
> 	Pages           : 126
> 	Date            : 2016-05-02
>=20
> Abstract:
>    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.
>=20
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-l3sm-l3vpn-service-model/
>=20
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-l3sm-l3vpn-service-model-06
>=20
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-l3sm-l3vpn-service-model-0=
6
>=20
>=20
> Please note that it may take a couple of minutes from the time of submiss=
ion
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> L3sm mailing list
> L3sm@ietf.org
> https://www.ietf.org/mailman/listinfo/l3sm


From nobody Wed Jun  1 02:25:27 2016
Return-Path: <michael.scharf@nokia.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 C40D512D509 for <l3sm@ietfa.amsl.com>; Wed,  1 Jun 2016 02:25:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-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 Mzs6uKjzQaUz for <l3sm@ietfa.amsl.com>; Wed,  1 Jun 2016 02:25:24 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3F4912D50B for <l3sm@ietf.org>; Wed,  1 Jun 2016 02:25:23 -0700 (PDT)
Received: from fr712umx3.dmz.alcatel-lucent.com (unknown [135.245.210.42]) by Websense Email Security Gateway with ESMTPS id 63E9EE9CEA0F3 for <l3sm@ietf.org>; Wed,  1 Jun 2016 09:25:19 +0000 (GMT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (fr711usmtp1.zeu.alcatel-lucent.com [135.239.2.122]) by fr712umx3.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u519PLon014120 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <l3sm@ietf.org>; Wed, 1 Jun 2016 09:25:21 GMT
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id u519PHq6030469 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <l3sm@ietf.org>; Wed, 1 Jun 2016 11:25:21 +0200
Received: from FR712WXCHMBA15.zeu.alcatel-lucent.com ([169.254.7.44]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.03.0195.001; Wed, 1 Jun 2016 11:25:14 +0200
From: "Scharf, Michael (Nokia - DE)" <michael.scharf@nokia.com>
To: "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: actual-site-start / actual-site-stop
Thread-Index: AdG754BaCsdcgaLmQSuurBNDNn10SA==
Date: Wed, 1 Jun 2016 09:25:14 +0000
Message-ID: <655C07320163294895BBADA28372AF5D4887B657@FR712WXCHMBA15.zeu.alcatel-lucent.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.41]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/l3sm/aAAUz3_As3yGkLkqkbZbptGzAoI>
Subject: [L3sm] actual-site-start / actual-site-stop
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: Wed, 01 Jun 2016 09:25:26 -0000

Hi,

Is "actual-site-start" and "actual-site-stop" indeed meant to tagged by "co=
nfig true"?

If so, what is the expected behavior if this is set, either directly or by =
template?

Thanks

Michael


From nobody Wed Jun  1 02:30:33 2016
Return-Path: <stephane.litkowski@orange.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 6D3D712B060 for <l3sm@ietfa.amsl.com>; Wed,  1 Jun 2016 02:30:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.345
X-Spam-Level: 
X-Spam-Status: No, score=-3.345 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 eWvo5vzCE9hV for <l3sm@ietfa.amsl.com>; Wed,  1 Jun 2016 02:30:29 -0700 (PDT)
Received: from relais-inet.orange.com (relais-nor34.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 382C912D098 for <l3sm@ietf.org>; Wed,  1 Jun 2016 02:30:29 -0700 (PDT)
Received: from opfednr07.francetelecom.fr (unknown [xx.xx.xx.71]) by opfednr20.francetelecom.fr (ESMTP service) with ESMTP id 472EB40B26; Wed,  1 Jun 2016 11:30:27 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.24]) by opfednr07.francetelecom.fr (ESMTP service) with ESMTP id 221EB1C0078; Wed,  1 Jun 2016 11:30:27 +0200 (CEST)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM7D.corporate.adroot.infra.ftgroup ([fe80::9044:c5ee:4dd2:4f16%19]) with mapi id 14.03.0294.000; Wed, 1 Jun 2016 11:30:27 +0200
From: <stephane.litkowski@orange.com>
To: "Scharf, Michael (Nokia - DE)" <michael.scharf@nokia.com>, "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: actual-site-start / actual-site-stop
Thread-Index: AdG754BaCsdcgaLmQSuurBNDNn10SAAAKeUA
Date: Wed, 1 Jun 2016 09:30:26 +0000
Message-ID: <14583_1464773427_574EAB33_14583_3223_1_9E32478DFA9976438E7A22F69B08FF921BC3B97E@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <655C07320163294895BBADA28372AF5D4887B657@FR712WXCHMBA15.zeu.alcatel-lucent.com>
In-Reply-To: <655C07320163294895BBADA28372AF5D4887B657@FR712WXCHMBA15.zeu.alcatel-lucent.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.3]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/l3sm/wYgVlZOkDBL8mFhiz26T10Lih-I>
Subject: Re: [L3sm] actual-site-start / actual-site-stop
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: Wed, 01 Jun 2016 09:30:31 -0000

Hi Michael,

This is a mistake, these are ops state that needs to be config false.

Thanks for the catch.


-----Original Message-----
From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of Scharf, Michael (Nok=
ia - DE)
Sent: Wednesday, June 01, 2016 11:25
To: l3sm@ietf.org
Subject: [L3sm] actual-site-start / actual-site-stop

Hi,

Is "actual-site-start" and "actual-site-stop" indeed meant to tagged by "co=
nfig true"?

If so, what is the expected behavior if this is set, either directly or by =
template?

Thanks

Michael

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

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.


From nobody Wed Jun  1 02:33:48 2016
Return-Path: <stephane.litkowski@orange.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 E94DB12D641 for <l3sm@ietfa.amsl.com>; Wed,  1 Jun 2016 02:33:46 -0700 (PDT)
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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 RQcXqz2OnG-q for <l3sm@ietfa.amsl.com>; Wed,  1 Jun 2016 02:33:44 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7895112D172 for <l3sm@ietf.org>; Wed,  1 Jun 2016 02:33:44 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id E9DB83B4E46; Wed,  1 Jun 2016 11:33:42 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.60]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id C86F74C048; Wed,  1 Jun 2016 11:33:42 +0200 (CEST)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM7F.corporate.adroot.infra.ftgroup ([fe80::c1d7:e278:e357:11ad%19]) with mapi id 14.03.0294.000; Wed, 1 Jun 2016 11:33:42 +0200
From: <stephane.litkowski@orange.com>
To: "Liushucheng (Will)" <liushucheng@huawei.com>, "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-06.txt
Thread-Index: AQHRpE7Qrd0LdHa2NkyPEk/qyPbJ8p/UX1QAgAAo4nA=
Date: Wed, 1 Jun 2016 09:33:42 +0000
Message-ID: <25496_1464773622_574EABF6_25496_90_1_9E32478DFA9976438E7A22F69B08FF921BC3B98E@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <20160502084407.23732.51331.idtracker@ietfa.amsl.com> <C9B5F12337F6F841B35C404CF0554ACB89759A6E@SZXEMA509-MBS.china.huawei.com>
In-Reply-To: <C9B5F12337F6F841B35C404CF0554ACB89759A6E@SZXEMA509-MBS.china.huawei.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.3]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.4.25.91516
Archived-At: <http://mailarchive.ietf.org/arch/msg/l3sm/_DVe2OV_Gj3RLG1uT40X4jaYfOU>
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-06.txt
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: Wed, 01 Jun 2016 09:33:47 -0000

The config manager is typically an EMS (element management system) that is =
used when a device cannot be configured directly.
The north interface of such EMS depends on the EMS itself, this may be prop=
rietary interfaces, or REST API or Netconf ...


-----Original Message-----
From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of Liushucheng (Will)
Sent: Wednesday, June 01, 2016 11:05
To: l3sm@ietf.org
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-06.txt

Hi authors,

I am reading your draft. First question is, what content is delivered on th=
e link between orchestration and config manager, and what type of protocol =
is used here?

L3VPN-SVC |
              MODEL   |
                      |
                   +------------------+         +-----+
                   |   Orchestration  | < --- > | OSS |
                   +------------------+         +-----+
                      |            |
              +----------------+   |
              | Config manager |   |
              +----------------+   |
                      |            |
                      | Netconf/CLI ...
                      |            |
        +------------------------------------------------+
                             Network

                           +++++++
                           + AAA +
                           +++++++
Regards,
Will (Shucheng LIU)

> -----Original Message-----
> From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of=20
> internet-drafts@ietf.org
> Sent: Monday, May 02, 2016 4:44 PM
> To: i-d-announce@ietf.org
> Cc: l3sm@ietf.org
> Subject: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-06.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
> This draft is a work item of the L3VPN Service Model  of the IETF.
>=20
>         Title           : YANG Data Model for L3VPN service delivery
>         Authors         : Stephane Litkowski
>                           Rob Shakir
>                           Luis Tomotaki
>                           Kenichi Ogaki
>                           Kevin D'Souza
> 	Filename        : draft-ietf-l3sm-l3vpn-service-model-06.txt
> 	Pages           : 126
> 	Date            : 2016-05-02
>=20
> Abstract:
>    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.
>=20
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-l3sm-l3vpn-service-model/
>=20
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-l3sm-l3vpn-service-model-06
>=20
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-l3sm-l3vpn-service-model-
> 06
>=20
>=20
> Please note that it may take a couple of minutes from the time of=20
> submission until the htmlized version and diff are available at tools.iet=
f.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> 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

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.


From nobody Mon Jun  6 07:17:11 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: l3sm@ietf.org
Delivered-To: l3sm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1819E12D7AE; Mon,  6 Jun 2016 07:17:10 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.21.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160606141710.20806.10098.idtracker@ietfa.amsl.com>
Date: Mon, 06 Jun 2016 07:17:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/9DN_zziu6lZJprHRLTn0E-w01aE>
Cc: l3sm@ietf.org
Subject: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
X-BeenThere: l3sm@ietf.org
X-Mailman-Version: 2.1.17
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, 06 Jun 2016 14:17:10 -0000

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

        Title           : YANG Data Model for L3VPN service delivery
        Authors         : Stephane Litkowski
                          Rob Shakir
                          Luis Tomotaki
                          Kenichi Ogaki
                          Kevin D'Souza
	Filename        : draft-ietf-l3sm-l3vpn-service-model-07.txt
	Pages           : 153
	Date            : 2016-06-06

Abstract:
   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:
https://datatracker.ietf.org/doc/draft-ietf-l3sm-l3vpn-service-model/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-l3sm-l3vpn-service-model-07

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-l3sm-l3vpn-service-model-07


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

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Jun  6 07:19:59 2016
Return-Path: <stephane.litkowski@orange.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 2197E12D7D3 for <l3sm@ietfa.amsl.com>; Mon,  6 Jun 2016 07:19:58 -0700 (PDT)
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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 YPUDN0zolxfi for <l3sm@ietfa.amsl.com>; Mon,  6 Jun 2016 07:19:56 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81E9512D7D2 for <l3sm@ietf.org>; Mon,  6 Jun 2016 07:19:56 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 4FAE5324968 for <l3sm@ietf.org>; Mon,  6 Jun 2016 16:19:55 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.72]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id 313E535C048 for <l3sm@ietf.org>; Mon,  6 Jun 2016 16:19:55 +0200 (CEST)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541%19]) with mapi id 14.03.0294.000; Mon, 6 Jun 2016 16:19:54 +0200
From: <stephane.litkowski@orange.com>
To: "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
Thread-Index: AQHRv/4i8iSSM4mtWE6AeESR5nwEZZ/cfFGw
Date: Mon, 6 Jun 2016 14:19:54 +0000
Message-ID: <27218_1465222795_5755868B_27218_684_1_9E32478DFA9976438E7A22F69B08FF921BC41DA1@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <20160606141710.20806.10098.idtracker@ietfa.amsl.com>
In-Reply-To: <20160606141710.20806.10098.idtracker@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.3]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.4.25.91516
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/uF4UGw0Rq7tp4KVB9c9g0cQBIeU>
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
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: Mon, 06 Jun 2016 14:19:58 -0000

Hi L3SM,

Here is a new revision of the service model.
It contains a new way for modeling the site-network-access placement.
Also some fixes thanks to comment of the WG.
It contains also some first text on NNI modeling. I putted for the moment o=
ption B and option C out of scope, but this is still a point to be discusse=
d. At least it describes what we think necessary to be modeled for those ca=
ses.

Feel free to comment it.

Best Regards,

Stephane


-----Original Message-----
From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of internet-drafts@ietf=
.org
Sent: Monday, June 06, 2016 16:17
To: i-d-announce@ietf.org
Cc: l3sm@ietf.org
Subject: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt


A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
This draft is a work item of the L3VPN Service Model  of the IETF.

        Title           : YANG Data Model for L3VPN service delivery
        Authors         : Stephane Litkowski
                          Rob Shakir
                          Luis Tomotaki
                          Kenichi Ogaki
                          Kevin D'Souza
	Filename        : draft-ietf-l3sm-l3vpn-service-model-07.txt
	Pages           : 153
	Date            : 2016-06-06

Abstract:
   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:
https://datatracker.ietf.org/doc/draft-ietf-l3sm-l3vpn-service-model/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-l3sm-l3vpn-service-model-07

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-l3sm-l3vpn-service-model-07


Please note that it may take a couple of minutes from the time of submissio=
n until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.


From nobody Tue Jun  7 03:01:24 2016
Return-Path: <michael.scharf@nokia.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 9456512D54B for <l3sm@ietfa.amsl.com>; Tue,  7 Jun 2016 03:01:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-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 mNfv8LtAATk5 for <l3sm@ietfa.amsl.com>; Tue,  7 Jun 2016 03:01:21 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C86FF12D5D2 for <l3sm@ietf.org>; Tue,  7 Jun 2016 03:01:20 -0700 (PDT)
Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id 70920C0D15871; Tue,  7 Jun 2016 10:01:17 +0000 (GMT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (fr712usmtp2.zeu.alcatel-lucent.com [135.239.2.42]) by fr712umx4.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u57A1I5t027341 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Jun 2016 10:01:19 GMT
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id u57A1GqM026269 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 7 Jun 2016 12:01:17 +0200
Received: from FR712WXCHMBA15.zeu.alcatel-lucent.com ([169.254.7.34]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.03.0195.001; Tue, 7 Jun 2016 12:00:55 +0200
From: "Scharf, Michael (Nokia - DE)" <michael.scharf@nokia.com>
To: "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>, "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: Ops state in templates?
Thread-Index: AQHRwKN7PYndtzDTtESL0ZWnCcdFug==
Date: Tue, 7 Jun 2016 10:00:55 +0000
Message-ID: <655C07320163294895BBADA28372AF5D488BABA8@FR712WXCHMBA15.zeu.alcatel-lucent.com>
References: <655C07320163294895BBADA28372AF5D4887B657@FR712WXCHMBA15.zeu.alcatel-lucent.com> <14583_1464773427_574EAB33_14583_3223_1_9E32478DFA9976438E7A22F69B08FF921BC3B97E@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
In-Reply-To: <14583_1464773427_574EAB33_14583_3223_1_9E32478DFA9976438E7A22F69B08FF921BC3B97E@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.38]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/fnL3Lvn-CGTiYyfUwe7GJHoae2Y>
Subject: [L3sm] Ops state in templates?
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: Tue, 07 Jun 2016 10:01:23 -0000

Hi Stephane,

I see that this has been fixed in -07. Thanks. However, is ops state indeed=
 useful in the subtree "site-templates"?

The more fundamental question is whether the template mechanism may require=
 some further thinking. For instance:

* According to Section 5.15, "If a site has some particular parameters, spe=
cific parameters within the site MUST always override parameters derived fr=
om template." Now, what happens if the template defines a list (e.g., "casc=
aded-lan-prefixes")? If a requester would want to add something to a pre-de=
fined list, does this mean that first the template list entries have to be =
read, then list entries have to be added by the requester, and then the mer=
ged list has to be used in the service request?

* Another example that comes into my mind is the error handling if a site c=
annot be added, because some parameter in the template cannot be deployed. =
Is this a problem of the service request or of the template?

At first sight, this sort of question may be quite independent of the model=
ing of a L3VPN. It seems to me that templates may have some implications on=
 a system implementing the YANG model.=20

Thanks

Michael



-----Original Message-----
From: stephane.litkowski@orange.com [mailto:stephane.litkowski@orange.com]=
=20
Sent: Wednesday, June 01, 2016 11:30 AM
To: Scharf, Michael (Nokia - DE); l3sm@ietf.org
Subject: RE: actual-site-start / actual-site-stop

Hi Michael,

This is a mistake, these are ops state that needs to be config false.

Thanks for the catch.


-----Original Message-----
From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of Scharf, Michael (Nok=
ia - DE)
Sent: Wednesday, June 01, 2016 11:25
To: l3sm@ietf.org
Subject: [L3sm] actual-site-start / actual-site-stop

Hi,

Is "actual-site-start" and "actual-site-stop" indeed meant to tagged by "co=
nfig true"?

If so, what is the expected behavior if this is set, either directly or by =
template?

Thanks

Michael

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

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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. Le=
s messages electroniques etant susceptibles d'alteration, Orange decline to=
ute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation 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 dele=
te 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.


From nobody Tue Jun  7 10:09:47 2016
Return-Path: <daviball@cisco.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 344C412D7F7 for <l3sm@ietfa.amsl.com>; Tue,  7 Jun 2016 10:09:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level: 
X-Spam-Status: No, score=-15.947 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_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-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 i4MsWQ6f5Syu for <l3sm@ietfa.amsl.com>; Tue,  7 Jun 2016 10:09:44 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63F2A12D7EE for <l3sm@ietf.org>; Tue,  7 Jun 2016 10:09:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=19328; q=dns/txt; s=iport; t=1465319383; x=1466528983; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=Tz/5aO+KJmvMwExWl3vtrvyjAJaE7ar2/L2GVoidQx8=; b=EUQ/FAHa/XA8/jLDzbNMwZiepEy1asYyTGyvFQGbgyZcKCMtBDQP6WQJ 0VQnt+wrn1t72S4Qd41uvc/3/lNaV4Pz63T1zMcnbdz/71OJ5DFXnjhhu AsoSA02367CXwh50LMYQ5QuEjRmtrQPnRGKZKitH2mqhoDx7NOcd+lXHp U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0B9AgB3/1ZX/xbLJq1UCYQUK1K1bYR+g?= =?us-ascii?q?XkXAQyFbwKBeRQBAQEBAQEBZSeERQEBAQQBAQFrFwQLEQQBAQEnBycfCQgGAQw?= =?us-ascii?q?GAgEBiCsOvGQBAQEBAQEBAQEBAQEBAQEBAQEBAQEchieBdwiBS4EDhBIHAwEGA?= =?us-ascii?q?UgKhSQFmEuGBIgjgWpOhASDCYVbi3odg0geNoIHBReBTDsyiEsBDheBHgEBAQ?=
X-IronPort-AV: E=Sophos;i="5.26,434,1459814400";  d="scan'208,217";a="677597094"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Jun 2016 17:09:40 +0000
Received: from [10.63.23.103] (dhcp-ensft1-uk-vla370-10-63-23-103.cisco.com [10.63.23.103]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id u57H9dkn024375; Tue, 7 Jun 2016 17:09:39 GMT
To: stephane.litkowski@orange.com, "l3sm@ietf.org" <l3sm@ietf.org>
References: <20160606141710.20806.10098.idtracker@ietfa.amsl.com> <27218_1465222795_5755868B_27218_684_1_9E32478DFA9976438E7A22F69B08FF921BC41DA1@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
From: David Ball <daviball@cisco.com>
Message-ID: <ec72f8b8-8626-ba2c-bc50-7ce4a0cdc6df@cisco.com>
Date: Tue, 7 Jun 2016 18:09:38 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <27218_1465222795_5755868B_27218_684_1_9E32478DFA9976438E7A22F69B08FF921BC41DA1@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
Content-Type: multipart/alternative; boundary="------------7ED929BD5816F2C04A916FC3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/IphKPnvVOHyqSeXf8VZQtTfGRfY>
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
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: Tue, 07 Jun 2016 17:09:46 -0000

This is a multi-part message in MIME format.
--------------7ED929BD5816F2C04A916FC3
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

Hi Stephane,

Thanks for posting the new version, here are a few additional comments:

  * I agree with Michael that config:false items should not appear in
    the templates - and more broadly, that templates are not an
    L3SM-specific concept.  I might be better to punt this to the netmod
    WG to create a generic templating mechanism for yang, rather than
    trying to solve it in L3SM.
  * Sn 5.1.1.4: you added a sentence saying "Hub and spoke disjoint can
    also be seen as two hub and spoke VPNs sharing with a common hub
    site." - actually it's the spokes that are common not the hub,
    right?  So it should say "... sharing a common set of spoke sites."
  * Sn 5.4.1: I think with your new diversity constraints, the SubVPN
    flavor is no longer needed, right?  You could model it as separate
    sites, with accesses in the same group and with a "same-bearer"
    constraint on that group, right?  So Sn 5.4.1.3 could be deleted,
    along with the site-vpn-flavor-sub identity in the model.
  * Sn 5.5.3: I think the intent here is that the constraint applies to
    *other* site-network-accesses in the targeted group.  If the
    site-network-access for which the constraint is set is also part of
    the target group, the constraint does not apply to itself (e.g. in
    the first example where all 5 site-network-accesses are in group 10,
    the site-network-access in SITE1 does not need to be pe-diverse with
    itself - that wouldn't make any sense).  So, I think the word
    "other" needs to be inserted in several places.
  * Sn 5.5.3: Need to describe what the behaviour is if conflicting
    constraints are configured.  The simplest example would be 2
    site-network accesses in the same group, where one has a
    "pe-diverse" constraint targeted at that group, and the other has a
    "same-pe" constraint targeted at that group.  To meet both
    constraints, the SP has to connect the site-network-accesses to the
    same PE and also to different PEs, which is clearly impossible.  Of
    course there are lots of more complex ways of creating conflicting
    requirements, so I think we need to say what happens in this case.
  * Sn 5.5.4.2: I can't parse the second paragraph  - I think it should
    say: "... 3 branch offices can be connected to the same PE but not
    on the same linecard."
  * Sn 5.5.4.2: Second bullet after the figure, should say "pop-diverse"
    not "pe-diverse".
  * Sn 5.7: Traffic Protection should be a per-site attribute - it makes
    no sense to enable protection on one network-access for a site and
    disable it on another; it needs to be either enabled on all
    network-accesses for a given site, or on none of them, i.e. at a
    service level it is a per-site attribute.
  * Sn 5.9: If the CE is provider-managed, why is a management address
    needed in the model?  How the provider connects to the device would
    be internal to the provider, right?
    (For co-managed I can see this could be needed, i.e. to tell the
    customer what address to use to connect to the device for
    configuration/monitoring)
  * Sn 5.10.2: You said before that the model can only manage P2P
    connections; but this figure (and the next one) show the PE
    connected to a LAN, not to a CE.  I am not sure how to interpret
    this?  Isn't this a case where the connection is multipoint, not P2P?
  * Sn 5.11.2.2: I don't understand what it means to say that the QoS
    profile will be implemented at the PE or CE side of the WAN link. 
    This is a service model, it should not specify how the SP implements
    their network.  It is still unclear to me whether the QoS profile is
    supposed to apply to traffic flowing from the SP to the customer or
    from the customer to the SP - please can you clarify this?
  * Sn 5.11.2.2: You've added text to the rate-limit bullet about
    whether to use svc-input-bandwidth or svc-output-bandwidth - same
    text also needs to be added to the bullet for guaranteed-bw-percent.
  * Sn 8: I don't think an identity is needed for non-diverse - with the
    new system, that can be achieved simply by not adding any constraints.

Thanks,

     David


On 06/06/2016 15:19, stephane.litkowski@orange.com wrote:
> Hi L3SM,
>
> Here is a new revision of the service model.
> It contains a new way for modeling the site-network-access placement.
> Also some fixes thanks to comment of the WG.
> It contains also some first text on NNI modeling. I putted for the moment option B and option C out of scope, but this is still a point to be discussed. At least it describes what we think necessary to be modeled for those cases.
>
> Feel free to comment it.
>
> Best Regards,
>
> Stephane
>
>
> -----Original Message-----
> From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
> Sent: Monday, June 06, 2016 16:17
> To: i-d-announce@ietf.org
> Cc: l3sm@ietf.org
> Subject: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.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  of the IETF.
>
>          Title           : YANG Data Model for L3VPN service delivery
>          Authors         : Stephane Litkowski
>                            Rob Shakir
>                            Luis Tomotaki
>                            Kenichi Ogaki
>                            Kevin D'Souza
> 	Filename        : draft-ietf-l3sm-l3vpn-service-model-07.txt
> 	Pages           : 153
> 	Date            : 2016-06-06
>
> Abstract:
>     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:
> https://datatracker.ietf.org/doc/draft-ietf-l3sm-l3vpn-service-model/
>
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-l3sm-l3vpn-service-model-07
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-l3sm-l3vpn-service-model-07
>
>
> Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> L3sm mailing list
> L3sm@ietf.org
> https://www.ietf.org/mailman/listinfo/l3sm
>
> _________________________________________________________________________________________________________________________
>
> 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
> L3sm@ietf.org
> https://www.ietf.org/mailman/listinfo/l3sm

-- 
David Ball
<daviball@cisco.com>


--------------7ED929BD5816F2C04A916FC3
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>Hi Stephane,</p>
    <p>Thanks for posting the new version, here are a few additional
      comments:</p>
    <ul>
      <li>I agree with Michael that config:false items should not appear
        in the templates - and more broadly, that templates are not an
        L3SM-specific concept.  I might be better to punt this to the
        netmod WG to create a generic templating mechanism for yang,
        rather than trying to solve it in L3SM.</li>
      <li>Sn 5.1.1.4: you added a sentence saying "Hub and spoke
        disjoint can also be seen as two hub and spoke VPNs sharing with
        a common hub site." - actually it's the spokes that are common
        not the hub, right?  So it should say "... sharing a common set
        of spoke sites."</li>
      <li>Sn 5.4.1: I think with your new diversity constraints, the
        SubVPN flavor is no longer needed, right?  You could model it as
        separate sites, with accesses in the same group and with a
        "same-bearer" constraint on that group, right?  So Sn 5.4.1.3
        could be deleted, along with the site-vpn-flavor-sub identity in
        the model.<br>
      </li>
      <li>Sn 5.5.3: I think the intent here is that the constraint
        applies to <b>other</b> site-network-accesses in the targeted
        group.  If the site-network-access for which the constraint is
        set is also part of the target group, the constraint does not
        apply to itself (e.g. in the first example where all 5
        site-network-accesses are in group 10, the site-network-access
        in SITE1 does not need to be pe-diverse with itself - that
        wouldn't make any sense).  So, I think the word "other" needs to
        be inserted in several places.</li>
      <li>Sn 5.5.3: Need to describe what the behaviour is if
        conflicting constraints are configured.  The simplest example
        would be 2 site-network accesses in the same group, where one
        has a "pe-diverse" constraint targeted at that group, and the
        other has a "same-pe" constraint targeted at that group.  To
        meet both constraints, the SP has to connect the
        site-network-accesses to the same PE and also to different PEs,
        which is clearly impossible.  Of course there are lots of more
        complex ways of creating conflicting requirements, so I think we
        need to say what happens in this case.<br>
      </li>
      <li>Sn 5.5.4.2: I can't parse the second paragraph  - I think it
        should say: "... 3 branch offices can be connected to the same
        PE but not on the same linecard."</li>
      <li>Sn 5.5.4.2: Second bullet after the figure, should say
        "pop-diverse" not "pe-diverse".</li>
      <li>Sn 5.7: Traffic Protection should be a per-site attribute - it
        makes no sense to enable protection on one network-access for a
        site and disable it on another; it needs to be either enabled on
        all network-accesses for a given site, or on none of them, i.e.
        at a service level it is a per-site attribute.</li>
      <li>Sn 5.9: If the CE is provider-managed, why is a management
        address needed in the model?  How the provider connects to the
        device would be internal to the provider, right?<br>
        (For co-managed I can see this could be needed, i.e. to tell the
        customer what address to use to connect to the device for
        configuration/monitoring)</li>
      <li>Sn 5.10.2: You said before that the model can only manage P2P
        connections; but this figure (and the next one) show the PE
        connected to a LAN, not to a CE.  I am not sure how to interpret
        this?  Isn't this a case where the connection is multipoint, not
        P2P?</li>
      <li>Sn 5.11.2.2: I don't understand what it means to say that the
        QoS profile will be implemented at the PE or CE side of the WAN
        link.  This is a service model, it should not specify how the SP
        implements their network.  It is still unclear to me whether the
        QoS profile is supposed to apply to traffic flowing from the SP
        to the customer or from the customer to the SP - please can you
        clarify this?</li>
      <li>Sn 5.11.2.2: You've added text to the rate-limit bullet about
        whether to use svc-input-bandwidth or svc-output-bandwidth -
        same text also needs to be added to the bullet for
        guaranteed-bw-percent.</li>
      <li>Sn 8: I don't think an identity is needed for non-diverse -
        with the new system, that can be achieved simply by not adding
        any constraints.</li>
    </ul>
    <p>Thanks,</p>
    <p>    David<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 06/06/2016 15:19,
      <a class="moz-txt-link-abbreviated" href="mailto:stephane.litkowski@orange.com">stephane.litkowski@orange.com</a> wrote:<br>
    </div>
    <blockquote
cite="mid:27218_1465222795_5755868B_27218_684_1_9E32478DFA9976438E7A22F69B08FF921BC41DA1@OPEXCLILMA4.corporate.adroot.infra.ftgroup"
      type="cite">
      <pre wrap="">Hi L3SM,

Here is a new revision of the service model.
It contains a new way for modeling the site-network-access placement.
Also some fixes thanks to comment of the WG.
It contains also some first text on NNI modeling. I putted for the moment option B and option C out of scope, but this is still a point to be discussed. At least it describes what we think necessary to be modeled for those cases.

Feel free to comment it.

Best Regards,

Stephane


-----Original Message-----
From: L3sm [<a class="moz-txt-link-freetext" href="mailto:l3sm-bounces@ietf.org">mailto:l3sm-bounces@ietf.org</a>] On Behalf Of <a class="moz-txt-link-abbreviated" href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a>
Sent: Monday, June 06, 2016 16:17
To: <a class="moz-txt-link-abbreviated" href="mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a>
Cc: <a class="moz-txt-link-abbreviated" href="mailto:l3sm@ietf.org">l3sm@ietf.org</a>
Subject: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.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  of the IETF.

        Title           : YANG Data Model for L3VPN service delivery
        Authors         : Stephane Litkowski
                          Rob Shakir
                          Luis Tomotaki
                          Kenichi Ogaki
                          Kevin D'Souza
	Filename        : draft-ietf-l3sm-l3vpn-service-model-07.txt
	Pages           : 153
	Date            : 2016-06-06

Abstract:
   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:
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-l3sm-l3vpn-service-model/">https://datatracker.ietf.org/doc/draft-ietf-l3sm-l3vpn-service-model/</a>

There's also a htmlized version available at:
<a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-ietf-l3sm-l3vpn-service-model-07">https://tools.ietf.org/html/draft-ietf-l3sm-l3vpn-service-model-07</a>

A diff from the previous version is available at:
<a class="moz-txt-link-freetext" href="https://www.ietf.org/rfcdiff?url2=draft-ietf-l3sm-l3vpn-service-model-07">https://www.ietf.org/rfcdiff?url2=draft-ietf-l3sm-l3vpn-service-model-07</a>


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

Internet-Drafts are also available by anonymous FTP at:
<a class="moz-txt-link-freetext" href="ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf.org/internet-drafts/</a>

_______________________________________________
L3sm mailing list
<a class="moz-txt-link-abbreviated" href="mailto:L3sm@ietf.org">L3sm@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/l3sm">https://www.ietf.org/mailman/listinfo/l3sm</a>

_________________________________________________________________________________________________________________________

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
<a class="moz-txt-link-abbreviated" href="mailto:L3sm@ietf.org">L3sm@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/l3sm">https://www.ietf.org/mailman/listinfo/l3sm</a>
</pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
David Ball
<a class="moz-txt-link-rfc2396E" href="mailto:daviball@cisco.com">&lt;daviball@cisco.com&gt;</a></pre>
  </body>
</html>

--------------7ED929BD5816F2C04A916FC3--


From nobody Wed Jun  8 02:45:03 2016
Return-Path: <stephane.litkowski@orange.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 7389E12D8AB for <l3sm@ietfa.amsl.com>; Wed,  8 Jun 2016 02:45:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.334
X-Spam-Level: 
X-Spam-Status: No, score=-3.334 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, UNPARSEABLE_RELAY=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 hEgn8dF1FVu6 for <l3sm@ietfa.amsl.com>; Wed,  8 Jun 2016 02:44:56 -0700 (PDT)
Received: from relais-inet.orange.com (relais-nor35.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 357E112D8B1 for <l3sm@ietf.org>; Wed,  8 Jun 2016 02:44:56 -0700 (PDT)
Received: from opfednr05.francetelecom.fr (unknown [xx.xx.xx.69]) by opfednr25.francetelecom.fr (ESMTP service) with ESMTP id D25551803F2; Wed,  8 Jun 2016 11:44:54 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.17]) by opfednr05.francetelecom.fr (ESMTP service) with ESMTP id 9B9D9200CD; Wed,  8 Jun 2016 11:44:54 +0200 (CEST)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM24.corporate.adroot.infra.ftgroup ([fe80::a1e6:3e6a:1f68:5f7e%19]) with mapi id 14.03.0294.000; Wed, 8 Jun 2016 11:44:54 +0200
From: <stephane.litkowski@orange.com>
To: David Ball <daviball@cisco.com>, "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
Thread-Index: AQHRv/4i8iSSM4mtWE6AeESR5nwEZZ/cfFGwgAGg6gCAASznEA==
Date: Wed, 8 Jun 2016 09:44:54 +0000
Message-ID: <32265_1465379094_5757E916_32265_10098_3_9E32478DFA9976438E7A22F69B08FF921BC454AB@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <20160606141710.20806.10098.idtracker@ietfa.amsl.com> <27218_1465222795_5755868B_27218_684_1_9E32478DFA9976438E7A22F69B08FF921BC41DA1@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <ec72f8b8-8626-ba2c-bc50-7ce4a0cdc6df@cisco.com>
In-Reply-To: <ec72f8b8-8626-ba2c-bc50-7ce4a0cdc6df@cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
Content-Type: multipart/alternative; boundary="_000_9E32478DFA9976438E7A22F69B08FF921BC454ABOPEXCLILMA4corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/eb5dz9Xsk2Qb8HtOwgJNg1k107o>
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
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: Wed, 08 Jun 2016 09:45:00 -0000

--_000_9E32478DFA9976438E7A22F69B08FF921BC454ABOPEXCLILMA4corp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

Pls find some comments/replies inline

Best Regards,

Stephane

From: David Ball [mailto:daviball@cisco.com]
Sent: Tuesday, June 07, 2016 19:10
To: LITKOWSKI Stephane OBS/OINIS; l3sm@ietf.org
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt


Hi Stephane,

Thanks for posting the new version, here are a few additional comments:

  *   I agree with Michael that config:false items should not appear in the=
 templates - and more broadly, that templates are not an L3SM-specific conc=
ept.  I might be better to punt this to the netmod WG to create a generic t=
emplating mechanism for yang, rather than trying to solve it in L3SM.
[SLI] Yes, I agree that it would be the best approach. If everyone agree, w=
e can remove the templates.
The config:false items come from the grouping I'm reusing, I need to explod=
e the grouping in order to remove them or put the op-states out.


  *   Sn 5.1.1.4: you added a sentence saying "Hub and spoke disjoint can a=
lso be seen as two hub and spoke VPNs sharing with a common hub site." - ac=
tually it's the spokes that are common not the hub, right?  So it should sa=
y "... sharing a common set of spoke sites."
[SLI] Right ! thanks for the catch

  *   Sn 5.4.1: I think with your new diversity constraints, the SubVPN fla=
vor is no longer needed, right?  You could model it as separate sites, with=
 accesses in the same group and with a "same-bearer" constraint on that gro=
up, right?  So Sn 5.4.1.3 could be deleted, along with the site-vpn-flavor-=
sub identity in the model.
[SLI] From a constraint perspective yes, now from a service point of view, =
it is still interesting to keep the information of the VPN style the custom=
er wants. Some SP may enforce some parameters based on this information.


  *   Sn 5.5.3: I think the intent here is that the constraint applies to o=
ther site-network-accesses in the targeted group.  If the site-network-acce=
ss for which the constraint is set is also part of the target group, the co=
nstraint does not apply to itself (e.g. in the first example where all 5 si=
te-network-accesses are in group 10, the site-network-access in SITE1 does =
not need to be pe-diverse with itself - that wouldn't make any sense).  So,=
 I think the word "other" needs to be inserted in several places.
[SLI] As mentioned by the text the constraint is expressed as : "I want my =
current site-network-
   access to be <constraint-type> (e.g. pe-diverse, pop-diverse) from
   those <target> site-network-accesses."
This means that if the current configured site-network-access is part of gr=
oup 10 and the constraint is targeting group 10, the current site is not ta=
king into account as part as group 10 because it is not placed yet in the n=
etwork.
I can change the text as follows :
"For a particular currently configured site-network-access , each constrain=
t MUST be
   expressed against a targeted set of site-network-accesses, the currently=
 configured site-network-access MUST never be taken into account in the tar=
geted set  : e.g.  "I want my
   current site-network-access to be not be connected on the same PoP as
   the site-network-accesses (other than the current one) that are part of =
group 10".
"


  *   Sn 5.5.3: Need to describe what the behaviour is if conflicting const=
raints are configured.  The simplest example would be 2 site-network access=
es in the same group, where one has a "pe-diverse" constraint targeted at t=
hat group, and the other has a "same-pe" constraint targeted at that group.=
  To meet both constraints, the SP has to connect the site-network-accesses=
 to the same PE and also to different PEs, which is clearly impossible.  Of=
 course there are lots of more complex ways of creating conflicting require=
ments, so I think we need to say what happens in this case.
[SLI] When conflicting rules are configured, no solution can be found, it i=
s expected to return an error in such case. I 'm adding a new small section=
 to talk about impossible placement :
"<t>
                                                Some impossible placement s=
cenarios may be created through the proposed configuration framework. Impos=
sible scenarios could be too restrictive constraints leading to impossible =
placement in the network or conflicting constraints that would also lead to=
 impossible placement.
                                                An example of conflicting r=
ules would be to ask a site-network-access#1 to be pe-diverse from a site-n=
etwork-access#2 and to ask at the same time that site-network-access#2 to b=
e on the same PE as site-network-access#1.
                                                When the management system =
cannot place the access, it SHOULD return an error message indicating that =
placement was not possible.
                                                </t>
"

  *   Sn 5.5.4.2: I can't parse the second paragraph  - I think it should s=
ay: "... 3 branch offices can be connected to the same PE but not on the sa=
me linecard."
[SLI] Implementing "linecard-diverse" does not mean that you want to be on =
the same PE. It means that the system MUST avoid to connect the sites on th=
e same LC, the solution can be to use the same PE with another LC, or anoth=
er PE also.

  *   Sn 5.5.4.2: Second bullet after the figure, should say "pop-diverse" =
not "pe-diverse".
[SLI] Right

  *   Sn 5.7: Traffic Protection should be a per-site attribute - it makes =
no sense to enable protection on one network-access for a site and disable =
it on another; it needs to be either enabled on all network-accesses for a =
given site, or on none of them, i.e. at a service level it is a per-site at=
tribute.
[SLI] Agree

  *   Sn 5.9: If the CE is provider-managed, why is a management address ne=
eded in the model?  How the provider connects to the device would be intern=
al to the provider, right?
(For co-managed I can see this could be needed, i.e. to tell the customer w=
hat address to use to connect to the device for configuration/monitoring)
[SLI] There is a mistake here. You must read "In case of "customer-managed"=
 or "co-managed", the model proposes ..."

  *   Sn 5.10.2: You said before that the model can only manage P2P connect=
ions; but this figure (and the next one) show the PE connected to a LAN, no=
t to a CE.  I am not sure how to interpret this?  Isn't this a case where t=
he connection is multipoint, not P2P?
[SLI] That's still point to point. In 5.10.3, customer must order two site =
network accesses (point to point). Each site network network access may be =
connected to a switch at customer side (same one or not).

  *   Sn 5.11.2.2: I don't understand what it means to say that the QoS pro=
file will be implemented at the PE or CE side of the WAN link.  This is a s=
ervice model, it should not specify how the SP implements their network.  I=
t is still unclear to me whether the QoS profile is supposed to apply to tr=
affic flowing from the SP to the customer or from the customer to the SP - =
please can you clarify this?
[SLI] Agree, that just a hint on what can be done. I will rephrase it to hi=
ghlight this is just an example. Qos-profile is a scheduling policy, it wil=
l affect both traffic sides in case of provider managed and SP to customer =
only in case of customer managed.


  *   Sn 5.11.2.2: You've added text to the rate-limit bullet about whether=
 to use svc-input-bandwidth or svc-output-bandwidth - same text also needs =
to be added to the bullet for guaranteed-bw-percent.
[SLI] Ok

  *   Sn 8: I don't think an identity is needed for non-diverse - with the =
new system, that can be achieved simply by not adding any constraints.
[SLI] I thought I already removed it, it's done now


Thanks,

    David

On 06/06/2016 15:19, stephane.litkowski@orange.com<mailto:stephane.litkowsk=
i@orange.com> wrote:

Hi L3SM,



Here is a new revision of the service model.

It contains a new way for modeling the site-network-access placement.

Also some fixes thanks to comment of the WG.

It contains also some first text on NNI modeling. I putted for the moment o=
ption B and option C out of scope, but this is still a point to be discusse=
d. At least it describes what we think necessary to be modeled for those ca=
ses.



Feel free to comment it.



Best Regards,



Stephane





-----Original Message-----

From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of internet-drafts@ietf=
.org<mailto:internet-drafts@ietf.org>

Sent: Monday, June 06, 2016 16:17

To: i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>

Cc: l3sm@ietf.org<mailto:l3sm@ietf.org>

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





A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.

This draft is a work item of the L3VPN Service Model  of the IETF.



        Title           : YANG Data Model for L3VPN service delivery

        Authors         : Stephane Litkowski

                          Rob Shakir

                          Luis Tomotaki

                          Kenichi Ogaki

                          Kevin D'Souza

  Filename        : draft-ietf-l3sm-l3vpn-service-model-07.txt

  Pages           : 153

  Date            : 2016-06-06



Abstract:

   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:

https://datatracker.ietf.org/doc/draft-ietf-l3sm-l3vpn-service-model/



There's also a htmlized version available at:

https://tools.ietf.org/html/draft-ietf-l3sm-l3vpn-service-model-07



A diff from the previous version is available at:

https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-l3sm-l3vpn-service-model-07





Please note that it may take a couple of minutes from the time of submissio=
n until the htmlized version and diff are available at tools.ietf.org.



Internet-Drafts are also available by anonymous FTP at:

ftp://ftp.ietf.org/internet-drafts/



_______________________________________________

L3sm mailing list

L3sm@ietf.org<mailto:L3sm@ietf.org>

https://www.ietf.org/mailman/listinfo/l3sm



___________________________________________________________________________=
______________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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

L3sm@ietf.org<mailto:L3sm@ietf.org>

https://www.ietf.org/mailman/listinfo/l3sm



--

David Ball

<daviball@cisco.com><mailto:daviball@cisco.com>

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.


--_000_9E32478DFA9976438E7A22F69B08FF921BC454ABOPEXCLILMA4corp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	color:black;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1656761572;
	mso-list-template-ids:-682878950;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=3D"white" lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Pls find some comments/re=
plies inline<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Best Regards,<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Stephane<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><spa=
n style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif=
&quot;;color:windowtext"> David Ball [mailto:daviball@cisco.com]
<br>
<b>Sent:</b> Tuesday, June 07, 2016 19:10<br>
<b>To:</b> LITKOWSKI Stephane OBS/OINIS; l3sm@ietf.org<br>
<b>Subject:</b> Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-=
07.txt<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p>Hi Stephane,<o:p></o:p></p>
<p>Thanks for posting the new version, here are a few additional comments:<=
o:p></o:p></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l0 level1 lfo1">
I agree with Michael that config:false items should not appear in the templ=
ates - and more broadly, that templates are not an L3SM-specific concept.&n=
bsp; I might be better to punt this to the netmod WG to create a generic te=
mplating mechanism for yang, rather than
 trying to solve it in L3SM.<o:p></o:p></li></ul>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">[SLI] Yes, I agree that it would be the=
 best approach. If everyone agree, we can remove the templates.<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">The config:false items come from the gr=
ouping I&#8217;m reusing, I need to explode the grouping in order
 to remove them or put the op-states out.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l0 level1 lfo1">
Sn 5.1.1.4: you added a sentence saying &quot;Hub and spoke disjoint can al=
so be seen as two hub and spoke VPNs sharing with a common hub site.&quot; =
- actually it's the spokes that are common not the hub, right?&nbsp; So it =
should say &quot;... sharing a common set of spoke sites.&quot;<o:p></o:p><=
/li></ul>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">[SLI] Right ! thanks for the catch<o:p>=
</o:p></span></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l0 level1 lfo1">
Sn 5.4.1: I think with your new diversity constraints, the SubVPN flavor is=
 no longer needed, right?&nbsp; You could model it as separate sites, with =
accesses in the same group and with a &quot;same-bearer&quot; constraint on=
 that group, right?&nbsp; So Sn 5.4.1.3 could be deleted,
 along with the site-vpn-flavor-sub identity in the model.<o:p></o:p></li><=
/ul>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">[SLI] From a constraint perspective yes=
, now from a service point of view, it is still interesting
 to keep the information of the VPN style the customer wants. Some SP may e=
nforce some parameters based on this information.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l0 level1 lfo1">
Sn 5.5.3: I think the intent here is that the constraint applies to <b>othe=
r</b> site-network-accesses in the targeted group.&nbsp; If the site-networ=
k-access for which the constraint is set is also part of the target group, =
the constraint does not apply to itself
 (e.g. in the first example where all 5 site-network-accesses are in group =
10, the site-network-access in SITE1 does not need to be pe-diverse with it=
self - that wouldn't make any sense).&nbsp; So, I think the word &quot;othe=
r&quot; needs to be inserted in several places.<o:p></o:p></li></ul>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">[SLI] As mentioned by the text the cons=
traint is expressed as : &quot;I want my current site-network-<o:p></o:p></=
span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp; access to be &lt;constrain=
t-type&gt; (e.g. pe-diverse, pop-diverse) from<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp; those &lt;target&gt; site-=
network-accesses.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">This means that if the current configur=
ed site-network-access is part of group 10 and the constraint
 is targeting group 10, the current site is not taking into account as part=
 as group 10 because it is not placed yet in the network.<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">I can change the text as follows :<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&#8220;For a particular currently confi=
gured site-network-access , each constraint MUST be<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp; expressed against a target=
ed set of site-network-accesses, the currently configured site-network-acce=
ss
 MUST never be taken into account in the targeted set &nbsp;: e.g.&nbsp; &q=
uot;I want my<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp; current site-network-acces=
s to be not be connected on the same PoP as<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp; the site-network-accesses =
(other than the current one) that are part of group 10&quot;.<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&#8220;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l0 level1 lfo1">
Sn 5.5.3: Need to describe what the behaviour is if conflicting constraints=
 are configured.&nbsp; The simplest example would be 2 site-network accesse=
s in the same group, where one has a &quot;pe-diverse&quot; constraint targ=
eted at that group, and the other has a &quot;same-pe&quot;
 constraint targeted at that group.&nbsp; To meet both constraints, the SP =
has to connect the site-network-accesses to the same PE and also to differe=
nt PEs, which is clearly impossible.&nbsp; Of course there are lots of more=
 complex ways of creating conflicting requirements,
 so I think we need to say what happens in this case.<o:p></o:p></li></ul>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">[SLI] When conflicting rules are config=
ured, no solution can be found, it is expected to return an
 error in such case. I &#8216;m adding a new small section to talk about im=
possible placement :<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&#8220;&lt;t&gt;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; Some impossible placement scenarios may be created
 through the proposed configuration framework. Impossible scenarios could b=
e too restrictive constraints leading to impossible placement in the networ=
k or conflicting constraints that would also lead to impossible placement.<=
o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; An example of conflicting rules would be to ask a
 site-network-access#1 to be pe-diverse from a site-network-access#2 and to=
 ask at the same time that site-network-access#2 to be on the same PE as si=
te-network-access#1.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; When the management system cannot place the access,
 it SHOULD return an error message indicating that placement was not possib=
le.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; &lt;/t&gt;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&#8220;<o:p></o:p></span></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l0 level1 lfo1">
Sn 5.5.4.2: I can't parse the second paragraph&nbsp; - I think it should sa=
y: &quot;... 3 branch offices can be connected to the same PE but not on th=
e same linecard.&quot;<o:p></o:p></li></ul>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">[SLI] Implementing &#8220;linecard-dive=
rse&#8221; does not mean that you want to be on the same PE. It means
 that the system MUST avoid to connect the sites on the same LC, the soluti=
on can be to use the same PE with another LC, or another PE also.<o:p></o:p=
></span></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l0 level1 lfo1">
Sn 5.5.4.2: Second bullet after the figure, should say &quot;pop-diverse&qu=
ot; not &quot;pe-diverse&quot;.<o:p></o:p></li></ul>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">[SLI] Right<o:p></o:p></span></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l0 level1 lfo1">
Sn 5.7: Traffic Protection should be a per-site attribute - it makes no sen=
se to enable protection on one network-access for a site and disable it on =
another; it needs to be either enabled on all network-accesses for a given =
site, or on none of them, i.e. at
 a service level it is a per-site attribute.<o:p></o:p></li></ul>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">[SLI] Agree<o:p></o:p></span></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l0 level1 lfo1">
Sn 5.9: If the CE is provider-managed, why is a management address needed i=
n the model?&nbsp; How the provider connects to the device would be interna=
l to the provider, right?<br>
(For co-managed I can see this could be needed, i.e. to tell the customer w=
hat address to use to connect to the device for configuration/monitoring)<o=
:p></o:p></li></ul>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">[SLI] There is a mistake here. You must=
 read &#8220;In case of &#8220;customer-managed&#8221; or &#8220;co-managed=
&#8221;, the
 model proposes &#8230;&#8221;<o:p></o:p></span></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l0 level1 lfo1">
Sn 5.10.2: You said before that the model can only manage P2P connections; =
but this figure (and the next one) show the PE connected to a LAN, not to a=
 CE.&nbsp; I am not sure how to interpret this?&nbsp; Isn't this a case whe=
re the connection is multipoint, not P2P?<o:p></o:p></li></ul>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">[SLI] That&#8217;s still point to point=
. In 5.10.3, customer must order two site network accesses (point
 to point). Each site network network access may be connected to a switch a=
t customer side (same one or not).<o:p></o:p></span></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l0 level1 lfo1">
Sn 5.11.2.2: I don't understand what it means to say that the QoS profile w=
ill be implemented at the PE or CE side of the WAN link.&nbsp; This is a se=
rvice model, it should not specify how the SP implements their network.&nbs=
p; It is still unclear to me whether the QoS
 profile is supposed to apply to traffic flowing from the SP to the custome=
r or from the customer to the SP - please can you clarify this?<o:p></o:p><=
/li></ul>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">[SLI] Agree, that just a hint on what c=
an be done. I will rephrase it to highlight this is just an
 example. Qos-profile is a scheduling policy, it will affect both traffic s=
ides in case of provider managed and SP to customer only in case of custome=
r managed.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l0 level1 lfo1">
Sn 5.11.2.2: You've added text to the rate-limit bullet about whether to us=
e svc-input-bandwidth or svc-output-bandwidth - same text also needs to be =
added to the bullet for guaranteed-bw-percent.<o:p></o:p></li></ul>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">[SLI] Ok<o:p></o:p></span></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"color:#1F497D;mso-margin-top-alt:auto;mso-=
margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style=3D"color:black">Sn 8: I don't think an identity is needed for n=
on-diverse - with the new system, that can be achieved simply by not adding=
 any constraints.</span><o:p></o:p></li></ul>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;margin-left:.5in">
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1F497D">[SLI] I thought I already removed it, it&#8217;s=
 done now</span><span style=3D"color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p>Thanks,<o:p></o:p></p>
<p>&nbsp;&nbsp;&nbsp; David<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On 06/06/2016 15:19, <a href=3D"mailto:stephane.litk=
owski@orange.com">
stephane.litkowski@orange.com</a> wrote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Hi L3SM,<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Here is a new revision of the service model.<o:p></o:p></pre>
<pre>It contains a new way for modeling the site-network-access placement.<=
o:p></o:p></pre>
<pre>Also some fixes thanks to comment of the WG.<o:p></o:p></pre>
<pre>It contains also some first text on NNI modeling. I putted for the mom=
ent option B and option C out of scope, but this is still a point to be dis=
cussed. At least it describes what we think necessary to be modeled for tho=
se cases.<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Feel free to comment it.<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Best Regards,<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Stephane<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>-----Original Message-----<o:p></o:p></pre>
<pre>From: L3sm [<a href=3D"mailto:l3sm-bounces@ietf.org">mailto:l3sm-bounc=
es@ietf.org</a>] On Behalf Of <a href=3D"mailto:internet-drafts@ietf.org">i=
nternet-drafts@ietf.org</a><o:p></o:p></pre>
<pre>Sent: Monday, June 06, 2016 16:17<o:p></o:p></pre>
<pre>To: <a href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a>=
<o:p></o:p></pre>
<pre>Cc: <a href=3D"mailto:l3sm@ietf.org">l3sm@ietf.org</a><o:p></o:p></pre>
<pre>Subject: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt=
<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>A New Internet-Draft is available from the on-line Internet-Drafts dir=
ectories.<o:p></o:p></pre>
<pre>This draft is a work item of the L3VPN Service Model&nbsp; of the IETF=
.<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Title&nbsp; &nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: YANG Data Model for L3VPN service =
delivery<o:p></o:p></pre>
<pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Authors&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; : Stephane Litkowski<o:p></o:p></pre>
<pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; Rob Shakir<o:p></o:p></pre>
<pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; Luis Tomotaki<o:p></o:p></pre>
<pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; Kenichi Ogaki<o:p></o:p></pre>
<pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; Kevin D'Souza<o:p></o:p></pre>
<pre>&nbsp; Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : draft-ietf=
-l3sm-l3vpn-service-model-07.txt<o:p></o:p></pre>
<pre>&nbsp; Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; : 153<o:p></o:p></pre>
<pre>&nbsp; Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; : 2016-06-06<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Abstract:<o:p></o:p></pre>
<pre>&nbsp;&nbsp; This document defines a YANG data model that can be used =
to deliver a<o:p></o:p></pre>
<pre>&nbsp;&nbsp; Layer 3 Provider Provisioned VPN service.&nbsp; The docum=
ent is limited to<o:p></o:p></pre>
<pre>&nbsp;&nbsp; the BGP PE-based VPNs as described in RFC4110 and RFC4364=
.&nbsp; This<o:p></o:p></pre>
<pre>&nbsp;&nbsp; model is intended to be instantiated at management system=
 to deliver<o:p></o:p></pre>
<pre>&nbsp;&nbsp; the overall service.&nbsp; This model is not a configurat=
ion model to be<o:p></o:p></pre>
<pre>&nbsp;&nbsp; used directly on network elements.&nbsp; This model provi=
des an abstracted<o:p></o:p></pre>
<pre>&nbsp;&nbsp; view of the Layer 3 IPVPN service configuration component=
s.&nbsp; It will<o:p></o:p></pre>
<pre>&nbsp;&nbsp; be up to a management system to take this as an input and=
 use<o:p></o:p></pre>
<pre>&nbsp;&nbsp; specific configurations models to configure the different=
 network<o:p></o:p></pre>
<pre>&nbsp;&nbsp; elements to deliver the service.&nbsp; How configuration =
of network<o:p></o:p></pre>
<pre>&nbsp;&nbsp; elements is done is out of scope of the document.<o:p></o=
:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>The IETF datatracker status page for this draft is:<o:p></o:p></pre>
<pre><a href=3D"https://datatracker.ietf.org/doc/draft-ietf-l3sm-l3vpn-serv=
ice-model/">https://datatracker.ietf.org/doc/draft-ietf-l3sm-l3vpn-service-=
model/</a><o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>There's also a htmlized version available at:<o:p></o:p></pre>
<pre><a href=3D"https://tools.ietf.org/html/draft-ietf-l3sm-l3vpn-service-m=
odel-07">https://tools.ietf.org/html/draft-ietf-l3sm-l3vpn-service-model-07=
</a><o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>A diff from the previous version is available at:<o:p></o:p></pre>
<pre><a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-l3sm-l3vpn-s=
ervice-model-07">https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-l3sm-l3vpn-=
service-model-07</a><o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Please note that it may take a couple of minutes from the time of subm=
ission until the htmlized version and diff are available at tools.ietf.org.=
<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Internet-Drafts are also available by anonymous FTP at:<o:p></o:p></pr=
e>
<pre><a href=3D"ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf.org/int=
ernet-drafts/</a><o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>L3sm mailing list<o:p></o:p></pre>
<pre><a href=3D"mailto:L3sm@ietf.org">L3sm@ietf.org</a><o:p></o:p></pre>
<pre><a href=3D"https://www.ietf.org/mailman/listinfo/l3sm">https://www.iet=
f.org/mailman/listinfo/l3sm</a><o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>______________________________________________________________________=
___________________________________________________<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Ce message et ses pieces jointes peuvent contenir des informations con=
fidentielles ou privilegiees et ne doivent donc<o:p></o:p></pre>
<pre>pas etre diffuses, exploites ou copies sans autorisation. Si vous avez=
 recu ce message par erreur, veuillez le signaler<o:p></o:p></pre>
<pre>a l'expediteur et le detruire ainsi que les pieces jointes. Les messag=
es electroniques etant susceptibles d'alteration,<o:p></o:p></pre>
<pre>Orange decline toute responsabilite si ce message a ete altere, deform=
e ou falsifie. Merci.<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>This message and its attachments may contain confidential or privilege=
d information that may be protected by law;<o:p></o:p></pre>
<pre>they should not be distributed, used or copied without authorisation.<=
o:p></o:p></pre>
<pre>If you have received this email in error, please notify the sender and=
 delete this message and its attachments.<o:p></o:p></pre>
<pre>As emails may be altered, Orange is not liable for messages that have =
been modified, changed or falsified.<o:p></o:p></pre>
<pre>Thank you.<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>L3sm mailing list<o:p></o:p></pre>
<pre><a href=3D"mailto:L3sm@ietf.org">L3sm@ietf.org</a><o:p></o:p></pre>
<pre><a href=3D"https://www.ietf.org/mailman/listinfo/l3sm">https://www.iet=
f.org/mailman/listinfo/l3sm</a><o:p></o:p></pre>
</blockquote>
<p class=3D"MsoNormal"><br>
<br>
<o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre>David Ball<o:p></o:p></pre>
<pre><a href=3D"mailto:daviball@cisco.com">&lt;daviball@cisco.com&gt;</a><o=
:p></o:p></pre>
</div>
<PRE>______________________________________________________________________=
___________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.
</PRE></body>
</html>

--_000_9E32478DFA9976438E7A22F69B08FF921BC454ABOPEXCLILMA4corp_--


From nobody Wed Jun  8 06:42:37 2016
Return-Path: <stephane.litkowski@orange.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 E364212D5C2 for <l3sm@ietfa.amsl.com>; Wed,  8 Jun 2016 06:42:35 -0700 (PDT)
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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 3cSV2OjIwqFR for <l3sm@ietfa.amsl.com>; Wed,  8 Jun 2016 06:42:34 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E98F12D0C9 for <l3sm@ietf.org>; Wed,  8 Jun 2016 06:42:34 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id A3E9618C2D1; Wed,  8 Jun 2016 15:42:32 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.2]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id 7E85F35C091; Wed,  8 Jun 2016 15:42:32 +0200 (CEST)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06%19]) with mapi id 14.03.0294.000; Wed, 8 Jun 2016 15:42:32 +0200
From: <stephane.litkowski@orange.com>
To: "Scharf, Michael (Nokia - DE)" <michael.scharf@nokia.com>, "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: Ops state in templates?
Thread-Index: AQHRwKOKR0JofdVIZkyADD+doOpm65/flPsg
Date: Wed, 8 Jun 2016 13:42:31 +0000
Message-ID: <2211_1465393352_575820C8_2211_6527_1_9E32478DFA9976438E7A22F69B08FF921BC4667D@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <655C07320163294895BBADA28372AF5D4887B657@FR712WXCHMBA15.zeu.alcatel-lucent.com> <14583_1464773427_574EAB33_14583_3223_1_9E32478DFA9976438E7A22F69B08FF921BC3B97E@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <655C07320163294895BBADA28372AF5D488BABA8@FR712WXCHMBA15.zeu.alcatel-lucent.com>
In-Reply-To: <655C07320163294895BBADA28372AF5D488BABA8@FR712WXCHMBA15.zeu.alcatel-lucent.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.6.8.132415
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/d1raxqew3Yc6U09G4nYlwB3XlbA>
Subject: Re: [L3sm] Ops state in templates?
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: Wed, 08 Jun 2016 13:42:36 -0000

Hi Michael

Pls find some inline comments.

Best Regards,


-----Original Message-----
From: Scharf, Michael (Nokia - DE) [mailto:michael.scharf@nokia.com]=20
Sent: Tuesday, June 07, 2016 12:01
To: LITKOWSKI Stephane OBS/OINIS; l3sm@ietf.org
Subject: Ops state in templates?

Hi Stephane,

I see that this has been fixed in -07. Thanks. However, is ops state indeed=
 useful in the subtree "site-templates"?

The more fundamental question is whether the template mechanism may require=
 some further thinking. For instance:

* According to Section 5.15, "If a site has some particular parameters, spe=
cific parameters within the site MUST always override parameters derived fr=
om template." Now, what happens if the template defines a list (e.g., "casc=
aded-lan-prefixes")? If a requester would want to add something to a pre-de=
fined list, does this mean that first the template list entries have to be =
read, then list entries have to be added by the requester, and then the mer=
ged list has to be used in the service request?
[SLI] As override is needed, I would say that the list in the template will=
 not be used and the local list will be.


* Another example that comes into my mind is the error handling if a site c=
annot be added, because some parameter in the template cannot be deployed. =
Is this a problem of the service request or of the template?
[SLI] Yes, but it's inherent to any template use case, it's not specific to=
 this service model.


At first sight, this sort of question may be quite independent of the model=
ing of a L3VPN. It seems to me that templates may have some implications on=
 a system implementing the YANG model.=20
[SLI] I agree that defining templates at YANG level would be helpful. Do yo=
u think we should remove the template in L3VPN SM ?


Thanks

Michael



-----Original Message-----
From: stephane.litkowski@orange.com [mailto:stephane.litkowski@orange.com]=
=20
Sent: Wednesday, June 01, 2016 11:30 AM
To: Scharf, Michael (Nokia - DE); l3sm@ietf.org
Subject: RE: actual-site-start / actual-site-stop

Hi Michael,

This is a mistake, these are ops state that needs to be config false.

Thanks for the catch.


-----Original Message-----
From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of Scharf, Michael (Nok=
ia - DE)
Sent: Wednesday, June 01, 2016 11:25
To: l3sm@ietf.org
Subject: [L3sm] actual-site-start / actual-site-stop

Hi,

Is "actual-site-start" and "actual-site-stop" indeed meant to tagged by "co=
nfig true"?

If so, what is the expected behavior if this is set, either directly or by =
template?

Thanks

Michael

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

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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. Le=
s messages electroniques etant susceptibles d'alteration, Orange decline to=
ute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation 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 dele=
te 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.


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.


From nobody Wed Jun  8 07:45:58 2016
Return-Path: <michael.scharf@nokia.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 736FA12D8BB for <l3sm@ietfa.amsl.com>; Wed,  8 Jun 2016 07:45:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-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 j1GsD3YFUOsz for <l3sm@ietfa.amsl.com>; Wed,  8 Jun 2016 07:45:54 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA2F912B077 for <l3sm@ietf.org>; Wed,  8 Jun 2016 07:45:53 -0700 (PDT)
Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id D184ECE974BAE; Wed,  8 Jun 2016 14:45:47 +0000 (GMT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (fr712usmtp2.zeu.alcatel-lucent.com [135.239.2.42]) by fr712umx4.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u58Ejpqj006960 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 8 Jun 2016 14:45:51 GMT
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id u58EjnMA019586 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 8 Jun 2016 16:45:50 +0200
Received: from FR712WXCHMBA15.zeu.alcatel-lucent.com ([169.254.7.34]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.03.0195.001; Wed, 8 Jun 2016 16:45:49 +0200
From: "Scharf, Michael (Nokia - DE)" <michael.scharf@nokia.com>
To: "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>, "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: Ops state in templates?
Thread-Index: AQHRwKN7PYndtzDTtESL0ZWnCcdFup/fdGeAgAAwoEA=
Date: Wed, 8 Jun 2016 14:45:49 +0000
Message-ID: <655C07320163294895BBADA28372AF5D488C4A46@FR712WXCHMBA15.zeu.alcatel-lucent.com>
References: <655C07320163294895BBADA28372AF5D4887B657@FR712WXCHMBA15.zeu.alcatel-lucent.com> <14583_1464773427_574EAB33_14583_3223_1_9E32478DFA9976438E7A22F69B08FF921BC3B97E@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <655C07320163294895BBADA28372AF5D488BABA8@FR712WXCHMBA15.zeu.alcatel-lucent.com> <2211_1465393352_575820C8_2211_6527_1_9E32478DFA9976438E7A22F69B08FF921BC4667D@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
In-Reply-To: <2211_1465393352_575820C8_2211_6527_1_9E32478DFA9976438E7A22F69B08FF921BC4667D@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.40]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/Tv2cpPYaJ8sfuk0rwAic6CQjUTw>
Subject: Re: [L3sm] Ops state in templates?
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: Wed, 08 Jun 2016 14:45:57 -0000

As I said already, I believe that the modeling of a L3VPN and the handling =
of templates are by and large orthogonal problems.

And, sure, I would prefer a generic solution for the latter, since template=
s could have a much wider applicability. But maybe that question could be r=
aised on the NETMOD list?

Michael

-----Original Message-----
From: stephane.litkowski@orange.com [mailto:stephane.litkowski@orange.com]=
=20
Sent: Wednesday, June 08, 2016 3:43 PM
To: Scharf, Michael (Nokia - DE); l3sm@ietf.org
Subject: RE: Ops state in templates?

Hi Michael

Pls find some inline comments.

Best Regards,


-----Original Message-----
From: Scharf, Michael (Nokia - DE) [mailto:michael.scharf@nokia.com]
Sent: Tuesday, June 07, 2016 12:01
To: LITKOWSKI Stephane OBS/OINIS; l3sm@ietf.org
Subject: Ops state in templates?

Hi Stephane,

I see that this has been fixed in -07. Thanks. However, is ops state indeed=
 useful in the subtree "site-templates"?

The more fundamental question is whether the template mechanism may require=
 some further thinking. For instance:

* According to Section 5.15, "If a site has some particular parameters, spe=
cific parameters within the site MUST always override parameters derived fr=
om template." Now, what happens if the template defines a list (e.g., "casc=
aded-lan-prefixes")? If a requester would want to add something to a pre-de=
fined list, does this mean that first the template list entries have to be =
read, then list entries have to be added by the requester, and then the mer=
ged list has to be used in the service request?
[SLI] As override is needed, I would say that the list in the template will=
 not be used and the local list will be.


* Another example that comes into my mind is the error handling if a site c=
annot be added, because some parameter in the template cannot be deployed. =
Is this a problem of the service request or of the template?
[SLI] Yes, but it's inherent to any template use case, it's not specific to=
 this service model.


At first sight, this sort of question may be quite independent of the model=
ing of a L3VPN. It seems to me that templates may have some implications on=
 a system implementing the YANG model.=20
[SLI] I agree that defining templates at YANG level would be helpful. Do yo=
u think we should remove the template in L3VPN SM ?


Thanks

Michael



-----Original Message-----
From: stephane.litkowski@orange.com [mailto:stephane.litkowski@orange.com]
Sent: Wednesday, June 01, 2016 11:30 AM
To: Scharf, Michael (Nokia - DE); l3sm@ietf.org
Subject: RE: actual-site-start / actual-site-stop

Hi Michael,

This is a mistake, these are ops state that needs to be config false.

Thanks for the catch.


-----Original Message-----
From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of Scharf, Michael (Nok=
ia - DE)
Sent: Wednesday, June 01, 2016 11:25
To: l3sm@ietf.org
Subject: [L3sm] actual-site-start / actual-site-stop

Hi,

Is "actual-site-start" and "actual-site-stop" indeed meant to tagged by "co=
nfig true"?

If so, what is the expected behavior if this is set, either directly or by =
template?

Thanks

Michael

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

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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. Le=
s messages electroniques etant susceptibles d'alteration, Orange decline to=
ute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation 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 dele=
te 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.


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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. Le=
s messages electroniques etant susceptibles d'alteration, Orange decline to=
ute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation 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 dele=
te 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.


From nobody Wed Jun  8 08:55:05 2016
Return-Path: <lucy.yong@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 D151812D0FD for <l3sm@ietfa.amsl.com>; Wed,  8 Jun 2016 08:55:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.636
X-Spam-Level: 
X-Spam-Status: No, score=-5.636 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=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 dus-o-BJrVBc for <l3sm@ietfa.amsl.com>; Wed,  8 Jun 2016 08:55:01 -0700 (PDT)
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 DB7DF12D93E for <l3sm@ietf.org>; Wed,  8 Jun 2016 08:54:58 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml701-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CLP37335; Wed, 08 Jun 2016 15:54:56 +0000 (GMT)
Received: from DFWEML702-CAH.china.huawei.com (10.193.5.176) by lhreml701-cah.china.huawei.com (10.201.5.93) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 8 Jun 2016 16:54:50 +0100
Received: from DFWEML501-MBB.china.huawei.com ([10.193.5.179]) by dfweml702-cah.china.huawei.com ([10.193.5.176]) with mapi id 14.03.0235.001; Wed, 8 Jun 2016 08:54:45 -0700
From: Lucy yong <lucy.yong@huawei.com>
To: "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>, "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
Thread-Index: AQHRv/4i8iSSM4mtWE6AeESR5nwEZZ/cfFGwgAM5XWA=
Date: Wed, 8 Jun 2016 15:54:44 +0000
Message-ID: <2691CE0099834E4A9C5044EEC662BB9D57296446@dfweml501-mbb>
References: <20160606141710.20806.10098.idtracker@ietfa.amsl.com> <27218_1465222795_5755868B_27218_684_1_9E32478DFA9976438E7A22F69B08FF921BC41DA1@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
In-Reply-To: <27218_1465222795_5755868B_27218_684_1_9E32478DFA9976438E7A22F69B08FF921BC41DA1@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.133.123]
Content-Type: multipart/alternative; boundary="_000_2691CE0099834E4A9C5044EEC662BB9D57296446dfweml501mbb_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020204.57583FD0.031E, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 23389c9ebb27ed3480818dde0078f00b
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/nmu9APoB_8o1wzfENZ0QevDa3fg>
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
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: Wed, 08 Jun 2016 15:55:04 -0000

--_000_2691CE0099834E4A9C5044EEC662BB9D57296446dfweml501mbb_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Stephane,



I read this version and have some comments.



*         Sn 5 states "A site is composed of at least one site-network-acce=
ss ...". In data model, site has a site-network-access container and a rout=
ing-protocols container; site-network-access also has a routing-protocols c=
ontainer. Why is the routing-protocols container needed at both? If the rou=
ting-protocols under site means to apply to all its site-network-accesses, =
suggest to state that explicitly clear under Sn 5.2 and usage role.



*         Sn 5.14 defining NNIs. It is worth to mention how that relates or=
 applies to interwork with a cloud provider. Sn 5.14.2 touches a bit in exa=
mple 1. I don't think that we need to care of a site within cloud provider,=
 but need to describe L3VPN provider and cloud provider interworking since =
L3SM supports cloud access.



*         A dummy question, which tool is used to convert the structure of =
YANG Module in Sn 5 to the YANG Module in Sn 8?

BRs/Thanks,

Lucy



-----Original Message-----
From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of stephane.litkowski@o=
range.com
Sent: Monday, June 06, 2016 9:20 AM
To: l3sm@ietf.org
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt



Hi L3SM,



Here is a new revision of the service model.

It contains a new way for modeling the site-network-access placement.

Also some fixes thanks to comment of the WG.

It contains also some first text on NNI modeling. I putted for the moment o=
ption B and option C out of scope, but this is still a point to be discusse=
d. At least it describes what we think necessary to be modeled for those ca=
ses.



Feel free to comment it.



Best Regards,



Stephane





-----Original Message-----

From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of internet-drafts@ietf=
.org<mailto:internet-drafts@ietf.org>

Sent: Monday, June 06, 2016 16:17

To: i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>

Cc: l3sm@ietf.org<mailto:l3sm@ietf.org>

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





A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.

This draft is a work item of the L3VPN Service Model  of the IETF.



        Title           : YANG Data Model for L3VPN service delivery

        Authors         : Stephane Litkowski

                          Rob Shakir

                          Luis Tomotaki

                          Kenichi Ogaki

                          Kevin D'Souza

      Filename        : draft-ietf-l3sm-l3vpn-service-model-07.txt

      Pages           : 153

      Date            : 2016-06-06



Abstract:

   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:

https://datatracker.ietf.org/doc/draft-ietf-l3sm-l3vpn-service-model/



There's also a htmlized version available at:

https://tools.ietf.org/html/draft-ietf-l3sm-l3vpn-service-model-07



A diff from the previous version is available at:

https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-l3sm-l3vpn-service-model-07





Please note that it may take a couple of minutes from the time of submissio=
n until the htmlized version and diff are available at tools.ietf.org.



Internet-Drafts are also available by anonymous FTP at:

ftp://ftp.ietf.org/internet-drafts/



_______________________________________________

L3sm mailing list

L3sm@ietf.org<mailto:L3sm@ietf.org>

https://www.ietf.org/mailman/listinfo/l3sm



___________________________________________________________________________=
______________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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. Le=
s messages electroniques etant susceptibles d'alteration, Orange decline to=
ute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged inf=
ormation 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 dele=
te 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

L3sm@ietf.org<mailto:L3sm@ietf.org>

https://www.ietf.org/mailman/listinfo/l3sm

--_000_2691CE0099834E4A9C5044EEC662BB9D57296446dfweml501mbb_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:784155387;
	mso-list-type:hybrid;
	mso-list-template-ids:-32874636 67698689 67698691 67698693 67698689 676986=
91 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">Hi Stephane,<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">I read this version and have some comments.<o:p><=
/o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in;text-indent:-.25in;mso-=
list:l0 level1 lfo1">
<![if !supportLists]><span style=3D"font-family:Symbol"><span style=3D"mso-=
list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roman&quot;"=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>Sn 5 states &#8220;A site is composed of at =
least one site-network-access &#8230;&#8221;. In data model, site has a sit=
e-network-access container and a routing-protocols container; site-network-=
access also has a routing-protocols container. Why
 is the routing-protocols container needed at both? If the routing-protocol=
s under site means to apply to all its site-network-accesses, suggest to st=
ate that explicitly clear under Sn 5.2 and usage role.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in;text-indent:-.25in;mso-=
list:l0 level1 lfo1">
<![if !supportLists]><span style=3D"font-family:Symbol"><span style=3D"mso-=
list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roman&quot;"=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>Sn 5.14 defining NNIs. It is worth to mentio=
n how that relates or applies to interwork with a cloud provider. Sn 5.14.2=
 touches a bit in example 1. I don&#8217;t think that we need to care of a =
site within cloud provider, but need to
 describe L3VPN provider and cloud provider interworking since L3SM support=
s cloud access.<o:p></o:p></p>
<p class=3D"MsoListParagraph"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in;text-indent:-.25in;mso-=
list:l0 level1 lfo1">
<![if !supportLists]><span style=3D"font-family:Symbol"><span style=3D"mso-=
list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roman&quot;"=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>A dummy question, which tool is used to conv=
ert the structure of YANG Module in Sn 5 to the YANG Module in Sn 8?
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">BRs/Thanks,<o:p></o:p></p>
<p class=3D"MsoPlainText">Lucy<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">-----Original Message-----<br>
From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of stephane.litkowski@o=
range.com<br>
Sent: Monday, June 06, 2016 9:20 AM<br>
To: l3sm@ietf.org<br>
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt<=
o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Hi L3SM,<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Here is a new revision of the service model.<o:p>=
</o:p></p>
<p class=3D"MsoPlainText">It contains a new way for modeling the site-netwo=
rk-access placement.<o:p></o:p></p>
<p class=3D"MsoPlainText">Also some fixes thanks to comment of the WG.<o:p>=
</o:p></p>
<p class=3D"MsoPlainText">It contains also some first text on NNI modeling.=
 I putted for the moment option B and option C out of scope, but this is st=
ill a point to be discussed. At least it describes what we think necessary =
to be modeled for those cases.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Feel free to comment it.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Best Regards,<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Stephane<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">-----Original Message-----<o:p></o:p></p>
<p class=3D"MsoPlainText">From: L3sm [<a href=3D"mailto:l3sm-bounces@ietf.o=
rg"><span style=3D"color:windowtext;text-decoration:none">mailto:l3sm-bounc=
es@ietf.org</span></a>] On Behalf Of
<a href=3D"mailto:internet-drafts@ietf.org"><span style=3D"color:windowtext=
;text-decoration:none">internet-drafts@ietf.org</span></a><o:p></o:p></p>
<p class=3D"MsoPlainText">Sent: Monday, June 06, 2016 16:17<o:p></o:p></p>
<p class=3D"MsoPlainText">To: <a href=3D"mailto:i-d-announce@ietf.org"><spa=
n style=3D"color:windowtext;text-decoration:none">i-d-announce@ietf.org</sp=
an></a><o:p></o:p></p>
<p class=3D"MsoPlainText">Cc: <a href=3D"mailto:l3sm@ietf.org"><span style=
=3D"color:windowtext;text-decoration:none">l3sm@ietf.org</span></a><o:p></o=
:p></p>
<p class=3D"MsoPlainText">Subject: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn=
-service-model-07.txt<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">A New Internet-Draft is available from the on-lin=
e Internet-Drafts directories.<o:p></o:p></p>
<p class=3D"MsoPlainText">This draft is a work item of the L3VPN Service Mo=
del&nbsp; of the IETF.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Title&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : YANG Data Mod=
el for L3VPN service delivery<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Author=
s&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : Stephane Litkowski<o:p>=
</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; Rob Shakir<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; Luis Tomotaki<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; &nbsp;&nbsp;&nbsp;&nbsp;Kenichi Ogaki<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; Kevin D'Souza<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Filename&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : draft-ietf-l3sm-l3vpn-service-model-07.t=
xt<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Pages&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 153<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Date&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 2016-06-06<o:p></o:p=
></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Abstract:<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; This document defines a YANG data mo=
del that can be used to deliver a<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; Layer 3 Provider Provisioned VPN ser=
vice.&nbsp; The document is limited to<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; the BGP PE-based VPNs as described i=
n RFC4110 and RFC4364.&nbsp; This<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; model is intended to be instantiated=
 at management system to deliver<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; the overall service.&nbsp; This mode=
l is not a configuration model to be<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; used directly on network elements.&n=
bsp; This model provides an abstracted<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; view of the Layer 3 IPVPN service co=
nfiguration components.&nbsp; It will<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; be up to a management system to take=
 this as an input and use<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; specific configurations models to co=
nfigure the different network<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; elements to deliver the service.&nbs=
p; How configuration of network<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; elements is done is out of scope of =
the document.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">The IETF datatracker status page for this draft i=
s:<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"https://datatracker.ietf.org/doc/draft=
-ietf-l3sm-l3vpn-service-model/"><span style=3D"color:windowtext;text-decor=
ation:none">https://datatracker.ietf.org/doc/draft-ietf-l3sm-l3vpn-service-=
model/</span></a><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">There's also a htmlized version available at:<o:p=
></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"https://tools.ietf.org/html/draft-ietf=
-l3sm-l3vpn-service-model-07"><span style=3D"color:windowtext;text-decorati=
on:none">https://tools.ietf.org/html/draft-ietf-l3sm-l3vpn-service-model-07=
</span></a><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">A diff from the previous version is available at:=
<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddr=
aft-ietf-l3sm-l3vpn-service-model-07"><span style=3D"color:windowtext;text-=
decoration:none">https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-l3sm-l3vpn-=
service-model-07</span></a><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Please note that it may take a couple of minutes =
from the time of submission until the htmlized version and diff are availab=
le at tools.ietf.org.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Internet-Drafts are also available by anonymous F=
TP at:<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"ftp://ftp.ietf.org/internet-drafts/"><=
span style=3D"color:windowtext;text-decoration:none">ftp://ftp.ietf.org/int=
ernet-drafts/</span></a><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">_______________________________________________<o=
:p></o:p></p>
<p class=3D"MsoPlainText">L3sm mailing list<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"mailto:L3sm@ietf.org"><span style=3D"c=
olor:windowtext;text-decoration:none">L3sm@ietf.org</span></a><o:p></o:p></=
p>
<p class=3D"MsoPlainText"><a href=3D"https://www.ietf.org/mailman/listinfo/=
l3sm"><span style=3D"color:windowtext;text-decoration:none">https://www.iet=
f.org/mailman/listinfo/l3sm</span></a><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">_________________________________________________=
________________________________________________________________________<o:=
p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Ce message et ses pieces jointes peuvent contenir=
 des informations confidentielles ou privilegiees et ne doivent donc pas et=
re diffuses, exploites ou copies sans autorisation. Si vous avez recu ce me=
ssage par erreur, veuillez le signaler
 a l'expediteur et le detruire ainsi que les pieces jointes. Les messages e=
lectroniques etant susceptibles d'alteration, Orange decline toute responsa=
bilite si ce message a ete altere, deforme ou falsifie. Merci.<o:p></o:p></=
p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">This message and its attachments may contain conf=
idential or privileged information that may be protected by law; they shoul=
d not be distributed, used or copied without authorisation.<o:p></o:p></p>
<p class=3D"MsoPlainText">If you have received this email in error, please =
notify the sender and delete this message and its attachments.<o:p></o:p></=
p>
<p class=3D"MsoPlainText">As emails may be altered, Orange is not liable fo=
r messages that have been modified, changed or falsified.<o:p></o:p></p>
<p class=3D"MsoPlainText">Thank you.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">_______________________________________________<o=
:p></o:p></p>
<p class=3D"MsoPlainText">L3sm mailing list<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"mailto:L3sm@ietf.org"><span style=3D"c=
olor:windowtext;text-decoration:none">L3sm@ietf.org</span></a><o:p></o:p></=
p>
<p class=3D"MsoPlainText"><a href=3D"https://www.ietf.org/mailman/listinfo/=
l3sm"><span style=3D"color:windowtext;text-decoration:none">https://www.iet=
f.org/mailman/listinfo/l3sm</span></a><o:p></o:p></p>
</div>
</body>
</html>

--_000_2691CE0099834E4A9C5044EEC662BB9D57296446dfweml501mbb_--


From nobody Thu Jun  9 00:06:27 2016
Return-Path: <stephane.litkowski@orange.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 4EA6912D518 for <l3sm@ietfa.amsl.com>; Thu,  9 Jun 2016 00:06:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.334
X-Spam-Level: 
X-Spam-Status: No, score=-3.334 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, UNPARSEABLE_RELAY=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 CBYcHsHik16c for <l3sm@ietfa.amsl.com>; Thu,  9 Jun 2016 00:06:23 -0700 (PDT)
Received: from relais-inet.orange.com (relais-nor36.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D46612D14F for <l3sm@ietf.org>; Thu,  9 Jun 2016 00:06:23 -0700 (PDT)
Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) by opfednr25.francetelecom.fr (ESMTP service) with ESMTP id 8B5BD180A90; Thu,  9 Jun 2016 09:06:21 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.31]) by opfednr04.francetelecom.fr (ESMTP service) with ESMTP id 516754007A; Thu,  9 Jun 2016 09:06:21 +0200 (CEST)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM22.corporate.adroot.infra.ftgroup ([fe80::8c90:f4e9:be28:2a1%19]) with mapi id 14.03.0294.000; Thu, 9 Jun 2016 09:06:21 +0200
From: <stephane.litkowski@orange.com>
To: Lucy yong <lucy.yong@huawei.com>, "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
Thread-Index: AQHRv/4i8iSSM4mtWE6AeESR5nwEZZ/cfFGwgAM5XWCAAQQHEA==
Date: Thu, 9 Jun 2016 07:06:20 +0000
Message-ID: <27896_1465455981_5759156D_27896_1169_1_9E32478DFA9976438E7A22F69B08FF921BC47FB9@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <20160606141710.20806.10098.idtracker@ietfa.amsl.com> <27218_1465222795_5755868B_27218_684_1_9E32478DFA9976438E7A22F69B08FF921BC41DA1@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <2691CE0099834E4A9C5044EEC662BB9D57296446@dfweml501-mbb>
In-Reply-To: <2691CE0099834E4A9C5044EEC662BB9D57296446@dfweml501-mbb>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
Content-Type: multipart/alternative; boundary="_000_9E32478DFA9976438E7A22F69B08FF921BC47FB9OPEXCLILMA4corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/YtM6RODhs05KHAAUaEWW8C40k8o>
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
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, 09 Jun 2016 07:06:26 -0000

--_000_9E32478DFA9976438E7A22F69B08FF921BC47FB9OPEXCLILMA4corp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Lucy,

Pls find some comments inline

Thanks,

Stephane

From: Lucy yong [mailto:lucy.yong@huawei.com]
Sent: Wednesday, June 08, 2016 17:55
To: LITKOWSKI Stephane OBS/OINIS; l3sm@ietf.org
Subject: RE: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt


Hi Stephane,



I read this version and have some comments.



*         Sn 5 states "A site is composed of at least one site-network-acce=
ss ...". In data model, site has a site-network-access container and a rout=
ing-protocols container; site-network-access also has a routing-protocols c=
ontainer. Why is the routing-protocols container needed at both? If the rou=
ting-protocols under site means to apply to all its site-network-accesses, =
suggest to state that explicitly clear under Sn 5.2 and usage role.

[SLI] Adding routing-protocols under site-network-access (as other paramete=
rs) was requested some time ago by the WG. Configuring at site level will p=
rovide a kind of inheritance for all site-network-accesses. I will add a st=
atement for this.



*         Sn 5.14 defining NNIs. It is worth to mention how that relates or=
 applies to interwork with a cloud provider. Sn 5.14.2 touches a bit in exa=
mple 1. I don't think that we need to care of a site within cloud provider,=
 but need to describe L3VPN provider and cloud provider interworking since =
L3SM supports cloud access.[SLI] Yes for sure, Cloud is part of NNI. I will=
 fix the text to better highlight it.



*         A dummy question, which tool is used to convert the structure of =
YANG Module in Sn 5 to the YANG Module in Sn 8?
[SLI] "pyang" does the job. There is an option command to convert yang modu=
le to tree.

BRs/Thanks,

Lucy



-----Original Message-----
From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of stephane.litkowski@o=
range.com<mailto:stephane.litkowski@orange.com>
Sent: Monday, June 06, 2016 9:20 AM
To: l3sm@ietf.org<mailto:l3sm@ietf.org>
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt



Hi L3SM,



Here is a new revision of the service model.

It contains a new way for modeling the site-network-access placement.

Also some fixes thanks to comment of the WG.

It contains also some first text on NNI modeling. I putted for the moment o=
ption B and option C out of scope, but this is still a point to be discusse=
d. At least it describes what we think necessary to be modeled for those ca=
ses.



Feel free to comment it.



Best Regards,



Stephane





-----Original Message-----

From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of internet-drafts@ietf=
.org<mailto:internet-drafts@ietf.org>

Sent: Monday, June 06, 2016 16:17

To: i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>

Cc: l3sm@ietf.org<mailto:l3sm@ietf.org>

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





A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.

This draft is a work item of the L3VPN Service Model  of the IETF.



        Title           : YANG Data Model for L3VPN service delivery

        Authors         : Stephane Litkowski

                          Rob Shakir

                          Luis Tomotaki

                          Kenichi Ogaki

                          Kevin D'Souza

      Filename        : draft-ietf-l3sm-l3vpn-service-model-07.txt

      Pages           : 153

      Date            : 2016-06-06



Abstract:

   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:

https://datatracker.ietf.org/doc/draft-ietf-l3sm-l3vpn-service-model/



There's also a htmlized version available at:

https://tools.ietf.org/html/draft-ietf-l3sm-l3vpn-service-model-07



A diff from the previous version is available at:

https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-l3sm-l3vpn-service-model-07





Please note that it may take a couple of minutes from the time of submissio=
n until the htmlized version and diff are available at tools.ietf.org.



Internet-Drafts are also available by anonymous FTP at:

ftp://ftp.ietf.org/internet-drafts/



_______________________________________________

L3sm mailing list

L3sm@ietf.org<mailto:L3sm@ietf.org>

https://www.ietf.org/mailman/listinfo/l3sm



___________________________________________________________________________=
______________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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. Le=
s messages electroniques etant susceptibles d'alteration, Orange decline to=
ute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged inf=
ormation 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 dele=
te 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

L3sm@ietf.org<mailto:L3sm@ietf.org>

https://www.ietf.org/mailman/listinfo/l3sm

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.


--_000_9E32478DFA9976438E7A22F69B08FF921BC47FB9OPEXCLILMA4corp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:784155387;
	mso-list-type:hybrid;
	mso-list-template-ids:-32874636 67698689 67698691 67698693 67698689 676986=
91 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Lucy,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Pls find some comments=
 inline<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Stephane<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Lucy yon=
g [mailto:lucy.yong@huawei.com]
<br>
<b>Sent:</b> Wednesday, June 08, 2016 17:55<br>
<b>To:</b> LITKOWSKI Stephane OBS/OINIS; l3sm@ietf.org<br>
<b>Subject:</b> RE: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-=
07.txt<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Hi Stephane,<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">I read this version and have some comments.<o:p><=
/o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in;text-indent:-.25in;mso-=
list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"font-family:Symbol"><span style=3D"mso-=
list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roman&quot;"=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>Sn 5 states &#8220;A site is composed of at =
least one site-network-access &#8230;&#8221;. In data model, site has a sit=
e-network-access container and a routing-protocols container; site-network-=
access also has a routing-protocols container. Why
 is the routing-protocols container needed at both? If the routing-protocol=
s under site means to apply to all its site-network-accesses, suggest to st=
ate that explicitly clear under Sn 5.2 and usage role.<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#1F497D">[SLI] Adding routin=
g-protocols under site-network-access (as other parameters) was requested s=
ome time ago by the WG. Configuring at site level will provide a kind of in=
heritance for all site-network-accesses.
 I will add a statement for this.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in;text-indent:-.25in;mso-=
list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"font-family:Symbol;color:#1F497D"><span=
 style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times Ne=
w Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>Sn 5.14 defining NNIs. It is worth to mentio=
n how that relates or applies to interwork with a cloud provider. Sn 5.14.2=
 touches a bit in example 1. I don&#8217;t think that we need to care of a =
site within cloud provider, but need to
 describe L3VPN provider and cloud provider interworking since L3SM support=
s cloud access.<span style=3D"color:#1F497D">[SLI] Yes for sure, Cloud is p=
art of NNI. I will fix the text to better highlight it.<o:p></o:p></span></=
p>
<p class=3D"MsoListParagraph"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in;text-indent:-.25in;mso-=
list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"font-family:Symbol"><span style=3D"mso-=
list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roman&quot;"=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>A dummy question, which tool is used to conv=
ert the structure of YANG Module in Sn 5 to the YANG Module in Sn 8?
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.25in"><span style=3D"color:#1F=
497D">[SLI] &#8220;pyang&#8221; does the job. There is an option command to=
 convert yang module to tree.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal">BRs/Thanks,<o:p></o:p></p>
<p class=3D"MsoPlainText">Lucy<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">-----Original Message-----<br>
From: L3sm [<a href=3D"mailto:l3sm-bounces@ietf.org">mailto:l3sm-bounces@ie=
tf.org</a>] On Behalf Of
<a href=3D"mailto:stephane.litkowski@orange.com">stephane.litkowski@orange.=
com</a><br>
Sent: Monday, June 06, 2016 9:20 AM<br>
To: <a href=3D"mailto:l3sm@ietf.org">l3sm@ietf.org</a><br>
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt<=
o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Hi L3SM,<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Here is a new revision of the service model.<o:p>=
</o:p></p>
<p class=3D"MsoPlainText">It contains a new way for modeling the site-netwo=
rk-access placement.<o:p></o:p></p>
<p class=3D"MsoPlainText">Also some fixes thanks to comment of the WG.<o:p>=
</o:p></p>
<p class=3D"MsoPlainText">It contains also some first text on NNI modeling.=
 I putted for the moment option B and option C out of scope, but this is st=
ill a point to be discussed. At least it describes what we think necessary =
to be modeled for those cases.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Feel free to comment it.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Best Regards,<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Stephane<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">-----Original Message-----<o:p></o:p></p>
<p class=3D"MsoPlainText">From: L3sm [<a href=3D"mailto:l3sm-bounces@ietf.o=
rg"><span style=3D"color:windowtext;text-decoration:none">mailto:l3sm-bounc=
es@ietf.org</span></a>] On Behalf Of
<a href=3D"mailto:internet-drafts@ietf.org"><span style=3D"color:windowtext=
;text-decoration:none">internet-drafts@ietf.org</span></a><o:p></o:p></p>
<p class=3D"MsoPlainText">Sent: Monday, June 06, 2016 16:17<o:p></o:p></p>
<p class=3D"MsoPlainText">To: <a href=3D"mailto:i-d-announce@ietf.org"><spa=
n style=3D"color:windowtext;text-decoration:none">i-d-announce@ietf.org</sp=
an></a><o:p></o:p></p>
<p class=3D"MsoPlainText">Cc: <a href=3D"mailto:l3sm@ietf.org"><span style=
=3D"color:windowtext;text-decoration:none">l3sm@ietf.org</span></a><o:p></o=
:p></p>
<p class=3D"MsoPlainText">Subject: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn=
-service-model-07.txt<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">A New Internet-Draft is available from the on-lin=
e Internet-Drafts directories.<o:p></o:p></p>
<p class=3D"MsoPlainText">This draft is a work item of the L3VPN Service Mo=
del&nbsp; of the IETF.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Title&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : YANG Data Mod=
el for L3VPN service delivery<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Author=
s&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : Stephane Litkowski<o:p>=
</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; Rob Shakir<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; Luis Tomotaki<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; &nbsp;&nbsp;&nbsp;&nbsp;Kenichi Ogaki<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; Kevin D'Souza<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Filename&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : draft-ietf-l3sm-l3vpn-service-model-07.t=
xt<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Pages&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 153<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Date&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 2016-06-06<o:p></o:p=
></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Abstract:<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; This document defines a YANG data mo=
del that can be used to deliver a<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; Layer 3 Provider Provisioned VPN ser=
vice.&nbsp; The document is limited to<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; the BGP PE-based VPNs as described i=
n RFC4110 and RFC4364.&nbsp; This<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; model is intended to be instantiated=
 at management system to deliver<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; the overall service.&nbsp; This mode=
l is not a configuration model to be<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; used directly on network elements.&n=
bsp; This model provides an abstracted<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; view of the Layer 3 IPVPN service co=
nfiguration components.&nbsp; It will<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; be up to a management system to take=
 this as an input and use<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; specific configurations models to co=
nfigure the different network<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; elements to deliver the service.&nbs=
p; How configuration of network<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; elements is done is out of scope of =
the document.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">The IETF datatracker status page for this draft i=
s:<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"https://datatracker.ietf.org/doc/draft=
-ietf-l3sm-l3vpn-service-model/"><span style=3D"color:windowtext;text-decor=
ation:none">https://datatracker.ietf.org/doc/draft-ietf-l3sm-l3vpn-service-=
model/</span></a><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">There's also a htmlized version available at:<o:p=
></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"https://tools.ietf.org/html/draft-ietf=
-l3sm-l3vpn-service-model-07"><span style=3D"color:windowtext;text-decorati=
on:none">https://tools.ietf.org/html/draft-ietf-l3sm-l3vpn-service-model-07=
</span></a><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">A diff from the previous version is available at:=
<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddr=
aft-ietf-l3sm-l3vpn-service-model-07"><span style=3D"color:windowtext;text-=
decoration:none">https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-l3sm-l3vpn-=
service-model-07</span></a><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Please note that it may take a couple of minutes =
from the time of submission until the htmlized version and diff are availab=
le at tools.ietf.org.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Internet-Drafts are also available by anonymous F=
TP at:<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"ftp://ftp.ietf.org/internet-drafts/"><=
span style=3D"color:windowtext;text-decoration:none">ftp://ftp.ietf.org/int=
ernet-drafts/</span></a><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">_______________________________________________<o=
:p></o:p></p>
<p class=3D"MsoPlainText">L3sm mailing list<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"mailto:L3sm@ietf.org"><span style=3D"c=
olor:windowtext;text-decoration:none">L3sm@ietf.org</span></a><o:p></o:p></=
p>
<p class=3D"MsoPlainText"><a href=3D"https://www.ietf.org/mailman/listinfo/=
l3sm"><span style=3D"color:windowtext;text-decoration:none">https://www.iet=
f.org/mailman/listinfo/l3sm</span></a><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">_________________________________________________=
________________________________________________________________________<o:=
p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Ce message et ses pieces jointes peuvent contenir=
 des informations confidentielles ou privilegiees et ne doivent donc pas et=
re diffuses, exploites ou copies sans autorisation. Si vous avez recu ce me=
ssage par erreur, veuillez le signaler
 a l'expediteur et le detruire ainsi que les pieces jointes. Les messages e=
lectroniques etant susceptibles d'alteration, Orange decline toute responsa=
bilite si ce message a ete altere, deforme ou falsifie. Merci.<o:p></o:p></=
p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">This message and its attachments may contain conf=
idential or privileged information that may be protected by law; they shoul=
d not be distributed, used or copied without authorisation.<o:p></o:p></p>
<p class=3D"MsoPlainText">If you have received this email in error, please =
notify the sender and delete this message and its attachments.<o:p></o:p></=
p>
<p class=3D"MsoPlainText">As emails may be altered, Orange is not liable fo=
r messages that have been modified, changed or falsified.<o:p></o:p></p>
<p class=3D"MsoPlainText">Thank you.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">_______________________________________________<o=
:p></o:p></p>
<p class=3D"MsoPlainText">L3sm mailing list<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"mailto:L3sm@ietf.org"><span style=3D"c=
olor:windowtext;text-decoration:none">L3sm@ietf.org</span></a><o:p></o:p></=
p>
<p class=3D"MsoPlainText"><a href=3D"https://www.ietf.org/mailman/listinfo/=
l3sm"><span style=3D"color:windowtext;text-decoration:none">https://www.iet=
f.org/mailman/listinfo/l3sm</span></a><o:p></o:p></p>
</div>
<PRE>______________________________________________________________________=
___________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.
</PRE></body>
</html>

--_000_9E32478DFA9976438E7A22F69B08FF921BC47FB9OPEXCLILMA4corp_--


From nobody Thu Jun  9 01:32:44 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: l3sm@ietf.org
Delivered-To: l3sm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D83EC12D145; Thu,  9 Jun 2016 01:32:40 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.21.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160609083240.16827.27610.idtracker@ietfa.amsl.com>
Date: Thu, 09 Jun 2016 01:32:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/-IeFLgRLiBa2LkZwrQUPii_SKOU>
Cc: l3sm@ietf.org
Subject: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-08.txt
X-BeenThere: l3sm@ietf.org
X-Mailman-Version: 2.1.17
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, 09 Jun 2016 08:32:41 -0000

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

        Title           : YANG Data Model for L3VPN service delivery
        Authors         : Stephane Litkowski
                          Rob Shakir
                          Luis Tomotaki
                          Kenichi Ogaki
                          Kevin D'Souza
	Filename        : draft-ietf-l3sm-l3vpn-service-model-08.txt
	Pages           : 156
	Date            : 2016-06-09

Abstract:
   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:
https://datatracker.ietf.org/doc/draft-ietf-l3sm-l3vpn-service-model/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-l3sm-l3vpn-service-model-08

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-l3sm-l3vpn-service-model-08


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

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Jun  9 01:34:40 2016
Return-Path: <stephane.litkowski@orange.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 E00A712D53C for <l3sm@ietfa.amsl.com>; Thu,  9 Jun 2016 01:34:37 -0700 (PDT)
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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 ZRd-ra5yJe_9 for <l3sm@ietfa.amsl.com>; Thu,  9 Jun 2016 01:34:33 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84CE112D54F for <l3sm@ietf.org>; Thu,  9 Jun 2016 01:34:32 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id D24DC324E9D; Thu,  9 Jun 2016 10:34:30 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.60]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id AB7214C06E; Thu,  9 Jun 2016 10:34:30 +0200 (CEST)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM7F.corporate.adroot.infra.ftgroup ([fe80::c1d7:e278:e357:11ad%19]) with mapi id 14.03.0294.000; Thu, 9 Jun 2016 10:34:30 +0200
From: <stephane.litkowski@orange.com>
To: "Scharf, Michael (Nokia - DE)" <michael.scharf@nokia.com>, "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: Ops state in templates?
Thread-Index: AQHRwKOKR0JofdVIZkyADD+doOpm65/flPsg///xG4CAAUvFAA==
Date: Thu, 9 Jun 2016 08:34:29 +0000
Message-ID: <2209_1465461270_57592A16_2209_2170_1_9E32478DFA9976438E7A22F69B08FF921BC4850F@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <655C07320163294895BBADA28372AF5D4887B657@FR712WXCHMBA15.zeu.alcatel-lucent.com> <14583_1464773427_574EAB33_14583_3223_1_9E32478DFA9976438E7A22F69B08FF921BC3B97E@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <655C07320163294895BBADA28372AF5D488BABA8@FR712WXCHMBA15.zeu.alcatel-lucent.com> <2211_1465393352_575820C8_2211_6527_1_9E32478DFA9976438E7A22F69B08FF921BC4667D@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <655C07320163294895BBADA28372AF5D488C4A46@FR712WXCHMBA15.zeu.alcatel-lucent.com>
In-Reply-To: <655C07320163294895BBADA28372AF5D488C4A46@FR712WXCHMBA15.zeu.alcatel-lucent.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.6.9.75417
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/Ab0F_ylRCXNbj1DGDtaRVO9GzWc>
Subject: Re: [L3sm] Ops state in templates?
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, 09 Jun 2016 08:34:38 -0000

I agree that they are orthogonal.

Please raise the question to netmod.


-----Original Message-----
From: Scharf, Michael (Nokia - DE) [mailto:michael.scharf@nokia.com]=20
Sent: Wednesday, June 08, 2016 16:46
To: LITKOWSKI Stephane OBS/OINIS; l3sm@ietf.org
Subject: RE: Ops state in templates?

As I said already, I believe that the modeling of a L3VPN and the handling =
of templates are by and large orthogonal problems.

And, sure, I would prefer a generic solution for the latter, since template=
s could have a much wider applicability. But maybe that question could be r=
aised on the NETMOD list?

Michael

-----Original Message-----
From: stephane.litkowski@orange.com [mailto:stephane.litkowski@orange.com]=
=20
Sent: Wednesday, June 08, 2016 3:43 PM
To: Scharf, Michael (Nokia - DE); l3sm@ietf.org
Subject: RE: Ops state in templates?

Hi Michael

Pls find some inline comments.

Best Regards,


-----Original Message-----
From: Scharf, Michael (Nokia - DE) [mailto:michael.scharf@nokia.com]
Sent: Tuesday, June 07, 2016 12:01
To: LITKOWSKI Stephane OBS/OINIS; l3sm@ietf.org
Subject: Ops state in templates?

Hi Stephane,

I see that this has been fixed in -07. Thanks. However, is ops state indeed=
 useful in the subtree "site-templates"?

The more fundamental question is whether the template mechanism may require=
 some further thinking. For instance:

* According to Section 5.15, "If a site has some particular parameters, spe=
cific parameters within the site MUST always override parameters derived fr=
om template." Now, what happens if the template defines a list (e.g., "casc=
aded-lan-prefixes")? If a requester would want to add something to a pre-de=
fined list, does this mean that first the template list entries have to be =
read, then list entries have to be added by the requester, and then the mer=
ged list has to be used in the service request?
[SLI] As override is needed, I would say that the list in the template will=
 not be used and the local list will be.


* Another example that comes into my mind is the error handling if a site c=
annot be added, because some parameter in the template cannot be deployed. =
Is this a problem of the service request or of the template?
[SLI] Yes, but it's inherent to any template use case, it's not specific to=
 this service model.


At first sight, this sort of question may be quite independent of the model=
ing of a L3VPN. It seems to me that templates may have some implications on=
 a system implementing the YANG model.=20
[SLI] I agree that defining templates at YANG level would be helpful. Do yo=
u think we should remove the template in L3VPN SM ?


Thanks

Michael



-----Original Message-----
From: stephane.litkowski@orange.com [mailto:stephane.litkowski@orange.com]
Sent: Wednesday, June 01, 2016 11:30 AM
To: Scharf, Michael (Nokia - DE); l3sm@ietf.org
Subject: RE: actual-site-start / actual-site-stop

Hi Michael,

This is a mistake, these are ops state that needs to be config false.

Thanks for the catch.


-----Original Message-----
From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of Scharf, Michael (Nok=
ia - DE)
Sent: Wednesday, June 01, 2016 11:25
To: l3sm@ietf.org
Subject: [L3sm] actual-site-start / actual-site-stop

Hi,

Is "actual-site-start" and "actual-site-stop" indeed meant to tagged by "co=
nfig true"?

If so, what is the expected behavior if this is set, either directly or by =
template?

Thanks

Michael

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

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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. Le=
s messages electroniques etant susceptibles d'alteration, Orange decline to=
ute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation 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 dele=
te 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.


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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. Le=
s messages electroniques etant susceptibles d'alteration, Orange decline to=
ute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation 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 dele=
te 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.


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.


From nobody Thu Jun  9 02:59:43 2016
Return-Path: <daviball@cisco.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 C26CB12D0F0 for <l3sm@ietfa.amsl.com>; Thu,  9 Jun 2016 02:59:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.946
X-Spam-Level: 
X-Spam-Status: No, score=-15.946 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_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-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 Kqf6Ht19qZst for <l3sm@ietfa.amsl.com>; Thu,  9 Jun 2016 02:59:38 -0700 (PDT)
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 51DD712D0A0 for <l3sm@ietf.org>; Thu,  9 Jun 2016 02:59:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15518; q=dns/txt; s=iport; t=1465466377; x=1466675977; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=WKNP2WoaU0w6f1l+lFVzYYGzxQAWsjXGQLWI0CGvIlc=; b=MrKec4glHRX6lQB55rOtypeePQo8aURGgpjg1RS/52YXliyPFYVW0fjB 0ircidrbINsoOdZyuWLjYRFCwCObLJX+EE7qYLPZRUhX16CYNWCe/tVvd tdPSIGLpUpdjkLiDEjnCZDecENcIH6NQJQk/sS+spfYkAZF/0kP9Zw8gs 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CWCACSPFlX/xbLJq1VCYJwgU9SthiGe?= =?us-ascii?q?YYTAoF/EQEBAQEBAQFlJ4RGAQEELVwLGC5XBgEMBgIBAReIFL4RAQEBAQEBAQE?= =?us-ascii?q?BAQEBAQEBAQEBAQEBHIYngXcIgk6EGYYBBZM8hRaIe4UrgWmHWyOFOIt+HYNIN?= =?us-ascii?q?CCCBwUXgUw7MooIAQEB?=
X-IronPort-AV: E=Sophos;i="5.26,444,1459814400";  d="scan'208,217";a="635074069"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Jun 2016 09:59:35 +0000
Received: from [10.63.23.103] (dhcp-ensft1-uk-vla370-10-63-23-103.cisco.com [10.63.23.103]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id u599xYaE010496; Thu, 9 Jun 2016 09:59:35 GMT
To: stephane.litkowski@orange.com, "l3sm@ietf.org" <l3sm@ietf.org>
References: <20160606141710.20806.10098.idtracker@ietfa.amsl.com> <27218_1465222795_5755868B_27218_684_1_9E32478DFA9976438E7A22F69B08FF921BC41DA1@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <ec72f8b8-8626-ba2c-bc50-7ce4a0cdc6df@cisco.com> <32265_1465379094_5757E916_32265_10098_3_9E32478DFA9976438E7A22F69B08FF921BC454AB@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
From: David Ball <daviball@cisco.com>
Message-ID: <1595f5bb-1838-8164-6e7f-1d383d8bfb87@cisco.com>
Date: Thu, 9 Jun 2016 10:59:34 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <32265_1465379094_5757E916_32265_10098_3_9E32478DFA9976438E7A22F69B08FF921BC454AB@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
Content-Type: multipart/alternative; boundary="------------E3035271096182E4DB8D1BAC"
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/Cs09Yt3IBfwCR9JbN3JikLu6cjk>
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
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, 09 Jun 2016 09:59:41 -0000

This is a multi-part message in MIME format.
--------------E3035271096182E4DB8D1BAC
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

Thanks Stephane.

See inline - I have cut out the points where we're agreed.

On 08/06/2016 10:44, stephane.litkowski@orange.com wrote:
>
>   * Sn 5.4.1: I think with your new diversity constraints, the SubVPN
>     flavor is no longer needed, right?  You could model it as separate
>     sites, with accesses in the same group and with a "same-bearer"
>     constraint on that group, right?  So Sn 5.4.1.3 could be deleted,
>     along with the site-vpn-flavor-sub identity in the model.
>
> [SLI] From a constraint perspective yes, now from a service point of 
> view, it is still interesting to keep the information of the VPN style 
> the customer wants. Some SP may enforce some parameters based on this 
> information.
>

[DB] Ok - I think in this case it would be useful to say that sub-VPN is 
the same as having 2 sites with a "same-bearer" constraint.

>   * Sn 5.5.4.2: I can't parse the second paragraph  - I think it
>     should say: "... 3 branch offices can be connected to the same PE
>     but not on the same linecard."
>
> [SLI] Implementing “linecard-diverse” does not mean that you want to 
> be on the same PE. It means that the system MUST avoid to connect the 
> sites on the same LC, the solution can be to use the same PE with 
> another LC, or another PE also.
>

[DB] Agreed - my comment was more about the grammar. :)

>   * Sn 5.9: If the CE is provider-managed, why is a management address
>     needed in the model?  How the provider connects to the device
>     would be internal to the provider, right?
>     (For co-managed I can see this could be needed, i.e. to tell the
>     customer what address to use to connect to the device for
>     configuration/monitoring)
>
> [SLI] There is a mistake here. You must read “In case of 
> “customer-managed” or “co-managed”, the model proposes …”
>

[DB] I don't understand what this is for in the customer-managed case 
either.  If it is customer-managed, the customer already knows the 
management address, and the SP doesn't need to know it.  I think it's 
only needed for co-managed, right?

>   * Sn 5.10.2: You said before that the model can only manage P2P
>     connections; but this figure (and the next one) show the PE
>     connected to a LAN, not to a CE.  I am not sure how to interpret
>     this?  Isn't this a case where the connection is multipoint, not P2P?
>
> [SLI] That’s still point to point. In 5.10.3, customer must order two 
> site network accesses (point to point). Each site network network 
> access may be connected to a switch at customer side (same one or not).
>

[DB] If there is an L2 switch, then at L3 it is a multipoint connection 
- the switch is part of the bearer.


     David


-- 
David Ball
<daviball@cisco.com>


--------------E3035271096182E4DB8D1BAC
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Thanks Stephane.<br>
    <br>
    See inline - I have cut out the points where we're agreed.<br>
    <br>
    <div class="moz-cite-prefix">On 08/06/2016 10:44,
      <a class="moz-txt-link-abbreviated" href="mailto:stephane.litkowski@orange.com">stephane.litkowski@orange.com</a> wrote:<br>
    </div>
    <blockquote
cite="mid:32265_1465379094_5757E916_32265_10098_3_9E32478DFA9976438E7A22F69B08FF921BC454AB@OPEXCLILMA4.corporate.adroot.infra.ftgroup"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <meta name="Generator" content="Microsoft Word 14 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	color:black;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1656761572;
	mso-list-template-ids:-682878950;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1"><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext"><o:p></o:p></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span>
        <ul type="disc">
          <li class="MsoNormal"
            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
            level1 lfo1">
            Sn 5.4.1: I think with your new diversity constraints, the
            SubVPN flavor is no longer needed, right?  You could model
            it as separate sites, with accesses in the same group and
            with a "same-bearer" constraint on that group, right?  So Sn
            5.4.1.3 could be deleted, along with the site-vpn-flavor-sub
            identity in the model.<o:p></o:p></li>
        </ul>
        <p class="MsoNormal"
          style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">[SLI]
            From a constraint perspective yes, now from a service point
            of view, it is still interesting to keep the information of
            the VPN style the customer wants. Some SP may enforce some
            parameters based on this information.</span></p>
      </div>
    </blockquote>
    <br>
    [DB] Ok - I think in this case it would be useful to say that
    sub-VPN is the same as having 2 sites with a "same-bearer"
    constraint.<br>
    <br>
    <blockquote
cite="mid:32265_1465379094_5757E916_32265_10098_3_9E32478DFA9976438E7A22F69B08FF921BC454AB@OPEXCLILMA4.corporate.adroot.infra.ftgroup"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal"
          style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span></p>
        <span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span>
        <ul type="disc">
          <li class="MsoNormal"
            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
            level1 lfo1">
            Sn 5.5.4.2: I can't parse the second paragraph  - I think it
            should say: "... 3 branch offices can be connected to the
            same PE but not on the same linecard."<o:p></o:p></li>
        </ul>
        <p class="MsoNormal"
          style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">[SLI]
            Implementing “linecard-diverse” does not mean that you want
            to be on the same PE. It means that the system MUST avoid to
            connect the sites on the same LC, the solution can be to use
            the same PE with another LC, or another PE also.</span></p>
      </div>
    </blockquote>
    <br>
    [DB] Agreed - my comment was more about the grammar. :)<br>
    <br>
    <blockquote
cite="mid:32265_1465379094_5757E916_32265_10098_3_9E32478DFA9976438E7A22F69B08FF921BC454AB@OPEXCLILMA4.corporate.adroot.infra.ftgroup"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal"
          style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span></p>
        <span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span>
        <ul type="disc">
          <li class="MsoNormal"
            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
            level1 lfo1">
            Sn 5.9: If the CE is provider-managed, why is a management
            address needed in the model?  How the provider connects to
            the device would be internal to the provider, right?<br>
            (For co-managed I can see this could be needed, i.e. to tell
            the customer what address to use to connect to the device
            for configuration/monitoring)<o:p></o:p></li>
        </ul>
        <p class="MsoNormal"
          style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">[SLI]
            There is a mistake here. You must read “In case of
            “customer-managed” or “co-managed”, the model proposes …”</span></p>
      </div>
    </blockquote>
    <br>
    [DB] I don't understand what this is for in the customer-managed
    case either.  If it is customer-managed, the customer already knows
    the management address, and the SP doesn't need to know it.  I think
    it's only needed for co-managed, right?<br>
    <br>
    <blockquote
cite="mid:32265_1465379094_5757E916_32265_10098_3_9E32478DFA9976438E7A22F69B08FF921BC454AB@OPEXCLILMA4.corporate.adroot.infra.ftgroup"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal"
          style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span></p>
        <ul type="disc">
          <li class="MsoNormal"
            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
            level1 lfo1">
            Sn 5.10.2: You said before that the model can only manage
            P2P connections; but this figure (and the next one) show the
            PE connected to a LAN, not to a CE.  I am not sure how to
            interpret this?  Isn't this a case where the connection is
            multipoint, not P2P?<o:p></o:p></li>
        </ul>
        <p class="MsoNormal"
          style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">[SLI]
            That’s still point to point. In 5.10.3, customer must order
            two site network accesses (point to point). Each site
            network network access may be connected to a switch at
            customer side (same one or not).</span></p>
      </div>
    </blockquote>
    <br>
    [DB] If there is an L2 switch, then at L3 it is a multipoint
    connection - the switch is part of the bearer.<br>
    <br>
    <br>
        David<br>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
David Ball
<a class="moz-txt-link-rfc2396E" href="mailto:daviball@cisco.com">&lt;daviball@cisco.com&gt;</a></pre>
  </body>
</html>

--------------E3035271096182E4DB8D1BAC--


From nobody Thu Jun  9 10:21:26 2016
Return-Path: <lucy.yong@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 899CB12B039 for <l3sm@ietfa.amsl.com>; Thu,  9 Jun 2016 10:21:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.647
X-Spam-Level: 
X-Spam-Status: No, score=-5.647 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=-1.426, 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 m7kIQaKbDBw4 for <l3sm@ietfa.amsl.com>; Thu,  9 Jun 2016 10:21:23 -0700 (PDT)
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 C305312D8C4 for <l3sm@ietf.org>; Thu,  9 Jun 2016 10:21:22 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml708-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CLR04883; Thu, 09 Jun 2016 17:21:20 +0000 (GMT)
Received: from DFWEML701-CAH.china.huawei.com (10.193.5.175) by lhreml708-cah.china.huawei.com (10.201.5.202) with Microsoft SMTP Server (TLS) id 14.3.235.1; Thu, 9 Jun 2016 18:21:17 +0100
Received: from DFWEML501-MBB.china.huawei.com ([10.193.5.179]) by dfweml701-cah.china.huawei.com ([10.193.5.175]) with mapi id 14.03.0235.001; Thu, 9 Jun 2016 10:21:12 -0700
From: Lucy yong <lucy.yong@huawei.com>
To: "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>, "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-08.txt
Thread-Index: AQHRwimKDx7H8IU3QUuz+M/AtvfoDJ/hSWnQ
Date: Thu, 9 Jun 2016 17:21:11 +0000
Message-ID: <2691CE0099834E4A9C5044EEC662BB9D57296AD0@dfweml501-mbb>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.130.234]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.5759A590.0258, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: cb65d53b80d43a7d67d687d01e0aed88
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/rzVma5aB8lDkYv5nLZqV-n6qeW8>
Subject: [L3sm] FW: I-D Action: draft-ietf-l3sm-l3vpn-service-model-08.txt
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, 09 Jun 2016 17:21:25 -0000

Hi Stephane,

Thank you to address my comments/suggestions in these version.

Sn 5.1.2, The usage of cloud-access is targeted for
   public cloud.  Internet access can also be considered as a public
   cloud access service. The cloud-access container provides parameters
   for network address translation and authorization rules.

Need cloud-access container for Internet access but no need a cloud identif=
ier for Internet access, right? Good to state out it.

One Caveat: you forget a description about the new figure under Sn 5.14.

Sn 5.14.1
   The cloud service provider or the customer itself may use our L3VPN
   service model exposed by service provider B to create the VPN
   connectivity.  We could consider that, as the NNI is shared, the
   physical connection (bearer) between CSP A and SP B already exists.
   CSPA may so request through a service model a new site creation with
   a single site-network-access (single homing used in the diagram).  As
   placement constraint, CSP A may use the existing bearer reference it
   has from SP A to force the placement of the VPN NNI on the existing
   link.

This is the case that multiple sites to share the same bearer between CSPA =
and SP A. This is different from subVPN case where it is related to a singl=
e site. It is important to point that out in Sn 5.2.1.1.

On page 83,
 <site>
    <site-id>CSP_B_attachment</site-id>

Should it be CSP_A to align with the example?

May consider add some description for cloud provider and SP interworking us=
ing option B and C as well.=20



Thanks,
Lucy

=20

-----Original Message-----
From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of internet-drafts@ietf=
.org
Sent: Thursday, June 09, 2016 3:33 AM
To: i-d-announce@ietf.org
Cc: l3sm@ietf.org
Subject: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-08.txt


A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
This draft is a work item of the L3VPN Service Model  of the IETF.

        Title           : YANG Data Model for L3VPN service delivery
        Authors         : Stephane Litkowski
                          Rob Shakir
                          Luis Tomotaki
                          Kenichi Ogaki
                          Kevin D'Souza
	Filename        : draft-ietf-l3sm-l3vpn-service-model-08.txt
	Pages           : 156
	Date            : 2016-06-09

Abstract:
   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:
https://datatracker.ietf.org/doc/draft-ietf-l3sm-l3vpn-service-model/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-l3sm-l3vpn-service-model-08

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-l3sm-l3vpn-service-model-08


Please note that it may take a couple of minutes from the time of submissio=
n until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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


From nobody Thu Jun  9 12:08:51 2016
Return-Path: <stephane.litkowski@orange.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 76AC012D907 for <l3sm@ietfa.amsl.com>; Thu,  9 Jun 2016 12:08:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.608
X-Spam-Level: 
X-Spam-Status: No, score=-2.608 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, UNPARSEABLE_RELAY=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 v8MW5CAYJ2UZ for <l3sm@ietfa.amsl.com>; Thu,  9 Jun 2016 12:08:47 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1FD412D933 for <l3sm@ietf.org>; Thu,  9 Jun 2016 12:08:46 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 25DD0324B1D; Thu,  9 Jun 2016 21:08:45 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.61]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id F3D0A35C045; Thu,  9 Jun 2016 21:08:44 +0200 (CEST)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM7E.corporate.adroot.infra.ftgroup ([fe80::b91c:ea2c:ac8a:7462%19]) with mapi id 14.03.0294.000; Thu, 9 Jun 2016 21:08:44 +0200
From: <stephane.litkowski@orange.com>
To: David Ball <daviball@cisco.com>, "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
Thread-Index: AQHRv/4i8iSSM4mtWE6AeESR5nwEZZ/cfFGwgAGg6gCAASznEIABf5oAgAC53hA=
Date: Thu, 9 Jun 2016 19:08:44 +0000
Message-ID: <7576_1465499325_5759BEBD_7576_3122_1_9E32478DFA9976438E7A22F69B08FF921BC4C5F2@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <20160606141710.20806.10098.idtracker@ietfa.amsl.com> <27218_1465222795_5755868B_27218_684_1_9E32478DFA9976438E7A22F69B08FF921BC41DA1@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <ec72f8b8-8626-ba2c-bc50-7ce4a0cdc6df@cisco.com> <32265_1465379094_5757E916_32265_10098_3_9E32478DFA9976438E7A22F69B08FF921BC454AB@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <1595f5bb-1838-8164-6e7f-1d383d8bfb87@cisco.com>
In-Reply-To: <1595f5bb-1838-8164-6e7f-1d383d8bfb87@cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.1]
Content-Type: multipart/alternative; boundary="_000_9E32478DFA9976438E7A22F69B08FF921BC4C5F2OPEXCLILMA4corp_"
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.6.9.181216
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/fMZX5oCWOTJ59gPY82zFsnYO0tY>
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
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, 09 Jun 2016 19:08:50 -0000

--_000_9E32478DFA9976438E7A22F69B08FF921BC4C5F2OPEXCLILMA4corp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

More inline

Thanks

From: David Ball [mailto:daviball@cisco.com]
Sent: Thursday, June 09, 2016 12:00
To: LITKOWSKI Stephane OBS/OINIS; l3sm@ietf.org
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

Thanks Stephane.

See inline - I have cut out the points where we're agreed.
On 08/06/2016 10:44, stephane.litkowski@orange.com<mailto:stephane.litkowsk=
i@orange.com> wrote:

  *   Sn 5.4.1: I think with your new diversity constraints, the SubVPN fla=
vor is no longer needed, right?  You could model it as separate sites, with=
 accesses in the same group and with a "same-bearer" constraint on that gro=
up, right?  So Sn 5.4.1.3 could be deleted, along with the site-vpn-flavor-=
sub identity in the model.
[SLI] From a constraint perspective yes, now from a service point of view, =
it is still interesting to keep the information of the VPN style the custom=
er wants. Some SP may enforce some parameters based on this information.

[DB] Ok - I think in this case it would be useful to say that sub-VPN is th=
e same as having 2 sites with a "same-bearer" constraint.

[SLI] Ok, will add it

  *   Sn 5.5.4.2: I can't parse the second paragraph  - I think it should s=
ay: "... 3 branch offices can be connected to the same PE but not on the sa=
me linecard."
[SLI] Implementing "linecard-diverse" does not mean that you want to be on =
the same PE. It means that the system MUST avoid to connect the sites on th=
e same LC, the solution can be to use the same PE with another LC, or anoth=
er PE also.

[DB] Agreed - my comment was more about the grammar. :)



  *   Sn 5.9: If the CE is provider-managed, why is a management address ne=
eded in the model?  How the provider connects to the device would be intern=
al to the provider, right?
(For co-managed I can see this could be needed, i.e. to tell the customer w=
hat address to use to connect to the device for configuration/monitoring)
[SLI] There is a mistake here. You must read "In case of "customer-managed"=
 or "co-managed", the model proposes ..."

[DB] I don't understand what this is for in the customer-managed case eithe=
r.  If it is customer-managed, the customer already knows the management ad=
dress, and the SP doesn't need to know it.  I think it's only needed for co=
-managed, right?

[SLI] Yes, I agree, will update accordingly



  *   Sn 5.10.2: You said before that the model can only manage P2P connect=
ions; but this figure (and the next one) show the PE connected to a LAN, no=
t to a CE.  I am not sure how to interpret this?  Isn't this a case where t=
he connection is multipoint, not P2P?
[SLI] That's still point to point. In 5.10.3, customer must order two site =
network accesses (point to point). Each site network network access may be =
connected to a switch at customer side (same one or not).

[DB] If there is an L2 switch, then at L3 it is a multipoint connection - t=
he switch is part of the bearer.
[SLI] From a SP  point of view no, in term of service, the customer will ha=
ve to order two site-network-accesses. How they are connected to the custom=
er network is not under the SP responsibility. If the customer connects the=
 two site-net-access on the same Lan through a switch, it becomes multipoin=
t, but SP is not essentially aware of it.




    David




--

David Ball

<daviball@cisco.com><mailto:daviball@cisco.com>

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.


--_000_9E32478DFA9976438E7A22F69B08FF921BC4C5F2OPEXCLILMA4corp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	color:black;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:464737076;
	mso-list-template-ids:1294353514;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1
	{mso-list-id:1082293066;
	mso-list-template-ids:492234094;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2
	{mso-list-id:1087075688;
	mso-list-template-ids:-296046016;}
@list l2:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3
	{mso-list-id:1590500162;
	mso-list-template-ids:-584673594;}
@list l3:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l4
	{mso-list-id:1656761572;
	mso-list-template-ids:-682878950;}
@list l4:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l4:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l4:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l4:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l4:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l4:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l4:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l4:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l4:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=3D"white" lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">More inline<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><spa=
n style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif=
&quot;;color:windowtext"> David Ball [mailto:daviball@cisco.com]
<br>
<b>Sent:</b> Thursday, June 09, 2016 12:00<br>
<b>To:</b> LITKOWSKI Stephane OBS/OINIS; l3sm@ietf.org<br>
<b>Subject:</b> Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-=
07.txt<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Thanks Stephane.<br>
<br>
See inline - I have cut out the points where we're agreed.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">On 08/06/2016 10:44, <a href=3D"mailto:stephane.litk=
owski@orange.com">
stephane.litkowski@orange.com</a> wrote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l4 level1 lfo3">
Sn 5.4.1: I think with your new diversity constraints, the SubVPN flavor is=
 no longer needed, right?&nbsp; You could model it as separate sites, with =
accesses in the same group and with a &quot;same-bearer&quot; constraint on=
 that group, right?&nbsp; So Sn 5.4.1.3 could be deleted,
 along with the site-vpn-flavor-sub identity in the model.<o:p></o:p></li><=
/ul>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">[SLI] From a constraint perspective yes=
, now from a service point of view, it is still interesting
 to keep the information of the VPN style the customer wants. Some SP may e=
nforce some parameters based on this information.</span><o:p></o:p></p>
</blockquote>
<p class=3D"MsoNormal"><br>
[DB] Ok - I think in this case it would be useful to say that sub-VPN is th=
e same as having 2 sites with a &quot;same-bearer&quot; constraint.<br>
<br>
<span style=3D"color:#1F497D">[SLI] Ok, will add it</span><o:p></o:p></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l4 level1 lfo3">
Sn 5.5.4.2: I can't parse the second paragraph&nbsp; - I think it should sa=
y: &quot;... 3 branch offices can be connected to the same PE but not on th=
e same linecard.&quot;<o:p></o:p></li></ul>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">[SLI] Implementing &#8220;linecard-dive=
rse&#8221; does not mean that you want to be on the same PE. It means
 that the system MUST avoid to connect the sites on the same LC, the soluti=
on can be to use the same PE with another LC, or another PE also.</span><o:=
p></o:p></p>
<p class=3D"MsoNormal"><br>
[DB] Agreed - my comment was more about the grammar. :)<br>
<br>
<br>
<o:p></o:p></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l4 level1 lfo3">
Sn 5.9: If the CE is provider-managed, why is a management address needed i=
n the model?&nbsp; How the provider connects to the device would be interna=
l to the provider, right?<br>
(For co-managed I can see this could be needed, i.e. to tell the customer w=
hat address to use to connect to the device for configuration/monitoring)<o=
:p></o:p></li></ul>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">[SLI] There is a mistake here. You must=
 read &#8220;In case of &#8220;customer-managed&#8221; or &#8220;co-managed=
&#8221;, the
 model proposes &#8230;&#8221;</span><o:p></o:p></p>
<p class=3D"MsoNormal"><br>
[DB] I don't understand what this is for in the customer-managed case eithe=
r.&nbsp; If it is customer-managed, the customer already knows the manageme=
nt address, and the SP doesn't need to know it.&nbsp; I think it's only nee=
ded for co-managed, right?<br>
<br>
<span style=3D"color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">[SLI] Yes, I agree, will =
update accordingly<o:p></o:p></span></p>
<p class=3D"MsoNormal"><br>
<br>
<o:p></o:p></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l4 level1 lfo3">
Sn 5.10.2: You said before that the model can only manage P2P connections; =
but this figure (and the next one) show the PE connected to a LAN, not to a=
 CE.&nbsp; I am not sure how to interpret this?&nbsp; Isn't this a case whe=
re the connection is multipoint, not P2P?<o:p></o:p></li></ul>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">[SLI] That&#8217;s still point to point=
. In 5.10.3, customer must order two site network accesses (point
 to point). Each site network network access may be connected to a switch a=
t customer side (same one or not).</span><o:p></o:p></p>
<p class=3D"MsoNormal"><br>
[DB] If there is an L2 switch, then at L3 it is a multipoint connection - t=
he switch is part of the bearer.<br>
<span style=3D"color:#1F497D">[SLI] From a SP &nbsp;point of view no, in te=
rm of service, the customer will have to order two site-network-accesses. H=
ow they are connected to the customer network is not under the SP responsib=
ility. If the customer connects the two
 site-net-access on the same Lan through a switch, it becomes multipoint, b=
ut SP is not essentially aware of it.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><br>
<br>
&nbsp;&nbsp;&nbsp; David<br>
<br>
<br>
<br>
<o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre>David Ball<o:p></o:p></pre>
<pre><a href=3D"mailto:daviball@cisco.com">&lt;daviball@cisco.com&gt;</a><o=
:p></o:p></pre>
</div>
<PRE>______________________________________________________________________=
___________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.
</PRE></body>
</html>

--_000_9E32478DFA9976438E7A22F69B08FF921BC4C5F2OPEXCLILMA4corp_--


From nobody Thu Jun  9 23:58:15 2016
Return-Path: <stephane.litkowski@orange.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 96F1812D1B1 for <l3sm@ietfa.amsl.com>; Thu,  9 Jun 2016 23:58:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.345
X-Spam-Level: 
X-Spam-Status: No, score=-3.345 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 F_lvQ3wBwMPV for <l3sm@ietfa.amsl.com>; Thu,  9 Jun 2016 23:58:12 -0700 (PDT)
Received: from relais-inet.orange.com (relais-nor35.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA85512D097 for <l3sm@ietf.org>; Thu,  9 Jun 2016 23:58:11 -0700 (PDT)
Received: from opfednr06.francetelecom.fr (unknown [xx.xx.xx.70]) by opfednr26.francetelecom.fr (ESMTP service) with ESMTP id 6993420387; Fri, 10 Jun 2016 08:58:10 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.66]) by opfednr06.francetelecom.fr (ESMTP service) with ESMTP id 3C0EE1A005E; Fri, 10 Jun 2016 08:58:10 +0200 (CEST)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILMA1.corporate.adroot.infra.ftgroup ([fe80::95e2:eb4b:3053:fabf%19]) with mapi id 14.03.0294.000; Fri, 10 Jun 2016 08:58:09 +0200
From: <stephane.litkowski@orange.com>
To: Lucy yong <lucy.yong@huawei.com>, "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-08.txt
Thread-Index: AQHRwimKDx7H8IU3QUuz+M/AtvfoDJ/hSWnQgAD8RNA=
Date: Fri, 10 Jun 2016 06:58:09 +0000
Message-ID: <5074_1465541890_575A6502_5074_546_1_9E32478DFA9976438E7A22F69B08FF921BC4DA8A@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <2691CE0099834E4A9C5044EEC662BB9D57296AD0@dfweml501-mbb>
In-Reply-To: <2691CE0099834E4A9C5044EEC662BB9D57296AD0@dfweml501-mbb>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.3]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/0V1_bgMDU_cfHZbMgVTkXl_z-PI>
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-08.txt
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: Fri, 10 Jun 2016 06:58:13 -0000

Hi Lucy,

Please find some inline comments.

-----Original Message-----
From: Lucy yong [mailto:lucy.yong@huawei.com]=20
Sent: Thursday, June 09, 2016 19:21
To: LITKOWSKI Stephane OBS/OINIS; l3sm@ietf.org
Subject: FW: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-08.txt

Hi Stephane,

Thank you to address my comments/suggestions in these version.

Sn 5.1.2, The usage of cloud-access is targeted for
   public cloud.  Internet access can also be considered as a public
   cloud access service. The cloud-access container provides parameters
   for network address translation and authorization rules.

Need cloud-access container for Internet access but no need a cloud identif=
ier for Internet access, right? Good to state out it.
[SLI] You also need to cloud-id for Internet, the SP needs to allocate a pa=
rticular ID to identify an access to Internet (as for any other cloud)

One Caveat: you forget a description about the new figure under Sn 5.14.
[SLI] I added the description

Sn 5.14.1
   The cloud service provider or the customer itself may use our L3VPN
   service model exposed by service provider B to create the VPN
   connectivity.  We could consider that, as the NNI is shared, the
   physical connection (bearer) between CSP A and SP B already exists.
   CSPA may so request through a service model a new site creation with
   a single site-network-access (single homing used in the diagram).  As
   placement constraint, CSP A may use the existing bearer reference it
   has from SP A to force the placement of the VPN NNI on the existing
   link.

This is the case that multiple sites to share the same bearer between CSPA =
and SP A. This is different from subVPN case where it is related to a singl=
e site. It is important to point that out in Sn 5.2.1.1.
[SLI] I added a new flavor site-vpn-flavor-nni and added a text for this to=
 differentiate from regular sites.

On page 83,
 <site>
    <site-id>CSP_B_attachment</site-id>

Should it be CSP_A to align with the example?
[SLI] That was a mistake, thanks.

May consider add some description for cloud provider and SP interworking us=
ing option B and C as well.=20
[SLI] I added it for option B. Option C is exactly the same as option B fro=
m a service point of view, so I would like to avoid duplication.
Now the question is : do we add the appropriate modeling for option B/C ? a=
nd how ?

Thanks,
Lucy

=20

-----Original Message-----
From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of internet-drafts@ietf=
.org
Sent: Thursday, June 09, 2016 3:33 AM
To: i-d-announce@ietf.org
Cc: l3sm@ietf.org
Subject: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-08.txt


A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
This draft is a work item of the L3VPN Service Model  of the IETF.

        Title           : YANG Data Model for L3VPN service delivery
        Authors         : Stephane Litkowski
                          Rob Shakir
                          Luis Tomotaki
                          Kenichi Ogaki
                          Kevin D'Souza
	Filename        : draft-ietf-l3sm-l3vpn-service-model-08.txt
	Pages           : 156
	Date            : 2016-06-09

Abstract:
   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:
https://datatracker.ietf.org/doc/draft-ietf-l3sm-l3vpn-service-model/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-l3sm-l3vpn-service-model-08

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-l3sm-l3vpn-service-model-08


Please note that it may take a couple of minutes from the time of submissio=
n until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.


From nobody Fri Jun 10 00:03:20 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: l3sm@ietf.org
Delivered-To: l3sm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F30412B037; Fri, 10 Jun 2016 00:03:17 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.21.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160610070317.15379.68499.idtracker@ietfa.amsl.com>
Date: Fri, 10 Jun 2016 00:03:17 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/xO6LKj5cHoI7ouftVJsTWxNpgYk>
Cc: l3sm@ietf.org
Subject: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-09.txt
X-BeenThere: l3sm@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 10 Jun 2016 07:03:17 -0000

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

        Title           : YANG Data Model for L3VPN service delivery
        Authors         : Stephane Litkowski
                          Rob Shakir
                          Luis Tomotaki
                          Kenichi Ogaki
                          Kevin D'Souza
	Filename        : draft-ietf-l3sm-l3vpn-service-model-09.txt
	Pages           : 158
	Date            : 2016-06-10

Abstract:
   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:
https://datatracker.ietf.org/doc/draft-ietf-l3sm-l3vpn-service-model/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-l3sm-l3vpn-service-model-09

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-l3sm-l3vpn-service-model-09


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

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Jun 10 00:13:31 2016
Return-Path: <stephane.litkowski@orange.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 6EB0F12DAC6 for <l3sm@ietfa.amsl.com>; Fri, 10 Jun 2016 00:13:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.618
X-Spam-Level: 
X-Spam-Status: No, score=-2.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 xYv7D_TwzsV0 for <l3sm@ietfa.amsl.com>; Fri, 10 Jun 2016 00:13:22 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E71612DAB5 for <l3sm@ietf.org>; Fri, 10 Jun 2016 00:13:21 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm09.si.francetelecom.fr (ESMTP service) with ESMTP id BEFB42DC5A6 for <l3sm@ietf.org>; Fri, 10 Jun 2016 09:13:19 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.17]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 92858238059 for <l3sm@ietf.org>; Fri, 10 Jun 2016 09:13:19 +0200 (CEST)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM24.corporate.adroot.infra.ftgroup ([fe80::a1e6:3e6a:1f68:5f7e%19]) with mapi id 14.03.0294.000; Fri, 10 Jun 2016 09:13:19 +0200
From: <stephane.litkowski@orange.com>
To: "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: L3SM pending question :Do we model option B/C NNI and how ?
Thread-Index: AdHC5ksvBflqsN0uRnGWrH6M59opvQ==
Date: Fri, 10 Jun 2016 07:13:18 +0000
Message-ID: <26703_1465542799_575A688F_26703_538_3_9E32478DFA9976438E7A22F69B08FF921BC4DB76@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.3]
Content-Type: multipart/related; boundary="_004_9E32478DFA9976438E7A22F69B08FF921BC4DB76OPEXCLILMA4corp_"; type="multipart/alternative"
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.6.7.90315
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/zREh-LKoRcLgPzxBQwCDA6NaOVg>
Subject: [L3sm] L3SM pending question :Do we model option B/C NNI and how ?
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: Fri, 10 Jun 2016 07:13:24 -0000

--_004_9E32478DFA9976438E7A22F69B08FF921BC4DB76OPEXCLILMA4corp_
Content-Type: multipart/alternative;
	boundary="_000_9E32478DFA9976438E7A22F69B08FF921BC4DB76OPEXCLILMA4corp_"


--_000_9E32478DFA9976438E7A22F69B08FF921BC4DB76OPEXCLILMA4corp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

Starting v07 we described the NNI scenarios.
NNI option A is modeled as a site.
NNI option B and C are described but not modeled yet but the requirements a=
re expressed :

-          Need to authorize the route-target

-          Need to associate RT value in one network with the value in the =
other network (optional). One of the issue that the current model does not =
deal with RT.


1)      Do we model it ?

2)      How ? here are two proposals :

a)      Creating a new top-level container called optionbc-nni like :



Optionbc-nni {

        List nni {

                        Leaf nni-reference {

                                        // There is a need of discussion be=
tween SP to agree on nni-references to use

                        }

                        Container authorized-rts {

                                        List rt {

                                                        Leaf rt {



                                                        }

                                                        Leaf translate-to {



                                                        }

                                        }

                        }

}

}



b)      Renaming site container to vpn-connection and site-network-access t=
o vpn-access, add a flavor nni-optionbc and add a container within vpn-conn=
ection to describe the connection. This container is only usable when flavo=
r is nni-optionbc, other containers of the vpn-connection cannot be used wh=
en flavor is nni-optionbc


Thoughts ?
[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/OINIS/NET
Orange Expert Future Networks
phone: +33 2 23 28 49 83 <https://monsi.sso.francetelecom.fr/index.asp?targ=
et=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do=
%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049=
%2083%20>
mobile: +33 6 37 86 97 52 <https://monsi.sso.francetelecom.fr/index.asp?tar=
get=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.d=
o%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%209=
7%2052%20>
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.


--_000_9E32478DFA9976438E7A22F69B08FF921BC4DB76OPEXCLILMA4corp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:483619900;
	mso-list-type:hybrid;
	mso-list-template-ids:623966204 357477344 67698691 67698693 67698689 67698=
691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1
	{mso-list-id:1062484651;
	mso-list-type:hybrid;
	mso-list-template-ids:1882985464 67698705 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2
	{mso-list-id:1430203293;
	mso-list-type:hybrid;
	mso-list-template-ids:-928728192 374362934 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l2:level1
	{mso-level-number-format:alpha-lower;
	mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.75in;
	text-indent:-.25in;}
@list l2:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.25in;
	text-indent:-.25in;}
@list l2:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:1.75in;
	text-indent:-9.0pt;}
@list l2:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:2.25in;
	text-indent:-.25in;}
@list l2:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:2.75in;
	text-indent:-.25in;}
@list l2:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:3.25in;
	text-indent:-9.0pt;}
@list l2:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:3.75in;
	text-indent:-.25in;}
@list l2:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:4.25in;
	text-indent:-.25in;}
@list l2:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:4.75in;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Starting v07 we described the NNI scenarios.<o:p></o=
:p></p>
<p class=3D"MsoNormal">NNI option A is modeled as a site.<o:p></o:p></p>
<p class=3D"MsoNormal">NNI option B and C are described but not modeled yet=
 but the requirements are expressed :<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Need to authorize the route-target<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Need to associate RT value in one network with the =
value in the other network (optional). One of the issue that the current mo=
del does not deal with RT.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">1)<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Do we model it ?<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">2)<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>How ? here are two proposals :<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in;text-indent:-.25in=
;mso-list:l2 level1 lfo3">
<![if !supportLists]><span style=3D"mso-list:Ignore">a)<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Creating a new top-level container called optionbc-=
nni like :<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in"><o:p>&nbsp;</o:p>=
</p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in">Optionbc-nni {<o:=
p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in">&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; List nni {<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in">&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Leaf nni-reference {<o:p></o=
:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in">&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // Ther=
e is a need of discussion between SP to agree on nni-references to use<o:p>=
</o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in">&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in">&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Container authorized-rts {<o=
:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in">&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List rt=
 {<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in">&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; Leaf rt {<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in"><o:p>&nbsp;</o:p>=
</p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in">&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; }<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in">&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; Leaf translate-to {<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in"><o:p>&nbsp;</o:p>=
</p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in">&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; }<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in">&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<o:p><=
/o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in">&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in;text-indent:.25in"=
>}<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in">}<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in"><o:p>&nbsp;</o:p>=
</p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in;text-indent:-.25in=
;mso-list:l2 level1 lfo3">
<![if !supportLists]><span style=3D"mso-list:Ignore">b)<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Renaming site container to vpn-connection and site-=
network-access to vpn-access, add a flavor nni-optionbc and add a container=
 within vpn-connection to describe the connection. This container is only u=
sable when flavor is nni-optionbc,
 other containers of the vpn-connection cannot be used when flavor is nni-o=
ptionbc<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;">Thoughts ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><a href=3D"http://www.orange.com/"><span style=3D"fo=
nt-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;co=
lor:blue;text-decoration:none"><img border=3D"0" width=3D"40" height=3D"40"=
 id=3D"Picture_x0020_1" src=3D"cid:image001.jpg@01D1C2F7.75A82700" alt=3D"O=
range logo"></span></a><span lang=3D"FR" style=3D"font-size:12.0pt;font-fam=
ily:&quot;Times New Roman&quot;,&quot;serif&quot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;">&nbsp;<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;;color:black">Stephane Litkowski
</span></b><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roma=
n&quot;,&quot;serif&quot;"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:black">Network Architect
</span><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&qu=
ot;,&quot;serif&quot;"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:black">Orange/SCE/EQUANT/OINIS/NET</span><span style=
=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&qu=
ot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">Orange Expert Fut=
ure Networks</span><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:=
&quot;Times New Roman&quot;,&quot;serif&quot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">phone:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%202%2023%2028%2049%2083%20">
<span style=3D"color:black">&#43;33 2 23 28 49 83 </span></a></span><span l=
ang=3D"FR" style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot=
;,&quot;serif&quot;"><br>
</span><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Arial&=
quot;,&quot;sans-serif&quot;;color:black">mobile:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%206%2037%2086%2097%2052%20">
<span style=3D"color:black">&#43;33 6 37 86 97 52 </span></a></span><span l=
ang=3D"FR" style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot=
;,&quot;serif&quot;"><br>
<a href=3D"mailto:stephane.litkowski@orange.com"><span style=3D"font-size:1=
0.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#FF6600">s=
tephane.litkowski@orange.com</span></a>
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<PRE>______________________________________________________________________=
___________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.
</PRE></body>
</html>

--_000_9E32478DFA9976438E7A22F69B08FF921BC4DB76OPEXCLILMA4corp_--

--_004_9E32478DFA9976438E7A22F69B08FF921BC4DB76OPEXCLILMA4corp_
Content-Type: image/jpeg; name="image001.jpg"
Content-Description: image001.jpg
Content-Disposition: inline; filename="image001.jpg"; size=1093;
	creation-date="Fri, 10 Jun 2016 07:13:18 GMT";
	modification-date="Fri, 10 Jun 2016 07:13:18 GMT"
Content-ID: <image001.jpg@01D1C2F7.75A82700>
Content-Transfer-Encoding: base64

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRofHh0a
HBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwhMjIyMjIy
MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAARCAAoACgDASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD1O48f
afbXMsDWl0WjcoSAuDg49aj/AOFiad/z53f5L/jXB6r/AMhe9/67v/M1Ur5Geb4pSaTX3H2dPJcJ
KCbT+89H/wCFiad/z53f5L/jR/wsTTv+fO7/ACX/ABrziip/tnFd19xX9iYPs/vPR/8AhYmnf8+d
3+S/40V5xRR/bOK7r7g/sTB9n95b1X/kL3v/AF3f+ZqpW3Po17qGo3s0Cx7DdPGpeQLvbOdq56mo
R4d1EmEFYVaZdyI0oDY9cda450KspNqLO2niKUYJOSvbv5GVRWwPC+qmR4zFErI/l4aUDc2A2B68
GmDw7qTQrIIkJZVYR+YN+GOAdvuan6tW/lf3FfWqH86+8yqK2bjQG0+EvqU/2dmyIgieYGI6gkHg
0VM6M4O0tGVCtCavF3R1o8Oa7BcTtbXdh5TztPGJYyxjY9xxwcUxfDniNZ1m+32DOIPs+WjJymc8
8dc96KK+y/s+l3f3s+J/tKt2X3Ie+geJZJlla/0/eswmH7s/eChfT0FXDo2rDTRCktoLoIqfaCxy
NrZGPlz+GaKKpYGmr6vXzJlj6sraLTyMrUPCOuant+03lh8pJ+RGXJPUniiiisZ5Thpvmldv1N4Z
xioLljZL0R//2Q==

--_004_9E32478DFA9976438E7A22F69B08FF921BC4DB76OPEXCLILMA4corp_--


From nobody Fri Jun 10 00:17:53 2016
Return-Path: <stephane.litkowski@orange.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 1BD4212DAC4 for <l3sm@ietfa.amsl.com>; Fri, 10 Jun 2016 00:17:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.618
X-Spam-Level: 
X-Spam-Status: No, score=-2.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 rMpbvHcvzRfi for <l3sm@ietfa.amsl.com>; Fri, 10 Jun 2016 00:17:49 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04D1F12B046 for <l3sm@ietf.org>; Fri, 10 Jun 2016 00:17:49 -0700 (PDT)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 93FB3324A0A for <l3sm@ietf.org>; Fri, 10 Jun 2016 09:17:47 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.69]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id 6E35C27C059 for <l3sm@ietf.org>; Fri, 10 Jun 2016 09:17:47 +0200 (CEST)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILMA2.corporate.adroot.infra.ftgroup ([fe80::bc1c:ad2f:eda3:8c3d%18]) with mapi id 14.03.0294.000; Fri, 10 Jun 2016 09:17:47 +0200
From: <stephane.litkowski@orange.com>
To: "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: L3SM pending question : do we remove templates ?
Thread-Index: AdHC5/UzVHHDUX6WRsyttooNlA2NDg==
Date: Fri, 10 Jun 2016 07:17:46 +0000
Message-ID: <22833_1465543067_575A699B_22833_61_1_9E32478DFA9976438E7A22F69B08FF921BC4DBCB@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.3]
Content-Type: multipart/related; boundary="_004_9E32478DFA9976438E7A22F69B08FF921BC4DBCBOPEXCLILMA4corp_"; type="multipart/alternative"
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.6.7.90315
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/mNTO1PX0_S2kUY6KuSOu9Ogg3FM>
Subject: [L3sm] L3SM pending question : do we remove templates ?
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: Fri, 10 Jun 2016 07:17:51 -0000

--_004_9E32478DFA9976438E7A22F69B08FF921BC4DBCBOPEXCLILMA4corp_
Content-Type: multipart/alternative;
	boundary="_000_9E32478DFA9976438E7A22F69B08FF921BC4DBCBOPEXCLILMA4corp_"


--_000_9E32478DFA9976438E7A22F69B08FF921BC4DBCBOPEXCLILMA4corp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

Concerns were raised on the list of having a template mechanism in L3SM whi=
ch is orthogonal to L3SM : templates may be useful in YANG modeling globall=
y. Moreover there may be a need to express exact rules of template applicat=
ion.

So the question is : is there a consensus to remove site-templates from L3S=
M ?

Thanks,


[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/OINIS/NET
Orange Expert Future Networks
phone: +33 2 23 28 49 83 <https://monsi.sso.francetelecom.fr/index.asp?targ=
et=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do=
%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049=
%2083%20>
mobile: +33 6 37 86 97 52 <https://monsi.sso.francetelecom.fr/index.asp?tar=
get=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.d=
o%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%209=
7%2052%20>
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.


--_000_9E32478DFA9976438E7A22F69B08FF921BC4DBCBOPEXCLILMA4corp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Concerns were raised on the list of having a templat=
e mechanism in L3SM which is orthogonal to L3SM : templates may be useful i=
n YANG modeling globally. Moreover there may be a need to express exact rul=
es of template application.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">So the question is : is there a consensus to remove =
site-templates from L3SM ?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;">Thanks,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><a href=3D"http://www.orange.com/"><span style=3D"fo=
nt-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;co=
lor:blue;text-decoration:none"><img border=3D"0" width=3D"40" height=3D"40"=
 id=3D"Picture_x0020_1" src=3D"cid:image001.jpg@01D1C2F8.F33A7EB0" alt=3D"O=
range logo"></span></a><span lang=3D"FR" style=3D"font-size:12.0pt;font-fam=
ily:&quot;Times New Roman&quot;,&quot;serif&quot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;">&nbsp;<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;;color:black">Stephane Litkowski
</span></b><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roma=
n&quot;,&quot;serif&quot;"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:black">Network Architect
</span><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&qu=
ot;,&quot;serif&quot;"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:black">Orange/SCE/EQUANT/OINIS/NET</span><span style=
=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&qu=
ot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">Orange Expert Fut=
ure Networks</span><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:=
&quot;Times New Roman&quot;,&quot;serif&quot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">phone:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%202%2023%2028%2049%2083%20">
<span style=3D"color:black">&#43;33 2 23 28 49 83 </span></a></span><span l=
ang=3D"FR" style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot=
;,&quot;serif&quot;"><br>
</span><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Arial&=
quot;,&quot;sans-serif&quot;;color:black">mobile:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%206%2037%2086%2097%2052%20">
<span style=3D"color:black">&#43;33 6 37 86 97 52 </span></a></span><span l=
ang=3D"FR" style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot=
;,&quot;serif&quot;"><br>
<a href=3D"mailto:stephane.litkowski@orange.com"><span style=3D"font-size:1=
0.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#FF6600">s=
tephane.litkowski@orange.com</span></a>
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<PRE>______________________________________________________________________=
___________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.
</PRE></body>
</html>

--_000_9E32478DFA9976438E7A22F69B08FF921BC4DBCBOPEXCLILMA4corp_--

--_004_9E32478DFA9976438E7A22F69B08FF921BC4DBCBOPEXCLILMA4corp_
Content-Type: image/jpeg; name="image001.jpg"
Content-Description: image001.jpg
Content-Disposition: inline; filename="image001.jpg"; size=1093;
	creation-date="Fri, 10 Jun 2016 07:17:46 GMT";
	modification-date="Fri, 10 Jun 2016 07:17:46 GMT"
Content-ID: <image001.jpg@01D1C2F8.F33A7EB0>
Content-Transfer-Encoding: base64

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRofHh0a
HBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwhMjIyMjIy
MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAARCAAoACgDASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD1O48f
afbXMsDWl0WjcoSAuDg49aj/AOFiad/z53f5L/jXB6r/AMhe9/67v/M1Ur5Geb4pSaTX3H2dPJcJ
KCbT+89H/wCFiad/z53f5L/jR/wsTTv+fO7/ACX/ABrziip/tnFd19xX9iYPs/vPR/8AhYmnf8+d
3+S/40V5xRR/bOK7r7g/sTB9n95b1X/kL3v/AF3f+ZqpW3Po17qGo3s0Cx7DdPGpeQLvbOdq56mo
R4d1EmEFYVaZdyI0oDY9cda450KspNqLO2niKUYJOSvbv5GVRWwPC+qmR4zFErI/l4aUDc2A2B68
GmDw7qTQrIIkJZVYR+YN+GOAdvuan6tW/lf3FfWqH86+8yqK2bjQG0+EvqU/2dmyIgieYGI6gkHg
0VM6M4O0tGVCtCavF3R1o8Oa7BcTtbXdh5TztPGJYyxjY9xxwcUxfDniNZ1m+32DOIPs+WjJymc8
8dc96KK+y/s+l3f3s+J/tKt2X3Ie+geJZJlla/0/eswmH7s/eChfT0FXDo2rDTRCktoLoIqfaCxy
NrZGPlz+GaKKpYGmr6vXzJlj6sraLTyMrUPCOuant+03lh8pJ+RGXJPUniiiisZ5Thpvmldv1N4Z
xioLljZL0R//2Q==

--_004_9E32478DFA9976438E7A22F69B08FF921BC4DBCBOPEXCLILMA4corp_--


From nobody Fri Jun 10 04:29:30 2016
Return-Path: <daviball@cisco.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 CED8512D534 for <l3sm@ietfa.amsl.com>; Fri, 10 Jun 2016 04:29:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.946
X-Spam-Level: 
X-Spam-Status: No, score=-15.946 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_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-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 fqXC2DbxjCGd for <l3sm@ietfa.amsl.com>; Fri, 10 Jun 2016 04:29:27 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4C6212D0E6 for <l3sm@ietf.org>; Fri, 10 Jun 2016 04:29:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=18722; q=dns/txt; s=iport; t=1465558166; x=1466767766; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=ubD/aXrE/+kvrbIAmmTGts9KqzRTpPbG0SM5zJp3LY4=; b=krv4V3jdWawoIhk6Gb+4zTGxwgBFA+HTbDvLwc8VI0cm+BT7lVJCzyBH gy+9CvouMQgbuct30V23V9cBUA0Gz3LV5ESF6Pq91HN6Re/UuUSsDqcEk 94yTFk97ICiO6pDsuOCHJj+AMPdC5FMDE/o2Mt0Qd+sIh/GCfr3yKsvk0 c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CqBAAjo1pX/xbLJq1dgnCBT1K9HYYTA?= =?us-ascii?q?oF/AQEBAQEBZieERgEBBC1cCxggDlcGAQwGAgEBiCy+HAEBAQEBAQEBAQEBAQE?= =?us-ascii?q?BAQEBAQEBARyGJ4F3glaKGwWIDJBTiHyFLIlEhVyPa1SCBxyBTDsyiggBAQE?=
X-IronPort-AV: E=Sophos;i="5.26,449,1459814400";  d="scan'208,217";a="636113251"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Jun 2016 11:29:24 +0000
Received: from [10.63.23.103] (dhcp-ensft1-uk-vla370-10-63-23-103.cisco.com [10.63.23.103]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id u5ABTNVY006236; Fri, 10 Jun 2016 11:29:23 GMT
To: stephane.litkowski@orange.com, "l3sm@ietf.org" <l3sm@ietf.org>
References: <20160606141710.20806.10098.idtracker@ietfa.amsl.com> <27218_1465222795_5755868B_27218_684_1_9E32478DFA9976438E7A22F69B08FF921BC41DA1@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <ec72f8b8-8626-ba2c-bc50-7ce4a0cdc6df@cisco.com> <32265_1465379094_5757E916_32265_10098_3_9E32478DFA9976438E7A22F69B08FF921BC454AB@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <1595f5bb-1838-8164-6e7f-1d383d8bfb87@cisco.com> <7576_1465499325_5759BEBD_7576_3122_1_9E32478DFA9976438E7A22F69B08FF921BC4C5F2@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
From: David Ball <daviball@cisco.com>
Message-ID: <bf0bd488-ff9e-ae4e-b37c-6123ae63a8ee@cisco.com>
Date: Fri, 10 Jun 2016 12:29:23 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <7576_1465499325_5759BEBD_7576_3122_1_9E32478DFA9976438E7A22F69B08FF921BC4C5F2@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
Content-Type: multipart/alternative; boundary="------------5B08318DEDB7A8F9D9D2ECA9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/xRBaqngP8UxRcBSGzInhzoe3du8>
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
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: Fri, 10 Jun 2016 11:29:29 -0000

This is a multi-part message in MIME format.
--------------5B08318DEDB7A8F9D9D2ECA9
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

Hi Stephane,

More inline:

On 09/06/2016 20:08, stephane.litkowski@orange.com wrote:
>
>   * Sn 5.10.2: You said before that the model can only manage P2P
>     connections; but this figure (and the next one) show the PE
>     connected to a LAN, not to a CE.  I am not sure how to interpret
>     this?  Isn't this a case where the connection is multipoint, not P2P?
>
> [SLI] That’s still point to point. In 5.10.3, customer must order two 
> site network accesses (point to point). Each site network network 
> access may be connected to a switch at customer side (same one or not).
>
>
> [DB] If there is an L2 switch, then at L3 it is a multipoint 
> connection - the switch is part of the bearer.
> [SLI] From a SP  point of view no, in term of service, the customer 
> will have to order two site-network-accesses. How they are connected 
> to the customer network is not under the SP responsibility. If the 
> customer connects the two site-net-access on the same Lan through a 
> switch, it becomes multipoint, but SP is not essentially aware of it.
>

[DB] I think we may be talking about different cases.  I don't mean it 
may be multipoint because there are multiple site-network-accesses, I'm 
talking about the case where there are multiple devices at the customer 
side (could be one or multiple site-network-accesses) - rather than a 
single CE terminating the L3 connection.  This seems to be what the 
figure in Sn 5.10.2 is showing.

   Host1 ------\
   Host2 ---- Switch ---------- PE
   Host3 ------/

I don't think it's entirely true in this case that the SP does not need 
to be aware of it - for instance, if the connection address is dynamic, 
the SP may need to allocate multiple addresses instead of just 1.  It 
also has some impact on other aspects of the model; for instance, the 
routing protocol probably needs to be direct or static (not an absolute 
requirement but probably true in practice), and BFD and IPSec probably 
need to be disabled (since these are inherently P2P).


     David


-- 
David Ball
<daviball@cisco.com>


--------------5B08318DEDB7A8F9D9D2ECA9
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi Stephane,<br>
    <br>
    More inline:<br>
    <br>
    <div class="moz-cite-prefix">On 09/06/2016 20:08,
      <a class="moz-txt-link-abbreviated" href="mailto:stephane.litkowski@orange.com">stephane.litkowski@orange.com</a> wrote:<br>
    </div>
    <blockquote
cite="mid:7576_1465499325_5759BEBD_7576_3122_1_9E32478DFA9976438E7A22F69B08FF921BC4C5F2@OPEXCLILMA4.corporate.adroot.infra.ftgroup"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <meta name="Generator" content="Microsoft Word 14 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	color:black;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:464737076;
	mso-list-template-ids:1294353514;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1
	{mso-list-id:1082293066;
	mso-list-template-ids:492234094;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2
	{mso-list-id:1087075688;
	mso-list-template-ids:-296046016;}
@list l2:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3
	{mso-list-id:1590500162;
	mso-list-template-ids:-584673594;}
@list l3:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l4
	{mso-list-id:1656761572;
	mso-list-template-ids:-682878950;}
@list l4:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l4:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l4:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l4:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l4:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l4:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l4:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l4:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l4:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1"><br>
        <o:p></o:p>
        <ul type="disc">
          <li class="MsoNormal"
            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l4
            level1 lfo3">
            Sn 5.10.2: You said before that the model can only manage
            P2P connections; but this figure (and the next one) show the
            PE connected to a LAN, not to a CE.  I am not sure how to
            interpret this?  Isn't this a case where the connection is
            multipoint, not P2P?<o:p></o:p></li>
        </ul>
        <p class="MsoNormal"
          style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">[SLI]
            That’s still point to point. In 5.10.3, customer must order
            two site network accesses (point to point). Each site
            network network access may be connected to a switch at
            customer side (same one or not).</span><o:p></o:p></p>
        <p class="MsoNormal"><br>
          [DB] If there is an L2 switch, then at L3 it is a multipoint
          connection - the switch is part of the bearer.<br>
          <span style="color:#1F497D">[SLI] From a SP  point of view no,
            in term of service, the customer will have to order two
            site-network-accesses. How they are connected to the
            customer network is not under the SP responsibility. If the
            customer connects the two site-net-access on the same Lan
            through a switch, it becomes multipoint, but SP is not
            essentially aware of it.</span></p>
      </div>
    </blockquote>
    <br>
    [DB] I think we may be talking about different cases.  I don't mean
    it may be multipoint because there are multiple
    site-network-accesses, I'm talking about the case where there are
    multiple devices at the customer side (could be one or multiple
    site-network-accesses) - rather than a single CE terminating the L3
    connection.  This seems to be what the figure in Sn 5.10.2 is
    showing.<br>
    <br>
    <tt>  Host1 ------\</tt><tt><br>
    </tt><tt>  Host2 ---- Switch ---------- PE<br>
        Host3 ------/<br>
    </tt><br>
    I don't think it's entirely true in this case that the SP does not
    need to be aware of it - for instance, if the connection address is
    dynamic, the SP may need to allocate multiple addresses instead of
    just 1.  It also has some impact on other aspects of the model; for
    instance, the routing protocol probably needs to be direct or static
    (not an absolute requirement but probably true in practice), and BFD
    and IPSec probably need to be disabled (since these are inherently
    P2P).<br>
    <br>
    <br>
        David<br>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
David Ball
<a class="moz-txt-link-rfc2396E" href="mailto:daviball@cisco.com">&lt;daviball@cisco.com&gt;</a></pre>
  </body>
</html>

--------------5B08318DEDB7A8F9D9D2ECA9--


From nobody Tue Jun 14 04:31:43 2016
Return-Path: <michael.scharf@nokia.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 5338112DB91 for <l3sm@ietfa.amsl.com>; Tue, 14 Jun 2016 04:31:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-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 WVvt7lxlW8bN for <l3sm@ietfa.amsl.com>; Tue, 14 Jun 2016 04:31:39 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B571112DB86 for <l3sm@ietf.org>; Tue, 14 Jun 2016 04:31:38 -0700 (PDT)
Received: from fr712umx3.dmz.alcatel-lucent.com (unknown [135.245.210.42]) by Websense Email Security Gateway with ESMTPS id BF1AB144C8EF5; Tue, 14 Jun 2016 11:31:34 +0000 (GMT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (fr711usmtp1.zeu.alcatel-lucent.com [135.239.2.122]) by fr712umx3.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u5EBVac2008385 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 14 Jun 2016 11:31:36 GMT
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id u5EBVOn7007875 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 14 Jun 2016 13:31:36 +0200
Received: from FR712WXCHMBA15.zeu.alcatel-lucent.com ([169.254.7.34]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.03.0195.001; Tue, 14 Jun 2016 13:31:28 +0200
From: "Scharf, Michael (Nokia - DE)" <michael.scharf@nokia.com>
To: "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>, "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: L3SM pending question : do we remove templates ?
Thread-Index: AdHC5/UzVHHDUX6WRsyttooNlA2NDgDR146w
Date: Tue, 14 Jun 2016 11:31:27 +0000
Message-ID: <655C07320163294895BBADA28372AF5D488D2743@FR712WXCHMBA15.zeu.alcatel-lucent.com>
References: <22833_1465543067_575A699B_22833_61_1_9E32478DFA9976438E7A22F69B08FF921BC4DBCB@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
In-Reply-To: <22833_1465543067_575A699B_22833_61_1_9E32478DFA9976438E7A22F69B08FF921BC4DBCB@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.38]
Content-Type: multipart/related; boundary="_004_655C07320163294895BBADA28372AF5D488D2743FR712WXCHMBA15z_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/ZjVVEpBVjR6fBrWbZknEKX68_2o>
Subject: Re: [L3sm] L3SM pending question : do we remove templates ?
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: Tue, 14 Jun 2016 11:31:41 -0000

--_004_655C07320163294895BBADA28372AF5D488D2743FR712WXCHMBA15z_
Content-Type: multipart/alternative;
	boundary="_000_655C07320163294895BBADA28372AF5D488D2743FR712WXCHMBA15z_"

--_000_655C07320163294895BBADA28372AF5D488D2743FR712WXCHMBA15z_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

As mentioned before, I fully agree that this is orthogonal.

If there was no consensus to remove site templates, perhaps the templates c=
ould be made optional, for instance by moving site-template a separate YANG=
 data model within the I-D (e.g., by import/include)?

Michael


From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of stephane.litkowski@o=
range.com
Sent: Friday, June 10, 2016 9:18 AM
To: l3sm@ietf.org
Subject: [L3sm] L3SM pending question : do we remove templates ?

Hi,

Concerns were raised on the list of having a template mechanism in L3SM whi=
ch is orthogonal to L3SM : templates may be useful in YANG modeling globall=
y. Moreover there may be a need to express exact rules of template applicat=
ion.

So the question is : is there a consensus to remove site-templates from L3S=
M ?

Thanks,


[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/OINIS/NET
Orange Expert Future Networks
phone: +33 2 23 28 49 83 <https://monsi.sso.francetelecom.fr/index.asp?targ=
et=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do=
%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049=
%2083%20>
mobile: +33 6 37 86 97 52 <https://monsi.sso.francetelecom.fr/index.asp?tar=
get=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.d=
o%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%209=
7%2052%20>
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>


___________________________________________________________________________=
______________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.

--_000_655C07320163294895BBADA28372AF5D488D2743FR712WXCHMBA15z_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">As mentioned before, I=
 fully agree that this is orthogonal.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">If there was no consen=
sus to remove site templates, perhaps the templates could be made optional,=
 for instance by moving site-template a separate YANG data model within the=
 I-D (e.g., by import/include)?
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Michael<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> L3sm [ma=
ilto:l3sm-bounces@ietf.org]
<b>On Behalf Of </b>stephane.litkowski@orange.com<br>
<b>Sent:</b> Friday, June 10, 2016 9:18 AM<br>
<b>To:</b> l3sm@ietf.org<br>
<b>Subject:</b> [L3sm] L3SM pending question : do we remove templates ?<o:p=
></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Concerns were raised on the list of having a templat=
e mechanism in L3SM which is orthogonal to L3SM : templates may be useful i=
n YANG modeling globally. Moreover there may be a need to express exact rul=
es of template application.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">So the question is : is there a consensus to remove =
site-templates from L3SM ?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;">Thanks,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><a href=3D"http://www.orange.com/"><span style=3D"fo=
nt-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;te=
xt-decoration:none"><img border=3D"0" width=3D"40" height=3D"40" id=3D"Pict=
ure_x0020_1" src=3D"cid:image001.jpg@01D1C640.A15F02A0" alt=3D"Orange logo"=
></span></a><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:&quot;T=
imes New Roman&quot;,&quot;serif&quot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;">&nbsp;<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;;color:black">Stephane Litkowski
</span></b><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roma=
n&quot;,&quot;serif&quot;"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:black">Network Architect
</span><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&qu=
ot;,&quot;serif&quot;"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:black">Orange/SCE/EQUANT/OINIS/NET</span><span style=
=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&qu=
ot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">Orange Expert Fut=
ure Networks</span><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:=
&quot;Times New Roman&quot;,&quot;serif&quot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">phone:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%202%2023%2028%2049%2083%20">
<span style=3D"color:black">&#43;33 2 23 28 49 83 </span></a></span><span l=
ang=3D"FR" style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot=
;,&quot;serif&quot;"><br>
</span><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Arial&=
quot;,&quot;sans-serif&quot;;color:black">mobile:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%206%2037%2086%2097%2052%20">
<span style=3D"color:black">&#43;33 6 37 86 97 52 </span></a></span><span l=
ang=3D"FR" style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot=
;,&quot;serif&quot;"><br>
<a href=3D"mailto:stephane.litkowski@orange.com"><span style=3D"font-size:1=
0.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#FF6600">s=
tephane.litkowski@orange.com</span></a>
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<pre>______________________________________________________________________=
___________________________________________________<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Ce message et ses pieces jointes peuvent contenir des informations con=
fidentielles ou privilegiees et ne doivent donc<o:p></o:p></pre>
<pre>pas etre diffuses, exploites ou copies sans autorisation. Si vous avez=
 recu ce message par erreur, veuillez le signaler<o:p></o:p></pre>
<pre>a l'expediteur et le detruire ainsi que les pieces jointes. Les messag=
es electroniques etant susceptibles d'alteration,<o:p></o:p></pre>
<pre>Orange decline toute responsabilite si ce message a ete altere, deform=
e ou falsifie. Merci.<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>This message and its attachments may contain confidential or privilege=
d information that may be protected by law;<o:p></o:p></pre>
<pre>they should not be distributed, used or copied without authorisation.<=
o:p></o:p></pre>
<pre>If you have received this email in error, please notify the sender and=
 delete this message and its attachments.<o:p></o:p></pre>
<pre>As emails may be altered, Orange is not liable for messages that have =
been modified, changed or falsified.<o:p></o:p></pre>
<pre>Thank you.<o:p></o:p></pre>
</div>
</body>
</html>

--_000_655C07320163294895BBADA28372AF5D488D2743FR712WXCHMBA15z_--

--_004_655C07320163294895BBADA28372AF5D488D2743FR712WXCHMBA15z_
Content-Type: image/jpeg; name="image001.jpg"
Content-Description: image001.jpg
Content-Disposition: inline; filename="image001.jpg"; size=1093;
	creation-date="Tue, 14 Jun 2016 11:31:26 GMT";
	modification-date="Tue, 14 Jun 2016 11:31:26 GMT"
Content-ID: <image001.jpg@01D1C640.A15F02A0>
Content-Transfer-Encoding: base64

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRofHh0a
HBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwhMjIyMjIy
MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAARCAAoACgDASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD1O48f
afbXMsDWl0WjcoSAuDg49aj/AOFiad/z53f5L/jXB6r/AMhe9/67v/M1Ur5Geb4pSaTX3H2dPJcJ
KCbT+89H/wCFiad/z53f5L/jR/wsTTv+fO7/ACX/ABrziip/tnFd19xX9iYPs/vPR/8AhYmnf8+d
3+S/40V5xRR/bOK7r7g/sTB9n95b1X/kL3v/AF3f+ZqpW3Po17qGo3s0Cx7DdPGpeQLvbOdq56mo
R4d1EmEFYVaZdyI0oDY9cda450KspNqLO2niKUYJOSvbv5GVRWwPC+qmR4zFErI/l4aUDc2A2B68
GmDw7qTQrIIkJZVYR+YN+GOAdvuan6tW/lf3FfWqH86+8yqK2bjQG0+EvqU/2dmyIgieYGI6gkHg
0VM6M4O0tGVCtCavF3R1o8Oa7BcTtbXdh5TztPGJYyxjY9xxwcUxfDniNZ1m+32DOIPs+WjJymc8
8dc96KK+y/s+l3f3s+J/tKt2X3Ie+geJZJlla/0/eswmH7s/eChfT0FXDo2rDTRCktoLoIqfaCxy
NrZGPlz+GaKKpYGmr6vXzJlj6sraLTyMrUPCOuant+03lh8pJ+RGXJPUniiiisZ5Thpvmldv1N4Z
xioLljZL0R//2Q==

--_004_655C07320163294895BBADA28372AF5D488D2743FR712WXCHMBA15z_--


From nobody Tue Jun 14 05:39:32 2016
Return-Path: <stephane.litkowski@orange.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 E1AC512B04F for <l3sm@ietfa.amsl.com>; Tue, 14 Jun 2016 05:39:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.344
X-Spam-Level: 
X-Spam-Status: No, score=-3.344 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 jWG6SItKMmJZ for <l3sm@ietfa.amsl.com>; Tue, 14 Jun 2016 05:39:27 -0700 (PDT)
Received: from relais-inet.orange.com (relais-nor36.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BE3712D12B for <l3sm@ietf.org>; Tue, 14 Jun 2016 05:39:27 -0700 (PDT)
Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) by opfednr24.francetelecom.fr (ESMTP service) with ESMTP id 6441E40122; Tue, 14 Jun 2016 14:39:25 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.57]) by opfednr04.francetelecom.fr (ESMTP service) with ESMTP id 273E640068; Tue, 14 Jun 2016 14:39:25 +0200 (CEST)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM23.corporate.adroot.infra.ftgroup ([fe80::787e:db0c:23c4:71b3%19]) with mapi id 14.03.0294.000; Tue, 14 Jun 2016 14:39:24 +0200
From: <stephane.litkowski@orange.com>
To: "Scharf, Michael (Nokia - DE)" <michael.scharf@nokia.com>, "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: L3SM pending question : do we remove templates ?
Thread-Index: AdHC5/UzVHHDUX6WRsyttooNlA2NDgDR146wAAKZBaA=
Date: Tue, 14 Jun 2016 12:39:24 +0000
Message-ID: <30226_1465907965_575FFAFD_30226_2747_29_9E32478DFA9976438E7A22F69B08FF921BC5BA19@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <22833_1465543067_575A699B_22833_61_1_9E32478DFA9976438E7A22F69B08FF921BC4DBCB@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <655C07320163294895BBADA28372AF5D488D2743@FR712WXCHMBA15.zeu.alcatel-lucent.com>
In-Reply-To: <655C07320163294895BBADA28372AF5D488D2743@FR712WXCHMBA15.zeu.alcatel-lucent.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
Content-Type: multipart/related; boundary="_004_9E32478DFA9976438E7A22F69B08FF921BC5BA19OPEXCLILMA4corp_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/bKEcVHw_LYy3BZFiYjJkjPKs-Zw>
Subject: Re: [L3sm] L3SM pending question : do we remove templates ?
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: Tue, 14 Jun 2016 12:39:30 -0000

--_004_9E32478DFA9976438E7A22F69B08FF921BC5BA19OPEXCLILMA4corp_
Content-Type: multipart/alternative;
	boundary="_000_9E32478DFA9976438E7A22F69B08FF921BC5BA19OPEXCLILMA4corp_"


--_000_9E32478DFA9976438E7A22F69B08FF921BC5BA19OPEXCLILMA4corp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks Michael,

Let's wait for other feedbacks to determine consensus.


From: Scharf, Michael (Nokia - DE) [mailto:michael.scharf@nokia.com]
Sent: Tuesday, June 14, 2016 13:31
To: LITKOWSKI Stephane OBS/OINIS; l3sm@ietf.org
Subject: RE: L3SM pending question : do we remove templates ?

As mentioned before, I fully agree that this is orthogonal.

If there was no consensus to remove site templates, perhaps the templates c=
ould be made optional, for instance by moving site-template a separate YANG=
 data model within the I-D (e.g., by import/include)?

Michael


From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of stephane.litkowski@o=
range.com<mailto:stephane.litkowski@orange.com>
Sent: Friday, June 10, 2016 9:18 AM
To: l3sm@ietf.org<mailto:l3sm@ietf.org>
Subject: [L3sm] L3SM pending question : do we remove templates ?

Hi,

Concerns were raised on the list of having a template mechanism in L3SM whi=
ch is orthogonal to L3SM : templates may be useful in YANG modeling globall=
y. Moreover there may be a need to express exact rules of template applicat=
ion.

So the question is : is there a consensus to remove site-templates from L3S=
M ?

Thanks,


[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/OINIS/NET
Orange Expert Future Networks
phone: +33 2 23 28 49 83 <https://monsi.sso.francetelecom.fr/index.asp?targ=
et=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do=
%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049=
%2083%20>
mobile: +33 6 37 86 97 52 <https://monsi.sso.francetelecom.fr/index.asp?tar=
get=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.d=
o%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%209=
7%2052%20>
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>


___________________________________________________________________________=
______________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.


--_000_9E32478DFA9976438E7A22F69B08FF921BC5BA19OPEXCLILMA4corp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks Michael,<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Let&#8217;s wait for o=
ther feedbacks to determine consensus.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Scharf, =
Michael (Nokia - DE) [mailto:michael.scharf@nokia.com]
<br>
<b>Sent:</b> Tuesday, June 14, 2016 13:31<br>
<b>To:</b> LITKOWSKI Stephane OBS/OINIS; l3sm@ietf.org<br>
<b>Subject:</b> RE: L3SM pending question : do we remove templates ?<o:p></=
o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">As mentioned before, I=
 fully agree that this is orthogonal.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">If there was no consen=
sus to remove site templates, perhaps the templates could be made optional,=
 for instance by moving site-template a separate YANG data model within the=
 I-D (e.g., by import/include)?
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Michael<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> L3sm [<a=
 href=3D"mailto:l3sm-bounces@ietf.org">mailto:l3sm-bounces@ietf.org</a>]
<b>On Behalf Of </b><a href=3D"mailto:stephane.litkowski@orange.com">stepha=
ne.litkowski@orange.com</a><br>
<b>Sent:</b> Friday, June 10, 2016 9:18 AM<br>
<b>To:</b> <a href=3D"mailto:l3sm@ietf.org">l3sm@ietf.org</a><br>
<b>Subject:</b> [L3sm] L3SM pending question : do we remove templates ?<o:p=
></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Concerns were raised on the list of having a templat=
e mechanism in L3SM which is orthogonal to L3SM : templates may be useful i=
n YANG modeling globally. Moreover there may be a need to express exact rul=
es of template application.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">So the question is : is there a consensus to remove =
site-templates from L3SM ?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;">Thanks,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><a href=3D"http://www.orange.com/"><span style=3D"fo=
nt-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;te=
xt-decoration:none"><img border=3D"0" width=3D"40" height=3D"40" id=3D"Pict=
ure_x0020_1" src=3D"cid:image001.jpg@01D1C64A.8AF078F0" alt=3D"Orange logo"=
></span></a><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:&quot;T=
imes New Roman&quot;,&quot;serif&quot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:15.0pt"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;">&nbsp;<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;;color:black">Stephane Litkowski
</span></b><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roma=
n&quot;,&quot;serif&quot;"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:black">Network Architect
</span><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&qu=
ot;,&quot;serif&quot;"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:black">Orange/SCE/EQUANT/OINIS/NET</span><span style=
=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&qu=
ot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">Orange Expert Fut=
ure Networks</span><span lang=3D"FR" style=3D"font-size:12.0pt;font-family:=
&quot;Times New Roman&quot;,&quot;serif&quot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">phone:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%202%2023%2028%2049%2083%20">
<span style=3D"color:black">&#43;33 2 23 28 49 83 </span></a></span><span l=
ang=3D"FR" style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot=
;,&quot;serif&quot;"><br>
</span><span lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Arial&=
quot;,&quot;sans-serif&quot;;color:black">mobile:
<a href=3D"https://monsi.sso.francetelecom.fr/index.asp?target=3Dhttp%3A%2F=
%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddef=
ault%26rootservice%3DSIGNATURE%26to%3D&#43;33%206%2037%2086%2097%2052%20">
<span style=3D"color:black">&#43;33 6 37 86 97 52 </span></a></span><span l=
ang=3D"FR" style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot=
;,&quot;serif&quot;"><br>
<a href=3D"mailto:stephane.litkowski@orange.com"><span style=3D"font-size:1=
0.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#FF6600">s=
tephane.litkowski@orange.com</span></a>
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<pre>______________________________________________________________________=
___________________________________________________<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Ce message et ses pieces jointes peuvent contenir des informations con=
fidentielles ou privilegiees et ne doivent donc<o:p></o:p></pre>
<pre>pas etre diffuses, exploites ou copies sans autorisation. Si vous avez=
 recu ce message par erreur, veuillez le signaler<o:p></o:p></pre>
<pre>a l'expediteur et le detruire ainsi que les pieces jointes. Les messag=
es electroniques etant susceptibles d'alteration,<o:p></o:p></pre>
<pre>Orange decline toute responsabilite si ce message a ete altere, deform=
e ou falsifie. Merci.<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>This message and its attachments may contain confidential or privilege=
d information that may be protected by law;<o:p></o:p></pre>
<pre>they should not be distributed, used or copied without authorisation.<=
o:p></o:p></pre>
<pre>If you have received this email in error, please notify the sender and=
 delete this message and its attachments.<o:p></o:p></pre>
<pre>As emails may be altered, Orange is not liable for messages that have =
been modified, changed or falsified.<o:p></o:p></pre>
<pre>Thank you.<o:p></o:p></pre>
</div>
<PRE>______________________________________________________________________=
___________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.
</PRE></body>
</html>

--_000_9E32478DFA9976438E7A22F69B08FF921BC5BA19OPEXCLILMA4corp_--

--_004_9E32478DFA9976438E7A22F69B08FF921BC5BA19OPEXCLILMA4corp_
Content-Type: image/jpeg; name="image001.jpg"
Content-Description: image001.jpg
Content-Disposition: inline; filename="image001.jpg"; size=1093;
	creation-date="Tue, 14 Jun 2016 12:39:23 GMT";
	modification-date="Tue, 14 Jun 2016 12:39:23 GMT"
Content-ID: <image001.jpg@01D1C64A.8AF078F0>
Content-Transfer-Encoding: base64

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRofHh0a
HBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwhMjIyMjIy
MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAARCAAoACgDASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD1O48f
afbXMsDWl0WjcoSAuDg49aj/AOFiad/z53f5L/jXB6r/AMhe9/67v/M1Ur5Geb4pSaTX3H2dPJcJ
KCbT+89H/wCFiad/z53f5L/jR/wsTTv+fO7/ACX/ABrziip/tnFd19xX9iYPs/vPR/8AhYmnf8+d
3+S/40V5xRR/bOK7r7g/sTB9n95b1X/kL3v/AF3f+ZqpW3Po17qGo3s0Cx7DdPGpeQLvbOdq56mo
R4d1EmEFYVaZdyI0oDY9cda450KspNqLO2niKUYJOSvbv5GVRWwPC+qmR4zFErI/l4aUDc2A2B68
GmDw7qTQrIIkJZVYR+YN+GOAdvuan6tW/lf3FfWqH86+8yqK2bjQG0+EvqU/2dmyIgieYGI6gkHg
0VM6M4O0tGVCtCavF3R1o8Oa7BcTtbXdh5TztPGJYyxjY9xxwcUxfDniNZ1m+32DOIPs+WjJymc8
8dc96KK+y/s+l3f3s+J/tKt2X3Ie+geJZJlla/0/eswmH7s/eChfT0FXDo2rDTRCktoLoIqfaCxy
NrZGPlz+GaKKpYGmr6vXzJlj6sraLTyMrUPCOuant+03lh8pJ+RGXJPUniiiisZ5Thpvmldv1N4Z
xioLljZL0R//2Q==

--_004_9E32478DFA9976438E7A22F69B08FF921BC5BA19OPEXCLILMA4corp_--


From nobody Tue Jun 14 05:51:43 2016
Return-Path: <daviball@cisco.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 26A4C12DB97 for <l3sm@ietfa.amsl.com>; Tue, 14 Jun 2016 05:51:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.946
X-Spam-Level: 
X-Spam-Status: No, score=-15.946 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_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-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 VYkuEDa-a-uS for <l3sm@ietfa.amsl.com>; Tue, 14 Jun 2016 05:51:40 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E51C12DB9C for <l3sm@ietf.org>; Tue, 14 Jun 2016 05:51:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13363; q=dns/txt; s=iport; t=1465908699; x=1467118299; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=pIY5fscrYUpZl9Jht7QYqYW46U8AZLTKFWPR+cTAShI=; b=fv1Z3wZ9DayqWdfeSe0m8jI0zTC6J7coyIZgDYm251pUMTpsAf8Wg03m 2Xvcf2jqtIPzds5zRDctrr9ZV8aBlT+6+w9jBdMg05egHpCFTke1cPCY8 LsNjn6VklDijHdMiP3DZ9wdbt8pMxw4LH7CFVHNDzDhMZz7Z8hmh0jSWE M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DpBQDX/F9X/xbLJq1cgnCBJCtStjWEC?= =?us-ascii?q?4JvFwEHhXgCHIFgAQEBAQEBZhwLhEwBAQQBAQEqPgMZAgsHEQUBAQEKFQcCFQE?= =?us-ascii?q?DCwEfEQYNBQECAQECiBADFw63KQOECgEBAQEBAQEBAQEBAQEBAQEBAQEBAQ4OB?= =?us-ascii?q?YYigXeCVoQSEQEiERUKhSUFk0OFIIUYbYgkgWlOhASDCoVdPI84VINvOzIBAQE?= =?us-ascii?q?BiE+BNQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.26,470,1459814400";  d="scan'208,145,217";a="638009493"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Jun 2016 12:51:37 +0000
Received: from [10.63.23.103] (dhcp-ensft1-uk-vla370-10-63-23-103.cisco.com [10.63.23.103]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u5ECpb8n014973 for <l3sm@ietf.org>; Tue, 14 Jun 2016 12:51:37 GMT
To: "l3sm@ietf.org" <l3sm@ietf.org>
References: <22833_1465543067_575A699B_22833_61_1_9E32478DFA9976438E7A22F69B08FF921BC4DBCB@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
From: David Ball <daviball@cisco.com>
Message-ID: <30e23c49-0b61-580e-bb69-9065a596311c@cisco.com>
Date: Tue, 14 Jun 2016 13:51:36 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <22833_1465543067_575A699B_22833_61_1_9E32478DFA9976438E7A22F69B08FF921BC4DBCB@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
Content-Type: multipart/alternative; boundary="------------0B94395E819AC6DC9DD56EA6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/rutYWvGOCDt_uA3cLgXeOfBgJ0E>
Subject: Re: [L3sm] L3SM pending question : do we remove templates ?
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: Tue, 14 Jun 2016 12:51:42 -0000

This is a multi-part message in MIME format.
--------------0B94395E819AC6DC9DD56EA6
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

I support removing them.

     David


On 10/06/2016 08:17, stephane.litkowski@orange.com wrote:
>
> Hi,
>
> Concerns were raised on the list of having a template mechanism in 
> L3SM which is orthogonal to L3SM : templates may be useful in YANG 
> modeling globally. Moreover there may be a need to express exact rules 
> of template application.
>
> So the question is : is there a consensus to remove site-templates 
> from L3SM ?
>
> Thanks,
>
> Orange logo <http://www.orange.com/>
>
> *Stephane Litkowski *
> Network Architect
> Orange/SCE/EQUANT/OINIS/NET
>
> Orange Expert Future Networks
>
> phone: +33 2 23 28 49 83 
> <https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049%2083%20>
> mobile: +33 6 37 86 97 52 
> <https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%2097%2052%20>
> stephane.litkowski@orange.com <mailto:stephane.litkowski@orange.com>
>
> _________________________________________________________________________________________________________________________
>
> 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
> L3sm@ietf.org
> https://www.ietf.org/mailman/listinfo/l3sm

-- 
David Ball
<daviball@cisco.com>


--------------0B94395E819AC6DC9DD56EA6
Content-Type: multipart/related;
 boundary="------------6681440202CDB16A79FA7265"


--------------6681440202CDB16A79FA7265
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>I support removing them.</p>
    <p>    David<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 10/06/2016 08:17,
      <a class="moz-txt-link-abbreviated" href="mailto:stephane.litkowski@orange.com">stephane.litkowski@orange.com</a> wrote:<br>
    </div>
    <blockquote
cite="mid:22833_1465543067_575A699B_22833_61_1_9E32478DFA9976438E7A22F69B08FF921BC4DBCB@OPEXCLILMA4.corporate.adroot.infra.ftgroup"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <meta name="Generator" content="Microsoft Word 14 (filtered
        medium)">
      <!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
      <style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal">Hi,<o:p></o:p></p>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal">Concerns were raised on the list of having
          a template mechanism in L3SM which is orthogonal to L3SM :
          templates may be useful in YANG modeling globally. Moreover
          there may be a need to express exact rules of template
          application.<o:p></o:p></p>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal">So the question is : is there a consensus
          to remove site-templates from L3SM ?<o:p></o:p></p>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal"><span
            style="font-size:12.0pt;font-family:&quot;Times New
            Roman&quot;,&quot;serif&quot;">Thanks,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:12.0pt;font-family:&quot;Times New
            Roman&quot;,&quot;serif&quot;"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:12.0pt;font-family:&quot;Times New
            Roman&quot;,&quot;serif&quot;"><o:p> </o:p></span></p>
        <p class="MsoNormal"><a moz-do-not-send="true"
            href="http://www.orange.com/"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;color:blue;text-decoration:none"><img
                id="Picture_x0020_1"
                src="cid:part1.50DAE995.C4E0F834@cisco.com" alt="Orange
                logo" height="40" border="0" width="40"></span></a><span
            style="font-size:12.0pt;font-family:&quot;Times New
            Roman&quot;,&quot;serif&quot;" lang="FR"><o:p></o:p></span></p>
        <p class="MsoNormal" style="line-height:15.0pt"><span
            style="font-size:12.0pt;font-family:&quot;Times New
            Roman&quot;,&quot;serif&quot;"> <o:p></o:p></span></p>
        <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">Stephane
              Litkowski
            </span></b><span
            style="font-size:12.0pt;font-family:&quot;Times New
            Roman&quot;,&quot;serif&quot;"><br>
          </span><span
style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">Network
            Architect
          </span><span style="font-size:12.0pt;font-family:&quot;Times
            New Roman&quot;,&quot;serif&quot;"><br>
          </span><span
style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">Orange/SCE/EQUANT/OINIS/NET</span><span
            style="font-size:12.0pt;font-family:&quot;Times New
            Roman&quot;,&quot;serif&quot;"><o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black"
            lang="FR">Orange Expert Future Networks</span><span
            style="font-size:12.0pt;font-family:&quot;Times New
            Roman&quot;,&quot;serif&quot;" lang="FR"><o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black"
            lang="FR">phone:
            <a moz-do-not-send="true"
href="https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049%2083%20"><span
                style="color:black">+33 2 23 28 49 83 </span></a></span><span
            style="font-size:12.0pt;font-family:&quot;Times New
            Roman&quot;,&quot;serif&quot;" lang="FR"><br>
          </span><span
style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black"
            lang="FR">mobile:
            <a moz-do-not-send="true"
href="https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%2097%2052%20"><span
                style="color:black">+33 6 37 86 97 52 </span></a></span><span
            style="font-size:12.0pt;font-family:&quot;Times New
            Roman&quot;,&quot;serif&quot;" lang="FR"><br>
            <a moz-do-not-send="true"
              href="mailto:stephane.litkowski@orange.com"><span
style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#FF6600">stephane.litkowski@orange.com</span></a>
            <o:p></o:p></span></p>
        <p class="MsoNormal"><o:p> </o:p></p>
      </div>
      <pre>_________________________________________________________________________________________________________________________

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.
</pre>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
L3sm mailing list
<a class="moz-txt-link-abbreviated" href="mailto:L3sm@ietf.org">L3sm@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/l3sm">https://www.ietf.org/mailman/listinfo/l3sm</a>
</pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
David Ball
<a class="moz-txt-link-rfc2396E" href="mailto:daviball@cisco.com">&lt;daviball@cisco.com&gt;</a></pre>
  </body>
</html>

--------------6681440202CDB16A79FA7265
Content-Type: image/jpeg
Content-Transfer-Encoding: base64
Content-ID: <part1.50DAE995.C4E0F834@cisco.com>

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRof
Hh0aHBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwh
MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAAR
CAAoACgDASIAAhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAA
AgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK
FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWG
h4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl
5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREA
AgECBAQDBAcFBAQAAQJ3AAECAxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYk
NOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE
hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk
5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD1O48fafbXMsDWl0WjcoSAuDg49aj/AOFi
ad/z53f5L/jXB6r/AMhe9/67v/M1Ur5Geb4pSaTX3H2dPJcJKCbT+89H/wCFiad/z53f5L/j
R/wsTTv+fO7/ACX/ABrziip/tnFd19xX9iYPs/vPR/8AhYmnf8+d3+S/40V5xRR/bOK7r7g/
sTB9n95b1X/kL3v/AF3f+ZqpW3Po17qGo3s0Cx7DdPGpeQLvbOdq56moR4d1EmEFYVaZdyI0
oDY9cda450KspNqLO2niKUYJOSvbv5GVRWwPC+qmR4zFErI/l4aUDc2A2B68GmDw7qTQrIIk
JZVYR+YN+GOAdvuan6tW/lf3FfWqH86+8yqK2bjQG0+EvqU/2dmyIgieYGI6gkHg0VM6M4O0
tGVCtCavF3R1o8Oa7BcTtbXdh5TztPGJYyxjY9xxwcUxfDniNZ1m+32DOIPs+WjJymc88dc9
6KK+y/s+l3f3s+J/tKt2X3Ie+geJZJlla/0/eswmH7s/eChfT0FXDo2rDTRCktoLoIqfaCxy
NrZGPlz+GaKKpYGmr6vXzJlj6sraLTyMrUPCOuant+03lh8pJ+RGXJPUniiiisZ5Thpvmldv
1N4ZxioLljZL0R//2Q==
--------------6681440202CDB16A79FA7265--

--------------0B94395E819AC6DC9DD56EA6--


From nobody Tue Jun 14 07:23:42 2016
Return-Path: <luis.tomotaki@verizon.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 9B8E912DBC2 for <l3sm@ietfa.amsl.com>; Tue, 14 Jun 2016 07:23:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.71
X-Spam-Level: 
X-Spam-Status: No, score=-2.71 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=verizon.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 5wbyV3DkkUTH for <l3sm@ietfa.amsl.com>; Tue, 14 Jun 2016 07:23:28 -0700 (PDT)
Received: from omzsmtpe02.verizonbusiness.com (omzsmtpe02.verizonbusiness.com [199.249.25.209]) (using TLSv1.2 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A56CD12DBAE for <l3sm@ietf.org>; Tue, 14 Jun 2016 07:23:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verizon.com; i=@verizon.com; q=dns/txt; s=corp; t=1465914207; x=1497450207; h=from:to:date:subject:message-id:references:in-reply-to: mime-version; bh=QoOq7/5rBaILS6Zi7ePzqkSedJ5rzu2CmUhqW62xEJs=; b=rTFdvcT7RuFu23rHhUcMAdeWgvlADSnHwaY5C5UfoCNsHferyYs4piYw yunHE4i4aDfnDNBrE0YZnp23jyzqR6ACzhDH1MHESY7Suy+z91gJGzRi/ fb+rIwfSeG04P6/mPav/W6kA9c/rDCg1dhLhCuQZv1+f9qr2qnFl9dwWv A=;
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi03.verizon.com) ([166.68.71.145]) by omzsmtpe02.verizonbusiness.com with ESMTP; 14 Jun 2016 14:23:26 +0000
From: "Tomotaki, Luis M" <luis.tomotaki@verizon.com>
X-IronPort-AV: E=Sophos;i="5.26,470,1459814400";  d="jpg'145?scan'145,208,217,145";a="156762238"
Received: from fhdp1lumxc7hb05.verizon.com (HELO FHDP1LUMXC7HB05.us.one.verizon.com) ([166.68.59.192]) by fldsmtpi03.verizon.com with ESMTP; 14 Jun 2016 14:22:46 +0000
Received: from FHDP1LUMXC7V91.us.one.verizon.com ([166.68.240.155]) by FHDP1LUMXC7HB05.us.one.verizon.com ([166.68.59.192]) with mapi; Tue, 14 Jun 2016 10:22:45 -0400
To: David Ball <daviball@cisco.com>, "l3sm@ietf.org" <l3sm@ietf.org>
Date: Tue, 14 Jun 2016 10:22:45 -0400
Thread-Topic: [E] Re: [L3sm] L3SM pending question : do we remove templates ?
Thread-Index: AdHGO4KRM2EMaIYtSZWEXFOMS/8/DwACm/MA
Message-ID: <467340A77F13C944919805BFF3B8ACFC301648AF73@FHDP1LUMXC7V91.us.one.verizon.com>
References: <22833_1465543067_575A699B_22833_61_1_9E32478DFA9976438E7A22F69B08FF921BC4DBCB@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <30e23c49-0b61-580e-bb69-9065a596311c@cisco.com>
In-Reply-To: <30e23c49-0b61-580e-bb69-9065a596311c@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/related; boundary="_004_467340A77F13C944919805BFF3B8ACFC301648AF73FHDP1LUMXC7V9_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/kSvQPydzofzKdf1sAQhs1u-yzYo>
Subject: Re: [L3sm] [E] Re: L3SM pending question : do we remove templates ?
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: Tue, 14 Jun 2016 14:23:34 -0000

--_004_467340A77F13C944919805BFF3B8ACFC301648AF73FHDP1LUMXC7V9_
Content-Type: multipart/alternative;
	boundary="_000_467340A77F13C944919805BFF3B8ACFC301648AF73FHDP1LUMXC7V9_"

--_000_467340A77F13C944919805BFF3B8ACFC301648AF73FHDP1LUMXC7V9_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Stephane,
I also agree to remove the site templates.

Luis

From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of David Ball
Sent: Tuesday, June 14, 2016 7:52 AM
To: l3sm@ietf.org
Subject: [E] Re: [L3sm] L3SM pending question : do we remove templates ?


I support removing them.

    David

On 10/06/2016 08:17, stephane.litkowski@orange.com<mailto:stephane.litkowsk=
i@orange.com> wrote:
Hi,

Concerns were raised on the list of having a template mechanism in L3SM whi=
ch is orthogonal to L3SM : templates may be useful in YANG modeling globall=
y. Moreover there may be a need to express exact rules of template applicat=
ion.

So the question is : is there a consensus to remove site-templates from L3S=
M ?

Thanks,


[cid:image001.jpg@01D1C61C.16CE0740]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/OINIS/NET
Orange Expert Future Networks
phone: +33 2 23 28 49 83 <https://monsi.sso.francetelecom.fr/index.asp?targ=
et=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do=
%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049=
%2083%20>
mobile: +33 6 37 86 97 52 <https://monsi.sso.francetelecom.fr/index.asp?tar=
get=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.d=
o%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%209=
7%2052%20>
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>


___________________________________________________________________________=
______________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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

L3sm@ietf.org<mailto:L3sm@ietf.org>

https://www.ietf.org/mailman/listinfo/l3sm



--

David Ball

<daviball@cisco.com><mailto:daviball@cisco.com>

--_000_467340A77F13C944919805BFF3B8ACFC301648AF73FHDP1LUMXC7V9_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV=3D"Content-Type" CONTENT=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#def=
ault#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"Times New Roman \, serif";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	color:black;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma",sans-serif;
	color:black;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma",sans-serif;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=3Dwhite lang=3DEN-US=
 link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>=
<span style=3D'color:#1F497D'>Stephane, <o:p></o:p></span></p><p class=3DMs=
oNormal><span style=3D'color:#1F497D'>I also agree to remove the site templ=
ates. <o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'color:#1F49=
7D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'color:#=
1F497D'>Luis<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'color=
:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div style=3D'border:none;border=
-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b=
><span style=3D'color:windowtext'>From:</span></b><span style=3D'color:wind=
owtext'> L3sm [mailto:l3sm-bounces@ietf.org] <b>On Behalf Of </b>David Ball=
<br><b>Sent:</b> Tuesday, June 14, 2016 7:52 AM<br><b>To:</b> l3sm@ietf.org=
<br><b>Subject:</b> [E] Re: [L3sm] L3SM pending question : do we remove tem=
plates ?<o:p></o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;<=
/o:p></p><p>I support removing them.<span style=3D'font-size:12.0pt'><o:p><=
/o:p></span></p><p>&nbsp;&nbsp;&nbsp; David<o:p></o:p></p><p class=3DMsoNor=
mal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>On 10/06/2016 08:17, <a =
href=3D"mailto:stephane.litkowski@orange.com">stephane.litkowski@orange.com=
</a> wrote:<o:p></o:p></p></div><blockquote style=3D'margin-top:5.0pt;margi=
n-bottom:5.0pt'><p class=3DMsoNormal>Hi,<o:p></o:p></p><p class=3DMsoNormal=
>&nbsp;<o:p></o:p></p><p class=3DMsoNormal>Concerns were raised on the list=
 of having a template mechanism in L3SM which is orthogonal to L3SM : templ=
ates may be useful in YANG modeling globally. Moreover there may be a need =
to express exact rules of template application.<o:p></o:p></p><p class=3DMs=
oNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal>So the question is : is t=
here a consensus to remove site-templates from L3SM ?<o:p></o:p></p><p clas=
s=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal><span style=3D'font=
-size:12.0pt;font-family:"Times New Roman , serif",serif'>Thanks,</span><o:=
p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-famil=
y:"Times New Roman , serif",serif'>&nbsp;</span><o:p></o:p></p><p class=3DM=
soNormal><span style=3D'font-size:12.0pt;font-family:"Times New Roman , ser=
if",serif'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><a href=3D"http=
://www.orange.com/"><span style=3D'font-size:12.0pt;text-decoration:none'><=
img border=3D0 width=3D40 height=3D40 id=3D"Picture_x0020_1" src=3D"cid:ima=
ge001.jpg@01D1C61C.16CE0740" alt=3D"Orange&#13;&#10;                logo"><=
/span></a><o:p></o:p></p><p class=3DMsoNormal style=3D'line-height:15.0pt'>=
<span style=3D'font-size:12.0pt;font-family:"Times New Roman , serif",serif=
'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><b><span style=3D'font-s=
ize:10.0pt;font-family:"Arial",sans-serif'>Stephane Litkowski </span></b><s=
pan style=3D'font-size:12.0pt;font-family:"Times New Roman , serif",serif'>=
<br></span><span style=3D'font-size:10.0pt;font-family:"Arial",sans-serif'>=
Network Architect </span><span style=3D'font-size:12.0pt;font-family:"Times=
 New Roman , serif",serif'><br></span><span style=3D'font-size:10.0pt;font-=
family:"Arial",sans-serif'>Orange/SCE/EQUANT/OINIS/NET</span><o:p></o:p></p=
><p class=3DMsoNormal><span lang=3DFR style=3D'font-size:10.0pt;font-family=
:"Arial",sans-serif'>Orange Expert Future Networks</span><o:p></o:p></p><p =
class=3DMsoNormal><span lang=3DFR style=3D'font-size:10.0pt;font-family:"Ar=
ial",sans-serif'>phone: <a href=3D"https://monsi.sso.francetelecom.fr/index=
.asp?target=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FT=
oolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%=
2028%2049%2083%20"><span style=3D'color:black'>+33 2 23 28 49 83 </span></a=
></span><span lang=3DFR style=3D'font-size:12.0pt;font-family:"Times New Ro=
man , serif",serif'><br></span><span lang=3DFR style=3D'font-size:10.0pt;fo=
nt-family:"Arial",sans-serif'>mobile: <a href=3D"https://monsi.sso.francete=
lecom.fr/index.asp?target=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FC=
licvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3=
D+33%206%2037%2086%2097%2052%20"><span style=3D'color:black'>+33 6 37 86 97=
 52 </span></a></span><span lang=3DFR style=3D'font-size:12.0pt;font-family=
:"Times New Roman , serif",serif'><br><a href=3D"mailto:stephane.litkowski@=
orange.com"><span style=3D'font-size:10.0pt;font-family:"Arial",sans-serif;=
color:#FF6600'>stephane.litkowski@orange.com</span></a> </span><o:p></o:p><=
/p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><pre>_________________________=
___________________________________________________________________________=
_____________________<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>Ce m=
essage et ses pieces jointes peuvent contenir des informations confidentiel=
les ou privilegiees et ne doivent donc<o:p></o:p></pre><pre>pas etre diffus=
es, exploites ou copies sans autorisation. Si vous avez recu ce message par=
 erreur, veuillez le signaler<o:p></o:p></pre><pre>a l'expediteur et le det=
ruire ainsi que les pieces jointes. Les messages electroniques etant suscep=
tibles d'alteration,<o:p></o:p></pre><pre>Orange decline toute responsabili=
te si ce message a ete altere, deforme ou falsifie. Merci.<o:p></o:p></pre>=
<pre><o:p>&nbsp;</o:p></pre><pre>This message and its attachments may conta=
in confidential or privileged information that may be protected by law;<o:p=
></o:p></pre><pre>they should not be distributed, used or copied without au=
thorisation.<o:p></o:p></pre><pre>If you have received this email in error,=
 please notify the sender and delete this message and its attachments.<o:p>=
</o:p></pre><pre>As emails may be altered, Orange is not liable for message=
s that have been modified, changed or falsified.<o:p></o:p></pre><pre>Thank=
 you.<o:p></o:p></pre><p class=3DMsoNormal><span style=3D'font-size:12.0pt;=
font-family:"Times New Roman",serif'><br><br><br><o:p></o:p></span></p><pre=
>_______________________________________________<o:p></o:p></pre><pre>L3sm =
mailing list<o:p></o:p></pre><pre><a href=3D"mailto:L3sm@ietf.org">L3sm@iet=
f.org</a><o:p></o:p></pre><pre><a href=3D"https://www.ietf.org/mailman/list=
info/l3sm">https://www.ietf.org/mailman/listinfo/l3sm</a><o:p></o:p></pre><=
/blockquote><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-famil=
y:"Times New Roman",serif'><br><br><o:p></o:p></span></p><pre>-- <o:p></o:p=
></pre><pre>David Ball<o:p></o:p></pre><pre><a href=3D"mailto:daviball@cisc=
o.com">&lt;daviball@cisco.com&gt;</a><o:p></o:p></pre></div></body></html>=

--_000_467340A77F13C944919805BFF3B8ACFC301648AF73FHDP1LUMXC7V9_--

--_004_467340A77F13C944919805BFF3B8ACFC301648AF73FHDP1LUMXC7V9_
Content-Type: image/jpeg; name="image001.jpg"
Content-Description: image001.jpg
Content-Disposition: inline; filename="image001.jpg"; size=1093;
	creation-date="Tue, 14 Jun 2016 14:22:44 GMT";
	modification-date="Tue, 14 Jun 2016 14:22:44 GMT"
Content-ID: <image001.jpg@01D1C61C.16CE0740>
Content-Transfer-Encoding: base64

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRofHh0a
HBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwhMjIyMjIy
MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAARCAAoACgDASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD1O48f
afbXMsDWl0WjcoSAuDg49aj/AOFiad/z53f5L/jXB6r/AMhe9/67v/M1Ur5Geb4pSaTX3H2dPJcJ
KCbT+89H/wCFiad/z53f5L/jR/wsTTv+fO7/ACX/ABrziip/tnFd19xX9iYPs/vPR/8AhYmnf8+d
3+S/40V5xRR/bOK7r7g/sTB9n95b1X/kL3v/AF3f+ZqpW3Po17qGo3s0Cx7DdPGpeQLvbOdq56mo
R4d1EmEFYVaZdyI0oDY9cda450KspNqLO2niKUYJOSvbv5GVRWwPC+qmR4zFErI/l4aUDc2A2B68
GmDw7qTQrIIkJZVYR+YN+GOAdvuan6tW/lf3FfWqH86+8yqK2bjQG0+EvqU/2dmyIgieYGI6gkHg
0VM6M4O0tGVCtCavF3R1o8Oa7BcTtbXdh5TztPGJYyxjY9xxwcUxfDniNZ1m+32DOIPs+WjJymc8
8dc96KK+y/s+l3f3s+J/tKt2X3Ie+geJZJlla/0/eswmH7s/eChfT0FXDo2rDTRCktoLoIqfaCxy
NrZGPlz+GaKKpYGmr6vXzJlj6sraLTyMrUPCOuant+03lh8pJ+RGXJPUniiiisZ5Thpvmldv1N4Z
xioLljZL0R//2Q==

--_004_467340A77F13C944919805BFF3B8ACFC301648AF73FHDP1LUMXC7V9_--


From nobody Tue Jun 14 07:49:23 2016
Return-Path: <ke-oogaki@kddi.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 8A88712DBCC for <l3sm@ietfa.amsl.com>; Tue, 14 Jun 2016 07:49:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.647
X-Spam-Level: 
X-Spam-Status: No, score=-5.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=o365kddi.onmicrosoft.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 15QFVVwyuRWG for <l3sm@ietfa.amsl.com>; Tue, 14 Jun 2016 07:49:18 -0700 (PDT)
Received: from post-send.kddi.com (athena3.kddi.com [27.90.165.196]) by ietfa.amsl.com (Postfix) with ESMTP id C3A7712DBCD for <l3sm@ietf.org>; Tue, 14 Jun 2016 07:49:17 -0700 (PDT)
Received: from LTMC2121.kddi.com (LTMC2121.kddi.com [10.206.0.61]) by post-send.kddi.com (KDDI Mail) with ESMTP id 642DEE0022 for <l3sm@ietf.org>; Tue, 14 Jun 2016 23:49:16 +0900 (JST)
Received: from LTMC2145.kddi.com ([10.206.0.236] [10.206.0.236]) by LTMC2121.kddi.com with ESMTP; Tue, 14 Jun 2016 23:49:16 +0900
Received: from LTMC2145.kddi.com (localhost [127.0.0.1]) by localhost.kddi.com (Postfix) with ESMTP id 3FBC53A006B for <l3sm@ietf.org>; Tue, 14 Jun 2016 23:49:16 +0900 (JST)
Received: from LTMC2152.kddi.com (post-incheck [10.206.0.239]) by LTMC2145.kddi.com (Postfix) with ESMTP id 34CA93A0065 for <l3sm@ietf.org>; Tue, 14 Jun 2016 23:49:16 +0900 (JST)
Received: from LTMC2152.kddi.com (localhost.localdomain [127.0.0.1]) by LTMC2152.kddi.com  with ESMTP id u5EEnFYX011144 for <l3sm@ietf.org>; Tue, 14 Jun 2016 23:49:16 +0900
Received: from LTMC2152.kddi.com.mid_39147302 (localhost.localdomain [127.0.0.1]) by LTMC2152.kddi.com  with ESMTP id u5EEdE0G008578 for <l3sm@ietf.org>; Tue, 14 Jun 2016 23:39:14 +0900
X-SA-MID: 39147302
Received: from APC01-HK2-obe.outbound.protection.outlook.com (mail-hk2apc01lp0210.outbound.protection.outlook.com [65.55.88.210]) by post-gate.kddi.com (KDDI Mail) with ESMTPS id E50A2E0003 for <l3sm@ietf.org>; Tue, 14 Jun 2016 23:39:13 +0900 (JST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=o365kddi.onmicrosoft.com; s=selector1-kddi-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=s1u7EH9aO/i0iCvchOrvoynHHINHAtweAnGCOZkXrgQ=; b=b6z6dMqLMArlxLQEajpHQyQvBpfs/9kZ2rcPl34uO+gms7IVqmZPrM3VVIZge1p45TnjkRBABCX//taeZNHLwZtX1J1w5hZmXwaydcwmJTMOK7JlNGxefumDal/1We6qpNV6x+raCJnG5Aqzsxh9LJeb0SjR9MVPN0//sq/RCcw=
Received: from PS1PR02MB1467.apcprd02.prod.outlook.com (10.167.47.141) by PS1PR02MB1466.apcprd02.prod.outlook.com (10.167.47.140) with Microsoft SMTP Server (TLS) id 15.1.523.4; Tue, 14 Jun 2016 14:39:12 +0000
Received: from PS1PR02MB1467.apcprd02.prod.outlook.com ([10.167.47.141]) by PS1PR02MB1467.apcprd02.prod.outlook.com ([10.167.47.141]) with mapi id 15.01.0523.011; Tue, 14 Jun 2016 14:39:12 +0000
From: "ke-oogaki@kddi.com" <ke-oogaki@kddi.com>
To: "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: Re:Re: [L3sm] [E] Re: L3SM pending question : do we remove templates ?
Thread-Index: AQHRxkqEtdUWNDiOQka1VwnXiCXhTw==
Date: Tue, 14 Jun 2016 14:39:11 +0000
Message-ID: <PS1PR02MB1467E752DE8ED5BF709CA66E90540@PS1PR02MB1467.apcprd02.prod.outlook.com>
Accept-Language: ja-JP, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ke-oogaki@kddi.com; 
x-originating-ip: [106.162.184.143]
x-ms-office365-filtering-correlation-id: a7db41a4-75c6-4461-a6b3-08d39461a6db
x-microsoft-exchange-diagnostics: 1; PS1PR02MB1466; 6:5y6ZjS6sXKrfG4ol12MtrGAZezIizqLNr/yzjO+FqrdiwQGzaDDQoi+uJcnl3tIWpNYY30ThGiBqa0LbHB1AG6fetJh2XmWT+0Y1tn+ZsDpTTtModHdnXm31CoiIh7W9ZO2xur7dzQiQINO9te+M24QX1rd5elo/ox7CaonHvvqqA8TZ/3Ut3aI72OSwhr7Gm5Qv3W5yYDyTsnxtyUBuN2OzRk+kIpXqU3MVarXxMpUdQ2cq1kvmu6Jk3y6HzlU8e6HmzZ2fVPQWNf1t5zpwHHkvO/p6hyVzh5ZO6An6Awo=; 5:+gw0jDvqC+tOC6e+pTyV6XsI5WwojGhY6z5PsrgGbkjnKS/QrykmhEZGGZchjh8SGmQhtBRXFS4oP6Ushwpv+ROYxn6Iv843KN6aqYU4xaanSLZlTetRSePr8fIkm4YKqG1HVUNMm45oOA1qxPHqbg==; 24:soDL/Y60SDXKMBWqdT8VShY3gFJASS2/oobLDKkQpWPtHSkl/ppxJlPY7h5oyW3DpOFPCpBJwefN6bBwiB8uVs9I6whcLP3v6L//GJ3HAbc=; 7:lwC2IM8kIZtct2dIrW4KHZvueIexjB80ou3WJsRPvmUWTKEcsiry8h8X0rskpHH7+nvlednL3JplFwT75/9cAJJ+ArEmDfzX0wGWh/lJaLlq9ESPfI5spnYKfk1Eb/Qe3hob9SwCNRUPHTzRVd7DIIXlinHDrErhiNbyPB04Xz9K9RIVvZ78Kyot3gLdttHZXyFRDZJ1T1o/ivPHXIOIL8IRP7KT7e3p8/Zzt2AnfA0=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:PS1PR02MB1466;
x-microsoft-antispam-prvs: <PS1PR02MB1466F4B806665E49443CDC5E90540@PS1PR02MB1466.apcprd02.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(115448073456579)(81850148713716)(100405760836317)(95692535739014)(18271650672692);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046); SRVR:PS1PR02MB1466; BCL:0; PCL:0; RULEID:; SRVR:PS1PR02MB1466; 
x-forefront-prvs: 09730BD177
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(377454003)(24454002)(189002)(199003)(97736004)(54356999)(19580395003)(87936001)(74316001)(76576001)(450100001)(5640700001)(8936002)(2906002)(106116001)(229853001)(106356001)(81156014)(5890100001)(81166006)(33656002)(101416001)(3280700002)(122556002)(8676002)(2351001)(19580405001)(3660700001)(105586002)(66066001)(10400500002)(6116002)(102836003)(3846002)(586003)(15975445007)(5002640100001)(5004730100002)(11100500001)(9686002)(2501003)(5003600100002)(68736007)(50986999)(92566002)(5008740100001)(86362001)(110136002)(107886002)(2900100001)(77096005)(189998001)(32563001); DIR:OUT; SFP:1102; SCL:1; SRVR:PS1PR02MB1466; H:PS1PR02MB1467.apcprd02.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  MX:1; A:1; CAT:NONE; LANG:en; CAT:NONE; 
received-spf: None (protection.outlook.com: kddi.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-2022-jp"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
X-OriginatorOrg: kddi.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Jun 2016 14:39:11.9161 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 040b5c43-0c27-49b3-b8e6-cdec886abcee
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PS1PR02MB1466
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/y2DMTUoyLk46U_SpFIWLdF-7aGM>
Subject: Re: [L3sm] [E] Re: L3SM pending question : do we remove templates ?
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: Tue, 14 Jun 2016 14:49:21 -0000

I agree to remove them.=0A=
=0A=
-Kenichi=0A=
=0A=
=0A=
=0A=
(2016/06/14 23:24:14), Tomotaki, Luis M wrote:=0A=
=0A=
Stephane,=0A=
I also agree to remove the site templates.=0A=
=0A=
Luis=0A=
=0A=
From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of David Ball=0A=
Sent: Tuesday, June 14, 2016 7:52 AM=0A=
To: l3sm@ietf.org=0A=
Subject: [E] Re: [L3sm] L3SM pending question : do we remove templates ?=0A=
=0A=
=0A=
I support removing them.=0A=
=0A=
    David=0A=
=0A=
On 10/06/2016 08:17, stephane.litkowski@orange.com<mailto:stephane.litkowsk=
i@orange.com> wrote:=0A=
Hi,=0A=
=0A=
Concerns were raised on the list of having a template mechanism in L3SM whi=
ch is orthogonal to L3SM : templates may be useful in YANG modeling globall=
y. Moreover there may be a need to express exact rules of template applicat=
ion.=0A=
=0A=
So the question is : is there a consensus to remove site-templates from L3S=
M ?=0A=
=0A=
Thanks,=0A=
=0A=
=0A=
[Orange                  logo]<http://www.orange.com/>=0A=
=0A=
Stephane Litkowski=0A=
Network Architect=0A=
Orange/SCE/EQUANT/OINIS/NET=0A=
Orange Expert Future Networks=0A=
phone: +33 2 23 28 49 83 <https://monsi.sso.francetelecom.fr/index.asp?targ=
et=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do=
%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049=
%2083%20>=0A=
mobile: +33 6 37 86 97 52 <https://monsi.sso.francetelecom.fr/index.asp?tar=
get=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.d=
o%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%209=
7%2052%20>=0A=
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>=0A=
=0A=
=0A=
___________________________________________________________________________=
______________________________________________=0A=
=0A=
=0A=
=0A=
Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc=0A=
=0A=
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler=0A=
=0A=
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,=0A=
=0A=
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.=0A=
=0A=
=0A=
=0A=
This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;=0A=
=0A=
they should not be distributed, used or copied without authorisation.=0A=
=0A=
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.=0A=
=0A=
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.=0A=
=0A=
Thank you.=0A=
=0A=
=0A=
=0A=
=0A=
_______________________________________________=0A=
=0A=
L3sm mailing list=0A=
=0A=
L3sm@ietf.org<mailto:L3sm@ietf.org>=0A=
=0A=
https://www.ietf.org/mailman/listinfo/l3sm=0A=
=0A=
=0A=
=0A=
--=0A=
=0A=
David Ball=0A=
=0A=
<daviball@cisco.com><mailto:daviball@cisco.com>=0A=


From nobody Tue Jun 14 17:56:43 2016
Return-Path: <lucy.yong@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 DE15C12DA8B for <l3sm@ietfa.amsl.com>; Tue, 14 Jun 2016 17:56:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.647
X-Spam-Level: 
X-Spam-Status: No, score=-5.647 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=-1.426, 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 X-C2Dmn3RvsX for <l3sm@ietfa.amsl.com>; Tue, 14 Jun 2016 17:56:40 -0700 (PDT)
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 727CE12DA81 for <l3sm@ietf.org>; Tue, 14 Jun 2016 17:56:40 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml705-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CLY86212; Wed, 15 Jun 2016 00:56:38 +0000 (GMT)
Received: from DFWEML701-CAH.china.huawei.com (10.193.5.175) by lhreml705-cah.china.huawei.com (10.201.5.168) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 15 Jun 2016 01:56:37 +0100
Received: from DFWEML501-MBB.china.huawei.com ([10.193.5.179]) by dfweml701-cah.china.huawei.com ([10.193.5.175]) with mapi id 14.03.0235.001; Tue, 14 Jun 2016 17:56:32 -0700
From: Lucy yong <lucy.yong@huawei.com>
To: "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: [L3sm] [E] Re: L3SM pending question : do we remove templates ?
Thread-Index: AQHRxkqEtdUWNDiOQka1VwnXiCXhT5/ptNyQ
Date: Wed, 15 Jun 2016 00:56:31 +0000
Message-ID: <2691CE0099834E4A9C5044EEC662BB9D57297E25@dfweml501-mbb>
References: <PS1PR02MB1467E752DE8ED5BF709CA66E90540@PS1PR02MB1467.apcprd02.prod.outlook.com>
In-Reply-To: <PS1PR02MB1467E752DE8ED5BF709CA66E90540@PS1PR02MB1467.apcprd02.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.129.58]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020206.5760A7C6.00FA, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 585def8144bd18a91e5f13c7859a3e51
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/kG0PW98KqKjahrAtFfag5apB0T8>
Subject: Re: [L3sm] [E] Re: L3SM pending question : do we remove templates ?
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: Wed, 15 Jun 2016 00:56:43 -0000

Agree to remove them.
Lucy

-----Original Message-----
From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of ke-oogaki@kddi.com
Sent: Tuesday, June 14, 2016 9:39 AM
To: l3sm@ietf.org
Subject: Re: [L3sm] [E] Re: L3SM pending question : do we remove templates =
?

I agree to remove them.

-Kenichi



(2016/06/14 23:24:14), Tomotaki, Luis M wrote:

Stephane,
I also agree to remove the site templates.

Luis

From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of David Ball
Sent: Tuesday, June 14, 2016 7:52 AM
To: l3sm@ietf.org
Subject: [E] Re: [L3sm] L3SM pending question : do we remove templates ?


I support removing them.

    David

On 10/06/2016 08:17, stephane.litkowski@orange.com<mailto:stephane.litkowsk=
i@orange.com> wrote:
Hi,

Concerns were raised on the list of having a template mechanism in L3SM whi=
ch is orthogonal to L3SM : templates may be useful in YANG modeling globall=
y. Moreover there may be a need to express exact rules of template applicat=
ion.

So the question is : is there a consensus to remove site-templates from L3S=
M ?

Thanks,


[Orange                  logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/OINIS/NET
Orange Expert Future Networks
phone: +33 2 23 28 49 83 <https://monsi.sso.francetelecom.fr/index.asp?targ=
et=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do=
%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049=
%2083%20>
mobile: +33 6 37 86 97 52 <https://monsi.sso.francetelecom.fr/index.asp?tar=
get=3Dhttp%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.d=
o%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%209=
7%2052%20>
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>


___________________________________________________________________________=
______________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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

L3sm@ietf.org<mailto:L3sm@ietf.org>

https://www.ietf.org/mailman/listinfo/l3sm



--

David Ball

<daviball@cisco.com><mailto:daviball@cisco.com>

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


From nobody Wed Jun 15 02:21:23 2016
Return-Path: <stephane.litkowski@orange.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 46D7312D51C for <l3sm@ietfa.amsl.com>; Wed, 15 Jun 2016 02:21:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.334
X-Spam-Level: 
X-Spam-Status: No, score=-3.334 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, UNPARSEABLE_RELAY=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 fymZ3HmubmaI for <l3sm@ietfa.amsl.com>; Wed, 15 Jun 2016 02:21:18 -0700 (PDT)
Received: from relais-inet.orange.com (relais-nor34.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FD9112D1AC for <l3sm@ietf.org>; Wed, 15 Jun 2016 02:21:18 -0700 (PDT)
Received: from opfednr00.francetelecom.fr (unknown [xx.xx.xx.64]) by opfednr25.francetelecom.fr (ESMTP service) with ESMTP id B37381805B8; Wed, 15 Jun 2016 11:21:16 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.57]) by opfednr00.francetelecom.fr (ESMTP service) with ESMTP id 824F71A0061; Wed, 15 Jun 2016 11:21:16 +0200 (CEST)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM23.corporate.adroot.infra.ftgroup ([fe80::787e:db0c:23c4:71b3%19]) with mapi id 14.03.0294.000; Wed, 15 Jun 2016 11:21:16 +0200
From: <stephane.litkowski@orange.com>
To: David Ball <daviball@cisco.com>, "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
Thread-Index: AQHRv/4i8iSSM4mtWE6AeESR5nwEZZ/cfFGwgAGg6gCAASznEIABf5oAgAC53hCAAPGPgIAH11+A
Date: Wed, 15 Jun 2016 09:21:16 +0000
Message-ID: <3459_1465982476_57611E0C_3459_229_11_9E32478DFA9976438E7A22F69B08FF921BC5ECBA@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <20160606141710.20806.10098.idtracker@ietfa.amsl.com> <27218_1465222795_5755868B_27218_684_1_9E32478DFA9976438E7A22F69B08FF921BC41DA1@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <ec72f8b8-8626-ba2c-bc50-7ce4a0cdc6df@cisco.com> <32265_1465379094_5757E916_32265_10098_3_9E32478DFA9976438E7A22F69B08FF921BC454AB@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <1595f5bb-1838-8164-6e7f-1d383d8bfb87@cisco.com> <7576_1465499325_5759BEBD_7576_3122_1_9E32478DFA9976438E7A22F69B08FF921BC4C5F2@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <bf0bd488-ff9e-ae4e-b37c-6123ae63a8ee@cisco.com>
In-Reply-To: <bf0bd488-ff9e-ae4e-b37c-6123ae63a8ee@cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
Content-Type: multipart/alternative; boundary="_000_9E32478DFA9976438E7A22F69B08FF921BC5ECBAOPEXCLILMA4corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/zqpiav68p2SOIXPHPBH0039FVVE>
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
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: Wed, 15 Jun 2016 09:21:21 -0000

--_000_9E32478DFA9976438E7A22F69B08FF921BC5ECBAOPEXCLILMA4corp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi David,

I see your point, as a mentioned, it is different from what I was thinking =
about.
So the question is : do we need to support this kind of architecture (is th=
ere a use case ?).
Regarding the two CEs/two PEs cases connected on the same LAN, I think it's=
 interesting to keep it, it usually used to connect some service platforms.=
 We may need to restrict options in this scenario (static address ...) , bu=
t I'm afraid that it may be hard to be exhaustive ... any idea ?

Thanks,


From: David Ball [mailto:daviball@cisco.com]
Sent: Friday, June 10, 2016 13:29
To: LITKOWSKI Stephane OBS/OINIS; l3sm@ietf.org
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

Hi Stephane,

More inline:
On 09/06/2016 20:08, stephane.litkowski@orange.com<mailto:stephane.litkowsk=
i@orange.com> wrote:



  *   Sn 5.10.2: You said before that the model can only manage P2P connect=
ions; but this figure (and the next one) show the PE connected to a LAN, no=
t to a CE.  I am not sure how to interpret this?  Isn't this a case where t=
he connection is multipoint, not P2P?
[SLI] That's still point to point. In 5.10.3, customer must order two site =
network accesses (point to point). Each site network network access may be =
connected to a switch at customer side (same one or not).

[DB] If there is an L2 switch, then at L3 it is a multipoint connection - t=
he switch is part of the bearer.
[SLI] From a SP  point of view no, in term of service, the customer will ha=
ve to order two site-network-accesses. How they are connected to the custom=
er network is not under the SP responsibility. If the customer connects the=
 two site-net-access on the same Lan through a switch, it becomes multipoin=
t, but SP is not essentially aware of it.

[DB] I think we may be talking about different cases.  I don't mean it may =
be multipoint because there are multiple site-network-accesses, I'm talking=
 about the case where there are multiple devices at the customer side (coul=
d be one or multiple site-network-accesses) - rather than a single CE termi=
nating the L3 connection.  This seems to be what the figure in Sn 5.10.2 is=
 showing.

  Host1 ------\
  Host2 ---- Switch ---------- PE
  Host3 ------/

I don't think it's entirely true in this case that the SP does not need to =
be aware of it - for instance, if the connection address is dynamic, the SP=
 may need to allocate multiple addresses instead of just 1.  It also has so=
me impact on other aspects of the model; for instance, the routing protocol=
 probably needs to be direct or static (not an absolute requirement but pro=
bably true in practice), and BFD and IPSec probably need to be disabled (si=
nce these are inherently P2P).


    David




--

David Ball

<daviball@cisco.com><mailto:daviball@cisco.com>

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.


--_000_9E32478DFA9976438E7A22F69B08FF921BC5ECBAOPEXCLILMA4corp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
tt
	{mso-style-priority:99;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	color:black;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle25
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1042284551;
	mso-list-template-ids:1502010652;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1
	{mso-list-id:1656761572;
	mso-list-template-ids:-682878950;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=3D"white" lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi David,<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I see your point, as a me=
ntioned, it is different from what I was thinking about.<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">So the question is : do w=
e need to support this kind of architecture (is there a use case ?).<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Regarding the two CEs/two=
 PEs cases connected on the same LAN, I think it&#8217;s interesting to kee=
p it, it usually used to connect some service platforms. We may
 need to restrict options in this scenario (static address &#8230;) , but I=
&#8217;m afraid that it may be hard to be exhaustive &#8230; any idea ?<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><spa=
n style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif=
&quot;;color:windowtext"> David Ball [mailto:daviball@cisco.com]
<br>
<b>Sent:</b> Friday, June 10, 2016 13:29<br>
<b>To:</b> LITKOWSKI Stephane OBS/OINIS; l3sm@ietf.org<br>
<b>Subject:</b> Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-=
07.txt<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Hi Stephane,<br>
<br>
More inline:<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">On 09/06/2016 20:08, <a href=3D"mailto:stephane.litk=
owski@orange.com">
stephane.litkowski@orange.com</a> wrote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal"><br>
<br>
<o:p></o:p></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l1 level1 lfo3">
Sn 5.10.2: You said before that the model can only manage P2P connections; =
but this figure (and the next one) show the PE connected to a LAN, not to a=
 CE.&nbsp; I am not sure how to interpret this?&nbsp; Isn't this a case whe=
re the connection is multipoint, not P2P?<o:p></o:p></li></ul>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">[SLI] That&#8217;s still point to point=
. In 5.10.3, customer must order two site network accesses (point
 to point). Each site network network access may be connected to a switch a=
t customer side (same one or not).</span><o:p></o:p></p>
<p class=3D"MsoNormal"><br>
[DB] If there is an L2 switch, then at L3 it is a multipoint connection - t=
he switch is part of the bearer.<br>
<span style=3D"color:#1F497D">[SLI] From a SP &nbsp;point of view no, in te=
rm of service, the customer will have to order two site-network-accesses. H=
ow they are connected to the customer network is not under the SP responsib=
ility. If the customer connects the two
 site-net-access on the same Lan through a switch, it becomes multipoint, b=
ut SP is not essentially aware of it.</span><o:p></o:p></p>
</blockquote>
<p class=3D"MsoNormal"><br>
[DB] I think we may be talking about different cases.&nbsp; I don't mean it=
 may be multipoint because there are multiple site-network-accesses, I'm ta=
lking about the case where there are multiple devices at the customer side =
(could be one or multiple site-network-accesses)
 - rather than a single CE terminating the L3 connection.&nbsp; This seems =
to be what the figure in Sn 5.10.2 is showing.<br>
<br>
<tt><span style=3D"font-size:10.0pt">&nbsp; Host1 ------\</span></tt><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><br>
<tt>&nbsp; Host2 ---- Switch ---------- PE</tt><br>
<tt>&nbsp; Host3 ------/</tt><br>
</span><br>
I don't think it's entirely true in this case that the SP does not need to =
be aware of it - for instance, if the connection address is dynamic, the SP=
 may need to allocate multiple addresses instead of just 1.&nbsp; It also h=
as some impact on other aspects of the
 model; for instance, the routing protocol probably needs to be direct or s=
tatic (not an absolute requirement but probably true in practice), and BFD =
and IPSec probably need to be disabled (since these are inherently P2P).<br>
<br>
<br>
&nbsp;&nbsp;&nbsp; David<br>
<br>
<br>
<br>
<o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre>David Ball<o:p></o:p></pre>
<pre><a href=3D"mailto:daviball@cisco.com">&lt;daviball@cisco.com&gt;</a><o=
:p></o:p></pre>
</div>
<PRE>______________________________________________________________________=
___________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.
</PRE></body>
</html>

--_000_9E32478DFA9976438E7A22F69B08FF921BC5ECBAOPEXCLILMA4corp_--


From nobody Wed Jun 15 05:04:59 2016
Return-Path: <daviball@cisco.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 6207A12D593 for <l3sm@ietfa.amsl.com>; Wed, 15 Jun 2016 05:04:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.936
X-Spam-Level: 
X-Spam-Status: No, score=-15.936 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_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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 bItLNVTTNC0Q for <l3sm@ietfa.amsl.com>; Wed, 15 Jun 2016 05:04:55 -0700 (PDT)
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 BC54A12D548 for <l3sm@ietf.org>; Wed, 15 Jun 2016 05:04:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=20566; q=dns/txt; s=iport; t=1465992294; x=1467201894; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=PkBoP+JxbVc7wlbpPvlZzWZfnkVmweCQW8b/caUmpso=; b=EwQy7TikzkrZBoYu/NkDX4eAA5/ne4z5IzzWbFIh+2/dHPPkzDFSzJyq pLa1f8+8EMrVc0WfQMsb5FC296NK7HhM/1mceoH3JniowSMwBa5hP/rej i3x2oSfYyYoR2tKFm/JVKBGZcImHVULT71/zb8eqr+v4Ik/4l3KnVs2OE 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BMAgB+Q2FX/xbLJq1dgnCBT1K7CIF5h?= =?us-ascii?q?hcCgWwUAQEBAQEBAWUnhEsBAQEELVwLEQEDAQEBIAcHRgMGCAYBDAYCAQGILL4?= =?us-ascii?q?xAQEBAQEBAQEBAQEBAQEBAQEBAQEBHIYngXcIgk6EEhEBSAqFJQWIDpBbiH2FL?= =?us-ascii?q?IFphFKDCoVdj3QeNoIHHIFNOzKIU4E1AQEB?=
X-IronPort-AV: E=Sophos;i="5.26,475,1459814400";  d="scan'208,217";a="635187546"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 Jun 2016 12:04:52 +0000
Received: from [10.63.23.103] (dhcp-ensft1-uk-vla370-10-63-23-103.cisco.com [10.63.23.103]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id u5FC4qwK007683; Wed, 15 Jun 2016 12:04:52 GMT
To: stephane.litkowski@orange.com, "l3sm@ietf.org" <l3sm@ietf.org>
References: <20160606141710.20806.10098.idtracker@ietfa.amsl.com> <27218_1465222795_5755868B_27218_684_1_9E32478DFA9976438E7A22F69B08FF921BC41DA1@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <ec72f8b8-8626-ba2c-bc50-7ce4a0cdc6df@cisco.com> <32265_1465379094_5757E916_32265_10098_3_9E32478DFA9976438E7A22F69B08FF921BC454AB@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <1595f5bb-1838-8164-6e7f-1d383d8bfb87@cisco.com> <7576_1465499325_5759BEBD_7576_3122_1_9E32478DFA9976438E7A22F69B08FF921BC4C5F2@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <bf0bd488-ff9e-ae4e-b37c-6123ae63a8ee@cisco.com> <3459_1465982476_57611E0C_3459_229_11_9E32478DFA9976438E7A22F69B08FF921BC5ECBA@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
From: David Ball <daviball@cisco.com>
Message-ID: <26334e73-054f-0797-31fd-5ad475f68385@cisco.com>
Date: Wed, 15 Jun 2016 13:04:51 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <3459_1465982476_57611E0C_3459_229_11_9E32478DFA9976438E7A22F69B08FF921BC5ECBA@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
Content-Type: multipart/alternative; boundary="------------0BCF39E87DB7B696FC74CF50"
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/4uaJqBkIJDDzTSZvKekJthIsi2E>
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
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: Wed, 15 Jun 2016 12:04:58 -0000

This is a multi-part message in MIME format.
--------------0BCF39E87DB7B696FC74CF50
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

Regarding the use case, I'll leave it to SPs such as yourself to answer. 
:)  But if there is no use case, then we should change those examples in 
the doc.

     David

On 15/06/2016 10:21, stephane.litkowski@orange.com wrote:
>
> Hi David,
>
> I see your point, as a mentioned, it is different from what I was 
> thinking about.
>
> So the question is : do we need to support this kind of architecture 
> (is there a use case ?).
>
> Regarding the two CEs/two PEs cases connected on the same LAN, I think 
> it’s interesting to keep it, it usually used to connect some service 
> platforms. We may need to restrict options in this scenario (static 
> address …) , but I’m afraid that it may be hard to be exhaustive … any 
> idea ?
>
> Thanks,
>
> *From:*David Ball [mailto:daviball@cisco.com]
> *Sent:* Friday, June 10, 2016 13:29
> *To:* LITKOWSKI Stephane OBS/OINIS; l3sm@ietf.org
> *Subject:* Re: [L3sm] I-D Action: 
> draft-ietf-l3sm-l3vpn-service-model-07.txt
>
> Hi Stephane,
>
> More inline:
>
> On 09/06/2016 20:08, stephane.litkowski@orange.com 
> <mailto:stephane.litkowski@orange.com> wrote:
>
>
>
>       * Sn 5.10.2: You said before that the model can only manage P2P
>         connections; but this figure (and the next one) show the PE
>         connected to a LAN, not to a CE.  I am not sure how to
>         interpret this?  Isn't this a case where the connection is
>         multipoint, not P2P?
>
>     [SLI] That’s still point to point. In 5.10.3, customer must order
>     two site network accesses (point to point). Each site network
>     network access may be connected to a switch at customer side (same
>     one or not).
>
>
>     [DB] If there is an L2 switch, then at L3 it is a multipoint
>     connection - the switch is part of the bearer.
>     [SLI] From a SP  point of view no, in term of service, the
>     customer will have to order two site-network-accesses. How they
>     are connected to the customer network is not under the SP
>     responsibility. If the customer connects the two site-net-access
>     on the same Lan through a switch, it becomes multipoint, but SP is
>     not essentially aware of it.
>
>
> [DB] I think we may be talking about different cases.  I don't mean it 
> may be multipoint because there are multiple site-network-accesses, 
> I'm talking about the case where there are multiple devices at the 
> customer side (could be one or multiple site-network-accesses) - 
> rather than a single CE terminating the L3 connection.  This seems to 
> be what the figure in Sn 5.10.2 is showing.
>
>   Host1 ------\
>   Host2 ---- Switch ---------- PE
>   Host3 ------/
>
> I don't think it's entirely true in this case that the SP does not 
> need to be aware of it - for instance, if the connection address is 
> dynamic, the SP may need to allocate multiple addresses instead of 
> just 1.  It also has some impact on other aspects of the model; for 
> instance, the routing protocol probably needs to be direct or static 
> (not an absolute requirement but probably true in practice), and BFD 
> and IPSec probably need to be disabled (since these are inherently P2P).
>
>
>     David
>
>
>
> -- 
> David Ball
> <daviball@cisco.com> <mailto:daviball@cisco.com>
> _________________________________________________________________________________________________________________________
>
> 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.

-- 
David Ball
<daviball@cisco.com>


--------------0BCF39E87DB7B696FC74CF50
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Regarding the use case, I'll leave it to SPs such as yourself to
    answer. :)  But if there is no use case, then we should change those
    examples in the doc.<br>
    <br>
        David<br>
    <br>
    <div class="moz-cite-prefix">On 15/06/2016 10:21,
      <a class="moz-txt-link-abbreviated" href="mailto:stephane.litkowski@orange.com">stephane.litkowski@orange.com</a> wrote:<br>
    </div>
    <blockquote
cite="mid:3459_1465982476_57611E0C_3459_229_11_9E32478DFA9976438E7A22F69B08FF921BC5ECBA@OPEXCLILMA4.corporate.adroot.infra.ftgroup"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <meta name="Generator" content="Microsoft Word 14 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
tt
	{mso-style-priority:99;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	color:black;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle25
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1042284551;
	mso-list-template-ids:1502010652;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1
	{mso-list-id:1656761572;
	mso-list-template-ids:-682878950;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi
            David,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">I
            see your point, as a mentioned, it is different from what I
            was thinking about.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">So
            the question is : do we need to support this kind of
            architecture (is there a use case ?).<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Regarding
            the two CEs/two PEs cases connected on the same LAN, I think
            it’s interesting to keep it, it usually used to connect some
            service platforms. We may need to restrict options in this
            scenario (static address …) , but I’m afraid that it may be
            hard to be exhaustive … any idea ?<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p> </o:p></span></p>
        <div>
          <div style="border:none;border-top:solid #B5C4DF
            1.0pt;padding:3.0pt 0in 0in 0in">
            <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">
                David Ball [<a class="moz-txt-link-freetext" href="mailto:daviball@cisco.com">mailto:daviball@cisco.com</a>]
                <br>
                <b>Sent:</b> Friday, June 10, 2016 13:29<br>
                <b>To:</b> LITKOWSKI Stephane OBS/OINIS; <a class="moz-txt-link-abbreviated" href="mailto:l3sm@ietf.org">l3sm@ietf.org</a><br>
                <b>Subject:</b> Re: [L3sm] I-D Action:
                draft-ietf-l3sm-l3vpn-service-model-07.txt<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal" style="margin-bottom:12.0pt">Hi Stephane,<br>
          <br>
          More inline:<o:p></o:p></p>
        <div>
          <p class="MsoNormal">On 09/06/2016 20:08, <a
              moz-do-not-send="true"
              href="mailto:stephane.litkowski@orange.com">
              <a class="moz-txt-link-abbreviated" href="mailto:stephane.litkowski@orange.com">stephane.litkowski@orange.com</a></a> wrote:<o:p></o:p></p>
        </div>
        <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
          <p class="MsoNormal"><br>
            <br>
            <o:p></o:p></p>
          <ul type="disc">
            <li class="MsoNormal"
              style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1
              level1 lfo3">
              Sn 5.10.2: You said before that the model can only manage
              P2P connections; but this figure (and the next one) show
              the PE connected to a LAN, not to a CE.  I am not sure how
              to interpret this?  Isn't this a case where the connection
              is multipoint, not P2P?<o:p></o:p></li>
          </ul>
          <p class="MsoNormal"
            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">[SLI]
              That’s still point to point. In 5.10.3, customer must
              order two site network accesses (point to point). Each
              site network network access may be connected to a switch
              at customer side (same one or not).</span><o:p></o:p></p>
          <p class="MsoNormal"><br>
            [DB] If there is an L2 switch, then at L3 it is a multipoint
            connection - the switch is part of the bearer.<br>
            <span style="color:#1F497D">[SLI] From a SP  point of view
              no, in term of service, the customer will have to order
              two site-network-accesses. How they are connected to the
              customer network is not under the SP responsibility. If
              the customer connects the two site-net-access on the same
              Lan through a switch, it becomes multipoint, but SP is not
              essentially aware of it.</span><o:p></o:p></p>
        </blockquote>
        <p class="MsoNormal"><br>
          [DB] I think we may be talking about different cases.  I don't
          mean it may be multipoint because there are multiple
          site-network-accesses, I'm talking about the case where there
          are multiple devices at the customer side (could be one or
          multiple site-network-accesses) - rather than a single CE
          terminating the L3 connection.  This seems to be what the
          figure in Sn 5.10.2 is showing.<br>
          <br>
          <tt><span style="font-size:10.0pt">  Host1 ------\</span></tt><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;"><br>
            <tt>  Host2 ---- Switch ---------- PE</tt><br>
            <tt>  Host3 ------/</tt><br>
          </span><br>
          I don't think it's entirely true in this case that the SP does
          not need to be aware of it - for instance, if the connection
          address is dynamic, the SP may need to allocate multiple
          addresses instead of just 1.  It also has some impact on other
          aspects of the model; for instance, the routing protocol
          probably needs to be direct or static (not an absolute
          requirement but probably true in practice), and BFD and IPSec
          probably need to be disabled (since these are inherently P2P).<br>
          <br>
          <br>
              David<br>
          <br>
          <br>
          <br>
          <o:p></o:p></p>
        <pre>-- <o:p></o:p></pre>
        <pre>David Ball<o:p></o:p></pre>
        <pre><a moz-do-not-send="true" href="mailto:daviball@cisco.com">&lt;daviball@cisco.com&gt;</a><o:p></o:p></pre>
      </div>
      <pre>_________________________________________________________________________________________________________________________

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.
</pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
David Ball
<a class="moz-txt-link-rfc2396E" href="mailto:daviball@cisco.com">&lt;daviball@cisco.com&gt;</a></pre>
  </body>
</html>

--------------0BCF39E87DB7B696FC74CF50--


From nobody Wed Jun 15 20:58:49 2016
Return-Path: <ke-oogaki@kddi.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 5467112B050 for <l3sm@ietfa.amsl.com>; Wed, 15 Jun 2016 20:58:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.647
X-Spam-Level: 
X-Spam-Status: No, score=-5.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, 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 g1p4rHOc96rw for <l3sm@ietfa.amsl.com>; Wed, 15 Jun 2016 20:58:46 -0700 (PDT)
Received: from post-send.kddi.com (athena3.kddi.com [27.90.165.196]) by ietfa.amsl.com (Postfix) with ESMTP id 1656C12B00C for <l3sm@ietf.org>; Wed, 15 Jun 2016 20:58:46 -0700 (PDT)
Received: from LTMC2122.kddi.com (LTMC2122.kddi.com [10.206.0.63]) by post-send.kddi.com (KDDI Mail) with ESMTP id 294DEE00CD; Thu, 16 Jun 2016 12:58:45 +0900 (JST)
Received: from LTMC2145.kddi.com ([10.206.0.236] [10.206.0.236]) by LTMC2122.kddi.com with ESMTP; Thu, 16 Jun 2016 12:58:45 +0900
Received: from LTMC2145.kddi.com (localhost [127.0.0.1]) by localhost.kddi.com (Postfix) with ESMTP id F15103A0065; Thu, 16 Jun 2016 12:58:44 +0900 (JST)
Received: from LTMC2153.kddi.com (post-incheck [10.206.0.239]) by LTMC2145.kddi.com (Postfix) with ESMTP id E6EB93A008E; Thu, 16 Jun 2016 12:58:44 +0900 (JST)
Received: from LTMC2153.kddi.com (localhost.localdomain [127.0.0.1]) by LTMC2153.kddi.com  with ESMTP id u5G3wixj017618; Thu, 16 Jun 2016 12:58:44 +0900
Received: from LTMC2153.kddi.com.mid_66891889 (localhost.localdomain [127.0.0.1]) by LTMC2153.kddi.com  with ESMTP id u5G3mgp4009483; Thu, 16 Jun 2016 12:48:42 +0900
X-SA-MID: 66891889
Received: from KDDI1508PC0003 ([10.200.122.178] [10.200.122.178]) by post-smtp2.kddi.com with ESMTPA; Thu, 16 Jun 2016 12:48:41 +0900
From: "Ogaki, Kenichi" <ke-oogaki@kddi.com>
To: "'David Ball'" <daviball@cisco.com>, <stephane.litkowski@orange.com>, <l3sm@ietf.org>
References: <20160606141710.20806.10098.idtracker@ietfa.amsl.com> <27218_1465222795_5755868B_27218_684_1_9E32478DFA9976438E7A22F69B08FF921BC41DA1@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <ec72f8b8-8626-ba2c-bc50-7ce4a0cdc6df@cisco.com> <32265_1465379094_5757E916_32265_10098_3_9E32478DFA9976438E7A22F69B08FF921BC454AB@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <1595f5bb-1838-8164-6e7f-1d383d8bfb87@cisco.com> <7576_1465499325_5759BEBD_7576_3122_1_9E32478DFA9976438E7A22F69B08FF921BC4C5F2@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <bf0bd488-ff9e-ae4e-b37c-6123ae63a8ee@cisco.com> <3459_1465982476_57611E0C_3459_229_11_9E32478DFA9976438E7A22F69B08FF921BC5ECBA@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <26334e73-054f-0797-31fd-5ad475f68385@cisco.com>
In-Reply-To: <26334e73-054f-0797-31fd-5ad475f68385@cisco.com>
Date: Thu, 16 Jun 2016 12:48:41 +0900
Message-ID: <011801d1c781$f9624290$ec26c7b0$@kddi.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJW+Huf9ydieY5WOdIeI0Z4sme4rQH+WJzEAfIETV4BePpT0gH9kPSrA5cjTFkBrBI9qQIhvackAvJMZnyeUyB2kA==
Content-Language: ja
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/BcWtPYxiFUer_oOdrmncHwGi5qw>
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
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, 16 Jun 2016 03:58:48 -0000

Hi David, Stephane,

The use case definitely exists. Then, it's reasonable to keep the example.

We are providing this as an option of our commercial VPN service.

Thanks,
Kenichi

-----Original Message-----
From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of David Ball
Sent: Wednesday, June 15, 2016 9:05 PM
To: stephane.litkowski@orange.com; l3sm@ietf.org
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

Regarding the use case, I'll leave it to SPs such as yourself to answer. :)  But if there is no use case, then we should change those examples in the doc.

    David


On 15/06/2016 10:21, stephane.litkowski@orange.com wrote:


	Hi David,

	 

	I see your point, as a mentioned, it is different from what I was thinking about.

	So the question is : do we need to support this kind of architecture (is there a use case ?).

	Regarding the two CEs/two PEs cases connected on the same LAN, I think it's interesting to keep it, it usually used to connect some service platforms. We may need to restrict options in this scenario (static address .) , but I'm afraid that it may be hard to be exhaustive . any idea ?

	 

	Thanks,

	 

	 

	From: David Ball [mailto:daviball@cisco.com] 
	Sent: Friday, June 10, 2016 13:29
	To: LITKOWSKI Stephane OBS/OINIS; l3sm@ietf.org
	Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

	 

	Hi Stephane,
	
	More inline:

	On 09/06/2016 20:08, <mailto:stephane.litkowski@orange.com> stephane.litkowski@orange.com wrote:

		
		
		

		*	Sn 5.10.2: You said before that the model can only manage P2P connections; but this figure (and the next one) show the PE connected to a LAN, not to a CE.  I am not sure how to interpret this?  Isn't this a case where the connection is multipoint, not P2P?

		[SLI] That's still point to point. In 5.10.3, customer must order two site network accesses (point to point). Each site network network access may be connected to a switch at customer side (same one or not).

		
		[DB] If there is an L2 switch, then at L3 it is a multipoint connection - the switch is part of the bearer.
		[SLI] From a SP  point of view no, in term of service, the customer will have to order two site-network-accesses. How they are connected to the customer network is not under the SP responsibility. If the customer connects the two site-net-access on the same Lan through a switch, it becomes multipoint, but SP is not essentially aware of it.

	
	[DB] I think we may be talking about different cases.  I don't mean it may be multipoint because there are multiple site-network-accesses, I'm talking about the case where there are multiple devices at the customer side (could be one or multiple site-network-accesses) - rather than a single CE terminating the L3 connection.  This seems to be what the figure in Sn 5.10.2 is showing.
	
	  Host1 ------\
	  Host2 ---- Switch ---------- PE
	  Host3 ------/
	
	I don't think it's entirely true in this case that the SP does not need to be aware of it - for instance, if the connection address is dynamic, the SP may need to allocate multiple addresses instead of just 1.  It also has some impact on other aspects of the model; for instance, the routing protocol probably needs to be direct or static (not an absolute requirement but probably true in practice), and BFD and IPSec probably need to be disabled (since these are inherently P2P).
	
	
	    David
	
	
	
	

	-- 
	David Ball
	<daviball@cisco.com> <mailto:daviball@cisco.com> 
	_________________________________________________________________________________________________________________________
	
	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.


-- 
David Ball
<daviball@cisco.com> <mailto:daviball@cisco.com> 


From nobody Thu Jun 16 06:07:14 2016
Return-Path: <stephane.litkowski@orange.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 E000812D594 for <l3sm@ietfa.amsl.com>; Thu, 16 Jun 2016 06:07:11 -0700 (PDT)
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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 k5SQfRxqlZ1R for <l3sm@ietfa.amsl.com>; Thu, 16 Jun 2016 06:07:09 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFC0B12D5F9 for <l3sm@ietf.org>; Thu, 16 Jun 2016 06:07:08 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 3434B324106; Thu, 16 Jun 2016 15:07:07 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.61]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 05702238073; Thu, 16 Jun 2016 15:07:07 +0200 (CEST)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM7E.corporate.adroot.infra.ftgroup ([fe80::b91c:ea2c:ac8a:7462%19]) with mapi id 14.03.0294.000; Thu, 16 Jun 2016 15:07:06 +0200
From: <stephane.litkowski@orange.com>
To: "Ogaki, Kenichi" <ke-oogaki@kddi.com>, 'David Ball' <daviball@cisco.com>,  "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
Thread-Index: AQHRv/4i8iSSM4mtWE6AeESR5nwEZZ/cfFGwgAGg6gCAASznEIABf5oAgAC53hCAAPGPgIAH11+AgAAOMoCAAQe0gIAAvNzg
Date: Thu, 16 Jun 2016 13:07:06 +0000
Message-ID: <26167_1466082427_5762A47B_26167_5405_1_9E32478DFA9976438E7A22F69B08FF921BC6338E@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <20160606141710.20806.10098.idtracker@ietfa.amsl.com> <27218_1465222795_5755868B_27218_684_1_9E32478DFA9976438E7A22F69B08FF921BC41DA1@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <ec72f8b8-8626-ba2c-bc50-7ce4a0cdc6df@cisco.com> <32265_1465379094_5757E916_32265_10098_3_9E32478DFA9976438E7A22F69B08FF921BC454AB@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <1595f5bb-1838-8164-6e7f-1d383d8bfb87@cisco.com> <7576_1465499325_5759BEBD_7576_3122_1_9E32478DFA9976438E7A22F69B08FF921BC4C5F2@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <bf0bd488-ff9e-ae4e-b37c-6123ae63a8ee@cisco.com> <3459_1465982476_57611E0C_3459_229_11_9E32478DFA9976438E7A22F69B08FF921BC5ECBA@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <26334e73-054f-0797-31fd-5ad475f68385@cisco.com> <011801d1c781$f9624290$ec26c7b0$@kddi.com>
In-Reply-To: <011801d1c781$f9624290$ec26c7b0$@kddi.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.1]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.6.16.120316
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/2nVE9laUpTYxUxnZ3NRNnZX89jo>
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
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, 16 Jun 2016 13:07:12 -0000

Hi Kenichi,

Do you think we need a special leaf to identify that a particular site-netw=
ork-access is multipoint rather than p2p ?
Or don't we care ?

As David pointed, for some features, there may be an issue : security featu=
res, oam ...
For dynamic IP addressing we may need a additional leaf to precise the numb=
er of addresses to be allocated (currently as we assume p2p, it's only 1).
Any idea on how to address it globally ?

Best Regards,


-----Original Message-----
From: Ogaki, Kenichi [mailto:ke-oogaki@kddi.com]=20
Sent: Thursday, June 16, 2016 05:49
To: 'David Ball'; LITKOWSKI Stephane OBS/OINIS; l3sm@ietf.org
Subject: RE: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

Hi David, Stephane,

The use case definitely exists. Then, it's reasonable to keep the example.

We are providing this as an option of our commercial VPN service.

Thanks,
Kenichi

-----Original Message-----
From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of David Ball
Sent: Wednesday, June 15, 2016 9:05 PM
To: stephane.litkowski@orange.com; l3sm@ietf.org
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

Regarding the use case, I'll leave it to SPs such as yourself to answer. :)=
  But if there is no use case, then we should change those examples in the =
doc.

    David


On 15/06/2016 10:21, stephane.litkowski@orange.com wrote:


	Hi David,

=09=20

	I see your point, as a mentioned, it is different from what I was thinking=
 about.

	So the question is : do we need to support this kind of architecture (is t=
here a use case ?).

	Regarding the two CEs/two PEs cases connected on the same LAN, I think it'=
s interesting to keep it, it usually used to connect some service platforms=
. We may need to restrict options in this scenario (static address .) , but=
 I'm afraid that it may be hard to be exhaustive . any idea ?

=09=20

	Thanks,

=09=20

=09=20

	From: David Ball [mailto:daviball@cisco.com]=20
	Sent: Friday, June 10, 2016 13:29
	To: LITKOWSKI Stephane OBS/OINIS; l3sm@ietf.org
	Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

=09=20

	Hi Stephane,
=09
	More inline:

	On 09/06/2016 20:08, <mailto:stephane.litkowski@orange.com> stephane.litko=
wski@orange.com wrote:

=09=09
=09=09
=09=09

		*	Sn 5.10.2: You said before that the model can only manage P2P connectio=
ns; but this figure (and the next one) show the PE connected to a LAN, not =
to a CE.  I am not sure how to interpret this?  Isn't this a case where the=
 connection is multipoint, not P2P?

		[SLI] That's still point to point. In 5.10.3, customer must order two sit=
e network accesses (point to point). Each site network network access may b=
e connected to a switch at customer side (same one or not).

=09=09
		[DB] If there is an L2 switch, then at L3 it is a multipoint connection -=
 the switch is part of the bearer.
		[SLI] From a SP  point of view no, in term of service, the customer will =
have to order two site-network-accesses. How they are connected to the cust=
omer network is not under the SP responsibility. If the customer connects t=
he two site-net-access on the same Lan through a switch, it becomes multipo=
int, but SP is not essentially aware of it.

=09
	[DB] I think we may be talking about different cases.  I don't mean it may=
 be multipoint because there are multiple site-network-accesses, I'm talkin=
g about the case where there are multiple devices at the customer side (cou=
ld be one or multiple site-network-accesses) - rather than a single CE term=
inating the L3 connection.  This seems to be what the figure in Sn 5.10.2 i=
s showing.
=09
	  Host1 ------\
	  Host2 ---- Switch ---------- PE
	  Host3 ------/
=09
	I don't think it's entirely true in this case that the SP does not need to=
 be aware of it - for instance, if the connection address is dynamic, the S=
P may need to allocate multiple addresses instead of just 1.  It also has s=
ome impact on other aspects of the model; for instance, the routing protoco=
l probably needs to be direct or static (not an absolute requirement but pr=
obably true in practice), and BFD and IPSec probably need to be disabled (s=
ince these are inherently P2P).
=09
=09
	    David
=09
=09
=09
=09

	--=20
	David Ball
	<daviball@cisco.com> <mailto:daviball@cisco.com>=20
	__________________________________________________________________________=
_______________________________________________
=09
	Ce message et ses pieces jointes peuvent contenir des informations confide=
ntielles ou privilegiees et ne doivent donc
	pas etre diffuses, exploites ou copies sans autorisation. Si vous avez rec=
u ce message par erreur, veuillez le signaler
	a l'expediteur et le detruire ainsi que les pieces jointes. Les messages e=
lectroniques etant susceptibles d'alteration,
	Orange decline toute responsabilite si ce message a ete altere, deforme ou=
 falsifie. Merci.
=09
	This message and its attachments may contain confidential or privileged in=
formation 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 del=
ete 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.


--=20
David Ball
<daviball@cisco.com> <mailto:daviball@cisco.com>=20


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.


From nobody Thu Jun 16 19:59:20 2016
Return-Path: <ke-oogaki@kddi.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 4821A12DAA0 for <l3sm@ietfa.amsl.com>; Thu, 16 Jun 2016 19:59:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.647
X-Spam-Level: 
X-Spam-Status: No, score=-5.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, 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 wFigRd8UMbG1 for <l3sm@ietfa.amsl.com>; Thu, 16 Jun 2016 19:59:17 -0700 (PDT)
Received: from post-send.kddi.com (athena3.kddi.com [27.90.165.196]) by ietfa.amsl.com (Postfix) with ESMTP id DF24E12DA17 for <l3sm@ietf.org>; Thu, 16 Jun 2016 19:59:16 -0700 (PDT)
Received: from LTMC2123.kddi.com (LTMC2123.kddi.com [10.206.0.65]) by post-send.kddi.com (KDDI Mail) with ESMTP id B9A06E00A6; Fri, 17 Jun 2016 11:59:15 +0900 (JST)
Received: from LTMC2145.kddi.com ([10.206.0.236] [10.206.0.236]) by LTMC2123.kddi.com with ESMTP; Fri, 17 Jun 2016 11:59:15 +0900
Received: from LTMC2145.kddi.com (localhost [127.0.0.1]) by localhost.kddi.com (Postfix) with ESMTP id 94F0F3A006B; Fri, 17 Jun 2016 11:59:15 +0900 (JST)
Received: from LTMC2153.kddi.com (post-incheck [10.206.0.239]) by LTMC2145.kddi.com (Postfix) with ESMTP id 89C5D3A0065; Fri, 17 Jun 2016 11:59:15 +0900 (JST)
Received: from LTMC2153.kddi.com (localhost.localdomain [127.0.0.1]) by LTMC2153.kddi.com  with ESMTP id u5H2xF66009514; Fri, 17 Jun 2016 11:59:15 +0900
Received: from LTMC2153.kddi.com.mid_66984897 (localhost.localdomain [127.0.0.1]) by LTMC2153.kddi.com  with ESMTP id u5H2nDPl029824; Fri, 17 Jun 2016 11:49:14 +0900
X-SA-MID: 66984897
Received: from KDDI1508PC0003 ([10.200.122.178] [10.200.122.178]) by post-smtp2.kddi.com with ESMTPA; Fri, 17 Jun 2016 11:49:13 +0900
From: "Ogaki, Kenichi" <ke-oogaki@kddi.com>
To: <stephane.litkowski@orange.com>, "'David Ball'" <daviball@cisco.com>, <l3sm@ietf.org>
References: <20160606141710.20806.10098.idtracker@ietfa.amsl.com> <27218_1465222795_5755868B_27218_684_1_9E32478DFA9976438E7A22F69B08FF921BC41DA1@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <ec72f8b8-8626-ba2c-bc50-7ce4a0cdc6df@cisco.com> <32265_1465379094_5757E916_32265_10098_3_9E32478DFA9976438E7A22F69B08FF921BC454AB@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <1595f5bb-1838-8164-6e7f-1d383d8bfb87@cisco.com> <7576_1465499325_5759BEBD_7576_3122_1_9E32478DFA9976438E7A22F69B08FF921BC4C5F2@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <bf0bd488-ff9e-ae4e-b37c-6123ae63a8ee@cisco.com> <3459_1465982476_57611E0C_3459_229_11_9E32478DFA9976438E7A22F69B08FF921BC5ECBA@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <26334e73-054f-0797-31fd-5ad475f68385@cisco.com> <011801d1c781$f9624290$ec26c7b0$@kddi.com> <26167_1466082427_5762A47B_26167_5405_1_9E32478DFA9976438E7A22F69B08FF921BC6338E@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
In-Reply-To: <26167_1466082427_5762A47B_26167_5405_1_9E32478DFA9976438E7A22F69B08FF921BC6338E@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
Date: Fri, 17 Jun 2016 11:49:13 +0900
Message-ID: <00f901d1c842$d4ebb970$7ec32c50$@kddi.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJW+Huf9ydieY5WOdIeI0Z4sme4rQH+WJzEAfIETV4BePpT0gH9kPSrA5cjTFkBrBI9qQIhvackAvJMZnwDP7hh6QITxPMFnioBn3A=
Content-Language: ja
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/JeOCGYZu2C9-WYBgTHWV2wjAawc>
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
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: Fri, 17 Jun 2016 02:59:19 -0000

Hi Stephane, David,

IMO, the current model is enough generic to cover the use case.

> I don't think it's entirely true in this case that the SP does not 
> need to be aware of it - for instance, if the connection address is 
> dynamic, the SP may need to allocate multiple addresses instead of 
> just 1.  It also has some impact on other aspects of the model; for 
> instance, the routing protocol probably needs to be direct or static 
> (not an absolute requirement but probably true in practice), and BFD 
> and IPSec probably need to be disabled (since these are inherently P2P).

The encryption or oam isn't mandatory even in p2p case, then we can apply the current model without any restriction. Just not specify them.

The current address-allocation-type is provider-dhcp, static-address (and slaac). The provider-dhcp works for assigning multiple addresses. Am I missing something?
In the static-address case, we only have to specify PE side.

>5.2.1.2.1.  IP addressing
>
>   o  static-address : Addresses will be assigned manually on both
>      sides, this is applicable to both IPv4 and IPv6 addressing.

We may be able to change the above sentence to cover this use case like:
   o  static-address : Addresses will be assigned manually on both sides, or one side in the case of Direct LAN connection, this is applicable to both IPv4 and IPv6 addressing.

For the static routing case, a customer may configure the following topology, but this can be also covered with cascaded-lan-prefixes.

	  Host1 ------\
	  Host2 ---- Switch ---------- PE
LAN  ---- Router -----/


Here is the simplest one's example.
    <site-network-accesses>
        <site-network-access>
            <site-network-access-id>Spoke_Site1</site-network-access-id>
            <ip-connection>
                <ipv4>
                    <address-allocation-type>static-address</address-allocation-type>
                    <addresses>
                      <provider-address>203.0.113.254</provider-address>
                      <mask>24</mask>
                    </addresses>
                </ipv4>
            </ip-connection>
            <vpn-attachment>
                <vpn-id>12456487</vpn-id>
                <site-role>spoke-role</site-role>
            </vpn-attachment>
            <routing-protocols>
                <routing-protocol>
                    <type>direct</type>
                </routing-protocol>
            </routing-protocols>
        </site-network-access>
    </site-network-accesses>


Am I missing something more?

Thanks,
Kenichi

-----Original Message-----
From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of stephane.litkowski@orange.com
Sent: Thursday, June 16, 2016 10:07 PM
To: Ogaki, Kenichi; 'David Ball'; l3sm@ietf.org
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

Hi Kenichi,

Do you think we need a special leaf to identify that a particular site-network-access is multipoint rather than p2p ?
Or don't we care ?

As David pointed, for some features, there may be an issue : security features, oam ...
For dynamic IP addressing we may need a additional leaf to precise the number of addresses to be allocated (currently as we assume p2p, it's only 1).
Any idea on how to address it globally ?

Best Regards,


-----Original Message-----
From: Ogaki, Kenichi [mailto:ke-oogaki@kddi.com] 
Sent: Thursday, June 16, 2016 05:49
To: 'David Ball'; LITKOWSKI Stephane OBS/OINIS; l3sm@ietf.org
Subject: RE: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

Hi David, Stephane,

The use case definitely exists. Then, it's reasonable to keep the example.

We are providing this as an option of our commercial VPN service.

Thanks,
Kenichi

-----Original Message-----
From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of David Ball
Sent: Wednesday, June 15, 2016 9:05 PM
To: stephane.litkowski@orange.com; l3sm@ietf.org
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

Regarding the use case, I'll leave it to SPs such as yourself to answer. :)  But if there is no use case, then we should change those examples in the doc.

    David


On 15/06/2016 10:21, stephane.litkowski@orange.com wrote:


	Hi David,

	 

	I see your point, as a mentioned, it is different from what I was thinking about.

	So the question is : do we need to support this kind of architecture (is there a use case ?).

	Regarding the two CEs/two PEs cases connected on the same LAN, I think it's interesting to keep it, it usually used to connect some service platforms. We may need to restrict options in this scenario (static address .) , but I'm afraid that it may be hard to be exhaustive . any idea ?

	 

	Thanks,

	 

	 

	From: David Ball [mailto:daviball@cisco.com] 
	Sent: Friday, June 10, 2016 13:29
	To: LITKOWSKI Stephane OBS/OINIS; l3sm@ietf.org
	Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

	 

	Hi Stephane,
	
	More inline:

	On 09/06/2016 20:08, <mailto:stephane.litkowski@orange.com> stephane.litkowski@orange.com wrote:

		
		
		

		*	Sn 5.10.2: You said before that the model can only manage P2P connections; but this figure (and the next one) show the PE connected to a LAN, not to a CE.  I am not sure how to interpret this?  Isn't this a case where the connection is multipoint, not P2P?

		[SLI] That's still point to point. In 5.10.3, customer must order two site network accesses (point to point). Each site network network access may be connected to a switch at customer side (same one or not).

		
		[DB] If there is an L2 switch, then at L3 it is a multipoint connection - the switch is part of the bearer.
		[SLI] From a SP  point of view no, in term of service, the customer will have to order two site-network-accesses. How they are connected to the customer network is not under the SP responsibility. If the customer connects the two site-net-access on the same Lan through a switch, it becomes multipoint, but SP is not essentially aware of it.

	
	[DB] I think we may be talking about different cases.  I don't mean it may be multipoint because there are multiple site-network-accesses, I'm talking about the case where there are multiple devices at the customer side (could be one or multiple site-network-accesses) - rather than a single CE terminating the L3 connection.  This seems to be what the figure in Sn 5.10.2 is showing.
	
	  Host1 ------\
	  Host2 ---- Switch ---------- PE
	  Host3 ------/
	
	I don't think it's entirely true in this case that the SP does not need to be aware of it - for instance, if the connection address is dynamic, the SP may need to allocate multiple addresses instead of just 1.  It also has some impact on other aspects of the model; for instance, the routing protocol probably needs to be direct or static (not an absolute requirement but probably true in practice), and BFD and IPSec probably need to be disabled (since these are inherently P2P).
	
	
	    David
	
	
	
	

	-- 
	David Ball
	<daviball@cisco.com> <mailto:daviball@cisco.com> 
	_________________________________________________________________________________________________________________________
	
	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.


-- 
David Ball
<daviball@cisco.com> <mailto:daviball@cisco.com> 


_________________________________________________________________________________________________________________________

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
L3sm@ietf.org
https://www.ietf.org/mailman/listinfo/l3sm


From nobody Thu Jun 16 23:28:47 2016
Return-Path: <stephane.litkowski@orange.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 9310D12D0BD for <l3sm@ietfa.amsl.com>; Thu, 16 Jun 2016 23:28:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.345
X-Spam-Level: 
X-Spam-Status: No, score=-3.345 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 6m6kh9N_KkOD for <l3sm@ietfa.amsl.com>; Thu, 16 Jun 2016 23:28:43 -0700 (PDT)
Received: from relais-inet.orange.com (relais-nor35.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F158412B024 for <l3sm@ietf.org>; Thu, 16 Jun 2016 23:28:42 -0700 (PDT)
Received: from opfednr03.francetelecom.fr (unknown [xx.xx.xx.67]) by opfednr25.francetelecom.fr (ESMTP service) with ESMTP id 8DB69180316; Fri, 17 Jun 2016 08:28:41 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.32]) by opfednr03.francetelecom.fr (ESMTP service) with ESMTP id 55BB91A0069; Fri, 17 Jun 2016 08:28:41 +0200 (CEST)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM32.corporate.adroot.infra.ftgroup ([fe80::8924:188:2124:a046%19]) with mapi id 14.03.0294.000; Fri, 17 Jun 2016 08:28:41 +0200
From: <stephane.litkowski@orange.com>
To: "Ogaki, Kenichi" <ke-oogaki@kddi.com>, 'David Ball' <daviball@cisco.com>,  "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
Thread-Index: AQHRv/4i8iSSM4mtWE6AeESR5nwEZZ/cfFGwgAGg6gCAASznEIABf5oAgAC53hCAAPGPgIAH11+AgAAOMoCAAQe0gIAAvNzggADE24CAAF4q0A==
Date: Fri, 17 Jun 2016 06:28:40 +0000
Message-ID: <18935_1466144921_57639899_18935_238_11_9E32478DFA9976438E7A22F69B08FF921BC65DC0@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <20160606141710.20806.10098.idtracker@ietfa.amsl.com> <27218_1465222795_5755868B_27218_684_1_9E32478DFA9976438E7A22F69B08FF921BC41DA1@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <ec72f8b8-8626-ba2c-bc50-7ce4a0cdc6df@cisco.com> <32265_1465379094_5757E916_32265_10098_3_9E32478DFA9976438E7A22F69B08FF921BC454AB@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <1595f5bb-1838-8164-6e7f-1d383d8bfb87@cisco.com> <7576_1465499325_5759BEBD_7576_3122_1_9E32478DFA9976438E7A22F69B08FF921BC4C5F2@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <bf0bd488-ff9e-ae4e-b37c-6123ae63a8ee@cisco.com> <3459_1465982476_57611E0C_3459_229_11_9E32478DFA9976438E7A22F69B08FF921BC5ECBA@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <26334e73-054f-0797-31fd-5ad475f68385@cisco.com> <011801d1c781$f9624290$ec26c7b0$@kddi.com> <26167_1466082427_5762A47B_26167_5405_1_9E32478DFA9976438E7A22F69B08FF921BC6338E@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <00f901d1c842$d4ebb970$7ec32c50$@kddi.com>
In-Reply-To: <00f901d1c842$d4ebb970$7ec32c50$@kddi.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.1]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/e_pug9z1fc7BcIqikg3mZhRz57k>
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
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: Fri, 17 Jun 2016 06:28:45 -0000

Hi Kenichi,

Some comment inline.

Best Regards,

-----Original Message-----
From: Ogaki, Kenichi [mailto:ke-oogaki@kddi.com]=20
Sent: Friday, June 17, 2016 04:49
To: LITKOWSKI Stephane OBS/OINIS; 'David Ball'; l3sm@ietf.org
Subject: RE: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

Hi Stephane, David,

IMO, the current model is enough generic to cover the use case.

> I don't think it's entirely true in this case that the SP does not=20
> need to be aware of it - for instance, if the connection address is=20
> dynamic, the SP may need to allocate multiple addresses instead of=20
> just 1.  It also has some impact on other aspects of the model; for=20
> instance, the routing protocol probably needs to be direct or static=20
> (not an absolute requirement but probably true in practice), and BFD=20
> and IPSec probably need to be disabled (since these are inherently P2P).

The encryption or oam isn't mandatory even in p2p case, then we can apply t=
he current model without any restriction. Just not specify them.
[SLI] Yes it's optional, but the issue is that it may work on p2p but not o=
n mp connections. So if customer requests it and if SP is not aware that it=
 will be a mp connection, oam or encryption may not work.

The current address-allocation-type is provider-dhcp, static-address (and s=
laac). The provider-dhcp works for assigning multiple addresses. Am I missi=
ng something?
[SLI] Yes, but the SP may need to know how many addresses are needed (to im=
plement correctly the DHCP pool)
In the static-address case, we only have to specify PE side.
[SLI] Static is not an issue

>5.2.1.2.1.  IP addressing
>
>   o  static-address : Addresses will be assigned manually on both
>      sides, this is applicable to both IPv4 and IPv6 addressing.

We may be able to change the above sentence to cover this use case like:
   o  static-address : Addresses will be assigned manually on both sides, o=
r one side in the case of Direct LAN connection, this is applicable to both=
 IPv4 and IPv6 addressing.

For the static routing case, a customer may configure the following topolog=
y, but this can be also covered with cascaded-lan-prefixes.

	  Host1 ------\
	  Host2 ---- Switch ---------- PE
LAN  ---- Router -----/


Here is the simplest one's example.
    <site-network-accesses>
        <site-network-access>
            <site-network-access-id>Spoke_Site1</site-network-access-id>
            <ip-connection>
                <ipv4>
                    <address-allocation-type>static-address</address-alloca=
tion-type>
                    <addresses>
                      <provider-address>203.0.113.254</provider-address>
                      <mask>24</mask>
                    </addresses>
                </ipv4>
            </ip-connection>
            <vpn-attachment>
                <vpn-id>12456487</vpn-id>
                <site-role>spoke-role</site-role>
            </vpn-attachment>
            <routing-protocols>
                <routing-protocol>
                    <type>direct</type>
                </routing-protocol>
            </routing-protocols>
        </site-network-access>
    </site-network-accesses>


Am I missing something more?

Thanks,
Kenichi

-----Original Message-----
From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of stephane.litkowski@o=
range.com
Sent: Thursday, June 16, 2016 10:07 PM
To: Ogaki, Kenichi; 'David Ball'; l3sm@ietf.org
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

Hi Kenichi,

Do you think we need a special leaf to identify that a particular site-netw=
ork-access is multipoint rather than p2p ?
Or don't we care ?

As David pointed, for some features, there may be an issue : security featu=
res, oam ...
For dynamic IP addressing we may need a additional leaf to precise the numb=
er of addresses to be allocated (currently as we assume p2p, it's only 1).
Any idea on how to address it globally ?

Best Regards,


-----Original Message-----
From: Ogaki, Kenichi [mailto:ke-oogaki@kddi.com]
Sent: Thursday, June 16, 2016 05:49
To: 'David Ball'; LITKOWSKI Stephane OBS/OINIS; l3sm@ietf.org
Subject: RE: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

Hi David, Stephane,

The use case definitely exists. Then, it's reasonable to keep the example.

We are providing this as an option of our commercial VPN service.

Thanks,
Kenichi

-----Original Message-----
From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of David Ball
Sent: Wednesday, June 15, 2016 9:05 PM
To: stephane.litkowski@orange.com; l3sm@ietf.org
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

Regarding the use case, I'll leave it to SPs such as yourself to answer. :)=
  But if there is no use case, then we should change those examples in the =
doc.

    David


On 15/06/2016 10:21, stephane.litkowski@orange.com wrote:


	Hi David,

=09=20

	I see your point, as a mentioned, it is different from what I was thinking=
 about.

	So the question is : do we need to support this kind of architecture (is t=
here a use case ?).

	Regarding the two CEs/two PEs cases connected on the same LAN, I think it'=
s interesting to keep it, it usually used to connect some service platforms=
. We may need to restrict options in this scenario (static address .) , but=
 I'm afraid that it may be hard to be exhaustive . any idea ?

=09=20

	Thanks,

=09=20

=09=20

	From: David Ball [mailto:daviball@cisco.com]=20
	Sent: Friday, June 10, 2016 13:29
	To: LITKOWSKI Stephane OBS/OINIS; l3sm@ietf.org
	Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

=09=20

	Hi Stephane,
=09
	More inline:

	On 09/06/2016 20:08, <mailto:stephane.litkowski@orange.com> stephane.litko=
wski@orange.com wrote:

=09=09
=09=09
=09=09

		*	Sn 5.10.2: You said before that the model can only manage P2P connectio=
ns; but this figure (and the next one) show the PE connected to a LAN, not =
to a CE.  I am not sure how to interpret this?  Isn't this a case where the=
 connection is multipoint, not P2P?

		[SLI] That's still point to point. In 5.10.3, customer must order two sit=
e network accesses (point to point). Each site network network access may b=
e connected to a switch at customer side (same one or not).

=09=09
		[DB] If there is an L2 switch, then at L3 it is a multipoint connection -=
 the switch is part of the bearer.
		[SLI] From a SP  point of view no, in term of service, the customer will =
have to order two site-network-accesses. How they are connected to the cust=
omer network is not under the SP responsibility. If the customer connects t=
he two site-net-access on the same Lan through a switch, it becomes multipo=
int, but SP is not essentially aware of it.

=09
	[DB] I think we may be talking about different cases.  I don't mean it may=
 be multipoint because there are multiple site-network-accesses, I'm talkin=
g about the case where there are multiple devices at the customer side (cou=
ld be one or multiple site-network-accesses) - rather than a single CE term=
inating the L3 connection.  This seems to be what the figure in Sn 5.10.2 i=
s showing.
=09
	  Host1 ------\
	  Host2 ---- Switch ---------- PE
	  Host3 ------/
=09
	I don't think it's entirely true in this case that the SP does not need to=
 be aware of it - for instance, if the connection address is dynamic, the S=
P may need to allocate multiple addresses instead of just 1.  It also has s=
ome impact on other aspects of the model; for instance, the routing protoco=
l probably needs to be direct or static (not an absolute requirement but pr=
obably true in practice), and BFD and IPSec probably need to be disabled (s=
ince these are inherently P2P).
=09
=09
	    David
=09
=09
=09
=09

	--=20
	David Ball
	<daviball@cisco.com> <mailto:daviball@cisco.com>=20
	__________________________________________________________________________=
_______________________________________________
=09
	Ce message et ses pieces jointes peuvent contenir des informations confide=
ntielles ou privilegiees et ne doivent donc
	pas etre diffuses, exploites ou copies sans autorisation. Si vous avez rec=
u ce message par erreur, veuillez le signaler
	a l'expediteur et le detruire ainsi que les pieces jointes. Les messages e=
lectroniques etant susceptibles d'alteration,
	Orange decline toute responsabilite si ce message a ete altere, deforme ou=
 falsifie. Merci.
=09
	This message and its attachments may contain confidential or privileged in=
formation 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 del=
ete 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.


--
David Ball
<daviball@cisco.com> <mailto:daviball@cisco.com>=20


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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
L3sm@ietf.org
https://www.ietf.org/mailman/listinfo/l3sm


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.


From nobody Fri Jun 17 02:48:42 2016
Return-Path: <ke-oogaki@kddi.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 25D4E12B04C for <l3sm@ietfa.amsl.com>; Fri, 17 Jun 2016 02:48:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.647
X-Spam-Level: 
X-Spam-Status: No, score=-5.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, 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 OUU-lNCfZeBy for <l3sm@ietfa.amsl.com>; Fri, 17 Jun 2016 02:48:37 -0700 (PDT)
Received: from post-send.kddi.com (athena4.kddi.com [27.90.165.197]) by ietfa.amsl.com (Postfix) with ESMTP id E7A8412B027 for <l3sm@ietf.org>; Fri, 17 Jun 2016 02:48:36 -0700 (PDT)
Received: from LTMC2122.kddi.com (LTMC2122.kddi.com [10.206.0.63]) by post-send.kddi.com (KDDI Mail) with ESMTP id A8B0F120070; Fri, 17 Jun 2016 18:48:35 +0900 (JST)
Received: from LTMC2146.kddi.com ([10.206.0.236] [10.206.0.236]) by LTMC2122.kddi.com with ESMTP; Fri, 17 Jun 2016 18:48:35 +0900
Received: from LTMC2146.kddi.com (localhost [127.0.0.1]) by localhost.kddi.com (Postfix) with ESMTP id 843BC30005D; Fri, 17 Jun 2016 18:48:35 +0900 (JST)
Received: from LTMC2151.kddi.com (post-incheck [10.206.0.239]) by LTMC2146.kddi.com (Postfix) with ESMTP id 793ED300050; Fri, 17 Jun 2016 18:48:35 +0900 (JST)
Received: from LTMC2151.kddi.com (localhost.localdomain [127.0.0.1]) by LTMC2151.kddi.com  with ESMTP id u5H9mZCp022230; Fri, 17 Jun 2016 18:48:35 +0900
Received: from LTMC2151.kddi.com.mid_39876088 (localhost.localdomain [127.0.0.1]) by LTMC2151.kddi.com  with ESMTP id u5H9cWoM011444; Fri, 17 Jun 2016 18:38:32 +0900
X-SA-MID: 39876088
Received: from KDDI1508PC0003 ([10.200.122.178] [10.200.122.178]) by post-smtp2.kddi.com with ESMTPA; Fri, 17 Jun 2016 18:38:31 +0900
From: "Ogaki, Kenichi" <ke-oogaki@kddi.com>
To: <stephane.litkowski@orange.com>, "'David Ball'" <daviball@cisco.com>, <l3sm@ietf.org>
References: <20160606141710.20806.10098.idtracker@ietfa.amsl.com> <27218_1465222795_5755868B_27218_684_1_9E32478DFA9976438E7A22F69B08FF921BC41DA1@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <ec72f8b8-8626-ba2c-bc50-7ce4a0cdc6df@cisco.com> <32265_1465379094_5757E916_32265_10098_3_9E32478DFA9976438E7A22F69B08FF921BC454AB@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <1595f5bb-1838-8164-6e7f-1d383d8bfb87@cisco.com> <7576_1465499325_5759BEBD_7576_3122_1_9E32478DFA9976438E7A22F69B08FF921BC4C5F2@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <bf0bd488-ff9e-ae4e-b37c-6123ae63a8ee@cisco.com> <3459_1465982476_57611E0C_3459_229_11_9E32478DFA9976438E7A22F69B08FF921BC5ECBA@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <26334e73-054f-0797-31fd-5ad475f68385@cisco.com> <011801d1c781$f9624290$ec26c7b0$@kddi.com> <26167_1466082427_5762A47B_26167_5405_1_9E32478DFA9976438E7A22F69B08FF921BC6338E@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <00f901d1c842$d4ebb970$7ec32c50$@kddi.com> <18935_1466144921_576 39899_18935_238_11_9E3 2478DFA9976438E7A22F69B08FF921BC65DC0@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
In-Reply-To: <18935_1466144921_57639899_18935_238_11_9E32478DFA9976438E7A22F69B08FF921BC65DC0@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
Date: Fri, 17 Jun 2016 18:38:31 +0900
Message-ID: <015801d1c87c$02b855f0$082901d0$@kddi.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJW+Huf9ydieY5WOdIeI0Z4sme4rQH+WJzEAfIETV4BePpT0gH9kPSrA5cjTFkBrBI9qQIhvackAvJMZnwDP7hh6QITxPMFAYruR6gBwfzeK54P5AGg
Content-Language: ja
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/0D3hY7WZFalE6jm5CdJ0sbXgOq0>
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
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: Fri, 17 Jun 2016 09:48:40 -0000

Hi Stephane,

See comments inline, please.

Thanks,
Kenichi

-----Original Message-----
From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of stephane.litkowski@orange.com
Sent: Friday, June 17, 2016 3:29 PM
To: Ogaki, Kenichi; 'David Ball'; l3sm@ietf.org
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

Hi Kenichi,

Some comment inline.

Best Regards,

-----Original Message-----
From: Ogaki, Kenichi [mailto:ke-oogaki@kddi.com]
Sent: Friday, June 17, 2016 04:49
To: LITKOWSKI Stephane OBS/OINIS; 'David Ball'; l3sm@ietf.org
Subject: RE: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

Hi Stephane, David,

IMO, the current model is enough generic to cover the use case.

> I don't think it's entirely true in this case that the SP does not 
> need to be aware of it - for instance, if the connection address is 
> dynamic, the SP may need to allocate multiple addresses instead of 
> just 1.  It also has some impact on other aspects of the model; for 
> instance, the routing protocol probably needs to be direct or static 
> (not an absolute requirement but probably true in practice), and BFD 
> and IPSec probably need to be disabled (since these are inherently P2P).

The encryption or oam isn't mandatory even in p2p case, then we can apply the current model without any restriction. Just not specify them.
[SLI] Yes it's optional, but the issue is that it may work on p2p but not on mp connections. So if customer requests it and if SP is not aware that it will be a mp connection, oam or encryption may not work.

[KO] We can restrict to avoid such impossible combinations by using when statement, but this can be also achieved outside of the model. Operator can just reject the impossible request and return the error. 
I think we don't need such a strict modeling without a strong requirement for now. 


The current address-allocation-type is provider-dhcp, static-address (and slaac). The provider-dhcp works for assigning multiple addresses. Am I missing something?
[SLI] Yes, but the SP may need to know how many addresses are needed (to implement correctly the DHCP pool)

[KO] It may be useful as an option. I'm asking my colleague if we need.

 In the static-address case, we only have to specify PE side.
[SLI] Static is not an issue

>5.2.1.2.1.  IP addressing
>
>   o  static-address : Addresses will be assigned manually on both
>      sides, this is applicable to both IPv4 and IPv6 addressing.

We may be able to change the above sentence to cover this use case like:
   o  static-address : Addresses will be assigned manually on both sides, or one side in the case of Direct LAN connection, this is applicable to both IPv4 and IPv6 addressing.

For the static routing case, a customer may configure the following topology, but this can be also covered with cascaded-lan-prefixes.

	  Host1 ------\
	  Host2 ---- Switch ---------- PE
LAN  ---- Router -----/


Here is the simplest one's example.
    <site-network-accesses>
        <site-network-access>
            <site-network-access-id>Spoke_Site1</site-network-access-id>
            <ip-connection>
                <ipv4>
                    <address-allocation-type>static-address</address-allocation-type>
                    <addresses>
                      <provider-address>203.0.113.254</provider-address>
                      <mask>24</mask>
                    </addresses>
                </ipv4>
            </ip-connection>
            <vpn-attachment>
                <vpn-id>12456487</vpn-id>
                <site-role>spoke-role</site-role>
            </vpn-attachment>
            <routing-protocols>
                <routing-protocol>
                    <type>direct</type>
                </routing-protocol>
            </routing-protocols>
        </site-network-access>
    </site-network-accesses>


Am I missing something more?

Thanks,
Kenichi

-----Original Message-----
From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of stephane.litkowski@orange.com
Sent: Thursday, June 16, 2016 10:07 PM
To: Ogaki, Kenichi; 'David Ball'; l3sm@ietf.org
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

Hi Kenichi,

Do you think we need a special leaf to identify that a particular site-network-access is multipoint rather than p2p ?
Or don't we care ?

As David pointed, for some features, there may be an issue : security features, oam ...
For dynamic IP addressing we may need a additional leaf to precise the number of addresses to be allocated (currently as we assume p2p, it's only 1).
Any idea on how to address it globally ?

Best Regards,


-----Original Message-----
From: Ogaki, Kenichi [mailto:ke-oogaki@kddi.com]
Sent: Thursday, June 16, 2016 05:49
To: 'David Ball'; LITKOWSKI Stephane OBS/OINIS; l3sm@ietf.org
Subject: RE: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

Hi David, Stephane,

The use case definitely exists. Then, it's reasonable to keep the example.

We are providing this as an option of our commercial VPN service.

Thanks,
Kenichi

-----Original Message-----
From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of David Ball
Sent: Wednesday, June 15, 2016 9:05 PM
To: stephane.litkowski@orange.com; l3sm@ietf.org
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

Regarding the use case, I'll leave it to SPs such as yourself to answer. :)  But if there is no use case, then we should change those examples in the doc.

    David


On 15/06/2016 10:21, stephane.litkowski@orange.com wrote:


	Hi David,

	 

	I see your point, as a mentioned, it is different from what I was thinking about.

	So the question is : do we need to support this kind of architecture (is there a use case ?).

	Regarding the two CEs/two PEs cases connected on the same LAN, I think it's interesting to keep it, it usually used to connect some service platforms. We may need to restrict options in this scenario (static address .) , but I'm afraid that it may be hard to be exhaustive . any idea ?

	 

	Thanks,

	 

	 

	From: David Ball [mailto:daviball@cisco.com] 
	Sent: Friday, June 10, 2016 13:29
	To: LITKOWSKI Stephane OBS/OINIS; l3sm@ietf.org
	Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

	 

	Hi Stephane,
	
	More inline:

	On 09/06/2016 20:08, <mailto:stephane.litkowski@orange.com> stephane.litkowski@orange.com wrote:

		
		
		

		*	Sn 5.10.2: You said before that the model can only manage P2P connections; but this figure (and the next one) show the PE connected to a LAN, not to a CE.  I am not sure how to interpret this?  Isn't this a case where the connection is multipoint, not P2P?

		[SLI] That's still point to point. In 5.10.3, customer must order two site network accesses (point to point). Each site network network access may be connected to a switch at customer side (same one or not).

		
		[DB] If there is an L2 switch, then at L3 it is a multipoint connection - the switch is part of the bearer.
		[SLI] From a SP  point of view no, in term of service, the customer will have to order two site-network-accesses. How they are connected to the customer network is not under the SP responsibility. If the customer connects the two site-net-access on the same Lan through a switch, it becomes multipoint, but SP is not essentially aware of it.

	
	[DB] I think we may be talking about different cases.  I don't mean it may be multipoint because there are multiple site-network-accesses, I'm talking about the case where there are multiple devices at the customer side (could be one or multiple site-network-accesses) - rather than a single CE terminating the L3 connection.  This seems to be what the figure in Sn 5.10.2 is showing.
	
	  Host1 ------\
	  Host2 ---- Switch ---------- PE
	  Host3 ------/
	
	I don't think it's entirely true in this case that the SP does not need to be aware of it - for instance, if the connection address is dynamic, the SP may need to allocate multiple addresses instead of just 1.  It also has some impact on other aspects of the model; for instance, the routing protocol probably needs to be direct or static (not an absolute requirement but probably true in practice), and BFD and IPSec probably need to be disabled (since these are inherently P2P).
	
	
	    David
	
	
	
	

	-- 
	David Ball
	<daviball@cisco.com> <mailto:daviball@cisco.com> 
	_________________________________________________________________________________________________________________________
	
	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.


--
David Ball
<daviball@cisco.com> <mailto:daviball@cisco.com> 


_________________________________________________________________________________________________________________________

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
L3sm@ietf.org
https://www.ietf.org/mailman/listinfo/l3sm


_________________________________________________________________________________________________________________________

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
L3sm@ietf.org
https://www.ietf.org/mailman/listinfo/l3sm


From nobody Fri Jun 17 05:51:19 2016
Return-Path: <stephane.litkowski@orange.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 A9CFB12D5FF for <l3sm@ietfa.amsl.com>; Fri, 17 Jun 2016 05:51:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.345
X-Spam-Level: 
X-Spam-Status: No, score=-3.345 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 et7AB3xZ7znk for <l3sm@ietfa.amsl.com>; Fri, 17 Jun 2016 05:51:16 -0700 (PDT)
Received: from relais-inet.orange.com (relais-nor36.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8F0612D08E for <l3sm@ietf.org>; Fri, 17 Jun 2016 05:51:15 -0700 (PDT)
Received: from opfednr07.francetelecom.fr (unknown [xx.xx.xx.71]) by opfednr22.francetelecom.fr (ESMTP service) with ESMTP id BDCA020363; Fri, 17 Jun 2016 14:51:13 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.57]) by opfednr07.francetelecom.fr (ESMTP service) with ESMTP id 8EBB51C005D; Fri, 17 Jun 2016 14:51:13 +0200 (CEST)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM23.corporate.adroot.infra.ftgroup ([fe80::787e:db0c:23c4:71b3%19]) with mapi id 14.03.0294.000; Fri, 17 Jun 2016 14:51:13 +0200
From: <stephane.litkowski@orange.com>
To: "Ogaki, Kenichi" <ke-oogaki@kddi.com>, 'David Ball' <daviball@cisco.com>,  "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
Thread-Index: AQHRv/4i8iSSM4mtWE6AeESR5nwEZZ/cfFGwgAGg6gCAASznEIABf5oAgAC53hCAAPGPgIAH11+AgAAOMoCAAQe0gIAAvNzggADE24CAAF4q0IAAFDKAgABV6+A=
Date: Fri, 17 Jun 2016 12:51:12 +0000
Message-ID: <6106_1466167873_5763F241_6106_533_1_9E32478DFA9976438E7A22F69B08FF921BC66D91@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <20160606141710.20806.10098.idtracker@ietfa.amsl.com> <27218_1465222795_5755868B_27218_684_1_9E32478DFA9976438E7A22F69B08FF921BC41DA1@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <ec72f8b8-8626-ba2c-bc50-7ce4a0cdc6df@cisco.com> <32265_1465379094_5757E916_32265_10098_3_9E32478DFA9976438E7A22F69B08FF921BC454AB@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <1595f5bb-1838-8164-6e7f-1d383d8bfb87@cisco.com> <7576_1465499325_5759BEBD_7576_3122_1_9E32478DFA9976438E7A22F69B08FF921BC4C5F2@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <bf0bd488-ff9e-ae4e-b37c-6123ae63a8ee@cisco.com> <3459_1465982476_57611E0C_3459_229_11_9E32478DFA9976438E7A22F69B08FF921BC5ECBA@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <26334e73-054f-0797-31fd-5ad475f68385@cisco.com> <011801d1c781$f9624290$ec26c7b0$@kddi.com> <26167_1466082427_5762A47B_26167_5405_1_9E32478DFA9976438E7A22F69B08FF921BC6338E@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <00f901d1c842$d4ebb970$7ec32c50$@kddi.com> <18935_1466144921_576 39899_18935_238_11_9E3 2478DFA9976438E7A22F69B08FF921BC65DC0@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <015801d1c87c$02b855f0$082901d0$@kddi.com>
In-Reply-To: <015801d1c87c$02b855f0$082901d0$@kddi.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.1]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/kVzxKOswHpfneP5krQ6cALdmpIg>
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
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: Fri, 17 Jun 2016 12:51:18 -0000

More inline

Best Regards,

-----Original Message-----
From: Ogaki, Kenichi [mailto:ke-oogaki@kddi.com]
Sent: Friday, June 17, 2016 04:49
To: LITKOWSKI Stephane OBS/OINIS; 'David Ball'; l3sm@ietf.org
Subject: RE: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

Hi Stephane, David,

IMO, the current model is enough generic to cover the use case.

> I don't think it's entirely true in this case that the SP does not=20
> need to be aware of it - for instance, if the connection address is=20
> dynamic, the SP may need to allocate multiple addresses instead of=20
> just 1.  It also has some impact on other aspects of the model; for=20
> instance, the routing protocol probably needs to be direct or static=20
> (not an absolute requirement but probably true in practice), and BFD=20
> and IPSec probably need to be disabled (since these are inherently P2P).

The encryption or oam isn't mandatory even in p2p case, then we can apply t=
he current model without any restriction. Just not specify them.
[SLI] Yes it's optional, but the issue is that it may work on p2p but not o=
n mp connections. So if customer requests it and if SP is not aware that it=
 will be a mp connection, oam or encryption may not work.

[KO] We can restrict to avoid such impossible combinations by using when st=
atement, but this can be also achieved outside of the model. Operator can j=
ust reject the impossible request and return the error.=20
I think we don't need such a strict modeling without a strong requirement f=
or now.=20

[SLI2] How can we do such restriction if we do not have the information abo=
ut the access-type (p2p or mp) ? Operator can reject the config as he does =
not know how the access will be used.
If we want the operator to check this out of the model, the customer needs =
to provide the info that it is a multipoint access and a new leaf per site-=
network-access may help here.


The current address-allocation-type is provider-dhcp, static-address (and s=
laac). The provider-dhcp works for assigning multiple addresses. Am I missi=
ng something?
[SLI] Yes, but the SP may need to know how many addresses are needed (to im=
plement correctly the DHCP pool)

[KO] It may be useful as an option. I'm asking my colleague if we need.

[SLI] Ok,we can add a leaf for ipv4 and ipv6 ip-connection like :

Leaf number-of-dynamic-addresses {
	When "../address-allocation-type =3D pe-dhcp";
	Type uint8;
}


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.


From nobody Sat Jun 18 00:46:55 2016
Return-Path: <ke-oogaki@kddi.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 37E1812B011 for <l3sm@ietfa.amsl.com>; Sat, 18 Jun 2016 00:46:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.647
X-Spam-Level: 
X-Spam-Status: No, score=-5.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, 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 E--PfzKsd43f for <l3sm@ietfa.amsl.com>; Sat, 18 Jun 2016 00:46:52 -0700 (PDT)
Received: from post-send.kddi.com (athena3.kddi.com [27.90.165.196]) by ietfa.amsl.com (Postfix) with ESMTP id F380112B026 for <l3sm@ietf.org>; Sat, 18 Jun 2016 00:46:51 -0700 (PDT)
Received: from LTMC2122.kddi.com (LTMC2122.kddi.com [10.206.0.63]) by post-send.kddi.com (KDDI Mail) with ESMTP id 2FAAFE0060; Sat, 18 Jun 2016 16:46:50 +0900 (JST)
Received: from LTMC2144.kddi.com ([10.206.0.236] [10.206.0.236]) by LTMC2122.kddi.com with ESMTP; Sat, 18 Jun 2016 16:46:50 +0900
Received: from LTMC2144.kddi.com (localhost [127.0.0.1]) by localhost.kddi.com (Postfix) with ESMTP id F2F1C4C0058; Sat, 18 Jun 2016 16:46:49 +0900 (JST)
Received: from LTMC2153.kddi.com (post-incheck [10.206.0.239]) by LTMC2144.kddi.com (Postfix) with ESMTP id E7C8F4C0051; Sat, 18 Jun 2016 16:46:49 +0900 (JST)
Received: from LTMC2153.kddi.com (localhost.localdomain [127.0.0.1]) by LTMC2153.kddi.com  with ESMTP id u5I7knn1002149; Sat, 18 Jun 2016 16:46:49 +0900
Received: from LTMC2153.kddi.com.mid_67052131 (localhost.localdomain [127.0.0.1]) by LTMC2153.kddi.com  with ESMTP id u5I7alam032237; Sat, 18 Jun 2016 16:36:47 +0900
X-SA-MID: 67052131
Received: from KDDI1508PC0003 ([10.200.122.178] [10.200.122.178]) by post-smtp2.kddi.com with ESMTPA; Sat, 18 Jun 2016 16:36:47 +0900
From: "Ogaki, Kenichi" <ke-oogaki@kddi.com>
To: <stephane.litkowski@orange.com>, "'David Ball'" <daviball@cisco.com>, <l3sm@ietf.org>
References: <20160606141710.20806.10098.idtracker@ietfa.amsl.com> <27218_1465222795_5755868B_27218_684_1_9E32478DFA9976438E7A22F69B08FF921BC41DA1@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <ec72f8b8-8626-ba2c-bc50-7ce4a0cdc6df@cisco.com> <32265_1465379094_5757E916_32265_10098_3_9E32478DFA9976438E7A22F69B08FF921BC454AB@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <1595f5bb-1838-8164-6e7f-1d383d8bfb87@cisco.com> <7576_1465499325_5759BEBD_7576_3122_1_9E32478DFA9976438E7A22F69B08FF921BC4C5F2@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <bf0bd488-ff9e-ae4e-b37c-6123ae63a8ee@cisco.com> <3459_1465982476_57611E0C_3459_229_11_9E32478DFA9976438E7A22F69B08FF921BC5ECBA@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <26334e73-054f-0797-31fd-5ad475f68385@cisco.com> <011801d1c781$f9624290$ec26c7b0$@kddi.com> <26167_1466082427_5762A47B_26167_5405_1_9E32478DFA9976438E7A22F69B08FF921BC6338E@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <00f901d1c842$d4ebb970$7ec32c50$@kddi.com> <18935_1466144921_576 39899_18935_238_11_9E 3 2478DFA9976438E7A22F69B08FF921BC65DC0@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <015801d1c87c$02b855f0$082901d0$@kddi.com> <6106_1466167873_5763F241_6106_533_1_9E32478DFA9976438E7A22F69B08FF921BC66D91@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
In-Reply-To: <6106_1466167873_5763F241_6106_533_1_9E32478DFA9976438E7A22F69B08FF921BC66D91@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
Date: Sat, 18 Jun 2016 16:36:46 +0900
Message-ID: <012001d1c934$2b240bc0$816c2340$@kddi.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJW+Huf9ydieY5WOdIeI0Z4sme4rQH+WJzEAfIETV4BePpT0gH9kPSrA5cjTFkBrBI9qQIhvackAvJMZnwDP7hh6QITxPMFAYruR6gB9BnsPwFC5KyXAgumbC6d9XwFQA==
Content-Language: ja
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/UXmjpUlr091tVvvmAMc6reKpkk8>
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
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: Sat, 18 Jun 2016 07:46:54 -0000

Hi Stephane,

Isn't enough wheter the customer-address is provided or not?

Whether p2p or mp access can't decide if ipsec/oam can be enabled or not.
If a customer provides his/her customer-address with ipsec or oam, their operator must appropriately configure ipsec or p2p oam *even in mp access*. On the other hand, he/she only provides the provider-address, the operator can't do so.

Thanks,
Kenichi


-----Original Message-----
From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of stephane.litkowski@orange.com
Sent: Friday, June 17, 2016 9:51 PM
To: Ogaki, Kenichi; 'David Ball'; l3sm@ietf.org
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

More inline

Best Regards,

-----Original Message-----
From: Ogaki, Kenichi [mailto:ke-oogaki@kddi.com]
Sent: Friday, June 17, 2016 04:49
To: LITKOWSKI Stephane OBS/OINIS; 'David Ball'; l3sm@ietf.org
Subject: RE: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

Hi Stephane, David,

IMO, the current model is enough generic to cover the use case.

> I don't think it's entirely true in this case that the SP does not 
> need to be aware of it - for instance, if the connection address is 
> dynamic, the SP may need to allocate multiple addresses instead of 
> just 1.  It also has some impact on other aspects of the model; for 
> instance, the routing protocol probably needs to be direct or static 
> (not an absolute requirement but probably true in practice), and BFD 
> and IPSec probably need to be disabled (since these are inherently P2P).

The encryption or oam isn't mandatory even in p2p case, then we can apply the current model without any restriction. Just not specify them.
[SLI] Yes it's optional, but the issue is that it may work on p2p but not on mp connections. So if customer requests it and if SP is not aware that it will be a mp connection, oam or encryption may not work.

[KO] We can restrict to avoid such impossible combinations by using when statement, but this can be also achieved outside of the model. Operator can just reject the impossible request and return the error. 
I think we don't need such a strict modeling without a strong requirement for now. 

[SLI2] How can we do such restriction if we do not have the information about the access-type (p2p or mp) ? Operator can reject the config as he does not know how the access will be used.
If we want the operator to check this out of the model, the customer needs to provide the info that it is a multipoint access and a new leaf per site-network-access may help here.


The current address-allocation-type is provider-dhcp, static-address (and slaac). The provider-dhcp works for assigning multiple addresses. Am I missing something?
[SLI] Yes, but the SP may need to know how many addresses are needed (to implement correctly the DHCP pool)

[KO] It may be useful as an option. I'm asking my colleague if we need.

[SLI] Ok,we can add a leaf for ipv4 and ipv6 ip-connection like :

Leaf number-of-dynamic-addresses {
	When "../address-allocation-type = pe-dhcp";
	Type uint8;
}


_________________________________________________________________________________________________________________________

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
L3sm@ietf.org
https://www.ietf.org/mailman/listinfo/l3sm


From nobody Wed Jun 22 02:26:32 2016
Return-Path: <stephane.litkowski@orange.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 2A7DE12B058 for <l3sm@ietfa.amsl.com>; Wed, 22 Jun 2016 02:26:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.345
X-Spam-Level: 
X-Spam-Status: No, score=-3.345 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 AlbyvgH0pDje for <l3sm@ietfa.amsl.com>; Wed, 22 Jun 2016 02:26:28 -0700 (PDT)
Received: from relais-inet.orange.com (relais-nor34.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCBF1127058 for <l3sm@ietf.org>; Wed, 22 Jun 2016 02:26:27 -0700 (PDT)
Received: from opfednr01.francetelecom.fr (unknown [xx.xx.xx.65]) by opfednr21.francetelecom.fr (ESMTP service) with ESMTP id 1AC93C010C; Wed, 22 Jun 2016 11:26:26 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.27]) by opfednr01.francetelecom.fr (ESMTP service) with ESMTP id D82F51A0060; Wed, 22 Jun 2016 11:26:25 +0200 (CEST)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM7C.corporate.adroot.infra.ftgroup ([fe80::8007:17b:c3b4:d68b%19]) with mapi id 14.03.0294.000; Wed, 22 Jun 2016 11:26:25 +0200
From: <stephane.litkowski@orange.com>
To: "Ogaki, Kenichi" <ke-oogaki@kddi.com>, 'David Ball' <daviball@cisco.com>,  "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
Thread-Index: AQHRv/4i8iSSM4mtWE6AeESR5nwEZZ/cfFGwgAGg6gCAASznEIABf5oAgAC53hCAAPGPgIAH11+AgAAOMoCAAQe0gIAAvNzggADE24CAAF4q0IAAFDKAgABV6+CAARplAIAGiQIQ
Date: Wed, 22 Jun 2016 09:26:24 +0000
Message-ID: <15514_1466587586_576A59C1_15514_457_7_9E32478DFA9976438E7A22F69B08FF921BC7788E@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <20160606141710.20806.10098.idtracker@ietfa.amsl.com> <27218_1465222795_5755868B_27218_684_1_9E32478DFA9976438E7A22F69B08FF921BC41DA1@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <ec72f8b8-8626-ba2c-bc50-7ce4a0cdc6df@cisco.com> <32265_1465379094_5757E916_32265_10098_3_9E32478DFA9976438E7A22F69B08FF921BC454AB@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <1595f5bb-1838-8164-6e7f-1d383d8bfb87@cisco.com> <7576_1465499325_5759BEBD_7576_3122_1_9E32478DFA9976438E7A22F69B08FF921BC4C5F2@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <bf0bd488-ff9e-ae4e-b37c-6123ae63a8ee@cisco.com> <3459_1465982476_57611E0C_3459_229_11_9E32478DFA9976438E7A22F69B08FF921BC5ECBA@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <26334e73-054f-0797-31fd-5ad475f68385@cisco.com> <011801d1c781$f9624290$ec26c7b0$@kddi.com> <26167_1466082427_5762A47B_26167_5405_1_9E32478DFA9976438E7A22F69B08FF921BC6338E@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <00f901d1c842$d4ebb970$7ec32c50$@kddi.com> <18935_1466144921_576 39899_18935_238_11_9E	3 2478DFA9976438E7A22F69B08FF921BC65DC0@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <015801d1c87c$02b855f0$082901d0$@kddi.com> <6106_1466167873_5763F241_6106_533_1_9E32478DFA9976438E7A22F69B08FF921BC66D91@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <012001d1c934$2b240bc0$816c2340$@kddi.com>
In-Reply-To: <012001d1c934$2b240bc0$816c2340$@kddi.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.3]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/MFNnUIdRaKz6yg7Z2MYS2zx7ZzM>
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt
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: Wed, 22 Jun 2016 09:26:30 -0000

Hi,

Using customer-address presence to deduce works but it's not very clear. Di=
d the customer forgot it or is it done on purpose ? Would be better to be m=
ore explicit in what the customer wants.

Brgds,


-----Original Message-----
From: Ogaki, Kenichi [mailto:ke-oogaki@kddi.com]=20
Sent: Saturday, June 18, 2016 09:37
To: LITKOWSKI Stephane OBS/OINIS; 'David Ball'; l3sm@ietf.org
Subject: RE: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

Hi Stephane,

Isn't enough wheter the customer-address is provided or not?

Whether p2p or mp access can't decide if ipsec/oam can be enabled or not.
If a customer provides his/her customer-address with ipsec or oam, their op=
erator must appropriately configure ipsec or p2p oam *even in mp access*. O=
n the other hand, he/she only provides the provider-address, the operator c=
an't do so.

Thanks,
Kenichi


-----Original Message-----
From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of stephane.litkowski@o=
range.com
Sent: Friday, June 17, 2016 9:51 PM
To: Ogaki, Kenichi; 'David Ball'; l3sm@ietf.org
Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

More inline

Best Regards,

-----Original Message-----
From: Ogaki, Kenichi [mailto:ke-oogaki@kddi.com]
Sent: Friday, June 17, 2016 04:49
To: LITKOWSKI Stephane OBS/OINIS; 'David Ball'; l3sm@ietf.org
Subject: RE: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-07.txt

Hi Stephane, David,

IMO, the current model is enough generic to cover the use case.

> I don't think it's entirely true in this case that the SP does not=20
> need to be aware of it - for instance, if the connection address is=20
> dynamic, the SP may need to allocate multiple addresses instead of=20
> just 1.  It also has some impact on other aspects of the model; for=20
> instance, the routing protocol probably needs to be direct or static=20
> (not an absolute requirement but probably true in practice), and BFD=20
> and IPSec probably need to be disabled (since these are inherently P2P).

The encryption or oam isn't mandatory even in p2p case, then we can apply t=
he current model without any restriction. Just not specify them.
[SLI] Yes it's optional, but the issue is that it may work on p2p but not o=
n mp connections. So if customer requests it and if SP is not aware that it=
 will be a mp connection, oam or encryption may not work.

[KO] We can restrict to avoid such impossible combinations by using when st=
atement, but this can be also achieved outside of the model. Operator can j=
ust reject the impossible request and return the error.=20
I think we don't need such a strict modeling without a strong requirement f=
or now.=20

[SLI2] How can we do such restriction if we do not have the information abo=
ut the access-type (p2p or mp) ? Operator can reject the config as he does =
not know how the access will be used.
If we want the operator to check this out of the model, the customer needs =
to provide the info that it is a multipoint access and a new leaf per site-=
network-access may help here.


The current address-allocation-type is provider-dhcp, static-address (and s=
laac). The provider-dhcp works for assigning multiple addresses. Am I missi=
ng something?
[SLI] Yes, but the SP may need to know how many addresses are needed (to im=
plement correctly the DHCP pool)

[KO] It may be useful as an option. I'm asking my colleague if we need.

[SLI] Ok,we can add a leaf for ipv4 and ipv6 ip-connection like :

Leaf number-of-dynamic-addresses {
	When "../address-allocation-type =3D pe-dhcp";
	Type uint8;
}


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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. Le=
s messages electroniques etant susceptibles d'alteration, Orange decline to=
ute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation 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 dele=
te 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
L3sm@ietf.org
https://www.ietf.org/mailman/listinfo/l3sm


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.


From nobody Mon Jun 27 05:04:03 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: l3sm@ietf.org
Delivered-To: l3sm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BC95012D0F5; Mon, 27 Jun 2016 05:04:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160627120401.5297.7466.idtracker@ietfa.amsl.com>
Date: Mon, 27 Jun 2016 05:04:01 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/O67AneBnaSo6GnUvm6GG2Ijmg-0>
Cc: l3sm@ietf.org
Subject: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-10.txt
X-BeenThere: l3sm@ietf.org
X-Mailman-Version: 2.1.17
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, 27 Jun 2016 12:04:02 -0000

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

        Title           : YANG Data Model for L3VPN service delivery
        Authors         : Stephane Litkowski
                          Rob Shakir
                          Luis Tomotaki
                          Kenichi Ogaki
                          Kevin D'Souza
	Filename        : draft-ietf-l3sm-l3vpn-service-model-10.txt
	Pages           : 150
	Date            : 2016-06-27

Abstract:
   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:
https://datatracker.ietf.org/doc/draft-ietf-l3sm-l3vpn-service-model/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-l3sm-l3vpn-service-model-10

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-l3sm-l3vpn-service-model-10


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

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

