Re: [nfsv4] New drop of 3530bis documents

> i18n was also axed

I want to make clear here that no amputation was done.  Also, although this was a rushed procedure, no ax was used, and the patient is in stable condition.

Actually, what was done was a retransplantation of the original I18N chapter for NFSv4.0 (from draft-ietf-nfsv4-rfc3010bis-04) with some small updates.

This is actually this is the third I8n transplant that NFSv4.0 has undergone.  The other two were:

*       The replacement of the original I18N chapter by the stringprep-based chapter that appeared in RFC3530.  This was required because of IESG rejection of the original chapter.  Subsequently, the new chapter  experienced implementer rejection.
*        The replacement of the unimplemented I18N chapter in RFC3530 by the one currently in draft-ietf-nfsv4-rfc3530bis-26.  This experienced rejection during the course of IESG review, leading to the most recent transplant.

Since the goal of the new I18N chapter is to describe, what existing NFSv4.0 implementations actually do, I'm asking client and server implementers to look at the new draft and verify that it accurately does that.   Although this is not, as Tom points out, the final draft, I would urge people not to wait for that but to make sure we have a valid I18N chapter going forward.   This emergency transplant routine is getting kind of old.

-----Original Message-----
From: nfsv4-bounces@ietf.org [mailto:nfsv4-bounces@ietf.org] On Behalf Of Haynes, Tom
Sent: Friday, August 16, 2013 7:23 PM
To: nfsv4 list (nfsv4@ietf.org)
Subject: [nfsv4] New drop of 3530bis documents

This has the major updates from the IESG comments, most notably:

fs_location "dialog" pulled back from 5661 was axed

i18n was also axed

At the very least, there will be one more copy of the draft.

Please review and provide feedback as needed.
_______________________________________________
nfsv4 mailing list
nfsv4@ietf.org<mailto:nfsv4@ietf.org>
https://www.ietf.org/mailman/listinfo/nfsv4