Make cTLS extensible #45
Conversation
|
This PR looks good to me. |
| : contains keys that are not required to be understood by the client. | ||
| The server MUST be able to accept connections that do or do not use any of | ||
| these keys. A key MUST NOT appear in both the main template and the optional | ||
| section. |
There was a problem hiding this comment.
I like the general idea here, but it's not clear to me how this is going to work. Like how do I infer whether the key is in use or not? Can you give an example?
There was a problem hiding this comment.
Yes, this can only be used for keys that the server can disambiguate. I'm not necessarily claiming that any such keys have been defined, but I think we might as well agree ahead of time on where to put them, for forwards-compatibility.
My main point here is that all the other keys are not optional, and if you don't recognize one then you can't use the template.
There was a problem hiding this comment.
OK, that's fair. Could you add some text to the effect about disambiguate and I'll merge thjs?
Fixes #39