IETF Logo Mail Archive

Re: [nfsv4] IETF 105 - Montreal - NFSv4 WG meeting ?

David Noveck <davenoveck@gmail.com> Thu, 25 April 2019 20:56 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 40ED51203DF for <nfsv4@ietfa.amsl.com>; Thu, 25 Apr 2019 13:56:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_NONE=-0.0001, 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 TAP_bcLcHkjt for <nfsv4@ietfa.amsl.com>; Thu, 25 Apr 2019 13:56:55 -0700 (PDT)
Received: from mail-oi1-x236.google.com (mail-oi1-x236.google.com [IPv6:2607:f8b0:4864:20::236]) (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 C7B2B1203C6 for <nfsv4@ietf.org>; Thu, 25 Apr 2019 13:56:55 -0700 (PDT)
Received: by mail-oi1-x236.google.com with SMTP id k10so1215226oik.7 for <nfsv4@ietf.org>; Thu, 25 Apr 2019 13:56:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Pdve8M9UjAk6tE9vs7izUCyOAgJ974qwv3HioXkC1w4=; b=tCbEZnFc5Tjcqn7JwI7zdEXj9fWerDyrV/E1doaeSR/OSkUKQ9aDh+Eyxw73JQCE51 a4SUvF6gDEgYvO+eeIS2KeL4+TUe+6h3ancrS7S7UMN8j7TepxfWFzeoGTLBvZEfJSqX 35Hw1M/vPIdwXLEatHLve43Fv/iC3e5K+3RiEy8q/vjhZ7anHUSw0RswrQywzcfAp2si d8hv9A/z1Dnd5g73vnLlBxpRBCcg38ltNJFH0EpkKrfMmemOVYlJtMZZq7Ncw3BjD4lJ AaDidH2Iu7NzgB14bZSJrnfTho/t+IZopLBZkY/8KdTIb9yDg+eTN/HDf+1g5SoCknu8 gyXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Pdve8M9UjAk6tE9vs7izUCyOAgJ974qwv3HioXkC1w4=; b=cz+KkoHQw3jHEl/5m2t2XPhFyvpQHNgQlZgdRqFz0b0GSIiMEqIs+G/Zr+0EWixdrK PlyyD4DFdhzUJLy43cGk7oelGLeTQqO49MTdJissvoUQ5wuPS0TbbYLpl+hRJq6xrUSj +C9FsSjjLBMSHRTAdJZkr/ks/zkTqQ8voZ7AwhQjpAoBeKVXYyVTtPXXFZQ8AVOmZEU9 CXjrlrSvGDtBMOp3kY8AF/afsmRY5ofus7yT5PbOcZ0t4VDlAxf+Bew3Fb3fVZpwaahS sTWTtgUUMu+nmgL0riaHOIQWFo3PkP00m8f5L5zSANsgx2tJTPkBaT6iY8rrGE7+/3XR rizA==
X-Gm-Message-State: APjAAAVHCMAkSG2MEWeUbjIIgumhINcKliMw3WgGSKnihLXLvG881n30 pevbPXG73pgqKC427wYUcVdSlsPRahbi5pYJh1c=
X-Google-Smtp-Source: APXvYqxyE/yZEnTrAtKAMIioT7x4NQMyX+u6px3Vsai8LRh1D8NjqMvMwhM+2MN7Rzikjp9t0pUDjmvMceo38slahbw=
X-Received: by 2002:aca:b68a:: with SMTP id g132mr4770042oif.47.1556225814791; Thu, 25 Apr 2019 13:56:54 -0700 (PDT)
MIME-Version: 1.0
References: <CAFt6BakCHvOnMR5RaX59uXSga03VVskRwKVpg97CbFr+Pxiz9A@mail.gmail.com>
In-Reply-To: <CAFt6BakCHvOnMR5RaX59uXSga03VVskRwKVpg97CbFr+Pxiz9A@mail.gmail.com>
From: David Noveck <davenoveck@gmail.com>
Date: Thu, 25 Apr 2019 16:56:43 -0400
Message-ID: <CADaq8jdaquKW0=jWB+H3BNbGTLVZTK=_TheN-gn52xrurn=yNw@mail.gmail.com>
To: spencer shepler <spencer.shepler@gmail.com>
Cc: NFSv4 <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e18eed0587610e89"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/Tu9lLhng40H-C3yZhJOWZnlzF7M>
Subject: Re: [nfsv4] IETF 105 - Montreal - NFSv4 WG meeting ?
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.29
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, 25 Apr 2019 20:57:06 -0000

I can't see us not meeting given that the last time we met was at IETF102
and that we are in the midst of major effort to move NFSv4 security from
its current unsatisfactory state to something better.

With regard to filling up a timeslot, I'll let Check and Trond (who, as I
undertand it wil be working on a v4-specific document to go with Chuck's
RPC-generic one) define their agenda items.

With regard to my own needs, we will need to discuss work on a possible
rfc5661bis.   It is now pretty clear that the IESG will want to see this.
The only question is whether they will be OK with publishing
rfc5661-msns-update soon.   Even if they are, there will be a need for an
rfc5661bis that includes a new Security Considerations section (with a real
threat analysis) and that will have to be co-ordinated with Trond and Chuck.

I know Tom thinks I'm crazy to even consider this, but, so far as I know,
there is no working group consensus on this point :-)

Also, there are there are a number of documets with target dates in the
second half of 2019., that we need to briefly discuss.  Given the securitty
work  underway, I don't see any need to add any non-security milestones for
2020 right now.

On Thu, Apr 25, 2019 at 4:07 PM spencer shepler <spencer.shepler@gmail.com>
wrote:

>
> The WG/BOF scheduling is open.
>
> Does the working group have the topics/agenda items necessary to meet face
> to face?
>
> Spencer
>
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4
>

v2.23.0 | Report a Bug | By Email