Re: [nfsv4] IETF 98 - NFSv4 WG meeting (soliciting agenda items)

David Noveck <davenoveck@gmail.com> Tue, 14 February 2017 15:16 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 AEB6E1294B9 for <nfsv4@ietfa.amsl.com>; Tue, 14 Feb 2017 07:16:56 -0800 (PST)
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 nIXIo49epV5Z for <nfsv4@ietfa.amsl.com>; Tue, 14 Feb 2017 07:16:54 -0800 (PST)
Received: from mail-ot0-x22d.google.com (mail-ot0-x22d.google.com [IPv6:2607:f8b0:4003:c0f::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 9D3B1126579 for <nfsv4@ietf.org>; Tue, 14 Feb 2017 07:16:54 -0800 (PST)
Received: by mail-ot0-x22d.google.com with SMTP id 73so95475719otj.0 for <nfsv4@ietf.org>; Tue, 14 Feb 2017 07:16:54 -0800 (PST)
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=BLmgF8b1weO307FGKjjmfLKKpZ1Bw20yBIWcljyfMUE=; b=aRvPK4IktusSEG2ALvO/sPlf8XKrpQ6wvjXztZxh/F/7f40a5YUkMe2YCHZHzGGj2g VVvlEajKqX4m3EMX+58QCWwZ5QG9MmiDZ4pQj0k/Q6l/qvMKxbXDYAo79R04xSQ/K0jE 3MKcfqiRVnaWqQbwjofD0GMVDqsoitBLtktK42oQDMxLcyekIDaPvz0DpeXFMvhp+QDF lz8Cuswsempeoja8/cvb/XsuhluzWcpU7JnXFs7FU0x2dRVhGxPbIDPyH+3QfkWYvSri 63Qfl9mIEJYNPUNuQ1dRJhEdJh2gbvpf9HaSbDup6HlUDvnsjvh9f5aa0VI5UuGJjeOF T3xw==
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=BLmgF8b1weO307FGKjjmfLKKpZ1Bw20yBIWcljyfMUE=; b=mjFyaKHhF9umIODj4GM8bddAuViHUJ/vZ/vO/o+3b7VLatR21W4OWde7ji7t0iQfYD 1MjAvCkWXe4y9O8fOFiUU+wIAHieeB90REaPDTEJs59Z8Llp8fEwzZsrMDvfEcn6jQUt ++T993jSA1XM9ZhYtC1IPOOuicl8oKctSNILuJvbS3rojuI0QeYBw4uonHxBQ92VB9vw LgBJyltyBrm568j6S+ATzAFskhzElIlanNxcyD+pmQ+eFt8WsBEBKC5tTkSUDPM1AeUw df7gINEaUQg0GbdW8FABx5KfpHBwGVS4HXMHxkr4YOq0otAJZOYY68hYN+0F+NFI1d95 wIdw==
X-Gm-Message-State: AMke39nzHhdFURiTeVLQbJ0mDpsKwQugWB+82elF6n8ad7NuBkCVySRisnqCxCjHXVPdqmSkHjgp0dwBM94ElA==
X-Received: by 10.157.19.93 with SMTP id q29mr18048708otq.60.1487085413934; Tue, 14 Feb 2017 07:16:53 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.137.200 with HTTP; Tue, 14 Feb 2017 07:16:53 -0800 (PST)
In-Reply-To: <MWHPR03MB28936969C47DE5706C68572FC74D0@MWHPR03MB2893.namprd03.prod.outlook.com>
References: <CAFt6Ba=BaG3+MyGGF-=JOaGOzwKTMaudL2Wxzh1d-2bQPBjZZA@mail.gmail.com> <CADaq8jdqqUtUmkJUtTaobfczmdyovH4oViB2Aj67cTVmTz3cew@mail.gmail.com> <20170201150547.GA7561@lst.de> <CADaq8jfZRKLTmuzwq3VyUfCBQk1-fJPNDwHChf3-uqrRqSaGcQ@mail.gmail.com> <MWHPR03MB28936969C47DE5706C68572FC74D0@MWHPR03MB2893.namprd03.prod.outlook.com>
From: David Noveck <davenoveck@gmail.com>
Date: Tue, 14 Feb 2017 10:16:53 -0500
Message-ID: <CADaq8jdk7QJoRieHYi2k755qJU5KE-smMVVSWMM09=mYjo_Rmw@mail.gmail.com>
To: Spencer Shepler <sshepler@microsoft.com>
Content-Type: multipart/alternative; boundary="001a11351ea4d9350905487f0d2d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/hAH8jp0sIC30FIxlCIIyy8K31iI>
Cc: Christoph Hellwig <hch@lst.de>, "nfsv4@ietf.org" <nfsv4@ietf.org>
Subject: Re: [nfsv4] IETF 98 - NFSv4 WG meeting (soliciting agenda items)
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, 14 Feb 2017 15:16:57 -0000

On  2/1/2017, Spencer wrote:
> On the topic of the MISREF, Christoph has responded with the references
that have been published that will suffice to move the RFC forward.

"will suffice" or "should suffice"?

> We are awaiting response from the RFC editor.

Thirteen  days later, the document is still in MISSREF and appears not to
have moved forward
at all.  Maybe something has happened that I'm unaware of but it may be
that you are still
waiting for a response from the RFC editor.  Has there been a response yet,
or at least some sort of an ETA provided?



On Wed, Feb 1, 2017 at 12:02 PM, Spencer Shepler <sshepler@microsoft.com>
wrote:

>
>
> On the topic of the MISREF, Christoph has responded with the references
> that have been published that will suffice to move the RFC forward.  We are
> awaiting response from the RFC editor.
>
>
>
> Spencer
>
>
>
> *From:* nfsv4 [mailto:nfsv4-bounces@ietf.org] *On Behalf Of *David Noveck
> *Sent:* Wednesday, February 1, 2017 8:52 AM
> *To:* Christoph Hellwig <hch@lst.de>
> *Cc:* nfsv4@ietf.org
> *Subject:* Re: [nfsv4] IETF 98 - NFSv4 WG meeting (soliciting agenda
> items)
>
>
>
> >> whether he
> >> is able to be physically present or not.
>
> > I won't make it to Chicago, but I plan to be in Prague in July.
>
>
>
> I hope you'll consider remote participation.  I did this for IETF96 in
> Berlin and it seemed to go OK.  Of course, I had  to get up at some ungodly
> time in the morning but you won't have that problem since the time zone
> issues are reversed (unless you are in Asia in late March).
>
>
>
> > It's in the RFC Editor stage now, and I just had an interaction with
> > them yesterday.
>
>
>
> I saw the MISSREF.  I''m guessing this is the SAM-5 issue.  I went looking
> for it and the result was sobering.  This started in 2004 and it is now in
> the ANSI approval process.  The page said 65% complete,, which might mean
> this is years away.
>
>
>
> It seems like the IETF is headed this way (rough consensus, running code,
> interminable review) which would be a shame.  I'd like to understand why
> things are getting slower and slower and see what can be done to improve
> the process.
>
>
>
> On Wed, Feb 1, 2017 at 10:05 AM, Christoph Hellwig <hch@lst.de> wrote:
>
> On Wed, Feb 01, 2017 at 06:44:07AM -0500, David Noveck wrote:
> > I hope we can hear from Christoph regarding NVMe-related stuff,
>
> I might do another minor update of the NVMe layout, I just need to find
> some time.
>
> > whether he
> > is able to be physically present or not.
>
> I won't make it to Chicago, but I plan to be in Prague in July.
>
> > In addition, I'd like us to her
> > about the progress of the scsi layout draft.  That took eight months to
> go
> > from -00 to working group consensus :-) and over thirteen months after
> that
> > and it is not out yet :-(. I think we have a general problem and need to
> > understand it better before we try to fix it.  Hearing from Christoph
> would
> > help us understand what is going on.
>
> It's in the RFC Editor stage now, and I just had an interaction with
> them yesterday.
>
>
>