Re: [MMUSIC] BUNDLE goes UP: Do we need port zero for bundle-only m- lines?

Hadriel Kaplan <hadriel.kaplan@oracle.com> Thu, 08 August 2013 18:42 UTC

Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C204321F9F9D for <mmusic@ietfa.amsl.com>; Thu, 8 Aug 2013 11:42:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.523
X-Spam-Level:
X-Spam-Status: No, score=-6.523 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, 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 7ABnbEl-kyOz for <mmusic@ietfa.amsl.com>; Thu, 8 Aug 2013 11:42:44 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id 5651311E8150 for <mmusic@ietf.org>; Thu, 8 Aug 2013 11:42:42 -0700 (PDT)
Received: from acsinet22.oracle.com (acsinet22.oracle.com [141.146.126.238]) by aserp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r78IgeB2015688 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 8 Aug 2013 18:42:40 GMT
Received: from userz7022.oracle.com (userz7022.oracle.com [156.151.31.86]) by acsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r78IgdV2022410 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Aug 2013 18:42:39 GMT
Received: from abhmt103.oracle.com (abhmt103.oracle.com [141.146.116.55]) by userz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r78IgcGK013557; Thu, 8 Aug 2013 18:42:38 GMT
Received: from [10.1.21.34] (/10.5.21.34) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 08 Aug 2013 11:42:38 -0700
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <001601ce945c$ef7509d0$ce5f1d70$@co.in>
Date: Thu, 08 Aug 2013 14:42:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <6C8CDE49-3C14-49EB-861F-2B3B0B108D6E@oracle.com>
References: <7594FB04B1934943A5C02806D1A2204B1C421C80@ESESSMB209.ericsson.se> <9AA75667-A597-4EB1-87B4-FA79A2F35C3C@oracle.com> <7594FB04B1934943A5C02806D1A2204B1C422263@ESESSMB209.ericsson.se> <E4D2C482-C7EF-4BCB-BC4B-BA218E9BFCE8@oracle.com> <001601ce945c$ef7509d0$ce5f1d70$@co.in>
To: Parthasarathi R <partha@parthasarathi.co.in>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: acsinet22.oracle.com [141.146.126.238]
Cc: "mmusic (E-mail)" <mmusic@ietf.org>
Subject: Re: [MMUSIC] BUNDLE goes UP: Do we need port zero for bundle-only m- lines?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 18:42:54 -0000

On Aug 8, 2013, at 1:30 PM, Parthasarathi R <partha@parthasarathi.co.in> wrote:

> My understanding is that the initial offer with same port breaks more than
> one existing system. Sec 4.1.1 of draft-reddy-rtcweb-mobile-03 draft
> indicates one of the possible interop issue with existing mobile networks.

I've only skimmed the draft, but I don't see the problem.  I know there's an issue with multiplexing all the RTP on one 5-tuple, but that's actually an orthogonal issue.  I was talking about whether an SDP offer with multiple m-lines using the same port number would have issues or not.  Am I missing something in the draft?


> So, I don't agree with Hadriel claim of 99% system works with same port. The
> current BUNDLE draft mechanism interop in the better way.

Please don't misrepresent what I said - I think if you read my paragraph, it's pretty clear I am not claiming 99% of them work with the same port; nor am I suggesting we go back to using the same port again.  It was in the context of the debates we had back when the issue was debated a couple IETF meetings ago, and I said as far as I knew they can handle an *SDP offer* with it... and I then *immediately* said I didn't argue it for long, because someone else stated they knew of a device which had a problem, and that concerned me.  Since most people generally try not to contradict themselves in the span of a dozen words, I think it's reasonable to assume I no longer believe all devices work.  I mean I may not be smart, but I'm not a complete idiot. (well... not generally an idiot anyway)

-hadriel