[nfsv4] Working group recharter
David Noveck <davenoveck@gmail.com> Sun, 23 July 2017 11:23 UTC
Return-Path: <davenoveck@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 AF6CE127ABE for <nfsv4@ietfa.amsl.com>; Sun, 23 Jul 2017 04:23:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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_LOW=-0.7, 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 a9coca678TaE for <nfsv4@ietfa.amsl.com>; Sun, 23 Jul 2017 04:23:43 -0700 (PDT)
Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (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 950E4127444 for <nfsv4@ietf.org>; Sun, 23 Jul 2017 04:23:43 -0700 (PDT)
Received: by mail-io0-x233.google.com with SMTP id g13so34571711ioj.5 for <nfsv4@ietf.org>; Sun, 23 Jul 2017 04:23:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=D1azCoZeU3G9xt572yA5C/Nlv/4o13pyL2lUEUHrHLM=; b=sRCKWEI9ZnR9iZ/dFw/G3IVRXX4iFd6kpvjygWH8dDEg5Rlu3jRKL6V9m6NlMg5QBo qkxP3Q0TidCIfpM3GFcP4JZx8aNDt/cLqE8KEy02nGl1HrlO7a9UtQnOduVdQbalhCZE 9sq+JXKOfUSG2CRoO8NR/9NdyZCrnpKRAxnc8/IFwsk/KvtuIKcJ2Kw4qaIxX4J89o22 t5lUPbmz7oXOL8LORmdiRIvWx16R0hXpKXPwQq5DRNAskyu+e/8df6419QuDhS4nCbAt RMxuZ6QMYDMNah4mH50sO85CfgwDQkGmbuDcBQeIQzbVDfH9/ZS4AHyhnB94b55gnfS2 cOaQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=D1azCoZeU3G9xt572yA5C/Nlv/4o13pyL2lUEUHrHLM=; b=UUSHpz1JEKLA1O6VANLI5R5nduzrWKcqhve2Qr5Gr+MfDEjJMlsAnaGfKkDSILzvxC FMJeXPscmepvToNrsHcIkg+a6IDKNWQ4DujUgIpQQyBkW4rkOFqPAQKCBW+qablNEV5i IXbrBr02p6fZwh7GTO3Y0PTAuS2YKeHnMsAVa9mRVSdJdCAreOumJvLBKbJt1bISjyr0 8U3OrGuVZXVYYrfCJO9Xt03Cg7tR6LbtuvbMxu84DovCbZ8mqUn3+MQWgZb5d49QZL5z QBr18C2ESK2oXQKi9g7/GlldXbQSwfOWQ1MMbsVGowsWugAYycOOjklKpx8ldh90kGNn 7Eug==
X-Gm-Message-State: AIVw1130haKoMqFC2BvOw3WtlJSB2tZIN/ERLtA6x8Vvb3YO9WnxEobg 8CwnF3lQwOVKltbnaAblUOldNPpWEA==
X-Received: by 10.107.164.130 with SMTP id d2mr13740447ioj.14.1500809022609; Sun, 23 Jul 2017 04:23:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.142.72 with HTTP; Sun, 23 Jul 2017 04:23:41 -0700 (PDT)
From: David Noveck <davenoveck@gmail.com>
Date: Sun, 23 Jul 2017 07:23:41 -0400
Message-ID: <CADaq8jfget+Yt05KL8CrPDMN6f8Bv+UVQG_N0d=jPNsu=DAKdA@mail.gmail.com>
To: "nfsv4@ietf.org" <nfsv4@ietf.org>
Content-Type: multipart/mixed; boundary="001a1141bc56ab60650554fa546f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/hw5B-mk12mjXpnJK30cJKjJklWI>
Subject: [nfsv4] Working group recharter
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 23 Jul 2017 11:23:46 -0000
We discussed this at the working group meeting at IETF99. In the meeting materials you can find: - Ietf99CharterDiscuss which are the slides I presented about the effort. - Ietf99CharterMateials which had the latest draft charter and milestone proposals, both converted to a powerpoint form. With regard to the draft charter there were only very minor changes made, which are reflected in the attached file NearFinalCharterDraft. I'd like people to look at the current draft and send mail to the list about any issues they see. Even though there was broad agreement at the working group meeting, I don't think we can consider this draft as final yet. I think people who were not able to be in Prague or to participate remotely given the meeting time (starting at 00:30 Pacific and 03:30 Eastern) should have the opportunity to comment before we go forward on a re-charter effort. I think a week is a reasonable time so please offer any comments by 7/30. In my presentation to the working group, I stressed that we were looking for agreement on the basic message and that minor corrections could wait. Because we seem to have reached that basic agreement, I'd like everyone think about any worthwhile correction they might offer, whether they attended the working group meeting or not. With regard to the milestones, things are a little further off. There is only one milestone in the current draft. While there is no minimum number, we would like to have more. David Black suggested that one-milestone-per-working-document was a good model, which makes sense. The only problem is that if you look at our current list of working group documents, we seems to have a temporary shortage. If you look at our current seven working group documents: - Three are past WGLC and waiting for various stages of IESG handling, which leaves them out as milestone candidates. Creating milestones fr these would essentially be giving the IESG milestones and they might not like that. The drafts in question are rfc5667bis, xattrs, and umask. - Two drafts, flex-file and layout-types., are now in a WGLC scheduled to end 8/11. which makes milestones for these kind of pointless. - The remaining draft, migration issues is the one that has an associated milestone. I expect that, in the next several weeks we will be considering adding some working group documents. I'd like to ask those who will be making proposals in this regard to give some thought to likely milestones and let me know so I can update the draft milestones. It's important to note that Spencer D has indicated that such milestones will not be set in stone. We are looking for people's best estimates, which can be revised if unanticipated issues arise.
- [nfsv4] Working group recharter David Noveck
- Re: [nfsv4] Working group recharter Mike Kupfer
- Re: [nfsv4] Working group recharter David Noveck
- Re: [nfsv4] Working group recharter Chuck Lever
- Re: [nfsv4] Working group recharter David Noveck