| CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 20:28:53 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
set-cookie: PHPSESSID=d0vjo8gafipj9jqhsvro7oh3ar; path=/
set-cookie: __cf_bm=JD4_9xrSVqEKEW8xMlT5UgLhWz3QFk9cnebwzopAhoo-1760214533-1.0.1.1-bu9mTpe__2xjT2CsGcgkki_QW7yMHABi03zQCkjlKu8VrKCqQUK6Q0XSFO6XIegCe3w4k8dkskTz4iKsEujFpclQth_.0L53NRJqPjbRisM; path=/; expires=Sat, 11-Oct-25 20:58:53 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 98d11b3c7bac6cd6-BLR
alt-svc: h3=":443"; ma=86400
RFC Errata Report » RFC Editor
Search RFCs
The Series
For Authors
Sponsor
RFC Errata
Found 1 record.
Status: Reported (1)
RFC 8864, "Negotiation Data Channels Using the Session Description Protocol (SDP)", January 2021
Source of RFC: mmusic (art)
Errata ID: 7805
Status: Reported
Type: Technical
Publication Format(s) : HTML
Reported By: Harald Alvestrand
Date Reported: 2024-02-09
Section 6.1 says:
In order to avoid SCTP Stream identifier collisions, in alignment with [RFC8832], the endpoint acting as a DTLS client (for the SCTP association used to realize data channels) MUST use even identifier values, and the endpoint acting as a DTLS server MUST use odd identifier values.
It should say:
[RFC8831] does not restrict the SCTP Stream identifiers for data channels negotiated out-of-band. The endpoints are free to assign any numbers to the negotiated data channels; collisions are handled by the usual mechanisms used to avoid SDP signalling glare.
Notes:
The procedures of [RFC8832] are inappropriate in this case, because DCMAP indicates channels negotiated out-of-band and not via DCEP.
At initial offer, the DTLS direction attribute is ACTPASS, so the direction is not known. Thus, the RFC 8832 numbering rule is impossible to apply anyway.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us