Re: [TLS] Bikeshedding ECHO

Rob Sayre <sayrer@gmail.com> Sun, 10 May 2020 19:38 UTC

Return-Path: <sayrer@gmail.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 53DA63A0B4D for <tls@ietfa.amsl.com>; Sun, 10 May 2020 12:38:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 (2048-bit key) header.d=gmail.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 JALX8GtD_Sci for <tls@ietfa.amsl.com>; Sun, 10 May 2020 12:38:07 -0700 (PDT)
Received: from mail-il1-x12b.google.com (mail-il1-x12b.google.com [IPv6:2607:f8b0:4864:20::12b]) (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 268923A0B4B for <TLS@ietf.org>; Sun, 10 May 2020 12:38:07 -0700 (PDT)
Received: by mail-il1-x12b.google.com with SMTP id m5so6405987ilj.10 for <TLS@ietf.org>; Sun, 10 May 2020 12:38:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=QgPjqAFRGmLvE/d0lds4gDsmKFJbGvM6A3rq0yBmsFI=; b=bQn3LvGtqW4p2j5Iob2jffGCTmZN9mJ9xdJQ9dftVxw4BbIM3hPIDFYWYWKBIYfqQG 6wAIkQvIaM0geRZ13e7Iz8q1bNX+b5LGe7sMuZ8QHlsxYvdhy6zwx8qvbDhPmXUdbiUq ofGjKSeSSkRD98LsRvXM59JeytD5N6cgsjsq5MyLjsusl6cTTM92uCVmgZXecRaE1a4+ oueLvzlEqCWQA6ZxYrn7ImEbHyNYgh/VSM5IS6RgzkCgES+K7WK8GYJkvCjZKTSR4Ib6 6aHlBnB92xhbgCzxl8wWkGfe1oYGEJfK9f7g2qqEpI9S52u2RpG8B4g79YvgW7kvqtuF myfA==
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=QgPjqAFRGmLvE/d0lds4gDsmKFJbGvM6A3rq0yBmsFI=; b=Q9iLLsjygwVPChJ5E5GvSa8OVX4W2Dsy4t+sU+aRwq3l/Msqg48WHy9D/XFJ4mJLba EvH1yebyNcS8aXSjoAYsgCqzaGLraIsHS7ViK0Gkeg0ta0rzCt4mUM4BUl8Lp1FEzU3j Dkd1YivEV1sF4XNmhELGM6Mtczg7KsyXoyZiQCCsIMzZ8yDCtipmYE/QHbi9swZApLLc FjoBZb1AvmvbJeGb+90oGPtwaqJMHduP8HPb7IQBe2g13kenzm6m7UYQusCkWIuZ6wBz TWN2pd6ILgeVrWWFCUnC2j5emZw2x0g6hgd8FclCSsQz9hlOMZMRoWc1+7oQzCcw8ELX 6v8A==
X-Gm-Message-State: AGi0PuZnxnJJHNCHEdXX6kZEBwRYerFkVDrP6lCBRDwxw0aolTlv8L0t Gd2k4Xlul7u1bL4YYpwelDWFIwvEqW9dSlqzYbc=
X-Google-Smtp-Source: APiQypLHEIRauXwbiNWsA/SuOTsvBilvt0YRStHE/A17rxqDV+O7RstgtRZMqqwYt8lhEVR2H2cLRdona6y38XNZoYA=
X-Received: by 2002:a92:d3c5:: with SMTP id c5mr13161706ilh.73.1589139486222; Sun, 10 May 2020 12:38:06 -0700 (PDT)
MIME-Version: 1.0
References: <a8fc0d18-7fe0-4bee-84d3-767fadb914a9@www.fastmail.com> <FDD2528E-679C-4248-A8E0-EEB3006693F9@apple.com> <CAKC-DJiRbkuYruxc=UV0fR1Bd6dJSNUJv6pr8z-TvLkgwd0SmQ@mail.gmail.com> <CABcZeBOH5y42GC1HHzQBofvpWcqVwns357pXUjooQeNwR_ooQA@mail.gmail.com> <20200508224240.GS3811@akamai.com> <CAChr6SydG_MdR8yVcFEi_Y4WruwizS4+jd=a=D1f9ASvD8t68Q@mail.gmail.com> <20200510171031.GT3811@akamai.com>
In-Reply-To: <20200510171031.GT3811@akamai.com>
From: Rob Sayre <sayrer@gmail.com>
Date: Sun, 10 May 2020 12:37:55 -0700
Message-ID: <CAChr6SyPvdy_g8NOE82VH_SEwP0phQPzr_LS8dk9L1JpT8H4Cg@mail.gmail.com>
To: Benjamin Kaduk <bkaduk@akamai.com>
Cc: "TLS@ietf.org" <TLS@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000093306405a5505e47"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/pJNZPE5CXpEAh4bXVH17ODTd9mQ>
Subject: Re: [TLS] Bikeshedding ECHO
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: Sun, 10 May 2020 19:38:12 -0000

On Sun, May 10, 2020 at 10:10 AM Benjamin Kaduk <bkaduk@akamai.com> wrote:

> Hi Rob,
>
> On Fri, May 08, 2020 at 10:51:00PM -0700, Rob Sayre wrote:
> > On Fri, May 8, 2020 at 3:43 PM Benjamin Kaduk <bkaduk=
> > 40akamai.com@dmarc.ietf.org> wrote:
> >
> > > On Fri, May 08, 2020 at 03:38:33PM -0700, Eric Rescorla wrote:
> > > > I rather prefer ECHO.
> > >
> > > Do you have some arguments to dispel the concerns about confusion,
> other
> > > than
> > > your personal preference?
> > >
> >
> > There's no confusion. I couldn't believe the issue was raised (the name
> > does not matter).
>
> I regret to say that I completely fail to understand how you can have
> the confidence to make such a blanket statement ("there's no confusion")
> that
> in principle applies to all human beings, without any apparent supporting
> evidence.


I don't believe it makes sense to demand "evidence" on a completely
subjective issue.

As I wrote in my other email in this thread, not very many people on the
planet are going to need to know what this is. I haven't run into
anyone confused as I've worked on it, and the name was presented 6 months
ago at IETF 106.


> If someone appears and says that they are confused, what are you
> going to tell them?
>

That all of the proposals collide with other meanings too (ETH, ETCH, etc).
This is one reason we expand acronyms on first use in IETF documents.

I don't think there's confusion here, but just preferences and annoyances.
The choice also doesn't matter to me.

thanks,
Rob