Re: [nfsv4] IETF 102 nfsv4 WG meeting go/no-go

[David Noveck <[e-mail]>]

 > https://datatracker.ietf.org/meeting/important-dates/

> Says the cut-off for requesting a meeting room is June 1, 2018.

Thanks for bringing this to our attention.

> I can think of a few agenda topics that are relevant at this time:

> - Tom/Trond have some virtualization-related extensions and other
protocol fixups

Agree that we should discuss this work.  I owe Tom a review of his document
and want that to be out at least a month before the meeting.

> - I can give a backgrounder on the Integrity Measurement work I'm doing

That would be good.  Given that document plans for this have changed
recently,
it will be good to prepare the working group for what is probably coming.

> - Dave and I have the mv0 and mv1 trunking documents

I also have draft-ietf-nfsv4-migration-issues which has a milestone date of
June
2018 for WGLC.   -15, which I expect to be the last revision, will be out
in the next
few weeks so WGLC is possible by 6/30, but, realistically, we have to
prepared to
discuss this at IETF102.

After -15 is out, I will send mail to the Spencer's regarding schedule
expectations.
I will copy the working group list to give others the opportnity to comment
about
the realism (or otherwise) of my expectations.

- Any other 2018 milestones, such as the expired pNFS SCSI NVMe layout I-D

This seems to me the only 2018 milestone that cannot be accommodated by a
relatively minor adjustment.  However, given that we are meeting in July
2018,
I think we need to look more than five months ahead.

Perhaps we need to review our milestones in general and discuss the
potential
need for adjustments.

- RPC/RDMA credits: the road ahead

Good topic.

Unless AI has made some enormous strides, there will be no self-driving
cars on this road :-)

> That's not an exhaustive list, but it seems like critical mass already.

It's enough for a 150-minute session.

> Any other thoughts?

Given that this will be in the eastern time zone, remote participation
should
be relatively easy.  So people should not have to wait for travel appoval
before deciding to have this meeting.

> Can we set a go/no-go decision date, say Friday May 18th?

I don't see why not.

On Mon, May 7, 2018 at 11:12 AM, Chuck Lever <[e-mail]> wrote:

> https://datatracker.ietf.org/meeting/important-dates/
>
> Says the cut-off for requesting a meeting room is June 1, 2018.
>
> I can think of a few agenda topics that are relevant at this time:
>
> - Tom/Trond have some virtualization-related extensions and other protocol
> fixups
> - I can give a backgrounder on the Integrity Measurement work I'm doing
> - Dave and I have the mv0 and mv1 trunking documents
> - Any other 2018 milestones, such as the expired pNFS SCSI NVMe layout I-D
> - RPC/RDMA credits: the road ahead
>
> That's not an exhaustive list, but it seems like critical mass already.
> Any other thoughts?
>
> Can we set a go/no-go decision date, say Friday May 18th?
>
>
> --
> Chuck Lever
>
>
>
> _______________________________________________
> nfsv4 mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/nfsv4
>