IETF Logo Mail Archive

Re: [nfsv4] draft-ietf-nfsv4-umask

David Noveck <davenoveck@gmail.com> Thu, 24 August 2017 10:32 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 5FA12132742 for <nfsv4@ietfa.amsl.com>; Thu, 24 Aug 2017 03:32:12 -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 NGw8YuXcgUaR for <nfsv4@ietfa.amsl.com>; Thu, 24 Aug 2017 03:32:10 -0700 (PDT)
Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (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 4330E1321A1 for <nfsv4@ietf.org>; Thu, 24 Aug 2017 03:32:10 -0700 (PDT)
Received: by mail-io0-x232.google.com with SMTP id r14so752951iod.1 for <nfsv4@ietf.org>; Thu, 24 Aug 2017 03:32:10 -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=3qjpHPGHE9OHyrgzgdlroXCaywOAyfkT87vSmAxBUkA=; b=WeyynXujMhSbsz8W4/lIZ9CUA9J6dLEYN/XPHDZT3U9XeYqSZYNjxEsOFfbMpIpFCh nEi1cMCkeC6+uh3+LWii6qAAY7WSheM3XnTY/UFvUi+WXJE579bm4Eqwn7ANSGFoOEKj BJzFFOh2UEV2xXF0Vd1OItoRG1BtCRV8MHzp9f5zevHpllswdTV2G5ZLInuf6SZh6tAz P7gtDiyAs2vfzv3hqkc4WbygMC10B0Wo30cV8yqkOgDjRcqLWUr9g0y6qPpik+K0Woxu HV1G0SEJ3X58NRD0emfQ4D/X2KT+18deeLpIEdvGXpWOY7SK5i17dClG6xFPSnqnzFGL rROA==
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=3qjpHPGHE9OHyrgzgdlroXCaywOAyfkT87vSmAxBUkA=; b=DiiOMoIo/re9QuGtu8kpTo12SVwVfWZXqRtszO0djT8AbSDxgn+dZWvj9auB4tRHVL SgFeD6Nn4dU83CaYV6YhgEvvrnhDxRiOtLpsa5KoXG2CV3A2NkuyD7YogNkOd6AbqSS+ 0JMQKcb6DzJyJNVaIDGuLUcb0OhesXwMOBDenj3qVEtyhcdu9uq4SemIlFh2KSz+XYFF 0KuARc4qiueOxizdW8HipJgKkzLfz58pZCi+KAeBoftz9QRvQreX2stYU42zEj7quklD F25ADKJW3o8gtdqsbT1f5mQQp94Ww9UKQyg0J3xUSHE9dDDNH6Mhce86D/ziHxYPJvYf QCEQ==
X-Gm-Message-State: AHYfb5hgx+O7IJHpNhD+WktwN+oyq88xaOHkkBgpmrCzpiYiJ2Q/DyPF NH9A1CWf9WAMhh8NRsrd5Wht9V5PRA==
X-Received: by 10.107.162.3 with SMTP id l3mr4745494ioe.348.1503570729444; Thu, 24 Aug 2017 03:32:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.10.213 with HTTP; Thu, 24 Aug 2017 03:32:08 -0700 (PDT)
Received: by 10.107.10.213 with HTTP; Thu, 24 Aug 2017 03:32:08 -0700 (PDT)
In-Reply-To: <20170824083637.GA19186@lst.de>
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>
From: David Noveck <davenoveck@gmail.com>
Date: Thu, 24 Aug 2017 06:32:08 -0400
Message-ID: <CADaq8jce=0GdZt4AngHCFFBkhrE=0B2QPHxALfSWzdZD6g0=Ew@mail.gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: "J. Bruce Fields" <bfields@fieldses.org>, nfsv4@ietf.org, Thomas Haynes <loghyr@primarydata.com>
Content-Type: multipart/alternative; boundary="001a1140eff4392dfa05577d5720"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/Lx4bKtNgeskgLN9zPFqjwaCJJ7w>
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: Thu, 24 Aug 2017 10:32:12 -0000

As far as the idea of being able to produce a consolidated XDR,  I remember
that I once proposed a series of conventions to allow a script to produce
an XDR from an existing XDR and an extension document.  I'll try to dig up
that email and turn it into a short I-D.

On Aug 24, 2017 4: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.
>

v2.23.0 | Report a Bug | By Email