Re: [rtcweb] A problem with both A and B

Christer Holmberg <christer.holmberg@ericsson.com> Tue, 21 May 2013 09:29 UTC

Return-Path: <christer.holmberg@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 2A31621F904B for <rtcweb@ietfa.amsl.com>; Tue, 21 May 2013 02:29:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.137
X-Spam-Level:
X-Spam-Status: No, score=-6.137 tagged_above=-999 required=5 tests=[AWL=0.112, 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 zfQvfT+V5v63 for <rtcweb@ietfa.amsl.com>; Tue, 21 May 2013 02:29:28 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 14C9221F929F for <rtcweb@ietf.org>; Tue, 21 May 2013 02:29:24 -0700 (PDT)
X-AuditID: c1b4fb25-b7efb6d000007c26-77-519b3e731727
Received: from ESESSHC004.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 69.55.31782.37E3B915; Tue, 21 May 2013 11:29:23 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.167]) by ESESSHC004.ericsson.se ([153.88.183.30]) with mapi id 14.02.0328.009; Tue, 21 May 2013 11:29:22 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Kevin Dempsey <kevindempsey70@gmail.com>
Thread-Topic: [rtcweb] A problem with both A and B
Thread-Index: AQHOUzwnCrd1S7QwyEqM9DOrRHv1xJkJuD4AgAPsAUCAAH7PAIABHI7Q///i6gCAACIxYP//4ZaAgAAM64CAACgpIP//5OqAAAR1XaA=
Date: Tue, 21 May 2013 09:29:22 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C3751EC@ESESSMB209.ericsson.se>
References: <BLU403-EAS40305B2D015B786CC67EB9293AC0@phx.gbl> <CABkgnnXX3zoeKqjFxjsfMgaGGRM0JzymaeWfA13LEjUZ4tGF9Q@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1C373EF0@ESESSMB209.ericsson.se> <519A4C9A.6020501@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1C374F13@ESESSMB209.ericsson.se> <519B22E8.9060709@jitsi.org> <7594FB04B1934943A5C02806D1A2204B1C375034@ESESSMB209.ericsson.se> <519B2613.9090707@jitsi.org> <CAMvTgcfbnww1PXzGNFoceAyMDjHY0x4M-UoTceeUCVojakK4EA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1C375159@ESESSMB209.ericsson.se> <CAMvTgceJd_QNdjWMuMoBVix-7+Gv=o3vtROT7OYznf49eE8uOw@mail.gmail.com>
In-Reply-To: <CAMvTgceJd_QNdjWMuMoBVix-7+Gv=o3vtROT7OYznf49eE8uOw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.17]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrELMWRmVeSWpSXmKPExsUyM+JvrW6x3exAg461xhZrdk5gsbg5/y2L xdp/7ewOzB47Z91l91iy5CeTx/83gQHMUVw2Kak5mWWpRfp2CVwZp5u0ClYKVzydfJ6xgbGP v4uRk0NCwERix4NnzBC2mMSFe+vZuhi5OIQEDjNK3Fq1lAnCWcIo8fX6Z8YuRg4ONgELie5/ 2iANIgI6EgfvT2YHCTMLuEhs3hcPEhYWMJT4feEUM0SJkcS19ftZIOwyiR2XPjOB2CwCqhLn Pu0Ci/MK+Er0bOljB7GFBBpZJdp7BUFsToFAiaNHt7OC2IxAt30/tQasl1lAXOLWk/lMEDcL SCzZcx7qflGJl4//sYKcIyGgKLG8Xw6iXEdiwe5PbBC2tsSyha+ZIdYKSpyc+YRlAqPYLCRT ZyFpmYWkZRaSlgWMLKsY2XMTM3PSy402MQLj5eCW36o7GO+cEznEKM3BoiTO26s9NVBIID2x JDU7NbUgtSi+qDQntfgQIxMHp1QD4/wX3Jsmyv8tsHrQf/2X+OvwL/GzOb+obbrkuD5uu1Q9 29kAre13WCJm/1lwsimLUyzTzStm/eP5zks7Su9O2fwwe8O6X8wyjk8mf/lWsF83Mfelmf+u 7sp9HwLO/P/uyD2zqkN1g6Eyc+9Ny9Yb9zft2bawrEhidn3Xc2HpBasjMv5lWgpP0lNiKc5I NNRiLipOBACSoBrAZQIAAA==
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] A problem with both A and B
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: Tue, 21 May 2013 09:29:33 -0000

Hi,

>Clearly adding a new m= line needs a SDP O/A.

Correct. 

>So in the multiplex case I would think that adding another m= line equivalent to a bundle would also need a SDP O/A.

Yes. In my opinion, adding a new m- line requires an SDP O/A - bundle or no bundle.

> In the non multiplex case changing to a different source doesn't require a SDP O/A. However,  unless there is 
> some identifier in the RTP packets that the receiver knows already, such a change would need to be signalled in the multiplex case.

What do you mean by "non-multiplex"?

1) No bundle, but possibly multiple SSRCs per m- line; or

2) No bundle, and only one SSRC per m- line

Regards,

Christer



> 
On 21 May 2013 09:57, Christer Holmberg <christer.holmberg@ericsson.com> wrote:
Hi,

> In cases where each m= line has a different port, when a new SSRC is received usually it is either discarded (when latched to a pre exisiting SSRC stream that does not stop) or is treated as replacing the previous SSRC.
>
> When multiplexing is being used it is not obvious whether the new SSRC is replacing a previous one, or is another separate stream.
>
> I think that in the multiplex case we need something like a virtual destination port in each RTP packet, such as a RTP header extension or even UDP over UDP!
Perhaps.

But, then we talk more about how to identify/demux a stream, once it has been added.

We would still need to answer whether the actual addition of a new stream requires a SDP O/A transaction :)

Regards,

Christer



On 21.05.13, 10:38, Christer Holmberg wrote:
> Hi,
>
>>> If adding a new stream means adding a new SSRC, within an
>>> existing m-, then it is also an SDP O/A issue - bundle or no
>>> bundle.
>>
>> Why is that?
>
> Because, even WITHOUT bundle, you have to answer whether adding a new
> SSRC (or, whatever mechanism we use to identify a stream) within an
> existing m- line requires an SDP O/A transaction or not.
OK, I guess I took your statement to mean that adding and removing SSRCs
to m= lines is a matter that cannot be handled without SDP O/A which I
think it isn't (and which is what this thread started with).

I obviously agree that it is not a bundle-specific issue.

Emil

--
https://jitsi.org
_______________________________________________
rtcweb mailing list
rtcweb@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb