I support adoption on this.
Yes, I'll assist in reviews, etc.
tim
On Wed, Sep 2, 2020 at 12:18 PM Christopher Wood
wrote:
> This email begins the adoption call for draft-rescorla-tls-rfc8446-bis. As
> mentioned [1], this updates language and fixes some errata against RFC8446
> (as identified
I support adoption of this draft, but as a consumer of SSL certificates
which have *17* wildcards on one certificate, I feel that the handling of
wildcard DNS records in this draft needs some more thought.
Tim
On Fri, Jul 27, 2018 at 11:22 PM, Victor Vasiliev <
vasilvv=40google@dmarc.ietf.or
My question would be "what will the HTTP community do if they find this
whole process unwieldy and long"?
Answer They will come up with a solution that does nothing with DANE.
is that an excuse to do something less than perfect for the better good, or
do we live in the world of smug satisfaction
+1 on sooner rather than later
tim
terrible at picking colors
On Thu, May 7, 2020 at 7:06 PM Stephen Farrell
wrote:
>
>
> On 07/05/2020 23:52, Christopher Wood wrote:
> > Erik raises some compelling reasons to change the name from ECHO
> > to... something else less confusing or misleading [1].
As one of those who yammered constantly about splitting the ECH portions
out of the SVCB document to move it forward, I feel some responsibility.
But I think Erik's text pulled from 9460 does a good job discussing this.
Is it enough text to reference the section in 9460?
tim
just a DNS guy
On Sat
On Fri, Oct 4, 2024 at 11:39 AM Stephen Farrell
wrote:
>
>
> On 10/4/24 16:09, Salz, Rich wrote:
> > https://github.com/tlswg/draft-ietf-tls-svcb-ech/pull/16 "Discuss
> > the impact of resolver selection on security"
>
> That suggested text seems inoffensive to me fwiw.
>
>
Agree with Stephen, th
