Re: [TLS] Call for adoption of draft-vvv-tls-cross-sni-resumption

nd Joe > > On Mon, Nov 9, 2020 at 7:44 PM 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: >> >> >>

Re: [TLS] Call for adoption of draft-vvv-tls-cross-sni-resumption

I also support adoption. > On Dec 3, 2020, at 4:17 PM, David Schinazi wrote: > > I support adoption of draft-vvv-tls-cross-sni-resumption. > > David > > On Thu, Dec 3, 2020 at 1:49 PM Salz, Rich > wrote: > > > Hmmm... I think it probably goes in this

Re: [TLS] Call for adoption of draft-vvv-tls-cross-sni-resumption

I support adoption of draft-vvv-tls-cross-sni-resumption. David On Thu, Dec 3, 2020 at 1:49 PM Salz, Rich wrote: > > >- Hmmm... I think it probably goes in this draft, but I'm open to >being wrong. > > > > That’s okay with me. > ___ > TLS

Re: [TLS] Call for adoption of draft-vvv-tls-cross-sni-resumption

* Hmmm... I think it probably goes in this draft, but I'm open to being wrong. That’s okay with me. ___ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls

Re: [TLS] Call for adoption of draft-vvv-tls-cross-sni-resumption

I think, like the tracking issue, it should go in both. (I wrote https://github.com/tlswg/tls13-spec/pull/1205 to try to capture the tracking case.) This draft should definitely (re)-state it because TLS preferences are most common keyed by domain name. So even if it's in TLS itself, it's worth

Re: [TLS] Call for adoption of draft-vvv-tls-cross-sni-resumption

Hmmm... I think it probably goes in this draft, but I'm open to being wrong. On Thu, Dec 3, 2020 at 12:46 PM Salz, Rich wrote: > >- I'm not sure if it's ever been written down anywhere (probably >should be...), but I think resumption is pretty much universally >interpreted as

Re: [TLS] Call for adoption of draft-vvv-tls-cross-sni-resumption

*I'm not sure if it's ever been written down anywhere (probably should be...), but I think resumption is pretty much universally interpreted as authenticating as the identities presented over the original connection, client and server. That means that, independent of this draft, the

Re: [TLS] Call for adoption of draft-vvv-tls-cross-sni-resumption

On Thu, Dec 3, 2020 at 11:12 AM David Benjamin wrote: > On Thu, Dec 3, 2020 at 1:16 PM Eric Rescorla wrote: > >>If a client certificate has been associated with the session, the >>client MUST use the same policy on whether to present said >>certificate to the server as if it were a

Re: [TLS] Call for adoption of draft-vvv-tls-cross-sni-resumption

On Thu, Dec 3, 2020 at 1:16 PM Eric Rescorla wrote: >If a client certificate has been associated with the session, the >client MUST use the same policy on whether to present said >certificate to the server as if it were a new TLS session. For >instance, if the client would show

Re: [TLS] Call for adoption of draft-vvv-tls-cross-sni-resumption

Document: draft-vvv-tls-cross-sni-resumption-00.txt I think we should adopt this draft. Some review comments below. S 1. Section 4.2.11). However, in the absence of additional signals, it discourages using a session ticket when the SNI value does not match ([RFC8446], Section 4.6.1),

Re: [TLS] Call for adoption of draft-vvv-tls-cross-sni-resumption

I support the draft and will review. ___ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls

Re: [TLS] Call for adoption of draft-vvv-tls-cross-sni-resumption

, Sean, Chris and Joe On Mon, Nov 9, 2020 at 7:44 PM 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/d

Re: [TLS] Call for adoption of draft-vvv-tls-cross-sni-resumption

I support adopting this draft. On Tue, Nov 10, 2020 at 5:38 PM Ryan Sleevi wrote: > On Tue, Nov 10, 2020 at 5:29 PM Victor Vasiliev 40google@dmarc.ietf.org> wrote: > >> On Mon, Nov 9, 2020 at 11:51 PM Martin Thomson wrote: >> >>> I've no objection to adopting this, though I will note that

Re: [TLS] Call for adoption of draft-vvv-tls-cross-sni-resumption

On Tue, Nov 10, 2020 at 5:29 PM Victor Vasiliev wrote: > On Mon, Nov 9, 2020 at 11:51 PM Martin Thomson wrote: > >> 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).

Re: [TLS] Call for adoption of draft-vvv-tls-cross-sni-resumption

On Wed, Nov 11, 2020, at 09:28, Victor Vasiliev wrote: > > 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. > > I considered

Re: [TLS] Call for adoption of draft-vvv-tls-cross-sni-resumption

On Tue, Nov 10, 2020, at 22:05, Stephen Farrell wrote: > I'd be more in the "not yet" bracket for this. As Martin > mentions this'd seem to create a possibly attractive way > to do more tracking, so I think we ought try understand > how that might fit into the wider set of new things (e.g. > the

Re: [TLS] Call for adoption of draft-vvv-tls-cross-sni-resumption

Hiya, On 10/11/2020 03: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

Re: [TLS] Call for adoption of draft-vvv-tls-cross-sni-resumption

. 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

[TLS] Call for adoption of draft-vvv-tls-cross-sni-resumption

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