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

Chuck Lever <chuck.lever@oracle.com> Mon, 21 May 2018 15:46 UTC

Return-Path: <chuck.lever@oracle.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 95BC712E9DA for <nfsv4@ietfa.amsl.com>; Mon, 21 May 2018 08:46:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level:
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oracle.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 wVlgs-wsAwCm for <nfsv4@ietfa.amsl.com>; Mon, 21 May 2018 08:46:48 -0700 (PDT)
Received: from aserp2130.oracle.com (aserp2130.oracle.com [141.146.126.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5528512E9D9 for <nfsv4@ietf.org>; Mon, 21 May 2018 08:46:48 -0700 (PDT)
Received: from pps.filterd (aserp2130.oracle.com [127.0.0.1]) by aserp2130.oracle.com (8.16.0.22/8.16.0.22) with SMTP id w4LFewNj071088; Mon, 21 May 2018 15:46:46 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=content-type : mime-version : subject : from : in-reply-to : date : cc : content-transfer-encoding : message-id : references : to; s=corp-2017-10-26; bh=WFbWpnj2wuzgH8oY/u1Q4d6/Jl2LrZaKVk7e3/bHJZs=; b=twWjS1qOOkGIn6ap3ZB+tVVK9P4UEGEGz6PavpuqH3hJPZYUUd7bIKO/2XDxj7mNiNI7 aHqKtVIV4UmRdYbJuDy5J/kxO6bFoHIm6n5RkMdulCF1luFYcTJScDOOgG7PYv76RgPc fHeWNyJpP+ZQAhdrqbP4hSCNV4nk5ZRpMCtS4RQWS3jruCAfM8yhWXzFWdlkG6i6GHc1 qIRSCq4PzB+8oqrlVaNhUQ5DOSRKTtghGtsxLNwa80WehjSF5Fgr5pwLe+2w0b1s6hv3 O0Bn+ZvgdZgR8nl/uYUOLUPVXWkOq0IMxP1+xSIUx6rpQsKx6d+/vrbyZHxJ7uNpt6mz PA==
Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by aserp2130.oracle.com with ESMTP id 2j29eyd37b-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 21 May 2018 15:46:46 +0000
Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by aserv0021.oracle.com (8.14.4/8.14.4) with ESMTP id w4LFkj9k021648 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 21 May 2018 15:46:45 GMT
Received: from abhmp0014.oracle.com (abhmp0014.oracle.com [141.146.116.20]) by aserv0122.oracle.com (8.14.4/8.14.4) with ESMTP id w4LFkjT1007874; Mon, 21 May 2018 15:46:45 GMT
Received: from [10.126.150.87] (/148.87.23.44) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 21 May 2018 08:46:45 -0700
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
From: Chuck Lever <chuck.lever@oracle.com>
In-Reply-To: <CAFt6Bam_3Kz4+AwSxxaHY0OUedZd2Xob2KQU3cgPvDPwhbaQXg@mail.gmail.com>
Date: Mon, 21 May 2018 08:46:44 -0700
Cc: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, NFSv4 <nfsv4@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <A048F25C-0F85-4DCF-AABA-7578919B761B@oracle.com>
References: <89A4F7ED-2658-492C-BDAC-02193C956C33@oracle.com> <CAKKJt-cZiLL-q-tm+h80S_BX85VNzdc+TKB8g9n-yJd5KP9aOA@mail.gmail.com> <CAFt6Bam_3Kz4+AwSxxaHY0OUedZd2Xob2KQU3cgPvDPwhbaQXg@mail.gmail.com>
To: spencer shepler <spencer.shepler@gmail.com>
X-Mailer: Apple Mail (2.3445.6.18)
X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=8900 signatures=668700
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1805210188
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/OOkOgWo5GqlLvxbf6GCpWC2GXLc>
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: Mon, 21 May 2018 15:46:57 -0000


> On May 11, 2018, at 3:42 PM, spencer shepler <spencer.shepler@gmail.com> wrote:
> 
> 
> As you will note, I have submitted a meeting request for IETF 102 (Thanks for pushing the discussion this week, Chuck).

Thank you for requesting the room!

Go/No-go went by us on Friday. I haven't heard any objections to
meeting, and there does seem to be a substantive list of topics
we could discuss. We appear to have enough energy behind meeting
in Montreal in July.


> I wanted to get the meeting request in given the positive outlook and for the fact that hotel registration deadlines were approaching quickly.
> 
> I can cancel the meeting request if there is a lack of interest but we should make that decision soon (Monday or Tuesday at the latest).
> 
> Spencer
> 
> 
> On Wed, May 9, 2018 at 12:37 PM, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> wrote:
> 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
> 
> 
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4
> 
> 

--
Chuck Lever