[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ietf-tls
Subject:    Re: [TLS] Bikeshedding ECHO
From:       Eric Rescorla <ekr () rtfm ! com>
Date:       2020-05-21 19:56:08
Message-ID: CABcZeBN3xFNw39WP8tJ009G=P--FG=C-kLfHMCLoXzBb6S8rYg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


I actually already merged it :)

On Thu, May 21, 2020 at 12:48 PM Christopher Wood <caw@heapingbits.net>
wrote:

> To make it official, here's a PR making that change:
>
>    https://github.com/tlswg/draft-ietf-tls-esni/pull/236
>
> Please have a look. I'll merge in the next day or so.
>
> Thanks!
> Chris (no hat)
>
> On Thu, May 21, 2020, at 8:58 AM, Sean Turner wrote:
> >  Okay let's call this done! ECH it is.
> >
> > spt
> >
> > Sent from my iPhone
> >
> > > On May 21, 2020, at 11:53, Erik Nygren <erik+ietf@nygren.org> wrote:
> > >
> > > Are there any objections to "ECH" or should we just go with that?
> > > (I'd like to update the parameter name in SRVB/HTTPSSVC accordingly
> based on what gets decided.)
> > >
> > >
> > > On Wed, May 20, 2020 at 11:37 PM Tommy Pauly <tpauly@apple.com> wrote:
> > >> ECH is good. Go for it!
> > >>
> > >> Tommy
> > >>
> > >>> On May 20, 2020, at 11:34 AM, Erik Nygren <erik+ietf@nygren.org
> <mailto:erik%2Bietf@nygren.org>> wrote:
> > >>>
> > >>>
> > >>> ECH works for me. (I really don't care between ECH and ETCH and
> thing both are fine.)
> > >>>
> > >>>  Erik
> > >>>
> > >>>
> > >>> On Wed, May 20, 2020 at 2:20 PM Christopher Wood <
> caw@heapingbits.net> wrote:
> > >>>> On Tue, May 19, 2020, at 8:18 PM, Filippo Valsorda wrote:
> > >>>>  > As a data point, I was fairly confused when ECHO came up in
> > >>>>  > conversation, and had to stop to ask what it was. I think I
> would have
> > >>>>  > had a better chance of figuring it out from context or search if
> it
> > >>>>  > were called ECH, but don't have a strong preference for any
> specific
> > >>>>  > name.
> > >>>>  >
> > >>>>  > ECH does have a remarkable short Wikipedia disambiguation list,
> FWIW.
> > >>>>  > https://en.wikipedia.org/wiki/ECH
> > >>>>
> > >>>>  ECH also works for me.
> > >>>>
> > >>>>  Best,
> > >>>>  Chris (no hat)
> > >>>>
> > >>>>  _______________________________________________
> > >>>>  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
> > _______________________________________________
> > 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
>

[Attachment #5 (text/html)]

<div dir="ltr">I actually already merged it :)<br></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 21, 2020 at 12:48 \
PM Christopher Wood &lt;<a \
href="mailto:caw@heapingbits.net">caw@heapingbits.net</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">To make it official, \
here&#39;s a PR making that change:<br> <br>
     <a href="https://github.com/tlswg/draft-ietf-tls-esni/pull/236" rel="noreferrer" \
