Received-SPF: pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
To:     nfsv4-chairs <nfsv4-chairs@ietf.org>,
        Linux NFS Mailing List <linux-nfs@vger.kernel.org>
From:   Tom Talpey <tom@talpey.com>
Subject: FYI on an update to "RDMA Flush" I-D and IETF107
Message-ID: <03bf747f-b255-677d-1e6c-900accac463c@talpey.com>
Date:   Sun, 1 Mar 2020 09:41:45 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101
 Thunderbird/68.5.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-nfs-owner@vger.kernel.org
Precedence: bulk

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/