Re: [rtcweb] Add, remove, add, remove, add, remove a media stream (lines in SDP)

Iñaki Baz Castillo <ibc@aliax.net> Mon, 23 April 2012 08:24 UTC

Return-Path: <ibc@aliax.net>
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 4B9D721F860F for <rtcweb@ietfa.amsl.com>; Mon, 23 Apr 2012 01:24:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.335
X-Spam-Level:
X-Spam-Status: No, score=-2.335 tagged_above=-999 required=5 tests=[AWL=-0.258, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_18=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 sw+pKXH6hLEB for <rtcweb@ietfa.amsl.com>; Mon, 23 Apr 2012 01:24:30 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8116D21F85BD for <rtcweb@ietf.org>; Mon, 23 Apr 2012 01:24:30 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so9223444vbb.31 for <rtcweb@ietf.org>; Mon, 23 Apr 2012 01:24:30 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=I6aQM2ofYVVQ7pZH6LeMLi7tUTlSzdlVoIwb+6lcTf8=; b=oLAwrSjmjt3kufl4X7kS7f6u2uBiQhVRee7qCW06HPAep3L4Xyn60mR6SeylZw71Xb /mVAeCABYLhVpVBNmTWAgK7I9Vkj9UlKhlU/iLK6iZfbWgcpFtyFV10ROagk4493s/1l qMJoRgqFY55CJcYypRHx8vNsYk5hnpGWWttjQfg6nICzVKiqe2XzzvOBOKvuSBGlGqQ5 NWRVxjBgT5tEURTHfqSIOgDeSBs+fNJcyveu/0Y9ykBhyK/Jf3ScH7RW/9pD9mW9USdU zvi/PF7x+hYpNilMZJ497kwZ1+sKexo9su8wsPjqz/VS8ZluIjCEkStejv8osaGPqMwK xEGw==
Received: by 10.52.91.72 with SMTP id cc8mr13358567vdb.17.1335169470054; Mon, 23 Apr 2012 01:24:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.170.165 with HTTP; Mon, 23 Apr 2012 01:24:09 -0700 (PDT)
In-Reply-To: <AC5A9A3E-B744-428D-AC6D-19359949600F@ag-projects.com>
References: <CALiegfkBFNv6emEg6gkxV+iPkx52rUwn+qcyEjk2r4iDYEXrAA@mail.gmail.com> <7F2072F1E0DE894DA4B517B93C6A05852C4400131A@ESESSCMS0356.eemea.ericsson.se> <CALiegfnDOFipBMK1DU=G5RUH0sHDDcL0C+smwJqRmazJB_xdJg@mail.gmail.com> <5D37D3F0-9A1C-4116-9A19-47E5A8929F71@ag-projects.com> <CALiegfmZNMjeLWjvS-7iAABCvRfoq8WeZ83ap2e7nmUzT5-07g@mail.gmail.com> <AC5A9A3E-B744-428D-AC6D-19359949600F@ag-projects.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Mon, 23 Apr 2012 10:24:09 +0200
Message-ID: <CALiegfn7rfXgY6URzoJyFWq2YpoxLDSfH9oa5y8jJ+9ziKZRcA@mail.gmail.com>
To: =?UTF-8?Q?Sa=C3=BAl_Ibarra_Corretg=C3=A9?= <saul@ag-projects.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQnF3vzjY+JYzwTgrYvngFw4jxmne7NFXF+vTaYFP4IClDo36CswxhAG3EMQwBK5+pJ7nV9I
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Add, remove, add, remove, add, remove a media stream (lines 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: Mon, 23 Apr 2012 08:24:33 -0000

2012/4/23 Saúl Ibarra Corretgé <saul@ag-projects.com>om>:
>>> But when you disabled the stream you did set the port to zero, so when you resurrect the stream you'd allocate a new port.
>>
>> The stack could try to allocate the same port as default behavior.
>>
>
> Well, then the stack needs to be fixed :-) The stack should 'forget' the port as soon as it sets it as zero in the stream, and allocate a new one, the same way it would do for a brand new stream.

The WebRTCP stack is being designed right now :)



>>> Were you thinking about setting the stream as inactive (a=inactive in SDP terms) instead?
>>
>> But setting a=inactive just pauses the stream in a single direction
>> (according to RFC 4566). You could be interested in stopping sending
>> and receiving video.
>>
>
> IIRC inactive pauses the stream in both directions. For pausing it in a single direction you can use sendonly / recvonly.

You are totally right, my fault. Anyhow setting a=inactive means that
resources are not freed (for example, RTCP must be still sent). Not
sure if this is good or bad.


-- 
Iñaki Baz Castillo
<ibc@aliax.net>