[nfsv4] What does v4.2 look like?

[Tom Haynes <[e-mail]>]

On 7/19/10 8:06 PM, [e-mail] wrote:
>
> Note that this doesn't fully address the issue of EOS across sessions
> for non-idempotent requests and I think some v4.2 changes would be
> required, but v4.1 does allow different so_minor_id value for clustered
> servers, and it seems kind of rough to say you can only do this if you
> accept the possibility of data corruption.
>
>    

Without a clear picture of what v4.2 means, is this the type of thing we 
want to put in it?

I'm not asking if it is something we want to fix, but rather is v4.2 the 
right vehicle?

If I look at v4.2, I see it as a collection of small optional feature 
sets - pathless objects,
hole punching, space reservation, server to server copy, dedup, 
metastripe, access
check, etc. I could be wrong, but that seems to be what people are 
proposing.

I don't see it as fixing things we got subtly wrong in either 4.0 or 4.1.

Perhaps even releases introduce new functionality and odd releases are 
informational?
Even ones driven by design and odd ones driven by implementation experience?

And that raises another question, according to your slide deck:
http://www.ietf.org/proceedings/10mar/slides/nfsv4-9.pdf

We don't want another huge document. But at what point do we want a 
comprehensive
document that rolls up all of the smaller v4.x changes from v4.1? I.e., 
when does it make
sense to have one document to consult versus 10 other ones?