Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace suppressSequenceNumber with transport-specific behavior #51

Merged
merged 2 commits into from
Mar 7, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
9 changes: 4 additions & 5 deletions draft-ietf-tls-ctls.md
Original file line number Diff line number Diff line change
Expand Up @@ -410,11 +410,10 @@ transports (e.g., TCP), the length field MUST be present. For use over other
transports length information may be inferred from the underlying layer.

Normal DTLS does not provide a mechanism for suppressing the sequence number
field entirely. In cases where a sequence number is not required (e.g., when a
reliable transport is in use), a cTLS implementation may suppress it by setting
the `suppressSequenceNumber` flag in the compression profile being used (see
{{template-based-specialization}}). When this flag is enabled, the S bit in the
configuration octet MUST be cleared.
field entirely. When a reliable, ordered transport (e.g., TCP) is in use, the
S bit in the configuration octet MUST be cleared and the sequence number
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

S = stream transport ?

MUST be omitted. When an unreliable transport is in use, the S bit
has its usual meaning and the sequence number MUST be included.


## Handshake Layer
Expand Down