Re: [rtcweb] JSEP and draft-ietf-mmusic-sdp-bundle-negotiation-03

Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com> Tue, 19 February 2013 09:14 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 CBF6B21F8D79 for <rtcweb@ietfa.amsl.com>; Tue, 19 Feb 2013 01:14:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.897
X-Spam-Level:
X-Spam-Status: No, score=-5.897 tagged_above=-999 required=5 tests=[AWL=0.053, BAYES_00=-2.599, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jYmwUNswAmVw for <rtcweb@ietfa.amsl.com>; Tue, 19 Feb 2013 01:14:58 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id AF10721F8D45 for <rtcweb@ietf.org>; Tue, 19 Feb 2013 01:14:57 -0800 (PST)
X-AuditID: c1b4fb2d-b7f316d0000028db-18-5123428d51ba
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 1F.44.10459.D8243215; Tue, 19 Feb 2013 10:14:54 +0100 (CET)
Received: from [150.132.141.119] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.279.1; Tue, 19 Feb 2013 10:14:53 +0100
Message-ID: <5123428D.5060009@ericsson.com>
Date: Tue, 19 Feb 2013 10:14:53 +0100
From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B0F555F@ESESSMB209.ericsson.se>, <BLU002-W14013516E3AE69595F4D5CC93F40@phx.gbl>, <7594FB04B1934943A5C02806D1A2204B0F55CD@ESESSMB209.ericsson.se> <BLU002-W210F2CC4F5AA749AEBA495B93F40@phx.gbl>
In-Reply-To: <BLU002-W210F2CC4F5AA749AEBA495B93F40@phx.gbl>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPJMWRmVeSWpSXmKPExsUyM+JvjW6fk3KgwdwJ7BZr/7WzOzB6LFny kymAMYrLJiU1J7MstUjfLoErY+UdsYKlXBUtjcdZGhi7OboYOTkkBEwkpi/9yAJhi0lcuLee rYuRi0NI4CSjxN79k5ggnLWMElPWXGYGqeIV0JbY+agfrINFQFXi1IseRhCbTSBQ4vr/X0wg tqhAlMT7q01Q9YISJ2c+AasXERCW2PqqF6xGWMBL4sbbb+wQC14zSvzavwasiFPAWuLAoU1g NrOArcSFOdehbHmJ7W/ngA0VEtCVePf6HusERoFZSHbMQtIyC0nLAkbmVYzsuYmZOenlhpsY gYF2cMtv3R2Mp86JHGKU5mBREucNc70QICSQnliSmp2aWpBaFF9UmpNafIiRiYNTqoFx8uaP y76duJ2SwKHceeV/h99Xs+ZzWjYHmVjUuC9Hyi5+yK8qKmLt7KNRM7Xo8vbip5/n3Vuuf3q5 +PzeesGAy8ZqizRjVZIyOVOq32y+3DX/lBmryjz7gLgbL76Ku3BlvFo6d2nE+u+bXu5unGST YHi+It6j1qFd663iHq1k2fuf38qfCzyrxFKckWioxVxUnAgAWA2d9QICAAA=
Subject: Re: [rtcweb] JSEP and draft-ietf-mmusic-sdp-bundle-negotiation-03
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, 19 Feb 2013 09:14:59 -0000

On 2013-02-18 21:25, Bernard Aboba wrote:
> Christer said:
>
>  > Good questions, for which I don't have any answers at this point :)
>  >
>  > But, IF we can agree on this as a way forward, one of the next steps
> is to look at the JSEP impacts.
>
> [BA] The problem is that my opinion will differ depending on whether the
> SDP in question is to be used in the API or over the wire.
>
> The "different port" formulation makes good sense to me if you are
> looking for backward compatibility with existing SIP/SDP implementations
> which are likely to send an error in response to a "same port"
> formulation.   So if this is an "on the wire" question I give it a
> thumbs up.
>
> However, if you are asking me whether it makes sense for createOffer()
> to output SDP with different ports by default, when 99 percent of
> applications are likely to not be doing SIP interop, I would say "no".
> Then the next question is whether there needs to be a mechanism in the
> API for indicating a preference for different ports, when this is desired.

That sounds like a reasonable approach to me (and the default would be 
one port).

Stefan

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