IETF Logo Mail Archive

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

Qin Wu <bill.wu@huawei.com> Thu, 01 September 2016 00:51 UTC

Return-Path: <bill.wu@huawei.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 3938112D7D2 for <l3sm@ietfa.amsl.com>; Wed, 31 Aug 2016 17:51:20 -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 iAJPQdXT_qHs for <l3sm@ietfa.amsl.com>; Wed, 31 Aug 2016 17:51:18 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FA4B12B044 for <l3sm@ietf.org>; Wed, 31 Aug 2016 17:51:17 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml706-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CQN61692; Thu, 01 Sep 2016 00:51:15 +0000 (GMT)
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by lhreml706-cah.china.huawei.com (10.201.5.182) with Microsoft SMTP Server (TLS) id 14.3.235.1; Thu, 1 Sep 2016 01:51:15 +0100
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.179]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0235.001; Thu, 1 Sep 2016 08:51:12 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "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] [l3sm] #15 (draft-ltsd-l3sm-l3vpn-service-model): Multi CE vs Single CE Multi-homing (network access diversity)
Thread-Index: AQHSA8IDT6YJ2Nq01EaXb2XWX9YWdKBjzKEg
Date: Thu, 01 Sep 2016 00:51:11 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA853B5C82@nkgeml513-mbx.china.huawei.com>
References: <056.58954a1533bba8322f5b6b46420a5b55@tools.ietf.org>
In-Reply-To: <056.58954a1533bba8322f5b6b46420a5b55@tools.ietf.org>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.79.65]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020203.57C77B83.01F9, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.1.179, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: b04c47903d4c7b93a99396832cf29dd1
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/b1B2QvEeU9rhALAaaxpceYcjYyA>
Cc: "l3sm@ietf.org" <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: Thu, 01 Sep 2016 00:51:20 -0000

It looks we receive a few late comments after the extended working group Last call.
Thanks Jplandry to bring up these issue and file tickets to get them tracked.
Authors, please consider to address these comments.

-Qin
-----邮件原件-----
发件人: L3sm [mailto:l3sm-bounces@ietf.org] 代表 l3sm issue tracker
发送时间: 2016年9月1日 3:58
收件人: draft-ltsd-l3sm-l3vpn-service-model@tools.ietf.org; jplandry@bell.ca
抄送: l3sm@ietf.org
主题: [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