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

Tom Talpey <ttalpey@microsoft.com> Mon, 02 March 2020 19:01 UTC

Return-Path: <ttalpey@microsoft.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 96EB53A0F0B; Mon, 2 Mar 2020 11:01:51 -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, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 c7pZhwv2vFY8; Mon, 2 Mar 2020 11:01:50 -0800 (PST)
Received: from NAM06-BL2-obe.outbound.protection.outlook.com (mail-eopbgr650138.outbound.protection.outlook.com [40.107.65.138]) (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 453213A0F12; Mon, 2 Mar 2020 11:01:47 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=K10CKg75NNdS/7X+St0ovkBRvinWBlHb0Ib9bh60BIbNgY/Mdy2wUvbVbzjOAKwbrovMZw4EyrpRqRE4XY/652xDtuM+yHmmscXdYC+h8sas2jR25iTkQoLO1wFzedDUfMMJmm/phBYnY6egqld3u9fIprSgea/I12p+q30IPiXKruiTvdsJcbnwcTCb/V5SGn2OenGmSiE7+11sBgQZolltV6MQw6t1+9oIiy51ahGK1GzZwQKtwOisSor7d7J2nmsvv33F/K+C7cQXq0fx/cJcN31hENf8UpJsfZ/n7K0+D8mSHQKnVfRxxsEuegbh3P3VEdiiRnazyDuwQ+mH+Q==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;bh=Vy0kfukHtOdE6oONVpQ4udxpHZJWalBOPkx12aK0OwE=; b=Fux+qkXAyOqtOtJuIUe72vIMdCteK9Pq9h/vLTbMMyROoofrvRs/8HKFM+waJI4WPKFgCRj8GcKRXGd8jZVWrTVACZOZK6fhkjvDzJbFIy2NPKHj1bphr4OtvjBbdpIdnEhB+UYP+ruiZY0kzHc6RHSDoncRzTnjCgXRefquuk9HtYg6sG10LQGvQ2FUoWplVVLNA7ztrZua5tU1PUOL0lC5DjK7GrWjgGlHhwH/S72fXm0Acly6Rz0t7XOSBAa++KKVh4lAF+Vb0/Yb/UmHvn4Rz5EXd9zZvNUejBC6PhCwtk7KbZU8gnTs+wnik31yIO/LiZVImLs2cOjFeM8cyw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;bh=Vy0kfukHtOdE6oONVpQ4udxpHZJWalBOPkx12aK0OwE=; b=KorEYAsVpxDEUTIiCZV5wglVvAQZwHTaleU5+fP3/7cq4lT5KGBIuwsAEiXsW22TOqVg9kXrNX/Xv3DGekRdQ4YQ9W498uHN2nC1WVbwU7JUJNic8npADkvcd9jhRd6OaVW/ogGQPxzazXLsGJ4Z0KdZJZfNm8Tx+v+eIEVGtco=
Received: from BYAPR00MB0645.namprd00.prod.outlook.com (2603:10b6:a03:ab::28) by BY5PR00MB0840.namprd00.prod.outlook.com (2603:10b6:a03:1d7::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2827.0; Mon, 2 Mar 2020 19:01:45 +0000
Received: from BYAPR00MB0645.namprd00.prod.outlook.com ([fe80::9d55:183c:1063:aacf]) by BYAPR00MB0645.namprd00.prod.outlook.com ([fe80::9d55:183c:1063:aacf%4]) with mapi id 15.20.2826.000; Mon, 2 Mar 2020 19:01:45 +0000
From: Tom Talpey <ttalpey@microsoft.com>
To: David Noveck <davenoveck@gmail.com>, Chuck Lever <chuck.lever@oracle.com>
CC: Tom Talpey <tom@talpey.com>, nfsv4-chairs <nfsv4-chairs@ietf.org>, NFSv4 <nfsv4@ietf.org>
Thread-Topic: [nfsv4] FYI on an update to "RDMA Flush" I-D and IETF107
Thread-Index: AdXwxOs0nnGG9pLtTkiGBPmVDC2wEg==
Date: Mon, 02 Mar 2020 19:01:45 +0000
Message-ID: <BYAPR00MB064509E30C8AF4C2D03F7B40A0E70@BYAPR00MB0645.namprd00.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ActionId=acef6cc5-f629-48c4-bbcd-00005bd7aece; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=true; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Standard; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=Internal; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2020-03-02T18:43:28Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47;
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ttalpey@microsoft.com;
x-originating-ip: [2001:4898:80e8:3:d585:6fc2:cef:ca0b]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: eb33dd69-6b65-40be-9e6c-08d7bedc2736
x-ms-traffictypediagnostic: BY5PR00MB0840:
x-microsoft-antispam-prvs: <BY5PR00MB0840E95961A10B71F8272F9BA0E70@BY5PR00MB0840.namprd00.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 033054F29A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(366004)(396003)(346002)(136003)(39860400002)(376002)(199004)(189003)(110136005)(54906003)(316002)(186003)(9686003)(8676002)(81166006)(81156014)(8936002)(55016002)(33656002)(8990500004)(86362001)(4326008)(71200400001)(6506007)(966005)(2906002)(15650500001)(66556008)(478600001)(76116006)(66446008)(64756008)(52536014)(66476007)(10290500003)(53546011)(5660300002)(7696005)(66946007); DIR:OUT; SFP:1102; SCL:1; SRVR:BY5PR00MB0840; H:BYAPR00MB0645.namprd00.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: MFt2PnZ0qU3aJvwg1RynfHQa2agtaMfGIIhuiNpuEMMxJh3YCntEEr74pRP2We9BBJFv+lra6miAK5+syKm+wMFcXMwh3TYlErvVToU4HOrj1NbLfgddQrdSH4HsEVuhO9k0vc9IVZPyaFsoQbUqISZ6OFKFjc2MOZVopz56fGYB3uje1ehZiktojeeqoOA6MVWYopeA6o3f8gn4WNxZK+wG2ktcYXrj+v5S20imfWVw6FmWDaG2bWz2d3TAuNAi16Vc8zANyQX7BKoL4tKKG45pECxUG1Wj2bu24IvQ7tcWx/E4nRsQp2w3wjWitsr2Kd5QKghNWMrG0STYdFBxAL4L+AHEQVCmCkOQshBEcx4H43HLr1ZCIpzscn1DVs0UZ0MwZXiAM+oRoaucWwxZ7M+IqCpWpEd/cDiXPxpcc6a97OvObcT28hFoWv06UCZMJeaIA7cWl5xK5Y/doS73omzNHFMz21MCBWj1506x1S+6WxoQEqmqxvHuwFxeTDPuDt9k8WrnkbTew7rb7Ld0Xw==
x-ms-exchange-antispam-messagedata: KzZ4nf9m/W8Trk7/fbkcR/qQ6qUEZcg8VEKrq+oekh3rcsrokMTxL7NiONULei+OnJJIbnhAC0ICnlubt85ZBL3dS1fw9lToaFKhrHgdIvbfbAPajlHL5nebPx/SIEB/28KE1Oz3KAIMKrtPyIjSRf1Td/gQJTMcY4ItA2aWh2dMTBoSj/SjvS2d/69+gbO51tPfom0EYButkYXeKhuZuQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BYAPR00MB064509E30C8AF4C2D03F7B40A0E70BYAPR00MB0645namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: eb33dd69-6b65-40be-9e6c-08d7bedc2736
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Mar 2020 19:01:45.4329 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: JCbpLTSF9AzRWCTw5MDWTJZzF1mQe9n74kunM2hDwXHXSYr/T8ZEIQ4KKxRaKhI7PkWyGjDJWvf7aUwVvKb3fQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR00MB0840
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/vO5xgAn1SG9Qf1SHEPmbXYNPrqw>
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 19:01:52 -0000

Yes, I’m fine with presenting as I said, and thanks Chuck for reforwarding and summarizing. Ten minutes is good. Here’s an agenda proposal:

RDMA Extensions/Tom Talpey/10min

Background and upcoming outlook for extensions to RDDP protocols in support of memory placement and “push mode”. Discussion of whether NFSv4 is an appropriate working group for the effort, in place of former RDDP.


From: nfsv4 <nfsv4-bounces@ietf.org> On Behalf Of David Noveck
Sent: Monday, March 2, 2020 9:57 AM
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Tom Talpey <tom@talpey.com>; nfsv4-chairs <nfsv4-chairs@ietf.org>; NFSv4 <nfsv4@ietf.org>
Subject: [EXTERNAL] Re: [nfsv4] FYI on an update to "RDMA Flush" I-D and IETF107

Assuming Tom is OK with making this presentation, I will add it to the next iteration of the agenda.

To keep ten minutes available we will have to enforce time discipline for existing talks..

If Tom does not provide a short description by EOD tomorrow, I will do my best to boil down Chuck's reasonable list into something that fits the existing agenda format.

On Mon, Mar 2, 2020 at 11:36 AM Chuck Lever <chuck.lever@oracle.com<mailto:chuck.lever@oracle.com>> wrote:
[ Cc: corrected ]

> On Mar 1, 2020, at 12:41 PM, Tom Talpey <tom@talpey.com<mailto: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