Re: [nfsv4] Benjamin Kaduk's Discuss on draft-ietf-nfsv4-mv1-msns-update-04: (with DISCUSS and COMMENT)

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Mon, 25 March 2019 13:58 UTC

Return-Path: <spencerdawkins.ietf@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 10564120442; Mon, 25 Mar 2019 06:58:40 -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 XYbgF86M-E2g; Mon, 25 Mar 2019 06:58:37 -0700 (PDT)
Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450:4864:20::230]) (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 2531F120381; Mon, 25 Mar 2019 06:58:37 -0700 (PDT)
Received: by mail-lj1-x230.google.com with SMTP id k8so7904336lja.8; Mon, 25 Mar 2019 06:58:37 -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=JDWI1C1sgeX2utQjf/PnZnV7csfrO/ohAAPfUpu6Vq0=; b=u903trafHNuhkwuGpEQJMLA87ioexTRmGdiJT3/ryLUYvbkQMBZRXzgdKkCAyTkaqV A9N3x7oyLN0Xe/g0NDb5pPtFugUWC/f6wB924HJuixPVTTHKpIWMtjZIJAKbUlzL1Og3 7UjgOIW95vMxmsnQKptP31fhr5tdVq6J5ItpIcoWQp6MAN9iymyD1R4G0NQvk019BO6Q +VuHQyOMW5v35e91Iy4nkXpDtjk5UNpOH70/Z0KNPX7FkN5IV+mdlShEuKX/ZfEYKHH5 +gm5sYb0juR9UAmYbF39LO4upEoADPgKspiWuwWqtrOehP/xvKbqWqUJtiT4264jEakN zS4A==
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=JDWI1C1sgeX2utQjf/PnZnV7csfrO/ohAAPfUpu6Vq0=; b=MXNqb4JcUZ0PhOpmRRMbkMADCQ2JnG700ZqW2udb3sIv1eAoKYeki6892N5x3G5Cw8 cYPOsWxti6iFxQYtRNJ+yBs0Ig9s/qYIXxKcc69++OLcK7Z3WYaRxhsw0O/4htbrGGDr iw6zbtCWQTlJ6LIgHWwKt0+FgP2ue4sxk4U1t56By6anuETZqt9fGOq48Hj+5Rbtr3V1 t3bM2FPgGEG/y+QbL25MSzr4dKZu+UPPa1dJctIGrUZ+PhkxfnVphLuMrumP3syhBwyt ql/jzf+jOmMNFyPkJRLL/mBDBSyRQCHEw4QTLTplQsHQfpUj6GJRuHDIqHIcqcLSSlKN xqGg==
X-Gm-Message-State: APjAAAVl9Es0XK3Qh0XXKfMMla0uFNQJbLB+ybpUMRjkQYPzQP7AUieL jrRwYJe8kzB9XX7p08+Nixd/eyaqncFly3sI88c4FvSQCVg=
X-Google-Smtp-Source: APXvYqwSWwjOaUW0WeZ+iwYG+6WLuwt/o3yS6Yy9zlIYD+uKXnbCm2V4EQekx+G8tZppK3SGtQ6NxI+sBZBRLpK+uTI=
X-Received: by 2002:a2e:8156:: with SMTP id t22mr4069798ljg.77.1553522315007; Mon, 25 Mar 2019 06:58:35 -0700 (PDT)
MIME-Version: 1.0
References: <155184411184.27685.16459405842977852294.idtracker@ietfa.amsl.com> <CADaq8jcbtAy+RnCsxLBHpGfX7YOUCXbVU21DKKF5yOuXtwM4GQ@mail.gmail.com>
In-Reply-To: <CADaq8jcbtAy+RnCsxLBHpGfX7YOUCXbVU21DKKF5yOuXtwM4GQ@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Mon, 25 Mar 2019 14:58:24 +0100
Message-ID: <CAKKJt-c++YwyEONK=He55uX0GR+23bc1jrjjU5hxHB3ipJYwmg@mail.gmail.com>
To: NFSv4 <nfsv4@ietf.org>
Cc: draft-ietf-nfsv4-mv1-msns-update@ietf.org, nfsv4-chairs@ietf.org, The IESG <iesg@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000bc99820584eb99ac"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/poALXPP_kHNtmotqPh8aGc4pQRs>
Subject: Re: [nfsv4] Benjamin Kaduk's Discuss on draft-ietf-nfsv4-mv1-msns-update-04: (with DISCUSS and COMMENT)
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: Mon, 25 Mar 2019 13:58:47 -0000

I'm putting this here, in Benjamin's Discuss ballot thread, but this is my
suggestion for going forward on this draft. Magnus will be your AD starting
Thursday morning, but if I might provide advice that I hope will be helpful
...

If you take a look at
https://datatracker.ietf.org/doc/draft-ietf-nfsv4-mv1-msns-update/ballot/,
you'll see that only 6 ADs cast ballot postions that are included in
considering whether a draft is to be approved during IESG Evaluation (Yes,
No Objection, or Discuss). That is barely half of the number of ballots
needed to approve this draft for publication.

Abstains and No Position ballots may have have useful comments, but they
are ignored when counting ballots for approval.

And my ballot expires on Wednesday, so clearing Benjamin's Discuss will
leave you only half the way to getting this draft approved.

As the ballot positions arrived, I began considering alternative ways
forward. Some ADs Abstained, saying "I don't think it's reasonable for me
to review a 100-page patch to a 600-page RFC", and that's a conversation
that I was prepared to have with the IESG, but other ADs Abstained, saying
"I tried, but I couldn't do it". In one case, Suresh, who is an experienced
and conscientious reviewer, said he found instances where he couldn't
identify changes between OLD and NEW blocks of text. So I decided I was
willing to believe the "not reasonable to review" Abstain positions, as
well as the "I tried and couldn't do it" Abstain positions.

For this reason, I waited until I knew who the responsible AD for NFSv4
would be - "hi, Magnus" - and am now telling you folks know that my advice
would be to produce a -bis version of NFSv4.1, rather than trying to
advance this draft.

Magnus can accept my suggestion, or do something else, starting Thursday
morning (he and I both try to act in your best interests, and we might not
always agree on what that means). And you don't have to wait until Thursday
morning to start talking with Magnus, and with each other.

I would suggest that you ask Benjamin whether he would be more comfortable
continuing discussion of his ballot position of this material in this form,
or in -bis form.

And I am truly sorry that you experienced this Late Surprise as I was
stepping down.

Best wishes with your work, and enjoy not having to include a last name
initial every time you mention "Spencer" in NFSv4 e-mail!

Spencer (D)