Re: [nfsv4] IETF 102 nfsv4 WG meeting go/no-go

David Noveck <davenoveck@gmail.com> Tue, 08 May 2018 11:01 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 837D212D88D for <nfsv4@ietfa.amsl.com>; Tue, 8 May 2018 04:01:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 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, 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 lF_LrTlpehOM for <nfsv4@ietfa.amsl.com>; Tue, 8 May 2018 04:01:17 -0700 (PDT)
Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (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 C620E12D88A for <nfsv4@ietf.org>; Tue, 8 May 2018 04:01:16 -0700 (PDT)
Received: by mail-oi0-x230.google.com with SMTP id t27-v6so27928270oij.9 for <nfsv4@ietf.org>; Tue, 08 May 2018 04:01:16 -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=+mYa5lSC2sBJ+JvyDxR/Ktho7BEk+rTPV3tKA+ZJVD8=; b=Ll/8pUhZ9inZtTAHptkFSLwrzDePUwxwxf2XdxspzyGuCZMpznamRl4A86Lx6rsVy4 JkoTKuVVOE1lWQUEnZ1qcdlESY5kv3IU0owzCUV9x2xYiuz0sFb5wKXggXwUymR5qd5Y 4Xz/5xQLLf9TehVSuPLP4moBtfCPHKTHFxKNXC8UmUP5g1l+s0TrEeQIYle4tlvfe6eX 10rqanmtFHqKwTfZc9OfGhT3pr6dWG4bqHbPeejMkRoTk4OzGe11s1dbgh7VDBH1ZVIN VxMED5ejE8uRfbceMNgmawGKdapCHIfAqnfqMJ9WilTXl+WoMYvObmhP4yvQ/PceFQAA olvA==
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=+mYa5lSC2sBJ+JvyDxR/Ktho7BEk+rTPV3tKA+ZJVD8=; b=mY6+qJtyP7CWCm1sHrPBXSEnAEMs8HDyO9/VjzjgqQMdNUHrh5pXZFIYAvziYP71eC fm7Bp8Xf00aaxX+Z6XwakOlCZQEbkU7FOZLiobROk6MfxKgHJ84siWKlRYsFv15mSqqI Bp5/x7rO5qyEkbLPfT92bGbuY/ZfQgpmJTUkY92UaO2EzeJfJvkHf/2sjOg+JTWMr6IM 9Ghb6M4oNP9cIZjegXfsVsj1jDo0pShaMKLZJw7JUZ/kJkavV2oUYdMco1jHNrDOMk3G 8EASzsLVhmo7xrtBzFhr5gjvkFreRW2N5ZVzzsm/KZipemnhVZPFNmk9w8WE19v0I2Vq osPw==
X-Gm-Message-State: ALQs6tDhWtwgBsxkGc16SBi+twNuAZqgs6rr+gnWqLWDgxH/JluFKamd 33zVxzANWvPjtU+rj2zySUzQriEFvAjGQaBYXJ0=
X-Google-Smtp-Source: AB8JxZq9tLkchTu1jXwTxu/Qjm7Y6sN82+Qdu81Wo/UN7HoCDviG1+frzqumL9DBk4vHtcvkWAlt5NIbFK5IQOO5RG4=
X-Received: by 2002:aca:efd5:: with SMTP id n204-v6mr13995320oih.218.1525777275851; Tue, 08 May 2018 04:01:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.201.55.233 with HTTP; Tue, 8 May 2018 04:01:15 -0700 (PDT)
In-Reply-To: <89A4F7ED-2658-492C-BDAC-02193C956C33@oracle.com>
References: <89A4F7ED-2658-492C-BDAC-02193C956C33@oracle.com>
From: David Noveck <davenoveck@gmail.com>
Date: Tue, 8 May 2018 07:01:15 -0400
Message-ID: <CADaq8jf8sfQhA6TX=WKFm7pwJdhR+F05T9GSzW_euMD129azoQ@mail.gmail.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: NFSv4 <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000889a23056bafb463"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/zAwz5jItovtaMBlJUoGMRS8pzug>
Subject: Re: [nfsv4] IETF 102 nfsv4 WG meeting go/no-go
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: Tue, 08 May 2018 11:01:19 -0000

 > https://datatracker.ietf.org/meeting/important-dates/

> Says the cut-off for requesting a meeting room is June 1, 2018.

Thanks for bringing this to our attention.

> I can think of a few agenda topics that are relevant at this time:

> - Tom/Trond have some virtualization-related extensions and other
protocol fixups

Agree that we should discuss this work.  I owe Tom a review of his document
and want that to be out at least a month before the meeting.

> - I can give a backgrounder on the Integrity Measurement work I'm doing

That would be good.  Given that document plans for this have changed
recently,
it will be good to prepare the working group for what is probably coming.

> - Dave and I have the mv0 and mv1 trunking documents

I also have draft-ietf-nfsv4-migration-issues which has a milestone date of
June
2018 for WGLC.   -15, which I expect to be the last revision, will be out
in the next
few weeks so WGLC is possible by 6/30, but, realistically, we have to
prepared to
discuss this at IETF102.

After -15 is out, I will send mail to the Spencer's regarding schedule
expectations.
I will copy the working group list to give others the opportnity to comment
about
the realism (or otherwise) of my expectations.

- Any other 2018 milestones, such as the expired pNFS SCSI NVMe layout I-D

This seems to me the only 2018 milestone that cannot be accommodated by a
relatively minor adjustment.  However, given that we are meeting in July
2018,
I think we need to look more than five months ahead.

Perhaps we need to review our milestones in general and discuss the
potential
need for adjustments.

- RPC/RDMA credits: the road ahead

Good topic.

Unless AI has made some enormous strides, there will be no self-driving
cars on this road :-)

> That's not an exhaustive list, but it seems like critical mass already.

It's enough for a 150-minute session.

> Any other thoughts?

Given that this will be in the eastern time zone, remote participation
should
be relatively easy.  So people should not have to wait for travel appoval
before deciding to have this meeting.

> Can we set a go/no-go decision date, say Friday May 18th?

I don't see why not.

On Mon, May 7, 2018 at 11:12 AM, Chuck Lever <chuck.lever@oracle.com> wrote:

> https://datatracker.ietf.org/meeting/important-dates/
>
> Says the cut-off for requesting a meeting room is June 1, 2018.
>
> I can think of a few agenda topics that are relevant at this time:
>
> - Tom/Trond have some virtualization-related extensions and other protocol
> fixups
> - I can give a backgrounder on the Integrity Measurement work I'm doing
> - Dave and I have the mv0 and mv1 trunking documents
> - Any other 2018 milestones, such as the expired pNFS SCSI NVMe layout I-D
> - RPC/RDMA credits: the road ahead
>
> That's not an exhaustive list, but it seems like critical mass already.
> Any other thoughts?
>
> Can we set a go/no-go decision date, say Friday May 18th?
>
>
> --
> Chuck Lever
>
>
>
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4
>