Re: [nfsv4] IETF 102 nfsv4 WG meeting go/no-go
spencer shepler <spencer.shepler@gmail.com> Fri, 11 May 2018 22:42 UTC
Return-Path: <spencer.shepler@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 8A8C7129C6D for <nfsv4@ietfa.amsl.com>; Fri, 11 May 2018 15:42:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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] 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 mi0WtpQL03I5 for <nfsv4@ietfa.amsl.com>; Fri, 11 May 2018 15:42:03 -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 9C88712AF83 for <nfsv4@ietf.org>; Fri, 11 May 2018 15:42:03 -0700 (PDT)
Received: by mail-oi0-x230.google.com with SMTP id b130-v6so6034924oif.12 for <nfsv4@ietf.org>; Fri, 11 May 2018 15:42:03 -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=qu6pAYas5EGl7gcr9tzxv9+MuEYYNF3w41XHy5bdu9I=; b=PGS+0Ue11B4jxIHu63p+qNIWmcuth9HK1m+SXlOX57oS2JXXxt14QS0yuJoLRIp/C3 rxGUoa028/45ayb/fQOgPHDK1D1HKuH4b4y1IVXbDfgqyMrK6bM88azgRUMausr0Ve+u ityR1Xozyk3llogBypqyQvo4sHRvCh3VPKGgmMneQOEBXoAwuU9oipVPEGuy6kHrk03I xg5/WoG9aOZ8YGReoqIrmYtcwRKq5o71BiXsQDuTFhrBBk/wckyuzKcBKFT8cVtFyMEE WCO3QLHs94FrwvDl2LjJShZ9zs8uTyHGpz5WY9hPQtHVYLldf8CWRjMA6EXQb0yDuiPs J/JQ==
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=qu6pAYas5EGl7gcr9tzxv9+MuEYYNF3w41XHy5bdu9I=; b=iqhof3Cd4LGZatkK6bDAzMPAQkfOw2yvZjW5EVlRbuhRgKDC9eiEwB/pkHNtWsgDaF c3oOhUI6OPRRXLXy2dGuxK0bJlHyrolIeKrybFsLJ08EplB35Lo1ypU0YQzyDLccu/f6 7sxglOqqyr0Fzv6qO0jbwZ6Jj4NfXSwmsbi7ZmF9jMaK9L2RXxr4cXi8wNbhQF7R7aX4 //poQma44KrTmspMdofBJhgPVB0r8muI21tGN+D46cN0qNUYdcwiCtCb7yxKjrGTlkg0 pIojDHxUYFrR0AU0nlo9K7IBZu/klz7E/K3sPnsqGtdOGzCqD2l7DihzvLC97zKn8OHj x0zQ==
X-Gm-Message-State: ALKqPwe7hljbnr1PXTQ0Tx37yDjDM6a6ecWprpqoDcSTVLpCykgW4Hlo f6EBO6oC1gO5hWLVkXF+b67TV7NlRBgfM7D0EOs=
X-Google-Smtp-Source: AB8JxZp1XZsfq51YQ/TYdd+QoP5LDoHRr2oGMkv6EE81G1pghnU4GIPh6JrXrOEuPq7iv4t0nxdfJdQXQPO8YbVutSg=
X-Received: by 2002:aca:bac2:: with SMTP id k185-v6mr512144oif.269.1526078523021; Fri, 11 May 2018 15:42:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.201.24.222 with HTTP; Fri, 11 May 2018 15:42:02 -0700 (PDT)
In-Reply-To: <CAKKJt-cZiLL-q-tm+h80S_BX85VNzdc+TKB8g9n-yJd5KP9aOA@mail.gmail.com>
References: <89A4F7ED-2658-492C-BDAC-02193C956C33@oracle.com> <CAKKJt-cZiLL-q-tm+h80S_BX85VNzdc+TKB8g9n-yJd5KP9aOA@mail.gmail.com>
From: spencer shepler <spencer.shepler@gmail.com>
Date: Fri, 11 May 2018 15:42:02 -0700
Message-ID: <CAFt6Bam_3Kz4+AwSxxaHY0OUedZd2Xob2KQU3cgPvDPwhbaQXg@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: Chuck Lever <chuck.lever@oracle.com>, NFSv4 <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000439daa056bf5d89b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/fenBONSsmZrZHMRhRF2bC__MODg>
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: Fri, 11 May 2018 22:42:06 -0000
As you will note, I have submitted a meeting request for IETF 102 (Thanks for pushing the discussion this week, Chuck). 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 > >
- [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