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

Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com> Sat, 21 July 2012 12:24 UTC

Return-Path: <stefan.lk.hakansson@ericsson.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69CC821F859F for <rtcweb@ietfa.amsl.com>; Sat, 21 Jul 2012 05:24:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.03
X-Spam-Level:
X-Spam-Status: No, score=-6.03 tagged_above=-999 required=5 tests=[AWL=0.219, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ds9oYnSpym5F for <rtcweb@ietfa.amsl.com>; Sat, 21 Jul 2012 05:24:47 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 43BD721F8594 for <rtcweb@ietf.org>; Sat, 21 Jul 2012 05:24:47 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f6c6d000001cc5-a8-500a9fc87ce5
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id E0.6C.07365.8CF9A005; Sat, 21 Jul 2012 14:25:45 +0200 (CEST)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.3.264.0; Sat, 21 Jul 2012 14:25:44 +0200
Message-ID: <500A9FC7.2000802@ericsson.com>
Date: Sat, 21 Jul 2012 14:25:43 +0200
From: Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CABw3bnMTAh6_fWEE-p8k2kd6kD=y+s3XVNWdA_rCBYs6OzA=jQ@mail.gmail.com> <5008EF08.6080803@alvestrand.no>
In-Reply-To: <5008EF08.6080803@alvestrand.no>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrFJMWRmVeSWpSXmKPExsUyM+Jvre7J+VwBBgcn8lms/dfO7sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujBkXX7IWXOKr+HtzP2sDYxNPFyMnh4SAicTrnzvYIWwxiQv3 1rN1MXJxCAmcYpTYtGMnI4SznFHi0eITLCBVvALaEueWPASzWQRUJWb+/wvWzSZgI7G2ewoT iC0qECKx5tsURoh6QYmTM5+A1YsICEtsfdULVMPBISwQJPH2vQBIWEigUGL/yVvMIDangK7E 8zePWEFsZgFbiQtzrrNA2PISzVtnM0PU60q8e32PdQKjwCwkG2YhaZmFpGUBI/MqRuHcxMyc 9HJDvdSizOTi4vw8veLUTYzA8Du45bfuDsZT50QOMUpzsCiJ83Il7fcXEkhPLEnNTk0tSC2K LyrNSS0+xMjEwSnVwNiS+k/6x7nwzTb14s4sQY17PSpZprqcSA4UT7MvWPow9tZpx8cWTCyL hWI9F7l/iOO6wM986Mu2bTv8e6cfL9u4QPO3zeKIo/1HDV57f39/ddWRqJoPmxOup9yqzZ6+ Zf+dlM2Wwo7ZHGJ9TkvS5ygK1adrZe0NmP0rsXnii2czF+2XWZNtkq/EUpyRaKjFXFScCAA2 TJ8xDQIAAA==
Subject: Re: [rtcweb] Terminate or Reject streams by setting port to zero in SDP
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Jul 2012 12:24:48 -0000

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
>