IETF Logo Mail Archive

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

David Noveck <davenoveck@gmail.com> Mon, 10 July 2017 15:10 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 906D61317AE for <nfsv4@ietfa.amsl.com>; Mon, 10 Jul 2017 08:10:59 -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 eDW7lHuYLI2H for <nfsv4@ietfa.amsl.com>; Mon, 10 Jul 2017 08:10:56 -0700 (PDT)
Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (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 7E24F127868 for <nfsv4@ietf.org>; Mon, 10 Jul 2017 08:10:56 -0700 (PDT)
Received: by mail-it0-x22c.google.com with SMTP id m68so36164384ith.1 for <nfsv4@ietf.org>; Mon, 10 Jul 2017 08:10:56 -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=g3NMEo+FRI8UukHEL1gs0RZTrRtN5NFCLyYhFR7JSfc=; b=NkpP8tw/3xxztBWscnFqC7G1tleNiW5+nHpWVl0B24WYBTAYBc69P0Nh7N8hMYjkzH uUDiI+sz99SAtGXILv1gLMSR7Hapo2+c9DvXYvrEaNLZkF5X3hDM7zS2CAvc/sWl4FUz C5tJO529VzIzMs7Ns1GbkWJrQ1XYOJZVaCsniP7GV1JQ3vTPUI5dwHwnlSkBT53f8P/9 ExuMcDoJ47J3X3z3NAzWMzCBGVqnUlnPkvWqLYVAntON1syx1dmOtvBo+F/L97rv4EGX tegZnjKJKMgxhTpqILY1OlDtVNbWqJQ1FLogQIjhAS99w3nM1f/y3gAfbLsFZmLNiqw3 NjFw==
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=g3NMEo+FRI8UukHEL1gs0RZTrRtN5NFCLyYhFR7JSfc=; b=QkP2kEBlrlqvwQEe8zrV/wrEQwbBtn/BhZkOaFB9+omv1NWGOBJuFGTYxwzTFYf00h PprNrk3SGcOs0EJgFTeWhdKHZJtBd5TO7C3Zk9JeJ769spCX+bp3uFwnS6sO1ArkO9lr Gtq5i81Jg5/v5y1R9aWUvfA1YeZAtVmfW45LxcgvksmQ/cxZeoox268d4UfvCOSS/yzh LZ3fx9X0WoL7Q1npqK9yamPye7v7yDs7xvrfGLZljCoJK55ie7IyqpKoSrWXEXnHEBvw RjOx+FpNE4uxt3FwSfp7JgpnR8hB/4mXISooOd7zOegfMUyI7aScmUbLHMlNknPWUfEK tyRA==
X-Gm-Message-State: AIVw111cBR2yhyJ6joKjdpxs+X1KNlt/tc9Edt5hYmSGNIYvAiZ09M+Q e+Z7oBLBQKSTSRe5Jtdjlnlj6M1tXg==
X-Received: by 10.36.208.139 with SMTP id m133mr12048819itg.48.1499699455848; Mon, 10 Jul 2017 08:10:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.57.86 with HTTP; Mon, 10 Jul 2017 08:10:55 -0700 (PDT)
In-Reply-To: <CAN0E48dmkuhbXKp=U7GR-sw3RhvNvsTH4TbFCY-qnnNv6CY16A@mail.gmail.com>
References: <CAN0E48cY+CSj+b8DtCW9Fiz3sMq4vixdLSkCMcH11YKJmSYpxw@mail.gmail.com> <CADaq8jfEg2UYH1vVXjtc4cqawPofUdwc+T5X5w114UNS+jZW1g@mail.gmail.com> <DAA343BB-F318-44C8-95FF-1D139BC8885A@oracle.com> <CADaq8jdyzQBayaKhnxy_K1ZKf5xzZPm6h45Q+=_bZ+FpThDDAQ@mail.gmail.com> <CAN0E48dmkuhbXKp=U7GR-sw3RhvNvsTH4TbFCY-qnnNv6CY16A@mail.gmail.com>
From: David Noveck <davenoveck@gmail.com>
Date: Mon, 10 Jul 2017 11:10:55 -0400
Message-ID: <CADaq8jduCaCbjJZ3hSSg1dxcYkFEyR4Yj0+SgsxszgaHfkK65w@mail.gmail.com>
To: Brian Pawlowski <beepy@purestorage.com>
Cc: Chuck Lever <chuck.lever@oracle.com>, "nfsv4@ietf.org" <nfsv4@ietf.org>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="001a1149977855f9570553f7fd0c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/CI2rSBLsZLiSwlqzRolV3knUqkM>
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 15:10:59 -0000

We can call it a "discussion" if you feel more comfortable with that.


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

> So... let's definitely not call this a meeting. We'll have one of those on
> Thursday.
>
> But I will have office hours from 6-7pm in the conference hotel. You will
> find me sitting near the lobby.
>
> You can send me e-mail if you have difficulty locating me... I will be
> checking it all the time between those hours.
>
> beepy
>
>
> On Mon, Jul 10, 2017 at 7:43 AM, David Noveck <davenoveck@gmail.com>
> wrote:
>
>> ad hoc is better than post hoc :-)
>>
>> On Mon, Jul 10, 2017 at 10:18 AM, Chuck Lever <chuck.lever@oracle.com>
>> wrote:
>>
>>>
>>> > On Jul 10, 2017, at 8:53 AM, David Noveck <davenoveck@gmail.com>
>>> wrote:
>>> >
>>> > I'll also be in Prague Sunday.
>>>
>>> Me too. A gentle request to keep arrangements for ad hoc recharter
>>> meetings on the list, so others may attend! Thanks.
>>>
>>>
>>> > 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
>>> >
>>> >
>>> > _______________________________________________
>>> > nfsv4 mailing list
>>> > nfsv4@ietf.org
>>> > https://www.ietf.org/mailman/listinfo/nfsv4
>>>
>>> --
>>> Chuck Lever
>>>
>>>
>>>
>>>
>>
>

v2.23.0 | Report a Bug | By Email