Re: [nfsv4] draft-ietf-nfsv4-umask
spencer shepler <spencer.shepler@gmail.com> Fri, 25 August 2017 16:49 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 2A14E132961 for <nfsv4@ietfa.amsl.com>; Fri, 25 Aug 2017 09:49:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 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, URIBL_BLOCKED=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 jtqgWpL7L61q for <nfsv4@ietfa.amsl.com>; Fri, 25 Aug 2017 09:49:02 -0700 (PDT)
Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003: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 9CD7A132C37 for <nfsv4@ietf.org>; Fri, 25 Aug 2017 09:49:02 -0700 (PDT)
Received: by mail-oi0-x233.google.com with SMTP id j144so3258340oib.1 for <nfsv4@ietf.org>; Fri, 25 Aug 2017 09:49:02 -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=pVg/eSggDLJow7sjeenhbAPTOgaSRj9TCXE/6QAXfD8=; b=tggUXPdUSijNzanpeflUY7VifRRqX9IBZfcLdFoZHkW4mMrdcE9npMweCjUJfLSTN5 4b95YMQYr+gQds91QTuOg8OyIhtx/3Jouj8SOKg7xI0+gPF0uZQjB+RJ1ulVgAVgxp41 28oLVaSxZkl8aEg0aR50W7/l826XXCKW7NCk7gIBqHdT0TW7ZgCw18DVvGZQtdbb6mMJ gAUt0VAoP5U8PEHj2cPV5b581d91/OKtDYH+uxL2ungYWWrBDr6fn0Y+pwTZn0lD+WA6 HSM0eVUwpaHwuTljy6eSDBQVfvUnP6uOQapNoGmde3gCtIr/wwYo3fvqHEXcl6M07MNn PpBQ==
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=pVg/eSggDLJow7sjeenhbAPTOgaSRj9TCXE/6QAXfD8=; b=LYP4a/BsR4wKY88Oo5vhpCvUUEZycWhdJu9aSVb/Yj3rjpYyS0o0TFC/fbKPbCBo4C dsQn9LuPoregMaOyHvCOvV0LTc4ocFhwJVZYp/s0a9UrpnPTgbwkUok23YzE5ScXdqn6 /B9Y+bzIGL0zZRg85/CZrMJ2Z7wNsAohi9REpO9BiQiGKg8kAWaPEnRObzijyjjEC/8X SpHgCAYa6HxdwvIeLxjM0LrDv8J6bMCc6SL6hnxSK76vFyAhEpi5L/s5T6wj63POr/LM NalYySFmGEGfP/BX7NGm7VXPDeqCCO5j6jyscKmdBDbPd7N49X8QQxQIYN7P7O39r7w3 USFQ==
X-Gm-Message-State: AHYfb5jUPVS72XFfqq1jmztKhZSEtn5Va2sHuW8z28CfCf7S/jIE7yFr ElBjG1w5EDixaFKKPHWE/cRI86XiZw==
X-Received: by 10.202.241.131 with SMTP id p125mr12787634oih.4.1503679741965; Fri, 25 Aug 2017 09:49:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.74.137.213 with HTTP; Fri, 25 Aug 2017 09:49:01 -0700 (PDT)
In-Reply-To: <CADaq8jdv9thBKqBViR=SEgbiUDe7c3kB_rpbB3w_F43sNFV9Yg@mail.gmail.com>
References: <CCE6471D-5252-4313-BDED-5EAA468E3FAA@primarydata.com> <20170823155536.GA10035@fieldses.org> <CAFt6Ba=Ab=TLURRJ9ULdmU_8FydkeijfoHpgzd1bBTtx6YcBHQ@mail.gmail.com> <7824C7CB-FA68-4BC8-BF92-F93B37521B91@primarydata.com> <CADaq8jd51=2fU=jzi-f17E5Yr-0ZJ461uuXC33Ff90YoCsQtDw@mail.gmail.com> <20170824083637.GA19186@lst.de> <5FBC8622-3207-4B5C-A6F6-B90FBD7492D0@primarydata.com> <20170824164508.GA21609@fieldses.org> <CADaq8jdv9thBKqBViR=SEgbiUDe7c3kB_rpbB3w_F43sNFV9Yg@mail.gmail.com>
From: spencer shepler <spencer.shepler@gmail.com>
Date: Fri, 25 Aug 2017 09:49:01 -0700
Message-ID: <CAFt6BakwE_p6Fg95GFNK_xF0Ph2TQi8S2xynA44vFBm+cYLrJA@mail.gmail.com>
To: David Noveck <davenoveck@gmail.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>, hch <hch@lst.de>, Thomas Haynes <loghyr@primarydata.com>, "nfsv4@ietf.org" <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c095ed4e03fb4055796b809"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/RR-eXFZaRi3GBm4W2aTOSa8j7h4>
Subject: Re: [nfsv4] draft-ietf-nfsv4-umask
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: Fri, 25 Aug 2017 16:49:05 -0000
Bruce, Do you agree to make changes as per Tom's original request? Spencer On Thu, Aug 24, 2017 at 10:46 AM, David Noveck <davenoveck@gmail.com> wrote: > > And I just got a "draft approved for publication" > > email yesterday so I was kinda surprised there's still time. > > It can take a while to get from approval for publication to AUTH48, which > always > takes longer than 48 hours. > > With 8178, I was pretty lucky in that in that it took only five weeks. > > 8154 took over five months. > > > Clearly I don't understand how this works. > > You are not alone. Just because there will be a delay does not mean you > are free > to make changes, even well-justified ones, at any time in that period. It > is best to > co-ordinate with the Spencers. > > On Thu, Aug 24, 2017 at 12:45 PM, J. Bruce Fields <bfields@fieldses.org> > wrote: > >> On Thu, Aug 24, 2017 at 03:46:41PM +0000, Thomas Haynes wrote: >> > >> > On Aug 24, 2017, at 1:36 AM, Christoph Hellwig <hch@lst.de<mailto: >> hch@lst.de>> wrote: >> > >> >> FYI, I agree with the request - every NFS RFC should be able to >> >> produce valid XDR. >> >> >> >> While we're at it it would be great if we had a way to merge the XDR >> >> sniplets from the various RFCs so that we can have an official >> >> combined XDR that we know is valid and can be used as starting point >> >> for implementations. >> > >> > >> > I did this earlier this week: >> > https://github.com/loghyr/nfsv42_xdr >> >> Thanks! >> >> I think Christoph was looking for something automatic, though? Like a >> script you could feed RFC URLs to and have it spit out an XDR file. >> >> I guess it could be nice, I'm just afraid it may take me a few days to >> get around to it. And I just got a "draft approved for publication" >> email yesterday so I was kinda surprised there's still time. Clearly I >> don't understand how this works. >> >> --b. >> > > > _______________________________________________ > nfsv4 mailing list > nfsv4@ietf.org > https://www.ietf.org/mailman/listinfo/nfsv4 > >
- [nfsv4] draft-ietf-nfsv4-umask Thomas Haynes
- Re: [nfsv4] draft-ietf-nfsv4-umask J. Bruce Fields
- Re: [nfsv4] draft-ietf-nfsv4-umask spencer shepler
- Re: [nfsv4] draft-ietf-nfsv4-umask Thomas Haynes
- Re: [nfsv4] draft-ietf-nfsv4-umask David Noveck
- Re: [nfsv4] draft-ietf-nfsv4-umask spencer shepler
- Re: [nfsv4] draft-ietf-nfsv4-umask Christoph Hellwig
- Re: [nfsv4] draft-ietf-nfsv4-umask David Noveck
- Re: [nfsv4] draft-ietf-nfsv4-umask Thomas Haynes
- Re: [nfsv4] draft-ietf-nfsv4-umask J. Bruce Fields
- Re: [nfsv4] draft-ietf-nfsv4-umask David Noveck
- Re: [nfsv4] draft-ietf-nfsv4-umask spencer shepler
- Re: [nfsv4] draft-ietf-nfsv4-umask J. Bruce Fields
- Re: [nfsv4] draft-ietf-nfsv4-umask spencer shepler