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

Warren Kumari <warren@kumari.net> Wed, 14 March 2018 15:04 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 A66E8127337 for <opsawg@ietfa.amsl.com>; Wed, 14 Mar 2018 08:04:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.7
X-Spam-Level:
X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable 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 rfqTZhKC0zcF for <opsawg@ietfa.amsl.com>; Wed, 14 Mar 2018 08:04:26 -0700 (PDT)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::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 89E44127444 for <opsawg@ietf.org>; Wed, 14 Mar 2018 08:04:18 -0700 (PDT)
Received: by mail-wm0-x230.google.com with SMTP id q83so4722127wme.5 for <opsawg@ietf.org>; Wed, 14 Mar 2018 08:04:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=JdVZR0aQOJkIQeVMxlCC8dYowsKxG6Rnp6j+9KHl+r4=; b=KnCYnqNrzxRM3i9oLoTSEXvl6EI/rWlqcZgwRmM+cUMOG4v4pB84jiT3DMfHEGZhDM IZgdETGKjSGPMGYaOVpawpHB0UJaXd+e21J9z89tN1KaGPCYC5tA169jVoBqm8arSjNE SOse3tlCHMy14rQMl5ak8rLyiA+fWv4oyV5verl/cngi6KxDitdDHSMGv4TKBWpQC7Y8 pkKOWkjBrt7bR8OvuAU235n4B5J8mJ9D7clgOJ3VnyS/DqQzAaUqWChj9igL4zEsubZJ mCdgDlB1lT34Frpi913Bey3okuX04V/VA/oG0RhxhqyUCQlZPSRnirOvzYJciA+YFrfe fwhw==
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=JdVZR0aQOJkIQeVMxlCC8dYowsKxG6Rnp6j+9KHl+r4=; b=ZA7Bn2irNwmgyyLEfzz6aEb/eAF3uoky9SuPo5O73NlJg9HEIMrwP0w+JkhuiHeB3m EkDA/TRAbQF+rz3QjvU+u+tG1zq73wc44wtyqFvU6aA5ZYEH5txYhE1yUSJuYCN5CGaD Qxnj6uVB0mSP9LGzzlhwjlmVIoMF72eKjgoo4cPx+N6IwcSl4+MVs+1eVPfpAo9fOl8g 1aGYQ+JM3ZQbFL46xN+IG6aIZsUEeodmYWmDiSc+MwxBzRbbKiFoVTfAxkNM3MMTqZ0S DdcDMWaQkl99R9dOpdFTxNqU36+1CvdpHKiTSE2en3xD2ZfSclUavGFSZaLvVYkwTpnc 4W0w==
X-Gm-Message-State: AElRT7H63E5q5xQmHDpLmJHw+EkLrCrMhx46nGgKOMhUm9KZrhmh57Se dtL90eqJV7gznLbXlIHAqAIUdvNaotx0oWucSZBq2Q==
X-Google-Smtp-Source: AG47ELuBVstDNkSaPFtG92t4i7waG3IAo6aP8nTXDKlrTvrNioT6KjrJ4nzavS3pH1PsRt97Z4M+3zdF+mUxSWz/aQU=
X-Received: by 10.28.191.138 with SMTP id o10mr1929440wmi.26.1521039856565; Wed, 14 Mar 2018 08:04:16 -0700 (PDT)
MIME-Version: 1.0
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> <CAHw9_i+Avngw1E11AdbM4DNJLUh-yBwiaY47f24yVA45y1JtYA@mail.gmail.com> <CABcZeBMvFym+KLogJGd=zXOjD_R-=OESuO=CSBJKNk6PwjNARQ@mail.gmail.com> <CAHw9_i+op0AWnmp7-zV40=PXDgjo=CTgVc59PGzHMSCbAg47Yg@mail.gmail.com> <CAHw9_i+1oaAzXZGG8NP4ic1npB3LXYDeHygrcwdRcOLEW2BcuA@mail.gmail.com> <CABcZeBOT+wb7V7yycPa9WFjD7DYyzKMKgYqL3N+2MDguUV489A@mail.gmail.com>
In-Reply-To: <CABcZeBOT+wb7V7yycPa9WFjD7DYyzKMKgYqL3N+2MDguUV489A@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
Date: Wed, 14 Mar 2018 15:04:06 +0000
Message-ID: <CAHw9_iLZEuAzRWnv1+Lk0XxEpar2v8hb_T=pei=gie8cBoXA6Q@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Cc: Benoit Claise <bclaise@cisco.com>, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, Paul Hoffman <paul.hoffman@vpnc.org>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, The IESG <iesg@ietf.org>, draft-mm-wg-effect-encrypt@ietf.org, opsawg@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c071c86571d7b056760b04f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/6xS5wg8R5mG9_Blwor0Kg_PV0jU>
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: Wed, 14 Mar 2018 15:04:30 -0000

On Wed, Mar 14, 2018 at 10:12 AM Eric Rescorla <ekr@rtfm.com> wrote:

> Hi Warren,
>
> I am on travel today, but I expect to read this today or Friday. Can you
> give me until Saturday?
>

Sure.
W


> Thanks,
> -Ekr
>
>
> On Wed, Mar 14, 2018 at 7:07 AM, Warren Kumari <warren@kumari.net> wrote:
>
>> EKR,
>> I'm planning on clicking the "This document is approved" button before
>> the IETF101 meeting unless I hear a clear signal that there is
>> something that you *cannot* live with.
>>
>> Thank you again for your Abstain and all of your comments on the document,
>> W
>>
>> On Mon, Mar 5, 2018 at 10:58 AM, Warren Kumari <warren@kumari.net> wrote:
>> > On Wed, Feb 28, 2018 at 9:45 AM, Eric Rescorla <ekr@rtfm.com> wrote:
>> >>
>> >>
>> >> On Tue, Feb 27, 2018 at 11:23 AM, Warren Kumari <warren@kumari.net>
>> wrote:
>> >>>
>> >>> 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
>> >>
>> >>
>> >> Hi Warren,
>> >>
>> >> Thanks for this note.
>> >>
>> >> It's too bad that we aren't able to see the proposed revisions at this
>> >> point, but I appreciate your commitment to working through the
>> >> remaining issues, and I think we should be able to reach a
>> >> satisfactory resolution.
>> >
>> > I appreciate your Abstain, but, as mentioned, I'm committed to making
>> > sure that the right thing happens here - a new version of the document
>> > (-24) was posted on Friday; I believe that it is now acceptable, and
>> > Paul (the document shepherd) also kindly looked through your comments
>> > and the changes and thinks it's OK.
>> >
>> > I'm sure that you are tired of this by now, but please take a look at
>> > the diffs (stuffed in GitHub
>> > (
>> https://github.com/wkumari/effect-encrypt/commit/974db6cb13faecbf5b1704c1da580b320843d0b3
>> )
>> > or on the IETF site
>> > (
>> https://www.ietf.org/rfcdiff?url1=draft-mm-wg-effect-encrypt-22&url2=draft-mm-wg-effect-encrypt-24
>> )
>> > and let mw know if the document is something you can live with...
>> >
>> > W
>> >
>> >
>> >>  In the interest of not forcing everyone to
>> >> read the document by tomorrow, I'm going to change my ballot to
>> >> Abstain.
>> >>
>> >> Best,
>> >> -Ekr
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>>
>> >>>
>> >>>
>> >>> >
>> >>> > 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
>> >>
>> >>
>> >
>> >
>> >
>> > --
>> > 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
>>
>>
>>
>> --
>> 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
>>
>
> --
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