IETF Logo Mail Archive

Re: [L3sm] Comments on draft-ietf-l3sm-l3vpn-service-model

<stephane.litkowski@orange.com> Mon, 27 July 2015 08:37 UTC

Return-Path: <stephane.litkowski@orange.com>
X-Original-To: l3sm@ietfa.amsl.com
Delivered-To: l3sm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59A551ACE32 for <l3sm@ietfa.amsl.com>; Mon, 27 Jul 2015 01:37:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 5QXPtwnYnw-M for <l3sm@ietfa.amsl.com>; Mon, 27 Jul 2015 01:37:51 -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 748EA1ACDF4 for <l3sm@ietf.org>; Mon, 27 Jul 2015 01:37:51 -0700 (PDT)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id DE1423B4557; Mon, 27 Jul 2015 10:37:49 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.60]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id 7FB3627C0EA; Mon, 27 Jul 2015 10:37:49 +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.0235.001; Mon, 27 Jul 2015 10:37:48 +0200
From: stephane.litkowski@orange.com
To: Eric C Rosen <erosen@juniper.net>, "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: [L3sm] Comments on draft-ietf-l3sm-l3vpn-service-model
Thread-Index: AQHQw8X3K3YLZClNO0qpeZYxRBC/cp3nugYAgADZWqCAAL2YgIAFtW5A
Date: Mon, 27 Jul 2015 08:37:48 +0000
Message-ID: <12269_1437986269_55B5EDDD_12269_740_1_9E32478DFA9976438E7A22F69B08FF92166A4D53@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <4B3B6546-2150-4EFB-B580-587A9EAD1E82@gmail.com> <55AFE9C4.5070704@juniper.net> <29351_1437643806_55B0B41E_29351_10618_1_9E32478DFA9976438E7A22F69B08FF92166A402F@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <55B13F23.4030001@juniper.net>
In-Reply-To: <55B13F23.4030001@juniper.net>
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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.7.16.85415
Archived-At: <http://mailarchive.ietf.org/arch/msg/l3sm/tYmwxy85r5puigasrmWD_YFuTBs>
Subject: Re: [L3sm] Comments on draft-ietf-l3sm-l3vpn-service-model
X-BeenThere: l3sm@ietf.org
X-Mailman-Version: 2.1.15
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, 27 Jul 2015 08:37:53 -0000

Hi Eric,

More inline

-----Original Message-----
From: Eric C Rosen [mailto:erosen@juniper.net] 
Sent: Thursday, July 23, 2015 21:23
To: LITKOWSKI Stephane SCE/IBNF; l3sm@ietf.org
Cc: erosen@juniper.net
Subject: Re: [L3sm] Comments on draft-ietf-l3sm-l3vpn-service-model

On 7/23/2015 5:30 AM, stephane.litkowski@orange.com wrote:
> [ECR] Some PE products allow the SP to offer a Rendezvous Point 
> service to their MVPN customers.

> [SLI] Type of tree, rendez vous point type and IP address is available 
> in the vpn-svc definition

If the SM specifies a particular RP address (say, an anycast-RP address), how can you tell whether the RP service is being offered by the PEs, or whether it is being offered by a system that is owned by the customer?  Is that what the "anycast-RP-location" is for?
[SLI] in my mind, if the referenced IP address is an IP address located on a PE, then the RP is the PE. 
For "anycast-RP-location", the idea is to give a list of internal references to encode the location of the different RPs. It can be  PEs, or CEs ...

If static-rp is being used, doesn't the SM need to contain the complete set of customer group-to-rp mappings?  (Presumably the customer provides this when the service is provisioned.)
[SLI] Group to RP mapping is missing today, thanks for pointing it, will be added in the next verison.


_________________________________________________________________________________________________________________________

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.

v2.23.0 | Report a Bug | By Email