[nfsv4] Re: Genart last call review of draft-ietf-nfsv4-layrec-01

worley@ariadne.com Wed, 16 October 2024 00:23 UTC

Return-Path: <worley@alum.mit.edu>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25F19C1D530E for <nfsv4@ietfa.amsl.com>; Tue, 15 Oct 2024 17:23:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.691
X-Spam-Level:
X-Spam-Status: No, score=-1.691 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
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 w3uvjmszHZsX for <nfsv4@ietfa.amsl.com>; Tue, 15 Oct 2024 17:23:01 -0700 (PDT)
Received: from resqmta-h2p-567038.sys.comcast.net (resqmta-h2p-567038.sys.comcast.net [96.102.200.7]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60F89C14F689 for <nfsv4@ietf.org>; Tue, 15 Oct 2024 17:23:01 -0700 (PDT)
Received: from resomta-h2p-555059.sys.comcast.net ([96.102.179.197]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 256/256 bits) (Client did not present a certificate) by resqmta-h2p-567038.sys.comcast.net with ESMTPS id 0rbcttj9Vhe7N0rmetKpJY; Wed, 16 Oct 2024 00:21:00 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20211018a; t=1729038060; bh=4P6ttetUu8dJQqVHmENCSzSwlxwskuhMr1HwHVS96jQ=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID:Xfinity-Spam-Result; b=JRFVnDahAB3b+NJTgzxLwjoPuWfwD+5vMTo7ESPhb6aMGpp5puxHgyWQFd68/7yMD jpBJEV7i0bHmrzZEPtQ63hyeSJVCJESedR1pR3Qd5i56wGWkw1/K9y3HZN7hNjHp6i wUhaV8f653mgkNghBEG/mGXZZAtmRowN35dTuKU44neO5HvwpzdhvfO8rX9y6L++ZF FGydJlq4SinWCdoqGw3nV0VVG5bmk/8+l8d4I31pm4E/mt+fDnIjZCL7VkL6VbNQMe +PuUiVTe8kBHBGQpKn/m/Ve/7KgF59/R45HhcTLj1x8enfXTEFHwC/CZqHj27dFF+I FQqNUahKsE0Zg==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4a00:430::1ea6]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 256/256 bits) (Client did not present a certificate) by resomta-h2p-555059.sys.comcast.net with ESMTPSA id 0rmbtpwqiCLj00rmdtwJMz; Wed, 16 Oct 2024 00:21:00 +0000
Received: from hobgoblin.ariadne.com (localhost [127.0.0.1]) by hobgoblin.ariadne.com (8.16.1/8.16.1) with ESMTPS id 49G0KrCu025505 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Tue, 15 Oct 2024 20:20:54 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.16.1/8.16.1/Submit) id 49G0KrV2025502; Tue, 15 Oct 2024 20:20:53 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Thomas Haynes <loghyr@gmail.com>
In-Reply-To: <4A621262-ADA3-4CF3-8E72-DCDBE28ADC30@gmail.com> (loghyr@gmail.com)
Sender: worley@ariadne.com
Date: Tue, 15 Oct 2024 20:20:53 -0400
Message-ID: <877ca87va2.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4xfHs/xpP5BWUZJx4PKaDMTs2Je2XYGPgkNGdnib7XfPi8hGGmpo4l9+33NcHG1KMxoSiiu3exgENmskuPAXDwwLn+BQloHXAfh3jt0JvznrECScKgauAB 0kWYJJ2WpJyLtLQBSQpAwQbm3NcaHABvZ1UrI9HqWn3qszVaBDWLvHYf5PPZiuZz7kONUgrvU0PmZcDRvZGqX5ItAkbC0j68+RN/ansTVKdMHMa9bKQYIdr5 T4dVYyO6IGH/t6Y1f3yMWLAAeWHhcVc0S/ZRQuIBbuxyVq22uIsFh0LwTg8et/Tioy48SXOSv+yjoZm5pUPsSUTsW8VKKPmMkySSnovduUffGyw8BUKr8OSa 617j6Q/7
Message-ID-Hash: RORWRKVI4Z7GSWCLATQN2VMAKRPH4ZBP
X-Message-ID-Hash: RORWRKVI4Z7GSWCLATQN2VMAKRPH4ZBP
X-MailFrom: worley@alum.mit.edu
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-nfsv4.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: gen-art@ietf.org, draft-ietf-nfsv4-layrec.all@ietf.org, last-call@ietf.org, nfsv4@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [nfsv4] Re: Genart last call review of draft-ietf-nfsv4-layrec-01
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/-h68keJhy6dC_SnLWJinmjG2dKM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Owner: <mailto:nfsv4-owner@ietf.org>
List-Post: <mailto:nfsv4@ietf.org>
List-Subscribe: <mailto:nfsv4-join@ietf.org>
List-Unsubscribe: <mailto:nfsv4-leave@ietf.org>

Thomas Haynes <loghyr@gmail.com> writes:
> I believe I have addressed all of your points, even if I did not
> directly reply to your points. I.e., an earlier rewrite might impact
> the scope of your comments.

Thanks for taking care of this!

It looks like you've considered everything carefully and resolved the
issues I see.  

>> The text is written for people who have the entirety of the previously
>> defined protocol in their heads, and know all of the processing
>> paths.  
>
> I will not argue this point.
>
>> That is, it's a very densely-written sent of amendments, with
>> no clear indexing of exactly what execution paths are affected by what
>> extensions/requirements.  It would be better if the items were broken
>> apart, the text expanded, and keyed to the definitions of the
>> procedures which are being amended.

I suppose I could argue that changes ought to address this issue, but
that is probably a monstrous piece of work, and the result possibly not
easier to read and digest than the current document structure.  So I am
going to defer to the authors about that.

Dale