Draft: draft-ietf-rtcweb-jsep

Commentary: of draft - nandakumar . This is a merge of a previously approved PR 
 lgtm 
 LGTM 
 As per discussion in mmusic , to make it abundantly clear that DTLS is to be used even when running over ICE - TCP , the profile name should be TCP / DTLS / RTP / SAVPF . We 'll leave the UDP / TLS / RTP / SAVPF one alone , since that ship has sailed , and it 's less ambiguous . 
   to update to reflect the above . 
 For SCTP , has the correct UDP / DTLS / SCTP and TCP / DTLS / SCTP things that we want to refer to . 
 The action item here is to update this document to use the correct fields as agreed above as if draft - nandakumar was done , and then when that document is fixed we will be good .
Paragraph (version A):
RFC5764 MUST be supported for signaling the UDP/TLS/RTP/SAVPF
RFC5764 and TCP/TLS/RTP/SAVPF I-D.nandakumar-mmusic-proto-iana-
registration RTP profiles.
Paragraph (version B):
RFC5764 MUST be supported for signaling the UDP/TLS/RTP/SAVPF
RFC5764 and TCP/DTLS/RTP/SAVPF I-D.nandakumar-mmusic-proto-iana-
registration RTP profiles.
Paragraph (version A):
For media m= sections, JSEP endpoints MUST support both the "UDP/TLS/
RTP/SAVPF" and "TCP/TLS/RTP/SAVPF" profiles and MUST indicate one of
these two profiles for each media m= line they produce in an offer.
For data m= sections, JSEP endpoints must support both the "UDP/TLS/
SCTP" and "TCP/TLS/SCTP" profiles and MUST indicate one of these two
profiles for each data m= line they produce in an offer.  Because ICE
can select either TCP or UDP transport depending on network
conditions, both advertisements are consistent with ICE eventually
selecting either either UDP or TCP.
Paragraph (version B):
For media m= sections, JSEP endpoints MUST support both the "UDP/TLS/
RTP/SAVPF" and "TCP/DTLS/RTP/SAVPF" profiles and MUST indicate one of
these two profiles for each media m= line they produce in an offer.
For data m= sections, JSEP endpoints must support both the "UDP/DTLS/
SCTP" and "TCP/DTLS/SCTP" profiles and MUST indicate one of these two
profiles for each data m= line they produce in an offer.  Because ICE
can select either TCP or UDP transport depending on network
conditions, both advertisements are consistent with ICE eventually
selecting either either UDP or TCP.
Paragraph (version A):
For data m= sections, JSEP endpoints MUST support receiving the
"UDP/ TLS/SCTP", "TCP/TLS/SCTP", or "DTLS/SCTP" (for backwards
compatibility) profiles.
Paragraph (version B):
For data m= sections, JSEP endpoints MUST support receiving the
"UDP/ DTLS/SCTP", "TCP/DTLS/SCTP", or "DTLS/SCTP" (for backwards
compatibility) profiles.
Paragraph (version A):
To properly indicate use of DTLS, the <proto> field MUST be set to
"UDP/TLS/RTP/SAVPF", as specified in RFC5764, Section 8, if the
default candidate uses UDP transport, or "TCP/TLS/RTP/SAVPF", as
specified inI-D.nandakumar-mmusic-proto-iana-registration if the
default candidate uses TCP transport.
Paragraph (version B):
To properly indicate use of DTLS, the <proto> field MUST be set to
"UDP/TLS/RTP/SAVPF", as specified in RFC5764, Section 8, if the
default candidate uses UDP transport, or "TCP/DTLS/RTP/SAVPF", as
specified inI-D.nandakumar-mmusic-proto-iana-registration if the
default candidate uses TCP transport.