On Wed, Jan 4, 2023 at 7:50 AM Kristijan Sedlak
wrote:
> ...how will an endpoint correctly distinguish between multiple,
CID-ext-based CTLSClientPlaintext requests and CTLSServerPlaintext
responses when the same socket is used for client and server communication.
On Wed, 4 Jan 2023 at 15:29, Ben
On Thu, Jan 5, 2023 at 6:31 AM Ben Smyth wrote:
> On Wed, Jan 4, 2023 at 7:50 AM Kristijan Sedlak
> wrote:
> > ...how will an endpoint correctly distinguish between multiple,
> CID-ext-based CTLSClientPlaintext requests and CTLSServerPlaintext
> responses when the same socket is used for client
On Thu, Jan 5, 2023 at 9:37 AM Eric Rescorla wrote:
...
> On Wed, 4 Jan 2023 at 17:10, Eric Rescorla wrote:
>> > When would this actually happen?
>>
>> Assuming this could happen, then the RFC should surely mention the
>> possibility, and perhaps be reworked to avoid raising an error.
>>
>
> Per
On Fri, Jan 6, 2023, at 01:46, Ben Schwartz wrote:
> In Datagram cTLS (as of -07), this is not possible. The parsing of
> handshake messages depends on prior knowledge of who is the client and
> who is the server. This is because CTLSServerPlaintext and
> CTLSClientPlaintext are different stru
