Re: [nfsv4] Adoption call for draft-dnoveck-rfc5661bis

[David Noveck <[e-mail]>]

This issue has been corrected.  Thanks.

We also need to address the companion documents draft-ietf-nfsv4-{security,
rfc5662bis} for which there were adoption calls starting at about the same
time, i.e. the middle of October 2022.

Please follow up so we can make progress on the rfc5661bis effort. There
has already been a three-month delay resulting from this adoption call and
I don't know of any issues that could reasonably result in further delay.

Further substantial prolongation might make it difficult to plan for
discussion  at IETF116 as it would result in the documents still being in
an uncertain state while they languish in this exended coda to the adoption
call process which was intended to finish by early November 2022.

If this situation cannot be corrected in the next week, please explain the
reasons for the delay.

On Sat, Dec 24, 2022, 6:05 AM David Noveck <[e-mail]> wrote:

> The adopted document is not available in the datatracker.  Please correct
> this.
>
> On Wed, Dec 14, 2022, 9:31 AM Brian Pawlowski <[e-mail]> wrote:
>
>> Good day, apologies for the inexcusable delay.
>>
>> I have determined that *we have consensus* to take on the persona draft
>> "draft-dnoveck-nfsv4 which is intended to be a standards-track describing
>>  nfsv4.1, obsoleting rfc8881" as a working group document, and on
>> bringing in to working group *Chris Inacio will be the document editor*.
>>
>> Are there any questions?
>>
>> P.S. Remaining individual document decisions coming.
>>
>> -- Brian Pawlowski
>> nfsv4 co-chair
>>
>>
>>
>> ---------- Forwarded message ---------
>> From: David Noveck <[e-mail]>
>> Date: Thu, Oct 13, 2022 at 1:58 PM
>> Subject: Adoption call for draft-dnoveck-rfc5661bis
>> To: NFSv4 <[e-mail]>
>> Cc: nfsv4-chairs <[e-mail]>, <[e-mail]>
>>
>>
>> This is an adoption call for draft-dnoveck-nfsv4 which is intended to be
>> a standards-track describing nfsv4.1, obsoleting rfc8881.
>>
>> As it says in the 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 RFC7530) and protocol extensions
>> made subsequently.  The later minor version has no dependencies on NFS
>> version 4 minor version 0, and was , until recently, documented as a
>> completely separate protocol.
>>
>> This document is part of a set of documents which collectively obsolete
>> RFC 8881.  In addition to many corrections and clarification, it will rely
>> on NFSv4-wide documents to substantially revise the treatment of protocol
>> extension, internationalization, and security, superseding the description
>> of those aspects of the protocol appearing in RFCs 5661 and 8881.
>>
>> -----
>>
>> The chairs would like to determine whether there is interest in adopting
>> this document by the nfsv4 working group. The adoption call will run for
>> two weeks and end on 10/26/2022 (UTC time). Please send any objections or
>> expressions of support for adoption to the wg mailing list.
>>
>> As stated previously, since I am editor of this document, I will not be
>> involved in making a judgment as to the existence of consensus.  It is
>> expected that Brian will be doing this with Zahed available as a backup if
>> circumstances do not allow Brian to do this job.
>>
>