Re: [Bier] Consensus call on adoption of RBS Work Into BIER WG

Toerless Eckert <tte@cs.fau.de> Thu, 03 August 2023 21:55 UTC

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 DEECEC15155F; Thu, 3 Aug 2023 14:55:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.66
X-Spam-Level:
X-Spam-Status: No, score=-6.66 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gwD00CQrPfHg; Thu, 3 Aug 2023 14:55:26 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5044C15155A; Thu, 3 Aug 2023 14:55:25 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [131.188.34.51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 4RH2hS02QHznkVp; Thu, 3 Aug 2023 23:55:19 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4RH2hR6RS1zkwcn; Thu, 3 Aug 2023 23:55:19 +0200 (CEST)
Date: Thu, 03 Aug 2023 23:55:19 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Tony Przygienda <tonysietf@gmail.com>, pim-chairs@ietf.org, mmcbride@futurewei.com
Cc: BIER WG <bier@ietf.org>
Message-ID: <ZMwiR5EBohAvvPfv@faui48e.informatik.uni-erlangen.de>
References: <CA+wi2hP58ssqVo7i8J9rgRRW+M0RrfX9VHoYx7gsY03t+R35zA@mail.gmail.com> <CA+wi2hNMmeTefXVYJxmCT8mRgmp1EfZr+zRsWbadb5Bw37rnpA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CA+wi2hNMmeTefXVYJxmCT8mRgmp1EfZr+zRsWbadb5Bw37rnpA@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/Sn4HFbvQPwn1OFdleUTXaRxVOBI>
Subject: Re: [Bier] Consensus call on adoption of RBS Work Into BIER WG
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 03 Aug 2023 21:55:31 -0000

Hi Tony

I am sorry you felt you had to send this email.

On Thu, Aug 03, 2023 at 06:38:21PM +0200, Tony Przygienda wrote:
> First, the working group chairs have considered the input from the working
> group and believe that there is consensus to work on the use case/solution
> presented under the BIER WG umbrella and RBS in particular.

I disagree.

I felt that both the raise of hands in the room, as well as the feedback
later on the list do not sum up to consensus, i rather would call it evenly split.

It would be really sad if by what i would call jumping the gun, we might divide the community and 
impair the technical results we could achieve. Instead, we should (IMHO) rather have more
technical, but also process discussion here on the list where everybody can participate, or
in Prague.  Instead of being excluded from the in-person discussion due to USAs failures to issue visas
(and some other unfortunate events) and hence limited participation.

> Second, per WG input the authors of the specific RBS draft presented under
> BCP 78/79 do not seem interested in an adoption call.  Any such future call

I think this does not restate correctly what i wrote to the WG on May 9th, 2023,
<ZFpoI7S9788nGGmv@faui48e.informatik.uni-erlangen.de>. It said that
i (and the co-authors) are not interested in a BIER-WG adoption call _NOW_
for the work that we presented... but that of course we are working towards
a version that we do want to propose for adoption by IETF. And the work we
have done since IETF116 did actually very much benefit from the discuss we
had there (especially with Tony), as well as discusses in IETF117. So repeated
going to IETF pre-WG-adoption has so far been very useful to the ultimate goal
of IETF adoption.

If it is necessary for the co-authors to also raise their voice here on this
thread, then please let us know so that they can chime in accordingly.

Let me summarize our current technical thinking in a separate message to
the better set of groups, see <ZMwhewRUm12vP6Xb@faui48e.informatik.uni-erlangen.de>
(sent tobier and pim).

Cheers
    Toerless