Re: [nfsv4] Is it time for a -00 for the IETF96 wg meeting draft agenda?

Chuck Lever <chuck.lever@oracle.com> Thu, 16 June 2016 15:09 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 0E01112D88E for <nfsv4@ietfa.amsl.com>; Thu, 16 Jun 2016 08:09:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.647
X-Spam-Level:
X-Spam-Status: No, score=-5.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 2VuomH9w1oZf for <nfsv4@ietfa.amsl.com>; Thu, 16 Jun 2016 08:09:41 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) (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 814E712D7A4 for <nfsv4@ietf.org>; Thu, 16 Jun 2016 08:09:40 -0700 (PDT)
Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u5GF9YIx030101 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 16 Jun 2016 15:09:34 GMT
Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by aserv0021.oracle.com (8.13.8/8.13.8) with ESMTP id u5GF9XR0029275 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 16 Jun 2016 15:09:34 GMT
Received: from abhmp0005.oracle.com (abhmp0005.oracle.com [141.146.116.11]) by userv0122.oracle.com (8.14.4/8.14.4) with ESMTP id u5GF9X3G027857; Thu, 16 Jun 2016 15:09:33 GMT
Received: from [10.10.10.167] (/108.204.28.189) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 16 Jun 2016 08:09:33 -0700
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Chuck Lever <chuck.lever@oracle.com>
In-Reply-To: <CADaq8jeq8EN2GgUPcoEvB+Yq=jrbLxAm5+DEZiVFWkG5MFdu6A@mail.gmail.com>
Date: Thu, 16 Jun 2016 11:09:30 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5F6671E1-0614-4971-8E4C-6D0061372DC7@oracle.com>
References: <CADaq8jeq8EN2GgUPcoEvB+Yq=jrbLxAm5+DEZiVFWkG5MFdu6A@mail.gmail.com>
To: David Noveck <davenoveck@gmail.com>
X-Mailer: Apple Mail (2.3124)
X-Source-IP: aserv0021.oracle.com [141.146.126.233]
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/oW9WkEtlIBbR7CMpwlLPvG-SHS0>
Cc: "nfsv4@ietf.org" <nfsv4@ietf.org>
Subject: Re: [nfsv4] Is it time for a -00 for the IETF96 wg meeting draft agenda?
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 16 Jun 2016 15:09:42 -0000

> On Jun 15, 2016, at 9:27 AM, David Noveck <davenoveck@gmail.com> wrote:
> 
> First a warning.  I'm going to be discussing schedules.
> 
> Now for people who are have not hit delete and are still reading, my answer to the above question is "Yes, we need it soon"
> 
> Let me provide some background here:
> 	• Spencer originally wanted to get a start on a draft agenda by 5/20.  While people did provide information about things they might talk about, there were not specific talk proposals with titles and durations that Spencer could use as the basis for an early draft agenda .  In any case, that target date went by nearly four weeks ago.
> 	• The critical target date is 7/7 by which time an actual agenda has to be provided.  Given the discussion that has already gone on regarding things that might talked about (by me, Chuck, and Christoph) it is pretty clear that some sort of draft can be provided by that date, given that we have the option, since it is a "draft", of making needed changes later.
> 	• If we want an agenda that truly reflects the working group's needs, we need to have a draft that we can discuss and possibly update before the official draft agenda is ready for submission.  Given that the target date is about three weeks off, I think we need to have that -00 for the draft within the next week.
> I'm going to propose a couple of talks below.  I think it makes sense for anyone with a talk proposal to add theirs to the list.  If those fit in 150 minutes, we have our -00.  If not, we may need some working group discussion to get to a -00.  While I expect the working group to try to accommodate late-arriving proposals, I'd hope that people would get their proposals in as soon as possible. 
> 
> Anyway, my proposed talks would be:
> 	• A discussion about the NFSv4 extension stuff, NFSv4 Extension Paradigm: What Next?.  The documents to be discussed would be draft-ietf-nfsv4-versioning-04 and draft-dnoveck-nfsv4-extension-00 (TBD).  The goal was to resolve current disagreements about whether we should go on as we have, with the existing standards-track document, convert the existing working-group document to be informational, or to split the document into standards-track and informational documents.  I'd allocate 30 minutes for this.  
> 	• A presentation about currently proposed extensions to RPC-over-RDMA Version Two, Updating RPC-over-RDMA: Next steps. The documents to be discussed would be draft-dnoveck-nfsv4-rpcrdma-xcharext-00, draft-dnoveck-nfsv4-rpcrdma-rtissues-00, and draft-dnoveck-nfsv4-rpcrdma-rtrext-00.  The goal here would be to present and discuss current extension proposals, see what the working group response is, and decide where we want to go next in this area.  I'd allocate 30 minutes for this.

As an introduction to the second talk above, I can give
an introduction to rpcrdma-version-two in about 10
minutes.

I can also give a presentation soliciting input and
answering questions about the current status and end-game
for rfc5666bis, rpcrdma-bidirection, and rfc5667bis.
That would take about 10 minutes.


--
Chuck Lever