Re: [nfsv4] draft-ietf-nfsv4-mv1-msns-update

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Tue, 22 January 2019 12:11 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 5EF0F130F1D; Tue, 22 Jan 2019 04:11:43 -0800 (PST)
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 hU2hA0CP9EBu; Tue, 22 Jan 2019 04:11:41 -0800 (PST)
Received: from mail-lf1-x134.google.com (mail-lf1-x134.google.com [IPv6:2a00:1450:4864:20::134]) (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 754D2130F18; Tue, 22 Jan 2019 04:11:40 -0800 (PST)
Received: by mail-lf1-x134.google.com with SMTP id e26so17897002lfc.2; Tue, 22 Jan 2019 04:11:40 -0800 (PST)
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=wGUtajQm9ssW6XOzMdNbBxGiIVI7QiIsjyGtExJANNw=; b=t+PpgyDwN+PjvqHHsXo7Ncifg8UN65dkTeFR5hWJjjlIAtVn+N0qDkd4QWK34AHac0 GbJMx21RTkUTw7+Wiyo5YSk9xrN5lpOFZKHmSmb+TY/58B/IYgyRcMIShg2dEisMkZwV fotRqgf41TkS8/KbjCc53sjthRbKSoCrKuIB3rH+97WuHNaS5jtCHRRGTeBb9Ad34s/x mI05KbvQat0XeS2auZ1K8dJhlrcWSCNWLreBpXTv0y6vRRE4MsCUiOD+250agdndHbli xw2BniCNJOeHJ4akcSwExMrGOyZ/QYZkXeTIXeZZXSN/QJZ5s8o64jbIsaGKwJ5GLU5o R2CQ==
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=wGUtajQm9ssW6XOzMdNbBxGiIVI7QiIsjyGtExJANNw=; b=fdCDuOLWAq/c2JrDVk48ni6uBCNMT9n41173S/+3gtVr0s/EpcQ2YbVfnUarxsST2O crkrd4ZwMQMVZZ1ep4mJjTzQX1E90CVvZ0uDyco1qHI+yCEn67aZMV96d7Ati+nzf+u2 legTvMJxqoqoIsdezX8b4zOts3y/kuudDMiMeTEDW92HtgW4Uo0nxfFQWwVvBYqiTerf TOXZj9gPA1W/xL0NVlfMV56+iRGkeH5HSbtOBy+PP6QcD4KS+66jzQ76rrqZAkSx30V1 ick8VnBgvLzh03PpGqvF53WYeqxT7kW8HA9fmxKCm8aG2k7xpvXMGpUcI3O9hFRS5GZR LfBg==
X-Gm-Message-State: AJcUukdIPf1MOoHBTs2u6C4D7rkExjK2X13o5vQR213Labw950uD9twq XvTkmh7fMdK+nlztsFfYFjo5Wu4SQUc7Hcfp4Fg=
X-Google-Smtp-Source: ALg8bN56NcxLO4/kuXaV0YeqTksMqG/mgxRRsQ/3o0HYSYKlWND4YpLzypns0wlncxvdDzwdyudcHU7sud1Xz9MNQ/c=
X-Received: by 2002:a19:5d42:: with SMTP id p2mr21381136lfj.83.1548159098301; Tue, 22 Jan 2019 04:11:38 -0800 (PST)
MIME-Version: 1.0
References: <CADaq8jewG+MYPgVRyqg4dM0-W4qOm=rgoyZ==w6OmowvipXtfw@mail.gmail.com> <CADaq8jciVYN6uwLJJjuE+ObgDc5=37LD53C_TUvEdUTx2Ns0Qw@mail.gmail.com> <CAFt6Bam+zd+ZbWD-FZ152vAkg5kg2+bpRfs8rPsC5SZCB_SX+A@mail.gmail.com> <CADaq8jfhJOP5ZeK60YuE8=V9osV0HpoH8T0b0COhAj+7OjHk_w@mail.gmail.com>
In-Reply-To: <CADaq8jfhJOP5ZeK60YuE8=V9osV0HpoH8T0b0COhAj+7OjHk_w@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 22 Jan 2019 06:11:27 -0600
Message-ID: <CAKKJt-fvRQ5SmSJPq7JA37cyfaNT4n-39CHYDDmR9_mZWxr8XA@mail.gmail.com>
To: David Noveck <davenoveck@gmail.com>
Cc: Spencer Shepler <spencer.shepler@gmail.com>, NFSv4 <nfsv4@ietf.org>, Spencer Shepler <sshepler@microsoft.com>, nfsv4-ads@ietf.org, nfsv4-chairs@ietf.org
Content-Type: multipart/alternative; boundary="0000000000001c369005800ae134"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/KX2G3V3OGOKoqqVc_xHlwMoKKA8>
Subject: Re: [nfsv4] draft-ietf-nfsv4-mv1-msns-update
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: Tue, 22 Jan 2019 12:11:44 -0000

Just as an AD interrupt ...

On Mon, Jan 14, 2019, 08:28 David Noveck <davenoveck@gmail.com wrote:

> > I will return to the office on Monday Jan 7th and this task will be on
> my list
>
> Given that you have been back a week now and no action has yet been taken,
> I am sending an additional reminder regarding the need to move forward on
> this.
>
> It is now five weeks since the end of working group last call and the
> document is still recorded as being in WGLC and no steps have been taken
> either to move the document forward or indicate reasons why it should not
> move forward.  If there are are issues that need to be addressed, please
> let me know what they are.
>

I step down as the responsible AD for NFSv4 in mid-March, which (I think)
barely leaves enough time for AD Evaluation, IETF Last Call (two weeks),
and an IESG telechat cycle before I would have to hand this document off to
Mirja or Magnus (they haven't divided up WG responsibility yet) and give
them time to catch up - for instance, a new responsible AD might do another
AD Evaluation before IETF Last Call, etc.

That might or might not matter, but if it does matter ... now, you know ...

Make good choices.

Spencer

On Thu, Jan 3, 2019 at 1:17 PM spencer shepler <spencer.shepler@gmail.com>
> wrote:
>
>>
>> I have been on vacation since Dec 13th, Dave. I will return to the office
>> on Monday Jan 7th and this task will be on my list.
>>
>> Spencer
>>
>> On Thu, Jan 3, 2019 at 7:50 AM David Noveck <davenoveck@gmail.com> wrote:
>>
>>> It's now over three weeks since the end of working group last call and
>>> the document is still in WGLC and no steps have been taken either to move
>>> the document forward or indicate reasons why it should not move forward.
>>> If there are are issues that need to be addressed, please let me know what
>>> they are.
>>>
>>> Normally,  I would have sent weekly reminders but two-weeks-after-WGLC
>>> turned out to be Chistmas Eve and three-weeks-after turned out to be New
>>> years Eve.  So I skipped those and am sending out the three-weeks-after
>>> reminder a bit late.   I will send our another reminder if necessary on
>>> 1/10, one month after the end of WGLC.
>>>
>>> On Mon, Dec 17, 2018 at 12:20 PM David Noveck <davenoveck@gmail.com>
>>> wrote:
>>>
>>>> IIRC, Working Group Last Call on this document ended a week ago.
>>>>
>>>> Could you please update the document state, to reflect the results of
>>>> Last Call.   Since there were no additional  comments, I believe Last Call
>>>> completed successfully and we should move on to the next step, which as I
>>>> understand it, requires you to produce a write-up.
>>>>
>>>> Once that is done, I believe it is up to Spencer D. to review the
>>>> documemt after which it can follow mv0-trunking-update in being considered
>>>> by the IESG.  Also, somewhere in there, a document shephered needs to be
>>>> designated.
>>>>
>>>