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

From: <[email-masked]>
Date: Thu, 1 Sep 2016 14:10:54 +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:[email-masked]] 
Sent: Wednesday, August 31, 2016 23:13
To: [email-masked]; [email-masked]
Cc: [email-masked]
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:  [email-masked]         |      Owner:  draft-ltsd-l3sm-l3vpn-
     Type:  enhancement              |  [email-masked]
 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.