The SDP spec requires that each line of SDP messages ends with CRLF:
https://tools.ietf.org/html/rfc4566#section-9
Both host and client (Web site) should be updated to comply with this (currently, we generate SDP with just \n endings). Parsing of SDP (on client and host) is already tolerant of \r\n versus \n - we just need to update the SDP messages that we generate.
Note that we apply signature verification to SDP messages, which is based on a normalized form of the SDP with just \n endings. This behavior needs to be preserved for backwards-compatibility. (Alternatively, we could migrate the signature check to a \r\n-based normalization)
Note that this CL:
https://chromium-review.googlesource.com/c/chromium/src/+/966441
recently broke us, because of the line-ending mismatch. Addressing this will avoid similar breakages in future.
Comment 1 by bugdroid1@chromium.org
, Apr 10 2018