Re: [nfsv4] Review of draft-ietf-nfsv4-rfc5667bis-03 (part one of three)

[Chuck Lever <[e-mail]>]

> On Dec 21, 2016, at 1:16 PM, David Noveck <[e-mail]> wrote:
> 
> > Because I'm not taking "the last of these approaches" (see
> > above), 
> 
> This third approach was:
> 
> Restructure the document to distinguish material required by rfc566bis and applicable to all transport versions from explanatory/illustrative  material tied to Version One.
> 
> I'm not clear why you object to this and what you propose to do instead.  You are very clear why you don't want to adopt either of the first two approaches listed above.

I plan to replace data placement mechanism-specific language that you
objected to (but did not replace in your proposed changes) with the generic
terminology we introduce in rfc5666bis.

That's probably closest to your "approach two" but with as little redaction
as I can get away with.

It's not the approach you took in your proposed changes. So as I said, I
will use your proposals as guidance, but probably not merge them wholesale.

I stated some risks to this approach. I'm willing to try it anyway. It's
only spilled electrons, trapped in a change control system, that can be
reverted if we end up not liking them.


> > at least for now, I will probably not merge many of your proposed
> > changes in this area, but will use the body of your remarks as a guide to
> > rework the text to be agnostic to data placement mechanism.
> 
> OK, but your point above is that this might result in a document that is unclear to implementers, so I think it will need to supplemented by material which is not transport-version-agnostic.  If you have such material, it needs to be clearly labeled as transport-version specific.

Agreed. In any event, I will produce a revision soon, and you can see if
I've corrected the issues you identified.


--
Chuck Lever