Re: [TLS] Editorial: chronological order in ECH draft

Martin Thomson <mt@lowentropy.net> Wed, 23 June 2021 23:37 UTC

Return-Path: <mt@lowentropy.net>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F200C3A143B for <tls@ietfa.amsl.com>; Wed, 23 Jun 2021 16:37:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=H30sloQT; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=vf3ugvYk
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 r0prfEL-nVwS for <tls@ietfa.amsl.com>; Wed, 23 Jun 2021 16:37:53 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA4D33A1433 for <tls@ietf.org>; Wed, 23 Jun 2021 16:37:53 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 8CCB85C0217 for <tls@ietf.org>; Wed, 23 Jun 2021 19:37:50 -0400 (EDT)
Received: from imap10 ([10.202.2.60]) by compute4.internal (MEProxy); Wed, 23 Jun 2021 19:37:50 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm2; bh=uyWofmX2eq6EbWQ+yus4Oxs/oeo87ZQ tL49uig9tTFc=; b=H30sloQT1cqodEY3vTqmLVCYJIy3IKXNbfX2xfWIyyIhIIu TDpUqMY8i0ozBeY6HCpi6v+Qedm8Q1DCpr02f7qO6OBMeLTcJdqW8JLGRDZ3cxvA jql1Mym+xyTp1xfIwKCefW6lar7wTVnRM+WuyhaqvrxvEU+eGVdoUFx2qx9b3YVT aPAH2xnxKPcWoJaok+4/EeJidjqOtPeheRZzU+20WMP5sThQ8LtktFcdow9JqtEU 3/iZ5evKkJ/r8bymli8+l5ugmIJ/QcuoXNVStc21mTZJ+6AfYebU0VfDbb8p/OX8 S5xOBOjKF0xRDJoc7CAwAli6sxq/RmlyeapKoig==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=uyWofm X2eq6EbWQ+yus4Oxs/oeo87ZQtL49uig9tTFc=; b=vf3ugvYkcX48kW6u8kwM6D e0qrB0ryHeV8dskIPLx+66VYx9WyeNaMVzpkSsRL5SiF7rU63BDCfa0rvTIeWRM6 SanuvxnEcO8TKlgoCzK/BszuOY7bgkJd80tNxCEOppTNHNyVZQ5rjF8TKIU+WtOZ Qxb7K+6GM3j8vNbXG39HepFnbhQozUbBQIJkPR36kmSYjP92UF+dMK2yJr4JBD7X j/0mKOgxZtD9K+VVOAYp20neZFrcMfAA8W5TBTa/wgKjuuZ+9IX35GGEq7g6pR9v QaKyP6VIGmX1rEeetS57BN0sqNEEPcm7wxECPPhHS9I75gYitc8WuHOU9uvoao3A ==
X-ME-Sender: <xms:zsXTYM1qBq1r0TMHwN-esn6J-LMowmlN1ffV7ptcqokQDa8GnMO8nw> <xme:zsXTYHHDofIe2yAvSOouE4xgIZE74MqN_UD3uhpUzTDmJ_OhiRXVfGgOYZgh7xwob 1dXx_PAw9_dYDODUXY>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfeeggedgvdduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderredtnecuhfhrohhmpedfofgrrhhtihhnucfvhhhomhhsohhnfdcuoehmtheslhho figvnhhtrhhophihrdhnvghtqeenucggtffrrghtthgvrhhnpeffveekgeetvdeuvedtve evtdeuleegveejhfehgfetffeiiefgveefleffteeuleenucffohhmrghinhepghhithhh uhgsrdgtohhmpdhivghtfhdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrh grmhepmhgrihhlfhhrohhmpehmtheslhhofigvnhhtrhhophihrdhnvght
X-ME-Proxy: <xmx:zsXTYE4VBMY8gvsP1rpfLZnck08eAz9RZekTjhiX_nnD19opWGAunQ> <xmx:zsXTYF2SrId4Y8bDKyCCq7SmzWRDn3GmyoD_YQMX76vH_jcgm-sLbA> <xmx:zsXTYPGj-Z--ZAzAzW375c155Wn6KDy3gKoYoYjpUX8G-M_3udSxYg> <xmx:zsXTYDSCGpmCrvM_69hiwF3L1JX8E9uskE0IUM0-w4Wm6plu0-3QFw>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 20AF24E00A2; Wed, 23 Jun 2021 19:37:50 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-530-gd0c265785f-fm-20210616.002-gd0c26578
Mime-Version: 1.0
Message-Id: <1b905089-d3c0-4cce-89d7-658c682a47af@www.fastmail.com>
In-Reply-To: <363384B1-7CB7-45FC-9FDF-7F8D08B80E81@icloud.com>
References: <363384B1-7CB7-45FC-9FDF-7F8D08B80E81@icloud.com>
Date: Thu, 24 Jun 2021 09:37:31 +1000
From: "Martin Thomson" <mt@lowentropy.net>
To: tls@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/nTN_1QCIUU-PMIH9StHL-6KXlxI>
Subject: Re: [TLS] Editorial: chronological order in ECH draft
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jun 2021 23:37:59 -0000

Whatever you can do to improve the readability of this document would be greatly appreciated.  It's a complicated design and I always spend far too much time trying to find answers to my questions.  A better structure would be appreciated.

I do find that questions aren't always about behaviour.  They are also about protocol elements, and those a scattered piecemeal throughout.  So I would be disappointed if any restructuring were limited to just getting the time sequence straightened out.

On Thu, Jun 24, 2021, at 09:04, Carrick Bartle wrote:
> Hi all,
> 
> I'm bringing https://github.com/tlswg/draft-ietf-tls-esni/issues/412 to 
> the list since it looks like we're (hopefully) getting close to the end 
> game with ECH.
> 
> The ECH draft is currently organized such that it describes all client 
> behavior and then all server behavior. Personally, I find this very 
> confusing to follow, and I'm constantly having to flip back and forth 
> between sections (which themselves constantly refer to each other). 
> Does anyone object to my rearranging the content to be in more of the 
> order in which things occur rather than being divided into client and 
> server sections? Of course, depending on how I do it, it could end up 
> being *more* confusing, but I just wanted to see if people were opposed 
> to it in principle.
> 
> Carrick
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>