[art] Re: [Last-Call] Artart last call review of draft-eastlake-fnv-28

Erik Auerswald <auerswal@unix-ag.uni-kl.de> Tue, 08 October 2024 14:55 UTC

Return-Path: <auerswal@unix-ag.uni-kl.de>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70998C1840CC; Tue, 8 Oct 2024 07:55:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, 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 ttZxBmUd_q1Q; Tue, 8 Oct 2024 07:55:16 -0700 (PDT)
Received: from mailgw1.uni-kl.de (mailgw1.uni-kl.de [IPv6:2001:638:208:120::220]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C6B8C14F6B8; Tue, 8 Oct 2024 07:55:09 -0700 (PDT)
Received: from sushi.unix-ag.uni-kl.de (sushi.unix-ag.uni-kl.de [IPv6:2001:638:208:ef34:0:ff:fe00:65]) by mailgw1.uni-kl.de (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id 498EteO0052358 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 8 Oct 2024 16:55:40 +0200
Received: from sushi.unix-ag.uni-kl.de (ip6-localhost [IPv6:::1]) by sushi.unix-ag.uni-kl.de (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id 498Et5oc029545 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 8 Oct 2024 16:55:05 +0200
Received: (from auerswal@localhost) by sushi.unix-ag.uni-kl.de (8.14.4/8.14.4/Submit) id 498Et5wY029543; Tue, 8 Oct 2024 16:55:05 +0200
Date: Tue, 08 Oct 2024 16:55:05 +0200
From: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
To: Barry Leiba <barryleiba@computer.org>
Message-ID: <20241008145505.GA28733@unix-ag.uni-kl.de>
References: <172816120099.282330.5360535206284650774@dt-datatracker-cb674fff7-jr9km>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <172816120099.282330.5360535206284650774@dt-datatracker-cb674fff7-jr9km>
Author: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
Message-ID-Hash: KTVBM2UTV24DIHZDBFJP7DKSQ4V4EHB6
X-Message-ID-Hash: KTVBM2UTV24DIHZDBFJP7DKSQ4V4EHB6
X-MailFrom: auerswal@unix-ag.uni-kl.de
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-art.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: art@ietf.org, draft-eastlake-fnv.all@ietf.org, last-call@ietf.org
X-Mailman-Version: 3.3.9rc5
Precedence: list
Subject: [art] Re: [Last-Call] Artart last call review of draft-eastlake-fnv-28
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/vAD_qsxC5kYzaRDWMaOVB4qqC9c>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Owner: <mailto:art-owner@ietf.org>
List-Post: <mailto:art@ietf.org>
List-Subscribe: <mailto:art-join@ietf.org>
List-Unsubscribe: <mailto:art-leave@ietf.org>

Hi,

On Sat, Oct 05, 2024 at 01:46:41PM -0700, Barry Leiba via Datatracker wrote:
> Reviewer: Barry Leiba
> Review result: Not Ready
> 
> As this is documenting an existing algorithm that was not developed
> in the IETF, we have no control over the substance of the document,
> so I am not commenting on that: it is what it is.
> 
> And that's exactly my issue with this: it's in the wrong stream.
> The shepherd writeup says that it was not developed in the IETF and
> there's no reason to put it on Standards Track, but also says that
> there's no reason it "needs to go to the ISE".  I disagree: this is
> *exactly* the sort of document that the Independent stream is there for.
> There is no meaningful sense of IETF consensus on this -- all we can
> have is consensus to publish it as is.
> 
> Ultimately, the IESG, not my review, will decide the right answer here.
> Please consider asking the ISE to move this to the Independent stream,
> where I think it should have been taken in the first place.  Thanks.

I also think that the Independant Stream would be a better fit for
this document.

Br,
Erik