Re: Long time to standard (was: Re: Google, etc, and their proprietary protocols)

Michael Thomas <mike@mtcc.com> Sat, 28 November 2020 22:20 UTC

Return-Path: <mike@fresheez.com>
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 8EF6E3A1155 for <ietf@ietfa.amsl.com>; Sat, 28 Nov 2020 14:20:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.652
X-Spam-Level:
X-Spam-Status: No, score=-1.652 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc-com.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 iXtN5vzOpo4e for <ietf@ietfa.amsl.com>; Sat, 28 Nov 2020 14:20:58 -0800 (PST)
Received: from mail-pl1-x632.google.com (mail-pl1-x632.google.com [IPv6:2607:f8b0:4864:20::632]) (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 8B1F03A03FA for <ietf@ietf.org>; Sat, 28 Nov 2020 14:20:58 -0800 (PST)
Received: by mail-pl1-x632.google.com with SMTP id s2so4385289plr.9 for <ietf@ietf.org>; Sat, 28 Nov 2020 14:20:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=Ylq9nixHOf3PGUZMALamUB+rBaunU9uSACfgzI0LaCE=; b=YW/xxmOluqRm1ChO+8DnlEXHpcEIQnCecXtC/IrcCxKFex6xbiK89u9w4e/ZbtyZ/g dRNtJlSa/B+vqEQmme6rExMw4QornTdXbAZsX4c8G8wntZY8cvbxUM2HDOagwLfAV7z0 qQKYolfM/Y4k7QZrD1u0AdxO3YmvUFV5yjzgIJ+z9IWmyYVT9Da8o0v12c7Ywg7rC4KC bHstLrs3XgSc5oTNReS0eL1w6v3DKRuSYGK4PDDaPnvgfd1wx3iQ6IM8VBiE7Cr8R8lo lMfLNddjmJY0VzTjymFlh/ZQ6OzKjl5X7i4jjrnQhNbz2iioGJi+RrwvtUf5wELw5cVn 7ufg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=Ylq9nixHOf3PGUZMALamUB+rBaunU9uSACfgzI0LaCE=; b=fNpP5t4HPoNXxrI4ak3GqysHpQNetQ6HWXV+XyFlEWHTndR/z+eGiK5pDFK4eLlYiR YrAjUGwOK46KlN0tZ5CjdpcuZkr3IJFC1LkBMKyOtOW5pjDgqSUegZXPllXb2kwG53aF uwEw2yLB8g1qJJFmu05Q3pJabaNtaWG4o5Zw9/k63uZbka/NSkYfmGcUhEPge4/PZa22 qOY+0nUy/7+94uI689j6CBl5V96xh4TpBjuTrG1VotUwCEIMEWpoDWOns6EWrgpydPqe W8Oc74sZqHjrEFuShR8VCtN1MGeLX8Gvg3OQ6hctwb8oFb2PVPpElnw2+zTon0O48lpJ 3/BQ==
X-Gm-Message-State: AOAM530BsJzbzopVlUi0IHKDDlvZktUhlWB5HWpPDhwAP6Sar0fNWl8/ 2CxvGweupvyn5zP5pyOOPnU4SoRASF3chw==
X-Google-Smtp-Source: ABdhPJybCn5+AhN5e71hs4JztMVMZwEjp9Ze/SMzJDCSpWAapEh9RHiy+fwWX7Wp3apA8snP8AmEVw==
X-Received: by 2002:a17:902:ee86:b029:da:612b:7de1 with SMTP id a6-20020a170902ee86b02900da612b7de1mr3884665pld.38.1606602057616; Sat, 28 Nov 2020 14:20:57 -0800 (PST)
Received: from mike-mac.lan (107-182-42-33.volcanocom.com. [107.182.42.33]) by smtp.gmail.com with ESMTPSA id h11sm11776682pfn.27.2020.11.28.14.20.56 for <ietf@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 28 Nov 2020 14:20:57 -0800 (PST)
Subject: Re: Long time to standard (was: Re: Google, etc, and their proprietary protocols)
To: ietf@ietf.org
References: <d00258b3-ef73-ee93-a47d-2831738d32d1@mtcc.com> <CAHw9_iLcYFkOuRgiyKLH-OnBs1i+Y-8L4ds3areJiT9EbxFs+w@mail.gmail.com> <20201128040004.GA11260@mit.edu> <a1d64f28-d04c-a192-1f3c-a79d0a6945a4@huitema.net>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <0cae8f00-2afb-fdca-aa4c-3c9cc3a75a49@mtcc.com>
Date: Sat, 28 Nov 2020 14:20:55 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.5.0
MIME-Version: 1.0
In-Reply-To: <a1d64f28-d04c-a192-1f3c-a79d0a6945a4@huitema.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/N2zYhwH4S_O35qecWl63u_djWkk>
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: Sat, 28 Nov 2020 22:21:00 -0000

On 11/27/20 8:20 PM, Christian Huitema wrote:
> In fact, Google kept shipping successive versions of "Google QUIC" in 
> their products during all these years, progressively integrating parts 
> of the IETF design in their code, until arriving at interoperability 
> with the IETF specification a few months ago, following draft-29. 
> Other companies followed the same pattern, deploying successive drafts 
> in controlled environments such as on an internal "back end" network, 
> or between a proprietary app an their servers. They learned a lot in 
> the process, and contributed to the standardization.
>
> One way the working group dealt with that was by conducting regular 
> interoperability tests based on specific draft numbers, which ensured 
> that some draft versions will be well supported by many 
> implementations. Another way was the support of version negotiation in 
> the protocol. But mostly, the rule was to only deploy interim QUIC 
> versions on systems that supported frequent software upgrades.
>
> I don't know whether this will apply to other IETF endeavors, but it 
> is probably worth documenting.
>
>
DIdn't the same sort of process happen with websockets? Is that back and 
forth really that unusual?

Mike