[nfsv4] Session Dealing with Current WG agenda at IETF 107

David Noveck <davenoveck@gmail.com> Wed, 18 December 2019 17:59 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 33321120241 for <nfsv4@ietfa.amsl.com>; Wed, 18 Dec 2019 09:59:19 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 PDwDLEENWTtG for <nfsv4@ietfa.amsl.com>; Wed, 18 Dec 2019 09:59:16 -0800 (PST)
Received: from mail-ed1-x52e.google.com (mail-ed1-x52e.google.com [IPv6:2a00:1450:4864:20::52e]) (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 2869D1200C3 for <nfsv4@ietf.org>; Wed, 18 Dec 2019 09:59:16 -0800 (PST)
Received: by mail-ed1-x52e.google.com with SMTP id f8so2397488edv.2 for <nfsv4@ietf.org>; Wed, 18 Dec 2019 09:59:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=+A0RDKJoHADybHthT7bDxSDtgvwiV6SwzeyyTsAZUKU=; b=gg+3i95qA57+O0qVoAjv2WGw8D2rB3syV9Ru+t4L8g8zxJnG5ZN9G1aQt2lMxmRpWQ gxyavV/jWp5XeZO18U6AfB9p4QbBrNJSbMyXsGzOB/IA2mIHYzHvPF9I9kylmWao0l1W dZgjY8zHJDOoiSyG+wphn9aHGVdExlWQPVQOqsfm4z7z+s5XzJ5TKeFnrpJHf8X/x4a9 Nt49oMOOK1s9dXwFcpeSEHPArMeedPv/eT8Dz+41hJ73AU43dASS0sj0f0nd6bf9d+0c HgvXWaj0eE3npZ/GXXAYJOQDhT+05X/umma/KWAwOSGa1JQRzayHq1AOqzY/20rgcM0B Zxcg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=+A0RDKJoHADybHthT7bDxSDtgvwiV6SwzeyyTsAZUKU=; b=J6AJDasmcAHA7o4hZMYjvNGAUAcCLHO0I3/3yUvhRYZoewyLidSy289MUnn/kD/1ui 4q6dlY7kwNf+fXNonSMv7yopuglVXh9hyDky74xynby0K5lxxVG6IQCTegu4vg2JEp4H Mc6JIz8NZ1VrdeMrxlb1CEUkSLPc4pTN1KpXjVTl2hOUx2JuhfrLS/h6TBfUv7qCvjD3 DjEzlJXg7F+HXBGOg1ondS+szECBCqxCCy+q97r3wKbZHIB6EVKnZRhLyFIBBJwji81i JK719n2NMnJNyskRZfsrX0RS1g/QGEVN3UNRbxglblwkB9EtYY/DG5DqkJqlBOnClrxp eonQ==
X-Gm-Message-State: APjAAAWyR0ZykKcE571l9krpOleTkRl/HrTd7nEgvBSgHiLH+sFLdIWK 7IujO+O1C8/JcHN6d5IOujiX8nLfNk+5piLaz+nSZg==
X-Google-Smtp-Source: APXvYqyWbnxX5J+5V9Kf6QOPwC1FMahU63A04JkhfEGfc+j9DsPedL4L3HqHUgvq3BXDGvQZnTFyXU4OZ1dzU/N3Uhc=
X-Received: by 2002:a50:8a04:: with SMTP id i4mr3916859edi.150.1576691954125; Wed, 18 Dec 2019 09:59:14 -0800 (PST)
MIME-Version: 1.0
From: David Noveck <davenoveck@gmail.com>
Date: Wed, 18 Dec 2019 12:59:02 -0500
Message-ID: <CADaq8jdsEMc9ov5UgiL2beFmJznDxgJcmc8QXJzJ8o9zSAgs7A@mail.gmail.com>
To: NFSv4 <nfsv4@ietf.org>
Content-Type: multipart/mixed; boundary="000000000000d8d76a0599fe3332"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/ZcVHu5FynQohgjQhK5ydYIRFjBk>
Subject: [nfsv4] Session Dealing with Current WG agenda at IETF 107
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: Wed, 18 Dec 2019 17:59:19 -0000

I've requested two two-hour sessions at IETF 107.  Planning for the session
dealing with the current wg agenda is farthest along and  we have a
tentative schedule, which I will describe in this mail.  The other session,
dealing with the future, is not as far along and I will send out informaion
about it on a few days.

The current working group agenda consists of:

   - existing active WG documents
   - milestones for which there are no existing WG documents yet
   - A few additional items, for which WG documents are expected, in
   connection with rfc5661bis.

Attached is a powerpoint describing the state of this agenda.   I didn't
include a .pdf because the size (500K) might run afoul of WG list size
limits.   I can send one directly to anybody who wants one.

Regarding the items on slide two, no time has been allocated.   We hope
these will be published by March.    If they aren't, I will want to discuss
that somewhere where ethanol is available, rather than in a wg session.

Regarding the items on slide three:

   - Sorin will be presenting on the NVMe pNFS document.    I'm allocating
   twenty minutes to this.   Given the 4/2020 target date for (now) requesting
   publication,  it will be important to get any lingering questions resolved
   before WGLC.
   - Chuck does not anticipte any need for discussion of this
   document/milestone.  If this document is to be discussed at IETF107, it
   will be in connection with the NFSv4-wide security rework that is going to
   be referenced by rfc5661bis.

With regard to the items on slide four:

   - Given the decision to drop the milestone for the RDMA layout type,
   this will not be discussed in this session.  If there is someone who is
   brave (or foolish, judgment call) enough to want to discuss reviving this,
   we might allocate some time in the future-work session.
   - Chuck is anticipating a 15-minute talk on rpc-pver-rdma version 2..  I
   think the focus will be on the items added to version one and whether thet
   are are adequate to meet our goals for a version 2: big enough to be
   worthwhile but small enough to get done in a reasonable time.

With regard to the items on slide five:

   - I've allocated 15 mnutes for a discussion of the state of delstid
   (will be -01 by IETF107).   If the authors need more time for this, they
   should let me know.
   - No time specfically allocated for nfs-ulb-v2. If there is neef for
   bried discussion of this, it could be folded into the discussion of
   rpc-over-rdma version 2.
   - Chuck will be giving a 15 minute talk on integrtiy meaurement.   I
   expect the discussion to focus on the metadata format description.    The
   intention would be to make progress about questions about its adequacy.

I'm allocating 40 minutes for discussion of the items on slide six.   We
will spend at least 10 minutes on each document and allocate the extra ten
minutes as seems most appropriate given the situation in March.

This adds up to 105 minutes, so the schedule should not be tight.   If
people anticipate needing more time, please tell me before the meeting,
rather than having everybody assuming they can run over without difficulty
and leaving someone with only 5 or ten minutes when they need fifteen.