Re: [nfsv4] I-D Action: draft-ietf-nfsv4-rfc5667bis-11.txt

David Noveck <davenoveck@gmail.com> Fri, 14 July 2017 16:53 UTC

Return-Path: <davenoveck@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 20295127369; Fri, 14 Jul 2017 09:53:56 -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 12Wca-kEWeMl; Fri, 14 Jul 2017 09:53:54 -0700 (PDT)
Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (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 D1954126C22; Fri, 14 Jul 2017 09:53:53 -0700 (PDT)
Received: by mail-it0-x232.google.com with SMTP id m84so28224719ita.0; Fri, 14 Jul 2017 09:53:53 -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=QJa+qKssd3sY3Zoe2016risz7VgPY4rmkNCwbxRI6y0=; b=bxMWyTBFhtXXkUtdbXswZ/ECp5MWFz7XCecwCIsz3gvCA5qMyrw9m1IDJCVAYx9nh5 KG1LglcGW/+m6cccJIoWSjqbCVTLcZRSeKLAeD9gBZBGHQsFFuczsnhyihp2JIgc2dn4 33PGE/H2QqiiWSE1f/oARjOPgY7Fge70A4DUmgMTfdMpkKaa94sZnPnVaklX3Qzr9V+H nUe+M5gVqcY5WZoFrCk9PoCUmMonhEjvp/i+4WaGvRuQcHbRxj9kzsVn8hSYYum7xu1W UBXRzUth0uARA1+G0zyUPWX0vhV7NGz0H9fe+3ShKFGvnV96NlD4zCB4/bjl/URjjpGX znNQ==
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=QJa+qKssd3sY3Zoe2016risz7VgPY4rmkNCwbxRI6y0=; b=lD+zl8GMLBuYOwIQ8/4ZDjGzd7l5JRr9CWBbT5Pcx6thvT9D4WIA+faitno16sxFRq og8p38XTYVVOPEol2KoLrdaPrSfW6iABOemhfBvv+1KqEeyrXvJoYF9iY7oS2BgJC4gS t/cn6jOLiy8dh2ti+K01nG8VPlMMKcKdRfwpRlRp4xuLyyz+XUxKNEVcMwKo5BDXECD3 5nuaPTvFuTaGmIjhiGorJ20V9ncU10vIDHMPVHcU1Zn4NT3+Pg5dYlKTZ2TGUtwji3Xi ti3DNHpCcEgkxZ65blpU02KA84CXcAfSJ08g8HXX4UjxmrEWAivac9K9YnDp327307Jt c+PQ==
X-Gm-Message-State: AIVw113rqStCYO9tiSFOOVAAfYlTW7Qdo+phRVfPQZ8nNsj7pVUVDpxV 2Ai94ZC/7u/sL7EziaooUnv6fJ6BAg==
X-Received: by 10.36.34.140 with SMTP id o134mr4570944ito.22.1500051232977; Fri, 14 Jul 2017 09:53:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.57.86 with HTTP; Fri, 14 Jul 2017 09:53:52 -0700 (PDT)
In-Reply-To: <83BADEC9-58CE-4208-8FB1-12CE44F6234D@oracle.com>
References: <149434320626.31731.1164417608724742692@ietfa.amsl.com> <A7B1204A-5F3A-4015-96F0-18E3F550C495@oracle.com> <CAFt6Ba=5wnyJZ-RbEeMRtSsrgE2iSgjERowCCzsju+pADd0AVw@mail.gmail.com> <6E769256-E907-49EA-A907-33C4C8F77E11@oracle.com> <83BADEC9-58CE-4208-8FB1-12CE44F6234D@oracle.com>
From: David Noveck <davenoveck@gmail.com>
Date: Fri, 14 Jul 2017 12:53:52 -0400
Message-ID: <CADaq8jdCnNr5ZFzGajfWtZ=G-XJFR9UBM5DuYutqWv2=rgM3xw@mail.gmail.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: spencer shepler <spencer.shepler@gmail.com>, Spencer Shepler <sshepler@microsoft.com>, Brian Pawlowski <beepy@purestorage.com>, Brian Pawlowski <beepee@gmail.com>, "nfsv4-chairs@ietf.org" <nfsv4-chairs@ietf.org>, NFSv4 <nfsv4@ietf.org>, nfsv4-ads@ietf.org
Content-Type: multipart/alternative; boundary="001a1144d0eae3007f055449e46c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/WWkSqMIrqG09NxMIWFXfqqMR0pQ>
Subject: Re: [nfsv4] I-D Action: draft-ietf-nfsv4-rfc5667bis-11.txt
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: Fri, 14 Jul 2017 16:53:56 -0000

I think the state definition in RFC6174 might help your search even though
it will
not, by itself, provide a reason:

4.2.9 <https://trac.tools.ietf.org/html/rfc6174#section-4.2.9>.  WG
Consensus: Waiting for Writeup

   A document in the "WG Consensus: Waiting for Writeup" state has
   essentially completed its development within the working group, and
   is nearly ready to be sent to the IESG for publication.  The last
   thing to be done is the preparation of a protocol writeup by a
   Document Shepherd.  The IESG requires that a document shepherd
   writeup be completed before publication of the I-D is requested.  The
   IETF document shepherding process and the role of a WG Document
   Shepherd is described in RFC 4858
<https://trac.tools.ietf.org/html/rfc4858> [RFC4858
<https://trac.tools.ietf.org/html/rfc4858>]

   A WG Chair may call consensus on an I-D without a formal WGLC and
   transition an I-D that was in the "WG Document" state directly into
   this state.

   The name of this state includes the words "Waiting for Writeup"
   because a good document shepherd writeup takes time to prepare.


So I guess you need to ask Spencer S. about the issues/difficulties
he is finding as he

prepares the writeup.  That might provide an explanation for the delay
we've seen so far,

although I expect that, given that two over months has elapsed, you
would prefer an ETA

in the near-future to an explanation.





On Wed, Jul 12, 2017 at 10:41 AM, Chuck Lever <chuck.lever@oracle.com>
wrote:

> Hello chairs-
>
> According to the datatracker, the document status is still
> "WG Consensus: Waiting for Write-Up". Is there a reason this
> document is not moving forward?
>
>
> > On Jul 5, 2017, at 2:06 PM, Chuck Lever <chuck.lever@oracle.com> wrote:
> >
> > Hi Spencer-
> >
> > Now that RFC 5666bis and rpcrdma-bidirection have been published,
> > it's time to push rfc5667bis. Is there anything more you need me
> > to do to get this going?
> >
> >
> >> On May 9, 2017, at 12:09 PM, spencer shepler <spencer.shepler@gmail.com>
> wrote:
> >>
> >>
> >> Thanks, Chuck.  Will move this one forward.
> >>
> >> On Tue, May 9, 2017 at 8:23 AM, Chuck Lever <chuck.lever@oracle.com>
> wrote:
> >> Hi Spencer-
> >>
> >> Revision -11 includes yesterday's fixes discussed on list.
> >> Please consider this revision for IESG review.
> >>
> >>
> >>> Begin forwarded message:
> >>>
> >>> From: internet-drafts@ietf.org
> >>> Subject: [nfsv4] I-D Action: draft-ietf-nfsv4-rfc5667bis-11.txt
> >>> Date: May 9, 2017 at 11:20:06 AM EDT
> >>> To: <i-d-announce@ietf.org>
> >>> Cc: nfsv4@ietf.org
> >>>
> >>>
> >>> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> >>> This draft is a work item of the Network File System Version 4 of the
> IETF.
> >>>
> >>>       Title           : Network File System (NFS) Upper Layer Binding
> To RPC-Over-RDMA Version One
> >>>       Author          : Charles Lever
> >>>      Filename        : draft-ietf-nfsv4-rfc5667bis-11.txt
> >>>      Pages           : 19
> >>>      Date            : 2017-05-09
> >>>
> >>> Abstract:
> >>>  This document specifies Upper Layer Bindings of Network File System
> >>>  (NFS) protocol versions to RPC-over-RDMA Version One, enabling the
> >>>  use of Direct Data Placement.  This document obsoletes RFC 5667.
> >>>
> >>>
> >>>
> >>> The IETF datatracker status page for this draft is:
> >>> https://datatracker.ietf.org/doc/draft-ietf-nfsv4-rfc5667bis/
> >>>
> >>> There are also htmlized versions available at:
> >>> https://tools.ietf.org/html/draft-ietf-nfsv4-rfc5667bis-11
> >>> https://datatracker.ietf.org/doc/html/draft-ietf-nfsv4-rfc5667bis-11
> >>>
> >>> A diff from the previous version is available at:
> >>> https://www.ietf.org/rfcdiff?url2=draft-ietf-nfsv4-rfc5667bis-11
> >>>
> >>>
> >>> Please note that it may take a couple of minutes from the time of
> submission
> >>> until the htmlized version and diff are available at tools.ietf.org.
> >>>
> >>> Internet-Drafts are also available by anonymous FTP at:
> >>> ftp://ftp.ietf.org/internet-drafts/
> >>>
> >>> _______________________________________________
> >>> nfsv4 mailing list
> >>> nfsv4@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/nfsv4
> >>
> >> --
> >> Chuck Lever
> >>
> >>
> >>
> >>
> >
> > --
> > Chuck Lever
> >
> >
> >
> > _______________________________________________
> > nfsv4 mailing list
> > nfsv4@ietf.org
> > https://www.ietf.org/mailman/listinfo/nfsv4
>
> --
> Chuck Lever
>
>
>
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4
>