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

Tom Haynes <loghyr@gmail.com> Mon, 07 May 2018 15:18 UTC

Return-Path: <loghyr@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 37EA2126CC4 for <nfsv4@ietfa.amsl.com>; Mon, 7 May 2018 08:18:06 -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 p7Y6C_cAKHqu for <nfsv4@ietfa.amsl.com>; Mon, 7 May 2018 08:18:04 -0700 (PDT)
Received: from mail-it0-x234.google.com (mail-it0-x234.google.com [IPv6:2607:f8b0:4001:c0b::234]) (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 001BC126B72 for <nfsv4@ietf.org>; Mon, 7 May 2018 08:18:03 -0700 (PDT)
Received: by mail-it0-x234.google.com with SMTP id q72-v6so1997453itc.0 for <nfsv4@ietf.org>; Mon, 07 May 2018 08:18:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=kg4xdJI25ZKu41QtdkgHC4AUNWJVQ+Dx7QsFMQZogio=; b=js4/nYBtjiwPLTEZEGHbwO29QcdyuDlTVWO5ZtTv2yQT9OoTMS+/mqxgoiwQfT02i5 uEXv3coGXe3rW9hiT0HBMHQfIKNQ2qfxRPM0X/+dMo7qYQlPo9FLSbPAB1707INGeQcy Pb2OPTugF4F/agjhcwXKE33Kc4UH9+o2pjWioJgazUOhYDFa27k0WQZLl/WByStcpxab l89gcrnuk2QA1yXrdZO77+qowEdhDJnB3nI8bQKnxPlryE2UaO15U4RELd4SRSRe0arl q1/VcAX71G3+TXH0YzeYKFTpfoFAB8dXPh2542JaRlZ5yfr0cxgnfbE6H3bUcWBqi7IN K9eA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=kg4xdJI25ZKu41QtdkgHC4AUNWJVQ+Dx7QsFMQZogio=; b=O5LRyiZ52TX25opklTCRQ3ICsaA4vHq65e2ZW3etNw9YTZPVsYNjBfBR92zNKUL2jn F0Igdsormx6wJolLtxqQ2w2hWbn65LZhl5grBn9F4RQo83MlXMfeirKHWFIZbJXmcNMD 5ZiS19Hs5/s6tO+JT5VqnapMLD9sPovVX/sjOY/ml7tKTYpgNBCHPte/mP6HOZ3PaNOb xHhAQ8OpSyVN4d1GTOZsP+5DeqEySoDCF9vutcwXXk6cyWVJf8wbaRhNwB3NYUvO9BUF ptO47TwFChJutoFuf91QW8Zc0mcR6PwfEthGFWQgXmLI3un2ZQywrXmVCSX9KwYat2uo PlRg==
X-Gm-Message-State: ALQs6tDeyitjEOsy/kWmKs6qGCVKaE5Xr/wuJ6OGE3NT4rOTMFsmtS5z HVtGjKA5v2+yvf0fiL9jswk=
X-Google-Smtp-Source: AB8JxZo5p96DLCOTQ49LuIeXydYfErGT31kGxQYnfJFGzSV8WDMtEajEnZXS9dzE98zZDcr9ThOaLg==
X-Received: by 2002:a17:902:265:: with SMTP id 92-v6mr37291082plc.368.1525706283305; Mon, 07 May 2018 08:18:03 -0700 (PDT)
Received: from kinslayer.corp.primarydata.com (63-157-6-18.dia.static.qwest.net. [63.157.6.18]) by smtp.gmail.com with ESMTPSA id k63sm63529206pfk.90.2018.05.07.08.18.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 07 May 2018 08:18:02 -0700 (PDT)
From: Tom Haynes <loghyr@gmail.com>
Message-Id: <C65BBF0E-80B6-4896-8604-08DA177FDE8E@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9A37DD85-FB42-48C2-9B1E-4AD3CA624998"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Mon, 07 May 2018 08:18:01 -0700
In-Reply-To: <89A4F7ED-2658-492C-BDAC-02193C956C33@oracle.com>
Cc: NFSv4 <nfsv4@ietf.org>
To: Chuck Lever <chuck.lever@oracle.com>
References: <89A4F7ED-2658-492C-BDAC-02193C956C33@oracle.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/ZjpdUcQxulLoMlOohFfwvuI01Z4>
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, 07 May 2018 15:18:06 -0000


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

draft-haynes-nfsv4-delstid-00 <https://datatracker.ietf.org/doc/draft-haynes-nfsv4-delstid/>


> - 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