IETF Logo Mail Archive

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

"Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net> Fri, 02 September 2016 21:47 UTC

Return-Path: <zzhang@juniper.net>
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 57CA212D56C; Fri, 2 Sep 2016 14:47:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=junipernetworks.onmicrosoft.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 0KP0yNsffDYY; Fri, 2 Sep 2016 14:47:40 -0700 (PDT)
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03on0109.outbound.protection.outlook.com [104.47.40.109]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65D0D12B076; Fri, 2 Sep 2016 14:47:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junipernetworks.onmicrosoft.com; s=selector1-juniper-net; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=E0ntXMSEH6vBhmUU1vItDTvXtypNFF7CDeDaIId3BdY=; b=L6+ZPzhkjqPpdD28pK3bLdIEmI0NAF3jZEBaTVjAZLL08uTViyDPfJ0V4H1Kh2Qahow0y5qd7ZaZBxI79pTuueymQEc2tSVuC7t2ThK+XZlBq3VAeNfEh7D7+wUgeRrl/UWDoLfNJQZXd+5DFZij/SDCJjE6BgaQ66mVAPlPw5Y=
Received: from DM5PR05MB3145.namprd05.prod.outlook.com (10.173.219.15) by CY1PR05MB2186.namprd05.prod.outlook.com (10.166.192.10) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384) id 15.1.599.8; Fri, 2 Sep 2016 21:47:38 +0000
Received: from DM5PR05MB3145.namprd05.prod.outlook.com ([10.173.219.15]) by DM5PR05MB3145.namprd05.prod.outlook.com ([10.173.219.15]) with mapi id 15.01.0599.008; Fri, 2 Sep 2016 21:47:38 +0000
From: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
To: "Arun Prakash (arprakas)" <arprakas@cisco.com>, "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/xbFfCPq5Uf5cEuX52pcqjLuZ6Ba0mOAgARhkTCAB4ytAIAAB12A
Date: Fri, 02 Sep 2016 21:47:38 +0000
Message-ID: <DM5PR05MB3145BD62EA70FEA19137DBBDD4E50@DM5PR05MB3145.namprd05.prod.outlook.com>
References: <57B308FA.4090201@nokia.com> <47146bd3-9273-5c85-5d2a-77cd10e7881e@juniper.net> <D3E53625.7DEF4%swaagraw@cisco.com> <DM5PR05MB31456BC2147AE1AF6EE10E57D4E10@DM5PR05MB3145.namprd05.prod.outlook.com> <D3EF3855.FC13E%arprakas@cisco.com>
In-Reply-To: <D3EF3855.FC13E%arprakas@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=zzhang@juniper.net;
x-originating-ip: [66.129.241.11]
x-ms-office365-filtering-correlation-id: 7e378ef5-d491-4a0b-b5bb-08d3d37ac1f2
x-microsoft-exchange-diagnostics: 1; CY1PR05MB2186; 6:qK44+v6Nc11fXXlEZw5K6stnwW2YQdaEu1SpD+AfEjIdzfeZkkJvdGGf82a3/lhaMF1l6dyGBFNI6gL/zz4PHrnxi5+vHZzPZd32bKt1rRKu3nZS60HinyQH3AzqD1fMMeFafUczaVw9hGkClSh4aMDXp4lzfIPaF0yvwKmR1/bCAqqUCLl1jncvNUzEMvXzcz7cgmE9/o2fSvX0mD9St8i5KXuz/hyf51AuRNa6T/wk8SXXKAObhkZhfnw87OpITIsn12GSC6P7i15MJiFeTUTaiQcLLNbkEgp+v5Z5bUElrXypSpvRRLjetWqKIW9OHihyjHWe9hD1NFia8e3dWQ==; 5:xLO2BQKCkZqq/ZJ8NykkS3Ei9SY2SNcWmk8G2ntmtvnoW3jmaySF66aPPwdd+RylI3slfbl0YVekzIPDknYbpDlOaQm5d3+F7gnPEhfq/Z6TumurLMFuShyNcWrhpMxOKGY5e88vQR6gMYkglEtECA==; 24:1Ngrt4I2/85tDe3aFj87eXAqAdXkFXfIB5BdDE0e4soYmUMPscaWv3l35Un+ovj8c9GXnoD31pLXpJFD8tE9AwP8K/FAuJ3GZBTx8MofI2Q=; 7:Ce5a+nMYGgd9ZlOWqD39Ipteg0nnWozyIdnGvXJN691/MSXhPxnp07skLxkuqNQU7Rv4qf507GJDMpRjKhIXbcQQXIDjo4Um/LoSV/r4mLe7rl552DDBrN1WEO+R3MOnoUFhYDad1gUMBuLrslL+Z7Y47SiqqjEvsz4s5ea8V1Xt1rKZg+coHbavE+FBjjnnYkkNztchCyTnXVoGPkUik27lVk+ATaVsVorrAY6eEzH3huBJEjzH3GCsS2xKwff/
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CY1PR05MB2186;
x-microsoft-antispam-prvs: <CY1PR05MB2186A2D0AF3EAA6002A52CE7D4E50@CY1PR05MB2186.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(138986009662008)(82608151540597)(95692535739014);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6055026); SRVR:CY1PR05MB2186; BCL:0; PCL:0; RULEID:; SRVR:CY1PR05MB2186;
x-forefront-prvs: 00531FAC2C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(377454003)(199003)(189002)(24454002)(13464003)(106116001)(345774005)(15975445007)(15650500001)(2501003)(77096005)(92566002)(19580395003)(189998001)(87936001)(305945005)(7696003)(122556002)(7736002)(3280700002)(7846002)(5002640100001)(5001770100001)(86362001)(33656002)(97736004)(1941001)(8676002)(68736007)(93886004)(74316002)(5660300001)(76576001)(19580405001)(2900100001)(230783001)(54356999)(76176999)(81166006)(81156014)(99286002)(50986999)(66066001)(105586002)(8936002)(106356001)(2950100001)(11100500001)(101416001)(102836003)(6116002)(4326007)(3846002)(586003)(10400500002)(2906002)(9686002)(3660700001); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR05MB2186; H:DM5PR05MB3145.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Sep 2016 21:47:38.1330 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR05MB2186
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/bb-cTqGH16TVaMCVIoccVBFhGVU>
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:47:43 -0000

Hi Arun,

It's for EVPN only, but using the same concept that has been developed for L3.

If we have both L2 and L3, it would be "ships in the night", and https://tools.ietf.org/html/draft-lin-bess-evpn-irb-mcast-02 is one way to optimize things. That draft talked about using MVPN when a bridge domain is not connected everywhere.

Jeffrey

> -----Original Message-----
> From: Arun Prakash (arprakas) [mailto:arprakas@cisco.com]
> Sent: Friday, September 02, 2016 5:17 PM
> 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
> Cc: draft-zzhang-bess-evpn-bum-procedure-updates@ietf.org; Nikhil Shetty
> (nikshett) <nikshett@cisco.com>
> Subject: Re: [bess] Poll for adoption: draft-zzhang-bess-evpn-bum-
> procedure-updates-03
> 
> 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