Re: [Bier] RFC8279: Request for authors to update RFC
Gyan Mishra <hayabusagsm@gmail.com> Tue, 15 June 2021 05:53 UTC
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 C4BB53A2108 for <bier@ietfa.amsl.com>; Mon, 14 Jun 2021 22:53:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.087
X-Spam-Level:
X-Spam-Status: No, score=-1.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, FREEMAIL_REPLY=1, 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=no 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 GiGbRT2jeEzO for <bier@ietfa.amsl.com>; Mon, 14 Jun 2021 22:53:05 -0700 (PDT)
Received: from mail-pl1-x62d.google.com (mail-pl1-x62d.google.com [IPv6:2607:f8b0:4864:20::62d]) (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 0D4423A1263 for <bier@ietf.org>; Mon, 14 Jun 2021 22:53:04 -0700 (PDT)
Received: by mail-pl1-x62d.google.com with SMTP id o21so83519pll.6 for <bier@ietf.org>; Mon, 14 Jun 2021 22:53:04 -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=xRD0iuQDG+2knzo+4xyfBAN9uDb0jI7GZl5wkTHjagI=; b=bH91XsqU4sR1lfC8qkuHsXodaWie2GuT/CQELTVAMAbeQvTeXKRfwG8bIE+8kom0fl Uoz6KGjrxzpa4vn1gUlkDOC3N8+dL9nmKix2gKy9A/uLCklcLupiXnreyMpOXh1JHYYh 4xfxRIPYQmQgkEmCdMG9o8zloOowTnyr8swF87Zq3GjtWV4wEgCwmjbGUDwPEU/kjKMK vvgiGaedKwn/oDqIscAkw6PQSx8god3pPm/iyRrDvmmaw8CVDiPABDiKW9M5JmLU7iaS KhkrbYeJBeUBMxhibEfz9awXUUtqbIrejLRpBpqCAMVMG47xK5W91kccd+2q2DmFDna9 i4GQ==
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=xRD0iuQDG+2knzo+4xyfBAN9uDb0jI7GZl5wkTHjagI=; b=jwE4P3xWWrGaH6Ficd/HTwDh1DZ6HVndPge3K9AK+9ENLgpnZp94CK14YRsuY6XWSh t1YhADmUuBHTV64ozgXNUNP/0MJ41SpNdWM/e+eFNobdVlZbQjLURVz6yaM0MbKivD/c /uiCKpLNN7jUk4M3L6Ifd3myJRhZQI3Im50VGlOBhd40I2YLnvoz9WKF8EHUAmdmP9zA uc3UNZbAQY5MHk4WcU5wtiopPHwXZlO/Z8p9gR3cbaF/PexZO6YXmAzV38wFZ0Y+pLe/ xhC91tji84+LapTnkZKcFBM7/BdC7uoParRkHpMIbsizK2GuZ24JcyTW129yuqO87awK R77g==
X-Gm-Message-State: AOAM533xsj9VJluV7jUmMLwszsZsyiI9WK6lATLMmiIwgQRQZUYjOGUo B1aGDwmSMnUpMh//Y+DjcCZoGHR/x8630BCA/ao=
X-Google-Smtp-Source: ABdhPJwJn2uXGxIlxwV7VwRdS3vBHuP0eqR8DedzudsSSSOoNYR2h1KMwE2Ms/kgi6Nz6AQmT6H6cy7eW7REtikZPMY=
X-Received: by 2002:a17:90a:5403:: with SMTP id z3mr3188521pjh.215.1623736381251; Mon, 14 Jun 2021 22:53:01 -0700 (PDT)
MIME-Version: 1.0
References: <CABFReBpjD3V14P8CuO+_OHvZr=XX1c5Dm8SjB9pahJmrQJx5qQ@mail.gmail.com> <202106122119264815393@zte.com.cn> <CABFReBoZ9y+WqTrNfpUZNcYon1m6ZcpYb8=hBc_XxK15EPphSQ@mail.gmail.com> <DM6PR08MB3978C93BE7DB5A1D920DF0A691319@DM6PR08MB3978.namprd08.prod.outlook.com> <CA+wi2hNgw7rVu8b1oGeQh56oyQSsTVQWXwp14CMLjF6hdS5usg@mail.gmail.com> <DM6PR08MB3978C8F24854038EB327B7D091309@DM6PR08MB3978.namprd08.prod.outlook.com>
In-Reply-To: <DM6PR08MB3978C8F24854038EB327B7D091309@DM6PR08MB3978.namprd08.prod.outlook.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Tue, 15 Jun 2021 01:52:48 -0400
Message-ID: <CABNhwV2Udt=STgiG69xJuAZWdbWMKAMnpjHgqH5NotDxCRPLTg@mail.gmail.com>
To: "Bidgoli, Hooman (Nokia - CA/Ottawa)" <hooman.bidgoli@nokia.com>
Cc: BIER WG <bier@ietf.org>, Tony Przygienda <tonysietf@gmail.com>, "gjshep@gmail.com" <gjshep@gmail.com>, "zhang.zheng" <zhang.zheng@zte.com.cn>
Content-Type: multipart/alternative; boundary="00000000000036a36005c4c79637"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/O8iFnAFhZJleHBuxkueYGat0qSM>
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\"" <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, 15 Jun 2021 05:53:10 -0000
I would like to help. Thanks Gyan On Mon, Jun 14, 2021 at 10:46 PM Bidgoli, Hooman (Nokia - CA/Ottawa) < hooman.bidgoli@nokia.com> wrote: > This time replying to all 😊 > > > > Thanks for the explanation, sure I can assist. > > > > Regards > > Hooman > > > > > > *From:* Tony Przygienda <tonysietf@gmail.com> > *Sent:* Monday, June 14, 2021 10:22 AM > *To:* Bidgoli, Hooman (Nokia - CA/Ottawa) <hooman.bidgoli@nokia.com> > *Cc:* gjshep@gmail.com; zhang.zheng <zhang.zheng@zte.com.cn>; BIER WG < > bier@ietf.org> > *Subject:* Re: [Bier] RFC8279: Request for authors to update RFC > > > > <individual> > > > > AFAIS the rev should include all the lessons we learned since 8279 was > smote ;-) > > > > Initial architecture was written in a very accessible form, alas could > have benefited from more rigour. Trade-off taken was to move fast with > folks who were largely mind-melted based on long experience in networking & > multicast problems and framework which was malleable rather than formalize > things into a strict corset readable for less experienced folks. The rigour > would benefit us now IMO, especially since lots of work fleshed the details > out and newest discussions show that lots of lessons that old-hands in > multicast learned are not necessarily obvious. Things like "how do you > route underlay?" which led to BAR/IPA discussions or "can you run BIER > without an IGP" which led to lots of yang discussions to allow for > controller only deployments or even BIER-TE which basically uses BIER to > interpret the bitmask completely differently should be codified in 8279bis > IMO. > > > > -- tony > > > > On Mon, Jun 14, 2021 at 4:12 PM Bidgoli, Hooman (Nokia - CA/Ottawa) < > hooman.bidgoli@nokia.com> wrote: > > Hi Greg > > > > Just to ensure is the final goal to update 8279 to include bier forwarding > with all BIER encapsulation including MPLS, non-MPLS and IPv6 encap? And/Or > is it to include bier forwarding over tunnels including mpls, ipv6, for FRR > etc… ? > > > > Thanks > > Hooman > > > > *From:* BIER <bier-bounces@ietf.org> *On Behalf Of *Greg Shepherd > *Sent:* Monday, June 14, 2021 9:47 AM > *To:* zhang.zheng <zhang.zheng@zte.com.cn> > *Cc:* BIER WG <bier@ietf.org> > *Subject:* Re: [Bier] RFC8279: Request for authors to update RFC > > > > Thank you, Sandy! > > > > Anyone else willing to help? > > > > Thanks, > > Greg > > (Chairs) > > > > > > 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! > Best regards, > Sandy > > 原始邮件 > > *发件人**:*gjshep<gjshep@gmail.com> > > *收件人**:*bier<bier@ietf.org>; > > *日期**:*2021-06-12 21:05:49 > > *主**题**:[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 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) > > _______________________________________________ > BIER mailing list > BIER@ietf.org > https://www.ietf.org/mailman/listinfo/bier > > _______________________________________________ > 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*
- [Bier] RFC8279: Request for authors to update RFC Greg Shepherd
- Re: [Bier] RFC8279: Request for authors to update… zhang.zheng
- Re: [Bier] RFC8279: Request for authors to update… Greg Shepherd
- Re: [Bier] RFC8279: Request for authors to update… Bidgoli, Hooman (Nokia - CA/Ottawa)
- Re: [Bier] RFC8279: Request for authors to update… Tony Przygienda
- Re: [Bier] RFC8279: Request for authors to update… Greg Shepherd
- Re: [Bier] RFC8279: Request for authors to update… Jeffrey (Zhaohui) Zhang
- Re: [Bier] RFC8279: Request for authors to update… Bidgoli, Hooman (Nokia - CA/Ottawa)
- Re: [Bier] RFC8279: Request for authors to update… Gyan Mishra
- Re: [Bier] RFC8279: Request for authors to update… Greg Shepherd
- Re: [Bier] RFC8279: Request for authors to update… Toerless Eckert
- Re: [Bier] RFC8279: Request for authors to update… Aijun Wang
- Re: [Bier] RFC8279: Request for authors to update… Greg Shepherd
- Re: [Bier] RFC8279: Request for authors to update… Toerless Eckert
- Re: [Bier] RFC8279: Request for authors to update… 'Toerless Eckert'
- Re: [Bier] RFC8279: Request for authors to update… zhang.zheng
- Re: [Bier] RFC8279: Request for authors to update… Mankamana Mishra (mankamis)