[nfsv4] Re: Fwd: New Version Notification for draft-dnoveck-nfsv4-rfc5662bis-04.txt
Pali Rohár <pali-ietf-nfsv4@ietf.pali.im> Fri, 01 November 2024 23:48 UTC
Return-Path: <pali-ietf-nfsv4@ietf.pali.im>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B484FC169419 for <nfsv4@ietfa.amsl.com>; Fri, 1 Nov 2024 16:48:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.003
X-Spam-Level:
X-Spam-Status: No, score=-2.003 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=pali.im
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iYU1j2tGZ_QU for <nfsv4@ietfa.amsl.com>; Fri, 1 Nov 2024 16:48:50 -0700 (PDT)
Received: from pali.im (mail.pali.im [IPv6:2a02:2b88:6:5cc6::2a]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF69BC15108A for <nfsv4@ietf.org>; Fri, 1 Nov 2024 16:48:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pali.im; s=mail; t=1730504921; i=@pali.im; bh=G8CXWvBVnHP7n6ePH2Y7MjPKNmcFt1OJEmC7ldQLgOA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=IeIHtkpv/RgiCrDUbPe4zrfhtcCM5iTzjtyTj10Ps2WZ1ECiu8bnmASTnQfP+2ZJZ XvTw83HlcwURIN3wCU/XYtwCyMS3RmId1r8kaZ/aSCiQYJeC6dX0jyR3DRX/eP/t9K W/C/q7h+TSNA5dvN+Vm0EAuDcVrck9omWxVlvX0YWbE6XF7l3QwOijApXaIhp+nsZw /YcQcK5Myq50VGsKToUg/3FWAkwh3kox9xgdpScYqHOXQh9d2hwnIG4sRCIFTJn+Je v7IeiBsJ705MAuDw0/GoR17k63Z9wELZ0m5kdMFGLceJks++GcIZ7PTckEec/An28p EhnbO7ONyiT8A==
Received: by pali.im (Postfix) id F022971F; Sat, 2 Nov 2024 00:48:40 +0100 (CET)
Date: Sat, 02 Nov 2024 00:48:40 +0100
From: Pali Rohár <pali-ietf-nfsv4@ietf.pali.im>
To: David Noveck <davenoveck@gmail.com>
Message-ID: <20241101234840.v4lhs3v4ua5cb4j4@pali>
References: <CADaq8jdwHnEJaNASK1no4je1fBguY+wyZNfH-kThWArzaReUcg@mail.gmail.com> <20240905162808.lirs2sbomsmapphh@pali> <CADaq8jcHziD31wn_HDwzbqbhxLiPp-vip=sPsQhcPvqQT2f9vA@mail.gmail.com> <CADaq8jf1CWbYYwR0oTt37cgJjp9HH6mrx1ki0Yh3rZZKAfxoNA@mail.gmail.com> <20240905220337.qiibg3h3ummyb7mt@pali> <CADaq8jf=dCwdnLkDX5OjYWmF9L9xJBKNUnaeAf1aSN2TKzS6MA@mail.gmail.com> <20240906161621.7b7kfw2ipzhx7g4o@pali> <CADaq8jc7vv9hvx+Qqf6MmhBOpe=jc0Uu4FpSFxpUJfYxQ2Q5yw@mail.gmail.com> <20240918133809.hogdxknznzleny33@pali> <CADaq8jc1zdXZCADB1KjdcZeSX6C5B7itumU0xjbLdoOVJQBZeg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CADaq8jc1zdXZCADB1KjdcZeSX6C5B7itumU0xjbLdoOVJQBZeg@mail.gmail.com>
User-Agent: NeoMutt/20180716
Message-ID-Hash: 5CTC7QZ5TB4IFK5T2QP6XEF5BX3HR5K5
X-Message-ID-Hash: 5CTC7QZ5TB4IFK5T2QP6XEF5BX3HR5K5
X-MailFrom: pali-ietf-nfsv4@ietf.pali.im
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-nfsv4.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: NFSv4 <nfsv4@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [nfsv4] Re: Fwd: New Version Notification for draft-dnoveck-nfsv4-rfc5662bis-04.txt
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/Utp8eA-m0APaV86AJ3k2kwf8fLA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Owner: <mailto:nfsv4-owner@ietf.org>
List-Post: <mailto:nfsv4@ietf.org>
List-Subscribe: <mailto:nfsv4-join@ietf.org>
List-Unsubscribe: <mailto:nfsv4-leave@ietf.org>
Hello, would you be able to verify those two erratas eid7667 and eid7669? On Wednesday 18 September 2024 09:58:25 David Noveck wrote: > I will submit -05, with those fixes, as soon as the author tools are > working again. > > On Wed, Sep 18, 2024 at 9:38 AM Pali Rohár <pali-ietf-nfsv4@ietf.pali.im> > wrote: > > > Ok, thanks for this! The still unaddressed are eid7667 and eid7669 as of > > the last rfc5662bis-04 draft. > > > > On Wednesday 18 September 2024 08:35:01 David Noveck wrote: > > > 7386 is addressed in rfc5661bis-08. I don't know of any unaddressed > > > errata reports.for this set of documents, > > > > > > On Fri, Sep 6, 2024 at 12:16 PM Pali Rohár <pali-ietf-nfsv4@ietf.pali.im > > > > > > wrote: > > > > > > > Hello and thank you for information. > > > > > > > > I'm looking at it again, as I sent list of erratas in my first email > > > > > > https://mailarchive.ietf.org/arch/msg/nfsv4/05tLPoZl1Jh8VmUaY_nFRAmAMeA/ > > > > and two of erratas eid7667 and eid7669 are for RFC 5662, the document > > > > which you are updating in this thread (XDR definitions). And another > > one > > > > is eid7386 which is for RFC 8881 (spec itself) which you referred in > > > > other email thread. > > > > > > > > I think that in this rfc5662bis document you can handle only eid7667 > > and > > > > eid7669. The last one needs to go via other rfc5661/rfc8881-bis > > document > > > > update. > > > > > > > > Pali > > > > > > > > On Friday 06 September 2024 04:02:47 David Noveck wrote: > > > > > The formal status of these is "Reported" which really means they > > haven't > > > > > been reviewed yet. Normally, the review process is triggered by an > > email > > > > > sent to the authors. In thjs case, two of the authors are no longer > > > > active > > > > > in the IETF but since I am, there might have been an email sent to my > > > > > netapp email. I will look but if I missed it a year ago, it us > > probably > > > > > not recoverable now. > > > > > > > > > > There should be a way to kick off the review process without the > > email > > > > but > > > > > I'm not sure one exists. I will send mail to ietf-action to see. > > > > > > > > > > On Thu, Sep 5, 2024, 6:03 PM Pali Rohár < > > pali-ietf-nfsv4@ietf.pali.im> > > > > > wrote: > > > > > > > > > > > Hello, Thank you for reply and looking at it. > > > > > > > > > > > > Anyway, what is the format status of those erratas? > > > > > > I have reported year ago but they have not been reviewed yet. > > > > > > > > > > > > Pali > > > > > > > > > > > > On Thursday 05 September 2024 13:44:24 David Noveck wrote: > > > > > > > Will include these in -05. Should be out next week. > > > > > > > > > > > > > > On Thu, Sep 5, 2024, 1:30 PM David Noveck <davenoveck@gmail.com> > > > > wrote: > > > > > > > > > > > > > > > Ok, I'll take a look. > > > > > > > > > > > > > > > > On Thu, Sep 5, 2024, 12:28 PM Pali Rohár < > > > > pali-ietf-nfsv4@ietf.pali.im > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > >> Hello David, could you look at errata reports which I sent for > > > > > > RFC5662? > > > > > > > >> It would be nice to review them and incorporate fixed into > > new bis > > > > > > > >> document. > > > > > > > >> Pali > > > > > > > >> > > > > > > > >> On Thursday 05 September 2024 12:09:32 David Noveck wrote: > > > > > > > >> > IIRC, an earlier version of this draft was supposed to be > > going > > > > > > through > > > > > > > >> the > > > > > > > >> > adoption call process, starting "at or before" IETF120. If > > > > there is > > > > > > > >> some > > > > > > > >> > reason/issue explaining why it has not been adopted, I need > > to > > > > get > > > > > > an > > > > > > > >> > explanation of that so that I can address whatever issues > > exist, > > > > > > > >> allowing > > > > > > > >> > us to make progress on the respecification effort. > > > > > > > >> > > > > > > > > >> > This case is much better than that for the security > > document, > > > > which > > > > > > has > > > > > > > >> > lingered in the adoption-requested-but-no-response state for > > > > about > > > > > > two > > > > > > > >> > years, but we need to avoid a repetition of that > > situation, I > > > > > > think the > > > > > > > >> > chairs need to follow up on all the documents for which > > > > adoption has > > > > > > > >> been > > > > > > > >> > requested, in a reasonable time, which has not been the > > case. > > > > > > > >> > > > > > > > > >> > ---------- Forwarded message --------- > > > > > > > >> > From: <internet-drafts@ietf.org> > > > > > > > >> > Date: Thu, Sep 5, 2024 at 11:49 AM > > > > > > > >> > Subject: New Version Notification for > > > > > > > >> draft-dnoveck-nfsv4-rfc5662bis-04.txt > > > > > > > >> > To: David Noveck <davenoveck@gmail.com> > > > > > > > >> > > > > > > > > >> > > > > > > > > >> > A new version of Internet-Draft > > > > > > draft-dnoveck-nfsv4-rfc5662bis-04.txt > > > > > > > >> has > > > > > > > >> > been > > > > > > > >> > successfully submitted by David Noveck and posted to the > > > > > > > >> > IETF repository. > > > > > > > >> > > > > > > > > >> > Name: draft-dnoveck-nfsv4-rfc5662bis > > > > > > > >> > Revision: 04 > > > > > > > >> > Title: Network File System (NFS) Version 4 Minor Version > > 1 > > > > > > External > > > > > > > >> Data > > > > > > > >> > Representation Standard (XDR) Description > > > > > > > >> > Date: 2024-09-05 > > > > > > > >> > Group: Individual Submission > > > > > > > >> > Pages: 79 > > > > > > > >> > URL: > > > > > > > >> > > > > > > > > > https://www.ietf.org/archive/id/draft-dnoveck-nfsv4-rfc5662bis-04.txt > > > > > > > >> > Status: > > > > > > > >> > > https://datatracker.ietf.org/doc/draft-dnoveck-nfsv4-rfc5662bis/ > > > > > > > >> > HTMLized: > > > > > > > >> > > > > > > > > > https://datatracker.ietf.org/doc/html/draft-dnoveck-nfsv4-rfc5662bis > > > > > > > >> > Diff: > > > > > > > >> > > > > > > > > >> > > > > > > > > > > > > https://author-tools.ietf.org/iddiff?url2=draft-dnoveck-nfsv4-rfc5662bis-04 > > > > > > > >> > > > > > > > > >> > Abstract: > > > > > > > >> > > > > > > > > >> > This document provides the External Data Representation > > > > Standard > > > > > > > >> > (XDR) description for Network File System version 4 > > (NFSv4) > > > > minor > > > > > > > >> > version 1. > > > > > > > >> > > > > > > > > >> > It includes protocol extensions made as part of > > > > respecification > > > > > > > >> > effort for minor version 1. > > > > > > > >> > > > > > > > > >> > It obsoletes and replaces RFC5662. > > > > > > > >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > >> > The IETF Secretariat > > > > > > > >> > > > > > > > > > > > > > > > > > > > >
- [nfsv4] Fwd: New Version Notification for draft-d… David Noveck
- [nfsv4] Re: Fwd: New Version Notification for dra… Pali Rohár
- [nfsv4] Re: Fwd: New Version Notification for dra… David Noveck
- [nfsv4] Re: Fwd: New Version Notification for dra… David Noveck
- [nfsv4] Re: Fwd: New Version Notification for dra… Pali Rohár
- [nfsv4] Re: Fwd: New Version Notification for dra… David Noveck
- [nfsv4] Re: Fwd: New Version Notification for dra… Pali Rohár
- [nfsv4] Re: Fwd: New Version Notification for dra… David Noveck
- [nfsv4] Re: Fwd: New Version Notification for dra… Pali Rohár
- [nfsv4] Re: Fwd: New Version Notification for dra… David Noveck
- [nfsv4] Re: Fwd: New Version Notification for dra… Pali Rohár
- [nfsv4] Re: Fwd: New Version Notification for dra… David Noveck
- [nfsv4] Re: Fwd: New Version Notification for dra… Pali Rohár
- [nfsv4] Re: New Version Notification for draft-dn… David Noveck
- [nfsv4] Re: New Version Notification for draft-dn… Chris Inacio