IETF Logo Mail Archive

Re: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum-procedure-updates-03

"Arun Prakash (arprakas)" <arprakas@cisco.com> Fri, 02 September 2016 21:17 UTC

Return-Path: <arprakas@cisco.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6856312D54F; Fri, 2 Sep 2016 14:17:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.07
X-Spam-Level:
X-Spam-Status: No, score=-15.07 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 tGRizgN7aq1q; Fri, 2 Sep 2016 14:17:28 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A119C12D54C; Fri, 2 Sep 2016 14:17:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2352; q=dns/txt; s=iport; t=1472851048; x=1474060648; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=bJz0Pp2jLa2LSdEJallIEdOnw+CH5E/sAvQvUwIbHlY=; b=crRI7wdlhcZzbzM4mFWjRUm7WwrKIPYMgpOwQJMbEg5FkF+TidT18pWK GmiI+b1hKYqM4xGgbCA5zbp5D5J+q8OuOyLB8x0pjgO10Uz3/BsSOKA6/ LSI8UAD+jrTbbH3LD2JilSCB56nUeT7yoEjyLydglAuXChBGWBtqQnTTT E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CzAgBt68lX/5RdJa1cg1ABAQEBAR5XfAe4L4ICJIV4AoFgOBQBAgEBAQEBAQFeJ4RhAQEFAQE4NAsMBAIBCBEEAQEBHgkHJwsUCQgCBAENBYhJAQ68CwEBAQEBAQEBAQEBAQEBAQEBAQEBARcFhi+ETYocBZlTAY81j1mMS4N5AR42hD1whXkBfgEBAQ
X-IronPort-AV: E=Sophos;i="5.30,272,1470700800"; d="scan'208";a="148429061"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Sep 2016 21:17:27 +0000
Received: from XCH-ALN-013.cisco.com (xch-aln-013.cisco.com [173.36.7.23]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id u82LHRaK028497 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 2 Sep 2016 21:17:27 GMT
Received: from xch-rcd-011.cisco.com (173.37.102.21) by XCH-ALN-013.cisco.com (173.36.7.23) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 2 Sep 2016 16:17:26 -0500
Received: from xch-rcd-011.cisco.com ([173.37.102.21]) by XCH-RCD-011.cisco.com ([173.37.102.21]) with mapi id 15.00.1210.000; Fri, 2 Sep 2016 16:17:26 -0500
From: "Arun Prakash (arprakas)" <arprakas@cisco.com>
To: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>, "Swadesh Agrawal (swaagraw)" <swaagraw@cisco.com>, Eric Rosen <erosen@juniper.net>, Martin Vigoureux <martin.vigoureux@nokia.com>, "bess@ietf.org" <bess@ietf.org>
Thread-Topic: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum-procedure-updates-03
Thread-Index: AQHR/xbLj8Uv+bSJTEOMVvTdiMvC4aBbJjWAgARj8QCABxTxAA==
Date: Fri, 02 Sep 2016 21:17:26 +0000
Message-ID: <D3EF3855.FC13E%arprakas@cisco.com>
References: <57B308FA.4090201@nokia.com> <47146bd3-9273-5c85-5d2a-77cd10e7881e@juniper.net> <D3E53625.7DEF4%swaagraw@cisco.com> <DM5PR05MB31456BC2147AE1AF6EE10E57D4E10@DM5PR05MB3145.namprd05.prod.outlook.com>
In-Reply-To: <DM5PR05MB31456BC2147AE1AF6EE10E57D4E10@DM5PR05MB3145.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.5.4.150722
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [171.70.247.23]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <329E3A5649256643BB606B2ABFCF6DDA@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/iUaCzeqy17eFNc1NrYXkHmzXcd0>
Cc: "Nikhil Shetty (nikshett)" <nikshett@cisco.com>, "draft-zzhang-bess-evpn-bum-procedure-updates@ietf.org" <draft-zzhang-bess-evpn-bum-procedure-updates@ietf.org>
Subject: Re: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum-procedure-updates-03
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Sep 2016 21:17:30 -0000

Hi Jeffrey,

Thank you for the explanation. Am not clear if this draft is only for L2
or can it be used for L3 as well?
What if we have both L2 and L3 multicast ?

Thanks
Arun

On 8/28/16, 7:08 PM, "BESS on behalf of Jeffrey (Zhaohui) Zhang"
<bess-bounces@ietf.org on behalf of zzhang@juniper.net> wrote:

>Hi Swadesh,
>
>"Enable MVPN safi and enhance it for EVPN" is not a trivial thing that
>can be cleanly done on top of MVPN. You'd end up complicating MVPN
>procedures a lot for EVPN specific things. Instead, we can apply the same
>principles to EVPN safi and procedures, and that's what this draft is
>about.
>
>BTW, we don't yet see the need of the equivalent of MVPN type-5 routes
>for EVPN. Draft-sajassi-bess-evpn-igmp-mld-proxy already proposed SMET
>route which is very similar to MVPN type-6/7 (to be exact, a combination
>of type-4/6/7). That is explained in
>draft-zzhang-bess-mvpn-evpn-cmcast-enhancements.
>
>Jeffrey
>
>> -----Original Message-----
>> From: Swadesh Agrawal (swaagraw) [mailto:swaagraw@cisco.com]
>> Sent: Friday, August 26, 2016 3:06 AM
>> To: Eric Rosen <erosen@juniper.net>; Martin Vigoureux
>> <martin.vigoureux@nokia.com>; bess@ietf.org
>> Cc: draft-zzhang-bess-evpn-bum-procedure-updates@ietf.org
>> Subject: Re: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum-
>> procedure-updates-03
>> 
>> Why we need to copy MVPN procedures in EVPN. Why not enable MVPN safi
>>and
>> enhance it for any EVPN specific requiremnt. Also going in this
>>direction
>> may require to add 5,6 and 7 routes as well in future.
>> 
>> Regards
>> Swadesh
>> 
>> On 8/25/16, 2:22 PM, "Eric C Rosen" <erosen@juniper.net> wrote:
>> 
>> >Support.
>> >
>> >MVPN has a number of multicast features that are valuable, but haven't
>> >yet been incorporated into EVPN.  This draft takes a comprehensive look
>> >at the MVPN  procedures that provide those features, and shows how to
>> >adapt them to EVPN.   This seems quite valuable to me, and thus I think
>> >the WG should adopt this draft.
>> >
>> >_______________________________________________
>> >BESS mailing list
>> >BESS@ietf.org
>> >https://www.ietf.org/mailman/listinfo/bess
>
>_______________________________________________
>BESS mailing list
>BESS@ietf.org
>https://www.ietf.org/mailman/listinfo/bess

v2.23.0 | Report a Bug | By Email