[nfsv4] Proposed Working Group Charter (ascii version)

David Noveck <davenoveck@gmail.com> Thu, 24 August 2017 10:33 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 B549F132742 for <nfsv4@ietfa.amsl.com>; Thu, 24 Aug 2017 03:33:35 -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 JH9-wU2KbwSb for <nfsv4@ietfa.amsl.com>; Thu, 24 Aug 2017 03:33:33 -0700 (PDT)
Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (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 8E9C51321C9 for <nfsv4@ietf.org>; Thu, 24 Aug 2017 03:33:33 -0700 (PDT)
Received: by mail-it0-x231.google.com with SMTP id a73so962581itd.1 for <nfsv4@ietf.org>; Thu, 24 Aug 2017 03:33:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=N862QF6IsCE6cVoBf80bILdXPlrbfEXqCQAVNg9zeQk=; b=BOgq4GGVzlkcEjB40AddG1IUd8hDcvcnd1O46vMAL0ac//BEXDI3vrI7wry9aRL2sa 00voH4l2zeageS/JR4ws+rCclUsfPCRbd1nUqxnuXNAbp//C0dZFP6e8D+8RGvJf1bwl kuGS6xfDGaPmybEVlTXyeu0dbut3Q/6Wc+JjWOFXrM8+XxYovg9YZ/veMLmmAQ/uGBTZ 9dJBUFld4Hsgj+GYQx5xGQcFRy36vdOnW0s/kUqYwATRpsnVj5ihzMZGbnDcTMk4IlpF eUeBHvvZQGndXueZqc/0qQfLSfuiYqRrhkixcfLkIW9yhqoOvuQz13x/I8W+ifsPXXlL Tn+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=N862QF6IsCE6cVoBf80bILdXPlrbfEXqCQAVNg9zeQk=; b=Zc6rwNMGnLZ5wcf8wn1e20+Hf3PuvLoSzifcqhZcGWkv2Sw/8wRxy3sNOHnl+bDNBV Zq2wz8YXoysmjNxjr7JBBzOVfA5crbdvuQ5vS5HwsFNOUBgko73vDGHD90zqG5xs3CRy CLKW94atXe0aKOnhJJ/sVBsOnVavRCqTLS1vp8j6h8sS7bz2NMjHpUMsfA9Ttl0i6K9o 3rKezIKp1PdA2FBcz6E7PUTFeRvRw5XMgFl2g2vQxOHpxT/ap5UfndRUwPR/7DVGbgop 2qLaCBfWOCMtQYoHLUinh5qJcf+nUgu5yM5WRoPGxMCGJB5lVDmS8JlUERi/qzZyBpHZ Il3Q==
X-Gm-Message-State: AHYfb5jEbn6OoGaTW+sFIqRdw7ecXXZACzX//HygI06oCievzKujT6/C AXQtIqyS0EGUGCKOrVlfkkNpGSEuWA==
X-Received: by with SMTP id 72mr5402526ity.117.1503570812295; Thu, 24 Aug 2017 03:33:32 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Thu, 24 Aug 2017 03:33:31 -0700 (PDT)
Received: by with HTTP; Thu, 24 Aug 2017 03:33:31 -0700 (PDT)
In-Reply-To: <CADaq8jcqmkT5pgCsVvZjs+dQ+p4LKgXWTOaD5B8=kA4xm2XnMw@mail.gmail.com>
References: <CADaq8jcqmkT5pgCsVvZjs+dQ+p4LKgXWTOaD5B8=kA4xm2XnMw@mail.gmail.com>
From: David Noveck <davenoveck@gmail.com>
Date: Thu, 24 Aug 2017 06:33:31 -0400
Message-ID: <CADaq8jdeNMpyuRxy6rCgb=0871GSv9xHafToY42KHCAxzo+e6g@mail.gmail.com>
To: nfsv4@ietf.org
Content-Type: multipart/alternative; boundary="001a1143849c29633e05577d5cf1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/Mja2OXjxGGiQvysDTbo86ng8_vA>
Subject: [nfsv4] Proposed Working Group Charter (ascii version)
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: Thu, 24 Aug 2017 10:33:36 -0000

NFSv4wg Charter

Near-Final Proposal

Including Proposed Milestones

David Noveck

August 24, 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
of minor versions.

Similarly, associated ONC protocol components that have a
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
with existing features, before adopting them as working group items and
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 after working group
consensus on 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                           |