IETF Logo Mail Archive

Re: Dealing with Design issues following Last Call

Christian Huitema <huitema@huitema.net> Fri, 18 December 2020 21:36 UTC

Return-Path: <huitema@huitema.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89BBD3A0827 for <quic@ietfa.amsl.com>; Fri, 18 Dec 2020 13:36:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level:
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] 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 9TXN8XeZXx78 for <quic@ietfa.amsl.com>; Fri, 18 Dec 2020 13:36:57 -0800 (PST)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEA7C3A0825 for <quic@ietf.org>; Fri, 18 Dec 2020 13:36:56 -0800 (PST)
Received: from xse208.mail2web.com ([66.113.196.208] helo=xse.mail2web.com) by mx136.antispamcloud.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1kqNQg-0016Wj-QI for quic@ietf.org; Fri, 18 Dec 2020 22:36:52 +0100
Received: from xsmtp22.mail2web.com (unknown [10.100.68.61]) by xse.mail2web.com (Postfix) with ESMTPS id 4CyMdD0NNJzDRj for <quic@ietf.org>; Fri, 18 Dec 2020 13:36:48 -0800 (PST)
Received: from [10.5.2.12] (helo=xmail02.myhosting.com) by xsmtp22.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1kqNQd-0004o4-UI for quic@ietf.org; Fri, 18 Dec 2020 13:36:47 -0800
Received: (qmail 17951 invoked from network); 18 Dec 2020 21:36:47 -0000
Received: from unknown (HELO [192.168.1.106]) (Authenticated-user:_huitema@huitema.net@[172.58.43.253]) (envelope-sender <huitema@huitema.net>) by xmail02.myhosting.com (qmail-ldap-1.03) with ESMTPA for <quic@ietf.org>; 18 Dec 2020 21:36:46 -0000
Subject: Re: Dealing with Design issues following Last Call
To: quic@ietf.org
References: <CALGR9oaAfy0jj=mqX1tiuKdE=Kk=mRHgv15pUUM1XHBMovkw4Q@mail.gmail.com> <20201218201131.GB34756@okhta> <CALGR9oZ13gFRjZERT9z6tEXZY+mxwncpiyPzwCuqK+BJemE98w@mail.gmail.com> <20201218205736.GC34756@okhta>
From: Christian Huitema <huitema@huitema.net>
Message-ID: <0f4fa906-2531-9e97-01eb-b3eb40922bbb@huitema.net>
Date: Fri, 18 Dec 2020 13:36:46 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.1
MIME-Version: 1.0
In-Reply-To: <20201218205736.GC34756@okhta>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-Originating-IP: 66.113.196.208
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.196.208/32
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.208/32@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.64)
X-Recommended-Action: accept
X-Filter-ID: Pt3MvcO5N4iKaDQ5O6lkdGlMVN6RH8bjRMzItlySaT8Z5/sh7ZnfdDp66DGgr0wNPUtbdvnXkggZ 3YnVId/Y5jcf0yeVQAvfjHznO7+bT5x6h2yQpzTslcOqazQkKtAFKj/EwzSHE5FGYwwjsNRPCG4q rQf32t6HsyVINLrxE+XmD6wdmZPcItWbGe10hXJtyz/MWLF6jnm7fdxjsJMmvxOMEZrAzcbOYTBU Hb9yjjUYFoLz2NZcguRHblw+ZN9KE5LN1n8YXzQY0mQUNzTGAwCyMkrqOaHyAipaXQfAHlJH3v3Q 7PQeNoNQjwiv3IhNPpDsdaHHqGG7YXgprtn5XLToE7g5LY8o1a6sSJrLl3xdARnv/HGR54G9CHRY hyVqYO/Ae1h1hLGGi4ebv387hThA9A+LrmkGouiRB8qN/5RbHDa6yUUKFnWNneAcuva3BS+iyyNq bT8dUMXMJ4tUCMj6G37ZfAMLceP5aNHPt26RBupu5v1nytoNnc138GfEJRQ2qC7jjynPIHPNqSn4 QTXUjLjYWQt1/5xnQymMoPsgr/U0flMcy2Vi/IcBgY4arPaiJ1W6hAyiRC61jekdwIcXNugoOEbH RyFULpSjm7jZ1h/HfDRQ5Ig8VhPsPE8NQ/T3Op6Um662jkOH4Bxha66H0vZllc/rYg8OgyqjLNYH 8++7z/4oNSvDHtMdpNZH2JUne37EdXOqrRyXv4wznmNqtRw4Y1cKz96iUSBQOBI11lqdy1V/0aEk MCdb3YpWUo4/+EUytKrR9Md9I2Rs10sdrmCBRCS5c8Csh9FMclNPCC/cRgvQKtcrMMueERx3Gnsw dJgV2sFvs6/mBvsb6bWt6l4sRzyMwXHrlkD6ksmIaIzNoZzswxuMaWjBAlpw7xJlYlOWG7exHkRs q0/tCPUf9oDBqtClgM5jH/om1Q5UomG0v+rwIiID/kwKc8V5Tj9+FRkaOS/DNjANmb8tO61SbYdY AwdpaVzHW7wHO7YhEWyJzIkwSFAW0Pw8uiKeubcolFl/rX+2ReQklqJDASQX2Id+W5hjJNcdGs0+ iHjXODmj5PX/tZQU3bYnWKpb
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Mu2sfF3AJpj-fHdvJfWRpJBf1N4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Dec 2020 21:36:58 -0000

On 12/18/2020 12:57 PM, Dmitri Tikhonov wrote:

> I am trying to prevent a situation where IESG approves -33 on one day and
> the RFC is published two days later and we do not have the changes
> implemented yet.  Then, we would really have to scramble!  Am I naive to
> expect such speedy RFC turnaround?

Typical delay between IESG approval and final publication is 3-4 months. 
Very rarely fewer than 2 months. Could be more if caught behind a big 
queue, or if authors and copy editors get in a long discussion.

-- Christian Huitema

v2.23.0 | Report a Bug | By Email