Re: [nfsv4] Documents, pre-drafts, and submission plans for documents related to the new security discussion to be part of the rfc5661bis effort.

Dave has updated the security and ACL drafts and put them in datatracker
since posting this email. Apologies, this message was stuck in queue
because of size of attachments. :-/

Please refer to these security and ACL drafts:

https://datatracker.ietf.org/doc/draft-dnoveck-nfsv4-security/

https://datatracker.ietf.org/doc/draft-dnoveck-nfsv4-acls/

-- beepy

On Mon, Mar 4, 2024 at 9:42 AM David Noveck <davenoveck@gmail.com> wrote:

> I have been working on next steps for the security document and have some
> documents for people to look at and will also discuss my plans for document
> submission in light of the 3/4 document submission deadline for IETF19.
>
>
>    - The current version of the Ontap implementation report is attached.
>    There are no plans to submit this as an IETF document.   People might find
>    it interesting in that it provides motivation for the changes made in the
>    ACL document.  Also, it gives an indication of the kind of information we
>    will need about existing ACL implementations.  If people have trouble with
>    the .docx format, let me know and I can post other formats.
>
>
>    - There is a pre-draft for the -08 of the security doc.  It is close
>    to complete and I will be able to submit the complete document by the
>    deadline.  There will probably not be time to incorporate
>    changes/suggestions based on the pre-draft in time for the -08, but will
>    probably have to defer responding to those until -09.
>
> Relative to -07, the main changes are to split the ACL stuff into a
> separate document, and to address the identity-related issues that Chris
> raised.  The document split makes an iddifff with -07 pretty messy.  The
> changes related to the identity issue are mostly in the sections 5.1 of the
> documents being compared.
>
>
> One noteworthy issue about the pre-draft is that since the ACL document
> has not been submitted yet, it cannot be referenced as it has to be in many
> places.  For now, I am referencing rfc5662bis instead, but will have to fix
> this before actual submission.  Also, some inter-document references are
> coded as ACLSPEC(target).  This will also be addressed before submission of
> the -08.
>
>
>    - There is also attached an early pre-draft for
>    *draft-dnoveck-nfsv4-acls-00*.  The work on this draft is not as far
>    along as that for the security document proper and will not be complete in
>    time for the 3/4 deadline.
>
> Nevertheless, I will submit something very close to the current pre-draft
> as the -00 with the understanding that there is still work to be done.  The
> first complete draft of this document will be submitted as -01 before the
> next wg interim meeting in early April.
>
>
> One important issue to note about the -00 is that the numeric ID's
> associated with consensus items in that document are temporary and likely
> to change, unlike those in the security document draft.  This will be
> relevant if some of the work discussed to transform these into github
> issues lists proceeds before acls-01 is out.
>
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4
>