[nfsv4] Benoit Claise's Block on charter-ietf-nfsv4-05-00: (with BLOCK and COMMENT)

Benoit Claise <bclaise@cisco.com> Thu, 14 September 2017 07:25 UTC

Return-Path: <bclaise@cisco.com>
X-Original-To: nfsv4@ietf.org
Delivered-To: nfsv4@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B07E1321D8; Thu, 14 Sep 2017 00:25:29 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benoit Claise <bclaise@cisco.com>
To: The IESG <iesg@ietf.org>
Cc: nfsv4-chairs@ietf.org, nfsv4@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.61.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150537392913.12691.17798959041359292248.idtracker@ietfa.amsl.com>
Date: Thu, 14 Sep 2017 00:25:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/RrIzPKCfLM2ZyWesROoSBHWpJs8>
Subject: [nfsv4] Benoit Claise's Block on charter-ietf-nfsv4-05-00: (with BLOCK and COMMENT)
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.22
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4/>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Sep 2017 07:25:29 -0000

Benoit Claise has entered the following ballot position for
charter-ietf-nfsv4-05-00: Block

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)



The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/charter-ietf-nfsv4/



----------------------------------------------------------------------
BLOCK:
----------------------------------------------------------------------

- "The working group is also responsible for approving changes to RPC- and
NFS-related IANA registries." I frown up the "approving" word. It sounds like
we change the IANA process here. Also, it seems like this sentence covers a
series of registries https://www.iana.org/protocols#index_N

Network File System version 4 (NFSv4)

NFSv4 ${ietf.org:CPU_ARCH} Value Registry       RFC 5661
First Come First Served
NFSv4 ${ietf.org:OS_TYPE} Value Registry        RFC 5661
First Come First Served
NFSv4 Device ID Notifications Registry  RFC 5661
Standards Action with Expert Review (Expert: Spencer Shepler)
NFSv4 Named Attribute Definitions Registry      RFC 5661, RFC 7530
Specification Required for new registrations; updates to fields other than the
contact field require Expert Review or IESG Approval (Expert: Spencer Shepler)
NFSv4 Path Variables Registry   RFC 5661 ietf.org domain: Standards Action with
Expert Review. non-ietf.org. domain: First Come First Served. (Expert: Spencer
Shepler) NFSv4 Recallable Object Types Registry  RFC 5661 Standards Action with
Expert Review (Expert: Spencer Shepler) pNFS Layout Types Registry      RFC 5661

So we have a mix of FCFS and Standard Action with Expert Review.
If the charter says that the WG is now responsible, what does it imply? For ex,
in terms of FCFS? What do you expect from the WG in the different situations?
Feedback? Approval? (what if the WG disagrees with the expert), Standards
Action Review? Standards Action with Expert Review (Expert: Spencer Shepler)


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------



- What are we balloting on?
https://datatracker.ietf.org/doc/charter-ietf-nfsv4/ballot/ shows two different
pieces of information 1. Ready w/o external review (05-00) 2. Ballot question:
"Is this charter ready for external review? Is this charter ready for approval
without external review?" Is this a tooling issue?

- "The NFSv4 working group is chartered with vetting reported issues and
determining correctness of submitted errata." I like that approach of not only
having the area responsible for evaluating errata.

- Like in the current NFSV4 charter, you should break down the proposed
milestones in "WG Last Call" and "Submit Final" and add the intended status

- Editorial

In addition, some areas may need more concentrated work to correct the
specifications already published, to deal with unanticipated interactions
between features, or to respond to evolving IESG expectations with regard
to areas such as security.

Could we remove "IESG"? While the IESG provides guidance and sometimes enforces
rules, we should stress that the IETF is a community-based effort, as opposed
to IESG-driven effort.