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

Paul Kyzivat <pkyzivat@alum.mit.edu> Sun, 09 June 2013 17:07 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 902A721F8916 for <mmusic@ietfa.amsl.com>; Sun, 9 Jun 2013 10:07:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.4
X-Spam-Level:
X-Spam-Status: No, score=-0.4 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
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 TUqEbucn0ktm for <mmusic@ietfa.amsl.com>; Sun, 9 Jun 2013 10:07:25 -0700 (PDT)
Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:64]) by ietfa.amsl.com (Postfix) with ESMTP id 9268021F8A68 for <mmusic@ietf.org>; Sun, 9 Jun 2013 10:07:25 -0700 (PDT)
Received: from omta11.westchester.pa.mail.comcast.net ([76.96.62.36]) by qmta07.westchester.pa.mail.comcast.net with comcast id mGZm1l0010mv7h057H7Rvc; Sun, 09 Jun 2013 17:07:25 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta11.westchester.pa.mail.comcast.net with comcast id mH7Q1l01Z3ZTu2S3XH7Q8A; Sun, 09 Jun 2013 17:07:25 +0000
Message-ID: <51B4B64B.1050101@alum.mit.edu>
Date: Sun, 09 Jun 2013 13:07:23 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Cullen Jennings <fluffy@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>
In-Reply-To: <ED508E23-575A-471A-90AB-3D5DF3D90314@iii.ca>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1370797645; bh=vhUKnqaDMnp8ywYRgLRurycq2ApkUC/uJnLoEUxN1Ys=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=UWZF7vsETN0EKHg+vRpfO4KyQsnUsQAEw7B4nZ/HWoc5Diq1Nf6izfAHwqrTzhL+k 2XOaIvk6whlEeoxFKJeMlVrZNCCj95BRxi8hn2DpyDkQunF/uefvetpJgsmScLlPxA GAC4kd2yrb8yi75omi6/9u/wwcc45xCZdwKkSu6C/jI7H/KyOfAxjc+l98k0FpiwnW Ko1p2NCDbuKSWKnZC5ZjteqlH7xFe7ZQoqQ/MNTD7z2+5d5mKCdDU59Z/1DMtmf2h2 b3h/PW/7Npn8hftw5WU9pvawRVVwpRaHn3YZp9O5xfFX4PLj+J+tE86kUVrNZWRT/P lwKhxTQoUHdhA==
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, 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: Sun, 09 Jun 2013 17:07:31 -0000

On 6/8/13 12:11 AM, Cullen Jennings wrote:
>
> On Jun 7, 2013, at 11:42 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>
>> And then can't we demand that to support BUNDLE you must also support PRACK?
>
> I think you will find the people that have not implemented PRACK still don't want to implement PRACK. I know there is no way I would want to mandate the complexity of PRACK just to do bundle.

They are willing to implement BUNDLE, and probably ICE and DTLS/SRTP, 
and perhaps RTCWEB, but they find PRACK undesirable to implement???

I have no sympathy!
Its time to join the 21st century.

I see no reason to struggle for ways to work around that if mandating 
PRACK would solve the problem.

	Thanks,
	Paul