
From nobody Sat May  1 03:42:35 2021
Return-Path: <adrian@olddog.co.uk>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D65B3A1386; Sat,  1 May 2021 03:42:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.782
X-Spam-Level: 
X-Spam-Status: No, score=0.782 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAY_BE_FORGED=2.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
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 yhhnIkLgFGLB; Sat,  1 May 2021 03:42:31 -0700 (PDT)
Received: from mta6.iomartmail.com (mta6.iomartmail.com [62.128.193.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 726CB3A1382; Sat,  1 May 2021 03:42:27 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta6.iomartmail.com (8.14.4/8.14.4) with ESMTP id 141AgKgV011923; Sat, 1 May 2021 11:42:20 +0100
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 7B07C2203A; Sat,  1 May 2021 11:42:20 +0100 (BST)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs3.iomartmail.com (Postfix) with ESMTPS id 6602922032; Sat,  1 May 2021 11:42:20 +0100 (BST)
Received: from LAPTOPK7AS653V (74.197.bbplus.pte-ag1.dyn.plus.net [81.174.197.74] (may be forged)) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.4/8.14.4) with ESMTP id 141AgJEE003461 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 1 May 2021 11:42:19 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'BIER WG'" <bier@ietf.org>
Cc: <draft-ietf-bier-ipv6-requirements@ietf.org>
Date: Sat, 1 May 2021 11:42:19 +0100
Organization: Old Dog Consulting
Message-ID: <01e801d73e76$a9f46c30$fddd4490$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: Adc+dCgezVRXt1a0SPiAUsVrQizUDw==
Content-Language: en-gb
X-Originating-IP: 81.174.197.74
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-26124.006
X-TM-AS-Result: No--4.495-10.0-31-10
X-imss-scan-details: No--4.495-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-26124.006
X-TMASE-Result: 10--4.494500-10.000000
X-TMASE-MatchedRID: UjGGZgD0m5UOwAmmWH5kBGxZ52CskxD+4Z1E3dd9R5lSCC/XvBtGypHc Remxdl5jT3xbA8Cn+evO39xuTH+S8oAAbHuIyuvnN8QmGQ8nUhovsOOmgOo1mSaTNbgbq25FQnU C1jfTwgt9bir0JAlV/yivjKXQTfpLsUfeSO4/2THVr2dC6ax+agKflB9+9kWViR84olPm6b20y3 Da3B9hq+LzNWBegCW2XC3N7C7YzrfQqQhSw0x2VGrz/G/ZSbVq+gtHj7OwNO0kshYUTZcZE797a 3xBG7FRraavcXfmWnxEziEKI+pDv2/3Vic9mx3g6Hq9RCTLxvsstHmcXeW1eBVSGW4LjW40FYnP SoXfG8ckhYHVA/r8kw==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/EUuqh0Bmy48nVPYLjNMHNZ5nkdc>
Subject: [Bier] Plans for draft-ietf-bier-ipv6-requirements
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 01 May 2021 10:42:34 -0000

Hi,

I notice that draft-ietf-bier-ipv6-requirements has expired.

There was lots of discussion about the draft in November and December last
year, but nothing seems to have happened since.

Is it our plan to use the draft as a repository for the results of
discussions, or is there an intention to pursue publication as an RFC.

In either case, it would be good to see an update that captures the
discussions from the end of last year.

Thanks,
Adrian


From nobody Thu May  6 23:22:32 2021
Return-Path: <hayabusagsm@gmail.com>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49B0A3A07DB; Thu,  6 May 2021 23:22:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level: 
X-Spam-Status: No, score=-2.087 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 0ksQH1y63iD3; Thu,  6 May 2021 23:22:25 -0700 (PDT)
Received: from mail-pf1-x429.google.com (mail-pf1-x429.google.com [IPv6:2607:f8b0:4864:20::429]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E22B3A07D4; Thu,  6 May 2021 23:22:25 -0700 (PDT)
Received: by mail-pf1-x429.google.com with SMTP id e15so6871299pfv.10; Thu, 06 May 2021 23:22:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zTCkfTbgBjyVvHsV2EdHPElQqR6rZS7zUIWmh16KqQU=; b=taH+SMqf05zXwp0At1RpWKSYfCcpD4g03i69IURJjDcqKhXsmriF/HQ7hGvVEdFPyd mlRzTwzwS0vGJVJ9MPKCpf1mpFXWDEZDQPj7dFUH7WMUyUErUb27z3yCpzUsaS94IQ+u cNKCV94Y6cWAGhhLi4afJTe1zOf/yY6aCjitrVVPL1WjWs9CH4UXRyf2M3Os4dejHWKf LO52EVk+qD+zGBctW2Kel59nHLwVhOAQlhfdMh7R94yvdM06RbdN+V74BJjguZXNZGRG 9VDXNx6P0RdyhWOq95gnjflc+SLbSUBiGoy3n2/P29faPWB6djj9N6qbX1+ykEhJZI6s nujQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zTCkfTbgBjyVvHsV2EdHPElQqR6rZS7zUIWmh16KqQU=; b=cLHuXJMagdbGv/0S0GAwJZe+jjjgwD603S655UQozGIKukZJlLB6160mOUg29xq9lS DZ1qy93B93PwdnTMzdt8J7AUGYoloCjd84P6ZfYvFGz2dHnlfRnMawQeDjadwNza1ixx MLB8Byk47LCL1Jzvkqy/KWq7cY+qNJwhCrfkAgr/1akkMlrwsIg6Uknr46qpqRsdCzAm R+xcn6dRV8jLV6nmstjDjCu8+tTo+uWMgwDsMRwRkq+Rscts8v5DsdWuyGpTb/TG6xza UhJPqWkXKn94b/vdFCt+DDgB3nBLH1BpDc4a2jVB4qOHldGgj+ciZdtv2+H9zny6D4Bj eFiw==
X-Gm-Message-State: AOAM531z2StRxJgJZQSbdO/wUQBD01svBiLAwjKH4AznGF4awJL7zfyw C4V4wPbekaG59kjm6xJVOlLewik4LGqWrpq6+m+hxUkepQM=
X-Google-Smtp-Source: ABdhPJy07DRfrVkROtKJ5hd2xnWssaQ6G6wIlRF/Fet6SHcUMZS9TJOMxHBF+5vh88bhW6+Peschdvq6OX4+yWJLvPQ=
X-Received: by 2002:aa7:8d03:0:b029:259:f2ed:1849 with SMTP id j3-20020aa78d030000b0290259f2ed1849mr9081617pfe.30.1620368543229; Thu, 06 May 2021 23:22:23 -0700 (PDT)
MIME-Version: 1.0
References: <01e801d73e76$a9f46c30$fddd4490$@olddog.co.uk>
In-Reply-To: <01e801d73e76$a9f46c30$fddd4490$@olddog.co.uk>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Fri, 7 May 2021 02:22:12 -0400
Message-ID: <CABNhwV2HHrN=rrTbWO=QkQw9Ce7Diwbhqs=WMUe8Rs2tZfg4oQ@mail.gmail.com>
To: adrian@olddog.co.uk
Cc: BIER WG <bier@ietf.org>, draft-ietf-bier-ipv6-requirements@ietf.org
Content-Type: multipart/alternative; boundary="0000000000006caa5905c1b7738e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/AH86t2BkStGFsp520ExKSvyV6Qs>
Subject: Re: [Bier] Plans for draft-ietf-bier-ipv6-requirements
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 07 May 2021 06:22:31 -0000

--0000000000006caa5905c1b7738e
Content-Type: text/plain; charset="UTF-8"

Hi Adrian

Thanks for asking about this draft.

Mike McBride is the main editor for this draft.  So this draft per Mike,
the goal was to help drive requirements for a solution but not progress  to
RFC.

The last update to the draft was prior IETF 109  when the appendixes were
removed from the draft.

My suggestion was to rollback the draft adding back the appendixes which I
think have a lot of value.

I will plan to update and add back the appendixes also any other updates
from the discussions on the two solutions we had last year.

Kind Regards

Gyan

On Sat, May 1, 2021 at 6:42 AM Adrian Farrel <adrian@olddog.co.uk> wrote:

> Hi,
>
> I notice that draft-ietf-bier-ipv6-requirements has expired.
>
> There was lots of discussion about the draft in November and December last
> year, but nothing seems to have happened since.
>
> Is it our plan to use the draft as a repository for the results of
> discussions, or is there an intention to pursue publication as an RFC.
>
> In either case, it would be good to see an update that captures the
> discussions from the end of last year.
>
> Thanks,
> Adrian
>
> _______________________________________________
> BIER mailing list
> BIER@ietf.org
> https://www.ietf.org/mailman/listinfo/bier
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*



*M 301 502-1347*

--0000000000006caa5905c1b7738e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Hi Adrian</div><div dir=3D"auto"><br></div><div dir=3D"au=
to">Thanks for asking about this draft.</div><div dir=3D"auto"><br></div><d=
iv dir=3D"auto">Mike McBride is the main editor for this draft.=C2=A0 So th=
is draft per Mike, the goal was to help drive requirements for a solution b=
ut not progress =C2=A0to RFC. =C2=A0</div><div dir=3D"auto"><br></div><div =
dir=3D"auto">The last update to the draft was prior IETF 109 =C2=A0when the=
 appendixes were removed from the draft.</div><div dir=3D"auto"><br></div><=
div dir=3D"auto">My suggestion was to rollback the draft adding back the ap=
pendixes which I think have a lot of value.</div><div dir=3D"auto"><br></di=
v><div dir=3D"auto">I will plan to update and add back the appendixes also =
any other updates from the discussions on the two solutions we had last yea=
r.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Kind Regards=C2=A0</d=
iv><div dir=3D"auto"><br></div><div dir=3D"auto">Gyan</div><div><br><div cl=
ass=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, May 1, 20=
21 at 6:42 AM Adrian Farrel &lt;<a href=3D"mailto:adrian@olddog.co.uk">adri=
an@olddog.co.uk</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<=
br>
<br>
I notice that draft-ietf-bier-ipv6-requirements has expired.<br>
<br>
There was lots of discussion about the draft in November and December last<=
br>
year, but nothing seems to have happened since.<br>
<br>
Is it our plan to use the draft as a repository for the results of<br>
discussions, or is there an intention to pursue publication as an RFC.<br>
<br>
In either case, it would be good to see an update that captures the<br>
discussions from the end of last year.<br>
<br>
Thanks,<br>
Adrian<br>
<br>
_______________________________________________<br>
BIER mailing list<br>
<a href=3D"mailto:BIER@ietf.org" target=3D"_blank">BIER@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/bier" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/listinfo/bier</a><br>
</blockquote></div></div>-- <br><div dir=3D"ltr" class=3D"gmail_signature" =
data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><div dir=3D"ltr"><div d=
ir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"l=
tr"><div><p style=3D"color:rgb(34,34,34)"><a href=3D"http://www.verizon.com=
/" style=3D"color:rgb(17,85,204);padding-bottom:1em;display:inline-block" t=
arget=3D"_blank"><img src=3D"http://ss7.vzw.com/is/image/VerizonWireless/vz=
-logo-email" width=3D"81" height=3D"18" style=3D"height:18px;width:81px"></=
a><br></p><p style=3D"font-size:1em;margin:0px;font-family:&quot;Verizon NH=
G DS&quot;,Arial,sans-serif;line-height:13px;color:black"><b>Gyan Mishra</b=
></p><p style=3D"color:rgb(34,34,34);margin:0px;line-height:13px"><font fac=
e=3D"georgia, serif" style=3D"color:black;font-size:1em"><i>Network Solutio=
ns A</i></font><font color=3D"#000000" face=3D"georgia, serif"><i>rchitect=
=C2=A0</i></font></p><p style=3D"color:rgb(34,34,34);margin:0px;line-height=
:13px"><i style=3D"color:rgb(0,0,0);font-size:13px"><font face=3D"georgia, =
serif">Email <a href=3D"mailto:gyan.s.mishra@verizon.com" target=3D"_blank"=
>gyan.s.mishra@verizon.com</a></font></i><font color=3D"#000000" face=3D"ge=
orgia, serif"><i><br></i></font></p><p style=3D"font-size:1em;margin:0px;li=
ne-height:13px;color:black"><i><font face=3D"georgia, serif">M 301 502-1347=
<br><br></font></i></p></div><div><br></div></div></div></div></div></div><=
/div></div></div>

--0000000000006caa5905c1b7738e--


From nobody Fri May 14 13:15:03 2021
Return-Path: <aretana.ietf@gmail.com>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9E1B3A3ED7; Fri, 14 May 2021 13:14:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 9coBMby-l4oh; Fri, 14 May 2021 13:14:49 -0700 (PDT)
Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10AFD3A3EC7; Fri, 14 May 2021 13:14:48 -0700 (PDT)
Received: by mail-ed1-x534.google.com with SMTP id di13so36004160edb.2; Fri, 14 May 2021 13:14:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:mime-version:date:message-id:subject:to:cc :content-transfer-encoding; bh=RSnJvjf9l7Wa/8IlKRJ0o/qxykDjz1TRpEArhQTr+5Q=; b=Gcsb1kZ55NYA3vyGdjvcg6IMOyZkYl4NNdzvRHbNJglE7cTXQeZmfcOlFS56j9NefD Po7yvf73pH30trCZG+UFdJxzKNMbTeK2u66EMp7Azo588WgtSIoWts360kd6x0qYS3Jy yqJ/3IOGJOveLICFVLzLw7nF7I+dyGfOrpk5uk2i/aIIG4v/jPsCxI9MyC92TOSHjCL9 pwmZjfte5DRX0ntWv9SjaCCXOg5NrA8s0jCc3XQTtpP2Xw32xTSyzi/nMF2VFXfmA2F3 NbmU2hwxTQz/CafU74ep/CTY7WIbi8mw3WMn+SsKIHJ9rHvmsOJFid+z2rYBNbo3dQLf R8Jw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:date:message-id:subject:to:cc :content-transfer-encoding; bh=RSnJvjf9l7Wa/8IlKRJ0o/qxykDjz1TRpEArhQTr+5Q=; b=BnL7y5tFFdBKwDYYa6twnXT+3xObsWMvZoNLVWjx1+8PfnPzgM2IFufrlo+hKXyeTI GOBlHqeQ/Uqc8zY63F/7ctZZr+uEbA5Q6mhcxaXNgxbRPmJVQqkEMFA8n9+4Xl59ssEy 70Ep5Fz1YLLAZEliBVp4LZzGboH5K5uaz0xrwDxQGihq1bvxtTG6aID1uk7U7ecPftDK 1GF3dkBhDq13169XOYxhCfWeiLYecvDlCMb/ZDEqhMauyFSJ3hDh01z44Kgu7LdVoZQK bz4GAHGUh03W5BUVDXdvSeW8Z3kba7I93XUQQdGWxHT4OBTrjw1yXSfjqFQ6aKpfEXRz aZww==
X-Gm-Message-State: AOAM533ucoTtkuaE2OYr2GKpmUqLuKvWOuCI9X1d5gEQMB3CpXQJuDNq RrT22ILMFXU7AjYDqhnVTiVJ8l/v60JREZ1aSRmMqi0M
X-Google-Smtp-Source: ABdhPJzSVp+aZFUnqWiqQ0bCzNnnBhlpttrgqFuSy4RKUrbHUmawzPOfExGpFboO3U+48wsyn5hAuul7RPlRV6sJARE=
X-Received: by 2002:aa7:cc98:: with SMTP id p24mr33413047edt.353.1621023283892;  Fri, 14 May 2021 13:14:43 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Fri, 14 May 2021 13:14:43 -0700
From: Alvaro Retana <aretana.ietf@gmail.com>
MIME-Version: 1.0
Date: Fri, 14 May 2021 13:14:43 -0700
Message-ID: <CAMMESsxEH-bNuEX6ETZLg1asBj+tPo67GC8BFA2sFx8fD_G9Yg@mail.gmail.com>
To: draft-ietf-bier-te-arch@ietf.org
Cc: "Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com>, BIER WG Chairs <bier-chairs@ietf.org>, BIER WG <bier@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/nnVGGEVt6GbNh3h1D3UJ-cIRvys>
Subject: [Bier] AD Review of draft-ietf-bier-te-arch-09
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 14 May 2021 20:15:03 -0000

Dear authors:

Thank you for the interesting work!


I have a couple of high-level comments/concerns.

(1) What is this document specifying?

=C2=A0 To start, I believe it is ok for an architecture document to be in t=
he
=C2=A0 Standards Track.

=C2=A0 As far as I can see, this document mainly specifies alternate semant=
ics for
=C2=A0 the BitString. =C2=A0Beyond that, the BIER-TE architecture (=C2=A72)=
 maps well onto
=C2=A0 the layering described in =C2=A74/rfc8297, where the BIER layer (=C2=
=A74.2/rfc8297) is
=C2=A0 "replaced" with the BIER-TE Control Plane and the BIER-TE forwarding=
 layer.
=C2=A0 Is this a fair high-level representation of what is defined in this
=C2=A0 document?

=C2=A0 In general, the BIER-TE forwarding is well specified. =C2=A0I would =
prefer it if
=C2=A0 the definition of the adjacencies included normative language. =C2=
=A0The
=C2=A0 requirements section (=C2=A73.6) introduces some confusion with the =
use of "basic
=C2=A0 BIER-TE forwarding" (vs "BIER-TE forwarding"). =C2=A0Suggestion: the
=C2=A0 specification should include required ("basic") and recommended/opti=
onal
=C2=A0 behaviors. =C2=A0See specific comments in-line.

=C2=A0 OTOH, the functions of the BIER-TE control plane are described (not
=C2=A0 specified) in what I consider a set of operational considerations (t=
hings
=C2=A0 the controller could consider -- including sections 4, 5, and 7). =
=C2=A0Having an
=C2=A0 extensive set of operational considerations is a good thing, special=
ly given
=C2=A0 how much BIER-TE relies on the controller. =C2=A0The BIER-TE control=
 protocol is
=C2=A0 central to the operation/implementation of BIER-TE, but left out of =
scope
=C2=A0 (see my comments in =C2=A72.2).

=C2=A0 The BIER-TE topology is a "key new component in BIER-TE". =C2=A0The =
document
=C2=A0 doesn't specify, explain, or leave out of scope how "BIER-TE Control=
ler
=C2=A0 discovers the network topology and creates the BIER-TE topology from=
 it"
=C2=A0 (=C2=A72.2). =C2=A0This omission is a significant hole in the archit=
ecture.

=C2=A0 It would be ideal if the Introduction included a high-level overview=
 of the
=C2=A0 document.


(2) Can BIER and BIER-TE really coexist in the same network?

=C2=A0 The Abstract mentions that they can:

=C2=A0 =C2=A0 =C2=A0BIER-TE can co-exist with BIER forwarding in the same d=
omain, for
=C2=A0 =C2=A0 =C2=A0example by using separate BIER sub-domains.

=C2=A0 The result of separate sub-domains is more akin to ships-in-the-nigh=
t than
=C2=A0 having them be "mixed": in the same sub-domain using a single BIFT
=C2=A0 (populated by different sources). =C2=A0 Is this correct?

=C2=A0 =C2=A73.3 speculates about potential "definitions in BIER encapsulat=
ion
=C2=A0 specifications" to "distinguish BIER from BIER-TE packets" -- and of=
fers a
=C2=A0 workaround if the MPLS encapsulation is used. =C2=A0Even here, a "mi=
xed"
=C2=A0 environment would seem to at least require independent BIFTs, and no=
t be
=C2=A0 possible with non-MPLS encapsulations.

=C2=A0 My conclusion is that using the encapsulation from rfc8296 it is not
=C2=A0 possible to have a "mixed" BIER/BIER-TE network -- unless using MPLS=
 with
=C2=A0 extra labels and separate BIFTs. =C2=A0 This is just a guess -- =C2=
=A0the coexistence
=C2=A0 topic deserves better coverage so that no one has to guess.


(3) Organization

=C2=A0 The document jumps right into examples and a short discussion of the=
 BIER-TE
=C2=A0 topology -- including a quick comparison with BIER (=C2=A71.2). =C2=
=A0There are 3
=C2=A0 other sections that are also called "comparison with BIER" (=C2=A71.=
3, =C2=A73.5, and
=C2=A0 =C2=A77.2). It may make the document clearer if the "baseline" compa=
rison with
=C2=A0 BIER was set from the start (you can dig deeper later of course).

=C2=A0 =C2=A73 describes BIER-TE forwarding, but sample pseudocode is in =
=C2=A76. =C2=A0Please
=C2=A0 move that to =C2=A73.

=C2=A0 As I mentioned above, several of the sections (4, 5, and 7) include
=C2=A0 considerations for the BIER-TE Controller. =C2=A0It would be great i=
f these
=C2=A0 sections were consolidated under a single heading: Operational
=C2=A0 Considerations for the BIER-TE Controller (for example).


Thanks!

Alvaro.


[Line numbers from idnits.]

13	Abstract

[] In general, I think this Abstract is longer than needed -- in fact,
it is longer than the initial part of the Introduction. =C2=A0Consider
making it shorter.


15	 =C2=A0 This memo introduces per-packet stateless strict and loose path
16	 =C2=A0 steered replication and forwarding for Bit Index Explicit Replic=
ation
17	 =C2=A0 packets (RFC8279). =C2=A0This is called BIER Tree Engineering (B=
IER-TE).
18	 =C2=A0 BIER-TE can be used as a path steering mechanism in future Traff=
ic
19	 =C2=A0 Engineering solutions for BIER (BIER-TE).

[major] "BIER-TE" has two different meanings? =C2=A0I'm assuming the last
mention is just a leftover.


...
25	 =C2=A0 In BIER, the BitPositions (BP) of the packets bitstring indicate=
 BIER
26	 =C2=A0 Forwarding Egress Routers (BFER), and hop-by-hop forwarding uses=
 a
27	 =C2=A0 Routing Underlay such as an IGP.

[major] The terminology used here doesn't correspond to what is used
in rfc8279. =C2=A0Please be consistent and don't make up new terminology
unless it is to present something new.

"BitPositions (BP)" doesn't appear in rfc8297. =C2=A0Instead, "bit position=
" is used.

s/bitstring/BitString/g

s/BIER Forwarding Egress Routers (BFER)/Bit-Forwarding Egress Routers (BFER=
s)


29	 =C2=A0 In BIER-TE, BitPositions indicate adjacencies. =C2=A0The BIFT of=
 each BFR
30	 =C2=A0 are only populated with BPs that are adjacent to the BFR in the =
BIER-
31	 =C2=A0 TE topology. =C2=A0The BIER-TE topology can consist of layer 2 o=
r remote
32	 =C2=A0 (routed) adjacencies. =C2=A0The BFR then replicates and forwards=
 BIER
33	 =C2=A0 packets to those adjacencies. =C2=A0This results in the aforemen=
tioned
34	 =C2=A0 strict and loose path steering and replications.

[minor] Expand all acronyms in the Abstract *and* on first mention later on=
.

[nit] s/The BIFT of each BFR are only populated/The BIFT of each BFR
is only populated


36	 =C2=A0 BIER-TE can co-exist with BIER forwarding in the same domain, fo=
r
37	 =C2=A0 example by using separate BIER sub-domains. =C2=A0In the absence=
 of routed
38	 =C2=A0 adjacencies, BIER-TE does not require a BIER routing underlay, a=
nd
39	 =C2=A0 can then be operated without requiring an Interior Gateway Routi=
ng
40	 =C2=A0 protocol (IGP).

[] This paragraph, for example, provides information that doesn't seem
to be easily located in the document body. =C2=A0I can't find another
mention of "co-exist" or easily determine where running separate
sub-domains (for BIER and BIER-TE) is covered. =C2=A0[The spelling is
different, but I finally found some discussion about "subdomains" in
=C2=A73.3.]


...
47	Name explanation

49	 =C2=A0 [RFC-editor: This section to be removed before publication.]

[] As I mentioned above, and is explained below, "BIER-TE" now has two
different meanings. :-( =C2=A0 IMO, this section will only result in
distracting from the contents of the document. =C2=A0Because it will be
deleted before publication anyway, I strongly suggest that you remote
it. =C2=A0It anything, the Shepherd may want to include it in the write-up.


51	 =C2=A0 Explanation for name change from BIER-TE to mean "Traffic
52	 =C2=A0 Engineering" to BIER-TE "Tree Engineering" in WG last-call (to
53	 =C2=A0 benefit IETF/IESG reviewers):

[nit] Up to this point, the IESG hasn't reviewed this document. =C2=A0The
comments did come from an AD, but it wasn't during IESG Evaluation.
This fact doesn't mean that the comments are more or less valid, I'm
just clarifying that the IESG hasn't looked at this document, so
mentioning "IESG reviewers" may, again, distract form the
specification.


...
172	1. =C2=A0Introduction

174	 =C2=A0 BIER-TE shares architecture, terminology and packet formats wit=
h BIER
175	 =C2=A0 as described in [RFC8279] and [RFC8296]. =C2=A0This document de=
scribes
176	 =C2=A0 BIER-TE in the expectation that the reader is familiar with the=
se two
177	 =C2=A0 documents.

[minor] "BIER-TE shares architecture..." =C2=A0Not the complete
architecture since the BitString indicates something different. =C2=A0Maybe
write something like s/architecture/most architectural concepts


...
186	 =C2=A0 Note that related work, [I-D.ietf-roll-ccast] uses Bloom filter=
s
187	 =C2=A0 [Bloom70] to represent leaves or edges of the intended delivery=
 tree.

189	 =C2=A0 Bloom filters in general can support larger trees/topologies wi=
th
190	 =C2=A0 fewer addressing bits than explicit bitstrings, but they introd=
uce
191	 =C2=A0 the heuristic risk of false positives and cannot reset bits in =
the
192	 =C2=A0 bitstring during forwarding to avoid loops. =C2=A0For these rea=
sons, BIER-
193	 =C2=A0 TE uses explicit bitstrings like BIER. =C2=A0The explicit bitst=
rings of
194	 =C2=A0 BIER-TE can also be seen as a special type of Bloom filter, and=
 this
195	 =C2=A0 is how related work [ICC] describes it.

[minor] I don't see any value in including these last 2 paragraphs:
you're basically telling the reader that someone else didn't chose the
same approach.


197	1.1. =C2=A0Basic Examples
...
239	 =C2=A0 Consider the simple network in the above BIER-TE overview examp=
le
240	 =C2=A0 picture with 6 BFRs. p1...p14 are the BitPositions (BP) used. =
=C2=A0All
241	 =C2=A0 BFRs can act as ingress BFR (BFIR), BFR1, BFR3, BFR4 and BFR6 c=
an
242	 =C2=A0 also be egress BFR (BFER). =C2=A0Forward_connected is the name =
for
243	 =C2=A0 adjacencies that are representing subnet adjacencies of the net=
work.
244	 =C2=A0 Local_decap is the name of the adjacency to decapsulate BIER-TE
245	 =C2=A0 packets and pass their payload to higher layer processing.

[nit] s/act as ingress/act as an ingress

[nit] s/egress BFR/egress BFRs


247	 =C2=A0 Assume a packet from BFR1 should be sent via BFR4 to BFR6. =C2=
=A0This
248	 =C2=A0 requires a bitstring (p2,p8,p10,p12). =C2=A0When this packet is=
 examined
249	 =C2=A0 by BIER-TE on BFR1, the only BitPosition from the bitstring tha=
t is
250	 =C2=A0 also set in the BIFT is p2. =C2=A0This will cause BFR1 to send =
the only
251	 =C2=A0 copy of the packet to BFR2. =C2=A0Similarly, BFR2 will forward =
to BFR4
252	 =C2=A0 because of p8, BFR4 to BFR5 because of p10 and BFR5 to BFR6 bec=
ause
253	 =C2=A0 of p12. p12 also makes BFR6 receive and decapsulate the packet.

[minor] =C2=A71 says that "BPs are normally also reset upon forwarding to
avoid duplicates and loops." =C2=A0Doesn't that mean that BFR6 won't
receive p12 set?


...
271	 =C2=A0 The following picture shows a modified example, in which Rtr2 a=
nd
272	 =C2=A0 Rtr5 are assumed not to support BIER-TE, so traffic has to be u=
nicast
273	 =C2=A0 encapsulated across them. =C2=A0Unicast tunneling of BIER-TE pa=
ckets can
274	 =C2=A0 leverage any feasible mechanism such as MPLS or IP, these
275	 =C2=A0 encapsulations are out of scope of this document. =C2=A0To emph=
asize non-
276	 =C2=A0 native forwarding of BIER-TE packets, these adjacencies are cal=
led
277	 =C2=A0 "forward_routed", but otherwise there is no difference in their
278	 =C2=A0 processing over the aforementioned "forward_connected" adjacenc=
ies.

[major] "leverage any feasible mechanism such as MPLS or IP, these
encapsulations are out of scope of this document."

I can see why the encapsulation is outside the scope of this document,
but there are basic considerations (for example, that the
encapsulation is able to indicate that the payload is a BIER-TE packet
--- as explained in rfc8279/=C2=A76.9 for BIER) that should be mentioned
(or referenced) here.


...
322	1.2. =C2=A0BIER-TE Topology and adjacencies
...
329	 =C2=A0 The BIER-TE Topology consists of the BIFT of all the BFR and ca=
n also
330	 =C2=A0 be expressed as a directed graph where the edges are the adjace=
ncies
331	 =C2=A0 between the BFR labelled with the BP used for the adjacency.
332	 =C2=A0 Adjacencies are naturally unidirectional. =C2=A0BP can be reuse=
d across
333	 =C2=A0 multiple adjacencies as long as this does not lead to undesired
334	 =C2=A0 duplicates or loops as explained further down in the text.

[nit] s/BIFT of all the BFR/BIFTs of all the BFRs

[nit] s/between the BFR/between the BFRs


336	 =C2=A0 If the BIER-TE topology represents the underlying (layer 2) top=
ology
337	 =C2=A0 of the network, this is called "native" BIER-TE as shown in the=
 first
338	 =C2=A0 example. =C2=A0This can be freely mixed with "overlay" BIER-TE,=
 in
339	 =C2=A0 "forward_routed" adjacencies are used.

[nit] s/This/This type of topology (?)


341	1.3. =C2=A0Comparison with BIER

343	 =C2=A0 The key differences over BIER are:

[minor] s/over/with respect to


...
351	 =C2=A0 o =C2=A0BIER-TE in each BFR has no routing table but only a BIE=
R-TE
352	 =C2=A0 =C2=A0 =C2=A0Forwarding Table (BIFT) indexed by SI:BitPosition =
and populated
353	 =C2=A0 =C2=A0 =C2=A0with only those adjacencies to which the BFR shoul=
d replicate
354	 =C2=A0 =C2=A0 =C2=A0packets to.

[minor] "BIER-TE Forwarding Table (BIFT)" =C2=A0Is a BIFT a "BIER-TE
Forwarding Table" or a "Bit Index Forwarding Table" (rfc8279)? =C2=A0Please
don't overload the meaning.


...
358	 =C2=A0 BIER-TE forwarding does not require/use the BFIR-ID. =C2=A0The =
BFIR-ID can
359	 =C2=A0 still be useful though for coordinated BFIR/BFER functions, suc=
h as
360	 =C2=A0 the context for upstream assigned labels for MPLS payloads in M=
VPN
361	 =C2=A0 over BIER-TE.

[minor] s/BFIR-ID/BFIR-id/g
That is the syntax from rfc8296.


[major] "BIER-TE forwarding does not require/use the BFIR-ID." =C2=A0If the
rfc8296 encapsulation is used, the BFIR-id is a required field.

I understand that the BFIR-IDs are not used in the same way, but they
are still required. =C2=A0The last paragraph (below) talks about
assignment, which contradicts the not-required characterization here.
I think the issue is with using "required"...


[minor] "The BFIR-ID can still be useful..." =C2=A0The utility is just an
example, right? =C2=A0 Because the paragraph started by stating that
BFIR-IDs are not required/used, the second sentence sounds out of
place and potentially confusing: there's no further mention in this
document, no reference...


...
366	 =C2=A0 If the BIER-TE domain is not running full BIER or does not want=
 to
367	 =C2=A0 reduce the need to allocate bits in BIER bitstrings for BFIR-ID
368	 =C2=A0 values, then the allocation of BFIR-ID values in BIER-TE packet=
s can
369	 =C2=A0 be done through other mechanisms outside the scope of this docu=
ment,
370	 =C2=A0 as long as this is appropriately agreed upon between all BFIR/B=
FER.

[] "reduce the need to allocate bits in BIER bitstrings for BFIR-ID
values" =C2=A0What does this phrase mean?


[] Related to the other comments (above) about the BFIR-id, this
paragraph indicates that they are needed.


[minor] "allocation of BFIR-ID values... can be done through other
mechanisms outside the scope of this document" =C2=A0 Ok -- but =C2=A77.4 d=
eals
specifically with the assignment of BFR-ids. =C2=A0I guess that pointing at
=C2=A77.4 as an example/set of considerations is ok.


372	1.4. =C2=A0Requirements Language

374	 =C2=A0 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL N=
OT",
375	 =C2=A0 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in=
 this
376	 =C2=A0 document are to be interpreted as described in RFC 2119 [RFC211=
9].

[major] Use the rfc8174 template.


378	2. =C2=A0Components

380	 =C2=A0 End to end BIER-TE operations consists of four mayor components=
: The
381	 =C2=A0 "Multicast Flow Overlay", the "BIER-TE control plane" consistin=
g of
382	 =C2=A0 the "BIER-TE Controller" and its signaling channels to the BFR,=
 the
383	 =C2=A0 "Routing Underlay" and the "BIER-TE forwarding layer". =C2=A0Th=
e Bier-TE
384	 =C2=A0 Controller is the new architectural component in BIER-TE compar=
ed to
385	 =C2=A0 BIER.

[nit] s/Bier/BIER


387	 =C2=A0 =C2=A0 =C2=A0Picture 2: Components of BIER-TE

[nit] The figure number/legend is also below the figure. =C2=A0No need for =
this text.


...
417	2.2. =C2=A0The BIER-TE Controller

419	 =C2=A0 The BIER-TE Controller is representing the control plane of BIE=
R-TE.
420	 =C2=A0 It communicates two sets of information with BFRs:

[nit] s/is representing/represents

[nit] s/with/to


422	 =C2=A0 During initial provisioning or modifications of the network top=
ology,
423	 =C2=A0 the BIER-TE Controller discovers the network topology and creat=
es the
424	 =C2=A0 BIER-TE topology from it: determine which adjacencies are requi=
red/
425	 =C2=A0 desired and assign BitPositions to them. =C2=A0Then it signals =
the
426	 =C2=A0 resulting of BitPositions and their adjacencies to each BFR to =
set up
427	 =C2=A0 their BIER-TE BIFTs.

[major] "BIER-TE Controller discovers the network topology and creates
the BIER-TE topology from it" =C2=A0 How? =C2=A0There are two steps here:
discovery of the network topology and creating the BIER-TE topology.


[nit] s/resulting of BitPositions/resulting BitPositions


...
432	 =C2=A0 Communications between the BIER-TE Controller and BFRs is ideal=
ly via
433	 =C2=A0 standardized protocols and data-models such as Netconf/Restconf=
/Yang.
434	 =C2=A0 This is currently outside the scope of this document. =C2=A0Ven=
dor-
435	 =C2=A0 specific CLI on the BFRs is also a possible stopgap option (as =
in
436	 =C2=A0 many other SDN solutions lacking definition of standardized dat=
a
437	 =C2=A0 model).

[major] Even though there is explicit mention of data models and the
use of specific protocols, this document doesn't dictate a specific
configuration methodology -- just like BIER (rfc8279/=C2=A77.1). =C2=A0 Thi=
s is
ok.

PCE is not mentioned as a possibility. =C2=A0I point this out simply
because there are 2 PCE-related active individual drafts
(draft-chen-pce-bier, draft-chen-pce-bier-te-path), but no active YANG
work (I know the drafts are expired).

My suggestion is to avoid mentioning specifics and provide a statement
similar to rfc8279 so that the choice of control protocol is left
open.


[minor] s/currently outside the scope/outside the scope/g


[minor] s/a possible stopgap option/an option


[nit] s/of standardized/of a standardized


...
446	2.2.1. =C2=A0Assignment of BitPositions to adjacencies of the network
447	 =C2=A0 =C2=A0 =C2=A0 =C2=A0topology

449	 =C2=A0 The BIER-TE Controller tracks the BFR topology of the BIER-TE d=
omain.
450	 =C2=A0 It determines what adjacencies require BitPositions so that BIE=
R-TE
451	 =C2=A0 explicit paths can be built through them as desired by operator
452	 =C2=A0 policy.

[major] "BIER-TE Controller tracks the BFR topology" =C2=A0How does it do t=
hat?


...
480	2.2.4. =C2=A0Link/Node Failures and Recovery

482	 =C2=A0 When link or nodes fail or recover in the topology, BIER-TE can
483	 =C2=A0 quickly respond with the optional FRR procedures described in [=
I-
484	 =C2=A0 D.eckert-bier-te-frr]. =C2=A0It can also more slowly react by
485	 =C2=A0 recalculating the BitStrings of affected multicast flows. =C2=
=A0This
486	 =C2=A0 reaction is slower than the FRR procedure because the BIER-TE
487	 =C2=A0 Controller needs to receive link/node up/down indications,
488	 =C2=A0 recalculate the desired BitStrings and push them down into the =
BFIRs.
489	 =C2=A0 With FRR, this is all performed locally on a BFR receiving the
490	 =C2=A0 adjacency up/down notification.

[minor] There's no reference for I-D.eckert-bier-te-frr.


...
505	2.4. =C2=A0The Routing Underlay
...
515	 =C2=A0 BIER relies on the routing underlay to calculate paths towards =
BFER
516	 =C2=A0 and derive next-hop BFR adjacencies for those paths. =C2=A0This=
 commonly
517	 =C2=A0 relies on BIER specific extensions to the routing protocols of =
the
518	 =C2=A0 routing underlay but may also be established by a controller. =
=C2=A0In
519	 =C2=A0 BIER-TE, the next-hops of a packet are determined by the bitstr=
ing
520	 =C2=A0 through the BIER-TE Controller established adjacencies on the B=
FR for
521	 =C2=A0 the BPs of the bitsring. =C2=A0There is thus no need for BFER s=
pecific
522	 =C2=A0 routing underlay extensions to forward BIER packets with BIER-T=
E
523	 =C2=A0 semantics.

[nit] s/towards BFER/towards BFERs


[major] Just to make sure I'm understanding. =C2=A0In BIER-TE there is no
need to learn the BP's because they are all locally significant, and,
more importantly, defined by the controller. =C2=A0Is that it? =C2=A0 =C2=
=A0[It makes
sense to me, just asking because I see several BIER-TE drafts related
to IGP extensions in the datatracker.]


...
539	2.5. =C2=A0Traffic Engineering Considerations
...
548	 =C2=A0 Policy decisions are made within the BIER-TE control plane, i.e=
.,
549	 =C2=A0 within BIER-TE Controllers. =C2=A0Controllers use policy when c=
omposing
550	 =C2=A0 BitStrings (BFR flow state) and BFR BIFT state. =C2=A0The mappi=
ng of user/
551	 =C2=A0 IP traffic to specific BitStrings/BIER-TE flows is made based o=
n
552	 =C2=A0 policy. =C2=A0The specifics details of BIER-TE policies and how=
 a
553	 =C2=A0 controller uses such are out of scope of this document.

[] "composing BitStrings (BFR flow state)" =C2=A0It feels like you really
want to say something more here, but the mention of "BFR flow state"
is confusing without other context. =C2=A0Please elaborate or take the
phrase out.


[nit] s/specifics details/specific details


[nit] s/uses such/uses them

555	 =C2=A0 Path steering is supported via the definition of a BitString.
556	 =C2=A0 BitStrings used in BIER-TE are composed based on policy and res=
ource
557	 =C2=A0 management considerations. =C2=A0When composing BIER-TE BitStri=
ngs, a
558	 =C2=A0 Controller MUST take into account the resources available at ea=
ch BFR
559	 =C2=A0 and for each BP when it is providing congestion loss free servi=
ces
560	 =C2=A0 such as Rate Controlled Service Disciplines [RCSD94]. =C2=A0Res=
ource
561	 =C2=A0 availability could be provided for example via routing protocol
562	 =C2=A0 information, but may also be obtained via a BIER-TE control pro=
tocol
563	 =C2=A0 such as Netconf or any other protocol commonly used by a PCE to
564	 =C2=A0 understand the resources of the network it operates on. =C2=A0T=
he resource
565	 =C2=A0 usage of the BIER-TE traffic admitted by the BIER-TE controller=
 can
566	 =C2=A0 be solely tracked on the BIER-TE Controller based on local acco=
unting
567	 =C2=A0 as long as no forward_routed adjacencies are used (see Section =
3.2.1
568	 =C2=A0 for the definition of forward_routed adjacencies). =C2=A0When
569	 =C2=A0 forward_routed adjacencies are used, the paths selected by the
570	 =C2=A0 underlying routing protocol need to be tracked as well.

[major] "Controller MUST take into account..." =C2=A0If the specific
details of how a controller uses a policy are out of scope, how can
then also be normatively required? =C2=A0 s/MUST/must


[minor] "congestion loss free services" =C2=A0This is the only time when a
specific type of service is called out. =C2=A0Is it necessary to do so? =C2=
=A0Is
this the only type of traffic that would be traffic engineered?
Should others be specifically mentioned elsewhere? =C2=A0 I don't think so,
just asking...


[minor] "used by a PCE" =C2=A0This is also the only place where a PCE is
specifically mentioned. =C2=A0In other places a generic "BIER-TE
controller" is used -- please be consistent. =C2=A0More importantly, =C2=A7=
2.2
doesn't even come close to mentioning the possibility of using PCEP as
the BIER-TE control protocol. =C2=A0 There's nothing wrong with not
mentioning PCE/PCEP there, it just feels sloppy that many options are
mentioned but not a single one required in a standards track document.


572	 =C2=A0 Resource management has implications on the forwarding plane be=
yond
573	 =C2=A0 the BIER-TE defined steering of packets. =C2=A0This includes al=
location of
574	 =C2=A0 buffers to guarantee the worst case requirements of admitted RC=
SD
575	 =C2=A0 trafic and potential policing and/or rate-shaping mechanisms,
576	 =C2=A0 typically done via various forms of queuing. =C2=A0This level o=
f resource
577	 =C2=A0 control, while optional, is important in networks that wish to
578	 =C2=A0 support congestion management policies to control or regulate t=
he
579	 =C2=A0 offered traffic to deliver different levels of service and alle=
viate
580	 =C2=A0 congestion problems, or those networks that wish to control lat=
encies
581	 =C2=A0 experienced by specific traffic flows.

[nit] s/trafic/traffic


...
585	3.1. =C2=A0The Bit Index Forwarding Table (BIFT)
...
592	 =C2=A0 BIER-TE can support multiple subdomains like BIER. =C2=A0Each o=
ne with a
593	 =C2=A0 separate BIFT

[minor] s/subdomains/sub-domains/g =C2=A0That is how rfc8279 uses the term.

[] Suggestion>
=C2=A0 =C2=A0Like BIER, BIER-TE can support multiple sub-domains, each with=
 a separate
=C2=A0 =C2=A0BIFT.


595	 =C2=A0 In the BIER architecture, indices into the BIFT are explained t=
o be
596	 =C2=A0 both BFR-id and SI:BitString (BitPosition). =C2=A0This is becau=
se there is
597	 =C2=A0 a 1:1 relationship between BFR-id and SI:BitString - every bit =
in
598	 =C2=A0 every SI is/can be assigned to a BFIR/BFER. =C2=A0In BIER-TE th=
ere are
599	 =C2=A0 more bits used in each BitString than there are BFIR/BFER assig=
ned to
600	 =C2=A0 the bitstring. =C2=A0This is because of the bits required to ex=
press the
601	 =C2=A0 engineered path through the topology. =C2=A0The BIER-TE forward=
ing
602	 =C2=A0 definitions do therefore not use the term BFR-id at all. =C2=A0=
Instead,
603	 =C2=A0 BFR-ids are only used as required by routing underlay, flow ove=
rlay
604	 =C2=A0 of BIER headers. =C2=A0Please refer to Section 7 for explanatio=
ns how to
605	 =C2=A0 deal with SI, subdomains and BFR-id in BIER-TE.

[minor] "SI:BitString (BitPosition)" =C2=A0The BitString is the collection
of all BitPositions -- it is not clear to me what you're trying to
indicate here (which is not in rfc8279).


[nit] "in each BitString...assigned to the bitstring" =C2=A0Is there a
difference between BitString and bitstring? =C2=A0Maybe you meant bit
string in the second case.


[minor] "In BIER-TE there are more bits used in each BitString than
there are BFIR/BFER assigned to the bitstring." =C2=A0BIER-TE doesn't
assign bits to the BFERs. =C2=A0I'm not sure what you're trying to say
here.


[nit] s/by routing underlay/by the routing underlay


[?] "flow overlay of BIER headers" =C2=A0?? =C2=A0 I'm assuming you mean th=
e
Multicast Flow Overlay (still don't understand the BIER headers part).
=C2=A0 Please be consistent in the naming: s/flow overlay/Multicast Flow
Overlay/g


607	 =C2=A0 =C2=A0 --------------------------------------------------------=
----------
608	 =C2=A0 =C2=A0 | Index: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| =C2=A0Adjac=
encies: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|
609	 =C2=A0 =C2=A0 | SI:BitPosition =C2=A0| =C2=A0<empty> or one or more pe=
r entry =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|
610	 =C2=A0 =C2=A0 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
611	 =C2=A0 =C2=A0 | 0:1 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | =C2=A0=
forward_connected(interface,neighbor{,DNR}) |
612	 =C2=A0 =C2=A0 --------------------------------------------------------=
----------
613	 =C2=A0 =C2=A0 | 0:2 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | =C2=A0=
forward_connected(interface,neighbor{,DNR}) |
614	 =C2=A0 =C2=A0 | =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 | =C2=A0forward_connected(interface,neighbor{,DNR}) |
615	 =C2=A0 =C2=A0 --------------------------------------------------------=
----------
616	 =C2=A0 =C2=A0 | 0:3 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | =C2=A0=
local_decap({VRF}) =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|
617	 =C2=A0 =C2=A0 --------------------------------------------------------=
----------
618	 =C2=A0 =C2=A0 | 0:4 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | =C2=A0=
forward_routed({VRF,}l3-neighbor) =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |
619	 =C2=A0 =C2=A0 --------------------------------------------------------=
----------
620	 =C2=A0 =C2=A0 | 0:5 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | =C2=A0=
<empty> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |
621	 =C2=A0 =C2=A0 --------------------------------------------------------=
----------
622	 =C2=A0 =C2=A0 | 0:6 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | =C2=A0=
ECMP({adjacency1,...adjacencyN}, seed) =C2=A0 =C2=A0 =C2=A0|
623	 =C2=A0 =C2=A0 --------------------------------------------------------=
----------
624	 =C2=A0 =C2=A0 ...
625	 =C2=A0 =C2=A0 | BitStringLength | =C2=A0... =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |
626	 =C2=A0 =C2=A0 --------------------------------------------------------=
----------
627	 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0Bit Index Forwarding Table

629	 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0Figure 4: BIFT adjacencies

[] This table isn't referred to or explicitly explained anywhere. =C2=A0The
following sections seem to cover some of the entries, but no pointer
back to it.


...
635	 =C2=A0 Adjacencies for the same BP when populated in more than one BFR=
 by
636	 =C2=A0 the BIER-TE Controller does not have to have the same adjacenci=
es.
637	 =C2=A0 This is up to the BIER-TE Controller. =C2=A0BPs for p2p links a=
re one case
638	 =C2=A0 (see below).

[nit] "Adjacencies ...does not have to have the same adjacencies."
Maybe there's a better way to avoid redundancy when explaining.


640	 =C2=A0 {VRF}indicates the Virtual Routing and Forwarding context into =
which
641	 =C2=A0 the BIER payload is to be delivered. =C2=A0This is optional and=
 depends on
642	 =C2=A0 the multicast flow overlay.

[nit] s/{VRF}indicates/{VRF} indicates


...
646	3.2.1. =C2=A0Forward Connected

648	 =C2=A0 A "forward_connected" adjacency is towards a directly connected=
 BFR
649	 =C2=A0 neighbor using an interface address of that BFR on the connecti=
ng
650	 =C2=A0 interface. =C2=A0A forward_connected adjacency does not route p=
ackets but
651	 =C2=A0 only L2 forwards them to the neighbor.

[] Does this imply that the non-MPLS encapsulation from rfc8296 is used?


653	 =C2=A0 Packets sent to an adjacency with "DoNotReset" (DNR) set in the=
 BIFT
654	 =C2=A0 will not have the BitPosition for that adjacency reset when the=
 BFR
655	 =C2=A0 creates a copy for it. =C2=A0The BitPosition will still be rese=
t for
656	 =C2=A0 copies of the packet made towards other adjacencies. =C2=A0This=
 can be
657	 =C2=A0 used for example in ring topologies as explained below.

[] I would prefer to see some normative language in this part of the
specification: "DNR...MUST NOT reset the BPs.." =C2=A0 ??


...
674	3.2.3. =C2=A0ECMP

676	 =C2=A0 The ECMP mechanisms in BIER are tied to the BIER BIFT and are
677	 =C2=A0 therefore not directly useable with BIER-TE. =C2=A0The followin=
g
678	 =C2=A0 procedures describe ECMP for BIER-TE that we consider to be
679	 =C2=A0 lightweight but also well manageable. =C2=A0It leverages the ex=
isting
680	 =C2=A0 entropy parameter in the BIER header to keep packets of the flo=
ws on
681	 =C2=A0 the same path and it introduces a "seed" parameter to allow for
682	 =C2=A0 traffic flows to be polarized or randomized across multiple hop=
s.

[minor] "The following procedures describe ECMP..." =C2=A0Which procedures?
=C2=A0The paragraph below just has one instruction ("must select the same
adjacency..."), but I wouldn't call that a procedure (much less
procedures). =C2=A0Is it possible to at least illustrate?


[style nit] "we consider" =C2=A0Don't write in first person. =C2=A0s/.../is=
 considered


684	 =C2=A0 An "Equal Cost Multipath" (ECMP) adjacency has a list of two or=
 more
685	 =C2=A0 adjacencies included in it. =C2=A0It copies the BIER-TE to one =
of those
686	 =C2=A0 adjacencies based on the ECMP hash calculation. =C2=A0The BIER-=
TE ECMP
687	 =C2=A0 hash algorithm must select the same adjacency from that list fo=
r all
688	 =C2=A0 packets with the same "entropy" value in the BIER-TE header if =
the
689	 =C2=A0 same number of adjacencies and same seed are given as parameter=
s.
690	 =C2=A0 Further use of the seed parameter is explained below.

[minor] s/copies the BIER-TE/copies the (BIER-TE) traffic


[minor] "Further use of the seed parameter is explained below." =C2=A0Add a
reference to =C2=A74.7.


692	3.2.4. =C2=A0Local Decap

[minor] s/Local Decap/Local Decapsulation


694	 =C2=A0 A "local_decap" adjacency passes a copy of the payload of the B=
IER-TE
695	 =C2=A0 packet to the packets NextProto within the BFR (IPv4/IPv6,
696	 =C2=A0 Ethernet,...). =C2=A0A local_decap adjacency turns the BFR into=
 a BFER for
697	 =C2=A0 matching packets. =C2=A0Local_decap adjacencies require the BFE=
R to
698	 =C2=A0 support routing or switching for NextProto to determine how to
699	 =C2=A0 further process the packet.

[major] "NextProto" =C2=A0The name of this field in rfc8296 is simply
"Proto", or you might want to call it "Next Protocol" with a pointer
to the header (so it is not confused with the next protocol at other
layers).


701	3.3. =C2=A0Encapsulation considerations

703	 =C2=A0 Specifications for BIER-TE encapsulation are outside the scope =
of
704	 =C2=A0 this document. =C2=A0This section gives explanations and guidel=
ines.

[major] I've been assuming all along that the rfc8296 encapsulation is
used. =C2=A0In fact, the previous section points at a field there. =C2=A0Th=
at
doesn't seem to be "out of scope". =C2=A0What am I missing?


...
720	 =C2=A0 "forward_routed" requires an encapsulation permitting to unicas=
t
721	 =C2=A0 BIER-TE packets to a specific interface address on a target BFR=
.
722	 =C2=A0 With MPLS encapsulation, this can simply be done via a label st=
ack
723	 =C2=A0 with that addresses label as the top label - followed by the la=
bel
724	 =C2=A0 assigned to (SI,subdomain) - and if necessary (see above) BIER-=
TE.
725	 =C2=A0 With non-MPLS encapsulation, some form of IP encapsulation woul=
d be
726	 =C2=A0 required (for example IP/GRE).

[minor] "and if necessary (see above) BIER-TE" =C2=A0I guess you mean a
"BIER-TE label", right?


...
733	3.4. =C2=A0Basic BIER-TE Forwarding Example

735	 =C2=A0 [RFC Editor: remove this section.]

737	 =C2=A0 THIS SECTION TO BE REMOVED IN RFC BECAUSE IT WAS SUPERCEEDED BY
738	 =C2=A0 SECTION 1.1 EXAMPLE - UNLESS REVIEWERS CHIME IN AND EXPRESS DES=
IRE TO
739	 =C2=A0 KEEP THIS ADDITIONAL EXAMPLE SECTION.

[] I don't mind the extra example.


741	 =C2=A0 Step by step example of basic BIER-TE forwarding. =C2=A0This do=
es not use
742	 =C2=A0 ECMP or forward_routed adjacencies nor does it try to minimize =
the
743	 =C2=A0 number of required BitPositions for the topology.

[nit] s/This does not/This example does not


...
775	 =C2=A0 =C2=A0 =C2=A0BIFT BFIR2:
776	 =C2=A0 =C2=A0 =C2=A0 =C2=A0p13: local_decap()
777	 =C2=A0 =C2=A0 =C2=A0 =C2=A0 p2: forward_connected(BFR3)

[] Shouldn't BFIR2 also know about p14? =C2=A0I'm assuming that LAN1 is
running IGMP/MLD and that maybe BFIR2 is the DR.


[nit] s/local_decap()/local_decap/g =C2=A0 To match how the rest of the
document uses local_decap.


...
815	 =C2=A0 BFR3 sees a BitString of p5,p7,p8,p10,p11,p12. =C2=A0It is only=
 interested
816	 =C2=A0 in p1,p7,p8. =C2=A0It creates a copy of the packet to BFER1 (du=
e to p7)
817	 =C2=A0 and one to BFR4 (due to p8). =C2=A0It resets p7, p8 before send=
ing.

[] There's no p1 in the BitString. =C2=A0I guess you mean that it is
"interested" in p1 because that is in the BFIT. =C2=A0The terminology is a
little confusing because the BitString is presented first. =C2=A0Perhaps
reword as something like "BFR3 only has p1, p7 and p8 in it's BIFT, so
it will only..."


819	 =C2=A0 BFER1 sees a BitString of p5,p10,p11,p12. =C2=A0It is only inte=
rested in
820	 =C2=A0 p6,p7,p8,p11 and therefore considers only p11. p11 is a "local_=
decap"
821	 =C2=A0 adjacency installed by the BIER-TE Controller because BFER1 sho=
uld
822	 =C2=A0 pass packets to IP multicast. =C2=A0The local_decap adjacency i=
nstructs
823	 =C2=A0 BFER1 to create a copy, decapsulate it from the BIER header and=
 pass
824	 =C2=A0 it on to the NextProtocol, in this example IP multicast. =C2=A0=
IP
825	 =C2=A0 multicast will then forward the packet out to LAN2 because it d=
id
826	 =C2=A0 receive PIM or IGMP joins on LAN2 for the traffic.

[minor] s/p6,p7,p8,p11/p6,p8,p11


[] The second and third sentences are redundant.


...
830	3.5. =C2=A0Forwarding comparison with BIER

832	 =C2=A0 Forwarding of BIER-TE is designed to allow common forwarding ha=
rdware
833	 =C2=A0 with BIER. =C2=A0In fact, one of the main goals of this documen=
t is to
834	 =C2=A0 encourage the building of forwarding hardware that can not only
835	 =C2=A0 support BIER, but also BIER-TE - to allow experimentation with =
BIER-
836	 =C2=A0 TE and support building of BIER-TE control plane code.

[major] "main goals of this document...allow experimentation with
BIER-TE and support building of BIER-TE control plane code."

Experimentation...build control plane!?!? =C2=A0 I know this document was
tagged as Experimental before -- maybe this text is just a leftover.
???


838	 =C2=A0 The pseudocode in Section 6 shows how existing BIER/BIFT forwar=
ding
839	 =C2=A0 can be amended to support basic BIER-TE forwarding, by using BI=
ER
840	 =C2=A0 BIFT's F-BM. =C2=A0Only the masking of bits due to avoid duplic=
ates must
841	 =C2=A0 be skipped when forwarding is for BIER-TE.

[major] What is "basic BIER-TE forwarding"? =C2=A0I'm guessing it is a
sub-set of what is discussed in this document, but which sub-set? =C2=A0Is
the reader to assume that "BIER-TE forwarding" (without "basic") is
different?

Note that =C2=A76 mixes the terms when introducing the pseudocode: =C2=A0"T=
he
following simplified pseudocode for BIER-TE forwarding...to support
basic BIER-TE forwarding."


[minor] Please expand F-BM on first mention.


[] "Only the masking of bits due to avoid duplicates must be skipped
when forwarding is for BIER-TE." =C2=A0I'm having a hard time parsing this
sentence.


843	 =C2=A0 Whether to use BIER or BIER-TE forwarding can simply be a confi=
gured
844	 =C2=A0 choice per subdomain and accordingly be set up by a BIER-TE
845	 =C2=A0 Controller. =C2=A0The BIER packet encapsulation [RFC8296] too c=
an be
846	 =C2=A0 reused without changes except that the currently defined BIER-T=
E ECMP
847	 =C2=A0 adjacency does not leverage the entropy field so that field wou=
ld be
848	 =C2=A0 unused when BIER-TE forwarding is used.

[major] "BIER-TE ECMP adjacency does not leverage the entropy field"
=C2=A73.2.3 says the opposite.


850	3.6. =C2=A0Requirements

[] I made the comments in this section as I was reading and (mostly)
before realizing that it is here where you try to make the distinction
between "basic BIER-TE forwarding" and "BIER-TE forwarding". =C2=A0Please
see some comments at the end related to the distinction.


852	 =C2=A0 Basic BIER-TE forwarding MUST support to configure Subdomains t=
o use
853	 =C2=A0 basic BIER-TE forwarding rules (instead of BIER). =C2=A0With ba=
sic BIER-TE
854	 =C2=A0 forwarding, every bit MUST support to have zero or one adjacenc=
y. =C2=A0It
855	 =C2=A0 MUST support the adjacency types forward_connected without DNR =
flag,
856	 =C2=A0 forward_routed and local_decap. =C2=A0All other BIER-TE forward=
ing
857	 =C2=A0 features are optional. =C2=A0These basic BIER-TE requirements m=
ake BIER-TE
858	 =C2=A0 forwarding exactly the same as BIER forwarding with the excepti=
on of
859	 =C2=A0 skipping the aforementioned F-BM masking on egress.

[minor] s/support to configure/support configuring


[nit] "Basic BIER-TE forwarding MUST support to configure Subdomains
to use basic BIER-TE forwarding rules (instead of BIER)." =C2=A0There's a
circular reference in basic BIER-TE supporting something to use basic
BIER-TE...


[major] "...every bit MUST support to have zero or one adjacency." =C2=A0It
sounds like you're saying that each bit is required to represent at
most one adjacency, or nothing. =C2=A0This requirement forbids reusing the
bits, or associating them with more than one adjacency:

This is the same thing that has been described before, for example:

=C2=A0 =C2=A0=C2=A71.2: "BP can be reused across multiple adjacencies..."

=C2=A0 =C2=A0=C2=A71.3: "every BitPosition...indicates one or more adjacenc=
ies"

=C2=A0 =C2=A0=C2=A73.2.3: "An "Equal Cost Multipath" (ECMP) adjacency has a=
 list of two or
=C2=A0 =C2=A0more adjacencies included in it."

Presumably the statement in this section is still true for a local
BFR, but putting it in the same paragraph as the initial requirement
related to a whole sub-domain creates confusion, at best.


[major] "All other BIER-TE forwarding features are optional." =C2=A0Are
optional for basic BIER-TE forwarding? =C2=A0 If so, then what
distinguishes the two modes?


[minor] Mixing of terms: "These basic BIER-TE requirements make
BIER-TE forwarding..."


[minor] "aforementioned F-BM masking on egress" =C2=A0 Maybe this is what I
didn't understand in =C2=A73.5, but I didn't see any mention of egress.


861	 =C2=A0 BIER-TE forwarding SHOULD support the DNR flag, as this is high=
ly
862	 =C2=A0 useful to save bits in rings (see Section 4.6).

[major] "SHOULD support the DNR flag" =C2=A0When is it ok for BIER-TE
forwarding to not support the DNR flag? =C2=A0IOW, why is this a
recommendation and not a requirement?


864	 =C2=A0 BIER-TE forwarding MAY support more than one adjacency on a bit=
 and
865	 =C2=A0 ECMP adjacencies. =C2=A0The importance of ECMP adjacencies is u=
nclear when
866	 =C2=A0 traffic steering is used because it may be more desirable to
867	 =C2=A0 explicitly steer traffic across non-ECMP paths to make per-path
868	 =C2=A0 traffic calculation easier for BIER-TE Controllers. =C2=A0Havin=
g more than
869	 =C2=A0 one adjacency for a bit allows further savings of bits in hub&s=
poke
870	 =C2=A0 scenarios, but unlike rings it is less "natural" to flood traff=
ic
871	 =C2=A0 across multiple links unconditional. =C2=A0Both ECMP and multip=
le
872	 =C2=A0 adjacencies are forwarding plane features that should be possib=
le to
873	 =C2=A0 support later when needed as they do not impact the basic BIER-=
TE
874	 =C2=A0 replication loop. =C2=A0This is true because there is no inter-=
copy
875	 =C2=A0 dependency through resetting of F-BM as in BIER.

[major] "BIER-TE forwarding MAY support more than one adjacency..."
This text makes this support optional for both basic BIER-TE
forwarding and BIER-TE forwarding.


[major] "The importance of ECMP adjacencies is unclear..." =C2=A0If
unclear, why is it specified? =C2=A0What are the operational considerations
that should be taken into account when deciding to use ECMP
adjacencies (if supported)?


[] "further savings of bits in hub&spoke scenarios, but unlike rings"
This sounds like a good start for operational considerations related
to how to save bits.


[] "it is less "natural" to flood traffic across multiple links"
Hmmm. I thought it was "natural" for multicast to forward traffic
across multiple links. =C2=A0Note that his is a specification --
characterizing a behavior should be specific.


[nit] s/links unconditional/links unconditionally


[] "features that should be possible to support later when needed"
Again, great material for operational considerations. =C2=A0When are these
features needed?


[minor] "basic BIER-TE replication loop" =C2=A0 Using "loop" is not the
best idea when talking about forwarding. =C2=A0What is the "replication
loop" anyway??


[] "...there is no inter-copy dependency through resetting of F-BM as
in BIER." =C2=A0You lost me again. =C2=A0BTW, I couldn't find a mention of
resetting (anything!) in rfc8279/rfc8296.


[major] After reading this section several times, I think that using
the "basic" terminology introduces significant confusion, especially
because there's no way to distinguish whether a node only supports
"basic" or not. =C2=A0Please define the requirements as required for the
"basic" flavor, and recommended/optional for the complete solution.


877	4. =C2=A0BIER-TE Controller BitPosition Assignments
...
883	 =C2=A0 Because the size of the BitString is limiting the size of the B=
IER-TE
884	 =C2=A0 domain, many of the options described exist to support larger
885	 =C2=A0 topologies with fewer BitPositions (4.1, 4.3, 4.4, 4.5, 4.6, 4.=
7,
886	 =C2=A0 4.8).

[nit] s/is limiting the size/limits the size


888	4.1. =C2=A0P2P Links

890	 =C2=A0 Each P2p link in the BIER-TE domain is assigned one unique
891	 =C2=A0 BitPosition with a forward_connected adjacency pointing to the
892	 =C2=A0 neighbor on the p2p link.

[nit] s/P2p/P2P


[minor] You mean the same BP for both directions, right? =C2=A0It might be
good to clarify.


...
899	4.3. =C2=A0Leaf BFERs
...
912	 =C2=A0 Leaf BFERs are BFERs where incoming BIER-TE packets never need =
to be
913	 =C2=A0 forwarded to another BFR but are only sent to the BFER to exit =
the
914	 =C2=A0 BIER-TE domain. =C2=A0For example, in networks where PEs are sp=
okes
915	 =C2=A0 connected to P routers, those PEs are Leaf BFERs unless there i=
s a
916	 =C2=A0 U-turn between two PEs. =C2=A0Consider how redundant disjoint t=
raffic can
917	 =C2=A0 reach BFER1/BFER2 in above picture: When BFER1/BFER2 are Non-Le=
af
918	 =C2=A0 BFER as shown on the right hand side, one traffic copy would be
919	 =C2=A0 forwarded to BFER1 from BFR1, but the other one could only reac=
h
920	 =C2=A0 BFER1 via BFER2, which makes BFER2 a non-Leaf BFER. =C2=A0Likew=
ise BFER1
921	 =C2=A0 is a non-Leaf BFER when forwarding traffic to BFER2.

[minor] Please expand P/PE on first use.


[nit] s/Leaf BFERs are BFERs/A leaf BFER is one


[nit] s/in above picture/in Figure 8


[minor] s/U-turn between two PEs/U-turn


923	 =C2=A0 Note that the BFERs in the left hand picture are only guarantee=
d to
924	 =C2=A0 be leaf-BFER by fitting routing configuration that prohibits tr=
ansit
925	 =C2=A0 traffic to pass through the BFERs, which is commonly applied in=
 these
926	 =C2=A0 topologies.

[minor] This paragraph continues discussion about the left hand side
of the picture -- this description started above and introduced the
term "U-turn". =C2=A0Consider grouping the common descriptions together --
and avoid duplication.


928	 =C2=A0 All leaf-BFER in a BIER-TE domain can share a single BitPositio=
n.
929	 =C2=A0 This is possible because the BitPosition for the adjacency to r=
each
930	 =C2=A0 the BFER can be used to distinguish whether or not packets shou=
ld
931	 =C2=A0 reach the BFER.

[nit] s/leaf-BFER/leaf-BFERs


...
937	4.4. =C2=A0LANs

939	 =C2=A0 In a LAN, the adjacency to each neighboring BFR on the LAN is g=
iven a
940	 =C2=A0 unique BitPosition. =C2=A0The adjacency of this BitPosition is =
a
941	 =C2=A0 forward_connected adjacency towards the BFR and this BitPositio=
n is
942	 =C2=A0 populated into the BIFT of all the other BFRs on that LAN.

[nit] s/In a LAN, the adjacency to each neighboring BFR on the LAN/In
a LAN, the adjacency to each neighboring BFR


...
952	 =C2=A0 If Bandwidth on the LAN is not an issue and most BIER-TE traffi=
c
953	 =C2=A0 should be copied to all neighbors on a LAN, then BitPositions c=
an be
954	 =C2=A0 saved by assigning just a single BitPosition to the LAN and
955	 =C2=A0 populating the BitPosition of the BIFTs of each BFRs on the LAN=
 with
956	 =C2=A0 a list of forward_connected adjacencies to all other neighbors =
on the
957	 =C2=A0 LAN.

[] "If Bandwidth on the LAN is not an issue..." =C2=A0I don't understand
how bw comes into play if the traffic needs to be forwarded to all
neighbors anyway. =C2=A0It seems that using a single BP may lead to L2
multicast, while different BPs might now. =C2=A0Just thinking out loud...


[minor] "most BIER-TE traffic should be copied to all neighbors" =C2=A0If
the LAN shares a BP, how is traffic that doesn't need to be copied to
all differentiated? =C2=A0It seems that a separate BP per BFR would still
be needed. =C2=A0Am I missing something?


959	 =C2=A0 This optimization does not work in the case of BFRs redundantly
960	 =C2=A0 connected to more than one LANs with this optimization because =
these
961	 =C2=A0 BFRs would receive duplicates and forward those duplicates into=
 the
962	 =C2=A0 opposite LANs. =C2=A0Adjacencies of such BFRs into their LANs s=
till need a
963	 =C2=A0 separate BitPosition.

[nit] s/one LANs/one LAN


[nit] s/their LANs/their LAN


965	4.5. =C2=A0Hub and Spoke
...
972	 =C2=A0 This option is similar to the BitPosition optimization in LANs:
973	 =C2=A0 Redundantly connected spokes need their own BitPositions.

[minor] Why? =C2=A0In this case the spokes are leaf-BFRs.


...
982	4.6. =C2=A0Rings
...
988	 =C2=A0 For the rings shown in the following picture, a single BitPosit=
ion
989	 =C2=A0 will suffice to forward traffic entering the ring at BFRa or BF=
Rb all
990	 =C2=A0 the way up to BFR1:

[minor] s/the following picture/Figure 10


...
1013	 =C2=A0 Note that this example only permits for packets to enter the r=
ing at
1014	 =C2=A0 BFRa and BFRb, and that packets will always travel clockwise. =
=C2=A0If
1015	 =C2=A0 packets should be allowed to enter the ring at any ring BFR, t=
hen one
1016	 =C2=A0 would have to use two ring BitPositions. =C2=A0One for clockwi=
se, one for
1017	 =C2=A0 counterclockwise.

[minor] "only permits for packets to enter the ring at BFRa and BFRb"
As long as the direction is maintained (clockwise), then the packets
should be able to enter through any BFR. =C2=A0Am I missing something here?


[nit] s/One for clockwise, one for counterclockwise./One for each
direction: clockwise and counterclockwise.


1019	 =C2=A0 Both would be set up to stop rotating on the same link, e.g. =
=C2=A0L1.
1020	 =C2=A0 When the ingress ring BFR creates the clockwise copy, it will =
reset
1021	 =C2=A0 the counterclockwise BitPosition because the DNR bit only appl=
ies to
1022	 =C2=A0 the bit for which the replication is done. =C2=A0Likewise for =
the
1023	 =C2=A0 clockwise BitPosition for the counterclockwise copy. =C2=A0In =
result, the
1024	 =C2=A0 ring ingress BFR will send a copy in both directions, serving =
BFRs on
1025	 =C2=A0 either side of the ring up to L1.

[nit] s/In result/As a result


1027	4.7. =C2=A0Equal Cost MultiPath (ECMP)

1029	 =C2=A0 The ECMP adjacency allows to use just one BP per link bundle b=
etween
1030	 =C2=A0 two BFRs instead of one BP for each p2p member link of that li=
nk
1031	 =C2=A0 bundle. =C2=A0In the following picture, one BP is used across =
L1,L2,L3.

[minor] s/the following picture/Figure 11


...
1057	 =C2=A0 This document does not standardize any ECMP algorithm because =
it is
1058	 =C2=A0 sufficient for implementations to document their freely chosen=
 ECMP
1059	 =C2=A0 algorithm. =C2=A0This allows the BIER-TE Controller to calcula=
te ECMP
1060	 =C2=A0 paths and seeds. =C2=A0The following picture shows an example =
ECMP
1061	 =C2=A0 algorithm:

[minor] s/The following picture/Figure 12


...
1069	 =C2=A0 In the following example, all traffic from BFR1 towards BFR10 =
is
1070	 =C2=A0 intended to be ECMP load split equally across the topology. =
=C2=A0This
1071	 =C2=A0 example is not meant as a likely setup, but to illustrate that=
 ECMP
1072	 =C2=A0 can be used to share BPs not only across link bundles, and it
1073	 =C2=A0 explains the use of the seed parameter.

[minor] "ECMP can be used to share BPs not only across link bundles"
Remove "not only". =C2=A0 ???


...
1128	 =C2=A0 With the setup of ECMP in above topology, traffic would not be
1129	 =C2=A0 equally load-split. =C2=A0Instead, links L22 and L31 would see=
 no traffic
1130	 =C2=A0 at all: BFR2 will only see traffic from BFR1 for which the ECM=
P hash
1131	 =C2=A0 in BFR1 selected the first adjacency in the list of 2 adjacenc=
ies
1132	 =C2=A0 given as parameters to the ECMP. =C2=A0It is link L11-to-BFR2.=
 =C2=A0BFR2
1133	 =C2=A0 performs again ECMP with two adjacencies on that subset of tra=
ffic
1134	 =C2=A0 using the same seed1, and will therefore again select the firs=
t of
1135	 =C2=A0 its two adjacencies: L21-to-BFR4. =C2=A0And therefore L22 and =
BFR5 sees no
1136	 =C2=A0 traffic. =C2=A0Likewise for L31 and BFR6.

[nit] s/in above topology/in the topology above


...
1146	 =C2=A0 Note that ECMP solutions outside of BIER often hide the seed b=
y auto-
1147	 =C2=A0 selecting it from local entropy such as unique local or next-h=
op
1148	 =C2=A0 identifiers. =C2=A0The solutions chosen for BIER-TE to allow t=
he BIER-TE
1149	 =C2=A0 Controller to explicitly set the seed maximizes the ability of=
 the
1150	 =C2=A0 BIER-TE Controller to choose the seed, independent of such see=
d
1151	 =C2=A0 source that the BIER-TE Controller may not be able to control =
well,
1152	 =C2=A0 and even calculate optimized seeds for multi-hop cases.

[] "independent of such seed source that the BIER-TE Controller may
not be able to control well" =C2=A0Not sure what is meant here -- the
sentence seems to read well with out this text.


1154	4.8. =C2=A0Routed adjacencies

[minor] Do you mean Forward Routed adjacencies? =C2=A0Later on you mention
it, but it is not clear at first read because "routed" is not one of
the defined types in =C2=A73.2.


1156	4.8.1. =C2=A0Reducing BitPositions
...
1174	 =C2=A0 Assume the requirement in the above picture is to explicitly s=
teer
1175	 =C2=A0 traffic flows that have arrived at BFR1 or BFR4 via a shortest=
 path
1176	 =C2=A0 in the routing underlay "Network Area 1" to one of the followi=
ng
1177	 =C2=A0 three next segments: (1) BFR2 via link L1, (2) BFR2 via link L=
2, (3)
1178	 =C2=A0 via BFR3.

[minor] s/the above picture/Figure 14


[nit] s/L2, (3)/L2, or (3)


...
1193	4.9. =C2=A0Reuse of BitPositions (without DNR)
...
1200	 =C2=A0 Because BP are reset after passing a BFR with an adjacency for=
 that
1201	 =C2=A0 BP, reuse of BP across multiple BFR does not introduce any pro=
blems
1202	 =C2=A0 with duplicates or loops that do not also exist when every adj=
acency
1203	 =C2=A0 has a unique BP: Instead of setting one BP in a BitString that=
 is
1204	 =C2=A0 reused in N-adjacencies, one would get the same or worse resul=
ts if
1205	 =C2=A0 each of these adjacencies had a unique BP and all of them wher=
e set
1206	 =C2=A0 in the BitString. =C2=A0Instead, based on the case, BPs can be=
 reused
1207	 =C2=A0 without limitation, or they introduce fewer path steering choi=
ces, or
1208	 =C2=A0 they do not work.

[?] "same or worse" =C2=A0 Worse?


[?] "BPs can be reused without limitation, or they introduce fewer
path steering choices, or they do not work." =C2=A0 What?


...
1216	 =C2=A0 An example of (A) was given in Figure 13, where BP 0:7, BP 0:8=
 and BP
1217	 =C2=A0 0:9 are each reused across multiple BFR because a single packe=
t/path
1218	 =C2=A0 would never be able to reach more than one BFR sharing the sam=
e BP.

[nit] s/multiple BFR/multiple BFRs


...
1235	 =C2=A0 Reuse may also save BPs in larger topologies. =C2=A0Consider t=
he topology
1236	 =C2=A0 shown in Figure 17, but only the following explanations: A BFI=
R/
1237	 =C2=A0 sender (e.g.: video headend) is attached to area 1, and area 2=
...6
1238	 =C2=A0 contain receivers/BFER. =C2=A0Assume each area had a distribut=
ion ring,
1239	 =C2=A0 each with two BPs to indicate the direction (as explained in b=
efore).
1240	 =C2=A0 These two BPs could be reused across the 5 areas. =C2=A0Packet=
s would be
1241	 =C2=A0 replicated through other BPs to the desired subset of areas, a=
nd once
1242	 =C2=A0 a packet copy reaches the ring of the area, the two ring BPs c=
ome
1243	 =C2=A0 into play. =C2=A0This reuse is a case of (B), but it limits th=
e topology
1244	 =C2=A0 choices: Packets can only flow around the same direction in th=
e rings
1245	 =C2=A0 of all areas. =C2=A0This may or may not be acceptable based on=
 the desired
1246	 =C2=A0 path steering options: If resilient transmission is the path
1247	 =C2=A0 engineering goal, then it is likely a good optimization, if th=
e
1248	 =C2=A0 bandwidth of each ring was to be optimized separately, it woul=
d not
1249	 =C2=A0 be a good limitation.

[] Figure 17 is all the way in =C2=A77.5.1. =C2=A0Consider duplicating it h=
ere
to help in the reading/continuity.


[minor] "but only the following explanations" =C2=A0 I haven't read =C2=A77=
.5.1
yet, but assume that there is an alternate description of the figure
there. =C2=A0Without that knowledge (a guess at this point) this text feels
out of place. =C2=A0Another reason to consider duplicating the figure
here...


[nit] s/as explained in before/as explained before


1251	4.10. =C2=A0Summary of BP optimizations

[] Maybe move the the start.


...
1268	 =C2=A0 o =C2=A0A LAN with N BFR needs at most N BP (one for each BFR)=
. =C2=A0It only
1269	 =C2=A0 =C2=A0 =C2=A0needs one BP for all those BFR tha are not redund=
anty connected to
1270	 =C2=A0 =C2=A0 =C2=A0multiple LANs (Section 4.4).

[nit] s/tha are not redundanty/that are not redundantly


...
1302	5.1. =C2=A0Loops
...
1309	 =C2=A0 With DNR set, looping can happen. =C2=A0Consider in the ring p=
icture that
1310	 =C2=A0 link L4 from BFR3 is plugged into the L1 interface of BFRa. =
=C2=A0This
1311	 =C2=A0 creates a loop where the rings clockwise BitPosition is never =
reset
1312	 =C2=A0 for copies of the packets traveling clockwise around the ring.

[minor] "the ring picture" =C2=A0Which one? =C2=A0Refer to a Figure and con=
sider
duplicating it closer to where it is refered to.


[minor] "link L4 from BFR3 is plugged into the L1 interface of BFRa"
Assuming you're talking about Figure 10... =C2=A0L4 seems to be the link
between BFR3 and BFR2, and L1 in BFRa is connected to BFR1 -- I don't
understand which changes you mean. =C2=A0Again, consider putting a figure
closer to this description.


...
1321	5.2. =C2=A0Duplicates

1323	 =C2=A0 Duplicates happen when the topology of the BitString is not a =
tree
1324	 =C2=A0 but redundantly connecting BFRs with each other. =C2=A0The BIE=
R-TE
1325	 =C2=A0 Controller must therefore ensure to only create BitStrings tha=
t are
1326	 =C2=A0 trees in the topology.

[] Can you provide an example?


...
1338	6. =C2=A0BIER-TE Forwarding Pseudocode

[] Placing this section here feels completely out of place because
BIER-TE forwarding is otherwise described in =C2=A73. =C2=A0Please move thi=
s
there.


...
1366	 =C2=A0 The difference is that in BIER-TE, step [1] must not be perfor=
med,
1367	 =C2=A0 but is replaced with [2] (when the forwarding plane algorithm =
is
1368	 =C2=A0 implemented verbatim as shown above).

[minor] "step [1]...is replaced with [2]" =C2=A0 Step 2 is already present
in the original pseudocode, so it is not really a replacement...Step 1
is simply not performed.


1370	 =C2=A0 In BIER, the F-BM of a BP has all BP set that are meant to be
1371	 =C2=A0 forwarded via the same neighbor. =C2=A0It is used to reset tho=
se BP in the
1372	 =C2=A0 packet after the first copy to this neighbor has been made to =
inhibit
1373	 =C2=A0 multiple copies to the same neighbor.

[nit] s/all BP/all BPs


[nit] s/those BP/those BPs


1375	 =C2=A0 In BIER-TE, the F-BM of a particular BP with an adjacency is t=
he list
1376	 =C2=A0 of all BPs with an adjacency on this BFR except the particular=
 BP
1377	 =C2=A0 itself if it has an adjacency with the DNR bit set. =C2=A0The =
F-BM is used
1378	 =C2=A0 to reset the F-BM BPs before creating copies.

[minor] "with the DNR bit set" =C2=A0 Theis pseudocode reflects "basic"
BIER-TE, right? =C2=A0I thought the DNR flag is not required/supported in
the "basic" version.


1380	 =C2=A0 In BIER, the order of BPs impacts the result of forwarding bec=
ause of
1381	 =C2=A0 [1]. =C2=A0In BIER-TE, forwarding is not impacted by the order=
 of BPs. =C2=A0It
1382	 =C2=A0 is therefore possible to further optimize forwarding than in B=
IER.
1383	 =C2=A0 For example, BIER-TE forwarding can be parallelized such that =
a
1384	 =C2=A0 parallel instance (such as an egres linecard) can process any =
subset
1385	 =C2=A0 of BPs without any considerations for the other BPs - and with=
out any
1386	 =C2=A0 prior, cross-BP shared processing.

[nit] s/because of [1]/because of step [1]


1388	 =C2=A0 The above simplified pseudocode is elaborated further as follo=
ws:

[] By "elaborated further" do you mean extended, enhanced, or
something like that? =C2=A0I first thought you meant you were explaining it
(elaborating on its meaning), but Figure 16 seems like an extension.
??


1390	 =C2=A0 o =C2=A0This pseudocode eliminates per-bit F-BM, therefore red=
ucing state
1391	 =C2=A0 =C2=A0 =C2=A0by BitStringLength^2*SI and eliminating the need =
for per-packet-
1392	 =C2=A0 =C2=A0 =C2=A0copy masking operation except for adjacencies wit=
h DNR flag set:

[nit] s/This pseudocode/The updated pseudocode in Figure 16


[nit] s/with DNR flag/with the DNR flag


...
1448	 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Figure 16: BI=
ER-TE Forwarding Pseudocode

[] I assume the intent is for this pseudocode to be a representation
of what is specified elsewhere -- is that correct? =C2=A0 Even then, it
would be very nice if the functions/operations were explained.


[major] Is this pseducode expected to "replace" the one in Figure 15?
Does it represent "full" BIER-TE forwarding? =C2=A0Neither is clear from
the text.


1450	7. =C2=A0Managing SI, subdomains and BFR-ids

1452	 =C2=A0 When the number of bits required to represent the necessary ho=
ps in
1453	 =C2=A0 the topology and BFER exceeds the supported bitstring length,
1454	 =C2=A0 multiple SI and/or subdomains must be used. =C2=A0This section=
 discusses
1455	 =C2=A0 how.

[minor] s/bitstring length/BitStringLength/s =C2=A0 =C2=A0From rfc8279.


[nit] s/multiple SI/multiple SIs/g


...
1461	7.1. =C2=A0Why SI and sub-domains

1463	 =C2=A0 For BIER and BIER-TE forwarding, the most important result of =
using
1464	 =C2=A0 multiple SI and/or subdomains is the same: Packets that need t=
o be
1465	 =C2=A0 sent to BFER in different SI or subdomains require different B=
IER
1466	 =C2=A0 packets: each one with a bitstring for a different (SI,subdoma=
in)
1467	 =C2=A0 combination. =C2=A0Each such bitstring uses one bitstring leng=
th sized SI
1468	 =C2=A0 block in the BIFT of the subdomain. =C2=A0We call this a BIFT:=
SI (block).

[nit] s/sent to BFER/sent to BFERs


[nit] s/different SI/different SIs/g


1470	 =C2=A0 For BIER and BIER-TE forwarding itself there is also no differ=
ence
1471	 =C2=A0 whether different SI and/or sub-domains are chosen, but SI and
1472	 =C2=A0 subdomain have different purposes in the BIER architecture sha=
red by
1473	 =C2=A0 BIER-TE. =C2=A0This impacts how operators are managing them an=
d how
1474	 =C2=A0 especially flow overlays will likely use them.

[nit] s/itself/themselves,


...
1479	 =C2=A0 If there are different flow services (or service instances) re=
quiring
1480	 =C2=A0 replication to different subsets of BFER, then it will likely =
not be
1481	 =C2=A0 possible to achieve the best replication efficiency for all of=
 these
1482	 =C2=A0 service instances via subdomain 0. =C2=A0Ideal replication eff=
iciency for
1483	 =C2=A0 N BFER exists in a subdomain if they are split over not more t=
han
1484	 =C2=A0 ceiling(N/bitstring-length) SI.

[minor] s/bitstring-length/BitStringLength/g


...
1498	 =C2=A0 To be able to easily reuse (and modify as little as possible)
1499	 =C2=A0 existing BIER procedures including flow-overlay and routing un=
derlay,
1500	 =C2=A0 when BIER-TE forwarding is added, we therefore reuse SI and su=
bdomain
1501	 =C2=A0 logically in the same way as they are used in BIER: All necess=
ary
1502	 =C2=A0 BFIR/BFER for a service use a single BIER-TE BIFT and are spli=
t
1503	 =C2=A0 across as many SI as necessary (see below). =C2=A0Different se=
rvices may
1504	 =C2=A0 use different subdomains that primarily exist to provide more
1505	 =C2=A0 efficient replication (and for BIER-TE desirable path steering=
) for
1506	 =C2=A0 different subsets of BFIR/BFER.

[minor] "see below" =C2=A0Where?


1508	7.2. =C2=A0Bit assignment comparison BIER and BIER-TE

[nit] s/comparison BIER/comparison between BIER


...
1519	 =C2=A0 "Desired" topology because it depends on the physical topology=
, and
1520	 =C2=A0 on the desire of the operator to allow for explicit path steee=
ring
1521	 =C2=A0 across every single hop (which requires more bits), or reducin=
g the
1522	 =C2=A0 number of required bits by exploiting optimizations such as un=
icast
1523	 =C2=A0 (forward_route), ECMP or flood (DNR) over "uninteresting" sub-=
parts
1524	 =C2=A0 of the topology - e.g. parts where different trees do not need=
 to
1525	 =C2=A0 take different paths due to path steering reasons.

[nit] s/steeering/steering


1527	 =C2=A0 The total number of bits to describe the topology vs. the BFER=
 in a
1528	 =C2=A0 BIFT:SI can range widely based on the size of the topology and=
 the
1529	 =C2=A0 amount of alternative paths in it. =C2=A0The higher the percen=
tage, the
1530	 =C2=A0 higher the likelihood, that those topology bits are not just B=
IER-TE
1531	 =C2=A0 overhead without additional benefit, but instead that they wil=
l allow
1532	 =C2=A0 to express desirable path steering alternatives.

[minor] s/vs. the BFER/vs. the number of BFERs


[minor] "The higher the percentage" of what?


1534	7.3. =C2=A0Using BFR-id with BIER-TE
...
1569	 =C2=A0 If "interdependent branches" are required, the application cou=
ld call
1570	 =C2=A0 a BIER-TE Controller API with the list of required BFER-id and=
 get
1571	 =C2=A0 the required bitstring back. =C2=A0Whenever the set of BFER-id=
 changes,
1572	 =C2=A0 this is repeated.

[minor] s/BFER-id/BFR0id =C2=A0 To be consistent with the rest of the text.


[] "call a BIER-TE Controller API" =C2=A0 Where is that defined?
Presumably (from the previous paragraph) "the BIER-TE Controller can
provide to such applications for every BFR-id a SI:bitstring with the
BIER-TE bits..." using the same API, right? =C2=A0 Isn't this out of scope?


[minor] "SI:bitstring with the BIER-TE bits" =C2=A0I assume that by
"BIER-TE bits" you mean the BPs that are set (or something to that
effect), right? =C2=A0Please don't introduce new terminology unless it is
necessary -- generically using "BIER-TE bits" may be confusing.


1574	 =C2=A0 Note that in either case (unlike in BIER), the bits in BIER-TE=
 may
1575	 =C2=A0 need to change upon link/node failure/recovery, network expans=
ion and
1576	 =C2=A0 network resource consumption by other traffic as part of traff=
ic
1577	 =C2=A0 engineering goals (e.g.: re-optimization of lower priority tra=
ffic
1578	 =C2=A0 flows). =C2=A0Interactions between such BFIR applications and =
the BIER-TE
1579	 =C2=A0 Controller do therefore need to support dynamic updates to the
1580	 =C2=A0 bitstrings.

[minor] As above, "bits in BIER-TE"...


1582	7.4. =C2=A0Assigning BFR-ids for BIER-TE

[] Isn't assignment also covered in the previous section?

[major] =C2=A71.3 says that "allocation of BFIR-ID values...[is]...outside
the scope of this document".


1584	 =C2=A0 For a non-leaf BFER, there is usually a single bit k for that =
BFER
1585	 =C2=A0 with a local_decap() adjacency on the BFER. =C2=A0The BFR-id f=
or such a
1586	 =C2=A0 BFER is therefore most easily the one it would have in BIER: S=
I *
1587	 =C2=A0 bitstring-length + k.

[minor] There's some redundancy (too many mentions of BFER) in the
first sentence.

Suggestion>
=C2=A0 =C2=A0For a non-leaf BFER, there is usually a single bit k set with =
a local_decap
=C2=A0 =C2=A0adjacency on it.


...
1600	 =C2=A0 It is not currently determined if a single subdomain could or =
should
1601	 =C2=A0 be allowed to forward both BIER and BIER-TE packets. =C2=A0If =
this should
1602	 =C2=A0 be supported, there are two options:

[major] If it is "not currently determined", then why even include it?
=C2=A0Isn't this also out of scope?


...
1618	7.5.1. =C2=A0With BIER

1620	 =C2=A0 Consider a network setup with a bitstring length of 256 for a =
network
1621	 =C2=A0 topology as shown in the picture below. =C2=A0The network has =
6 areas,
1622	 =C2=A0 each with ca. 170 BFR, connecting via a core with some larger =
(core)
1623	 =C2=A0 BFR. =C2=A0To address all BFER with BIER, 4 SI are required. =
=C2=A0To send a
1624	 =C2=A0 BIER packet to all BFER in the network, 4 copies need to be se=
nt by
1625	 =C2=A0 the BFIR. =C2=A0On the BFIR it does not make a difference how =
the BFR-id
1626	 =C2=A0 are allocated to BFER in the network, but for efficiency furth=
er down
1627	 =C2=A0 in the network it does make a difference.

[minor] s/the picture below/Figure 17


[nit] s/170 BFR/170 BFRs


[nit] s/some larger (core) BFR/some larger (core) BFRs


[nit] s/all BFER/all BFERs


[nit] s/4 SI/4 SIs


[minor] "4 SI are required" =C2=A0That is true if each area has 170 BFRs
(not "about 170") and there are 4 core BFRs (not just "some"). =C2=A0IOW,
the example is ok, but somewhat sloppy.


[nit] s/BFR-id are allocated to BFER/BFR-ids are allocated to BFERs


...
1641	 =C2=A0 With random allocation of BFR-id to BFER, each receiving area =
would
1642	 =C2=A0 (most likely) have to receive all 4 copies of the BIER packet =
because
1643	 =C2=A0 there would be BFR-id for each of the 4 SI in each of the area=
s.
1644	 =C2=A0 Only further towards each BFER would this duplication subside =
- when
1645	 =C2=A0 each of the 4 trees runs out of branches.

[nit] s/BFR-id for each of the 4 SI/BFR-ids for each of the 4 SIs


1647	 =C2=A0 If BFR-id are allocated intelligently, then all the BFER in an=
 area
1648	 =C2=A0 would be given BFR-id with as few as possible different SI. =
=C2=A0Each
1649	 =C2=A0 area would only have to forward one or two packets instead of =
4.

[nit] s/BFR-id/BFR-ids


1651	 =C2=A0 Given how networks can grow over time, replication efficiency =
in an
1652	 =C2=A0 area will also easily go down over time when BFR-id are networ=
k wide
1653	 =C2=A0 allocated sequentially over time. =C2=A0An area that initially=
 only has
1654	 =C2=A0 BFR-id in one SI might end up with many SI over a longer perio=
d of
1655	 =C2=A0 growth. =C2=A0Allocating SIs to areas with initially sufficien=
tly many
1656	 =C2=A0 spare bits for growths can help to alleviate this issue. =C2=
=A0Or renumber
1657	 =C2=A0 BFR-id after network expansion. =C2=A0In this example one may =
consider to
1658	 =C2=A0 use 6 SI and assign one to each area.

[nit] s/BFR-id/BFR-ids


[nit] s/many SI/many SIs


[minor] s/renumber BFR-id/renumber BFERs


[nit] s/6 SI/6 SIs


...
1663	7.5.2. =C2=A0With BIER-TE

1665	 =C2=A0 In BIER-TE one needs to determine a subset of the physical top=
ology
1666	 =C2=A0 and attached BFER so that the "desired" representation of this
1667	 =C2=A0 topology and the BFER fit into a single bitstring. =C2=A0This =
process
1668	 =C2=A0 needs to be repeated until the whole topology is covered.

[nit] s/BFER/BFERs


1670	 =C2=A0 Once bits/SIs are assigned to topology and BFER, BFR-id is jus=
t a
1671	 =C2=A0 derived set of identifiers from the operator/BIER-TE Controlle=
r as
1672	 =C2=A0 explained above.

[nit] s/BFER/BFERs


1674	 =C2=A0 Every time that different sub-topologies have overlap, bits ne=
ed to
1675	 =C2=A0 be repeated across the bitstrings, increasing the overall amou=
nt of
1676	 =C2=A0 bits required across all bitstring/SIs. =C2=A0In the worst cas=
e, random
1677	 =C2=A0 subsets of BFER are assigned to different SI. =C2=A0This is mu=
ch worse
1678	 =C2=A0 than in BIER because it not only reduces replication efficienc=
y with
1679	 =C2=A0 the same number of overall bits, but even further - because mo=
re bits
1680	 =C2=A0 are required due to duplication of bits for topology across mu=
ltiple
1681	 =C2=A0 SI. =C2=A0Intelligent BFER to SI assignment and selecting spec=
ific
1682	 =C2=A0 "desired" subtopologies can minimize this problem.

[nit] s/subsets of BFER are assigned to different SI/subsets of BFERs
are assigned to different SIs


[nit] s/multiple SI/multiple SIs


1684	 =C2=A0 To set up BIER-TE efficiently for above topology, the followin=
g bit
1685	 =C2=A0 allocation methods can be used. =C2=A0This method can easily b=
e expanded
1686	 =C2=A0 to other, similarly structured larger topologies.

[nit] s/for above/for the above


[nit] s/methods/method


1688	 =C2=A0 Each area is allocated one or more SI depending on the number =
of
1689	 =C2=A0 future expected BFER and number of bits required for the topol=
ogy in
1690	 =C2=A0 the area. =C2=A0In this example, 6 SI, one per area.

[nit] s/SI/SIs


[nit] s/BFER/BFERs


...
1699	 =C2=A0 On all BFIR in an area j, bia in each BIFT:SI is populated wit=
h the
1700	 =C2=A0 same forward_routed(BFRja), and bib with forward_routed(BFRjb)=
. =C2=A0On
1701	 =C2=A0 all area edge BFR, bea in BIFT:SI=3Dk is populated with
1702	 =C2=A0 forward_routed(BFRka) and beb in BIFT:SI=3Dk with
1703	 =C2=A0 forward_routed(BFRkb).

[nit] s/BFIR/BFIRs


[minor] The meaning of what you mean with this nomenclature may not be
clear to everyone. =C2=A0You might want to define it -- or change how it is
explained.


1705	 =C2=A0 For BIER-TE forwarding of a packet to some subset of BFER acro=
ss all
1706	 =C2=A0 areas, a BFIR would create at most 6 copies, with SI=3D1...SI=
=3D6, In
1707	 =C2=A0 each packet, the bits indicate bits for topology and BFER in t=
hat
1708	 =C2=A0 topology plus the four bits to indicate whether to pass this p=
acket
1709	 =C2=A0 via the ingress area a or b border BFR and the egress area a o=
r b
1710	 =C2=A0 border BFR, therefore allowing path steering for those two "un=
icast"
1711	 =C2=A0 legs: 1) BFIR to ingress are edge and 2) core to egress area e=
dge.
1712	 =C2=A0 Replication only happens inside the egress areas. =C2=A0For BF=
ER in the
1713	 =C2=A0 same area as in the BFIR, these four bits are not used.

[nit] s/some subset of BFER/a subset of BFERs


1715	7.6. =C2=A0Summary

1717	 =C2=A0 BIER-TE can like BIER support multiple SI within a sub-domain =
to
1718	 =C2=A0 allow re-using the concept of BFR-id and therefore minimize BI=
ER-TE
1719	 =C2=A0 specific functions in underlay routing, flow overlay methods a=
nd BIER
1720	 =C2=A0 headers.

[] Maybe I missed it, but I don't remember seeing a discussion on
"specific functions in underlay routing, flow overlay methods".


[nit] s/BIER-TE can like BIER/BIER-TE can, like BIER,


[nit] s/multiple SI/multiple SIs


...
1725	 =C2=A0 Subdomains can in BIER-TE be used like in BIER to create more
1726	 =C2=A0 efficient replication to known subsets of BFER.

[nit] s/BFER/BFERs


1728	 =C2=A0 Assigning bits for BFER intelligently into the right SI is mor=
e
1729	 =C2=A0 important in BIER-TE than in BIER because of replication effic=
iency
1730	 =C2=A0 and overall amount of bits required.

[nit] s/BFER/BFERs


1732	8. =C2=A0BIER-TE and Segment Routing

[] What is the purpose of this section? =C2=A0It seems to somehow compare
BIER/BIER-TE with SR -- but, why? =C2=A0In the context of this document,
why is mentioning SR needed? =C2=A0At times the text seems to even try to
position BIER-TE as some type of SR alternative. =C2=A0Even then it talks
about how they can "naturally be combined"...

I don't understand the purpose and think it would be better to remove it.


...
1784	9. =C2=A0Security Considerations

1786	 =C2=A0 The security considerations are the same as for BIER with the
1787	 =C2=A0 following differences:

1789	 =C2=A0 BFR-ids and BFR-prefixes are not used in BIER-TE, nor are proc=
edures
1790	 =C2=A0 for their distribution, so these are not attack vectors agains=
t BIER-
1791	 =C2=A0 TE.

[minor] BFR-ids are used -- not for BIER-TE-specific actions but
because of the encapsulation; they are still there.

[major] Add references to the relevant documents where BIER security
is discussed.

[major] For the most part the BIER-TE architecture seems close enough
to the BIER architecture to have the same security properties.
However, I think that short security considerations tend to attract
more scrutiny. =C2=A0A couple of suggestions:

(1) The big change is that "BIER-TE replaces in-network autonomous
path calculation by explicit paths calculated by the BIER-TE
Controller." =C2=A0There are all kinds of security vulnerabilities that
could come from incorrect (because of an error or malicious action)
path calculation and the subsequent programming. =C2=A0Even if the specific
BIER-TE control protocol is not specified, some type of generic
security considerations should be provided. =C2=A0Consider rfc7428.

(2) The concept of BIER-TE topology is also introduced. =C2=A0An
invalid/wrong network topology (because of an error or malicious
action) can result in an invalid/wrong BIER-TE topology which, in
turn, can result in all kinds of bad paths through the network. =C2=A0As
above, it would be ideal to include general security considerations
related to topology discovery. =C2=A0There is some text that could be
reused in rfc7752, but it is probably not a good general reference.

(3) In general it would be a good idea to mention why the changes in
BIER-TE wrt BIER (at least the major ones) don't affect the security.
For example, the use of the BitString is different, but the same
vulnerabilities exist because the packets may still be misdirected if
the packet is not processed appropriately (there's some text about
this in rfc8279).


...
2089	13.2. =C2=A0Informative References
...
2121	 =C2=A0 [RFC2119] =C2=A0Bradner, S., "Key words for use in RFCs to Ind=
icate
2122	 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Requirement Levels", =
BCP 14, RFC 2119,
2123	 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0DOI 10.17487/RFC2119,=
 March 1997,
2124	 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<https://www.rfc-edit=
or.org/info/rfc2119>.

[major] This reference (and the one to rfc8174) should be Normative.

[End of Review -09]


From nobody Mon May 17 01:07:51 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: bier@ietf.org
Delivered-To: bier@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D8EDE3A2DB9; Mon, 17 May 2021 01:07:46 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: bier@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: bier@ietf.org
Message-ID: <162123886683.10569.1393123162321832900@ietfa.amsl.com>
Date: Mon, 17 May 2021 01:07:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/funmCdLcuf0M_CvMkSNrNnkx1N4>
Subject: [Bier] I-D Action: draft-ietf-bier-te-yang-03.txt
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 17 May 2021 08:07:47 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Bit Indexed Explicit Replication WG of the IETF.

        Title           : A YANG data model for Traffic Engineering for Bit Index Explicit Replication (BIER-TE)
        Authors         : Zheng(Sandy) Zhang
                          Cui(Linda) Wang
                          Ran Chen
                          Fangwei Hu
                          Mahesh Sivakumar
                          Huanan Chen
	Filename        : draft-ietf-bier-te-yang-03.txt
	Pages           : 18
	Date            : 2021-05-17

Abstract:
   This document defines a YANG data model for Traffic Engineering for
   Bit Index Explicit Replication (BIER-TE) configuration and operation.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-bier-te-yang/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-bier-te-yang-03
https://datatracker.ietf.org/doc/html/draft-ietf-bier-te-yang-03

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-bier-te-yang-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Mon May 17 02:44:24 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: bier@ietf.org
Delivered-To: bier@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 61B613A30B7; Mon, 17 May 2021 02:44:18 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: bier@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: bier@ietf.org
Message-ID: <162124465835.32125.15869513264274398630@ietfa.amsl.com>
Date: Mon, 17 May 2021 02:44:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/A-cop_GnUQPxGe6M4_W-N0L0wnA>
Subject: [Bier] I-D Action: draft-ietf-bier-bgp-ls-bier-ext-10.txt
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 17 May 2021 09:44:19 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Bit Indexed Explicit Replication WG of the IETF.

        Title           : BGP Link-State extensions for BIER
        Authors         : Ran Chen
                          Zheng Zhang
                          Vengada Prasad Govindan
                          IJsbrand Wijnands
	Filename        : draft-ietf-bier-bgp-ls-bier-ext-10.txt
	Pages           : 12
	Date            : 2021-05-17

Abstract:
   Bit Index Explicit Replication (BIER) is an architecture that
   provides optimal multicast forwarding through a "BIER domain" without
   requiring intermediate routers to maintain any multicast related per-
   flow state.  BIER also does not require any explicit tree-building
   protocol for its operation.  A multicast data packet enters a BIER
   domain at a "Bit-Forwarding Ingress Router" (BFIR), and leaves the
   BIER domain at one or more "Bit-Forwarding Egress Routers" (BFERs).
   The BFIR router adds a BIER header to the packet.  The BIER header
   contains a bitstring in which each bit represents exactly one BFER to
   forward the packet to.  The set of BFERs to which the multicast
   packet needs to be forwarded is expressed by setting the bits that
   correspond to those routers in the BIER header.

   BGP Link-State (BGP-LS) enables the collection of various topology
   information from the network, and the topology informations are used
   by the controller to calculate the fowarding table and then program
   them onto the BFRs(instead of having each node to calculate on its
   own) and that can be for both inter-as and intra-as situations.

   This document specifies extensions to the BGP Link-state address-
   family in order to advertise BIER informations.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-bier-bgp-ls-bier-ext/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-bier-bgp-ls-bier-ext-10
https://datatracker.ietf.org/doc/html/draft-ietf-bier-bgp-ls-bier-ext-10

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-bier-bgp-ls-bier-ext-10


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Tue May 18 08:30:56 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: bier@ietf.org
Delivered-To: bier@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8846D3A1701; Tue, 18 May 2021 08:30:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: bier@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: bier@ietf.org
Message-ID: <162135185152.29960.14081004092284625573@ietfa.amsl.com>
Date: Tue, 18 May 2021 08:30:51 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/p8KKkMI_yQDRBTwUF-rlz84EQdA>
Subject: [Bier] I-D Action: draft-ietf-bier-ospfv3-extensions-04.txt
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
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, 18 May 2021 15:30:52 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Bit Indexed Explicit Replication WG of the IETF.

        Title           : OSPFv3 Extensions for BIER
        Authors         : Peter Psenak
                          Nagendra Kumar Nainar
                          IJsbrand Wijnands
	Filename        : draft-ietf-bier-ospfv3-extensions-04.txt
	Pages           : 10
	Date            : 2021-05-18

Abstract:
   Bit Index Explicit Replication (BIER) is an architecture that
   provides multicast forwarding through a "BIER domain" without
   requiring intermediate routers to maintain multicast related per-flow
   state.  Neither does BIER require an explicit tree-building protocol
   for its operation.  A multicast data packet enters a BIER domain at a
   "Bit-Forwarding Ingress Router" (BFIR), and leaves the BIER domain at
   one or more "Bit-Forwarding Egress Routers" (BFERs).  The BFIR router
   adds a BIER header to the packet.  Such header contains a bit-string
   in which each bit represents exactly one BFER to forward the packet
   to.  The set of BFERs to which the multicast packet needs to be
   forwarded is expressed by the according set of bits set in BIER
   packet header.

   This document describes the OSPFv3 [RFC8362] protocol extensions
   required for BIER with MPLS encapsulation [RFC8296].  Support for
   other encapsulation types is outside the scope of this document.  The
   use of multiple encapsulation types is outside the scope of this
   document.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-bier-ospfv3-extensions/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-bier-ospfv3-extensions-04
https://datatracker.ietf.org/doc/html/draft-ietf-bier-ospfv3-extensions-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-bier-ospfv3-extensions-04


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Tue May 18 11:25:56 2021
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1717D3A1C52; Tue, 18 May 2021 11:25:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.87
X-Spam-Level: 
X-Spam-Status: No, score=-0.87 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 WfIHJor1d4KJ; Tue, 18 May 2021 11:25:49 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78A133A1C4F; Tue, 18 May 2021 11:25:48 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [131.188.34.51]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 121F5548017; Tue, 18 May 2021 20:25:42 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 0A1064E74E6; Tue, 18 May 2021 20:25:42 +0200 (CEST)
Date: Tue, 18 May 2021 20:25:41 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: bier@ietf.org, chen.ran@zte.com.cn
Cc: aretana.ietf@gmail.com, draft-ietf-bier-te-arch@ietf.org, draft-ietf-bier-bier-yang@ietf.org, bier-chairs@ietf.org, draft-ietf-bier-te-yang@ietf.org
Message-ID: <20210518182541.GB16353@faui48e.informatik.uni-erlangen.de>
References: <20210517180558.GD40483@faui48e.informatik.uni-erlangen.de> <202105181741009543295@zte.com.cn> <20210518180839.GA5939@faui48e.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20210518180839.GA5939@faui48e.informatik.uni-erlangen.de>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/50EMTW4eCcRz21FbiazO4kyuc90>
Subject: Re: [Bier] draft-ietf-bier-bier-yang (was: Re: draft bier yang expired and it needs a bier te branch as well)
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
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, 18 May 2021 18:25:54 -0000

[resending after mailman rightfully complained about too many recipients. eliminated duplicates]

On Tue, May 18, 2021 at 05:41:00PM +0800, chen.ran@zte.com.cn wrote:
> 3.4 Q: Can someone (authors) please explain what bift-id-base is ? And then put this explanation into the description for that field.
>  Ran:It means bift-id. We will update it.

Still not clear to me, what it means. How does it relate to e.g.: in-bift-id and out-bift-id ?

> The most simple model might be something like this:
>  
>   rename underlay-protocol-type to birt-owner
>  
>   Then add a value "controller" to this field.
>   So, when the value is "controller", then the BIRT is writeable via yang,
>   otherwise it is read-only because it is populated by the protocol
>  Ran:  Agree.

Ok, then next step towards useful/writeable BIRT:

RFC8279/6.3: The "Bit Index Routing Table" (BIRT) is a table that maps from the
BFR-id (in a particular sub-domain) of a BFER to the BFR-prefix of
that BFER, and to the BFR-NBR on the path to that BFER.

These tables are not in the yang model BIRT. I would argue that what the
yang model calls birt is mostly rfc8296 encap information. but not the actual birt.

 +--rw birt* [sub-domain-id]
            +--rw sub-domain-id             uint16
            +--rw bfr-id?                   uint16
       >    +-- rw tbd-resolve-nbr-from-rip
            +--rw birt-bitstringlength* [bitstringlength]
               +--rw bitstringlength    uint16
       >       +--rw bfer* [bfer-id]
       >          +--rw bfer-id
       >             +-- rw bfr-id
       >             +-- rw bfr-prefix
       >             +-- rw bfr-nbr
               +--rw encap* [si]
                  +--rw si                    uint16
                  +--rw in-bift-id?           uint32
                  +--rw bfr-nbr
                     +--rw bfr-nbr               inet:ip-prefix
                     +--rw encapsulation-type?   enumeration
                     +--rw out-bift-id           uint32

I think(hope) this would make it complete:

When a controller (without any IGP) wants to set up BIER, it could do this
by setting up the bfr table for every bfr by setting the bfr-nbr. And then
of course the encap for every nbr. I changed "birt-si" to "encap" for cosmetic
reasons. And of course, when a routing protocol is in control, this info is all RO.

Making the controller set bfr-prefix would not
be required for BIER itself, the BIFT is solely determined from the bfr-nbr
and encap info. But some overlay signaling may want to know the bfr-prefix,
and besides, the bible (rfc8279) says that BIRT includes this info.

Now, there is one IMHO very interesting option where bfr-prefix would be
used by BIER, and that is when the controller would actually not set bfr-nbr,
but only bfr-prefix, and it would be part of the BIRT->BIFT resolution logic
to track the next-hop for bfr-prefix in the RIB and dynamically change
the bfr-nbr based on unicast routing for the bfr-prefix. This setup
would therefore allow to use BIER with _any_ routing protocols, including
any type of static routing/path-engineering, but without the need for any
BIER extensions: All the BIER extensions would be instead configured by
the controller (via bfr-id/bfr-prefix and encap configs).

So, i indicated that option through the maybe binary tbd-resolve-nbr-from-rib
element. Lets say it is binary, and if it is set, then such BIRT->BIFT
logic could be used. Whether or not a vendors BIRT implementation
is decoupled from IGPs such that it is tracking bfr-prefix routes to determine
bfr-neighbor, independent of which protocol sources the route information
for bfr-prefix. I can think of at least one vendor with a very flexible
RIB infra architecure where i would expect this to be true (just guessing).

> 5. Sender-only BFIR
>  
> The BIFT-ID in BIER packet headers is only for the benefit of the BFER,
> and especially overlay stuff. I can imagine, that there can be really good
> usecases of many BIFER, for example sensors delivering packets to fewer
> number of BFIR acting as processing elements. To support this, we
> would set up BIER to maybe only have one SI for up to 256 of such BFER,
> but on the BFIR, we still configure a bfr-id (larger than 256), and
> would also announce it in the IGP so that BFER can map back from bfr-id
> in received packets to the IPv6 or IPv4 identifier of the BFIR.
>  
> So: what would we need to do to ensure that all applications will
> accordingly process bfr-id > (max-si * bsl) in the IGP, but not
> create/waste BIFT space ?

>  Ran???This kind of scenario is uncommon scenario, and I am not sure whether this scenario needs to be considered in the YANG model.

As explained above, it would depend IMHO on the deployment use-case. For
the most common SP use-case it might be not required, yes.

But the main question for the yang model is how we can make it clearer how it
is meant to work: Will it be an error to configure in the yang model a
bfr-id that is larger than (bsl * max-si) ? If we think it should be an
error, how can we codify this in the Yang model ? If we think this is not
an error, how can we codify in he yang model, what the expected behavior
of the system is when this is configured - e.g.: as i outlined above.

I just think we should not let this be underspecified but be very clear.
If implementers have different opinions about the matter, we can introduce
a RO binary yang object that allows implementations to express their
implementation behavior. 

This is just local configuration. he other question of course is what happens
when the IGP receives bfr-id information that is > than locally configured
(max-six * bsl). What should implementations do, and how do we express this.
E.g.: add bfr-id out-of-range notification for example.

> 
> 6. exemplary workflow
>  
> If would be great to add an explanatory chapter outlining a simple
> reference case:
>  
>    This yang model is used to consistently provision the BIER parameters
>    for one or more BIER subdomains across all BFIR/BFR/BFER. This configuration
>    will also be read by BIER enabled IGPs , such as IS-IS with RFC8401  
>    to learn the BIER parameters it needs to know.
>  
>    And then follow up with something like:
>  
>    On a BFR the following parameters from this YANG model need to be
>    configured to enable a BIER subdomain using ISIS with RFC8401 and
>    MPLS encapsulation:
>  
>    (BFR of course not requiring a bfr-id, but for diagnostics purposes of the
>     IGP, highly recommended to assign one - but beyond max-si*bls IMHO...)
>    ...
>  
>    On a BFIR, the following...
>  
>    (BFIR of course requiring a bfr-id, but not necessarily a bit in the BIFT)
>    ...
>  
>    On a BFER, the following...
>    (BFER of course requiring a bfr-id that must have an assigned bit).
>    ...
>  Ran:I will try my best and refer to other RFCs related to the YANG model.

Thanks a lot!

Cheers
    Toerless

> Thanks.


From nobody Tue May 18 14:41:14 2021
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64BC93A103C; Tue, 18 May 2021 14:41:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.87
X-Spam-Level: 
X-Spam-Status: No, score=-0.87 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 5iihkGXimXIw; Tue, 18 May 2021 14:41:08 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F85D3A1031; Tue, 18 May 2021 14:41:06 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [131.188.34.51]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 56679548015; Tue, 18 May 2021 23:40:55 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4ACFA4E74E9; Tue, 18 May 2021 23:40:55 +0200 (CEST)
Date: Tue, 18 May 2021 23:40:55 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Alvaro Retana <aretana.ietf@gmail.com>
Cc: draft-ietf-bier-te-arch@ietf.org, "Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com>, BIER WG Chairs <bier-chairs@ietf.org>, BIER WG <bier@ietf.org>
Message-ID: <20210518214055.GC5939@faui48e.informatik.uni-erlangen.de>
References: <CAMMESsxEH-bNuEX6ETZLg1asBj+tPo67GC8BFA2sFx8fD_G9Yg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAMMESsxEH-bNuEX6ETZLg1asBj+tPo67GC8BFA2sFx8fD_G9Yg@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/ssjAkjqT69FjfYkJtum1WyyMu2g>
Subject: Re: [Bier] AD Review of draft-ietf-bier-te-arch-09
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
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, 18 May 2021 21:41:13 -0000

On Fri, May 14, 2021 at 01:14:43PM -0700, Alvaro Retana wrote:
> Dear authors:
> Thank you for the interesting work!

Thanks for the review! Just some quick feedback / questions, before
i get to work on the requested changes. Unless i comment, i agree in general
with your feedback, which doesn't necessarily mean that they all can be resolved
perfecly (e.g.: reshuffling sections may create a better structure, but i have
to check if it works because of sequential introduction of new concepts required
by the later chapters).

> I have a couple of high-level comments/concerns.
> 
> (1) What is this document specifying?
> 
>   To start, I believe it is ok for an architecture document to be in the
>   Standards Track.
> 
>   As far as I can see, this document mainly specifies alternate semantics for
>   the BitString.  Beyond that, the BIER-TE architecture (§2) maps well onto
>   the layering described in §4/rfc8297, where the BIER layer (§4.2/rfc8297) is
>   "replaced" with the BIER-TE Control Plane and the BIER-TE forwarding layer.
>   Is this a fair high-level representation of what is defined in this
>   document?

"replaced" is certainly how the doc is written, so as to make it read
as simple as possible. The intent of course is to "amend" BIER by sharing
as much as possible with it such that a joint BIER/BIER-TE implementation
is but slightly more work than just a BIER implementation.

>   In general, the BIER-TE forwarding is well specified.  I would prefer it if
>   the definition of the adjacencies included normative language.  The
>   requirements section (§3.6) introduces some confusion with the use of "basic
>   BIER-TE forwarding" (vs "BIER-TE forwarding").  Suggestion: the
>   specification should include required ("basic") and recommended/optional
>   behaviors.  See specific comments in-line.
> 
>   OTOH, the functions of the BIER-TE control plane are described (not
>   specified) in what I consider a set of operational considerations (things
>   the controller could consider -- including sections 4, 5, and 7).  Having an
>   extensive set of operational considerations is a good thing, specially given
>   how much BIER-TE relies on the controller.  The BIER-TE control protocol is
>   central to the operation/implementation of BIER-TE, but left out of scope
>   (see my comments in §2.2).
> 
>   The BIER-TE topology is a "key new component in BIER-TE".  The document
>   doesn't specify, explain, or leave out of scope how "BIER-TE Controller
>   discovers the network topology and creates the BIER-TE topology from it"
>   (§2.2).  This omission is a significant hole in the architecture.

How about this. As long as it is clear that no references here are normative,
but all informational (like any similar references in RFC8279 that are all
informational too).

| In statically managed networks, such as in industrial environments, topology
| discovery may be a manual/offline process. In other networks topology discovery may rely on
| protocols such extending the LSP IGP into the controller itself, RFC7752 (BGP-LS)
| or RFC8345 (Yang topology) as well as BIER-TE specific extensions for example
| via draft-ietf-bier-te-yang. These examples are non-exhaustive.

>   It would be ideal if the Introduction included a high-level overview of the
>   document.
> 
> (2) Can BIER and BIER-TE really coexist in the same network?
> 
>   The Abstract mentions that they can:
> 
>      BIER-TE can co-exist with BIER forwarding in the same domain, for
>      example by using separate BIER sub-domains.
> 
>   The result of separate sub-domains is more akin to ships-in-the-night than
>   having them be "mixed": in the same sub-domain using a single BIFT
>   (populated by different sources).   Is this correct?

The way in which the BIER-TE draft defines BIER-TE forwarding, it is exclusively
"owning" a BIFT. This is because the code, e.g.: Figure 15 shows the bit-reset
semantic for all bits to use BIER-TE ([1] vs. [2]). So, what you call "mixed"
is not part of the draft.

Of course, implementations can easily build a single implementation of forwarding
across BIER/BIER-TE, even with semantic, BIER vs. BIER-TE different for every bit,
but to me this is just implementation optimization. Reason is that i have not 
identified good operational benefits to make this part of the BIER-TE architecture.
(aka: use case with some bits using bier othre bits in same bitstring using bier-te
 bit-reset logic).

However, your ships-in-the night semantic is probably incorrect. 
Even BIER alone can already have multiple BIFT per sub-domain,
because according to rfc8279, you need a combination of (sub-domain, bsl) 
to map to a BIFT, not just a sub-domain.

Here is suggested text to help clarify:

| When BIER-TE is used with rfc8296 encapsulation, the bift-id identifies an SI,
| a sub-domain, and a BitStringLength (as specified in rfc8279) AND whether to
| use BIER or BIER-TE forwarding for this bift-id.

>   §3.3 speculates about potential "definitions in BIER encapsulation
>   specifications" to "distinguish BIER from BIER-TE packets"

Yes. we had a draft to that end (one more bit in BIER header used to indicate
BIER/BIER-TE mode), but that was not met with much love by the WG back then,
but i see no good reason to now mention this as a still open option given how
rfc8279 also did not constrain itself to only rfc8296 encap.

>    -- and offers a
>   workaround if the MPLS encapsulation is used.

Not a workaround, See above proposed text "|".

In the rfc8296 forwarding plane we can easily have the same
(sub-domain, bsl) with BIER as well as BIER-TE by just giving them
different bift-ids. And that works for both mpls and non-mpls.

The routing protocol signaling right now would only work for BIER semantic bift,
but that is fine as we do not use/need the IGP BIER extensions for BIER-TE.

>   Even here, a "mixed" environment would seem to at least require independent
>   BIFTs, and not be possible with non-MPLS encapsulations.

Hope this is clear by now (yes, each BIFT is either BIER or BIER-TE architecturally,
but no - will work for MPLS and non-MPLS).

>   My conclusion is that using the encapsulation from rfc8296 it is not
>   possible to have a "mixed" BIER/BIER-TE network -- unless using MPLS with
>   extra labels and separate BIFTs.   This is just a guess --  the coexistence
>   topic deserves better coverage so that no one has to guess.
> 
> 
> (3) Organization
> 
>   The document jumps right into examples and a short discussion of the BIER-TE
>   topology -- including a quick comparison with BIER (§1.2).  There are 3
>   other sections that are also called "comparison with BIER" (§1.3, §3.5, and
>   §7.2). It may make the document clearer if the "baseline" comparison with
>   BIER was set from the start (you can dig deeper later of course).
> 
>   §3 describes BIER-TE forwarding, but sample pseudocode is in §6.  Please
>   move that to §3.
>
>   As I mentioned above, several of the sections (4, 5, and 7) include
>   considerations for the BIER-TE Controller.  It would be great if these
>   sections were consolidated under a single heading: Operational
>   Considerations for the BIER-TE Controller (for example).

Let me see if i can do the reshuffling without having to completely rewrite explanations
(stuff was put in order of explanation dependencies).

Stay tuned.

Cheers
    Toerless

> Thanks!
> 
> Alvaro.
> 
> 
> [Line numbers from idnits.]
> 
> 13	Abstract
> 
> [] In general, I think this Abstract is longer than needed -- in fact,
> it is longer than the initial part of the Introduction.  Consider
> making it shorter.
> 
> 
> 15	   This memo introduces per-packet stateless strict and loose path
> 16	   steered replication and forwarding for Bit Index Explicit Replication
> 17	   packets (RFC8279).  This is called BIER Tree Engineering (BIER-TE).
> 18	   BIER-TE can be used as a path steering mechanism in future Traffic
> 19	   Engineering solutions for BIER (BIER-TE).
> 
> [major] "BIER-TE" has two different meanings?  I'm assuming the last
> mention is just a leftover.
> 
> 
> ...
> 25	   In BIER, the BitPositions (BP) of the packets bitstring indicate BIER
> 26	   Forwarding Egress Routers (BFER), and hop-by-hop forwarding uses a
> 27	   Routing Underlay such as an IGP.
> 
> [major] The terminology used here doesn't correspond to what is used
> in rfc8279.  Please be consistent and don't make up new terminology
> unless it is to present something new.
> 
> "BitPositions (BP)" doesn't appear in rfc8297.  Instead, "bit position" is used.
> 
> s/bitstring/BitString/g
> 
> s/BIER Forwarding Egress Routers (BFER)/Bit-Forwarding Egress Routers (BFERs)
> 
> 
> 29	   In BIER-TE, BitPositions indicate adjacencies.  The BIFT of each BFR
> 30	   are only populated with BPs that are adjacent to the BFR in the BIER-
> 31	   TE topology.  The BIER-TE topology can consist of layer 2 or remote
> 32	   (routed) adjacencies.  The BFR then replicates and forwards BIER
> 33	   packets to those adjacencies.  This results in the aforementioned
> 34	   strict and loose path steering and replications.
> 
> [minor] Expand all acronyms in the Abstract *and* on first mention later on


-- 
---
tte@cs.fau.de


From nobody Wed May 19 00:33:01 2021
Return-Path: <session-request@ietf.org>
X-Original-To: bier@ietf.org
Delivered-To: bier@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C92253A215E; Wed, 19 May 2021 00:32:58 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: aretana.ietf@gmail.com, bier-chairs@ietf.org, bier@ietf.org, zzhang_ietf@hotmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <162140957832.23863.17421013415384900367@ietfa.amsl.com>
Date: Wed, 19 May 2021 00:32:58 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/2lruDbjcUqEkyEX_hniaWk-I5kA>
Subject: [Bier] bier - New Meeting Session Request for IETF 111
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 19 May 2021 07:32:59 -0000

A new meeting session request has just been submitted by Zheng Zhang, a Secretary of the bier working group.


---------------------------------------------------------
Working Group Name: Bit Indexed Explicit Replication
Area Name: Routing Area
Session Requester: Zheng Zhang


Number of Sessions: 1
Length of Session(s):  2 Hours
Number of Attendees: 50
Conflicts to Avoid: 
 Chair Conflict: mboned pim roll lsr mpls spring rift







People who must be present:
  Tony Przygienda
  Greg Shepherd
  Alvaro Retana

Resources Requested:

Special Requests:
  
---------------------------------------------------------



From nobody Fri May 21 07:38:57 2021
Return-Path: <aretana.ietf@gmail.com>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09F563A12AE; Fri, 21 May 2021 07:38:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 0Vo-5d_9Xfke; Fri, 21 May 2021 07:38:52 -0700 (PDT)
Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9877F3A12A0; Fri, 21 May 2021 07:38:51 -0700 (PDT)
Received: by mail-ed1-x52b.google.com with SMTP id o5so14598991edc.5; Fri, 21 May 2021 07:38:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc:content-transfer-encoding; bh=LtvapuyXiBFjUSBHDVl0/mPkNx/bb292saiLwgAlU/g=; b=fO50PsYRIFncE54geij3hgFZ8+NzW5ZS4Ga5DIycWr/aTciYJI2uFDgcUf6YrhRe2Z Yd+zd7kHvsQ9YxUEkYpLZP8y9bw6lSxiPFExbdQKNZYCmdElCRvFDmjh2tCFWxR80Gma RhywoOqOO5cU+rzbe5ne2mz8HPUUMUGedACU4d3CKuNvREDsLBomq/F32CDnzD7qM+Z6 6ILZifA+uPBfE0cI1hFVTSWBgQyuRrRV16/9dwjLi9ca2qsgM62CljLAsRB+vR/yR1F5 R5nSb5xktWM62z78+iZ6iRzkffWoyGodiFPjWaz1+vMeuviQ9J6GUKNMOBPRE0jXOI4I 97jQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc:content-transfer-encoding; bh=LtvapuyXiBFjUSBHDVl0/mPkNx/bb292saiLwgAlU/g=; b=eTuBR43QX5tnyXsvDSlLNcK8x0ddwkFWq9Pfa79FN1fxuQfW4ILqKTZIMfFiYPdFO5 EEtbE1Mn58EYUHQSWfYXOEwtByORVBmd/h1p/F8txR9L68xbDdKvRH+2G3tqI8AJqX2y OtUzKlt+VQlnP0kgVGpCIlCPZnHlmdIdg4YFIgMspvWIOhTwchUcyrW4WbpvlYByioKg J6hJFchmSu1iS6d4zI/nOAAufq4dHZ64eTkAVJ9i705suMzq2em2v1QAls6/KvICfQsv +pqPU1URmmJ0w8Cr9W40HEGfXZ/KufGYPh/4IIgAGNJ3En19sVcLzPzSDZ014Q/dC60p tN5w==
X-Gm-Message-State: AOAM533kpZAUMe0U269DcMaIc9gEWeGB4SLNQ9cmdenySMtnAfHhv1u/ 8eIoCLzihkeZ1WmQfxkXcG2rbvAtj5rgPIaGi4s=
X-Google-Smtp-Source: ABdhPJw7DVUVcHqsDvczbY6JMcJ06swaBmTHn5qeqjiyif390ATAUonSdU28fUCiVGwMs7d8RmsEq5f1vxRQtgxvSBk=
X-Received: by 2002:a05:6402:5201:: with SMTP id s1mr11637436edd.86.1621607929366;  Fri, 21 May 2021 07:38:49 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Fri, 21 May 2021 07:38:48 -0700
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <20210518214055.GC5939@faui48e.informatik.uni-erlangen.de>
References: <CAMMESsxEH-bNuEX6ETZLg1asBj+tPo67GC8BFA2sFx8fD_G9Yg@mail.gmail.com> <20210518214055.GC5939@faui48e.informatik.uni-erlangen.de>
MIME-Version: 1.0
Date: Fri, 21 May 2021 07:38:48 -0700
Message-ID: <CAMMESsw4JqO4rD=NBxXJfmqKhvTK4FhunC_EU7wHhUBKOTOGsQ@mail.gmail.com>
To: Toerless Eckert <tte@cs.fau.de>
Cc: draft-ietf-bier-te-arch@ietf.org,  "Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com>, BIER WG <bier@ietf.org>, BIER WG Chairs <bier-chairs@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/h-CWXu5YM-8Lrwtmg9kY2VX4DaE>
Subject: Re: [Bier] AD Review of draft-ietf-bier-te-arch-09
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 21 May 2021 14:38:55 -0000

On May 18, 2021 at 5:41:00 PM, Toerless Eckert wrote:


Toerless:

Hi!

Just replying to a couple of things.


...
> > (1) What is this document specifying?
> >
> > To start, I believe it is ok for an architecture document to be in the
> > Standards Track.
> >
> > As far as I can see, this document mainly specifies alternate semantics
> > for the BitString. Beyond that, the BIER-TE architecture (=C2=A72) maps=
 well
> > onto the layering described in =C2=A74/rfc8297, where the BIER layer (=
=C2=A74.2/
> > rfc8297) is "replaced" with the BIER-TE Control Plane and the BIER-TE
> > forwarding layer. =C2=A0Is this a fair high-level representation of wha=
t is
> > defined in this document?
>
> "replaced" is certainly how the doc is written, so as to make it read
> as simple as possible. The intent of course is to "amend" BIER by sharing
> as much as possible with it such that a joint BIER/BIER-TE implementation
> is but slightly more work than just a BIER implementation.

Simplicity is good, but being clear is better. =C2=A0I would like to see a
list of the things in the BIER layer that are not replaced. =C2=A0I
remember text about the differences -- think of something similar for
the things that don't change.


...
> > The BIER-TE topology is a "key new component in BIER-TE". The document
> > doesn't specify, explain, or leave out of scope how "BIER-TE Controller
> > discovers the network topology and creates the BIER-TE topology from it=
"
> > (=C2=A72.2). This omission is a significant hole in the architecture.
>
> How about this. As long as it is clear that no references here are
> normative, but all informational (like any similar references in RFC8279
> that are all informational too).
>
> | In statically managed networks, such as in industrial environments,
> | topology discovery may be a manual/offline process. In other networks
> | topology discovery may rely on protocols such extending the LSP IGP int=
o
> | the controller itself, RFC7752 (BGP-LS) or RFC8345 (Yang topology) as
> | well as BIER-TE specific extensions for example via draft-ietf-bier-te-
> | yang. These examples are non-exhaustive.

Sure, that works for me.



...
> > (2) Can BIER and BIER-TE really coexist in the same network?
> >
> > The Abstract mentions that they can:
> >
> > BIER-TE can co-exist with BIER forwarding in the same domain, for
> > example by using separate BIER sub-domains.
> >
> > The result of separate sub-domains is more akin to ships-in-the-night t=
han
> > having them be "mixed": in the same sub-domain using a single BIFT
> > (populated by different sources). Is this correct?
>
> The way in which the BIER-TE draft defines BIER-TE forwarding, it is
> exclusively "owning" a BIFT. This is because the code, e.g.: Figure 15 sh=
ows
> the bit-reset semantic for all bits to use BIER-TE ([1] vs. [2]). So, wha=
t
> you call "mixed" is not part of the draft.
>
> Of course, implementations can easily build a single implementation of
> forwarding across BIER/BIER-TE, even with semantic, BIER vs. BIER-TE
> different for every bit, but to me this is just implementation optimizati=
on.
> Reason is that i have not identified good operational benefits to make th=
is
> part of the BIER-TE architecture. (aka: use case with some bits using bie=
r
> othre bits in same bitstring using bier-te bit-reset logic).
>
> However, your ships-in-the night semantic is probably incorrect.
> Even BIER alone can already have multiple BIFT per sub-domain,
> because according to rfc8279, you need a combination of (sub-domain, bsl)
> to map to a BIFT, not just a sub-domain.

Does this mean that multiple BIFTs could exist in the same sub-domain,
some using only BIER and other only BIER-TE? =C2=A0If so, then that should
be the clarification: they can coexist even in the same sub-domain as
long as the BIFTs are separate.


> Here is suggested text to help clarify:
>
> | When BIER-TE is used with rfc8296 encapsulation, the bift-id identifies
> | an SI, a sub-domain, and a BitStringLength (as specified in rfc8279) AN=
D
> | whether to use BIER or BIER-TE forwarding for this bift-id.

Hmmm...that may be locally true: the local node "knows" how the
adjacencies look like and how they were populated, but the BIFR
doesn't. =C2=A0Even if the controller programs the encapsulation at the
BIFR, the meaning of the BIFT-id field is not changing. =C2=A0I think this
text raises more questions.

Also, the text above seems to have an implication on BIER: "When
BIER-TE is used...AND whether to use BIER or BIER-TE..."


...
> > (3) Organization
...
> Let me see if i can do the reshuffling without having to completely rewri=
te
> explanations (stuff was put in order of explanation dependencies).

ACK


Thanks!

Alvaro.


From nobody Sun May 30 09:05:44 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: bier@ietf.org
Delivered-To: bier@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C2F33A40AE; Sun, 30 May 2021 09:05:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: bier@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.30.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: bier@ietf.org
Message-ID: <162239074147.4752.12152120273349404619@ietfa.amsl.com>
Date: Sun, 30 May 2021 09:05:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/qZdRfkpWCVizIiHR9uCSOL4_VVQ>
Subject: [Bier] I-D Action: draft-ietf-bier-non-mpls-bift-encoding-04.txt
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 30 May 2021 16:05:42 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Bit Indexed Explicit Replication WG of the IETF.

        Title           : An Optional Encoding of the BIFT-id Field in the non-MPLS BIER Encapsulation
        Authors         : IJsbrand Wijnands
                          Mankamana Mishra
                          Xiaohu Xu
                          Hooman Bidgoli
	Filename        : draft-ietf-bier-non-mpls-bift-encoding-04.txt
	Pages           : 6
	Date            : 2021-05-30

Abstract:
   Bit Index Explicit Replication (BIER) is an architecture that
   provides optimal multicast forwarding through a "multicast domain",
   without requiring intermediate routers to maintain any per-flow state
   or to engage in an explicit tree-building protocol.  The Multicast
   packet is encapsulated using a BIER Header and transported through an
   MPLS or non-MPLS network.  When MPLS is used as the transport, the
   Bit Indexed Forwarding Table (BIFT) is identified by a MPLS Label.
   When non-MPLS transport is used, the BIFT is identified by a 20bit
   value.  This document describes one way of encoding the 20bit value.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-bier-non-mpls-bift-encoding/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-bier-non-mpls-bift-encoding-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-bier-non-mpls-bift-encoding-04


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Mon May 31 06:29:34 2021
Return-Path: <martin.vigoureux@nokia.com>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58F913A1857 for <bier@ietfa.amsl.com>; Mon, 31 May 2021 06:29:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.698, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=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=nokia.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 thvANZYuGy_C for <bier@ietfa.amsl.com>; Mon, 31 May 2021 06:29:17 -0700 (PDT)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-he1eur04on070d.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe0d::70d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A89B3A1861 for <bier@ietf.org>; Mon, 31 May 2021 06:29:17 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=SgYlKUi3xCRR08/0Iy20pVkLDk+CE/a1grBMegq3v16JqMyu8lOitkKtjNKRugjGpZoW/eWprO24b4Lg22JsEwUoo5ACJ5+kqoSXlyMUyMD85hsyruB+E0oB12v9+u8YUTTUg4iQrGzLRb8WK3YzeL+hGoJMiyd5Lk/SpMXqFUzgVAC+aGNPpIj+1NYKnai5Z7EmUJ/f2McO6g9lfWKSTKHAp/yTvnJbX9RY+jv8whlxGAXLqAR9mxx0kX4OC4di6caWcgbTZFy4HATqLwSNr2iIAPmtAajlHcu0x2Yi5hwsN4XUB/6RMN6XCmfWIJ7Gd4KWQEpY1jSboqllEIU1yA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=IpWccT9E3g6ao9x2Y2RW67H+EZ7Aamls/j9ZfFq9GbM=; b=j6LGSH08mDsUYqD8vmMpUiWbM78XesND8EtIzmOW96hSMC8StF2dcl6U0wC5+XMlwX7qVSuMeekQKdw0Wq2zrWeLwzV1Z/eFNYFQBFHFhk82YKpLZyjpeBdM3WxZWYTN7/3jEcr0yBZbIpxbH5QbZtVoDb9JTBlfNrFtyWpC/dZze4Yxm8eIaETxDtpI3bo8c1Icg1CM+4hz+dP7F2DnI3pVAJvqV4pCPB2YuDeXglX/3gVts9AOgHWTbeFXkMNPQym1G2xtscbrkl4Lpfk718qfWCPMeZ3+AA0HRtCz1kqmtPcPByxwGg7sB/E1TrVYsiK4tQBUR0jWt8RnRdeqsg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nokia.com; dmarc=pass action=none header.from=nokia.com; dkim=pass header.d=nokia.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com;  s=selector1-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=IpWccT9E3g6ao9x2Y2RW67H+EZ7Aamls/j9ZfFq9GbM=; b=owEZKOr9zCvscC2Y4H75RkaVH8k6t2vbKPKPuQ1M63hgv7btdqtfqkxSOKA2bIrLD+/dEy5A3XgL+VDZXjtzTJvrgt1F3cj+Qcfl+l+SYFlgQtrFE8xVmUCDVWAO07T2vDVy5Ij6qMbWHQnk1Xd6+WU9w0u5fcUroPcw16OFO9k=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=nokia.com;
Received: from AM6PR07MB5560.eurprd07.prod.outlook.com (2603:10a6:20b:6f::22) by AM7PR07MB6946.eurprd07.prod.outlook.com (2603:10a6:20b:1b8::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4195.12; Mon, 31 May 2021 13:29:13 +0000
Received: from AM6PR07MB5560.eurprd07.prod.outlook.com ([fe80::79ba:ddfb:6bf3:9a66]) by AM6PR07MB5560.eurprd07.prod.outlook.com ([fe80::79ba:ddfb:6bf3:9a66%5]) with mapi id 15.20.4195.017; Mon, 31 May 2021 13:29:13 +0000
From: Martin Vigoureux <martin.vigoureux@nokia.com>
To: bier@ietf.org
Message-ID: <a2a82830-faf2-0992-c4bf-b02cdb8e6e4c@nokia.com>
Date: Mon, 31 May 2021 15:28:58 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
X-Originating-IP: [131.228.2.21]
X-ClientProxiedBy: CH0PR03CA0243.namprd03.prod.outlook.com (2603:10b6:610:e5::8) To AM6PR07MB5560.eurprd07.prod.outlook.com (2603:10a6:20b:6f::22)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [172.30.2.231] (131.228.2.21) by CH0PR03CA0243.namprd03.prod.outlook.com (2603:10b6:610:e5::8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4173.21 via Frontend Transport; Mon, 31 May 2021 13:29:11 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 4a4ba2c5-1f2c-49a1-5179-08d92438147a
X-MS-TrafficTypeDiagnostic: AM7PR07MB6946:
X-Microsoft-Antispam-PRVS: <AM7PR07MB69466F338094A0D024929C6F8C3F9@AM7PR07MB6946.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:9508;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: nkRVSmE2bsAKOSz2NqxG9eiiQU+J9jeGpIPy1GdzSbhMxfyprw2NoZzwSgYFtXzPKXQBKpizOHuGAgXc8FO6K4bfjQe5ALN4yG5CxmsU98KVYe0CmY3l6Q1Gu+QYiGnMXMHP/d03OU2/Jk2d9kz8t0lhOtOY2TiNJ3+QzCEoAWEcWfj80aPYZaEdCG9icozBOPuiXRyhz/XVomGzSv9aap9FEGfYyIqn0AyhRTZ7UAa7oOgUivxMOm32H2vPtegU1P8cVUTJ/57QE0HPqLseFrk0mu4QN5o7SCC/BZKa9hPMwvxDOuGmsoWRvd4BV87apccYw1cy1eFf9QnymQLXpHft8wkxlHjd37EAn1bJCOQUTrA49SOTaB4aPxYeHleqLDltNZWy+lybrR/N4mpWoemTScAS3hLeooVPYBxx6jn0lNWaVaa/0bUX/dNwY07VaQhSSw3AOjN9d9QmZbE7P12ZGZyRSwEZPTeZqLJL2GVHMfSRM5oejMbVsMwSWlmn26D2Qz6YRsIRao3MM8MV5MhDToUzz/Hjfe+HaiCLoQHbzG42PlaeU7xaqumNaFyIsynpLd2c3AZ4tOtSXXswZQA+zh/9mOh+kT6J3l82p68L6n8U4RsFpTo/JRHoKvuSDVF3yCI+ULHcosba4tuyRuP1Lmqgrm+zvQBC5VfsLz2psSegNgfmvFaRQl/OCUUQUiTsdmvWfjPERXF4iT/ssJ4pMY7XlIPmV2SOkL/EDmmM0rC2apl16QxOYOKYR89D
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:AM6PR07MB5560.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(346002)(396003)(366004)(376002)(39840400004)(16526019)(5660300002)(186003)(26005)(8936002)(36756003)(44832011)(52116002)(38100700002)(66556008)(66946007)(6486002)(66476007)(38350700002)(2906002)(6916009)(8676002)(86362001)(16576012)(31686004)(956004)(6666004)(2616005)(34490700003)(31696002)(508600001)(45980500001)(43740500002); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData: =?utf-8?B?TDJDV0lrSWRqeGlrYVhCcjU5aTAxVHIwRHp3eVFjTzh1WWNMTFczN0l6RGZs?= =?utf-8?B?UFRESkdXK3QvcjF2Y2RBVURhU1J6L0xtV0lKaVBDbnlhZGtaWmxueS9rVlU2?= =?utf-8?B?dFpGTDM5Qng5OVlaVlBoNWNvTVRFWXdLTWhpanAyY3Q4OVNldk9KOHlOdFFy?= =?utf-8?B?ZEwvTVZ1QjV4Y2dubFIvT09iM3hzSUw0aE1xUmRvWVEwRklHMXBBSDBLYnJR?= =?utf-8?B?cFRqZ3JoWkFudXNLTFh6VVhsTmFsVzdzaUZlR0krRlpLcTZNMVNrb2UzNklZ?= =?utf-8?B?aFZDMEpNenZydzl6NVZmQmdubHlNWnExSWN2WllSSWFZd1JCM1NQbStCVlh4?= =?utf-8?B?SzJLZ2w5Z2tqVklzWTdQK2tYSi9FbXBPdDZhOEhLZ1o4NmFmNVNVZXRIbmxz?= =?utf-8?B?eHlzUXN2b3RLZmR6bll6WUw5blRUN295UkZaSElnRXUvcVlXM2VBY0s0RVJi?= =?utf-8?B?T040NG9XTTlvNmlWa2xGOTI4eE1USzJLc2xVSnFJTC9yL01nQnJqM20vN2ox?= =?utf-8?B?a1dHUlhkdlhrOW9sRW5aNHZWYWh1T2liTlpucXlqUVozL1pGaUhLdWtGc2Rm?= =?utf-8?B?OEo0a0Z3RUR2WGZMVC9VbHlKR1NmcjE0dVl6WGVDRjZUQmZ2c2VoeTY5dHVP?= =?utf-8?B?WVl1cGFsR0FDcllOczVxRTlzcjRJT2ZUdldEcW9WbE1KMDJwcTNjdWh6MzJY?= =?utf-8?B?N1BpVTg3aWE1Yno3ZnVVYm5zcW9kcWpKTHYrbFpqK21QRDJ4UCtHN2RRazhu?= =?utf-8?B?U2FDMjlLUmJMMVlnam05UWIxUVZqTjJDb0Jsa1NwaUZPR0UxNTAwUEJ4TWx3?= =?utf-8?B?eXdIK2x3ZUpaTG9iWEpQMThBWkZTOXBSK1d2MG41aUNoWHQxR2FuRzVSWFVP?= =?utf-8?B?cGp4RG1Xd3hHWURzYkp0ajVwRFlIMUc1NmEyV3ZHWGtJZDBUWlFNM3F6QWt0?= =?utf-8?B?dThKY0FlQjRsNHpZWE9vakhFdERPR1M5dHpmcmJqakJqNjZ0NjZoVlJpSUlR?= =?utf-8?B?WTRGeDRhSE1IQkpnMm1BVjY1R0xlWXFzUWJ0NUtZRHZKSm51V2JMZk9aRU1Y?= =?utf-8?B?NSsvRkdvMDNGamhiRHJFenRMdU5oS0lNWmYydmxma0MxcHpsTmg1NnpWL0dG?= =?utf-8?B?SzZKd1k3Y2JGaE1sZzdEMkgrM08vWWVnVk9JTU5XSlJZUS9jRUxTdk5remF2?= =?utf-8?B?TXBIUHl0TVZFbDQyZG9HOThrQlFhQUFyY2pwM3FFbk4rYTJnWmltTFI5V0tW?= =?utf-8?B?TnR1ZU5kZVpidEVqWEdsL1ljWm02U2dIdUdURnJYaVNGQWZvajQ4Y2NuRjAr?= =?utf-8?B?S0R5RnJ6Q2V6STh4OURiREs5ZWdYVDZ1bCtkUDNDRHBERXNnN2hWTHBzNi9H?= =?utf-8?B?RkU2UENFQStVeVlIa256VlBjTXBIUm43OEZiRFlHVlFvMEIreUlZb2JSZEFP?= =?utf-8?B?aFRVSy9LZGNjRFdxdU1WakJvY1NPNmMrMFRISmxYemk5M3lMZE52dlU0UFdW?= =?utf-8?B?VEJIbFpDZnpMN0IwWHpCZ0tCWUgzODV4N2VpWmZUMXM4UzNTaDZqTWtOaWRY?= =?utf-8?B?d0dXYS9QUGNmTjFXRHVDOXVuZ2c1NlVlSE5CeEpPcHE4eHB3L25vZnVvVG1Q?= =?utf-8?B?dys2OG53OFJrL3V1NzNIam1GNGpnTmZGUUk4bDRxUzdmMHEwY3Z0KzVLY010?= =?utf-8?B?WG5XOXRuS2cxMHcvRGtObXR4RDIxQ1lacGlaV1JCTW5FbjRvQmdndnJvS241?= =?utf-8?Q?IV+tbnUY41LFWpEQNHK5iICq8mHG2sub+HPXvCN?=
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 4a4ba2c5-1f2c-49a1-5179-08d92438147a
X-MS-Exchange-CrossTenant-AuthSource: AM6PR07MB5560.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 31 May 2021 13:29:13.1204 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: d14mJv7yqRhJ34hdXAXQBBAL2E+YDnBtUNMgrHOZJ81T1n11+waZPPo+i1DE84BZt2Pe1JLmKzsLYucJrwOc+3bKRhaJ+g1/NOACAibDjaY=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM7PR07MB6946
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/67Xxny9_742Ks0TjEIrEo3mWY3U>
Subject: [Bier] In reply to the formal complaints
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 31 May 2021 13:29:32 -0000

WG

First, I'd like to apologize for the time this has taken.

I have reviewed the two formal complaints that were sent early March, 
and I have also reviewed most of the e-mails that were sent on the bier 
mailing list for the past 12 months or so, relating to BIER and IPv6.

I will not individually discuss the various points raised, rather I will 
make a general statement.

It is my opinion that a certain number of points are not critical (in 
the sense of not needing an AD to step-in) and some typically happen 
sometimes as part of the life cycle of WGs. Yet, I do recognize that 
some points are more problematic than others.
Further, it is my opinion that the points listed may arise from a 
variety of intentions and as such it is hazardous to associate them with 
a particular one.
It is however my opinion that the multiplicity of concerns is, in 
itself, a concern.
I have talked with the chairs. They do recognize that, at some 
occasions, their communication was not the most effective one, and I 
trust they will pay attention to that in the future.

About the adoption poll on draft-zhang-bier-bierin6. Although the way 
this was handled raised some concerns, I'd like to remind that an 
adoption poll is not formally part of our processes, even if it is 
common practice, and in fact it only marks the start of the WG 
discussion. As such, I have little arguments to go back on this.

The last part is about the progress of a so-called BIER v6 solution. 
Here, I have asked the chairs to establish a summary of the discussions 
regarding that type of solution in general and regarding the specific 
document which proposes a solution. They should publish it some time 
after this e-mail.

Following that, it is my expectation that the WG has a fair and open 
discussion, ideally focussing on the general aspects, and then concludes 
on the way forward.


Martin


From nobody Mon May 31 07:46:41 2021
Return-Path: <acee@cisco.com>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 861223A1A9C for <bier@ietfa.amsl.com>; Mon, 31 May 2021 07:46:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.596
X-Spam-Level: 
X-Spam-Status: No, score=-9.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 header.b=QDp44Mco; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=zQCiIJsP
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 GGrePuRq8h80 for <bier@ietfa.amsl.com>; Mon, 31 May 2021 07:46:34 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80A193A1A98 for <bier@ietf.org>; Mon, 31 May 2021 07:46:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4156; q=dns/txt; s=iport; t=1622472394; x=1623681994; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=kUCkzui0PjkZpVSebIwZS2MFtDwM3x0sKYGSOpozjbU=; b=QDp44McoQSuagxHKfd2aVJ3TDnALA7ET6q9CZcS+9Rmv3Ipp04kDezYh J4kpXUOu26qqlRxOqQkpnX882ugOpg2vS0lKwinHrNO2v5YKLYZ2MfNvI pRCB2/tSwvpwbEZiwRz37HP7X4ahs54jlQ9zjfnwvORjPVI+nmVTLSh67 0=;
IronPort-PHdr: =?us-ascii?q?A9a23=3A852BHxTE3ijT+DNDVFY0gP3WH9pso6HLVj580?= =?us-ascii?q?XJvo7RJcaWquZ/lOR+X6fZsiQrPWoPWo7JBhvHNuq/tEWoH/d6asX8EfZANM?= =?us-ascii?q?n1NicgfkwE6RsLQD0r9Ia3saC87FYJJU1o2t32+OFJeTcD5YVCaq3au7DkUT?= =?us-ascii?q?xP4Mwc9Jun8FoPIycqt0OXn8JzIaAIOjz24MttP?=
IronPort-HdrOrdr: =?us-ascii?q?A9a23=3AR+doPKt1S0zvdhcdKX3KCzkl7skCuoMji2?= =?us-ascii?q?hC6mlwRA09TyXGraGTdaUguyMc1gx/ZJh5o6H9BEEZKUmstKKdkrNhQotKOz?= =?us-ascii?q?OW+FdATbsSo7cKpgeBJ8SQzJ8k6U4NSdkaNDS0NykGsS+Y2nj6Lz9D+qj9zE?= =?us-ascii?q?nAv463pB0BIXAIGsNdBkVCe3ym+yZNNW577O8CZeOhD7181lydkBosH6CGL0?= =?us-ascii?q?hAe9KGi8zAlZrgbxJDLQUg8hOygTSh76O/OwSE3z8FOgk/g4sKwCzgqUjU96?= =?us-ascii?q?+ju/a0xlv3zGnI9albn9Pn159qGNGMsM4IMT/h4zzYIbiJGofy+Azdktvfrm?= =?us-ascii?q?rCo+O8+ivI+P4Ds085S1vF5icFHTOQiwrGpUWSk2NwykGT3/ARDAhKevapw7?= =?us-ascii?q?gpLycwLyEbzY5BOGUh5RPEi3MfN2KyoMy2jeK4Jy1Chw66p2EvnvUUiGEaWY?= =?us-ascii?q?wCaKVJpYha509NFowcdRiKpbzPPdMeR/003swmO29yrkqpyFWHy+bcEkjb3i?= =?us-ascii?q?32CnTqn/blnAS+sEoJu3fw9fZv10vorqhNPqWsz960RZiAuos+PPMrUQ=3D?= =?us-ascii?q?=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CPCgCM9bRg/4UNJK1TBx0BAQEBCQE?= =?us-ascii?q?SAQUFAUCBV4FTUQd3WjcxC4Q9g0gDhTmIRSWaD4FCgREDVAsBAQENAQEqCwo?= =?us-ascii?q?CBAEBhFACF4FnAiU4EwIEAQEBEgEBBQEBAQIBBgRxE4VoDYZFAgQBARAREQw?= =?us-ascii?q?BASwMDwIBCBoCJgICAiULFRACBAESGQIHgk8BglUDLwEOnBYBgToCih96gTK?= =?us-ascii?q?BAYIHAQEGBASCTYJSGIIxAwaBECqCe4QOhmEnHIINgRUnDBCCMC8+gmIBAYE?= =?us-ascii?q?iKYMsNoIugWl2TwQDUCA4AwEpDFIeAhBhi3qFBYM9px8KgxmXGoZPBRwJpVi?= =?us-ascii?q?VR6QiAgQCBAUCDgEBBoFrJIFZcBU7KgGCPlAXAg6OH4NwhRSFSnM4AgYBCQE?= =?us-ascii?q?BAwl8iBcrgQsBMQFeAQE?=
X-IronPort-AV: E=Sophos;i="5.83,237,1616457600"; d="scan'208";a="873100502"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 31 May 2021 14:46:33 +0000
Received: from mail.cisco.com (xbe-aln-003.cisco.com [173.36.7.18]) by alln-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id 14VEkXx5007032 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 31 May 2021 14:46:33 GMT
Received: from xfe-aln-003.cisco.com (173.37.135.123) by xbe-aln-003.cisco.com (173.36.7.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.792.15; Mon, 31 May 2021 09:46:33 -0500
Received: from xfe-aln-002.cisco.com (173.37.135.122) by xfe-aln-003.cisco.com (173.37.135.123) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.792.15; Mon, 31 May 2021 09:46:32 -0500
Received: from NAM04-MW2-obe.outbound.protection.outlook.com (173.37.151.57) by xfe-aln-002.cisco.com (173.37.135.122) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.792.15 via Frontend Transport; Mon, 31 May 2021 09:46:32 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Fs9J07NKcqI1GO6X+PyBD5bC9RduGU08OmKlL3fiUCa1e6Pe2TlIJYqVLejIMibr1ZVZ74UfLNVoSsHBlo8nyttJaqLmKR5WJDxF7HBtUDeCds78+PgFoGpqKWbfhENgn+g+CciReKwTC/+UU+yrIKXjeTxrtCjW/oN3x0Eye1EsgwX/do4wGKqOkcljE63aV0r5OVjcctfTGzpF9A+kpkEMvKfpfb69Ll7dt+Vy4o6NghE45I+uVa3VuN3n6kCul7ynuhPyngZqMYf1RQlteMsgTZ79ggWvw+faMM2QXhIlAIKTmRlNezLFgzyK4wGvUXGek/YXintNUSl6qakw/g==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=kUCkzui0PjkZpVSebIwZS2MFtDwM3x0sKYGSOpozjbU=; b=af/iUXJ7stXPajHI6TvLphDuvGeTGfglDkinzWsekxv0WwyQCE2nCGeWPrTQIOXRPgLgaVTlwIoUvwM0wgmcXAbMDYr82uHB98cBNYK7EFPyLQf5PrvapJeqaI6FB/qN5VPSjq5hccDX+iVCSuYR0567c85iOf2f4XBRqPpaY29uV9iaRhUt4uMQOW04AgiGY1dVTzrQkPCpb5/DKc92S1vq9curKHme9S5HdnbXrFPPByZm7wFGrTEYnzQP1pO5pCo1cx2C/Tm2erToSMg6KIPaSa/5qVbVbHmT3RsR3cEbg5goz/LiOiGmK7yeqvyFRarpbFfw1vIsVPQuJomtUA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com;  s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=kUCkzui0PjkZpVSebIwZS2MFtDwM3x0sKYGSOpozjbU=; b=zQCiIJsPzUAlwqd8AhlOLgmF0ZLgMnwuujB2kRHPH/7EKGxWUBTgcLtqN2uwGFZTL3eh1bQ0n0Wtn/zFVJS/C3rSB+/tS0wMAzvcaFfDfGXFPKjUNt+59f0Uq/iJvWztc8YTLoKiEJ1ZczNU+Us/GWVoZXV6olxL4uOCsVb6TEM=
Received: from BYAPR11MB2887.namprd11.prod.outlook.com (2603:10b6:a03:89::27) by SJ0PR11MB4832.namprd11.prod.outlook.com (2603:10b6:a03:2dd::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4173.20; Mon, 31 May 2021 14:46:31 +0000
Received: from BYAPR11MB2887.namprd11.prod.outlook.com ([fe80::e98f:cd3e:b6d:6f9d]) by BYAPR11MB2887.namprd11.prod.outlook.com ([fe80::e98f:cd3e:b6d:6f9d%7]) with mapi id 15.20.4173.029; Mon, 31 May 2021 14:46:31 +0000
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Martin Vigoureux <martin.vigoureux@nokia.com>, "bier@ietf.org" <bier@ietf.org>
Thread-Topic: [Bier] In reply to the formal complaints
Thread-Index: AQHXViEHX9eORVUojEW2G4tCWLecQKr9aCsA
Date: Mon, 31 May 2021 14:46:31 +0000
Message-ID: <E399E493-093A-4615-AD9E-04EE059CD756@cisco.com>
References: <a2a82830-faf2-0992-c4bf-b02cdb8e6e4c@nokia.com>
In-Reply-To: <a2a82830-faf2-0992-c4bf-b02cdb8e6e4c@nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/16.49.21050901
authentication-results: nokia.com; dkim=none (message not signed) header.d=none;nokia.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [136.56.133.70]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 0d5eb44e-e9c0-4d1e-cc9d-08d92442e157
x-ms-traffictypediagnostic: SJ0PR11MB4832:
x-microsoft-antispam-prvs: <SJ0PR11MB4832B92614722A0D56A16D21C23F9@SJ0PR11MB4832.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: ZnDy39H1Ybt5SV2ZIH2xzEH2FmtOEGghug/PzSzaWBThv+V7eOwEFqXKvAsOMAX49aU/m4hhwMa0PZF4rv8yDBlVOeqNubQbZXRs7V3SGRKbkXi7w+Kp/qvomM2Z6gZF7x2ga8SK1BjftNxDQqjFL91B1/pY2EnToiM4Pj0X9TTKOKM5WSKnm9YOCARrn3k7dcT1NxNcnf7ImcKJoINR2IxgxLslYzhhRQwMSEw8s6T2PTzZfIq0Kt+lf+ByWtr4+p/yZB6zydsGFAuVBuLz7iwaNWUkf/KKJXu33AAAhvfvfQCzPxkwWrVjswNOnix5nXonp2BT1kHO5fEi/pohq2ATP1YJdO/XvjNNSgx3iO1TQzzMe3Bl+LoaX597y9XfDeVhBBu7ogYs0xuWrckGPvqYcs+fveNysRcrKNHk/TthJxQuUUFMWJF1D56VzKlfprQ4qUC4OuvRrmcODs7qXyK6fgj0+435RNyi34HaJfPfBzSw6zJVOxXyN8IT/ox0o9MQytpoRvJcEur+d+RY9N4H5Bdnjr4+yjrIpp+qVXJulk/vYfqUhR1/TM4h2hb30My0OfjFqmzeYpijwHtZ15cp/BoeXn2oOKFE0c1z2QGCb5WHbQrYE2NIL1Aq9qs14CF5FVP0NzfVILUiuuQUQyrHZpPLjLK/SiS0XN8mRuOTJGvI4+DlpGW/BlOnNMokgc0fyAjbxSTXLul57vwYDDp17/TsbwMlWbKEDAV1uVFzCHfks3P7N2b/9t6xmfmfITuSu7BijOyrPvH+ta05pA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:BYAPR11MB2887.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(396003)(346002)(136003)(376002)(366004)(39860400002)(66446008)(86362001)(2616005)(478600001)(966005)(66476007)(296002)(26005)(5660300002)(2906002)(83380400001)(186003)(316002)(33656002)(6512007)(66946007)(6506007)(6486002)(71200400001)(122000001)(38100700002)(91956017)(76116006)(8676002)(64756008)(66556008)(110136005)(36756003)(8936002)(45980500001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?bm1saXJLSHlNQUdLMnhoTitNaHJNSDJUTjFlL3g0MllqL0xuekFNaUE0OFhu?= =?utf-8?B?a0xFTHdPUWt6N2NuQ3plajlvQW9UdjlhSWZqTVJJT3VwQ3JYTnZFOEsrU0hX?= =?utf-8?B?QXhVNGEySzNFbVM5anU1OGlPWithQnFtbWdFbDB5a1JOQ1YvR3lYRHVyUFBB?= =?utf-8?B?TmttcElDUkp0bVNUR0xVN25TS05EV3RwTmdldWNhOWtuR0RlT2Fub0NXK0tQ?= =?utf-8?B?aGNjL3Q1MFFYdkltYkhaSkpEd0tFWXZyNm5tNEovN1JYNGIzdzZxaG0vS21C?= =?utf-8?B?dHI4Um91RW1HRUN2UkwvTWw1enFKWEpPaVkzbzJhbXZZdWtQQklmT0V4SE5z?= =?utf-8?B?NFo0QVB1UEprd2FWV29ybEtmK3pQSzRRZFBBbWg0YXg3SWNJV056d0R3VUxw?= =?utf-8?B?KzZKcURXQzdmTkxjZzB5aTBsTFpVS0lKTzcyZWlPaEt2RVY3RVNGVXUreDhp?= =?utf-8?B?emJVanhaMHNacUVCRExPVHpBTHY1c2Z0VlQ3YzhQRzEwcWM4SzZBY2VBSENr?= =?utf-8?B?ZVpSbXdsUXRCN0ZQWU5IOFUzQ0xOUWwrWUNpVEZPMlhVOGtOZk1qMThYb2dD?= =?utf-8?B?Sktxdzl0MVE4Um5tbDZhTjE2Y0xtM0t4UGJXWng0dXVMVDVPeW9sRytHeWdh?= =?utf-8?B?eFJsVUNmWEo0eHRZN1NBZFFHY3JKeUZmdmpWakpmWERDUkh3RHpNMDVXUVRB?= =?utf-8?B?WW1VWEZKK21xVGhCS2o2Nm43L2ZrTXFRQ3NTQlBQOVNmZC9oVEJuY3V0NnNw?= =?utf-8?B?bmxaZ0pkNGZ3ZnkrdktHZVFQY0FuY0VmZnlqRklZSDFtdHFrbjVvUm9vYTJy?= =?utf-8?B?czVkbVBuVGxnYUFMWWc2VC9CR2pnZGpKYWtUZHFSbjZWYjBiUDBaREhFak5w?= =?utf-8?B?UVQrbFdGNS9vaWY2Uy9UQ0puTFZqZ1VCRFQ0RU9wWk9WSzdFVC9rVXgzSzZC?= =?utf-8?B?b3dMZVRseC9aWHg5Tnd5U1NJTVRIMlZVL2szMThpWXJjckVyaGk3Wnc3Mkts?= =?utf-8?B?Y0p2U1ZrajcxNWtBL2ptUkZqcUF5Ulk1Zk5lN1ZmeEFtNTUyZTU4cExGS1V6?= =?utf-8?B?Zmk2bzJIL245K1NCZm1HMENjMG1FT1hxa0RvR2E3cWxmV2hXOFhDWXR5ay82?= =?utf-8?B?Wmd1VmJpWHMxV1k2Nzl2aDZrclpaaUhsd2M1aUVRZ1pLSmpCV2dRVDlKZE84?= =?utf-8?B?RHppWDZ1dHRJUUNrSE90RXoyVWZWbmN3ajVZbmFWdGhjbXd4VlBpUm5FUEI3?= =?utf-8?B?eDZDTk5pNzBuN0tUcUtsUG0xeVM3bkV2OXpzci9TelhrVi9PQmhWM3FSajRC?= =?utf-8?B?SFFEaGZrK2hncXZ2d2RNTnpWZHZrOG81R2wwdWVZcThHSjVueHZqWVRZZ1Vw?= =?utf-8?B?b3ROZWRSeE9oc0FEM0xnQ2VQMGNzQXI2NFc4NEVCUGlUZUhENVE4TG1HNjlH?= =?utf-8?B?bWFXZW5qdmF0bytneDYvTVpYTjhSMjlpQ0h4T0JQUG9lNjBvRU9scUJldWl3?= =?utf-8?B?b1dVRVVSMXRmS0dRSjFmZlBtaEJqUW9PVzA3bGptWXVCZXNva1YvaE00aTVJ?= =?utf-8?B?VWlRTytIMktkRmFuck9XZWVEWnUydlNpWFo4Uk9XdWFrcEdkaXpyWGhrT25Q?= =?utf-8?B?SW8zT3IwK1BFZFJ3RERMVER0cWp5TFZ2VzJjZVZNZlVlcDBiRFcrR3JRTmxR?= =?utf-8?B?MFE5V1B3ZSs0b2pwUjR5UU9ZNFh4OFR6bGxGSGsvdENab1lUcW81WUJZREZQ?= =?utf-8?Q?gt4004GZYp6IpA8BV+/O7YvFpJjXHZ93tFWf4mL?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <A83EB4A4BA917A4FBDDCDF2C995F4503@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BYAPR11MB2887.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 0d5eb44e-e9c0-4d1e-cc9d-08d92442e157
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 May 2021 14:46:31.5645 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: /O5ubdNN+zW4EUVuKvLfWbjmsOrmywbWZPoT4k1PLUSFWEP6bFrPN/gbTo/9th3u
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SJ0PR11MB4832
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.18, xbe-aln-003.cisco.com
X-Outbound-Node: alln-core-11.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/MAH67j3DrFfoOISlkXMbq9UGhok>
Subject: Re: [Bier] In reply to the formal complaints
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 31 May 2021 14:46:40 -0000

SGkgTWFydGluLCANCg0KVGhhbmtzIGZvciB5b3VyIHdvcmsgaW4gZXZhbHVhdGluZyB0aGUgZGlz
Y3Vzc2lvbiwgY29tcGxhaW50LCBhbmQgYnJpbmdpbmcgdGhlIGlzc3VlIHRvIHJlc29sdXRpb24u
IEknbSBzdXJlIGV2ZXJ5b25lIGNhbiBhcHByZWNpYXRlIHRoYXQgaXQgd2FzIG5vdCBhbiBlYXN5
IHRhc2sgYW5kIG9uZSB0aGF0IHJlcXVpcmVkIGNvbnNpZGVyYXRpb24gYW5kIHJlc3BlY3QgZm9y
IGV2ZXJ5b25lJ3Mgb3BpbmlvbnMuIA0KDQrvu79PbiA1LzMxLzIxLCA5OjI5IEFNLCAiQklFUiBv
biBiZWhhbGYgb2YgTWFydGluIFZpZ291cmV1eCIgPGJpZXItYm91bmNlc0BpZXRmLm9yZyBvbiBi
ZWhhbGYgb2YgbWFydGluLnZpZ291cmV1eEBub2tpYS5jb20+IHdyb3RlOg0KDQogICAgV0cNCg0K
ICAgIEZpcnN0LCBJJ2QgbGlrZSB0byBhcG9sb2dpemUgZm9yIHRoZSB0aW1lIHRoaXMgaGFzIHRh
a2VuLg0KDQogICAgSSBoYXZlIHJldmlld2VkIHRoZSB0d28gZm9ybWFsIGNvbXBsYWludHMgdGhh
dCB3ZXJlIHNlbnQgZWFybHkgTWFyY2gsIA0KICAgIGFuZCBJIGhhdmUgYWxzbyByZXZpZXdlZCBt
b3N0IG9mIHRoZSBlLW1haWxzIHRoYXQgd2VyZSBzZW50IG9uIHRoZSBiaWVyIA0KICAgIG1haWxp
bmcgbGlzdCBmb3IgdGhlIHBhc3QgMTIgbW9udGhzIG9yIHNvLCByZWxhdGluZyB0byBCSUVSIGFu
ZCBJUHY2Lg0KDQogICAgSSB3aWxsIG5vdCBpbmRpdmlkdWFsbHkgZGlzY3VzcyB0aGUgdmFyaW91
cyBwb2ludHMgcmFpc2VkLCByYXRoZXIgSSB3aWxsIA0KICAgIG1ha2UgYSBnZW5lcmFsIHN0YXRl
bWVudC4NCg0KICAgIEl0IGlzIG15IG9waW5pb24gdGhhdCBhIGNlcnRhaW4gbnVtYmVyIG9mIHBv
aW50cyBhcmUgbm90IGNyaXRpY2FsIChpbiANCiAgICB0aGUgc2Vuc2Ugb2Ygbm90IG5lZWRpbmcg
YW4gQUQgdG8gc3RlcC1pbikgYW5kIHNvbWUgdHlwaWNhbGx5IGhhcHBlbiANCiAgICBzb21ldGlt
ZXMgYXMgcGFydCBvZiB0aGUgbGlmZSBjeWNsZSBvZiBXR3MuIFlldCwgSSBkbyByZWNvZ25pemUg
dGhhdCANCiAgICBzb21lIHBvaW50cyBhcmUgbW9yZSBwcm9ibGVtYXRpYyB0aGFuIG90aGVycy4N
CiAgICBGdXJ0aGVyLCBpdCBpcyBteSBvcGluaW9uIHRoYXQgdGhlIHBvaW50cyBsaXN0ZWQgbWF5
IGFyaXNlIGZyb20gYSANCiAgICB2YXJpZXR5IG9mIGludGVudGlvbnMgYW5kIGFzIHN1Y2ggaXQg
aXMgaGF6YXJkb3VzIHRvIGFzc29jaWF0ZSB0aGVtIHdpdGggDQogICAgYSBwYXJ0aWN1bGFyIG9u
ZS4NCiAgICBJdCBpcyBob3dldmVyIG15IG9waW5pb24gdGhhdCB0aGUgbXVsdGlwbGljaXR5IG9m
IGNvbmNlcm5zIGlzLCBpbiANCiAgICBpdHNlbGYsIGEgY29uY2Vybi4NCiAgICBJIGhhdmUgdGFs
a2VkIHdpdGggdGhlIGNoYWlycy4gVGhleSBkbyByZWNvZ25pemUgdGhhdCwgYXQgc29tZSANCiAg
ICBvY2Nhc2lvbnMsIHRoZWlyIGNvbW11bmljYXRpb24gd2FzIG5vdCB0aGUgbW9zdCBlZmZlY3Rp
dmUgb25lLCBhbmQgSSANCiAgICB0cnVzdCB0aGV5IHdpbGwgcGF5IGF0dGVudGlvbiB0byB0aGF0
IGluIHRoZSBmdXR1cmUuDQoNCiAgICBBYm91dCB0aGUgYWRvcHRpb24gcG9sbCBvbiBkcmFmdC16
aGFuZy1iaWVyLWJpZXJpbjYuIEFsdGhvdWdoIHRoZSB3YXkgDQogICAgdGhpcyB3YXMgaGFuZGxl
ZCByYWlzZWQgc29tZSBjb25jZXJucywgSSdkIGxpa2UgdG8gcmVtaW5kIHRoYXQgYW4gDQogICAg
YWRvcHRpb24gcG9sbCBpcyBub3QgZm9ybWFsbHkgcGFydCBvZiBvdXIgcHJvY2Vzc2VzLCBldmVu
IGlmIGl0IGlzIA0KICAgIGNvbW1vbiBwcmFjdGljZSwgYW5kIGluIGZhY3QgaXQgb25seSBtYXJr
cyB0aGUgc3RhcnQgb2YgdGhlIFdHIA0KICAgIGRpc2N1c3Npb24uIEFzIHN1Y2gsIEkgaGF2ZSBs
aXR0bGUgYXJndW1lbnRzIHRvIGdvIGJhY2sgb24gdGhpcy4NCg0KSSBhZ3JlZSB3aG9sZWhlYXJ0
ZWRseS4gSSBjYW1lIHRvIHRoZSBkaXNjdXNzaW9uIGxhdGUgYW5kIGJ5IHRoZSB0aW1lIEkgd2Fz
IHJlYWR5IHRvIGNoaW1lLCB0aGUgY29tcGxhaW50IGhhZCBiZWVuIHJlZ2lzdGVyZWQgYW5kIGRp
c2N1c3Npb24gaGFkIGJlZW4gc3VzcGVuZGVkLiBUaGVyZSB3YXMgbXVjaCBzdXBwb3J0IGZvciB0
aGUgZG9jdW1lbnQuIEZyb20gYSB0ZWNobmljYWwgc3RhbmRwb2ludCwgdGhlIGRyYWZ0IHJlcHJl
c2VudHMgdGhlIG1vc3Qgc3RyYWlnaHQtZm9yd2FyZCB3YXksIGkuZS4sIHZpYSBJUHY2IG5leHQt
aGVhZGVyIHRvIHN1cHBvcnQgQklFUiBpbiBJUHY2LiAgQWxzbywgSSdkIHBvaW50IG91dCB0aGF0
IGFkb3B0aW9uIG9mIHRoaXMgb3B0aW9uIGRvZXMgbm90IHByZWNsdWRlIG90aGVyIGFsdGVybmF0
aXZlcy4gDQoNClRoYW5rcywNCkFjZWUNCg0KICAgIFRoZSBsYXN0IHBhcnQgaXMgYWJvdXQgdGhl
IHByb2dyZXNzIG9mIGEgc28tY2FsbGVkIEJJRVIgdjYgc29sdXRpb24uIA0KICAgIEhlcmUsIEkg
aGF2ZSBhc2tlZCB0aGUgY2hhaXJzIHRvIGVzdGFibGlzaCBhIHN1bW1hcnkgb2YgdGhlIGRpc2N1
c3Npb25zIA0KICAgIHJlZ2FyZGluZyB0aGF0IHR5cGUgb2Ygc29sdXRpb24gaW4gZ2VuZXJhbCBh
bmQgcmVnYXJkaW5nIHRoZSBzcGVjaWZpYyANCiAgICBkb2N1bWVudCB3aGljaCBwcm9wb3NlcyBh
IHNvbHV0aW9uLiBUaGV5IHNob3VsZCBwdWJsaXNoIGl0IHNvbWUgdGltZSANCiAgICBhZnRlciB0
aGlzIGUtbWFpbC4NCg0KICAgIEZvbGxvd2luZyB0aGF0LCBpdCBpcyBteSBleHBlY3RhdGlvbiB0
aGF0IHRoZSBXRyBoYXMgYSBmYWlyIGFuZCBvcGVuIA0KICAgIGRpc2N1c3Npb24sIGlkZWFsbHkg
Zm9jdXNzaW5nIG9uIHRoZSBnZW5lcmFsIGFzcGVjdHMsIGFuZCB0aGVuIGNvbmNsdWRlcyANCiAg
ICBvbiB0aGUgd2F5IGZvcndhcmQuDQoNCg0KICAgIE1hcnRpbg0KDQogICAgX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCiAgICBCSUVSIG1haWxpbmcgbGlz
dA0KICAgIEJJRVJAaWV0Zi5vcmcNCiAgICBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL2JpZXINCg0K

