Re: I-D Action: draft-ietf-nfsv4-rfc5661sesqui-msns-02.txt

I would like to draw attention to Section 1.1 of this document.

I've been asked several times recently what is needed for the rfc5661bis
work. Section 1.1 provides a comprehensive roadmap of what is likely
going to be needed to be done for rfc5661bis.


> On Oct 3, 2019, at 10:27 AM, David Noveck <[email protected]> wrote:
> 
> This is pretty close to -01, as a diff will show.
> 
> Relative to -01, it contains:
> 	• Changes addressing comments in Magnus's review done 9/20.
> 	• Changes addressing pending errata for rfc5661: Summary is that eratta 2006 is relevant and is adopted and extended in this version but that the other rfc5661 erratas are not relevant to this document but need to be addressed in rfc5661bis (and transferred to this document since it will obsolete rfc5661 when approved)
> 
> ---------- Forwarded message ---------
> From: <[email protected]>
> Date: Thu, Oct 3, 2019 at 9:29 AM
> Subject: [nfsv4] I-D Action: draft-ietf-nfsv4-rfc5661sesqui-msns-02.txt
> To: <[email protected]>
> Cc: <[email protected]>
> 
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Network File System Version 4 WG of the IETF.
> 
>         Title           : Network File System (NFS) Version 4 Minor Version 1 Protocol
>         Authors         : David Noveck
>                           Charles Lever
>         Filename        : draft-ietf-nfsv4-rfc5661sesqui-msns-02.txt
>         Pages           : 662
>         Date            : 2019-10-03
> 
> Abstract:
>    This document describes the Network File System (NFS) version 4 minor
>    version 1, including features retained from the base protocol (NFS
>    version 4 minor version 0, which is specified in RFC 7530) and
>    protocol extensions made subsequently.  The later minor version has
>    no dependencies on NFS version 4 minor version 0, and is considered a
>    separate protocol.
> 
>    This document obsoletes RFC5661.  It substantialy revises the
>    treatment of features relating to multi-server namesapce superseding
>    the description of those features appearing in RFC5661.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-nfsv4-rfc5661sesqui-msns/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-nfsv4-rfc5661sesqui-msns-02
> https://datatracker.ietf..org/doc/html/draft-ietf-nfsv4-rfc5661sesqui-msns-02
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-nfsv4-rfc5661sesqui-msns-02
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> nfsv4 mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/nfsv4
> _______________________________________________
> nfsv4 mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/nfsv4

--
Chuck Lever
[email protected]



_______________________________________________
nfsv4 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nfsv4