Re: [nfsv4] FYI on an update to "RDMA Flush" I-D and IETF107

Chuck Lever <chuck.lever@oracle.com> Mon, 02 March 2020 16:36 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 37E3F3A0AF6; Mon, 2 Mar 2020 08:36:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 JCL2pU_y2lFm; Mon, 2 Mar 2020 08:36:39 -0800 (PST)
Received: from userp2120.oracle.com (userp2120.oracle.com [156.151.31.85]) (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 BD79C3A0ABD; Mon, 2 Mar 2020 08:36:38 -0800 (PST)
Received: from pps.filterd (userp2120.oracle.com [127.0.0.1]) by userp2120.oracle.com (8.16.0.42/8.16.0.42) with SMTP id 022GWq6C177662; Mon, 2 Mar 2020 16:36:38 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=content-type : mime-version : subject : from : in-reply-to : date : cc : content-transfer-encoding : message-id : references : to; s=corp-2020-01-29; bh=nQOqH5TuClsOhTGF0M9GeVX5fMOszyPPgRF93oxp/lk=; b=qbvp2oSmHOe2h1fgEzUDRXuQbyEv+vnozMuTUXKrjB8Ic2DZ02KS9PAnSEdvL1dfmjSj sfq9YTqgndhSgZoadRQYWv37f1oznsksDas7N6aAq0tYbmkNWe5M670L+J/SLTZ1R7KF xZOouWsOVVSeOCxZdTrmGbubOrEUe+c7CbYj7O6MBg32DskH5tofu2NOcaQ76iCVQT3P 7MH9+XySFF6d8FspV9+JhP205XsZnybjdFlr6BcEtqJX9iKBW9kem+1uIdtSAokYYv7h tbEMO1dqhvuAhxl0XtOdwogAxMzc50HFKl6MWRXCyBdJ7S4/64u+14m3pZgFAzQndJaG 0g==
Received: from userp3020.oracle.com (userp3020.oracle.com [156.151.31.79]) by userp2120.oracle.com with ESMTP id 2yghn2vrjy-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 02 Mar 2020 16:36:38 +0000
Received: from pps.filterd (userp3020.oracle.com [127.0.0.1]) by userp3020.oracle.com (8.16.0.42/8.16.0.42) with SMTP id 022GWOmj131280; Mon, 2 Mar 2020 16:36:37 GMT
Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by userp3020.oracle.com with ESMTP id 2yg1p24sq6-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 02 Mar 2020 16:36:37 +0000
Received: from abhmp0004.oracle.com (abhmp0004.oracle.com [141.146.116.10]) by aserv0121.oracle.com (8.14.4/8.13.8) with ESMTP id 022GaZKO003502; Mon, 2 Mar 2020 16:36:36 GMT
Received: from anon-dhcp-153.1015granger.net (/68.61.232.219) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 02 Mar 2020 08:36:35 -0800
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Chuck Lever <chuck.lever@oracle.com>
In-Reply-To: <03bf747f-b255-677d-1e6c-900accac463c@talpey.com>
Date: Mon, 2 Mar 2020 11:36:33 -0500
Cc: nfsv4-chairs <nfsv4-chairs@ietf.org>, NFSv4 <nfsv4@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <36BC4F65-C6E0-4030-B650-52AB209E2804@oracle.com>
References: <03bf747f-b255-677d-1e6c-900accac463c@talpey.com>
To: Tom Talpey <tom@talpey.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9547 signatures=668685
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 phishscore=0 malwarescore=0 mlxlogscore=999 mlxscore=0 spamscore=0 adultscore=0 bulkscore=0 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2001150001 definitions=main-2003020114
X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9547 signatures=668685
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 malwarescore=0 phishscore=0 spamscore=0 impostorscore=0 mlxscore=0 adultscore=0 mlxlogscore=999 lowpriorityscore=0 priorityscore=1501 bulkscore=0 clxscore=1015 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2001150001 definitions=main-2003020114
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/r1rDzpmX7gOw4B1zk0M4-splk0E>
Subject: Re: [nfsv4] FYI on an update to "RDMA Flush" I-D and IETF107
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: Mon, 02 Mar 2020 16:36:42 -0000

[ Cc: corrected ]

> On Mar 1, 2020, at 12:41 PM, Tom Talpey <tom@talpey.com> wrote:
> 
> A couple of things FYI.
> 
> - I am updating the draft-talpey-rdma-commit document* in
> advance of IETF107. This is an iWARP extension in support of
> RDMA access to persistent memory, although it is somewhat more
> general than simply pmem. There is a parallel effort in IBTA.
> 
> - Because there is no longer an RDDP working group, one option
> discussed in the past with several WG chairs and Transport ADs was
> to move this forward in the NFSv4 WG. With the new chair situation,
> and the document republication, it may be worthwhile to discuss
> this again. I believe there is good merit to the idea.
> 
> - I plan to attend IETF107 NFSv4 WG meeting, but can only be
> there one day. I hope to discuss this further there. If you
> would like me to say something as part of the agenda, I am
> happy to do so.
> 
> Tom.
> 
> 
> * https://datatracker.ietf.org/doc/draft-talpey-rdma-commit/

The final IETF 107 session agenda has been published, and now both
nfsv4 WG sessions are planned for Thursday afternoon.

I propose the addition of a 10-minute session led by Tom, if there
is room on the nfsv4 agenda, to discuss the following matters:

- A review of the material for those unfamiliar with RDMA Flush
- Whether this work falls in the current WG charter
- Whether the I-D should be adopted as an nfsv4 WG document
- Whether a milestone is needed
- Whether this is a one-time proposal, or if we are agreeing
  that until there is another IETF home for RDMA-related documents,
  the nfsv4 WG should act as shepherd for such work.


--
Chuck Lever