Re: [nfsv4] Thinking about an RFC5661bis.

Tom Haynes <loghyr@gmail.com> Fri, 01 March 2019 21:42 UTC

Return-Path: <loghyr@gmail.com>
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 BAF6E130F3A for <nfsv4@ietfa.amsl.com>; Fri, 1 Mar 2019 13:42:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CBcW7e1hahD4 for <nfsv4@ietfa.amsl.com>; Fri, 1 Mar 2019 13:42:47 -0800 (PST)
Received: from mail-pf1-x431.google.com (mail-pf1-x431.google.com [IPv6:2607:f8b0:4864:20::431]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1160E130EF1 for <nfsv4@ietf.org>; Fri, 1 Mar 2019 13:42:47 -0800 (PST)
Received: by mail-pf1-x431.google.com with SMTP id i20so12011178pfo.6 for <nfsv4@ietf.org>; Fri, 01 Mar 2019 13:42:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=yCWCc8UFVVTvOmdN9N4kMl8tlNXzmL5rMnEyPYMQsgU=; b=e3S9m7dlZKbdvcB0sEewUCxwyKBO/EBoOIVu5V/PPcM/a5EB90CIIj4mCEJZu84Vl/ tMz0ND3n7x7YVHwA8KwbvFLEoIdW9XPo6lDyU8aqEqPx7lQseuTLf4AyFjnsg6cdcj9e zUohSp6wgMOqvYTBQpWoipyexGYEj0zE/r1K+z1dmqdk5PMhwWsszglCIHvuW94/NW/D UZJ/ZNTnaE1c0ed2q09zW+m3gvlX2WLfvH1vHtpIx6n71iziwB2UBOLUHauArPpGu0of cd1NnI7eQGfrnUjgs3qm5Zg3Mu9Wcj3Bd8kP0KvMTsFLqqf5AT1PQf4HbbKLy7IC2Lkr sIpg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=yCWCc8UFVVTvOmdN9N4kMl8tlNXzmL5rMnEyPYMQsgU=; b=X0ujwnmuer2IoOfQvRoZhSNnK58NtOV+l29de8uHPMWmgn3UFqQuhdFkXsVKtUD38d b3YHJo1qCwX1K/EjGCgphkPhKPbnAZMMatNvhUEkDgRo50r0VcSx4ZGz2ZBvZThnO9aV vU/OVtG3be0VNHmiUdINg3X79xIArOQvxImq4fQQjT6orZdBhmWy7DcXeKK+dqifSxqB uOu4UL12WrnUDuurG/vCMiwG1vKHEb63UNvSJHQaXWjpdlb59It2P4AhcZcgqR+Vd2nf 6iQGrt9ytn3SRvZCWhUr/ZqplSNJt61qhOEvy/VRvb7S121fEIixewUUX4I9SGxe/yqM x6Ow==
X-Gm-Message-State: APjAAAUg8tCECJpyGcQnVByVqULnpyTCttb3dDyOiKOiepoQ1vuYuovp DSo8/X2pCJr2hc49Mx/ee8g=
X-Google-Smtp-Source: APXvYqyhE4S6xzZTMm31s4n+n2JZArhJDShP/L9p8Ip9lX1m31tJW+9YO7g1hN2fg1cnXDmmBc5GOw==
X-Received: by 2002:a63:ce4a:: with SMTP id r10mr6644334pgi.336.1551476566221; Fri, 01 Mar 2019 13:42:46 -0800 (PST)
Received: from macbook-pro.lat.hammerspace.com (63-235-104-78.dia.static.qwest.net. [63.235.104.78]) by smtp.gmail.com with ESMTPSA id x15sm29506975pfn.74.2019.03.01.13.42.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Mar 2019 13:42:45 -0800 (PST)
From: Tom Haynes <loghyr@gmail.com>
Message-Id: <4C694772-ED58-4B85-9C38-107E251599C5@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_73C9BC8E-BBD4-4960-A658-1F78250F5942"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Fri, 01 Mar 2019 13:42:44 -0800
In-Reply-To: <CADaq8jc+E2OL7dSWfYy3S67HLCvLfTGjCVKoz=k_uFUx8A+B3w@mail.gmail.com>
Cc: Bruce Fields <bfields@fieldses.org>, NFSv4 <nfsv4@ietf.org>
To: David Noveck <davenoveck@gmail.com>
References: <CADaq8je5pzF7m+4oVCNfSeeBDQ98kBwAdCN_o1hBrfDob=SBaA@mail.gmail.com> <20190301181752.GA18668@fieldses.org> <CADaq8jc+E2OL7dSWfYy3S67HLCvLfTGjCVKoz=k_uFUx8A+B3w@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/t3uIwvHxOEbyeqjWIDKXHfI_PJg>
Subject: Re: [nfsv4] Thinking about an RFC5661bis.
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4/>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Mar 2019 21:43:02 -0000


> On Mar 1, 2019, at 12:15 PM, David Noveck <davenoveck@gmail.com> wrote:
> 
> >    https://github.com/loghyr/3530bis <https://github.com/loghyr/3530bis>
> 
> > and check that everything applicable there also makes it to 5661bis.  
> 
> The simplest way to do this is to start the bis document based on the 
> work that has already been done, as long as Tom is Ok with it being 
> used in that way.  We would still have to check the existing erratta list for
> things that did not make it into Tom's repo. 


Yes, the current bis document belongs to the WG and not me.

I started this document when I was doing RFC3530bis as a means to fix
issues I found in RFC5661 (and had to also resolve in RFC3530bis).
As I applied errata from either RFC3530 or RFC5661, I also applied
it to RFC5661bis.

I think I had also just gone through the effort to convert from the
format used for the files to the setup I used to track the chapters.

And when I determined never to do such a large BIS again, I probably
abandoned making changes to the git repo. In any event, I found
having the RFC5661bis to be useful for reference.

So feel free to base the changes off of it!