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

David Noveck <davenoveck@gmail.com> Wed, 01 February 2017 16:51 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 4486F129485 for <nfsv4@ietfa.amsl.com>; Wed, 1 Feb 2017 08:51:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, URIBL_BLOCKED=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 BtcedSKBlON5 for <nfsv4@ietfa.amsl.com>; Wed, 1 Feb 2017 08:51:41 -0800 (PST)
Received: from mail-ot0-x22a.google.com (mail-ot0-x22a.google.com [IPv6:2607:f8b0:4003:c0f::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 C38B3128B37 for <nfsv4@ietf.org>; Wed, 1 Feb 2017 08:51:41 -0800 (PST)
Received: by mail-ot0-x22a.google.com with SMTP id 73so294713803otj.0 for <nfsv4@ietf.org>; Wed, 01 Feb 2017 08:51:41 -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=YlACKKJMULzPTIioZ3Axc1WLASWC1Q3ZMEkfzjfh8pU=; b=e9MWskU/KtNJedq/u5PRvs7MvIYk9yAfV/2RB5A+YGY/fUcxiD1ONqrTOGPlQRWgbX Z9I/awWLSg4ENOzPpUvOLgV/zu/Wh0Cn2TgUmT3NdcPcdtKeJPa7VvmRenns8wXsmR5T bt9ANi2IEN6z6QSDUNcnSyE82ztoLvjgu3e6EWVNv5cGEeLVuwox7yp6CYvD1LmtoTYQ eEzMs1W4I/dUhlpnr/Q1ofkWfOXdxnR3vEhQ/LZ10ym5E+PXGPG713NyF49kOMqDPFh6 DAxEoY5RNhaIhBqzC2KhyWM63l5r02qA34dm5+sRL9WDvjlC61Y9mU2QPy0FL9n9/spH jDaQ==
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=YlACKKJMULzPTIioZ3Axc1WLASWC1Q3ZMEkfzjfh8pU=; b=kGStsMR3wnYG4g+F96g5h7+NC5iZBL6rQG190t8/sjC8XzKmOBGRpcWhmxM16IteiY FuZ6Aia8diPwTbGsFzY2Iulv/9zoLrFuzgCFYL0Xew8s+iaq+f98ijrmL7bfSr05i/HY avewbjcnYgPNJ3IWm8rPz2uVdxCCo0HuJq1BNS6kvPOIwq97++hDroOLOuGSs3VEBnvR FGpNXJWSl3n0ibIXohWAM+5KG7XKMbUD+d4sgzkrEZzk63CwloSQ+mPSwBvbnUjs5ZIz BWY6WM1xJnMHAWmdX3pHutTqbm/lCOWYJvddtBFw1Cqe/Urr5GOeeNTm9PWO4lN8erzp v0Lg==
X-Gm-Message-State: AIkVDXLekdAjYiYO2rAtt3l7+0Q/Jry9GZ8hSUBsic4/DKwWlUj+mSZNnl2nZut6hNMm2Zm6eIP3cbz86zTpSg==
X-Received: by 10.157.29.182 with SMTP id y51mr1671325otd.256.1485967901092; Wed, 01 Feb 2017 08:51:41 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.137.200 with HTTP; Wed, 1 Feb 2017 08:51:40 -0800 (PST)
In-Reply-To: <20170201150547.GA7561@lst.de>
References: <CAFt6Ba=BaG3+MyGGF-=JOaGOzwKTMaudL2Wxzh1d-2bQPBjZZA@mail.gmail.com> <CADaq8jdqqUtUmkJUtTaobfczmdyovH4oViB2Aj67cTVmTz3cew@mail.gmail.com> <20170201150547.GA7561@lst.de>
From: David Noveck <davenoveck@gmail.com>
Date: Wed, 01 Feb 2017 11:51:40 -0500
Message-ID: <CADaq8jfZRKLTmuzwq3VyUfCBQk1-fJPNDwHChf3-uqrRqSaGcQ@mail.gmail.com>
To: Christoph Hellwig <hch@lst.de>
Content-Type: multipart/alternative; boundary="001a1141fb8ae4710205477adcee"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/oP47-vcUk-lKYJVcivSbVX4plBw>
Cc: "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: Wed, 01 Feb 2017 16:51:43 -0000

>> 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.
>