[nfsv4] Target date for draft-jetf-nfsv4-migration-issues

David Noveck <davenoveck@gmail.com> Sun, 20 May 2018 15:40 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 A2B6A129C59 for <nfsv4@ietfa.amsl.com>; Sun, 20 May 2018 08:40:30 -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 MwjkmBUyIOA1 for <nfsv4@ietfa.amsl.com>; Sun, 20 May 2018 08:40:28 -0700 (PDT)
Received: from mail-ot0-x22b.google.com (mail-ot0-x22b.google.com [IPv6:2607:f8b0:4003:c0f::22b]) (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 AAFFF129C56 for <nfsv4@ietf.org>; Sun, 20 May 2018 08:40:28 -0700 (PDT)
Received: by mail-ot0-x22b.google.com with SMTP id t1-v6so14269516oth.8 for <nfsv4@ietf.org>; Sun, 20 May 2018 08:40:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=eczHig+kFifFAd+N9b711VTDFyQKDsVOgHKqnaSXK0Q=; b=r4ixONcscHfy1BFUZI+tpQzNmz32eI9hHqydCk65T7vIRVnC4cRHs5VI/JsJe50DEr UMcKxeqMLIdd3Few2RBQtg9hDq5McxghXS7+oRgJqnMOirEhzwr8KqBHFDxj0MlbdExP 6ITaz3rjpTu3dFEYjK28wFD/0aT7IJUc8LTE38WtCsQaU0f1r0LnFz9Y5pmcKCQlazVd TJSaUTy28+Kh5X4GsMB1vaylvrJgcsWQkQkPNMMnwDIxK1cujUezOmku08KGfydicuAm 7npfMdDJYj4WQN/Yk9MYLg67AgIsm+aJCy2AP80XKsug6O7a6qh+pRQ+DqsaXTuwP49e RYVQ==
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:cc; bh=eczHig+kFifFAd+N9b711VTDFyQKDsVOgHKqnaSXK0Q=; b=V9Ctslh5Pt/mw3p2hyUm/007OK3YkkNYm1HkvUAcjfMMLiwQXDDAbj45Kc9p6AyjTV vLbLflwN5vUjnIkKp8GTN15YwzlIcSMxxBV5v+MCK0xK+eMaWT7ijJBpwwGcW5cqXTBx 3apOdp4BTiDrfZipiv9q8teEJ5/ySB4CzIJO+bW8bg+CHXwBQdDeVg5wEb8fz5zNPSCi P6XuCtukhEKUInWfSwS5Im8WCy3kBu8lsh9bTjDlAP0q0292tjk8J+jkdMoPx0faPs+9 l8M8F0udYz+OzlabfsK0J2WrCxgv8Z337w4HdePGXHhjVHYFOFvom7J1VuG2RGOtIgEM s6VQ==
X-Gm-Message-State: ALKqPwdmaZJOvDWv1GZBCuH6vB3MdRuAStjB25SgdWk6+hbcfuiARUxO wrh0COEjAW04gsFthCid7wA7NbBFw+LPzSAls3I=
X-Google-Smtp-Source: AB8JxZqRRuaVVsJsNZ1QUQHaTH7R31sK1z4YX18Q5PNbDhjI3snFXsEZx02+We21oSLuriDINBrcqOiVUVicqx4HzVI=
X-Received: by 2002:a9d:2e0f:: with SMTP id q15-v6mr10860125otb.302.1526830827949; Sun, 20 May 2018 08:40:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.201.55.233 with HTTP; Sun, 20 May 2018 08:40:27 -0700 (PDT)
From: David Noveck <davenoveck@gmail.com>
Date: Sun, 20 May 2018 11:40:27 -0400
Message-ID: <CADaq8jfWfaoR=fmzaGFLu3CVEpQcWHS=5g44vwhSYw+eH68PPA@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Spencer Shepler <sshepler@microsoft.com>
Cc: NFSv4 <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000021d445056ca50111"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/FTjJQV9f5m7eftSJ6wS3jXCGW4Y>
Subject: [nfsv4] Target date for draft-jetf-nfsv4-migration-issues
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: Sun, 20 May 2018 15:40:31 -0000

I have just submitted -15.  It appears that the current target date for
WGLC, 6/2018 is not likely to be realized and some adjustment will be
required.  The primary reason for this is the need to include some
additional material relating to the existence of multiple connection types
in -15.

Because of the need for discussion of this new material, I will probably be
unable to request WGLC of -15 for a while in order to give the working
group time to discuss -15. The July 2 cutoff date for draft submission will
also come into a play meaning that a decision will have to be made in late
June or early July.

Based on working group discussion, a decision will need to be made before
7/2 anong the following potential paths:

   - That -15 is to be a basis for WGLC.
   - There is a set of changes to be made for a -16 to be submitted by 7/2
   with WGLC to be requested soon after submission
   - There is not yet general agreement on a set of changes to be made to
   get to a final version of this document.

In the last case, there will be discussion of the contents of -16 at
IETF102, with the expectation that WGLC will be requested on that,
probably in early August. In the other two cases, WGLC will be be going on
during IETF102 and there will probably need to be time at the meeting for a
discussion of related issues. In all cases, the ultimate fate of the
document will need to be discussed.  The question of whether it needs to be
published as an Informational RFC needs to be resolved.

It appears that 8/2018 is a reasonable target for the completion of WGLC
but I don't see a need to change milestones now.  As I see it, we should
ensure that any problematic milestones are discussed at IETF102 so that an
updated set of milestones can be published soon after the completion of
IETF 102.