Re: [OPSAWG] Eric Rescorla's Discuss on draft-mm-wg-effect-encrypt-17: (with DISCUSS and COMMENT)

Warren Kumari <warren@kumari.net> Tue, 27 February 2018 19:24 UTC

Return-Path: <warren@kumari.net>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20E2312711E for <opsawg@ietfa.amsl.com>; Tue, 27 Feb 2018 11:24:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.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 CokGfnNHl7aw for <opsawg@ietfa.amsl.com>; Tue, 27 Feb 2018 11:24:27 -0800 (PST)
Received: from mail-wr0-x229.google.com (mail-wr0-x229.google.com [IPv6:2a00:1450:400c:c0c::229]) (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 E1CFF126B6E for <opsawg@ietf.org>; Tue, 27 Feb 2018 11:24:26 -0800 (PST)
Received: by mail-wr0-x229.google.com with SMTP id k9so26060292wre.9 for <opsawg@ietf.org>; Tue, 27 Feb 2018 11:24:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=w9Cf7M/bZocrAt9/qK92OGTkjn+g/lvcSWx+LZjgkqs=; b=FXsYxR9oviqYnXrs4JpEo2HG0mrzdJLG5Wa/vaCgw949TQ9007B4hgexwg1fhfrMGx w4/qRP9AT4F4kTRKkwt2134mbWrwgVDmbShX0r8rn9lAuyDjjG6Z9djfKJ6TNT/HD3Pa CVx1GLstFcOKtF+LfmkIkx5+la99+znePUqB3Ib5jMCc2qoy2BXbQRW5HuyyaOSOBolT gfuPbE2pKYfPyw2cv/ei5RXnGSnSkvjkfK5WMfi7HDbbVMmSHI+CBQC39U1M4mNJkJMO w0PiK9oYrd9TxeKwWyHmEUGN5mjVv/1g9rz/uMJH83yh/k4CWHxR6cr1q/gvM2OsXnXm cejA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=w9Cf7M/bZocrAt9/qK92OGTkjn+g/lvcSWx+LZjgkqs=; b=OQ21kaDJBF12pyOginrfOct5Ds2U5jxse1aQLAFPWfRe9Odf+1vPwulmCKFg817oTY 8GwCl/ATsuIE7GR3/kg2WShIoL97vhv0U71v5PROn892axpUA2vqX4M1+fb4xHpujDFD ZfxAhl36FYG6FxsbNYchKo+AdeyMteQJPHZizsG7CoZ1cpVLx6ayZNSN51XsIwEnl6qP Z4ZwZirAs/BDrZdbr8y/PBWS7osdNz9WIpakjnUqK6TSz9TvLZWupnhf/in7qduEIYvY w7Z0F6h3UN2B9Y/3tpq7ooh0Baa4HHtwn9HUT/ItO6PADf0CyELJqskUtB355nTO216h 5NFg==
X-Gm-Message-State: APf1xPAUTiY5Kz3voSRF/bFLdCJRQ2Of4feAfZcXeDDERNYaO3paYb2j zplMGLgZmbMvKy5/MJbMq9CgpEVwq2puQdr5KV3Isg==
X-Google-Smtp-Source: AH8x224L6k7LjHXMSccXSnthGsrYCA3qn1McJhohGmCKzfhuQuXBokJubfnxEMX6HWzupGM6ae4fsRtDTbYPDzVu1Hg=
X-Received: by 10.223.162.152 with SMTP id s24mr13232578wra.148.1519759465067; Tue, 27 Feb 2018 11:24:25 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.152.235 with HTTP; Tue, 27 Feb 2018 11:23:44 -0800 (PST)
In-Reply-To: <CAKKJt-cuNapkF=f9SxsxZFPQcns3uLVw9CiqoWo=HGm3icJ3zg@mail.gmail.com>
References: <151806627444.17073.14252972331367641645.idtracker@ietfa.amsl.com> <CAHbuEH63n1LaqqfxLfRS85swW8QT5fnjfkYJWAdtZB0QNGCd9A@mail.gmail.com> <CABcZeBMTs3-L4Nfxw_ovyTu_gyzkhL41Kcnc0oeP-QWMQy8uMA@mail.gmail.com> <CAKKJt-fWPb8iwOSD1awxwj2yf7wv_foYXR_J=iLw6JUC9Yz_4A@mail.gmail.com> <d53550b4-17be-72c7-91e5-717cddcc91fa@cisco.com> <CAKKJt-cuNapkF=f9SxsxZFPQcns3uLVw9CiqoWo=HGm3icJ3zg@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
Date: Tue, 27 Feb 2018 14:23:44 -0500
Message-ID: <CAHw9_i+Avngw1E11AdbM4DNJLUh-yBwiaY47f24yVA45y1JtYA@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: Benoit Claise <bclaise@cisco.com>, Eric Rescorla <ekr@rtfm.com>, Paul Hoffman <paul.hoffman@vpnc.org>, draft-mm-wg-effect-encrypt@ietf.org, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, The IESG <iesg@ietf.org>, opsawg@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/PYOj52ikX93oLr0IMIQHyH51esE>
Subject: Re: [OPSAWG] Eric Rescorla's Discuss on draft-mm-wg-effect-encrypt-17: (with DISCUSS and COMMENT)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Feb 2018 19:24:29 -0000

On Mon, Feb 26, 2018 at 3:28 PM, Spencer Dawkins at IETF
<spencerdawkins.ietf@gmail.com> wrote:
> Hi, Benoit,
>
> On Mon, Feb 26, 2018 at 2:15 PM, Benoit Claise <bclaise@cisco.com> wrote:
>>
>> The way I see it, we're going to fix comments forever.
>
>
> Right. But my concern was that the text that we're reading for an up/down
> vote can change after we read it, so I should be tracking the proposed text
> changes.

[ Updating in the middle of the thread as this seems the logical entry point ]

... so, we are not updating the current version (we wanted 7 days for
people to read it), and so will be (I believe) balloting on that --
but, just like any other document we ballot on, the RAD will pay
attention to comments received and "Do the right thing".

I believe that EKRs comments are helpful, and Kathleen hopes to
address / incorporate them before the call. I will be putting both the
current (being balloted on) and updated version in GitHub (for a
friendly web enabled diff) so that people can see what the final
version will actually look like.
So, I guess we are formally balloting (unless the DISCUSS is cleared)
on the text as written (-22), but with an understanding that the AD
will make it look like the version in GitHub before taking off the
Approved, Revised ID needed / AD follow-up flag.

Confused yet? :-P


>
> That doesn't seem up/down. It seems like every other draft I've balloted on
> as an AD :-)
>

Indeed.
W

> Spencer
>
>>
>> And we need to resolve this one before the current ADs step down.
>>
>> Regards, Benoit
>>
>> This may not be my week, when it comes to comprehension. At least, I'm 0
>> for 2 so far today.
>>
>> Are we still tuning text in this draft?
>>
>> https://www.ietf.org/standards/process/iesg-ballots/ says that the
>> alternate balloting procedure is an up/down vote - we either agree to
>> publish, or agree to send a document off for rework.
>>
>> If we're still resolving comments, one can imagine that we'd get to a
>> one-Discuss situation, or even no Discusses, and wouldn't be doing an
>> Alternate Ballot on Thursday.
>>
>> I don't object to resolving comments (actually, I find that lovely), but I
>> don't know what we're doing.
>>
>> I've never seen the alternate balloting procedure executed (either as IESG
>> scribe or as an IESG member), so maybe I don't get it, and other people have
>> different expectations.
>>
>> Spencer
>>
>>
>> _______________________________________________
>> OPSAWG mailing list
>> OPSAWG@ietf.org
>> https://www.ietf.org/mailman/listinfo/opsawg
>>
>>
>
>
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf