Re: [nfsv4] Session Dealing with Current WG agenda at IETF 107

Chuck Lever <chuck.lever@oracle.com> Wed, 18 December 2019 18:48 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 96AF0120A77 for <nfsv4@ietfa.amsl.com>; Wed, 18 Dec 2019 10:48:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] 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 RdkR6SZAd2OF for <nfsv4@ietfa.amsl.com>; Wed, 18 Dec 2019 10:48:12 -0800 (PST)
Received: from aserp2120.oracle.com (aserp2120.oracle.com [141.146.126.78]) (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 D1387120A54 for <nfsv4@ietf.org>; Wed, 18 Dec 2019 10:48:12 -0800 (PST)
Received: from pps.filterd (aserp2120.oracle.com [127.0.0.1]) by aserp2120.oracle.com (8.16.0.27/8.16.0.27) with SMTP id xBIIiQlY082594 for <nfsv4@ietf.org>; Wed, 18 Dec 2019 18:48:11 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=from : content-type : content-transfer-encoding : mime-version : subject : date : references : to : in-reply-to : message-id; s=corp-2019-08-05; bh=W5kMiHd7A0pWogEdCs9zoU1EgVmVVPcKadV01WFH3cU=; b=Z3zCipV4L+9ahstsiPKho0qSlyTmO9SpU5Bfq+jH9G0sVhD7HUf3gMvTcSNpIvEUp2f4 cCVMSgi/kIqDzgM+XJfj63NYg9LLsv4Z9DeOtj+3kp7FtlH8LOS4VkmEGBAI0rDGulYv f0Yca7irWcKO9O4k4jc7JByC7ZAueuaD+L0hWQaIxOgohPC4gKzDwsqyEo/zSTt65qYo mSejHyeoKytoyPLaz+Ey1dh7br/K4bgKf3AmP2kSep0/38uX7AfOeiPuq3Ie/TOICIcT WrRQSFLNkLyfCvws71CUnXs9BOl362aH7eoinWBAuCsW0Zw8qErwSLd9cAzCiZq6gGlI Gw==
Received: from userp3020.oracle.com (userp3020.oracle.com [156.151.31.79]) by aserp2120.oracle.com with ESMTP id 2wvqpqfgx6-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for <nfsv4@ietf.org>; Wed, 18 Dec 2019 18:48:10 +0000
Received: from pps.filterd (userp3020.oracle.com [127.0.0.1]) by userp3020.oracle.com (8.16.0.27/8.16.0.27) with SMTP id xBIIhuHc022011 for <nfsv4@ietf.org>; Wed, 18 Dec 2019 18:48:10 GMT
Received: from userv0121.oracle.com (userv0121.oracle.com [156.151.31.72]) by userp3020.oracle.com with ESMTP id 2wyp083kv9-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for <nfsv4@ietf.org>; Wed, 18 Dec 2019 18:48:09 +0000
Received: from abhmp0001.oracle.com (abhmp0001.oracle.com [141.146.116.7]) by userv0121.oracle.com (8.14.4/8.13.8) with ESMTP id xBIIm9bM032354 for <nfsv4@ietf.org>; Wed, 18 Dec 2019 18:48:09 GMT
Received: from dhcp-10-76-202-105.usdhcp.oraclecorp.com (/10.76.202.105) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 18 Dec 2019 10:48:09 -0800
From: Chuck Lever <chuck.lever@oracle.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Wed, 18 Dec 2019 13:48:55 -0500
References: <CADaq8jdsEMc9ov5UgiL2beFmJznDxgJcmc8QXJzJ8o9zSAgs7A@mail.gmail.com>
To: NFSv4 <nfsv4@ietf.org>
In-Reply-To: <CADaq8jdsEMc9ov5UgiL2beFmJznDxgJcmc8QXJzJ8o9zSAgs7A@mail.gmail.com>
Message-Id: <CDEBA4F5-FF44-4F45-BE1D-483F9C619EB4@oracle.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9475 signatures=668685
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-1911140001 definitions=main-1912180147
X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9475 signatures=668685
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1911140001 definitions=main-1912180147
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/TBHtJadoAAksoGoyL0f5ZcdSX_8>
Subject: Re: [nfsv4] Session Dealing with Current WG agenda at IETF 107
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 18 Dec 2019 18:48:14 -0000


> On Dec 18, 2019, at 12:59 PM, David Noveck <davenoveck@gmail.com> wrote:
> 
> I've requested two two-hour sessions at IETF 107.  Planning for the session dealing with the current wg agenda is farthest along and  we have a tentative schedule, which I will describe in this mail.  The other session, dealing with the future, is not as far along and I will send out informaion about it on a few days. 
> 
> The current working group agenda consists of:
> 	• existing active WG documents
> 	• milestones for which there are no existing WG documents yet
> 	• A few additional items, for which WG documents are expected, in connection with rfc5661bis.
> Attached is a powerpoint describing the state of this agenda.   I didn't include a .pdf because the size (500K) might run afoul of WG list size limits.   I can send one directly to anybody who wants one.
> 
> Regarding the items on slide two, no time has been allocated.   We hope these will be published by March.    If they aren't, I will want to discuss that somewhere where ethanol is available, rather than in a wg session..  
> 
> Regarding the items on slide three:
> 	• Sorin will be presenting on the NVMe pNFS document.    I'm allocating twenty minutes to this.   Given the 4/2020 target date for (now) requesting publication,  it will be important to get any lingering questions resolved before WGLC.
> 	• Chuck does not anticipte any need for discussion of this document/milestone.  If this document is to be discussed at IETF107, it will be in connection with the NFSv4-wide security rework that is going to be referenced by rfc5661bis.
> With regard to the items on slide four: 
> 	• Given the decision to drop the milestone for the RDMA layout type, this will not be discussed in this session.  If there is someone who is brave (or foolish, judgment call) enough to want to discuss reviving this, we might allocate some time in the future-work session. 
> 	• Chuck is anticipating a 15-minute talk on rpc-pver-rdma version 2..  I think the focus will be on the items added to version one and whether thet are are adequate to meet our goals for a version 2: big enough to be worthwhile but small enough to get done in a reasonable time.
> With regard to the items on slide five:
> 	• I've allocated 15 mnutes for a discussion of the state of delstid (will be -01 by IETF107).   If the authors need more time for this, they should let me know.
> 	• No time specfically allocated for nfs-ulb-v2. If there is neef for bried discussion of this, it could be folded into the discussion of rpc-over-rdma version 2.

It will be folded into the rpcrdma-version-two discussion. There isn't much to say about it.


> 	• Chuck will be giving a 15 minute talk on integrtiy meaurement.   I expect the discussion to focus on the metadata format description.    The intention would be to make progress about questions about its adequacy.
> I'm allocating 40 minutes for discussion of the items on slide six.   We will spend at least 10 minutes on each document and allocate the extra ten minutes as seems most appropriate given the situation in March. 
> 
> This adds up to 105 minutes, so the schedule should not be tight.   If people anticipate needing more time, please tell me before the meeting, rather than having everybody assuming they can run over without difficulty and leaving someone with only 5 or ten minutes when they need fifteen.
> <WgAgendaDec.pptx>_______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4

--
Chuck Lever