Re: [TLS] ECH - handling retry config with different public name?

2021-11-06 Thread Stephen Farrell
Hiya, On 06/11/2021 22:20, Martin Thomson wrote: I assume that you might add "just once" there. Or at least a limited number of times. Right. I think that's in the spec already. Cheers, S. Infinite regress seems like something worth avoiding. outer1 -> outer2 -> outer1 is likely not a

Re: [TLS] ECH - handling retry config with different public name?

2021-11-06 Thread Martin Thomson
I assume that you might add "just once" there. Or at least a limited number of times. Infinite regress seems like something worth avoiding. outer1 -> outer2 -> outer1 is likely not a great outcome. On Sat, Nov 6, 2021, at 02:20, David Benjamin wrote: > That's my inclination as well. It's an

Re: [TLS] ECH - handling retry config with different public name?

2021-11-05 Thread David Benjamin
That's my inclination as well. It's an odd thing for a server to do, but it seems fine to just retry with the new config without much fuss? On Fri, Nov 5, 2021 at 10:18 AM Stephen Farrell wrote: > > Hiya, > > Bit of a corner case I'm not sure about. Apologies > if this has come up before. > >

[TLS] ECH - handling retry config with different public name?

2021-11-05 Thread Stephen Farrell
Hiya, Bit of a corner case I'm not sure about. Apologies if this has come up before. The scenario: - inner SNI is inner.example - ECHConfig from inner.example's DNS has outer.example as public_name - client authenticates with ClientHelloOuter and the ServerHello contains retry_configs