On Wed, Feb 27, 2019 at 11:34 PM Kazuho Oku wrote:
>
> Hi Chris,
>
> Thank you for writing down the PRs describing possible designs that we
> might adopt. I think it helps a lot in understanding the details and
> making accurate comparisons.
>
> My comments inline.
>
> 2019年2月27日(水) 8:19 Christoph
Dear Christopher Wood,
The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request.
tls Session 1 (1:00 requested)
Monday, 25 March 2019, Morning Session II 1120-1220
Room Name: Congress Hall 2 size: 350
Stephen, there are a couple complicating factors here where I think we all have
varying knowledge gaps.
* There are two major ways of pointing to a CDN: Direct A/ records and
CNAMEs. The easiest way to handle key update complexities on the part of the
CDN(s) is simply to CNAME the ESN
Hiya,
On 01/03/2019 23:19, Mike Bishop wrote:
> Stephen, there are a couple complicating factors here where I think
> we all have varying knowledge gaps.
Doubtless. I confess lots of ignorance as to how CDNs operate.
>
> * There are two major ways of pointing to a CDN: Direct A/
> record
"The issue" the PRs are attempting to solve, not in terms of ESNI
all-inclusive. I think we're on the same page, then, except that I'm confused
by two things in your reply that appear to be contradictory: You want to
address the content "and structure" of ESNIKeys now, but in the next paragrap
On Fri, Mar 1, 2019 at 3:19 PM Mike Bishop wrote:
>
> Stephen, there are a couple complicating factors here where I think we all
> have varying knowledge gaps.
>
> There are two major ways of pointing to a CDN: Direct A/ records and
> CNAMEs. The easiest way to handle key update complexiti
On Fri, Mar 1, 2019 at 6:27 PM Christopher Wood
wrote:
> On Fri, Mar 1, 2019 at 3:19 PM Mike Bishop wrote:
> >
> > Stephen, there are a couple complicating factors here where I think we
> all have varying knowledge gaps.
> >
> > There are two major ways of pointing to a CDN: Direct A/ recor
On Fri, Mar 1, 2019 at 6:39 PM Nick Sullivan wrote:
>
>
> On Fri, Mar 1, 2019 at 6:27 PM Christopher Wood <
> christopherwoo...@gmail.com> wrote:
>
>> On Fri, Mar 1, 2019 at 3:19 PM Mike Bishop wrote:
>> >
>> > Stephen, there are a couple complicating factors here where I think we
>> all have va
Totally agree that we want to avoid the extra DNS round-trip as often as
possible. However, I see the options in the opposite light – if all you need
is #136, then you can put exact addresses into #137 and get the same behavior.
The question is whether the additional capabilities of #137 are s
