Re: [nfsv4] Thinking about an RFC5661bis.
Tom Haynes <loghyr@gmail.com> Thu, 28 February 2019 20:58 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 EFEA7129524 for <nfsv4@ietfa.amsl.com>; Thu, 28 Feb 2019 12:58:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 7Uw8ZfAeUR2y for <nfsv4@ietfa.amsl.com>; Thu, 28 Feb 2019 12:58:40 -0800 (PST)
Received: from mail-pl1-x62e.google.com (mail-pl1-x62e.google.com [IPv6:2607:f8b0:4864:20::62e]) (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 A4364127AC2 for <nfsv4@ietf.org>; Thu, 28 Feb 2019 12:58:40 -0800 (PST)
Received: by mail-pl1-x62e.google.com with SMTP id bj4so10321694plb.7 for <nfsv4@ietf.org>; Thu, 28 Feb 2019 12:58:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=sWMvtJQfXCSuY97RewClmrdM/o/olx/zXsObfZYuIXM=; b=gmREVCgGguceojcyuq6ZmnA5DGnLAnwaApfRBAaS6bnXqpXI8XKBww6Ppp96nVcgeM B9oOjYs1lpaWDtPyRnlhvqgNZncjHJ5Gp/0MpQZtCFRtipaiHvbTTXxiAfy/4/KCosjc tH8OSA9QTW0KAI0ucE4SrVM63Yj14FhfzDfE1zWPN/2mryIakrbMh8bCUyEzalLxSw3H Mww90aY+qLKRfgyOeIXra28WrB702j8CLQidNiiEX/aIsn5Zuk2IyhGuRriGiHXeZ9kX gfHmvDAKn3/aGsRy1BmO83UZAM4eTyVimdd1Fe4/5NNB76f2QjqSUqa09HsE0rn1ddUg bjlw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=sWMvtJQfXCSuY97RewClmrdM/o/olx/zXsObfZYuIXM=; b=Ho/ydfgxFmY0p8iq8kvqdpd0Zw8F0eX1C+3v+ajGcp/1rEwDsq2MJ8gFF1s14fX/Nf GdmS+ML0hZk6J5D9jDdB+e4TNWYv0/cudKkdDLGa6EOWILcKssRuyZLBcFZC08RMKQ+V 1MMwBl2krIekJCcn3UTgFT/8n2C3DtK8Ga18OAqMLxVYRHSuLLGqcKRWxWaxCAXhTx2G Gqy/p4vGl14CAixB+omzQO0KM807j/ZlYvlrxVvMlKg+/YibVLbOyeEdW9Qgf3GrWOxh Y3V88yCVbxpH0lMvJbskAB8XPdplT6dcjjJpYakjxqlr0+Bs2qH74iQpbvcgfrHA/oRW OEyw==
X-Gm-Message-State: APjAAAWrffL/WLRe4RXitvzwM44g+kxjy8bq0F6zTMWtPCIud/v5avDn PjLBIzhrzEmX/Z+lZHbLo18=
X-Google-Smtp-Source: APXvYqxjCjrtwgSPn4F/wpsH+OnRtBmMkhzY7le8BmmacOeC/rB4EyJaBNUYt+sBNnkN92Eo5pa6kw==
X-Received: by 2002:a17:902:b904:: with SMTP id bf4mr1360418plb.273.1551387520026; Thu, 28 Feb 2019 12:58:40 -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 p86sm47033856pfa.104.2019.02.28.12.58.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 28 Feb 2019 12:58:39 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Tom Haynes <loghyr@gmail.com>
In-Reply-To: <CADaq8jcpJAEXw_+UL-7v-EKZXeL8i-F9d2TDgiwjkHbUJpi=OQ@mail.gmail.com>
Date: Thu, 28 Feb 2019 12:58:37 -0800
Cc: NFSv4 <nfsv4@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <86A0117E-D8F0-4FE1-BA4F-656CEC9545F9@gmail.com>
References: <CADaq8je5pzF7m+4oVCNfSeeBDQ98kBwAdCN_o1hBrfDob=SBaA@mail.gmail.com> <435DA055-E09A-4E0E-8E5D-49D5554DDAAC@gmail.com> <CADaq8jcpJAEXw_+UL-7v-EKZXeL8i-F9d2TDgiwjkHbUJpi=OQ@mail.gmail.com>
To: David Noveck <davenoveck@gmail.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/5KGOsHoh2pFriCjNcWh5HCI7o4Q>
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: Thu, 28 Feb 2019 20:58:44 -0000
> On Feb 28, 2019, at 12:50 PM, David Noveck <davenoveck@gmail.com> wrote: > > > While not volunteering, I do have a git repository for this work already started - last entry was 4-5 years ago. > > > I believe it also had some of the errata applied. > > This could be helpful if there is an .xml file that could be diffed against the .xml for the existing RFC5661. Yes, there is... orbie:5661bis loghyr$ git log --oneline 56b2b56 Merge branch 'master' of github.com:loghyr/5661bis facd52c Typo 98e73e5 Update instructions for getting xml2rfc a54892e another typo fix: client vs server a1c884f typo fix: notify_device_type4 2cf1b26 Get testx working b4a0b2c Aargh, make the hurting stop... Got to work with newer xml2rfc 758d013 Typos b28e561 Merge branch 'master' of github.com:loghyr/5661bis e2402b0 Update address cee7f7a Fix up NFS4ERR_DQUOT's value 8d7292e Merge branch 'master' of github.com:loghyr/5661bis 0fc3ee5 LOCKT can expire 9f736f7 Apply Asmita's errata 798cac6 Andy proposed some clarity on name lookup security 4ff393c Merge branch 'master' of github.com:loghyr/5661bis 710d3e8 Fix spaces in Makefile c5ec1ac Fix ipr f5028a8 Pull out xml2rfc as this is not the source control for it. e578199 Marc Eshel\'s Errata 3226 91b2d4e Make idnit friendly 9078e8e Fix up xml2rfc ef1ced3 Fix some formatting 62774b0 ERRATA: layoutget serialization e364335 Small typos 8741ca6 Applied David Black's errata e797eca Fix vspace issue a8d2b06 Fix up testx e302743 Tighten up the LAYOUTCOMMIT errata 6faa82b Fix typo bc9a378 Added Implications of LAYOUTCOMMIT on file layouts 8964638 Take care of the errata 68ad4d6 More documentation on the documentation bdd32f5 Archived original rfc5661.txt and the first official copy of the bis a963a32 Start tracking changes 740a42b Fix Makefile copy error 284f6b5 Fix Makefile copy error 0b27cec Wrong Makefile 824c2c6 Create project, based off of fresh pull of RFC 5661 You can grab a copy here: git clone git@github.com:loghyr/5661bis.git Also, not sure that the XML for RFC5661 is available. One of the things I have been doing is grabbing the last XML copy of a document before the editors are done. I.e., they make straight changes to the XML before publishing. > > > And again, the reason why we never started is because it is a lot of work - both to edit and review. > > Everything we do is work, but I don't think it is as much work as you think given the work already done in the documents published so far and soon to be published. > We said that exact same thing about RFC3530bis.
- [nfsv4] Thinking about an RFC5661bis. David Noveck
- Re: [nfsv4] Thinking about an RFC5661bis. Tom Haynes
- Re: [nfsv4] Thinking about an RFC5661bis. Chuck Lever
- Re: [nfsv4] Thinking about an RFC5661bis. David Noveck
- Re: [nfsv4] Thinking about an RFC5661bis. Tom Haynes
- Re: [nfsv4] Thinking about an RFC5661bis. David Noveck
- Re: [nfsv4] Thinking about an RFC5661bis. David Noveck
- Re: [nfsv4] Thinking about an RFC5661bis. Benjamin Kaduk
- Re: [nfsv4] Thinking about an RFC5661bis. David Noveck
- Re: [nfsv4] Thinking about an RFC5661bis. Chuck Lever
- Re: [nfsv4] Thinking about an RFC5661bis. J. Bruce Fields
- Re: [nfsv4] Thinking about an RFC5661bis. David Noveck
- Re: [nfsv4] Thinking about an RFC5661bis. Tom Haynes
- Re: [nfsv4] Thinking about an RFC5661bis. Benjamin Kaduk