[nfsv4] Proposed Working Group Charter

David Noveck <davenoveck@gmail.com> Mon, 28 August 2017 14:04 UTC

Return-Path: <davenoveck@gmail.com>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id B4A6C132962; Mon, 28 Aug 2017 07:04:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id py3qSckVc2Ru; Mon, 28 Aug 2017 07:04:19 -0700 (PDT)
Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12B28132D14; Mon, 28 Aug 2017 07:04:10 -0700 (PDT)
Received: by mail-io0-x234.google.com with SMTP id k22so1860373iod.2; Mon, 28 Aug 2017 07:04:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=yeh/UskoA3T8hiyGh7VmZxDnOK9ZwMNBuw2gMh7aolU=; b=HZFYozP1XMKJBhZHY1CcBUWfAYJvNyUkG0QhXKX6n1ig07tTy6NkQSPBPt8/KuZ8ax 8ZEKEigLhJelEohd1ONMYVyKJpRxHoBxNjjzEcUxiwKyloX1F0sbGIO51W6+xFF42Vqb 9iQbQBsdbfidY2Ynwn+YLVIBHj3gBPlO/urWPcB3dJQ/A+CAW3J+BM4kcs8e/EW0bmNa VrfEwqc5QyG0MUT2Yac41k7dGFl6MWoRx471Jk7LGEmPj8fVNJegLT6+kYPcz9tunQ+q ragizUkW7JI0/8QARjZRyICaMwe+OhvTwzOg2SAFD2b59SpPV6MLZsXdQOtLqgAPpsi7 AC7w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=yeh/UskoA3T8hiyGh7VmZxDnOK9ZwMNBuw2gMh7aolU=; b=CjfeLRuo/wdXCuBeYsFCKAqkmpnUIyZ6WxoRpJ3sLxRZfKqh57atCKFO2sQ5ABzPnz BjF+fdk4T7UDIm1sGNybDvj4wpKrt/M/GbXqbcJC2xcT41br7HSAnm7QgCJcLdrwmt1G 9Oze60IUi07tFCT5slGCi6PAY8HrIFOBiL7bq56V8Pw6JhdBN/zdn085sXGOk4z+aDT/ d5NR2IfK0kx4GN0vkf+95XNFUynAjLY1P+MS5tTe1rWCqFT2kuhVC4obe4wTSsPtlYKI YvFERa6IyE7ml0dsxJrHT+jZIUA/uZCGUIfQaPAEiIkk6BG6OnHkAt60GQZtEKTB7cI7 h+vw==
X-Gm-Message-State: AHYfb5iTuG1ya/mxZSHIz2aL9mcGl/XaAcRAd6XkciHYmHfrXJQVde3f NLKDpmJnmtQOEe3qcwkcszCLCuERSw==
X-Received: by with SMTP id m63mr634618iof.9.1503929049621; Mon, 28 Aug 2017 07:04:09 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Mon, 28 Aug 2017 07:04:08 -0700 (PDT)
From: David Noveck <davenoveck@gmail.com>
Date: Mon, 28 Aug 2017 10:04:08 -0400
Message-ID: <CADaq8jdNRenxK0yfXC9xpmCidfzuetcrC=dhkK7w2TnehZ6X4g@mail.gmail.com>
To: "nfsv4-chairs@ietf.org" <nfsv4-chairs@ietf.org>, nfsv4-ads@ietf.org
Cc: "nfsv4@ietf.org" <nfsv4@ietf.org>
Content-Type: multipart/mixed; boundary="94eb2c05d500c57d630557d0c4f2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/eHfLSIFFPQuE_XFd9kIpjtZDM-c>
Subject: [nfsv4] Proposed Working Group Charter
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
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: Mon, 28 Aug 2017 14:04:22 -0000

The attached file is based on what was presented at IETF99.  It includes
minor tweaks that were suggested at the meeting or soon therafter.

Added to that was material on proposed milestones which was presented to the
working group for its review on 8/17.  It now appears that the consolidated
is ready for presentation to the IESG.

Because there have been some difficulties with the archiving of
powerpoints, I want to
make sure that any further such difficulties will not prevent access to the
substance of this
proposal.  In order to provide another path of access, an ascii-ized
representation is to be
found below.


NFSv4wg Charter

Final Proposal

Including Proposed Milestones

David Noveck

August 28, 2017

1. Proposed Charter Text

1.1.  General Section

NFS Version 4 is the IETF standard  for file sharing.

To maintain NFS Version 4's utility and currency, the working group is
chartered to maintain the existing NFSv4.0, NFSv4.1, and NFSv4.2 protocols
and specifications of related ONC components, such as those defining RPC,

In addition, extensions will be developed, as necessary, to correct
with the protocols as currently specified, to accommodate needed file
semantics, and to respond to technological developments in the areas of
networking and persistent storage/memory.

1.2 Maintenance Section

The working group has found that, as NFSv4 implementations mature and
deployments continue, clarifications and corrections to existing RFCs
are needed.

These specification updates help vendors in delivering high-quality and
interoperable implementations.

The working group is chartered with the vetting of reported issues and
determining correctness of submitted errata.

The working group is also responsible for approving changes to RPC- and
NFS-related IANA registries

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.

Since necessary changes in such cases are generally not appropriate for
the errata system, the working group will assist in publication of RFCs
that provide implementation guidance and of RFCs that provide editorial
modification or technical updates to original RFCs.

Since the new NFSv4 versioning framework is in effect, such technical
updates to NFSv4 minor versions could include limited XDR changes.

1.3 Extension Section

The NFSv4 protocol is designed to allow extension by the definition of
new operations, new attributes, and new pNFS layout types, as well as
the creation of minor versions.

Similarly, associated ONC protocol components that have a versioning/
extension framework can be incrementally extended, when necessary.

The working group will discuss proposals for such extensions and assure
that they have adequate technical review, including discussion of their
interaction with existing features, before adopting them as working group
items and helping to draft specification documents.

Some likely motivations for such extensions would be to:

Maximize NFS performance on advanced network fabrics.

Accommodate new storage technologies.

Provide facilities useful in management of NFS-accessed storage in

large-scale virtualization environments.

Provide more effective NFS response to security challenges.

2. Proposed Milestones

Because the previous charter was at variance with the work the group
was actually doing, the list of pending milestones that can determined
now is somewhat limited.

To accommodate this situation and in light of the fact that maintenance
activities are inherently unpredictable, new milestones that fall within
the scope specified within the charter can be added to the list of
milestones below after working group consensus upon acceptance and
approval by the responsible Area Director

|   Date  |                Milestone                                   |
| 3/2018  | WGLC for description of use of NVMe in accessing a pNFS    |
|         | SCSI Layout                                                |
| 6/2018  | WGLC for draft-ietf-nfsv4-migration-issues (Informational) |
| 8/2018  | WGLC for document describing NFSv4.0 trunking discovery    |
| 10/2018 | WGLC for document describing NFSv4.1 trunking discovery    |
| 10/2018 | WGLC for document describing Transparent State Migration   |
|         | in NFSv4.1                                                 |
| 1Q2019  | WGLC for description of CM private data convention         |
|         | (Informational)                                            |
| 1Q2019  | WGLC for pNFS RDMA Layout                                  |
| 3Q2019  | WGLC for RPC-over-RDMA Version 2                           |