Re: [Bier] BIER: draft-eckert-bier-cgm2-rbs-01 with performance analysis simulation Tue, 15 February 2022 02:00 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3BD993A0C05 for <>; Mon, 14 Feb 2022 18:00:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id oKNNm_AdF6UH for <>; Mon, 14 Feb 2022 18:00:28 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4E5B33A0BD6 for <>; Mon, 14 Feb 2022 18:00:27 -0800 (PST)
Received: from (unknown []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (FangMail) with ESMTPS id 4JyPSB0kZMz8131j for <>; Tue, 15 Feb 2022 10:00:26 +0800 (CST)
Received: from (unknown []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (FangMail) with ESMTPS id 4JyPRc0DXcz501Zm; Tue, 15 Feb 2022 09:59:56 +0800 (CST)
Received: from ([]) by with SMTP id 21F1xef2009533; Tue, 15 Feb 2022 09:59:40 +0800 (GMT-8) (envelope-from
Received: from mapi (njxapp01[null]) by mapi (Zmail) with MAPI id mid203; Tue, 15 Feb 2022 09:59:40 +0800 (CST)
Date: Tue, 15 Feb 2022 09:59:40 +0800
X-Zmail-TransId: 2af9620b090c51f7b882
X-Mailer: Zmail v1.0
Message-ID: <>
In-Reply-To: <>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
X-MAIL: 21F1xef2009533
X-Fangmail-Gw-Spam-Type: 0
X-FangMail-Miltered: at cgslv5.04- with ID 620B093A.002 by FangMail milter!
X-FangMail-Envelope: 1644890426/4JyPSB0kZMz8131j/620B093A.002/[]/<>
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 620B093A.002/4JyPSB0kZMz8131j
Archived-At: <>
Subject: Re: [Bier] BIER: draft-eckert-bier-cgm2-rbs-01 with performance analysis simulation
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 15 Feb 2022 02:00:36 -0000

Hi Toerless, 
Thank you very much for your response! 
I have one more question, let we consider CGM2/RBS solution only. 
Since all the bits have local significance in CGM2/RBS,  what if we want to send one flow to multiple BFERs but we don't want to indicate any path?
In this case we can't reach the BFERs because we don't put any path bits in the BitString and there is no global BIFT in the intermediate nodes, right?
Best regards,

日 期 :2022年02月11日 00:51
主 题 :Re: [Bier] BIER: draft-eckert-bier-cgm2-rbs-01 with performance analysis simulation
On Thu, Feb 10, 2022 at 09:16:28AM +0800, wrote:
> Hi Toerless,
> Haven't read the new version of CGM2/RBS, just have the same question with Jeffrey.
> If I understand BIER-TE and CGM2/RBS solutions right, the forwarding tables of the two methods are only focus on the local links.
> So the table's scale for the two solutions is almost same.
Jeffrey wasn't asking about BIER-TE (i think).
> The commen issue of the two solution is the BSL limitation.
> BIER-TE solution has an exclusive issue that the BP needs to be assigned globally.
> But in CGM2/RBS solution, the BP needs not to be assigned globally.
> So the main difference of the two solutions is: is it necessary to assign the BP globally, right?
That is one core difference, yes. And it eliminates IMHO all the scaling
challenges we have with BIER-TE (that we try to compensate for to some degree with
controller based bit optimizations). But as discussed in the answer to Jeffs message,
the fact that the encoding in CGM2/RBS is a tree means that we also eliminate
the BIER/BIER-TE issue that a bitstring can carry a lot of unnecessary (zero) bits
and need to make multiple copies just because some BFER or adjacencies have their
bits in different SI (in larger topologies).
> Best regards,
> Sandy
> ------------------原始邮件------------------
> 发件人:Jeffrey(Zhaohui)Zhang
> 收件人;;
> 抄送人;
> 日 期 :2022年02月10日 04:50
> 主 题 :Re: [Bier] BIER: draft-eckert-bier-cgm2-rbs-01 with performance analysis simulation
> Hi Toerless,
> Not sure if my understanding is correct, but it seems that RBS does not reduce the number of bits that are needed to encode the tree. Rather, it increases the number of bits (to encode the recursive structure).
> I agree that it reduces the size of BIFTs, but even current BIER-TE can reduce the number of copies if you use a longer bitstring?
> Jeffrey
> Juniper Business Use Only
> -----Original Message-----
> From: BIER <> On Behalf Of
> Sent: Wednesday, February 9, 2022 2:19 PM
> To:
> Cc:
> Subject: [Bier] BIER: draft-eckert-bier-cgm2-rbs-01 with performance analysis simulation
> [External Email. Be cautious of content]
> Dear BIER-TE WG:
> Robin did add a section (6.3) describing an initial performance gain analysis of CGM2/RBS to the github source (;!!NEt6yMaO-gk!WS49OT72vlonSWP3yLtLcW_RQARYP00KEiAWpH592AuDXmrOOJH_bgVzQZyfK9En$ ), and i just did a bit of editorial fixup and posted it as -01 of the draft.
> This actually is the first time i actually like the HTML'ized version of a draft, because the topology picture is so large it doesn't fit a single page:
> The interesting piece about the comparison is that it is actually comparing CGM2/RBS to BIER, and not BIER-TE. Because BIER itself should be requiring less copies than BIER-TE, so the gain of CGM2/RBS over BIER-TE should be even higher, but the fact alone that you get away with fewer packet copies to large receiver sets even though the bitstring also needs to encode the path/tree towards the receivers is really cool.
> Robin, two Q:
> 1. The new text mentions "in our graphs", but the text does not include any such graphs (yet).
> I guess such a graph would be even worse to convert to ASCII than the topology.
> Maybe post whatever format you have those results in to github (PDF, png...) and then we actually may want to see if/how a PDF version of the draft could include better than just ASCII art. Certainly a good reason to finally try it out.
> And short term we can just add references to such visuals to the draft.
> 2; Is it correct to assume that the hops through the topology that you simulated are "just" shortest-path, maybe with some ECMP choice - aka: the same paths that also BIER would choose given some "default" IGP routing setup ?
> Cheers
> Toerless
> _______________________________________________
> BIER mailing list
> _______________________________________________
> BIER mailing list