search

tlswg / dtls13-spec

Repo for DTLS 1.3
32 stars 25 forks source link

Describe how to distinguish DTLS 1.2 and DTLS 1.3 connections. Fixes … #197

Closed ekr closed 3 years ago

ekr commented 3 years ago

…#159

ekr commented 3 years ago

I don't.

On Mon, Dec 28, 2020 at 10:09 PM kaduk notifications@github.com wrote:

@kaduk approved this pull request.

This WFM

In draft-ietf-tls-dtls13.md https://github.com/tlswg/dtls13-spec/pull/197#discussion_r549580317:

@@ -367,7 +367,11 @@ The DTLSCiphertext header is tightly bit-packed, as shown below: Fixed Bits: : The three high bits of the first byte of the DTLSCiphertext header are set to

  1. This ensures that the value will fit within the DTLS region when
    • multiplexing is performed as described in {{?RFC7983}}.
    • multiplexing is performed as described in {{?RFC7983}}. It also ensures
    • that it is possible to distinguish encrypted DTLS 1.3 records from
    • encrypted DTLS 1.2 records when they are carried on the same host/port quartet;

(Do we care about "host/port quartet" vs. "5-tuple"? I don't think I do...)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/tlswg/dtls13-spec/pull/197#pullrequestreview-559389477, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIPLIOTRB23GNRCSCU6EJDSXFXA3ANCNFSM4VMT66PA .