IETF Logo Mail Archive

Re: Things that used to be clear (was Re: Evolving Documents (nee "Living Documents") side meeting at IETF105.)

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 04 July 2019 20:54 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A41F12023D for <ietf@ietfa.amsl.com>; Thu, 4 Jul 2019 13:54:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 gQye39oJpJ_G for <ietf@ietfa.amsl.com>; Thu, 4 Jul 2019 13:54:06 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D81EE1202AB for <ietf@ietf.org>; Thu, 4 Jul 2019 13:54:05 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 80B6D38195 for <ietf@ietf.org>; Thu, 4 Jul 2019 16:52:07 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id D0AE1BA4 for <ietf@ietf.org>; Thu, 4 Jul 2019 16:54:02 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: Things that used to be clear (was Re: Evolving Documents (nee "Living Documents") side meeting at IETF105.)
In-Reply-To: <CABcZeBNwze0fbikPbr8LG4=ZRJ=fUyU8dBrTDBw2Vjx90C0Kxw@mail.gmail.com>
References: <0856af71-4d84-09d1-834d-12ac7252420c@network-heretics.com> <CAL02cgQ9qWVUTPW=Cpx=r32k3i1PLgfp5ax0pKMdH0nKObcKTg@mail.gmail.com> <e8d28a7f-128d-e8d0-17d3-146c6ff5b546@joelhalpern.com> <CAHw9_i+UBs85P+gjcF6BJd1_WD2qFrrYCnXb4rtcG9Hepqm37w@mail.gmail.com> <796c1f6c-cd67-2cd5-9a98-9059a0e516f8@network-heretics.com> <20190704013009.dlifopcbm2umnqo7@mx4.yitter.info> <b18809df-ee98-fb29-b6c4-04ed579e163a@network-heretics.com> <20190704052335.GF3508@localhost> <911a7af5-071a-ce88-527d-70dfe939b256@network-heretics.com> <6317584D-4C9B-46E9-8197-D2A488701868@fugue.com> <20190704140552.GE49950@hanna.meerval.net> <b0943792-1afc-0c94-51b7-f2d393ef39c5@network-heretics.com> <CABcZeBOKmCCSU0Md1myDyhQ=Ja6H0TUgEdrGZ4bQCQOw5K0H9w@mail.gmail.com> <m25zohy8or.wl-randy@psg.com> <CABcZeBNwze0fbikPbr8LG4=ZRJ=fUyU8dBrTDBw2Vjx90C0Kxw@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Thu, 04 Jul 2019 16:54:02 -0400
Message-ID: <20555.1562273642@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LCK16rMoi3L6FXkc8asKgi1JtW4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jul 2019 20:54:13 -0000

Eric Rescorla <ekr@rtfm.com> wrote:
    >> and your description of how tls did this with 1.3, 'marked' versions of
    >> internet-drafts, seemed to work well.  and those with colder feet could
    >> wait for the rfc.  but i note that the triel implementations seemed not
    >> to be deployed in production until the ietf sausage was made.


    > I don't want to debate the precise meaning of production, but what I will
    > say is that at in the case of TLS 1.3, we had pre-draft versions on in
    > Release
    > versions of Chrome and Firefox and serving live domains at Cloudflare
    > (and I think Facebook and Google, but I'd have to check my notes). This
    > was actually essential to finding problems because there are environments
    > which will not run prerelease software.

I agree how valuable it was.

But, the parties involved all understood (in a deep way, up to product
managers, I expect) that there might be incompatible changes.

I have been through protocols with obvious flaws waiting for a zero-day bugs
where I could not get a fix in ID-07 because "it's been deployed".

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email