Re: [nfsv4] Adjustomg milestones to address Benoit's comments

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Tue, 10 October 2017 16:52 UTC

Return-Path: <spencerdawkins.ietf@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 AB09313495E for <nfsv4@ietfa.amsl.com>; Tue, 10 Oct 2017 09:52:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_NONE=-0.0001, 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 azUi9GLVu8QX for <nfsv4@ietfa.amsl.com>; Tue, 10 Oct 2017 09:52:06 -0700 (PDT)
Received: from mail-qt0-x22e.google.com (mail-qt0-x22e.google.com [IPv6:2607:f8b0:400d:c0d::22e]) (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 345E1134F83 for <nfsv4@ietf.org>; Tue, 10 Oct 2017 09:42:32 -0700 (PDT)
Received: by mail-qt0-x22e.google.com with SMTP id 34so36026002qtb.13 for <nfsv4@ietf.org>; Tue, 10 Oct 2017 09:42:32 -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=dQrKNdD85PZ1UGM48bMzw518pMTFoCT9S7LGOna/rdk=; b=blU8PFXP6tHUgCiG9nhKjytep9XFN94bz6B2vfh66hYE38dUsOBnH6J0KiMc27Xw6t /yJVUHoUuVqiF2Eqs7M9niJR3yFzRnfE+lbWfoPguAoSqluHsPf4s7ZcDeTwqMpni3ir vGBxl7pme0gRisXTH8Ilu6ptMSE/7GP3h+0e67/dh7PZ2ilWYJAQwOz88DR/qQ23Kz3c Vujl/sgmQ1mOkf1RzveBMazlBlOpx43gY+Qr8AOA8M6iH0fm0MrhRbxnpHWTYtx+++13 ElEieDU/lIL5dLpnE2PcnHXq3dUPWHh2olB07qn0JB0psJPr8fl9jtWEXhOcwwOjT5vS ffgw==
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=dQrKNdD85PZ1UGM48bMzw518pMTFoCT9S7LGOna/rdk=; b=GfzVyECFj76BE1Euprc9W4VafXa05ZxDnH00Gw7yTo22bgcUMjmwiOIjAwkj3+YZwz Y0wCtqIUoWwwGlW3FuTfbM8kJx38kPliufpwp+v5YUY0zhFJWB30mzfKcYuUCGbr1/TR gci6uSK9U9Dgnc6C98aqD8Kny/VzMPEHmquZUs7/MR3LAFppqzETntwfWIloO1MSXi8d JvDuEqNTaN9v72cce8dDWiYu6jNCrWkxjkdh7QHGq4N3WyoL/0AC3SaHVpQrbyk1Bw5m 0AKy9gYj2t6AQPtXaVGcuTxxLlTAiFIQEd1VlYUlHNqzmi2P48b44zIfpUAHHHSAig3C XPXA==
X-Gm-Message-State: AMCzsaUNCQcz1saevdQtn/Yp+2gFDo0ftY4aB/pB4Qy5kdWDSY9eHGN6 2ZQx7jeqRbD+5GUp87LcfGrRxpOZQdMhd/QuNUPXCg==
X-Google-Smtp-Source: AOwi7QC3d+/eXGaqT8XESMoVOnDGKs645b6O7fsTxeXWBhXJWJi4tZwcnKvCgb3cxhrXlBpkw4IZxkhzH/3uCERr0dE=
X-Received: by 10.129.1.2 with SMTP id 2mr2742672ywb.66.1507653751162; Tue, 10 Oct 2017 09:42:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.107.68 with HTTP; Tue, 10 Oct 2017 09:42:30 -0700 (PDT)
In-Reply-To: <CADaq8jen_e1PwJwdV_kGDJaznvtZHOGqhThnvw-x=xN8KvPbdA@mail.gmail.com>
References: <CADaq8jen_e1PwJwdV_kGDJaznvtZHOGqhThnvw-x=xN8KvPbdA@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 10 Oct 2017 11:42:30 -0500
Message-ID: <CAKKJt-eFox6FiTcLSvmgw7EVaBVn6cZGDiD+Y7Ae72Ld=2jn_Q@mail.gmail.com>
To: David Noveck <davenoveck@gmail.com>
Cc: "nfsv4@ietf.org" <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="001a114293c84850ba055b33fe05"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/i2plprs1SKiEpD8uP1ebxOph-gI>
Subject: Re: [nfsv4] Adjustomg milestones to address Benoit's comments
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: Tue, 10 Oct 2017 16:52:08 -0000

Dear NFSters,

On Sun, Sep 24, 2017 at 6:28 AM, David Noveck <davenoveck@gmail.com> wrote:

> Benoit's comments could be read as suggesting two milestone's per
> document,  but I've continued to use the one-milestone-per-document
> framework suggested by David Black as more manageable and understandable.
> In shifting most milestones from WGLC to "submit final" I've added three
> months per milstone,assuming that the documents will have sufficient review
> before entering WGLC to avoid major issues arising at that time.  The one
> document that retains a WGLC milestone is one that may well never be
> published as an (informational) RFC, although the working group is free to
> decide otherwise:
>
> In any case, the following is a proposed replacement section.
>
> ========================================================================
> |   Date  |                Milestone                                   |
> |---------+------------------------------------------------------------|
> | 6/2018  | WGLC for draft-ietf-nfsv4-migration-issues (Informational) |
> |---------+------------------------------------------------------------|
> | 6/2018  | Submit final document describing use of NVMe in accessing  |
> |         | a pNFS SCSI Layout (as Proposed Standard)                  |
> | 11/2018 | Submit final document describing NFSv4.0 trunking          |
> |         | discovery (as Proposed Standard)                           |
> | 1Q2019  | Submit final document describing NFSv4.1 trunking          |
> |         | discovery (as Proposed Standard)                           |
> | 1Q2019  | Submit final document describing Transparent State         |
> |         | Migration in NFSv4.1 (as Proposed Standard)                |
> | 2Q2019  | Submit final document describing CM private data           |
> |         | convention for RPC-over-RDMA version 1 (Informational)     |
> | 3Q2019  | Submit final document describing pNFS RDMA Layout (as      |
> |         | Proposed Standard)                                         |
> | 4Q2019  | Submit final document defining RPC-over-RDMA Version 2     |
> |         | (as Proposed Standard).                                    |
> ========================================================================
>

I saw an "OK with me" from Spencer (S), and no objections, so I've approved
these in the datatracker.