target="_blank">https://github.com/tlswg/draft-ietf-tls-esni/pull/236</a><br> <br>
Please have a look. I&#39;ll merge in the next day or so.<br>
<br>
Thanks!<br>
Chris (no hat)<br>
<br>
On Thu, May 21, 2020, at 8:58 AM, Sean Turner wrote:<br>
&gt;   Okay let's call this done! ECH it is.<br>
&gt; <br>
&gt; spt<br>
&gt; <br>
&gt; Sent from my iPhone<br>
&gt; <br>
&gt; &gt; On May 21, 2020, at 11:53, Erik Nygren &lt;<a \
href="mailto:erik%2Bietf@nygren.org" target="_blank">erik+ietf@nygren.org</a>&gt; \
wrote:<br> &gt; &gt; <br>
&gt; &gt; Are there any objections to &quot;ECH&quot; or should we just go with \
that?<br> &gt; &gt; (I&#39;d like to update the parameter name in SRVB/HTTPSSVC \
accordingly based on what gets decided.)<br> &gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; On Wed, May 20, 2020 at 11:37 PM Tommy Pauly &lt;<a \
href="mailto:tpauly@apple.com" target="_blank">tpauly@apple.com</a>&gt; wrote:<br> \
&gt; &gt;&gt; ECH is good. Go for it!<br> &gt; &gt;&gt; <br>
&gt; &gt;&gt; Tommy<br>
&gt; &gt;&gt; <br>
&gt; &gt;&gt;&gt; On May 20, 2020, at 11:34 AM, Erik Nygren &lt;<a \
href="mailto:erik%2Bietf@nygren.org" target="_blank">erik+ietf@nygren.org</a> \
&lt;mailto:<a href="mailto:erik%252Bietf@nygren.org" \
target="_blank">erik%2Bietf@nygren.org</a>&gt;&gt; wrote:<br> &gt; &gt;&gt;&gt; <br>
&gt; &gt;&gt;&gt; <br>
&gt; &gt;&gt;&gt; ECH works for me. (I really don&#39;t care between ECH and ETCH and \
thing both are fine.)<br> &gt; &gt;&gt;&gt; <br>
&gt; &gt;&gt;&gt;   Erik<br>
&gt; &gt;&gt;&gt; <br>
&gt; &gt;&gt;&gt; <br>
&gt; &gt;&gt;&gt; On Wed, May 20, 2020 at 2:20 PM Christopher Wood &lt;<a \
href="mailto:caw@heapingbits.net" target="_blank">caw@heapingbits.net</a>&gt; \
wrote:<br> &gt; &gt;&gt;&gt;&gt; On Tue, May 19, 2020, at 8:18 PM, Filippo Valsorda \
wrote:<br> &gt; &gt;&gt;&gt;&gt;   &gt; As a data point, I was fairly confused when \
ECHO came up in <br> &gt; &gt;&gt;&gt;&gt;   &gt; conversation, and had to stop to \
ask what it was. I think I would have <br> &gt; &gt;&gt;&gt;&gt;   &gt; had a better \
chance of figuring it out from context or search if it <br> &gt; &gt;&gt;&gt;&gt;   \
&gt; were called ECH, but don&#39;t have a strong preference for any specific <br> \
&gt; &gt;&gt;&gt;&gt;   &gt; name.<br> &gt; &gt;&gt;&gt;&gt;   &gt; <br>
&gt; &gt;&gt;&gt;&gt;   &gt; ECH does have a remarkable short Wikipedia \
disambiguation list, FWIW. <br> &gt; &gt;&gt;&gt;&gt;   &gt; <a \
href="https://en.wikipedia.org/wiki/ECH" rel="noreferrer" \
target="_blank">https://en.wikipedia.org/wiki/ECH</a><br> &gt; &gt;&gt;&gt;&gt; <br>
&gt; &gt;&gt;&gt;&gt;   ECH also works for me.<br>
&gt; &gt;&gt;&gt;&gt; <br>
&gt; &gt;&gt;&gt;&gt;   Best,<br>
&gt; &gt;&gt;&gt;&gt;   Chris (no hat)<br>
&gt; &gt;&gt;&gt;&gt; <br>
&gt; &gt;&gt;&gt;&gt;   _______________________________________________<br>
&gt; &gt;&gt;&gt;&gt;   TLS mailing list<br>
&gt; &gt;&gt;&gt;&gt; <a href="mailto:TLS@ietf.org" \
target="_blank">TLS@ietf.org</a><br> &gt; &gt;&gt;&gt;&gt; <a \
href="https://www.ietf.org/mailman/listinfo/tls" rel="noreferrer" \
target="_blank">https://www.ietf.org/mailman/listinfo/tls</a><br> &gt; &gt;&gt;&gt; \
_______________________________________________<br> &gt; &gt;&gt;&gt; TLS mailing \
list<br> &gt; &gt;&gt;&gt; <a href="mailto:TLS@ietf.org" \
target="_blank">TLS@ietf.org</a><br> &gt; &gt;&gt;&gt; <a \
href="https://www.ietf.org/mailman/listinfo/tls" rel="noreferrer" \
target="_blank">https://www.ietf.org/mailman/listinfo/tls</a><br> &gt; &gt; \
_______________________________________________<br> &gt; &gt; TLS mailing list<br>
&gt; &gt; <a href="mailto:TLS@ietf.org" target="_blank">TLS@ietf.org</a><br>
&gt; &gt; <a href="https://www.ietf.org/mailman/listinfo/tls" rel="noreferrer" \
target="_blank">https://www.ietf.org/mailman/listinfo/tls</a><br> &gt; \
_______________________________________________<br> &gt; TLS mailing list<br>
&gt; <a href="mailto:TLS@ietf.org" target="_blank">TLS@ietf.org</a><br>
&gt; <a href="https://www.ietf.org/mailman/listinfo/tls" rel="noreferrer" \
target="_blank">https://www.ietf.org/mailman/listinfo/tls</a><br> &gt;<br>
<br>
_______________________________________________<br>
TLS mailing list<br>
<a href="mailto:TLS@ietf.org" target="_blank">TLS@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/tls" rel="noreferrer" \
target="_blank">https://www.ietf.org/mailman/listinfo/tls</a><br> </blockquote></div>



_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic