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

David Noveck <davenoveck@gmail.com> Mon, 14 January 2019 14:28 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 7FD5C130FD1; Mon, 14 Jan 2019 06:28:50 -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 gZBblZXmERW0; Mon, 14 Jan 2019 06:28:49 -0800 (PST)
Received: from mail-ot1-x334.google.com (mail-ot1-x334.google.com [IPv6:2607:f8b0:4864:20::334]) (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 D70AC12D4F0; Mon, 14 Jan 2019 06:28:48 -0800 (PST)
Received: by mail-ot1-x334.google.com with SMTP id v23so19404521otk.9; Mon, 14 Jan 2019 06:28:48 -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=FXAuI4/JSWlwuyLDLbCyd7fB6D8luWu3uIeGXtU3EEs=; b=FdiPlA5nAiRLb2RkhrAO1wI318TaccNQFEdUIjj62vSWYGptvlV952kimzthynZOGU MwW3R406dexAovrDRYmNquA5J2u2ojz58Vvo0HHn9HZwcZmMni6rQaFMG55bG/kpT5AQ 7wgISrhEoMVAW7P91gow/gAu97slw+Ei5kNSXBdKy3oOtHOLz2ZtetupgnAXqIB/Jvg1 +5fVG0G5PiUZSdliiHQ5uwsnFNUAUne0nSJBYVDccE7WbRajlaUeyuhab3vu9gGIrPRg 1dxMflvo4xs5yEfz8I+FD7CE3EAf/uy4c0pOiKKnmv2QKKXz/PP0HOSqJLjojLDjmxiO EmYA==
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=FXAuI4/JSWlwuyLDLbCyd7fB6D8luWu3uIeGXtU3EEs=; b=kVMK1D0mkKfFRszyThpJASvAvKdBr1Aas9WJd1iWSGQ+pFFY9uhjQV3PA3xOzYn7h+ j/Y/epzWv4PfVzwibF5tegfH5QnUX0LyVroL1cIGILK5+VVWDHIsFaOGpW3mcbvF8MnL pwDSBfZ4OdTdm3QEOvj4hQNSAHkQcCaHBql4LIedL8pXAEQY4xCin0PjEJ2wMeOGUWg0 jnYKIREl25nPXR+AK8fOpGAj7tIdTQRiEpn9Cr+jxjC/aB/gkcDOXPOPYPmwB4E9MSxr M91d+jmSC8wPd9afuUcDiDGonBfxFcr3ABLZJ0UzUU4qyNTMXMUn9RP7cDlA9jbFmXWC OluQ==
X-Gm-Message-State: AJcUukfhenaS97tLXcGRdVjpFr0BgCIOrRChwpwiPbfwuvPppiqpJdkr OjQJB4sqWwqmPJZnZwHpdEGPTwAl2hhMSBX1JN0=
X-Google-Smtp-Source: ALg8bN7aEElpNvNCDrea/1i1Cus1w2r3HbPv/hwHVint8mddK0cB+18IbYqzESMGsu5f5XQEYuNPE4dr/UQXYN+xog8=
X-Received: by 2002:a9d:60c4:: with SMTP id b4mr16523451otk.221.1547476127873; Mon, 14 Jan 2019 06:28:47 -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>
In-Reply-To: <CAFt6Bam+zd+ZbWD-FZ152vAkg5kg2+bpRfs8rPsC5SZCB_SX+A@mail.gmail.com>
From: David Noveck <davenoveck@gmail.com>
Date: Mon, 14 Jan 2019 09:28:36 -0500
Message-ID: <CADaq8jfhJOP5ZeK60YuE8=V9osV0HpoH8T0b0COhAj+7OjHk_w@mail.gmail.com>
To: spencer shepler <spencer.shepler@gmail.com>
Cc: NFSv4 <nfsv4@ietf.org>, Spencer Shepler <sshepler@microsoft.com>, nfsv4-ads@ietf.org, nfsv4-chairs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000e680e8057f6bdcec"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/H9EkgKNrBkhFbX8p0TWKd1hKhoA>
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: Mon, 14 Jan 2019 14:28:51 -0000

> 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.

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.
>>>
>>