Persistence

[mnot]

Dare we specify that clients MAY/SHOULD persist origin information for a given endpoint beyond the lifetime of the connection?

[mcmanus]

origin set is defined per connection not (ironically) per origin.. so I'm not sure how this would work.

[mcmanus]

2 loadbalanced hosts could have different sets of certs even if they answered to the same SNI on the same (public) IP.. I don't know how you could persist that.

[mnot]

Yeah. I think there are a lot of ways we could mess up here.

If you think of the binding as between a set of origins and a connection, AIUI what's being posited here is that it might be interesting to re-attach that binding to a new connection.

It might be interesting if the server could associate a token with a particular set, and then have a dance where its use can be explicitly negotiated. Question is whether it's worth the effort (we've already tried to over-engineer this thing a few times).

[enygren]

Agreed that persisting across connections seems like it may add too much risk and complexity and further additional interactions, especially if we include hosts not found through the DNS. (And doesn't even make sense with some of the changes made to not always rely on DNS.)

[mnot]

Seems like there's no support for this ATM, closing. Comment if you disagree.