Re: [secdir] [nfsv4] SECDIR Review of draft-ietf-nfsv4-umask-03

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Wed, 07 June 2017 07:08 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47DA912EA5A; Wed, 7 Jun 2017 00:08:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, 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 5bSM3SqJLbbq; Wed, 7 Jun 2017 00:08:47 -0700 (PDT)
Received: from mail-yb0-x229.google.com (mail-yb0-x229.google.com [IPv6:2607:f8b0:4002:c09::229]) (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 BAE421201FA; Wed, 7 Jun 2017 00:08:47 -0700 (PDT)
Received: by mail-yb0-x229.google.com with SMTP id 202so941367ybd.0; Wed, 07 Jun 2017 00:08:47 -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=98TiONn++xsHp86j0MNsM0RhkjRerMShMU8N3T1+AEk=; b=p4ESZIXBsivoSOWta1bfw0/28b9SD/XOZ6i+2vfchyvxK0q43Dlg1d+XP6eAVSjc2a 4/8IBi5L2CozAmkSGO7ah4GTp6+gsY7V9mcgf/V6vmLhjHch+opAM4qqu40fKrvzbRzr veJZXTe9aty2auYabZ5Im4z+ujZIMxjrqZqQU+fWJKSSpaIVpIgd7b2iyDFWtS/bhPPM ogk35oax0CedOu0a6L/41oY6n0VP9co9AnkjRLcGLITVlXdNMPfVXzRaW2unIrKoYxfZ 8ExenrmPkstpSqPYOFdO+i9tplQpocw9iXahQBWPJ4PVLLJSDwWaehv55WyLlP4KfJUJ 4KMg==
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=98TiONn++xsHp86j0MNsM0RhkjRerMShMU8N3T1+AEk=; b=X7HITvYCkQpmS9adCxURR8GhAyfQprUWRZIczVB2rafV1SGF/BYInAhzV+sp8QpeE9 MSVTui5Mwi//3e1V4cc3ycMh+ddfL8Ue5AFYimARIb0P42u4WlVdJDgVWYnM05o4TG6g 3F8DKtvsJRc/PS8uNtJUGTQuYmc58MPzDtAgN5ejWXynHwXDKJdXoQttNoyVTIuaE+zq /7qNlVNNYJYLEVmR4d0jn64nioLzmPwmhk2V7YqKMYFxZZpPELexJMxXmxK9wWMYMhM1 nd/6Heh7LrHnyJOyPhfSeMjFSp/+hQ83jPTCJM/kzuBPF8RbnCGBX9UouZc3Al0Kiyz4 pdaw==
X-Gm-Message-State: AODbwcA5H//QO5Mb25l2x8Q+9wH2Zm6KVtTUs4E1pGA1SF7H87gTVJG4 3+wUUWj9rlzJH66wwNX9foWeSDGhZw==
X-Received: by 10.37.204.75 with SMTP id l72mr5486620ybf.176.1496819327003; Wed, 07 Jun 2017 00:08:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.195.194 with HTTP; Wed, 7 Jun 2017 00:08:46 -0700 (PDT)
In-Reply-To: <20170606160032.GC3432@localhost>
References: <CAMm+Lwh+E+BsATQmmX6ccJou-sz1XNtFHxQZikohYCeT0qkfdQ@mail.gmail.com> <CAKKJt-fsJ1UinNiW2LitxVQT4M1YqnFF+1cygU132=bQNgiUnA@mail.gmail.com> <CADaq8jd+6gN2H0QWC+dM-e3pb1gUJKLE7=8PPpprGGKBQZhueg@mail.gmail.com> <CACsn0cnd0L2o2Db6OA1Uvp-C+geA+Ju-7E8Yo=OKS1V3P4G8sA@mail.gmail.com> <20170605165254.GE2903@localhost> <CADaq8jcOD8eodG6-jguvy3xytMkAwBhmWUTxF-eXhjxZGymXGA@mail.gmail.com> <20170606160032.GC3432@localhost>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 07 Jun 2017 02:08:46 -0500
Message-ID: <CAKKJt-f4-+VzZD++bKS1-+ZyWzByuTE9tjncwnV_2Mhj4JucoA@mail.gmail.com>
To: Nico Williams <nico@cryptonector.com>
Cc: David Noveck <davenoveck@gmail.com>, Watson Ladd <watsonbladd@gmail.com>, "secdir@ietf.org" <secdir@ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>, NFSv4 <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c0ef74247737105515968be"
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/-6hch2Quyi-lyhGdUXhEX0fHpRE>
Subject: Re: [secdir] [nfsv4] SECDIR Review of draft-ietf-nfsv4-umask-03
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jun 2017 07:08:49 -0000

Hi, David,

Speaking as the responsible AD ...

On Tue, Jun 6, 2017 at 11:00 AM, Nico Williams <nico@cryptonector.com>
wrote:

> On Tue, Jun 06, 2017 at 11:21:13AM -0400, David Noveck wrote:
> > > A more complete analysis of RPCSEC_GSS should really not be
> > > done in the context of this I-D.
> >
> > I agree that it should not, but it is not clear exactly what is being
> > asked for to get this document into the RFC editing process.  Unlike
>
> It's a secdir review.  It plays no official part in the publication
> process.  It is merely a review meant to aid the IESG.
>
> > xattrs, this document actually has been approved.  The state is listed
> > as "Approved-announcement to be sent::Point Raised - writeup needed"
> > so we know it has been approved but are unclear about why this has not
> > been announced, what exactly the point raised might be and how the
> > issue/point is to be resolved.
>
> The secdir review may simply have been too late.  But it's still worth
> responding to, which I have.
>
> I took up this sub-thread because I'm familiar enough with the subject
> so I can, and because I think Phillip and Watson deserve getting answers
> on this even if there's no procedural need to provide them.
>
> > I think the authors are entitled to a clearer treatment of these matters.
>
> So are non-NFSv4 WG participants in this thread.  It's not every day you
> get a free analysis of your protocol by folks like Watson.  Rejoice.


 The document is approved. We now approve documents with no Discuss ballot
positions, but can still make changes to resolve comments that arise during
IESG Evaluation, if that's appropriate.

I read Phillip's SECDIR review with interest. It does not seem to apply to
this draft, any more than to the rest of NFSv4, so I wouldn't hold up this
draft to pursue the issues Phillip raised.

Those issues do seem to be a useful input to NFSv4, as the working group
considers a charter update (after finishing quite a lot of work, and thanks
to you all for that).

Does that help?

Spencer (D)