Re: [rtcweb] Terminate or Reject streams by setting port to zero in SDP

On 07/20/2012 07:39 AM, Harald Alvestrand wrote:
> On 07/17/2012 07:35 AM, José Luis Millán wrote:
>> Hi,
>>
>> Offer/Answer Model with Session Description Protocol states that a
>> stream can be terminated or rejected by setting the port to zero in
>> the Offer/Answer SDP respectively.
>>
>> How can this be achieved with PeerConnection?
> Terminating a stream: Remove all references to the stream in the SDP
> "msid" attributes.
>
> draft-alvestrand-rtcweb-msid-02 section 4.
Agree to that part.
>
> Rejecting a stream: draft-westerlund-avtext-rtp-stream-pause-02 suggests
> one way to do this (I have not reviewed it).
I don't think that draft covers rejecting a stream. It is more related 
to pause/resume (which correlates to enable/disable and mute/unmute in 
API terminology).

Which leads to the question: If we use a solution like described in 
draft-alvestrand-rtcweb-msid-02 to signal the mapping between 
MediaStream's and MediaStreamTracks and ssrcs (RTP) (which makes sense 
to me), how should rejection be signaled? And should the receiver be 
able to accept certain added ssrc's in a new offer while rejecting 
others, or should the entire offer be rejected (and the presumable the 
current state of the session be maintained)?

In 3264 it is said "The means for rejecting an offer are dependent on 
the higher layer protocol.", but that does not seem appropriate in this 
case.
>
> Note: An m-line (the entity in SDP that carries the port number) does
> NOT correspond to a WebRTC MediaStream.
>
>>
>> Thanks in advance.
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>