Re: [Bier] DR election ...

"Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net> Tue, 10 November 2015 22:46 UTC

Return-Path: <zzhang@juniper.net>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0B1A1B4222; Tue, 10 Nov 2015 14:46:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 G6Wj6nea6_wR; Tue, 10 Nov 2015 14:46:29 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0782.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:782]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 097501B421F; Tue, 10 Nov 2015 14:45:26 -0800 (PST)
Received: from CY1PR0501MB1721.namprd05.prod.outlook.com (10.163.140.158) by CY1PR0501MB1723.namprd05.prod.outlook.com (10.163.140.17) with Microsoft SMTP Server (TLS) id 15.1.318.15; Tue, 10 Nov 2015 22:45:06 +0000
Received: from CY1PR0501MB1721.namprd05.prod.outlook.com ([10.163.140.158]) by CY1PR0501MB1721.namprd05.prod.outlook.com ([10.163.140.158]) with mapi id 15.01.0318.003; Tue, 10 Nov 2015 22:45:06 +0000
From: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
To: Toerless Eckert <eckert@cisco.com>
Thread-Topic: [Bier] DR election ...
Thread-Index: AdEbx1XoVoRoqWJEReWKSaVt1JY85AAQIOaAAABbT+A=
Date: Tue, 10 Nov 2015 22:45:05 +0000
Message-ID: <CY1PR0501MB1721DC86A438A2ED37ECD219D4140@CY1PR0501MB1721.namprd05.prod.outlook.com>
References: <CY1PR0501MB17218924FFB052DA1B502BC8D4140@CY1PR0501MB1721.namprd05.prod.outlook.com> <20151110223341.GB19769@cisco.com>
In-Reply-To: <20151110223341.GB19769@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.12]
x-microsoft-exchange-diagnostics: 1; CY1PR0501MB1723; 5:08xP2OuZ5qDTf0HJAVduJerY/G+9D1sS2YmKT4ejLFa/4PdqlaWaypkxhqJIWcbyMNViIMf85rbqxD9LdEtdDXJQ8zYCn5KJhIAeRS3xnkVe0ktCgSuGB6t1SoeD/0W9UG2v9BS/mfouh4D00XfKzg==; 24:vFCjtmvoX14KRx8lDTfw0wn3X/k/1bHGU/9SSPd3exK+wl9yTb31Q/LV9UjJPsdtgJQqyft91bnltXrlA2IHzBpckAN2LCIRZrzFli0D/Wo=; 20:z8ol7sbLIb1wWXfNGhHiO+PUlr98wgarz7akIQ/Kh3G9wjIqBqPpYleZR2O9dYOcH5p27pZ5TpyrR317CW3dNw==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CY1PR0501MB1723;
x-microsoft-antispam-prvs: <CY1PR0501MB1723DA8A5A5C90B442C95C39D4140@CY1PR0501MB1723.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(138986009662008)(95692535739014);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(520078)(5005006)(10201501046)(3002001); SRVR:CY1PR0501MB1723; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0501MB1723;
x-forefront-prvs: 07562C22DA
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(13464003)(199003)(164054003)(189002)(24454002)(377454003)(97736004)(5008740100001)(2950100001)(10400500002)(81156007)(77096005)(33656002)(101416001)(5001920100001)(11100500001)(5007970100001)(54356999)(102836002)(5004730100002)(5001960100002)(74316001)(19580395003)(110136002)(76576001)(15975445007)(50986999)(87936001)(2900100001)(5003600100002)(76176999)(122556002)(40100003)(99286002)(5002640100001)(106356001)(19580405001)(66066001)(105586002)(189998001)(86362001)(92566002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR0501MB1723; H:CY1PR0501MB1721.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:23
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: 10 Nov 2015 22:45:05.7457 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0501MB1723
Archived-At: <http://mailarchive.ietf.org/arch/msg/bier/6on-oXCnef2ssDUwMK2cf8zlpQ4>
Cc: Haoweiguo <haoweiguo@huawei.com>, "bier@ietf.org" <bier@ietf.org>, IJsbrand Wijnands <ice@cisco.com>, "pim@ietf.org" <pim@ietf.org>, Robert Raszuk <robert@raszuk.net>
Subject: Re: [Bier] DR election ...
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <bier.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bier>, <mailto:bier-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bier/>
List-Post: <mailto:bier@ietf.org>
List-Help: <mailto:bier-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bier>, <mailto:bier-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Nov 2015 22:46:31 -0000

Neither should BIER care - or it's transparent to PIM/BIER ... that's my point.

> -----Original Message-----
> From: Toerless Eckert [mailto:eckert@cisco.com]
> Sent: Tuesday, November 10, 2015 5:34 PM
> To: Jeffrey (Zhaohui) Zhang <zzhang@juniper.net>
> Cc: Haoweiguo <haoweiguo@huawei.com>; Robert Raszuk <robert@raszuk.net>;
> IJsbrand Wijnands <ice@cisco.com>; bier@ietf.org; pim@ietf.org
> Subject: Re: [Bier] DR election ...
> 
> 
> https://en.wikipedia.org/wiki/MC-LAG ???
> 
> Thats an L2 technology, PIM would neither know nor care.
> 
> If you're talking about eg: dual-PE or in general dual PIM routers
> connecting to the same LAN, PIM DR/DF priority can follow VRRP/HSRP
> priority to leverage their fast failover draft-zhou-pim-vrrp-03.
> 
> There is no load-splitting in this approach though, so only one
> router is DR/DF. If you want load-balancing, you may want
> draft-ietf-pim-drlb (currently expired, already had last call).
> 
> 
> Toerless
> 
> On Tue, Nov 10, 2015 at 02:52:49PM +0000, Jeffrey (Zhaohui) Zhang wrote:
> > [ + PIM ]
> >
> > Weiguo,
> >
> > In the MC-LAG case, put aside BIER, how does it work today with PIM?
> >
> > Jeffrey
> >
> > From: Haoweiguo [mailto:haoweiguo@huawei.com]
> > Sent: Tuesday, November 10, 2015 7:19 AM
> > To: Jeffrey (Zhaohui) Zhang <zzhang@juniper.net>; Robert Raszuk
> <robert@raszuk.net>; IJsbrand Wijnands <ice@cisco.com>
> > Cc: bier@ietf.org
> > Subject: RE: [Bier] DR election ...
> >
> >
> > Hi Jeffrey,
> >
> > There are two multi-homing scenarios, one is multi-homed network,
> another one is multi-homed device. For multi-homed network, the network is
> a LAN, DR/DF mechanism can be used to select one router as master and
> other routers as slave, only the master router can forward traffic to the
> LAN network, IGMP/MLD extension can be used for the DR/DF election, this
> is the focus of draft-wijnands-bier-mld-lan-election-00. However, if a
> multicast source or receiver is directly accessed to two multicast routers
> through MC-LAG, flow-based loadbalancing can be achieved for uplink
> direction traffic. In this case, IGMP/MLD can't be used for DR/DF election
> for the MC-LAG. I think the new DR/DF election mechanism should also cover
> the MC-LAG multi-homed scenario.
> >
> > My two cents.
> >
> > Thanks,
> >
> > weiguo
> >
> > ________________________________
> > From: Jeffrey (Zhaohui) Zhang [zzhang@juniper.net]
> > Sent: Monday, November 09, 2015 23:08
> > To: Haoweiguo; Robert Raszuk; IJsbrand Wijnands
> > Cc: bier@ietf.org<mailto:bier@ietf.org>
> > Subject: RE: [Bier] DR election ...
> > Not exactly sure about the details of active-active or active-standby
> scenarios and their relationship to BIER, but here is my understanding:
> >
> > - BIER architecture has three layers: multicast overlay, bier forwarding,
> and routing underlay. It is really the multicast overlay's job to handle
> the multi-homing - be it PIM, IGMP/MLD, or BGP, or any other things.
> > - While Ice's DR election draft was triggered from using IGMP/MLD to
> replace PIM for multicast overlay signaling in a BIER domain and the draft
> has some BIER keywords in it, it is really independent of BIER. The draft
> is still applicable if BIER had never happened.
> >
> > Jeffrey
> >
> > From: BIER [mailto:bier-bounces@ietf.org] On Behalf Of Haoweiguo
> > Sent: Thursday, November 05, 2015 7:39 PM
> > To: Robert Raszuk <robert@raszuk.net<mailto:robert@raszuk.net>>;
> IJsbrand Wijnands <ice@cisco.com<mailto:ice@cisco.com>>
> > Cc: bier@ietf.org<mailto:bier@ietf.org>
> > Subject: Re: [Bier] DR election ...
> >
> >
> > I agree with Robert's comments. I think BIER also should cover active-
> active and active-standby access scenarios.
> >
> > Thanks,
> >
> > weiguo
> >
> > ________________________________
> > From: BIER [bier-bounces@ietf.org] on behalf of Robert Raszuk
> [robert@raszuk.net]
> > Sent: Friday, November 06, 2015 8:36
> > To: IJsbrand Wijnands
> > Cc: bier@ietf.org<mailto:bier@ietf.org>
> > Subject: [Bier] DR election ...
> >
> > Ice,
> >
> > As we duscussed offline there are practically two major types of
> multihomed deployments in production networks:
> >
> > 1. True multihoming ... each edge router connect to CEs over different
> subnet
> >
> > 2. Active/standby .. there is multiaccess lan but VRRP is used so hosts
> can have single default out.
> >
> > Now moreover beteen BIER domain and multicast senders and receivers
> there will pretty much always CEs. I am worried that most BIER slides skip
> those.
> >
> > Cheers,
> > R.
> 
> > _______________________________________________
> > BIER mailing list
> > BIER@ietf.org
> > https://www.ietf.org/mailman/listinfo/bier
> 
> 
> --
> ---
> Toerless Eckert, eckert@cisco.com