Re: 答复: Questions about the draft of "A new Designated Forwarder Election for the EVPN"
"Satya Mohanty (satyamoh)" <satyamoh@cisco.com> Wed, 01 October 2014 15:46 UTC
Return-Path: <satyamoh@cisco.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 33DF61ACE7D
for <l2vpn@ietfa.amsl.com>; Wed, 1 Oct 2014 08:46:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.986
X-Spam-Level:
X-Spam-Status: No, score=-14.986 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3,
RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001,
USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 wVgbpO8-jG17 for <l2vpn@ietfa.amsl.com>;
Wed, 1 Oct 2014 08:45:58 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79])
(using TLSv1 with cipher RC4-SHA (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 14A3A1ACE77
for <l2vpn@ietf.org>; Wed, 1 Oct 2014 08:45:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;
d=cisco.com; i=@cisco.com; l=19165; q=dns/txt;
s=iport; t=1412178358; x=1413387958;
h=from:to:subject:date:message-id:references:in-reply-to:
mime-version; bh=oqlJ3gywqLm0kDQ7yv2iguDrZ8aokXILWPLvJFLy8bo=;
b=jNLGoPcIC+dwhV+BXK0rtumd6Tm18pgSkp4+gRPCcJi4k5eJzqo2CE3F
EpOHSZotjs2txcBE6dJAYIpAE1bCyUJy+3zxgkjT5S8AJNJJc3eSTxWKz
l5hHBFGvNxbi0Gdzw8asEqD5Hl8xme4xo5dYv861J7byReTilo/e8quux g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgFAA8hLFStJA2K/2dsb2JhbABggkhGgSwEgn7PBwIZcxYBe4QDAQEBBCNmAgEGAhEDAQIoAwICAjAUBgMIAQEEARIbiCOMIpxMlWsBF49DAREBNQoXAYJ4gVMFkW2LRoxFiS6CIIFDbIEPOYECAQEB
X-IronPort-AV: E=Sophos;i="5.04,633,1406592000";
d="scan'208,217";a="359855210"
Received: from alln-core-5.cisco.com ([173.36.13.138])
by rcdn-iport-8.cisco.com with ESMTP; 01 Oct 2014 15:45:58 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75])
by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s91FjvJp024279
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL);
Wed, 1 Oct 2014 15:45:57 GMT
Received: from xmb-aln-x07.cisco.com ([169.254.2.136]) by
xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.03.0195.001; Wed, 1
Oct 2014 10:45:56 -0500
From: "Satya Mohanty (satyamoh)" <satyamoh@cisco.com>
To: "Ali Sajassi (sajassi)" <sajassi@cisco.com>, Haoweiguo
<haoweiguo@huawei.com>, "l2vpn@ietf.org" <l2vpn@ietf.org>
Subject: =?utf-8?B?UmU6IOetlOWkjTogUXVlc3Rpb25zIGFib3V0IHRoZSBkcmFmdCBvZiAiQSBu?=
=?utf-8?Q?ew_Designated_Forwarder_Election_for_the_EVPN"?=
Thread-Topic: =?utf-8?B?562U5aSNOiBRdWVzdGlvbnMgYWJvdXQgdGhlIGRyYWZ0IG9mICJBIG5ldyBE?=
=?utf-8?Q?esignated_Forwarder_Election_for_the_EVPN"?=
Thread-Index: Ac/cVzVI2xbfnFI0SNaQkvamT0+xcgAA58Xl///5GYCAADNn9YAAnQYAgAF83IA=
Date: Wed, 1 Oct 2014 15:45:56 +0000
Message-ID: <D05161B5.1C6D2%satyamoh@cisco.com>
References: <DD5FC8DE455C3348B94340C0AB5517334F806A16@nkgeml501-mbs.china.huawei.com>
<D0502DC5.F0F11%sajassi@cisco.com>
In-Reply-To: <D0502DC5.F0F11%sajassi@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.21.82.232]
Content-Type: multipart/alternative;
boundary="_000_D05161B51C6D2satyamohciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/PqC-qXo3-1VhqKb4jVeyqrAEDwA
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: Wed, 01 Oct 2014 15:46:05 -0000
Haoweiguo, In addition to Ali's clarifications. Since EVPN is a BGP based solution, anytime the BGP peering between the PE and its corresponding peer (usually a Route Reflector), is down, the DF Election algorithm needs to be recomputed at all participating PEs. In fact the PEs could be connected through hierarchical RR clusters, and there can be a connectivity there as well. These wont be visible to DRNI ; so it wont be able to act on these kind of failures. Thanks, --Satya From: "Ali Sajassi (sajassi)" <sajassi@cisco.com<mailto:sajassi@cisco.com>> Date: Tuesday, September 30, 2014 10:02 AM To: Haoweiguo <haoweiguo@huawei.com<mailto:haoweiguo@huawei.com>>, "l2vpn@ietf.org<mailto:l2vpn@ietf.org>" <l2vpn@ietf.org<mailto:l2vpn@ietf.org>> Subject: Re: 答复: Questions about the draft of "A new Designated Forwarder Election for the EVPN" Haoweiguo, First we are not in business of comparing/contrasting our solutions/procedures with the ones from other SDOs. We have written a requirement document [RFC7209], and we need to ensure our solutions to adhere to the specified requirements. Second, wrt your question on what are the advantages of EVPN redundancy mechanism compare to DRNI, just FYI, there are couple of main advantages: 1. EVPN can accommodate any number of systems in a redundancy group (not just 2 or 3 !!) - e.g., in DRNI terminology, you can have any number of systems in a Portal 2. EVPN doesn’t require any data links (virtual or physical) between the member of redundancy groups – e.g., no Intra-Portal Links are required Cheers, Ali From: Haoweiguo <haoweiguo@huawei.com<mailto:haoweiguo@huawei.com>> Date: Monday, September 29, 2014 at 10:46 PM To: Cisco Employee <sajassi@cisco.com<mailto:sajassi@cisco.com>>, "l2vpn@ietf.org<mailto:l2vpn@ietf.org>" <l2vpn@ietf.org<mailto:l2vpn@ietf.org>> Subject: 答复: Questions about the draft of "A new Designated Forwarder Election for the EVPN" Hi Ali, Compared to IEEE DRNI, what's the advantage of your solution? It's better to add a section in your draft to describe the comparison. Thanks weiguo ________________________________ 发件人: Ali Sajassi (sajassi) [sajassi@cisco.com<mailto:sajassi@cisco.com>] 发送时间: 2014年9月30日 12:36 收件人: Haoweiguo; l2vpn@ietf.org<mailto:l2vpn@ietf.org> 主题: Re: Questions about the draft of "A new Designated Forwarder Election for the EVPN" There is no plan to use DRNI for EVPN. -Ali From: Haoweiguo <haoweiguo@huawei.com<mailto:haoweiguo@huawei.com>> Date: Monday, September 29, 2014 at 8:03 PM To: "l2vpn@ietf.org<mailto:l2vpn@ietf.org>" <l2vpn@ietf.org<mailto:l2vpn@ietf.org>> Subject: Questions about the draft of "A new Designated Forwarder Election for the EVPN" Sorry to repost the email to make it more clear... Hi Co-authors, In all-active connection case, to avoid frame duplication and looping, only one exit point among multiple PEs corresponding to a ESI is allowed to egress BUM traffic from EVPN network to local access network . DF election algorithm is a candidated solution. To overcome some DF election drawbacks,this draft proposed a new algorithm to replace DF election algorithm. IEEE802.1AX,DRNI specs also can meet EVPN active-active connection requirements. Do you have plan to use IEEE existing standard to solve the problem? Thanks weiguo ________________________________ 发件人: L2vpn [l2vpn-bounces@ietf.org<mailto:l2vpn-bounces@ietf.org>] 代表 Haoweiguo [haoweiguo@huawei.com<mailto:haoweiguo@huawei.com>] 发送时间: 2014年9月30日 10:37 收件人: l2vpn@ietf.org<mailto:l2vpn@ietf.org> 主题: Questions about the draft of "A new Designated Forwarder Election for the EVPN" Hi Co-authors, In all-active connection case, to avoid frame duplication and looping, only one exit point multiple PEs corresponding to a ESI is allowed to egress BUM traffic from EVPN network to local access network among . DF election algorithm is a candidated solution. To overcome some DF election drawbacks,this draft proposed a new algorithm to replace DF election algorithm. IEEE802.1AX,DRNI specs also can meet EVPN active-active connection requirements. Do you have plan to use IEEE existing standard to solve the problem? Thanks weiguo
- Questions about the draft of "A new Designated Fo… Haoweiguo
- Questions about the draft of "A new Designated Fo… Haoweiguo
- Re: Questions about the draft of "A new Designate… Ali Sajassi (sajassi)
- 答复: Questions about the draft of "A new Designate… Haoweiguo
- Re: 答复: Questions about the draft of "A new Desig… Ali Sajassi (sajassi)
- Re: 答复: Questions about the draft of "A new Desig… Satya Mohanty (satyamoh)