IETF Logo Mail Archive

Re: Two comments about draft-rabadan-l2vpn-evpn-optimized-ir-00

"Rabadan, Jorge (Jorge)" <jorge.rabadan@alcatel-lucent.com> Fri, 25 July 2014 20:19 UTC

Return-Path: <jorge.rabadan@alcatel-lucent.com>
X-Original-To: l2vpn@ietfa.amsl.com
Delivered-To: l2vpn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 991851A03AF for <l2vpn@ietfa.amsl.com>; Fri, 25 Jul 2014 13:19:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.342
X-Spam-Level:
X-Spam-Status: No, score=-0.342 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FB_REPLIC_CAP=6.557, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5] autolearn=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 wJ9Hgoqo0diN for <l2vpn@ietfa.amsl.com>; Fri, 25 Jul 2014 13:19:54 -0700 (PDT)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45DD81A008B for <l2vpn@ietf.org>; Fri, 25 Jul 2014 13:19:54 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id s6PKJnCa008484 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 25 Jul 2014 15:19:50 -0500 (CDT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s6PKJmdk020107 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 25 Jul 2014 22:19:48 +0200
Received: from FR711WXCHMBA03.zeu.alcatel-lucent.com ([169.254.3.230]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Fri, 25 Jul 2014 22:19:48 +0200
From: "Rabadan, Jorge (Jorge)" <jorge.rabadan@alcatel-lucent.com>
To: Haoweiguo <haoweiguo@huawei.com>
Subject: Re: Two comments about draft-rabadan-l2vpn-evpn-optimized-ir-00
Thread-Topic: Two comments about draft-rabadan-l2vpn-evpn-optimized-ir-00
Thread-Index: AQHPp2yss+S974O4HUamtD82udyxcZuwpcEA
Date: Fri, 25 Jul 2014 20:19:48 +0000
Message-ID: <CFF80651.4980D%jorge.rabadan@alcatel-lucent.com>
References: <DD5FC8DE455C3348B94340C0AB5517334F7E6909@nkgeml501-mbs.china.huawei.com>
In-Reply-To: <DD5FC8DE455C3348B94340C0AB5517334F7E6909@nkgeml501-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.2.140509
x-originating-ip: [135.239.27.40]
Content-Type: multipart/alternative; boundary="_000_CFF806514980Djorgerabadanalcatellucentcom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/GRhaUVa9Xvpg11GTom8Ekbj7MMg
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Layer 2 Virtual Private Networks <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2vpn/>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jul 2014 20:19:55 -0000

Hi Weiguo,

Thank you for your comments.
Please see in-line.

From: Haoweiguo <haoweiguo@huawei.com<mailto:haoweiguo@huawei.com>>
Date: Thursday, July 24, 2014 at 11:25 AM
To: Jorge Rabadan <jorge.rabadan@alcatel-lucent.com<mailto:jorge.rabadan@alcatel-lucent.com>>
Cc: "l2vpn@ietf.org<mailto:l2vpn@ietf.org>" <l2vpn@ietf.org<mailto:l2vpn@ietf.org>>
Subject: Two comments about draft-rabadan-l2vpn-evpn-optimized-ir-00


Hi Jorge,

I have two comments:
1. More than one REPLICATOR scenario:
In a service where there is more than one or more REPLICATORs,
In per-flow loadbalancing mode:
Relies on LEAF’s local traffic HASH algorithm, a packet can be sent to any one of the REPLICATOR and replicated to destinations.Multicast traffic can be fully dispersed among all REPLICATORs.

OK. This is implementation-specific and compatible with the current draft.

In per-VNI mode:
To ensure traffic loadbalancing among multiple REPLICATORs,each REPLICATOR should announce VNI List or multicast group range to all leafs, the VN List or multicast group on each REPLICATOR is configured by operators in beforehand. For example if there are two REPLICATORs and 100 VN in NVO3 network, REPLICATOR1 can be responsible for VNI 1-50 multicast traffic forwarding, REPLICATOR2 is responsible for VNI 51-100. When a leaf receives multicast traffic from local connecting TS, if the TS belongs to VNI 1-50, the traffic will be sent to REPLICATOR1;If the TS belongs to VNI 51-100, the traffic will be sent to REPLICATOR2.
EVPN protocol should be extended to support VNI List or multicast group range advertisement.

The per-VNI mode is already possible with the current revision of the draft. The LEAF can already build a list of AR-REPLICATORs for each <evi, eth-tag> and decide how to balance. As for the multicast groups, if you refer to IP multicast streams, this is possible in the per-flow balancing mode.



2. Hierarchical REPLICATOR-LEAF:
Hierarchical REPLICATOR-LEAF should be supported, i.e, a device can be REPLICATOR and LEAF at the same time, for lower LAYER network, its REPLICATOR;For upper layer network, its LEAF.

We are already working in a revision that will take care of that.

Thanks

weiguo

v2.23.0 | Report a Bug | By Email