Re: [nfsv4] Milestone draft for working group review

spencer shepler <spencer.shepler@gmail.com> Thu, 24 August 2017 06:35 UTC

Return-Path: <spencer.shepler@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 D92FC12700F for <nfsv4@ietfa.amsl.com>; Wed, 23 Aug 2017 23:35:26 -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 14rPwRXT-ZBO for <nfsv4@ietfa.amsl.com>; Wed, 23 Aug 2017 23:35:24 -0700 (PDT)
Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::22b]) (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 A10D5126E64 for <nfsv4@ietf.org>; Wed, 23 Aug 2017 23:35:24 -0700 (PDT)
Received: by mail-oi0-x22b.google.com with SMTP id k77so8609566oib.0 for <nfsv4@ietf.org>; Wed, 23 Aug 2017 23:35:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=KQX4NVP+ito9trzb0GnP+m45NbarRk5WxuHZe8NKLzw=; b=HPreBHONnxNmuIVdtFVpgHyMpKChGe7Y/UMyISoZJlEzB20YBE5Q2WtP5AdBREMVfa jnGclDgLg24vDkmIuSLkF5yMTS8jG0MMKRbHu/Z6nWsX+oMLlR91cMJBiv4NRqr5i0sZ 0U8/dipOiqAr+zcoMzjM+rnL3mIun7cwhj2CodKSPLJs+n8fCloDc23plp8iy27tLarA 63jR/swEz62QjKHH0np9+tbtCgwy7sOctfk7gKoMHYjoAycVPPVGYbgI0kFBg+c9KV6G RqksJVSnBNW1GdEy45P0huve3S8W2IOnEIs144vBumtspcUwU3x0MQU0w6LZW1eYpK4d Z+sw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=KQX4NVP+ito9trzb0GnP+m45NbarRk5WxuHZe8NKLzw=; b=HVdJj+YQGl8Wn9tHcI4hv2C5ohf1Lt3v71W4DoYvBqlGnddEmHgFi144Gict0afZ2S NdVO9NhQ3//w8O8X0m27Zce1/XKPYzXx6eYpbTqZdAuzVTmAuIPRiehZMjEtS98/VtRV AkaZej/rqg+ytw/2Wu8dQcbtpKfCobYLmdFFdBeYZZ7qlsayGqVeOYnVkkXpgsuzdzsy hjqiyeN++aRne/d4WG2P8bop6uLDvkmpRGcnGGUTFZSY6htC7KjhwQftje/VYHs09Wi/ 0fBYDl2B64NwraJXpW1vwZiRno9jhFFZx2iivyCu4uGIEnDKHopyCj1tjbLzDv55k1DW SR5w==
X-Gm-Message-State: AHYfb5jv3srxg7g5wuyMavne1kpDa768yCyTQqBHrHL6wOb0PPPOHU10 a5xoR6lymA7v7Kawk/lgVrco2vEuMw==
X-Received: by 10.202.241.131 with SMTP id p125mr5999189oih.4.1503556524078; Wed, 23 Aug 2017 23:35:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.74.137.213 with HTTP; Wed, 23 Aug 2017 23:35:23 -0700 (PDT)
In-Reply-To: <8A66FD34-C6D5-47B2-A300-D99DD021F2D7@oracle.com>
References: <CADaq8jcAn_VAZCO=B_VbAZGoOK2LYB9n3FEr4zwnwC1MWL2yjQ@mail.gmail.com> <3BFF8A11-6052-4172-8635-D735D1D309A3@oracle.com> <CADaq8jeCv89mCo2=-F5mFED4xJ_Dfoz88ythgw8P_gmQh=Sm-w@mail.gmail.com> <8A66FD34-C6D5-47B2-A300-D99DD021F2D7@oracle.com>
From: spencer shepler <spencer.shepler@gmail.com>
Date: Wed, 23 Aug 2017 23:35:23 -0700
Message-ID: <CAFt6Bakj+TH4Lp445kSkckJMA1tQWe=7Frj4Q4DzNfZAQ12KgA@mail.gmail.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: David Noveck <davenoveck@gmail.com>, "nfsv4@ietf.org" <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c095ed4847db705577a0888"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/9U8qp-kGDXUcJuUFzdjatSRrMMM>
Subject: Re: [nfsv4] Milestone draft for working group review
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: Thu, 24 Aug 2017 06:35:27 -0000

On Mon, Aug 21, 2017 at 9:08 AM, Chuck Lever <chuck.lever@oracle.com> wrote:

> Hi Dave-
>
> > On Aug 21, 2017, at 11:45 AM, David Noveck <davenoveck@gmail.com> wrote:
> >
> > > I have only very minor quibbles with any of this content, none worth
> > > bringing up.
> >
> > If they are not brought up, then the draft I send to the chairs and ads
> > cannot include them.  Please make sure that you make me aware of
> > issues that need to be addressed, even if they might seem minor right
> > now.
>
> Perhaps I should have said "No objections."
>
>
> > > I suggested privately, and would like to bring up on the list, that
> > > it would also be helpful to have a repository for our "stretch goals"
> > > and "almost ready" or "wacky" ideas (thanks Bill Baker for that term).
> >
> > Those are three different categories.  What I'm thinking about is
> > a list of "potential goals", which could include things that might
> > become goals if there were a person to take on the work and provide
> > a target date.
>
> Thanks, looking forward to seeing it!
>
>
> > It could also include things that are not quite well-defined
> > enough for us to be sure about what document might really be done,
> > and ideas of various degrees of "wackiness", although we will try to
> > avoid things that the working group thinks are not worth considering.
>
> Our usual criterion for considering "wacky" ideas is a personal
> I-D. I'm OK with placing these ideas in a "requires I-D"
> category.
>
>
> > > It could help create an institutional memory, along with the mailing
> > > list and IETF meeting notes (hint hint). We obviously have some worthy
> > > ideas, as noted by Tom's "Next steps" presentation during IETF 99,
> > > even if they aren't completely formed.
> >
> > I will be producing that list, but it will take a while.  Maybe by the
> end of
> > September.
> >
> > I have looked at Tom's presentation and there are a number of items that
> > could be potential goals, although none is really "wacky".  In some of
> the
> > cases, the presentation isn't clear about what specific things the
> working group
> > might do to further these ideas, but I can consult with Tom and Trond to
> get the
> > necessary clarity.
>
> I'd like to see these items and any clarifications discussed
> on-list first, or (preferably) in I-D form. Perhaps that's a
> high bar, but the WG deserves a clear problem statement and
> explanation of a proposed solution, so that it's members can
> evaluate new ideas fairly.
>
>
> > > Can you post subsequent revisions of the Charter and milestone list
> > > only in ASCII text? That also makes it possible to simply hit "Reply"
> > > and respond narrowly to individual parts of the text. Thanks!
> >
> > I'll do that, since the IETF seems to be stuck in the last century.
> There
> > might somewhere be a plan to bring the IETF into the twenty-first
> century,
> > but, from what I've seen, 2099 might be too aggressive a target date :-(.
>
> It's not just the IETF.
>
> There are some on the list who cannot open a .pptx document.
> There are some who refuse to, out of principal. There are
> some who are behind corporate firewalls that discard e-mail
> attachments as a policy, or that place size restrictions on
> in-bound e-mail.
>
> My own interest is archival, but I think we should strive for
> inclusiveness.
>

Dave,

Please go ahead and post the current draft charter and milestones to the WG
alias in text form so that we are inclusive as Chuck suggests.

Spencer