Re: [Bier] RFC8279: Request for authors to update RFC

Greg Shepherd <> Mon, 14 June 2021 13:47 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B7EE63A2507 for <>; Mon, 14 Jun 2021 06:47:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.097
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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id nmP0BJETMEDx for <>; Mon, 14 Jun 2021 06:47:19 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::62e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E39233A2502 for <>; Mon, 14 Jun 2021 06:47:18 -0700 (PDT)
Received: by with SMTP id nd37so9070351ejc.3 for <>; Mon, 14 Jun 2021 06:47:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=w1/sDlTKDiqaF23zMISDKKL0rniNXpG2PuUiTxM4HGs=; b=qaOhTtEtybpOa84I+KtsvfR3BD3bdtJLsk72TdlR9Os8wwBNLaVjNZRKukDO5fnzu4 PDHFZblseSc/u3JU2QKGw9fFWAh5d9Mibt2MyOh1klslixnmxOBejkYMwiAWKTdfA4HC pUEQhQjoVz4s8N8VUX/L1pFmRlkL3NzwdG4EGSae2RMbQ09lk094xHUe3Hl2i0jg1gUD ig56Czw71P9zqB6BHSBA116T4cFGFm59wnHtSNTEiRTX/yfoJ1lKdLMv3c6OYs8jLII+ 6jIDFTSJfAZK9fDNjESdJBw6buMz/9+4+fSGmibc0K+khCETpwQRDFjiRa7nt6wVW03X kohA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=w1/sDlTKDiqaF23zMISDKKL0rniNXpG2PuUiTxM4HGs=; b=K4eeWF9faDnBTMgknkuPRDObGM1R+lEIWPA/1BHX04UjYi4bbfYluuqlUmLlXAaefX kV8YcuEtw2MVD7Arh9MAisKVfhczTmhr1O5FKWs5iBXI2QfVDci3Zz7f7CGeT3z8SjqT wepKcyF+B00K6iMCbK3IenSS7TiBuiYH+ghbUkBuMbbI6PZPmustW4P49daYCfwIv810 zGgs0gVuH/5UWr9TghrJZYDhsWcI7LfD+0Axwhi1pgX/aUbvOCQ41UZdElDcqLfp50LF ysW7KBjr69pTf7L+xEWezjsemaTf4p0NwuB4DEvnex+26F/NB6pcowZODFRcC+JNvVLl 5n9A==
X-Gm-Message-State: AOAM531b0TcyWIwH/KkF6lF6nhJeLCFGruw8lZ+n0yGpQ+wfOZjdrazo pg5Y519itzNEkZubbVi2c+rVveNbRrydEUsE0AA=
X-Google-Smtp-Source: ABdhPJwlHVCjr5a+fSfR2IweCrQg8oSbSgdpt8X4AokIIz784ZbZUqXct4bvaH/xumeB/bIrW6n3Awp8jQUL3SibPsg=
X-Received: by 2002:a17:906:530e:: with SMTP id h14mr15563793ejo.165.1623678431039; Mon, 14 Jun 2021 06:47:11 -0700 (PDT)
MIME-Version: 1.0
References: <> <>
In-Reply-To: <>
From: Greg Shepherd <>
Date: Mon, 14 Jun 2021 06:46:58 -0700
Message-ID: <>
To: "zhang.zheng" <>
Cc: BIER WG <>
Content-Type: multipart/alternative; boundary="0000000000001c96bf05c4ba188d"
Archived-At: <>
Subject: Re: [Bier] RFC8279: Request for authors to update RFC
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 14 Jun 2021 13:47:24 -0000

Thank you, Sandy!

Anyone else willing to help?


On Sat, Jun 12, 2021 at 6:19 AM <> wrote:

> Hi Gerg, Tony,
> May I volunteer for the work to help making the description more detailed?
> Thank you very much!
> Best regards,
> Sandy
> 原始邮件
> *发件人:*gjshep<>
> *收件人:*bier<>;
> *日期:*2021-06-12 21:05:49
> *主题:**[Bier] RFC8279: Request for authors to update RFC*
> _______________________________________________
> BIER mailing list
> A big "thank you" to all WG members who have worked so hard to get BIER to
> where it is today. And to no surprise, our work is not done. The following
> bullet points are from the Chairs' technical summary previously sent to the
> list:
> • BIER encoding is specified in RFC8296
> • Alia Atlas: “IANA code-points don’t change.  This is the reason why
> BIER began as experimental - narrow
>         point in hourglass”
> • The encoding at the “narrow point of the hourglass” – the forwarding
> plane –  is the foundation from which
>         the rest of the architecture grows.
> • This was the position of the IESG and the BIER WG ADs at the time of
> the original WG Experimental Charter.
> • This is admittedly historic/institutional knowledge of those involved
> in the WG from the beginning. But it is also
>         a core tenet of the layered and scalable architecture of the
> Internet and was erroneously assumed as
>         well-understood by the original WG contributors. The WG needs to
> update the BIER architecture to make this
>         responsibility clear for all future contributors.
> RFC8279 began as a draft at the very beginning of the WG. It has since
> been made clear that the authors at that time had assumed the importance of
> the forwarding plane as the foundation of architecture was well understood
> by the community at large. That no longer seems to be the case.
> Additionally, the draft of RFC8279 began before the draft of RFC8296 was
> complete, and even before the assignment of the IEEE BIER ethertype.
> This is a call for volunteers to update RFC8279 to better define BIER at
> the forwarding plane, and clarify how IETF-standard encapsulation
> mechanisms can be used to transit BIER packets, while preserving the core
> tenet of a layered and scalable architecture of the Internet.
> If you would like to tackle this update, please reply to this thread.
> Thanks,
> Greg
> (Chairs)