Return-Path: 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 CF2FD126DD9 for ; Fri, 25 Aug 2017 10:27:37 -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 smUtLBh-GXGQ for ; Fri, 25 Aug 2017 10:27:35 -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 1AC9D126C7A for ; Fri, 25 Aug 2017 10:27:35 -0700 (PDT) Received: by mail-oi0-x233.google.com with SMTP id k77so3931667oib.2 for ; Fri, 25 Aug 2017 10:27:35 -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=YwfAHLHi1Sm0b/fKHrF6tW6Sswn8mE0CLxWgzWoXakk=; b=XNTH2n7jrZDLchKVb6XSTyJJaIRQkyCdEZa1842Afbv+ph/Wn62o1iZW5oa8ljyYHQ RhPvos7t67VSAHpDYn+nZxtyfIUe83w3BvnS7lBMJJPSX45fjqKIDNvyMgFPLaSAXzYT +RUxKX9QsP8WPRnqV2qCykUW2Wp/rC+tQx9FHNgePaPZ48i7YzLTpEmCrttMbBreE7E0 30/snTrvrfaSVwrBhl3S+zVn9+Lc0k7gr7AdDrcTJvytdtJc+8TWclMvrOUo/Fo6tdD2 PxOMLERYsm7B8tL3fQuWsFkvyM4S0jLwEW6O+hMQz0gP9bz0ySHoI8j5YewcCpJPi4fs Qh1A== 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=YwfAHLHi1Sm0b/fKHrF6tW6Sswn8mE0CLxWgzWoXakk=; b=uiiIXo4Y7Kb/BARU2CR/QCVRAT6k2sgm9a87BiRritygbDHKACWJO7llzgEiv8od49 uN6+n7YC2pV/9C8OMlBLgkuBwsKCgXhuueutNOJ8BKIt774CI9gyogFMtj8qyBpGk4nJ Dzza6b5SpSfnVtQhS/xPXLGJN9+nzjGWP4E1vvy9SzzLotkIVhUqqePErSCU7Jl7lwJC Z3j0xI531FC2nmVQRRL8Ob/FmPpkvnc5xRrXBpPiJFBwjdkUQ9HZgl1SjmIwPzFoUaQC ZtxygEVSoyywj3tZFx7e9jD/Mp9441ZkzZLjWhM/4UOzcy10Yb18+xPZ7bzSUpaGETNJ DnrQ== X-Gm-Message-State: AHYfb5iSih0wk6g0j9v85sNUSlmpKqHrBPJPYnpfGo2JqokMzvTbSLvp KN4C0pvxDtlkFtnaVVbW7koQrWNK6A== X-Received: by 10.202.214.141 with SMTP id n135mr14212389oig.214.1503682054365; Fri, 25 Aug 2017 10:27:34 -0700 (PDT) MIME-Version: 1.0 Received: by 10.74.137.213 with HTTP; Fri, 25 Aug 2017 10:27:33 -0700 (PDT) In-Reply-To: <20170825172522.GB28124@fieldses.org> References: <20170823155536.GA10035@fieldses.org> <7824C7CB-FA68-4BC8-BF92-F93B37521B91@primarydata.com> <20170824083637.GA19186@lst.de> <5FBC8622-3207-4B5C-A6F6-B90FBD7492D0@primarydata.com> <20170824164508.GA21609@fieldses.org> <20170825172522.GB28124@fieldses.org> From: spencer shepler Date: Fri, 25 Aug 2017 10:27:33 -0700 Message-ID: To: "J. Bruce Fields" Cc: David Noveck , hch , Thomas Haynes , "nfsv4@ietf.org" Content-Type: multipart/alternative; boundary="001a113b0282b4aa02055797428a" Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Aug 2017 17:27:38 -0000 --001a113b0282b4aa02055797428a Content-Type: text/plain; charset="UTF-8" Thanks for agreeing to the change. The timeline we can work out. Spencer On Fri, Aug 25, 2017 at 10:25 AM, J. Bruce Fields wrote: > On Fri, Aug 25, 2017 at 09:49:01AM -0700, spencer shepler wrote: > > Bruce, > > > > Do you agree to make changes as per Tom's original request? > > I can do it, it might just take a week or two to get to it. > > (Or Tom can send a patch--source is in > git://linux-nfs.org/~bfields/NFSv4-umask.git.) > > --b. > > > > > Spencer > > > > On Thu, Aug 24, 2017 at 10:46 AM, David Noveck > 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>> 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 > > > > > > > --001a113b0282b4aa02055797428a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Thanks for agreeing to the change.=C2= =A0 The timeline we can work out.

Spencer

On Fri, Aug 25= , 2017 at 10:25 AM, J. Bruce Fields <bfields@fieldses.org> wrote:
On Fri, Aug 25, 2017 at 09= :49:01AM -0700, spencer shepler wrote:
> Bruce,
>
> Do you agree to make changes as per Tom's original request?

I can do it, it might just take a week or two to get to it.

(Or Tom can send a patch--source is in
git://linux-nfs.org/~bfields/NFSv4-umask.git.)=

--b.

>
> 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"<= br> > > > email yesterday so I was kinda surprised there's still t= ime.
> >
> > It can take a while to get from approval for publication to AUTH4= 8, which
> > always
> > takes longer than 48 hours.
> >
> > With 8178, I was pretty lucky in that in that it took only five w= eeks.
> >
> > 8154 took over five months.
> >
> > > Clearly I don't understand how this works.
> >
> > You are not alone.=C2=A0 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 pe= riod.=C2=A0 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 a= n official
> >> >> combined XDR that we know is valid and can be used a= s 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= ?=C2=A0 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.=C2=A0 And I just got a "draft approved= for publication"
> >> email yesterday so I was kinda surprised there's still ti= me.=C2=A0 Clearly I
> >> don't understand how this works.
> >>
> >> --b.
> >>
> >
> >
> > _______________________________________________
> > nfsv4 mailing list
> > nfsv4@ietf.org
> > https://www.ietf.org/mailman/listinfo/nfsv= 4
> >
> >

--001a113b0282b4aa02055797428a--