An update to a meeting session request has just been submitted by Sean Turner,
a Chair of the tls working group.
-
Working Group Name: Transport Layer Security
Area Name: Security Area
Session Requester: Sean Turner
Number of
A new meeting session request has just been submitted by Sean Turner, a Chair
of the tls working group.
-
Working Group Name: Transport Layer Security
Area Name: Security Area
Session Requester: Sean Turner
Number of Sessions: 1
I don't think the upgrade path needs any mention or changes. It's no
different from what we always do: allocate a new code point.
Now that we've removed all the in-protocol combinator schemes from the
early versions, what remains is simply *a* method for defining a NameGroup
out of a pile of
I'd like to reiterate my suggestion: While for now there is concensus for
using concatenation to combine the two shared secrets, we should have a
clear upgrade path if we want to use other combination methods in the
future.
As Douglas notes here [1], the document does commit to concatenation as
