Re: [nfsv4] Proposed Working Group Charter

spencer shepler <spencer.shepler@gmail.com> Mon, 28 August 2017 15:34 UTC

Return-Path: <spencer.shepler@gmail.com>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E905C132C41; Mon, 28 Aug 2017 08:34:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QW0F_XoRLQiS; Mon, 28 Aug 2017 08:34:18 -0700 (PDT)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (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 5681B132355; Mon, 28 Aug 2017 08:34:18 -0700 (PDT)
Received: by mail-oi0-x22d.google.com with SMTP id r203so6777906oih.0; Mon, 28 Aug 2017 08:34:18 -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 :cc; bh=cOjaAnGTx+vaOFH/pNM7kjkhoDpTaRBPAzWqSCr1GqU=; b=OE0/w/ER+aroIhjsU5KQCmM+1889ECw9G6LXRcAPHtQ9SPpOOgiXgdGNlVVp9XFEAW cQsJs8hazdzCd1cGXZaWuov7w53K7e9YNYMPmx38jq0/fiGjYvub8+ADKISbwWKG/fAy 00nf4cTX3wIuG38lXLEreok8Qk70waQ13lJsSzZqveq5FT03yubwXs+XOWHWgm3IAqt1 pau2evhXWJV5BJIXfPzQHOF/LqYxvBPmBYidCzO5Fz/5pWTutgE7AtGVttaM/uPljD75 sA+3/3U2dG9ld+jmWuDj7Foa4DUkS9ZzJHExz/lXC2q0gr2GELVdX4jGUcf2qHv4NPID mZcg==
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:cc; bh=cOjaAnGTx+vaOFH/pNM7kjkhoDpTaRBPAzWqSCr1GqU=; b=YkwFH52OD3+/gonP+sfnURKrXgElXXTt9OgYpJPPV3XFj3RKKhpxwEsV7Fg5Ck/CXo aTkwCSSyVygNMCKu/OkcrhzA7YYmlxCTOOLJMS0vnUe9COijpAUMCw+Js6+1MdWoDyUU yEeASn3idmRpQOtIsZMttiLh75O41LEP1ZfDd3ZIpCKlXq3rIl2+Y6T8sSzM9jBS4Nb1 uynj8wZ9FiwXcjQqXwmDP/vxS0A51urwmzQzVVXaXw0vSWXxfDnWAR6wDEnAkv2LuCwl UtxogzNhQs9lXgrzJUoBiqh1SSbnvVDOz3CbUZ+ssmv6r3g9zqTeG+/Rpv6CAaET9RAW dICw==
X-Gm-Message-State: AHYfb5j+y8tFitnO0KjzKtHJLFG4iTb8Car7ZAeciVjDPZbyA6/vWauU ukTRbTUH1YG1EZhJ7IjQcAX66jlLEQ==
X-Received: by 10.202.83.133 with SMTP id h127mr752597oib.217.1503934457615; Mon, 28 Aug 2017 08:34:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.74.137.213 with HTTP; Mon, 28 Aug 2017 08:34:17 -0700 (PDT)
In-Reply-To: <CADaq8jdNRenxK0yfXC9xpmCidfzuetcrC=dhkK7w2TnehZ6X4g@mail.gmail.com>
References: <CADaq8jdNRenxK0yfXC9xpmCidfzuetcrC=dhkK7w2TnehZ6X4g@mail.gmail.com>
From: spencer shepler <spencer.shepler@gmail.com>
Date: Mon, 28 Aug 2017 08:34:17 -0700
Message-ID: <CAFt6Ba=qLqJGN2XCy_RE9sMMkU1-TjommK9Zhz7Y6Pvo2+E4hQ@mail.gmail.com>
To: David Noveck <davenoveck@gmail.com>
Cc: "nfsv4-chairs@ietf.org" <nfsv4-chairs@ietf.org>, nfsv4-ads@ietf.org, "nfsv4@ietf.org" <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="001a113dd5461ca5f20557d207d9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/We1fa-akR9OoJkcEBYrXRH4fK_8>
Subject: Re: [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 15:34:21 -0000

Thanks, Dave.  The charter update does look ready to go.  Will leave it to
Spencer D. on next steps and his feedback.

Spencer S.


On Mon, Aug 28, 2017 at 7:04 AM, David Noveck <davenoveck@gmail.com>; wrote:

> The attached file is based on what was presented at IETF99.  It includes
> some
> 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 proposal
> 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,
> XDR, and RPCSECGSS.
>
> 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.
>
> 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                           |
> ========================================================================
>
>
>