Re: [L3sm] [l3sm] #18 (draft-ltsd-l3sm-l3vpn-service-model): "pop-diverse" Diversity Constraint Augmentation Suggestion

<stephane.litkowski@orange.com> Thu, 01 September 2016 14:16 UTC

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 303CB12D1D3 for <l3sm@ietfa.amsl.com>; Thu, 1 Sep 2016 07:16:08 -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 BSJzV4w8GLSV for <l3sm@ietfa.amsl.com>; Thu, 1 Sep 2016 07:16:03 -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 340F912D58D for <l3sm@ietf.org>; Thu, 1 Sep 2016 07:10:57 -0700 (PDT)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id 66F29264070; Thu, 1 Sep 2016 16:10:55 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.69]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id 3229527C064; Thu, 1 Sep 2016 16:10:55 +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.0301.000; Thu, 1 Sep 2016 16:10:54 +0200
From: stephane.litkowski@orange.com
To: l3sm issue tracker <trac+l3sm@tools.ietf.org>, "draft-ltsd-l3sm-l3vpn-service-model@tools.ietf.org" <draft-ltsd-l3sm-l3vpn-service-model@tools.ietf.org>, "jplandry@bell.ca" <jplandry@bell.ca>
Thread-Topic: [l3sm] #18 (draft-ltsd-l3sm-l3vpn-service-model): "pop-diverse" Diversity Constraint Augmentation Suggestion
Thread-Index: AQHSA8xu2bjPRcmPVUGfpoBdJwse56BkrJvQ
Date: Thu, 01 Sep 2016 14:10:54 +0000
Message-ID: <10500_1472739055_57C836EF_10500_133_1_9E32478DFA9976438E7A22F69B08FF921BD64378@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <056.67cd8a003c5128595f7f1c51a3a214ff@tools.ietf.org>
In-Reply-To: <056.67cd8a003c5128595f7f1c51a3a214ff@tools.ietf.org>
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: 2016.6.17.114517
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/qlLiG5ac1fF5Yu6p-4rDzo6cizU>
Cc: "l3sm@ietf.org" <l3sm@ietf.org>
Subject: Re: [L3sm] [l3sm] #18 (draft-ltsd-l3sm-l3vpn-service-model): "pop-diverse" Diversity Constraint Augmentation Suggestion
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, 01 Sep 2016 14:16:08 -0000

I agree with your statement, but I think this is a too specific case to add it in the model.
This is a layer 3 VPN model, so we really focus on the IP layer side. Bunches of networks are using backhaul from other service providers that they cannot really control, so they can control on what PE the access is connected (IP layer), but they do not really know what happens underneath : SP will try to translate the diversity request to the backhaul responsible SP but without 100% insurance of what has been implemented in reality.

This kind of constraint can be added by augmentation if a particular SP want to offer it.


-----Original Message-----
From: l3sm issue tracker [mailto:trac+l3sm@tools.ietf.org] 
Sent: Wednesday, August 31, 2016 23:13
To: draft-ltsd-l3sm-l3vpn-service-model@tools.ietf.org; jplandry@bell.ca
Cc: l3sm@ietf.org
Subject: [l3sm] #18 (draft-ltsd-l3sm-l3vpn-service-model): "pop-diverse" Diversity Constraint Augmentation Suggestion

#18: "pop-diverse" Diversity Constraint  Augmentation Suggestion

 Point of Presence (POP) normally corresponds to the location where the PE  router is installed. For large service provider networks, the access  network typically first terminates in a Local Serving Office and from  there additional backhaul is performed to reach the POP where the PE is  located. In some cases the local serving office and the POP are at the  same building/location but this is not always the case.

 For this reason, certain service providers also sell Local Serving Office  diversity options on top of POP diversity to their IP.VPN customers.
 (because a common Local Serving Office for 2 otherwise diverse network  accesses can be perceived as a single point of failure for high profile  IP.VPN customers)

 As a result, this recommendation is to add “local-serving-office-diverse”
 diversity option.

-- 
-------------------------------------+----------------------------------
-------------------------------------+---
 Reporter:  jplandry@bell.ca         |      Owner:  draft-ltsd-l3sm-l3vpn-
     Type:  enhancement              |  service-model@tools.ietf.org
 Priority:  minor                    |     Status:  new
Component:  draft-ltsd-l3sm-l3vpn-   |  Milestone:
  service-model                      |    Version:
 Severity:  -                        |   Keywords:
-------------------------------------+----------------------------------
-------------------------------------+---

Ticket URL: <https://trac.tools.ietf.org/wg/l3sm/trac/ticket/18>
l3sm <https://tools.ietf.org/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.