IETF Logo Mail Archive

Re: [L3sm] [l3sm] #15 (draft-ltsd-l3sm-l3vpn-service-model): Multi CE vs Single CE Multi-homing (network access diversity)

"Ogaki, Kenichi" <ke-oogaki@kddi.com> Fri, 02 September 2016 04:44 UTC

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 23E0112D51D for <l3sm@ietfa.amsl.com>; Thu, 1 Sep 2016 21:44:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.769
X-Spam-Level:
X-Spam-Status: No, score=-4.769 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=-0.548, 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 tKVuZ3oBBbF2 for <l3sm@ietfa.amsl.com>; Thu, 1 Sep 2016 21:44:39 -0700 (PDT)
Received: from post-send.kddi.com (athena3.kddi.com [27.90.165.196]) by ietfa.amsl.com (Postfix) with ESMTP id D8A5512D51A for <l3sm@ietf.org>; Thu, 1 Sep 2016 21:44:38 -0700 (PDT)
Received: from LTMC2123.kddi.com (LTMC2123.kddi.com [10.206.0.65]) by post-send.kddi.com (KDDI Mail) with ESMTP id 97190E0031; Fri, 2 Sep 2016 13:44:37 +0900 (JST)
Received: from LTMC2145.kddi.com ([10.206.0.236] [10.206.0.236]) by LTMC2123.kddi.com with ESMTP; Fri, 2 Sep 2016 13:44:37 +0900
Received: from LTMC2145.kddi.com (localhost [127.0.0.1]) by localhost.kddi.com (Postfix) with ESMTP id 5EC6C3A006B; Fri, 2 Sep 2016 13:44:37 +0900 (JST)
Received: from LTMC2154.kddi.com (post-incheck [10.206.0.239]) by LTMC2145.kddi.com (Postfix) with ESMTP id 53BD13A0065; Fri, 2 Sep 2016 13:44:37 +0900 (JST)
Received: from LTMC2154.kddi.com (localhost.localdomain [127.0.0.1]) by LTMC2154.kddi.com with ESMTP id u824ib27124306; Fri, 2 Sep 2016 13:44:37 +0900
Received: from LTMC2154.kddi.com.mid_4410481 (localhost.localdomain [127.0.0.1]) by LTMC2154.kddi.com with ESMTP id u824YXJD113284; Fri, 2 Sep 2016 13:34:33 +0900
X-SA-MID: 4410481
Received: from KDDI1508PC0003 ([10.200.122.178] [10.200.122.178]) by post-smtp2.kddi.com with ESMTPA; Fri, 2 Sep 2016 13:34:33 +0900
From: "Ogaki, Kenichi" <ke-oogaki@kddi.com>
To: jplandry@bell.ca
References: <056.58954a1533bba8322f5b6b46420a5b55@tools.ietf.org>
In-Reply-To: <056.58954a1533bba8322f5b6b46420a5b55@tools.ietf.org>
Date: Fri, 02 Sep 2016 13:34:33 +0900
Message-ID: <01d601d204d3$4d80e870$e882b950$@kddi.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJyQaQuULUNYtH/398BzQWLzPemtp8lHpkw
Content-Language: ja
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/3XS-BfMYz51TOAix7uz7HmtH2G8>
Cc: l3sm@ietf.org
Subject: Re: [L3sm] [l3sm] #15 (draft-ltsd-l3sm-l3vpn-service-model): Multi CE vs Single CE Multi-homing (network access diversity)
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, 02 Sep 2016 04:44:41 -0000

Hi,

The example case 2 is limited where the CE is provider-managed and the provider deployed multiple CEs at their customer premises.
I think this is a specific use case for particular customers for particular service providers. To avoid  frequent misconfiguration from majority customers who don't have multiple CEs, we have to consider an additional solution how to differentiate a customer has multiple CEs, and this brings a complexity.
Such a specific requirement should be solved by augmentation.

All the best,
Kenichi

-----Original Message-----
From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of l3sm issue tracker
Sent: Thursday, September 01, 2016 4:58 AM
To: draft-ltsd-l3sm-l3vpn-service-model@tools.ietf.org; jplandry@bell.ca
Cc: l3sm@ietf.org
Subject: [L3sm] [l3sm] #15 (draft-ltsd-l3sm-l3vpn-service-model): Multi CE vs Single CE Multi-homing (network access diversity)

#15: Multi CE vs  Single CE   Multi-homing  (network access  diversity)

 The current model allows to implement site multi-homing to different POPs  or PEs (or even Line Cards) but does not allow to specify whether the  different network accesses should use same or different CEs.

 Considering multiple diversity constraints can be specified per network  access, it should be feasible to combine them to achieve a more  deterministic configuration specification. Adding "Same CE" and  "Diverse  CE" constraint types would enable this.
 == Example Case 1 Single CE multi-homing configuration ==  Constraint 1: Network Access 1 needs a "Diverse PE" with “all-access”
 Constraint 2: Network Access 1 needs "Same CE" as “all-access”

 == Example Case 2 Multi CE multi-homing configuration ==  Constraint 1: Network Access 1 needs a "Diverse PE" with “all-access”
 Constraint 2: Network Access 1 needs "Diverse CE" with “all-access”

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

Ticket URL: <https://trac.tools.ietf.org/wg/l3sm/trac/ticket/15>
l3sm <https://tools.ietf.org/l3sm/>

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

v2.23.0 | Report a Bug | By Email