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

Christer Holmberg <christer.holmberg@ericsson.com> Wed, 20 February 2013 11:48 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 AE43721F8793 for <rtcweb@ietfa.amsl.com>; Wed, 20 Feb 2013 03:48:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.283
X-Spam-Level:
X-Spam-Status: No, score=-6.283 tagged_above=-999 required=5 tests=[AWL=-0.034, BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 tVHql4eq9Cx1 for <rtcweb@ietfa.amsl.com>; Wed, 20 Feb 2013 03:48:45 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id A867821F86A5 for <rtcweb@ietf.org>; Wed, 20 Feb 2013 03:48:44 -0800 (PST)
X-AuditID: c1b4fb2d-b7f316d0000028db-10-5124b81bcbbb
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 3B.C6.10459.B18B4215; Wed, 20 Feb 2013 12:48:43 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.82]) by ESESSHC020.ericsson.se ([153.88.183.78]) with mapi id 14.02.0318.004; Wed, 20 Feb 2013 12:48:43 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: JSEP and draft-ietf-mmusic-sdp-bundle-negotiation-03
Thread-Index: AQHODhK5jGYz3rJxuE6H2F9+HS8Ud5iACdXY///1aQCAAqOCsA==
Date: Wed, 20 Feb 2013 11:48:42 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B0FC2EF@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B0F555F@ESESSMB209.ericsson.se>, <BLU002-W14013516E3AE69595F4D5CC93F40@phx.gbl>, <7594FB04B1934943A5C02806D1A2204B0F55CD@ESESSMB209.ericsson.se> <BLU002-W210F2CC4F5AA749AEBA495B93F40@phx.gbl>
In-Reply-To: <BLU002-W210F2CC4F5AA749AEBA495B93F40@phx.gbl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.20]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrILMWRmVeSWpSXmKPExsUyM+Jvja70DpVAg4P3dC32L7nMbLH2Xzu7 A5PH454zbB5LlvxkCmCK4rJJSc3JLEst0rdL4MpY07SVqWAvT8WhN/OYGxhfcXYxcnJICJhI TF39nxHCFpO4cG89WxcjF4eQwCFGic7WyUwQzmJGiRlz57F3MXJwsAlYSHT/0wZpEBEIkThz +hkriC0s4Cgxa9YeFoi4k8SurYsYYeyZJzaC2SwCqhIHf19nA7F5BbwlWhseQy17zSixdcc5 JpAEp4C1xIFDm8AGMQJd9P3UGrA4s4C4xK0n85kgLhWQWLLnPDOELSrx8vE/VghbUeLq9OVQ 9XoSN6ZOYYOwtSWWLXzNDLFYUOLkzCcsExhFZyEZOwtJyywkLbOQtCxgZFnFyJ6bmJmTXm64 iREYDQe3/NbdwXjqnMghRmkOFiVx3jDXCwFCAumJJanZqakFqUXxRaU5qcWHGJk4OKUaGOVq fG+uFrxpF2RRfUkqbcsd3g3LCrOq02+84Njo1rfpWsmGmez7LdVnvGX+PPmweOyR2KUqc3mv hosczlY/6ZTiNysq+IaGS/OatcKB3UUvnf6djQ/Yc3czn+fDAiURjcgvrNvTZ4jfPVHIcWJN T+2Tg8GHc2+cKPdwU1SQvtmrnCj0aur7C0osxRmJhlrMRcWJAIDm3gRUAgAA
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: Wed, 20 Feb 2013 11:48:45 -0000

Hi,

>> 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. 

True. But, if SDP is NOT used on the wire, the BUNDLE document does not put any requirements on whatever other signaling protocol you may be using. You can use a protocol that ONLY signals different port numbers, or one that ONLE signals identical port numbers, or one that ONLY signals a single port number, on the wire, and there is nothing BUNDLE can do about it :) 

BUNDLE is only about users of SDP Offer/Answer - no matter whether it's an API or a wire protocol.

>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's a good discussion topic for JSEP :)

Regards,

Christer