[nfsv4] Artart last call review of draft-ietf-nfsv4-delstid-06
Henry Thompson via Datatracker <noreply@ietf.org> Mon, 26 August 2024 09:40 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: nfsv4@ietf.org
Delivered-To: nfsv4@ietfa.amsl.com
Received: from [10.244.2.19] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id C9A21C1516E2; Mon, 26 Aug 2024 02:40:40 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Henry Thompson via Datatracker <noreply@ietf.org>
To: art@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.22.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <172466524045.637056.13920337417309493111@dt-datatracker-584cd6c8dd-fvr2f>
Date: Mon, 26 Aug 2024 02:40:40 -0700
Message-ID-Hash: UP66VRH36XJRQAMNGVXQCHVBKDFSAITK
X-Message-ID-Hash: UP66VRH36XJRQAMNGVXQCHVBKDFSAITK
X-MailFrom: noreply@ietf.org
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: draft-ietf-nfsv4-delstid.all@ietf.org, last-call@ietf.org, nfsv4@ietf.org
X-Mailman-Version: 3.3.9rc4
Reply-To: Henry Thompson <ht@inf.ed.ac.uk>
Subject: [nfsv4] Artart last call review of draft-ietf-nfsv4-delstid-06
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/j5VSxjYzwN-hVjjYHMQCVJu_7sU>
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>
Reviewer: Henry Thompson Review result: Ready with Issues Document: draft-ietf-nfsv4-delstid-06 Intended RFC status: Proposed Standard Review type: artart - Last Call review Reviewer: Henry S. Thompson Review Date: 2024-08-26 Result: Ready with minor issues *Summary* *Substantive points* *Minor points* Section 2.1: Probably worth mentioning that the 'CODE' shown here is defined per RFC 4506. Section 4: "The open stateid field, OPEN4resok.stateid ..., will MUST be set to the special all zero" There's a typo here, and in any case I _think_ it should be expanded slightly for clarity: "The open stateid field, OPEN4resok.stateid ..., MUST be set to the special all zero in this case." Section 4.1: I'm not familiar with the implementation details of NFS, but I find this discussion difficult to follow. Perhaps it would help if it were expanded to show what the two compounds sequences look like for the two different values of OPEN_ARGS_SHARE_ACCESS_WANT_OPEN_XOR_DELEGATION. Section 5: As far as the protocol itself is concerned, this section looks OK to me, but the mixture of BCP14 keywords and ordinary language to describe the correct _use_ of the protocol with respect to the various times involved is quite confusing, and would benefit from a more structure, in the form of an analysis by cases. *Nits* Section 3: "Note that as these flags MUST only change from OPTIONAL to REQUIRED when the NFSv4 minor version is incremented" --- something wrong with the grammar here, possibly just delete "as". Section 6: I think "the that" should be just "that", but you may possibly have meant just "the". ht --
- [nfsv4] Artart last call review of draft-ietf-nfs… Henry Thompson via Datatracker
- [nfsv4] Re: Artart last call review of draft-ietf… Thomas Haynes