Re: [MMUSIC] JSEP Issue #394: What appears in m= lines.

[Paul Kyzivat <[e-mail]>]

On 1/10/17 1:08 PM, Roman Shpount wrote:
> We can do the registration for ICE transport tag in ICE-SIP-SDP. ICE tag
> will indicate that ICE is required for this offer/answer exchange to
> succeed. When ICE transport tag is used, c= and m= SDP line would carry
> no address information and will contain "c=IN IP4 0.0.0.0" and port 9 in
> the m= line. Also, if ICE/ transport tag is used, we should remove the
> requirement for a re-INVITE after ICE nomination process is complete,
> since it serves no purpose when no address is specified in c= and m= lines.
>
> If we are not going to define ICE/ transport, then I propose the following:
>
> 1. When c= line is set to "IN IP4 0.0.0.0" and m= line is set to port 9,
> so that these lines carry no valid address information as it is
> specified in JSEP, protocol should be UDP/DTLS/SAVPF for RTP
> or UDP/DTLS/SCTP for data

To do this cleanly, IMO there should be no singling out of IP4. The fact 
is that in this case the c= line is not needed. (And this isn't the only 
case where it isn't. It also isn't needed for MSRP and for websockets - 
things that use URLs in attributes instead of c=.) So perhaps we should 
revise 4566bis to make c= optional for m= lines where it isn't needed. 
Or define a new addrtype for use in c= (e.g. simply "IP" or "IP4/6") and 
define a placeholder address value for this case. For example:

   c=IN IP -

> 2. When c= line and m= line carry valid address information, protocol
> should match the candidate specified in c= and m= lines.
>
> 3. In cases when c= line and m= line carry valid address
> information, when initial offer and answer are generated, they must
> include UDP candidates and UDP candidates must be used as defaults. Once
> ICE nomination process is complete, only the active candidate pair MUST
> be included in SDP, and the transport for the active pair must be used.

I think this could be handled by having different <proto> values:

ICE/DTLS      DTLS over either UDP or TCP
ICE/UDP/DTLS  DTLS over only UDP
ICE/TCP/DTLS  DTLS over only TCP

ICE/DTLS/RTP/SAVPF      Like above, but for RTP/SAVPF
ICE/UDP/DTLS/RTP/SAVPF  "
ICE/TCP/DTLS/RTP/SAVPF  "

So this allows restricting the type of candidates that are allowed, or 
not. And it avoids "lying" about the type that is to be used.

	Thanks,
	Paul