On Fri, Jul 27, 2018 at 04:20:43PM -0700, Eric Rescorla wrote:
> Dear TLS WG members.
>
> I am doing my final copy-edits for the TLS 1.3 RFC and I noted one
> technical point and two points I would like to edit for clarity but I
> wanted more eyes on.
>
> 2. https://tools.ietf.org/html/draft-ietf
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
On Sat, Jul 28, 2018 at 12:48 AM, Ilari Liusvaara
wrote:
> On Fri, Jul 27, 2018 at 04:20:43PM -0700, Eric Rescorla wrote:
> > Dear TLS WG members.
> >
> > I am doing my final copy-edits for the TLS 1.3 RFC and I noted one
> > technical point and two points I would like to edit for clarity but I
>
(Reviving this thread to help the WG move forward on getting this
document published)
On 18 Jul 2018, at 5:41, Shumon Huque wrote:
On Wed, Jul 18, 2018 at 4:55 AM Eric Rescorla wrote:
To the extent to which this is true, it's an argument that one should
be
pinning at a different layer.
Minutes for both TLS sessions at IETF 102 have been uploaded:
https://datatracker.ietf.org/doc/minutes-102-tls/
Many thanks to Joe Hall and Gurshabad Grover for taking detailed notes.
Please review the minutes and check for inaccuracies. If anything is
incorrect, please let the chairs know ASAP.
