Re: [nfsv4] Proposed charter changes (with updates)

On Fri, Jun 5, 2020 at 8:15 AM Tom Talpey <tom@talpey.com> wrote:

> On 6/5/2020 3:25 AM, Lars Eggert wrote:
> > Hi,
> >
> > On 2020-6-5, at 10:23, Magnus Westerlund <magnus.westerlund=
> 40ericsson.com@dmarc.ietf.org> wrote:
> >> For that reason I would recommend that one work through the technical
> proposal
> >> to better understand what desired propoerties of RDMA over QUIC has, as
> well as
> >> what is required to realize those from QUIC. Then one can likely make a
> good
> >> decision if that work should be done in QUIC WG or in this or another
> WG.
> >
> > +1
> >
> > An initial individual draft would be very useful in triaging where the
> best place for this work would be.
>
> So, to be clear I was describing a process for a potential
> NFSv4-over-QUIC binding, not an RDMA-over-QUIC one.

That would probably take the form of an extension to RPC, updating RFC
5531, with no change to QUIC itself anticipated.  Unless I'm missing
something, that could be done even under the current charter, although I'm
cc-ing Lars to make sure he is aware of the possibility of us doing this.

> Although,
> I have been thinking about both.
>
> Apparently, Magnus read your mind.   I'm not sure how I feel about having
AD's with that capability :-)

> I'd like to get the RDMA Push Mode extension draft process
> through the knothole before considering the next one. :-)
>

I hope "through the knothole" means waiting for IESG approval.   Waiting
for publication as an RFC has lately become a process of unbounded duration.

I think you are the right person to do the individual draft for
RDMA-over-QUIC and hope that you would be interested in doing it, when the
time is ripe.

With regard to RPC-over-QUIC, I'd be glad if you are interested in doing
this, but there are a number of people that can participate so it would not
take all that much of your time.  It is interesting to the working group
primarily because of its security implications.

>
> Tom.
>
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4
>