IETF Logo Mail Archive

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

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Wed, 09 May 2018 19:37 UTC

Return-Path: <spencerdawkins.ietf@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 1C4041270AC for <nfsv4@ietfa.amsl.com>; Wed, 9 May 2018 12:37:15 -0700 (PDT)
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 lgOAkD68Y8lV for <nfsv4@ietfa.amsl.com>; Wed, 9 May 2018 12:37:13 -0700 (PDT)
Received: from mail-yb0-x231.google.com (mail-yb0-x231.google.com [IPv6:2607:f8b0:4002:c09::231]) (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 10C14120724 for <nfsv4@ietf.org>; Wed, 9 May 2018 12:37:13 -0700 (PDT)
Received: by mail-yb0-x231.google.com with SMTP id o14-v6so12749080ybq.3 for <nfsv4@ietf.org>; Wed, 09 May 2018 12:37:13 -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=tyUBlfoyB8qhprOaN+UkaRSC2wjZXr22dN79HyVdYwY=; b=kZY2been9eFt9VYwd93a1O0Onhi9YDFBqITguQfibzbhLBx+WK4cQ1UpvND51oPDo+ 2FM0gr71TsdK7lOWLLYTiHApX2VYLVpo//2/E1iQcOMW+WtGDXHKfEli9y5N+II4jIzD 6Ud7CUNt9ZQL2D3+6+E5DCaug/3hNwTdA0kOeB593ROaurgTFdJdsqUc5UGmgZLOFxJK k8rQO2GT9NwZjHLwgQ8j7b/JuQpOYZ1Gq6oIUoeH/R8YzhFtHpAs8H/bLbJpTwqauux5 KUyiNU8SCMQ8GN3M28gVDa22wkFsDv0sWK7OgNo/uVkf7/fvFJl/cIcwkNrSUJ7GQj4/ /9Qw==
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=tyUBlfoyB8qhprOaN+UkaRSC2wjZXr22dN79HyVdYwY=; b=S3Zfs/ooLEs+BJPVQwFfHQDdAZbCX+f/nQVz0K/Z/XcFsiGXda8UGFiL+i4s0PMdEt AFoUIOnVlx9S30VbwAdnMDSz46i0gJhDhQwYv8krxT0+JcWu9YpWEzMQxdA94NaLjba5 CfUdZ6f8BbuVdkvzcA8jKlG3NdGxc06dgCl/XbY9C2tTP9eYV5thX6f/Ntcw0wMi6qpU 6UrvEM8ZnD6gXhz2S1LzFitBFTXwBI2zcDoicbqmES/eKnA2YJTSumzqNxzIFBABiPjx 16R9sVrpC+a7Oq/vIT/0qGXiKDt0lN9CWQ2iUilWDTTT6ntaHSkNxyxrtIeiiyqcUnq9 ac2A==
X-Gm-Message-State: ALQs6tCT0PK2TCSdlpd/NQdGEDnAkzKTwYe02BAvaedaohWdzSbz9XUT DJhOwU99Z3fHWVej3O/7CL1zWstLWiuzr/NVc4o=
X-Google-Smtp-Source: AB8JxZppTGLY0eg4FENTPBMnMHXEthIAhQXrqSpOl6RGSkk37Jl9ff45stlxOI0jlGWH1NSDc8gH3Lga7F3yiqh/VbE=
X-Received: by 2002:a25:b214:: with SMTP id i20-v6mr28269674ybj.471.1525894632074; Wed, 09 May 2018 12:37:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a25:d014:0:0:0:0:0 with HTTP; Wed, 9 May 2018 12:37:11 -0700 (PDT)
In-Reply-To: <89A4F7ED-2658-492C-BDAC-02193C956C33@oracle.com>
References: <89A4F7ED-2658-492C-BDAC-02193C956C33@oracle.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 09 May 2018 14:37:11 -0500
Message-ID: <CAKKJt-cZiLL-q-tm+h80S_BX85VNzdc+TKB8g9n-yJd5KP9aOA@mail.gmail.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: NFSv4 <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008273a7056bcb07fd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/E9ezkDTx947ZT1RBm580Br8a60U>
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: Wed, 09 May 2018 19:37:15 -0000

Without expressing an opinion about when WGs meet and do not meet (that's a
WG decision), it might be worth me mentioning that it's extremely unlikely
I would object to a virtual interim meeting for any of my WGs, and the TSV
ADs have a dedicated WebEx bridge ... so if you need to talk, but not badly
enough to meet face to face, you still have options.

Do the right thing, of course!

Thanks,

Spencer (D)

On Mon, May 7, 2018 at 10: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
>

v2.23.0 | Report a Bug | By Email