IETF Logo Mail Archive

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

Christopher Patton <cpatton@cloudflare.com> Wed, 23 June 2021 23:51 UTC

Return-Path: <cpatton@cloudflare.com>
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 69B813A14C1 for <tls@ietfa.amsl.com>; Wed, 23 Jun 2021 16:51:10 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cloudflare.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 inkeCa-STMeP for <tls@ietfa.amsl.com>; Wed, 23 Jun 2021 16:51:05 -0700 (PDT)
Received: from mail-qk1-x731.google.com (mail-qk1-x731.google.com [IPv6:2607:f8b0:4864:20::731]) (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 7CFD13A14BC for <tls@ietf.org>; Wed, 23 Jun 2021 16:51:05 -0700 (PDT)
Received: by mail-qk1-x731.google.com with SMTP id w21so9728286qkb.9 for <tls@ietf.org>; Wed, 23 Jun 2021 16:51:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=B8IFzzuS0HdrhREbSoYSEQNWWNmphBqjMurOh2k4Al8=; b=ViQh8uenedaAapVSaKo79YcIJsH6pXjHO1V82SKAoQMUg2K+I5pB/5cG53FoLdl9C2 3DKyRSM2FboYQ5Y/UF9hmom8eNYsEsDG5MyWbT8K8tj6sdktaull9+WwTHAH9d2gvjGD bemQQ4XYXIvuuzfTrk0HAE01XE5klzv/Y9MBo=
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=B8IFzzuS0HdrhREbSoYSEQNWWNmphBqjMurOh2k4Al8=; b=lB+sRHIBMLyC+Pnu+6q3MzkhQzL6+C9yTjQTxVwUILbw4mHsCydY1chbKlOHtp8sDD HK4o+H7KNuyo5v9PE9u9y8BXTy9ECtWA/MH2pbNyBgNyGaX5BtS98mD3dNmYatpkCs55 NJ/oAPSqsEzGLk9iFdN9zhvu+62NLN43MjdIxwxANePTvJOZdJJJp01e6DMeaGGZTXHK XnWQAY6OFZR4K2jS/38H0nZPVFh3/uo9pTzQ7wC4yKkGA1uMwASoDy1jfmtlmLW0Tuyt 7uz1mZPqDL9whEmtcW/t6wlHzupKocFmJhkdVFfMZ0xH/LrF3tP1l6MRXWMERwulpnV2 7tpg==
X-Gm-Message-State: AOAM530Y3s+duzDJTdJkHdit8Z0gu/6yQ30uts7DLITEog3djr/V1FG5 GG9jvQdMVgMwoBi2QmaY6dDMB0s+AgD5qiM9DqqgqQ==
X-Google-Smtp-Source: ABdhPJzFI0Qb2KX5cSepmsA0iMsq4XlW0ieKTKsMpIYzl4qxlooQYvraHAHyYbQs+dKtZNXKIVHMsIGrlRMFMhcOp3k=
X-Received: by 2002:a37:9c84:: with SMTP id f126mr2786057qke.329.1624492263619; Wed, 23 Jun 2021 16:51:03 -0700 (PDT)
MIME-Version: 1.0
References: <363384B1-7CB7-45FC-9FDF-7F8D08B80E81@icloud.com> <1b905089-d3c0-4cce-89d7-658c682a47af@www.fastmail.com> <e55e0e94-4c9c-edd4-4333-ff9e23af6aee@cs.tcd.ie>
In-Reply-To: <e55e0e94-4c9c-edd4-4333-ff9e23af6aee@cs.tcd.ie>
From: Christopher Patton <cpatton@cloudflare.com>
Date: Wed, 23 Jun 2021 16:50:52 -0700
Message-ID: <CAG2Zi20qaiPOtVJuU_L7zckiEqaFhe6P5dWYE_boikCH8zNjAg@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: Martin Thomson <mt@lowentropy.net>, "<tls@ietf.org>" <tls@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000050625a05c577942e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/BLkfb3IC_xxH_EsUOjFfaEQ8a0I>
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:51:10 -0000

+1 to new readers! I think a chronological description would be a good
starting point, though like MT, I suspect there would be rearranging to do
afterwards that would break with a strictly chronological description.

Chris P.

On Wed, Jun 23, 2021 at 4:48 PM Stephen Farrell <stephen.farrell@cs.tcd.ie>
wrote:

>
>
> On 24/06/2021 00:37, Martin Thomson wrote:
> > Whatever you can do to improve the readability of this document would
> > be greatly appreciated.
>
> +1 though I have to admit I've really been mostly looking
> at diffs at this stage - probably some new readers/coders
> are needed,
>
> S.
>
> > 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
> >>
> >
> > _______________________________________________ TLS mailing list
> > TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
> >
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>

v2.23.0 | Report a Bug | By Email