Re: [MMUSIC] Scope of RTP payload types in BUNDLE?

Cullen Jennings <fluffy@iii.ca> Mon, 10 June 2013 03:48 UTC

Return-Path: <fluffy@iii.ca>
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 4097521F8FA3 for <mmusic@ietfa.amsl.com>; Sun, 9 Jun 2013 20:48:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.574
X-Spam-Level:
X-Spam-Status: No, score=-2.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599]
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 xuECRzTiUpoY for <mmusic@ietfa.amsl.com>; Sun, 9 Jun 2013 20:48:25 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 6076421F85C0 for <mmusic@ietf.org>; Sun, 9 Jun 2013 20:48:25 -0700 (PDT)
Received: from tky-vpn-client-231-131.cisco.com (unknown [64.104.46.217]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 451B122E253; Sun, 9 Jun 2013 23:48:19 -0400 (EDT)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <BLU169-W17498C680BC2DD3D2C2381939B0@phx.gbl>
Date: Mon, 10 Jun 2013 12:48:16 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <635C2BBF-DA79-430D-9911-A2001D171002@iii.ca>
References: <749DCA95-2D40-46B3-9A3D-E63356C7A2C1@csperkins.org>, <1892A917-C408-4E8F-AB19-206ED508762C@csperkins.org>, <7594FB04B1934943A5C02806D1A2204B1C3799BC@ESESSMB209.ericsson.se>, <4EDA75BD-D753-4153-929B-10427274224D@csperkins.org>, <7594FB04B1934943A5C02806D1A2204B1C3799EE@ESESSMB209.ericsson.se>, , <599C780A-F483-470E-91F2-68DBA605C79C@csperkins.org>, <7594FB04B1934943A5C02806D1A2204B1C379D6E@ESESSMB209.ericsson.se>, , <64C06EE8-A16D-4C3E-8A11-D6400F620A8E@csperkins.org>, <7594FB04B1934943A5C02806D1A2204B1C379DC8@ESESSMB209.ericsson.se>, <71ED9E54-DF0C-4DB9-A7F4-09A0BC90B177@csperkins.org>, <51A3B070.1090006@alum.mit.edu>, <FF8A3ABB-992C-48D9-856F-A6A21A35A0C1@iii.ca>, <51AF5EEE.8080904@alum.mit.edu>, <7594FB04B1934943A5C02806D1A2204B1C3836E7@ESESSMB209.ericsson.se>, <51AF6BB9.3010807@alum.mit.edu>, <7594FB04B1934943A5C02806D1A2204B1C383757@ESESSMB209.ericsson.se>, <5E88302B-9DA1-4752-A6C5-367D6F00FAB5@iii.ca>, <51B20D64.7050600@alum.mit.edu>, <ED508E23-575A-471A-90AB-3D5DF3D90314@iii. ca>, <51B4B64B.1050101@alum.mit.edu> <BLU169-W17498C680BC2DD3D2C2381939B0@phx.gbl>
To: Bernard Aboba <bernard_aboba@hotmail.com>
X-Mailer: Apple Mail (2.1503)
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Scope of RTP payload types in BUNDLE?
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: Mon, 10 Jun 2013 03:48:31 -0000

On Jun 10, 2013, at 2:32 AM, Bernard Aboba <bernard_aboba@hotmail.com> wrote:

> Paul said: 
> 
> > I see no reason to struggle for ways to work around that if mandating 
> > PRACK would solve the problem.
> 
> [BA]  "solving the problem" requires more than just PRACK.  In a WebRTC implementation, I believe that the requirement is to be able to receive media before setRemoteDescription is called.   Unless that  functionality (which is not specifically called out in the use case document) is implemented, it doesn't matter whether PRACK is supported or not.  

+1 

and "work with 1-800-gofedex" is a deliberate wording so we can make sure we work with at least one of the key use cases but at the same time not drag in every weird corner case that has been imagined for early media.