Re: Progressing draft-ietf-nfsv4-rfc5661sesqui-msns-01

Magnus Westerlund <[email protected]>
Newsgroups gmane.ietf.nfsv4
Message-ID <[email protected]>
On Tue, 2019-09-17 at 08:53 +0000, Magnus Westerlund wrote:
> 
> > All other errata I found to be not within the scope of
> > rfc5661sesqui.
> > However, for Verified errata targeting RFC 5661: is there a process
> > for retargeting them to the RFC that rfc5661sesqui will become? If
> > rfc5661sesqui obsoletes RFC 5661, how do implementers find these 
> > errata?
> 
> I looked at what I can do in my interface, and I can unfortunately
> not
> duplicate and change the RFC number. I will contact the RFC-editor to
> see if they can do something in the backend to duplicate a set of
> Erratas to the future RFC. 


The RFC-Editor can duplicate the errata we think are relevant to have
read on RFC5661seqqui when published. So that appear to not be a big
issue. This aspect is something I will bring with me to the discussion
of the proposal by Adam on these limited scope updates. 

Cheers

Magnus Westerlund 


----------------------------------------------------------------------
Network Architecture & Protocols, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: [email protected]
----------------------------------------------------------------------

_______________________________________________
nfsv4 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nfsv4
smime.p7s (application/x-pkcs7-signature, 5.5 KB) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.