From nobody Mon Jun 14 06:47:25 2021 Return-Path: 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 B7EE63A2507 for ; Mon, 14 Jun 2021 06:47:23 -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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 nmP0BJETMEDx for ; Mon, 14 Jun 2021 06:47:19 -0700 (PDT) Received: from mail-ej1-x62e.google.com (mail-ej1-x62e.google.com [IPv6:2a00:1450:4864:20::62e]) (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 E39233A2502 for ; Mon, 14 Jun 2021 06:47:18 -0700 (PDT) Received: by mail-ej1-x62e.google.com 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; d=gmail.com; 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; d=1e100.net; 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: <202106122119264815393@zte.com.cn> In-Reply-To: <202106122119264815393@zte.com.cn> Reply-To: gjshep@gmail.com 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-BeenThere: bier@ietf.org 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 --0000000000001c96bf05c4ba188d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thank you, Sandy! Anyone else willing to help? Thanks, Greg (Chairs) 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 > > =E5=8E=9F=E5=A7=8B=E9=82=AE=E4=BB=B6 > *=E5=8F=91=E4=BB=B6=E4=BA=BA:*gjshep > *=E6=94=B6=E4=BB=B6=E4=BA=BA:*bier; > *=E6=97=A5=E6=9C=9F:*2021-06-12 21:05:49 > *=E4=B8=BB=E9=A2=98:**[Bier] RFC8279: Request for authors to update RFC* > > _______________________________________________ > BIER mailing list > BIER@ietf.org > https://www.ietf.org/mailman/listinfo/bier > > A big "thank you" to all WG members who have worked so hard to get BIER t= o > where it is today. And to no surprise, our work is not done. The followin= g > bullet points are from the Chairs' technical summary previously sent to t= he > list: > > =E2=80=A2 BIER encoding is specified in RFC8296 > =E2=80=A2 Alia Atlas: =E2=80=9CIANA code-points don=E2=80=99t change. Th= is is the reason why > BIER began as experimental - narrow > point in hourglass=E2=80=9D > =E2=80=A2 The encoding at the =E2=80=9Cnarrow point of the hourglass=E2= =80=9D =E2=80=93 the forwarding > plane =E2=80=93 is the foundation from which > the rest of the architecture grows. > =E2=80=A2 This was the position of the IESG and the BIER WG ADs at the ti= me of > the original WG Experimental Charter. > =E2=80=A2 This is admittedly historic/institutional knowledge of those in= volved > 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 understoo= d > 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) > --0000000000001c96bf05c4ba188d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thank you, Sandy!=C2=A0

Anyone else wil= ling to help?

Thanks,
Greg
(Ch= airs)


On Sat, Jun 12, 2021 at 6:19 AM <zhang.zheng@zte.com.cn> wrote:
Hi Gerg, Tony,
May I volunteer for the work to = help making the description more detailed?
Thank you very much!
Bes= t regards,
Sandy

=E5=8E=9F=E5=A7=8B=E9= =82=AE=E4=BB=B6

_____________________________= __________________
BIER=C2=A0mailing=C2=A0list
BIER@ietf.org
https://www.ietf.org/mailma= n/listinfo/bier

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 pre= viously sent to the list:=C2=A0

=E2=80=A2 BIER encoding is= specified in RFC8296
=E2=80=A2 Alia Atlas: =E2= =80=9CIANA code-points don=E2=80=99t change.=C2=A0 This is the reason why B= IER began as experimental - narrow
=C2=A0 =C2=A0 =C2=A0 =C2=A0 point in hourglass=E2=80=9D
=E2=80=A2 The encoding at = the =E2=80=9Cnarrow point of the hourglass=E2=80=9D =E2=80=93 the forwardin= g plane =E2=80=93 =C2=A0is the foundation from which=C2=A0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 the rest of the architecture grows.
=E2=80=A2 This was the pos= ition of the IESG and the BIER WG ADs at the time of the original WG Experi= mental Charter.
=E2=80=A2 This is admitted= ly historic/institutional knowledge of those involved in the WG from the be= ginning. But it is also=C2=A0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 a core tenet of the layered and scalable a= rchitecture of the Internet and was erroneously assumed as=C2=A0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 well-understood by the original WG contrib= utors. The WG needs to update the BIER architecture to make this=C2=A0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 responsibility clear for all future contri= butors.

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 o= f the forwarding plane as the foundation of architecture was well understoo= d by the community at large. That no longer seems to be the case. Additiona= lly, the draft of RFC8279 began before the draft of RFC8296 was complete, a= nd 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 mechan= isms can be used to transit BIER packets, while preserving the core tenet o= f a layered and scalable architecture of the Internet.

If you would like to tackle this update, please reply to this thread.<= /div>

Thanks,
Greg
(Chairs)
--0000000000001c96bf05c4ba188d--