IETF Logo Mail Archive

Re: [nfsv4] Agenda for nfsv4 working group meeting Prague July 20

David Noveck <davenoveck@gmail.com> Mon, 10 July 2017 12:53 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 43F10127B60 for <nfsv4@ietfa.amsl.com>; Mon, 10 Jul 2017 05:53:25 -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 zLyQaSne-rhS for <nfsv4@ietfa.amsl.com>; Mon, 10 Jul 2017 05:53:23 -0700 (PDT)
Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (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 8CB94124C27 for <nfsv4@ietf.org>; Mon, 10 Jul 2017 05:53:23 -0700 (PDT)
Received: by mail-it0-x231.google.com with SMTP id m84so37349642ita.0 for <nfsv4@ietf.org>; Mon, 10 Jul 2017 05:53:23 -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=/7HS82dDUou+5hBrb6542EzPQJArX1ybehT4px31S6A=; b=rC1BeiY4VMlFSkBGAR9gFfheY8hy3XzlgUJLYCdXOLSXUz9kJbf6g2pOq1PIt/WeC8 0Ilf/56G2fMo2bseqQlvSPMcxyNk0tiE3fO82bbzg+QcA5v+NBIY59Gy6322vzQ+6A4y 9SoqHwWluUM7EhQbPihzdlIz+l+qb+oa0MF+1pGywBWqRkyM9L94/9TsS0O1FLzpn37S sxw3Vzt2HX5ENFxWn3hkJ8mcTkWvBCcmG2ZKXeouxwsUYwHfhew/cNf9NHCVgr6S0vZQ BIXjNZvfi7uVjs0ZFpoXgYiq/UX8Xw2r9J6Uui+t1ZDsCxRvbksBRGyxmdINCK3+p+50 phRg==
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=/7HS82dDUou+5hBrb6542EzPQJArX1ybehT4px31S6A=; b=ZSzWmCsEEOXfIi0tlPyqEuiM0P/MR1Y8ClwV3X1liQA482/AqcseKrwvnaN5uhp6xr ZordANqTXsRxnygRsC1CawzwSofcg3pgNsEsa4B5AU9w+qlrs+MdtHTBj+FIP/bra5SR 3fxsNG98mhbcVjLLgoNKJ+vd9iwYHSeNLcfEgngzc1ikgYO43wKUyZBeUEocZH96HIcK JmxcGRH/E/GrP3Q5E05zuQYPdOLOOOSPYG0S+mApfAqddeOIIeFu1UwffSmYCQHdVZgK DLcvbK0yE9RNDeK5BnTowioDjLU21ucsI4+viA/6koomQ1w9XgVIZX1m2aysF4QPj0zI AYTA==
X-Gm-Message-State: AIVw1134xZ3SOPCjUsSwysecsbYtjPR9Xog9LGwOtJczv0N9BuR4BGIi MXTf1flo8+pn9S1xPj0W++SLOwhaXQ==
X-Received: by 10.107.18.19 with SMTP id a19mr2920727ioj.93.1499691202693; Mon, 10 Jul 2017 05:53:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.57.86 with HTTP; Mon, 10 Jul 2017 05:53:22 -0700 (PDT)
In-Reply-To: <CAN0E48cY+CSj+b8DtCW9Fiz3sMq4vixdLSkCMcH11YKJmSYpxw@mail.gmail.com>
References: <CAN0E48cY+CSj+b8DtCW9Fiz3sMq4vixdLSkCMcH11YKJmSYpxw@mail.gmail.com>
From: David Noveck <davenoveck@gmail.com>
Date: Mon, 10 Jul 2017 08:53:22 -0400
Message-ID: <CADaq8jfEg2UYH1vVXjtc4cqawPofUdwc+T5X5w114UNS+jZW1g@mail.gmail.com>
To: Brian Pawlowski <beepy@purestorage.com>
Cc: "nfsv4@ietf.org" <nfsv4@ietf.org>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="001a113ee86e68e7230553f6113d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/oqphUbAf-iHp0kq3_WtBD3I5fY0>
Subject: Re: [nfsv4] Agenda for nfsv4 working group meeting Prague July 20
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: Mon, 10 Jul 2017 12:53:25 -0000

I'll also be in Prague Sunday.  I have put together a short presentation
regarding the re-charter discussion.  Lately I've been focusing on SECDIR's
comments about the existing security considerations section in RFC7530.
Let's get together some time (how about Monday morning?) and co-ordinate
our presentations to avoid overlap.

So far, with regard to the re-charter I've kept the response to these
security issues pretty minimal.  It is limited to us saying that, as part
of maintenance we will try to meet IESG expectations in this regard, while
allowing us to do extensions "to meet new security challenges".

My worry is that this might not be enough and that the working needs to
consider something more substantial.  I don't think we can arrive at a new
direction for NFSv4 security at IETF99 but at least we need to raise the
issue of a possible change now to get some idea of what might be possible.
It would help if we got more specifics about what SECDIR is looking for.
If we could set up some meetings with SECDIR before Thursday, we would have
a better framework for the working group meeting.  Alternatively, it would
help to have some SECDIR people attend our meeting and take part in the
discussion.

On Mon, Jul 10, 2017 at 5:40 AM, Brian Pawlowski <beepy@purestorage.com>
wrote:

> Thanks Dave N. for driving discussion.
>
> I will be posting this to IETF meeting site. Please note that the agenda
> includes bashing to make adjustments at meeting.
>
> I will be in Prague on Sunday before hand. Would like to curl up with
> people to go over recharter discussion before Thursday to make sure I have
> a good strawman. Again Dave N. did  great job of teeing this up (look back
> on e-mail thread if you missed this).
>
> beepy
> in Munich
>
>
>
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4
>
>

v2.23.0 | Report a Bug | By Email