[nfsv4] Fwd: I-D Action: draft-ietf-nfsv4-scsi-layout-10.txt

David Noveck <davenoveck@gmail.com> Tue, 06 December 2016 12:00 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 D5B9A129996 for <nfsv4@ietfa.amsl.com>; Tue, 6 Dec 2016 04:00:56 -0800 (PST)
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 mCQ4bDOJQ2U3 for <nfsv4@ietfa.amsl.com>; Tue, 6 Dec 2016 04:00:53 -0800 (PST)
Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (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 9D132129999 for <nfsv4@ietf.org>; Tue, 6 Dec 2016 04:00:50 -0800 (PST)
Received: by mail-oi0-x22c.google.com with SMTP id w63so375433624oiw.0 for <nfsv4@ietf.org>; Tue, 06 Dec 2016 04:00:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fJnKpMZWPnM3/fqtc/SPUwxgTE5XXJfMZHxItzjfJ9s=; b=z3T+YyMW2m8H4jZPtyQetUUOEzu1Wg0lb0flc1hiQ/ysPwuAPFsi6ne5nQkdZfU30D iVZiEo/rT0Bc2j0a1wateBEg4VuczJqfTfn6GFVtz6Wt1JdQbejsmMQtcsEoAzu7A9vp oFA+mUeb3hJBASDliaVfD2fTaRFyWfJ4OPj1S/+zGg02Vo6ocGt8jr6pyFplhcjxbRMG jn6CIuzFJloC+x/GjAycBrGtCk9tWQOO00H6+H7875HGujeGpXld9+V379eAXsSPVBwG EEx5TlvpeaZJhrFMpNu0/mWhrkOv+rprS/D+xIxm66KhBrsPYf05LUJoyCGZnIznJR6a kF/Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=fJnKpMZWPnM3/fqtc/SPUwxgTE5XXJfMZHxItzjfJ9s=; b=SDSmCD1jx9wiKGJHaE+0jmm5zP3cE2U+7pSW7jFSXgNlFU4W80cihfeDtgkgCJwWvI EdI/thwRS78098vFNzi6w3CqXrVboWS64ektkCZHy76br8PktlpbC4LBc/w3OYDe5zt/ 97uxy610pOdyDO38YBClkvTITdNvxSYWxbTWF/nG3Ggl80zU7J1YOBYByZ6LMP9tHXvM unUcI5wtPLjFxjflB5ND2OWNfEKuj05jv56LxX8T9AJyUb/Y/RAFNfZ3lpoMHoX0xrWp BY+97nVgmOOr3QBFfbHgRltAhYaxxZ4B0LA15lHVksyL4s/omamxVRKOLXyMGpaE88BB qE1Q==
X-Gm-Message-State: AKaTC006S2xl0jh64V46PEYEuU7p8QFcNMTthCxwT82CRHtILdBobxSk82dNJ9v+pgvic1xWVZxX5kYInrTA1A==
X-Received: by with SMTP id u198mr29894386oia.165.1481025649704; Tue, 06 Dec 2016 04:00:49 -0800 (PST)
MIME-Version: 1.0
Received: by with HTTP; Tue, 6 Dec 2016 04:00:49 -0800 (PST)
In-Reply-To: <148101397648.1854.13150900676997654570.idtracker@ietfa.amsl.com>
References: <148101397648.1854.13150900676997654570.idtracker@ietfa.amsl.com>
From: David Noveck <davenoveck@gmail.com>
Date: Tue, 06 Dec 2016 07:00:49 -0500
Message-ID: <CADaq8jcZb4HEyiP3xJtBgeHRKDksTanXDOU-+XjgZ7aLSYr4CA@mail.gmail.com>
To: Christoph Hellwig <hch@lst.de>
Content-Type: multipart/alternative; boundary="001a113e574ec103820542fc2756"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/r3Sg_pOo80mn0SsMck8K41x2RB8>
Cc: "nfsv4@ietf.org" <nfsv4@ietf.org>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Subject: [nfsv4] Fwd: I-D Action: draft-ietf-nfsv4-scsi-layout-10.txt
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.17
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, 06 Dec 2016 12:00:57 -0000

Congraulations on getting out what I hope will be the final draft of this
needed document.  I hope publication will soon follow.

As I understand it, this document completed last call in December 2015 and
will probably wind up taking over a year to get from there to actual
publication.  Although there is no WGLC date recorded in the data tracker,
it appears that the 600-page RFC 5661 took about four months to go from
publication of the draft that went into IESG review to actual publication.
I didn't think of that review as speedy but now it seems so.

It appears that one-year publication delays are becoming depressingly
common.  I hope that they will not become the new normal.

I think we need to understand why this is happening and try to improve the
situation.  Regarding Spencer's suggestion that authors and other
rank-and-file wg members might not be putting sufficient effort into the
process, I see no evidence that this is the case with this document.  Does
anyone think otherwise?

I would appreciate hearing the Spencers' views about the pace of review and
what might be done to improve it.   I think those in the IETF
superstructure need to take this issue more seriously before they start
pointing fingers at the authors and other rank-and-file wg members.

Consider draft-ietf-nfsv4-rfc5666bis.  The authors have put a lot of work
into this effort to resurrect an RDMA transport for NFS (and potentially
other RPC protocols).  It is not reasonable for it to take almost 8 months
to go from Consensus on 4/17 to now with no substantive issues found with
the document and no publication request.  I think the authors are owed an
explanation and need some sort of assurance that the problem is being

Although "excruciatingly sluggish" did seem harsh to me, I can't say it is
inaccurate.  We have a problem.

---------- Forwarded message ----------
From: <internet-drafts@ietf.org>
Date: Tue, Dec 6, 2016 at 3:46 AM
Subject: [nfsv4] I-D Action: draft-ietf-nfsv4-scsi-layout-10.txt
To: i-d-announce@ietf.org
Cc: nfsv4@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts
This draft is a work item of the Network File System Version 4 of the IETF.

        Title           : Parallel NFS (pNFS) SCSI Layout
        Author          : Christoph Hellwig
        Filename        : draft-ietf-nfsv4-scsi-layout-10.txt
        Pages           : 29
        Date            : 2016-12-06

   The Parallel Network File System (pNFS) allows a separation between
   the metadata (onto a metadata server) and data (onto a storage
   device) for a file.  The SCSI Layout Type is defined in this document
   as an extension to pNFS to allow the use SCSI based block storage

The IETF datatracker status page for this draft is:

There's also a htmlized version available at:

A diff from the previous version is available at:

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:

nfsv4 mailing list