Re: [nfsv4] IETF 102 nfsv4 WG meeting go/no-go
David Noveck <davenoveck@gmail.com> Mon, 21 May 2018 16:34 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 C34F112EA24 for <nfsv4@ietfa.amsl.com>; Mon, 21 May 2018 09:34:55 -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 QH5WN1UTEkHY for <nfsv4@ietfa.amsl.com>; Mon, 21 May 2018 09:34:53 -0700 (PDT)
Received: from mail-ot0-x235.google.com (mail-ot0-x235.google.com [IPv6:2607:f8b0:4003:c0f::235]) (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 0C7B512E89F for <nfsv4@ietf.org>; Mon, 21 May 2018 09:34:53 -0700 (PDT)
Received: by mail-ot0-x235.google.com with SMTP id l12-v6so17528057oth.6 for <nfsv4@ietf.org>; Mon, 21 May 2018 09:34:53 -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=zdliEX3pcsoh8tRkRcNqhj+hH0nA/judDOA7H70zWTM=; b=rzPZREXPSN5NQ1QGG3D7pyGNZfgioVA8iDhI6NyTHG9ViRTSlxJ2NMvLe8WHssJ2us l2os6SYgGa0Ncm2IDbT894fPqSGN+uyZmbabWF9EDIauhorICQZwP9eN2w+sZ2pUgrH8 KX/h6w54BsCCOWpPodwUDC5l/mkqqF6P9X0eAQFAnUn/imgWOE1DH79bihVb7Ca6pD9f Mbz5Uy3go3DlKVfrOZsm2JsglBQI13/4DEkNiAJi+55goM+0nOvRlP1vOVTlWUlWHjVX 99bwArxjA+nxU4MLb+mrfYX0E/4n+sgIgsAgOAHJa0/4zTn7Ea9JJ2WGkIzH1KqeVbnf m+PQ==
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=zdliEX3pcsoh8tRkRcNqhj+hH0nA/judDOA7H70zWTM=; b=JWF50HGfVAcDhyESHbtjBK0ewuXPwG9zdz2TwTAl6tyP+0l+aIGzf9+FNFr+VDSWqr ZXfQ/sTKdMhWEviG/uA5E2T+/D9rMPzer5XREiXUHeCmRRB5h+yZw+3wk9xIrxA7/m5t KwydFWsnQoIQyhqJ4CUJc8D5YbCN9LPQVgSn3Y0m5PzbJThtdivXx2MbgjlUBYxJIDGX Jp2kWQlIG6SUeQPkeHitiaKe3917jU6mHBPrzol3E4cZEkxZvLUCfn9lhYN34zj5RhxW DTbGzBhU4iO+ZXx4Ia6auT3w2zOvQZZFKojfJDTTNhsZ/o24ClHCmaxdK91zwUEj4GJl rfxA==
X-Gm-Message-State: ALKqPwc5zgioopM2b7woC/asaxme2DBeBdEXzzSLxwjzjmakYmv0YI7V I/iR/RYXQh0lsd/yxljm+I0NvL5cjDRWEdUObIA=
X-Google-Smtp-Source: AB8JxZoWonNApBYIP24SqAX4iqBkLAbbFGkSyy1UNEWaGEh1KzrMmRisdO5BhXt3bsa3PrwsyaTiP/aKT2QNvPjk2vA=
X-Received: by 2002:a9d:422a:: with SMTP id q42-v6mr14859988ote.42.1526920492185; Mon, 21 May 2018 09:34:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.201.55.233 with HTTP; Mon, 21 May 2018 09:34:51 -0700 (PDT)
In-Reply-To: <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> <A048F25C-0F85-4DCF-AABA-7578919B761B@oracle.com>
From: David Noveck <davenoveck@gmail.com>
Date: Mon, 21 May 2018 12:34:51 -0400
Message-ID: <CADaq8jfAz=-GPxQia7j-0snFr-zaTaqD=pjhdScpiAfz8DbC0w@mail.gmail.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: spencer shepler <spencer.shepler@gmail.com>, NFSv4 <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000897cb0056cb9e16b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/cdSB-0c7l7LBCi-_J4qLFLdHRS0>
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 16:35:04 -0000
> Go/No-go went by us on Friday. I had thought of Spencer's message as the as the Go/No-go (in this case Go). My interpretation was that he requested a meeting based on his judgment that there was a general feeling that we should meet. > I haven't heard any objections to meeting, Neither did Spencer. > and there does seem to be a substantive list of topics > we could discuss. We now have to turn that into a list of topics we will discuss and divvy up the meeting time. > We appear to have enough energy behind meeting > in Montreal in July. Yes. Now it's just a question of getting money, reservations, and plane tickets, and getting presentations ready. On Mon, May 21, 2018 at 11:46 AM, Chuck Lever <chuck.lever@oracle.com> wrote: > > > > 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 > > > > _______________________________________________ > nfsv4 mailing list > nfsv4@ietf.org > https://www.ietf.org/mailman/listinfo/nfsv4 >
- [nfsv4] IETF 102 nfsv4 WG meeting go/no-go Chuck Lever
- Re: [nfsv4] IETF 102 nfsv4 WG meeting go/no-go Tom Haynes
- Re: [nfsv4] IETF 102 nfsv4 WG meeting go/no-go David Noveck
- Re: [nfsv4] IETF 102 nfsv4 WG meeting go/no-go Spencer Dawkins at IETF
- Re: [nfsv4] IETF 102 nfsv4 WG meeting go/no-go spencer shepler
- Re: [nfsv4] IETF 102 nfsv4 WG meeting go/no-go J. Bruce Fields
- Re: [nfsv4] IETF 102 nfsv4 WG meeting go/no-go Trond Myklebust
- Re: [nfsv4] IETF 102 nfsv4 WG meeting go/no-go Dr James Bruce Fields
- Re: [nfsv4] IETF 102 nfsv4 WG meeting go/no-go Thomas Haynes
- Re: [nfsv4] IETF 102 nfsv4 WG meeting go/no-go J. Bruce Fields
- Re: [nfsv4] IETF 102 nfsv4 WG meeting go/no-go Chuck Lever
- Re: [nfsv4] IETF 102 nfsv4 WG meeting go/no-go David Noveck
- Re: [nfsv4] IETF 102 nfsv4 WG meeting go/no-go spencer shepler
- Re: [nfsv4] IETF 102 nfsv4 WG meeting go/no-go Chuck Lever
- Re: [nfsv4] IETF 102 nfsv4 WG meeting go/no-go David Noveck
- Re: [nfsv4] IETF 102 nfsv4 WG meeting go/no-go Tom Haynes