Re: [nfsv4] Update on documents related to rfc5661bis effort.

[Chuck Lever III <[e-mail]>]

On Oct 5, 2022, at 10:19 AM, Noveck, David <David.Noveck=[e-mail]<mailto:David.Noveck=[e-mail]>> wrote:

I’m looking to move to adopting any non-WG documents associated with this effort  within the next week.   Brian will wind up judging consensus on these adoption calls.

Thanks for posting your plan!

We already have three WG documents (not counting the RPC/RDMA v2 documents that are to expire), at least two of which might require significant external review. In years past, we had a large body of folks who could help out. But these days, and considering the total number of pages involved, does the WG have enough review and document stewardship resources to proceed with all of these in parallel?

In any event, I'm not feeling inclined to support adoption of Security at this time due to the many outstanding issues in that document that remain to be worked out. I'd like to see resolution of some or most of those issues before deciding on document adoption.

Also IMO the completion dates are optimistic and are likely to be extended, in particular because of the IESG's and the RFC Editor's workload. I would feel more comfortable with 6/2023 for i18n and 6/2024 for rfc5661/2bis... or even further out.



Document
Suffix
Near-term
Status
Completion
Target
Recent
Changes
Notes and
Comments
Internationalization
WGLC already requested.
2/2023
Updated (in -03) to reflect information about existing implementations of internationalized domain names.
Target date needs to be approved by AD.
I have appointed Brian as document shepherd.
Security
WG Document within a week
1/2024
Last individual draft (-05) focused on appendices clarifying process going forward.
Target date needs to be approved by AD.
Discussion of SECINFO extensions may be continuing.
Expect to focus first on issues in Appendix A.1
rfc5661bis
WG Document within a week
2/2024
Last individual draft (-05) focused on adapting to the current limited split-up plan and resolving most pending errata.
Target date needs to be approved by AD.
Expect consensus in next six months but submission will wait for security.
Only two errata reports need to be applied to document although some in document need wg discussion.
Summary of errata status in attached document
rfc5662bis
WG Document within a week
12/2023
New document.based on rfc5662.  Made changes corresponding to rfc5661 errata reports 3067, 4118, 4914.
Target date needs to be approved by AD.
Expect consensus in next few months but will delay submission to be near rfc5661bis.


<Err1004.docx>_______________________________________________
nfsv4 mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/nfsv4

--
Chuck Lever