Re: [Bier] WGLC for https://datatracker.ietf.org/doc/draft-ietf-bier-frr/

Toerless Eckert <tte@cs.fau.de> Tue, 13 February 2024 04:25 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 1FD33C157931 for <bier@ietfa.amsl.com>; Mon, 12 Feb 2024 20:25:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.658
X-Spam-Level:
X-Spam-Status: No, score=-1.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 wfhBE_knywpE for <bier@ietfa.amsl.com>; Mon, 12 Feb 2024 20:25:18 -0800 (PST)
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) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38777C15198F for <bier@ietf.org>; Mon, 12 Feb 2024 20:25:17 -0800 (PST)
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) server-digest SHA256) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 4TYpCF64Y7znkTk; Tue, 13 Feb 2024 05:25:13 +0100 (CET)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4TYpCF56yRzkmps; Tue, 13 Feb 2024 05:25:13 +0100 (CET)
Date: Tue, 13 Feb 2024 05:25:13 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Tony Przygienda <tonysietf@gmail.com>
Cc: BIER WG <bier@ietf.org>
Message-ID: <ZcrvKaDMBS5B7LQE@faui48e.informatik.uni-erlangen.de>
References: <CA+wi2hPyVhJmWP9bnixy3QSvQhm5BO7ug0nUUH50USY5h5HQTg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CA+wi2hPyVhJmWP9bnixy3QSvQhm5BO7ug0nUUH50USY5h5HQTg@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/FToZciAO_uXaxRPnT_VtNDJ8igU>
Subject: Re: [Bier] WGLC for https://datatracker.ietf.org/doc/draft-ietf-bier-frr/
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: Tue, 13 Feb 2024 04:25:22 -0000

ETOOLATE (past 2 weeks i guess), but still:

I have read the draft and support its publication.

Wrt. to the necessity: This document is well written and describes the different
options IMHO thoroughly.

I have not followed the prior discussion, but to answer the points Tony raised below:

Is it necessary ? I think yes. I consider its really nice dual purpose document for and against BIER FRR:

If somebody is asked to implement FRR for BIER, i think the document supports the right 
level of detail we can give without assuming specific forwarding plane implementation/optimization
options. If someone instead wants to avoid having to implement BIER FRR, then the document
also support that goal by elaborating on all the complexities, analysis and limitations
the FRR solution would have.

Does it need to be standardized/published ? Well, it only targets informational, because i think we can
make the argument that it does not introduce new on-the-wire interoperability requirements
(arguably for tunnels, but that's fine).  And if i was a customer told by a vendor that they had
perfect working BIER-FRR, then i would know a lot more questions that i would need to ask how it
was implemented/how it works so i can troubleshoot it, after reading this draft.

So, thanks a lot to the co-authors and contributors for this work. I think its a good
thing for BIER overall if we have this out as an RFC.

Cheers
    Toerless

On Thu, Jan 18, 2024 at 11:16:58AM +0100, Tony Przygienda wrote:
> Per authors' request this initiates 2 weeks WG LC for
> https://datatracker.ietf.org/doc/draft-ietf-bier-frr/
> 
> Please voice support/dissent. There was lively discussion about
> aspects/necessity of the document and involved data structures and I'd
> encourage the "speak now or hold your peace forever" discussion if necessary
> 
> * authors' list needs pruning pls
> * A shepherd is needed and according writedown
> * all authors pls disclose IPR
> 
> early reviews will be requested  after C passes
> 
> -- tony

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