I've no objection to adopting this, though I will note that it is likely of minimal use in the browser context due to the move to isolated storage (which includes tickets). The potential value for cross-origin connections on the same page exists, but it would be good to understand whether the advantages seen are significant enough to justify the effort and complication involved.
Thus, the draft needs to include privacy considerations, particularly regarding cross-origin tracking. I am also of the opinion that it should use flags, but that would depend on changes to the flags draft. On Tue, Nov 10, 2020, at 14:44, Joseph Salowey wrote: > > Based on interest and support expressed at IETF 108, this email starts > the call for adoption of draft-vvv-tls-cross-sni-resumption. The draft > can be found here: > > > > https://tools.ietf.org/html/draft-vvv-tls-cross-sni-resumption-00 > > > > This adoption call will run until November 30, 2020. Please indicate > whether or not you would like to see this draft adopted. Note that this > is an adoption call for the draft as a starting point towards solving > the problem of resumption across SNI values. The final mechanism may > certainly change depending on related efforts, e.g., > draft-ietf-tls-tlsflags. > > > > Thanks, > > > > Sean, Chris and Joe > > _______________________________________________ > 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
