IETF Logo Mail Archive

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

spencer shepler <spencer.shepler@gmail.com> Sun, 24 September 2017 12:07 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 E21D2133059 for <nfsv4@ietfa.amsl.com>; Sun, 24 Sep 2017 05:07:28 -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 62hHt-CTDZvp for <nfsv4@ietfa.amsl.com>; Sun, 24 Sep 2017 05:07:27 -0700 (PDT)
Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (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 1CD53132A89 for <nfsv4@ietf.org>; Sun, 24 Sep 2017 05:07:27 -0700 (PDT)
Received: by mail-oi0-x22a.google.com with SMTP id l74so3669589oih.1 for <nfsv4@ietf.org>; Sun, 24 Sep 2017 05:07:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=D/9C7tsSw2RtO4Kmvm1CtrmIKBNd/L3rjDok7LGFJIU=; b=DjMrKCifXDOFFg/2TxegmVd990qxRibnRR4oM69oP+94i2gvpKskhcTB8GbSxbMPTJ XUYs87eZGkFBn9FPPUIvPpTOUaCFWzSzoVUgTDfB9Dxf66Y2oZstAzzmp7SIfh++YH/x 90GnNZWfU1UBHugrzw1jhy6Rj4F0HjElXF8WyWMUEnjdgMgpIg5E9JioGnXKDZNZa/aS RvBbvnY3tCtmvSH6wgbVtKg0EKh6KORbt/XNo2rT2AJvYVy86UkUbh4nOF4vUKgW0MX/ CrQQ3xcrwkOnmbFSU9I7CKzXYfzERCliYBLjlj+5E2cpTwAb0rASwEgfuBTL/U6Lfi3O 9bQw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=D/9C7tsSw2RtO4Kmvm1CtrmIKBNd/L3rjDok7LGFJIU=; b=jftvx62//V4sG6urqEMZntP5AQKBQZBpfJImYBWK2T/g89x9Ffe74qre2SPeydE7eX LEJncB7jr5nmB9Rm6Ht3na5QvljtrDUriZzUoB6iaKIf3rlO/Z0GZcO2oWB+5OpfqQCE KbFUZbEB2gfZt+2Xr3xWg2+aZCKxtOXJ1JnDym4HEh8NRo1L7jsvbOuv1UQ3AyifwWjv iHPu9ddWjDXkAW6uM0SZNbIN6F5J9+zgqafA8u+EgmaXCqCpqwYM0eLbnTZR9+mijSVi Hkn40amqBNH3R1IF3gUWUWRQiXFzWJsl6cmGP2KIHKfMc/24PUHCEE1dSYFdZgVpU+zl cfVQ==
X-Gm-Message-State: AHPjjUgpz4k6n1WQvx+/HQIO6Chrr8e+MXRhRXB8w3KRzK1Lb7j4YCP7 FS6vRCeyqHvbvIwgjwF7J602J+Xj50lkS/7a5CY=
X-Google-Smtp-Source: AOwi7QCPRDQIRkDWoY2JiFbqDc8+dmyarlCII7MZ2oZ7NcxKX0g1oKbZghNHFKSglPwFt2QQaG1YkSJtJ+Ocy0kRdks=
X-Received: by 10.202.80.78 with SMTP id e75mr5766428oib.1.1506254846366; Sun, 24 Sep 2017 05:07:26 -0700 (PDT)
MIME-Version: 1.0
References: <CADaq8jen_e1PwJwdV_kGDJaznvtZHOGqhThnvw-x=xN8KvPbdA@mail.gmail.com>
In-Reply-To: <CADaq8jen_e1PwJwdV_kGDJaznvtZHOGqhThnvw-x=xN8KvPbdA@mail.gmail.com>
From: spencer shepler <spencer.shepler@gmail.com>
Date: Sun, 24 Sep 2017 12:07:15 +0000
Message-ID: <CAFt6Ban1H9U7vXfUs3HE35ddmhLRx3Ew58H1m-k=2aUbB6qyjA@mail.gmail.com>
To: David Noveck <davenoveck@gmail.com>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: "nfsv4@ietf.org" <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="001a113d64b20f1dbe0559ee49cd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/yGYp5wWgzc6gvNNx5azMVtjmCts>
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: Sun, 24 Sep 2017 12:07:29 -0000

Thanks, Dave. This is okay with me.

Spencer

On Sun, Sep 24, 2017 at 7: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).                                    |
> ========================================================================
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4
>

v2.23.0 | Report a Bug | By Email