Re: [nfsv4] Proposed Working Group Charter

Spencer Dawkins at IETF <> Tue, 29 August 2017 18:12 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E8610132D76; Tue, 29 Aug 2017 11:12:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id RH9UsqVcqkV4; Tue, 29 Aug 2017 11:12:26 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4002:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0E8F7132C48; Tue, 29 Aug 2017 11:12:26 -0700 (PDT)
Received: by with SMTP id h127so20866991ywf.3; Tue, 29 Aug 2017 11:12:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=MzC9hzy7kay5aDJDnhSrKTUFoj7fzX58JvSfFJl0UtE=; b=N2+9fJxydB2s374/pgEKOtfhRaF+NxR8rQPpeGyekrC2AdFXLCEYR+B/4mw6mpLFIF 60cm0oQZHMfbiM4XH+nlTgv0L2GyA9CEPuK44cFFEXHPFupluLeTdP602LfD/6xROFlW lkd+CgyXIBO9O/JDsjFINJ+o0JkWddN3ZfoMyAIOXDgvJd6XbDNWO0dFstUKh2yfFO4x q0FunFB2r6AY4gq7TMS7S1ZArDpsH+KbiPZhmldMOqvmx+I4/VSU6HViTGSsLAEyCDPD X2EHTahFsGD2S3eRQDGjYqDp1KVD1TNJKR8sp6JQEp9OL5cfCO57AQy4nixbfx3NtJ1C bVbQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=MzC9hzy7kay5aDJDnhSrKTUFoj7fzX58JvSfFJl0UtE=; b=ALU1zAxs5xBJ4J5r+xYI6ICWAsjPFEt2SW/slmiZXtBNM6yGYlL9yikji+6LiRPiHB iaQhfCTZS9A5/3ae4NODEX6QJexv+UWka4WWZQ15SFAPOZf1cMCqKpBHuoJQCU02z6PA R5oRPT82hsZyAgVbE+e6x6m6pwc3RLjro3De+tB/8Ogxr5y0UnoZ22NWeCm9deVrwFqq 6skxJtcCt7tSXvcDLXq6pXqyl4oaYu/Jd+fVvPxiR1eOMzdiGDw4pZnrJBUW/2Glf8Lq Tn4Vf5Vj47xAokjKpJTeCl/p6rNijQWWUx5ceG05b863NZMLTuhnDZ55U6VDWE7gCjsW m2cA==
X-Gm-Message-State: AHYfb5glBxXxKTlY/26GH/8cIWuqoB6NBq8PUju6IgCB5J1DefLFb14V nHZ6sKClh79HI/BSxRimHXd8MGZhag==
X-Received: by with SMTP id j187mr1174774ywg.311.1504030344984; Tue, 29 Aug 2017 11:12:24 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Tue, 29 Aug 2017 11:12:24 -0700 (PDT)
In-Reply-To: <>
References: <> <> <> <> <> <> <>
From: Spencer Dawkins at IETF <>
Date: Tue, 29 Aug 2017 13:12:24 -0500
Message-ID: <>
To: spencer shepler <>
Cc: David Noveck <>, "" <>,, "" <>
Content-Type: multipart/alternative; boundary="94eb2c09236e71bf9c0557e85a64"
Archived-At: <>
Subject: Re: [nfsv4] Proposed Working Group Charter
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NFSv4 Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 29 Aug 2017 18:12:28 -0000

Dear NFSv4 Chairs and working group participants,

This is what I've got in the datatracker as version 05-00 of the charter.

It is intended to be what David proposed in this thread, with some
abbreviation expansions and paraphrasing. I did leave the part about adding
milestones for deliverables within charter, and we'll see if other ADs
think that should change.

Please let me know how this looks, and I'll start Internal Review.



Network File System version 4 (NFSv4) is the IETF standard for file

To maintain NFS Version 4's utility and currency, the NFSv4 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 problems
with the protocols as currently specified, to accommodate needed file system
semantics, and to respond to technological developments in the areas of
networking and persistent storage/memory.


The working group's experience has been that, as NFSv4 implementations
and deployments continue, clarifications and corrections to existing RFCs
are needed.

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

The NFSv4 working group is chartered with vetting 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 new RFCs that provide implementation guidance,
editorial modification or technical updates to existing RFCs.

Since the new NFSv4 versioning framework has been approved, these technical
updates to NFSv4 minor versions could include limited XDR changes.


The NFSv4 protocol is designed to allow extension by the definition of
new operations, new attributes, and new Parallel NFS layout types, as well
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.

New milestones that fall within the scope specified in this charter can
be added to the list below after working group consensus and upon
approval by the responsible Area Director.

Proposed Milestones

|   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                           |