Subject: Re: [L3sm] [l3sm] #19 (draft-ltsd-l3sm-l3vpn-service-model): "site-entrance" and "pop-entrance" Diversity Constraint Augmentation Suggestion

From: "Ogaki, Kenichi" <[email-masked]>
Date: Fri, 2 Sep 2016 13:46:47 +0900

Hi,

Can this be covered by path diversity described in 5.12.2?
I think customers just want to make sure multihomed paths are disjoint, but don't want to care how it is achieved.

All the best,
Kenichi

-----Original Message-----
From: L3sm [mailto:[email-masked]] On Behalf Of l3sm issue tracker
Sent: Thursday, September 01, 2016 6:31 AM
To: [email-masked]; [email-masked]
Cc: [email-masked]
Subject: [L3sm] [l3sm] #19 (draft-ltsd-l3sm-l3vpn-service-model): "site-entrance" and "pop-entrance" Diversity Constraint Augmentation Suggestion

#19: "site-entrance" and "pop-entrance"  Diversity Constraint Augmentation Suggestion

 Offering building entrance diversity is a good way to avoid outside plant  single point of failures associated to common cable conduits and common  access facility routes. Site and POP entrance diversity options are  therefore made available to sensitive IP.VPN customers.

 Recommending to add "site-entrance-diverse" and "pop-entrance-diverse"
 diversity constraints.

-- 
-------------------------------------+----------------------------------
-------------------------------------+---
 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/19>
l3sm <https://tools.ietf.org/l3sm/>

_______________________________________________
L3sm mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/l3sm