Re: [rtcweb] Plan A, respun

Emil Ivov <emcho@jitsi.org> Thu, 16 May 2013 18:17 UTC

Return-Path: <emil@sip-communicator.org>
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 57AF211E8126 for <rtcweb@ietfa.amsl.com>; Thu, 16 May 2013 11:17:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 bsoxiUBz5ybW for <rtcweb@ietfa.amsl.com>; Thu, 16 May 2013 11:16:59 -0700 (PDT)
Received: from mail-bk0-x22f.google.com (mail-bk0-x22f.google.com [IPv6:2a00:1450:4008:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id D689911E8105 for <rtcweb@ietf.org>; Thu, 16 May 2013 11:16:55 -0700 (PDT)
Received: by mail-bk0-f47.google.com with SMTP id jg9so1881630bkc.34 for <rtcweb@ietf.org>; Thu, 16 May 2013 11:16:54 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding:x-gm-message-state; bh=o++S5BrPnG2Eo13BzblkN5HB6gzgWVQzYGlMXre2yl8=; b=MAciKxQtafp53v2jwYDsREguhMhC4kKOjjew5KEOQ++NrQXoUi1WnQ78Lsmgsv1f7K Xc3JhAiy7l3cn8v7RBrPlRyfLragsqFuWQsQSCT0lLoY1KLRlltKvRds5hiD7vzKgDQA iRAqwYqJZFIAO4x/9NrVMkhymZCmX05Gf39H7dZtW1h0bogZRDGrlvagwRs+XJVkwGN/ G29YNf2tqLaM8px43H0RW6qIJFEtj09XaLABKWFyDZ33XyuUJ8id9MiQGS5eSGlvEkIZ tRPlzJi4MndoEzDjiwVHkIporZPG/W/tZjTc690fKrVBc8mlzel1DfL5ShWQiTqWasd4 gbug==
X-Received: by 10.204.113.78 with SMTP id z14mr14021465bkp.44.1368728214532; Thu, 16 May 2013 11:16:54 -0700 (PDT)
Received: from camionet.local ([79.100.215.70]) by mx.google.com with ESMTPSA id i15sm2352426bkz.12.2013.05.16.11.16.52 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 16 May 2013 11:16:53 -0700 (PDT)
Message-ID: <51952294.9080603@jitsi.org>
Date: Thu, 16 May 2013 21:16:52 +0300
From: Emil Ivov <emcho@jitsi.org>
Organization: Jitsi
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Adam Roach <adam@nostrum.com>
References: <51894846.3090102@nostrum.com> <518A304A.1030609@alvestrand.no> <518F6338.8070903@jitsi.org> <518F83E5.4060209@alvestrand.no> <519519DB.6050702@nostrum.com> <CAPvvaa+ec3BtwE6Q_4KY7SA_3mUNAFCY70J4vNRE27ztMmcmpg@mail.gmail.com>
In-Reply-To: <CAPvvaa+ec3BtwE6Q_4KY7SA_3mUNAFCY70J4vNRE27ztMmcmpg@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQnmQxM/xJQl3vpJlMI+5vfiUF2BL3JXPdzeHPPPPitraGdSAjMcgULdQ2d94PKrIfb2HVZE
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Plan A, respun
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: Thu, 16 May 2013 18:17:00 -0000

On 16.05.13, 20:43, Emil Ivov wrote:
> On Thu, May 16, 2013 at 8:39 PM, Adam Roach <adam@nostrum.com> wrote:
>>
>> Your insistence of using "32" rather than "96" is somewhat reminiscent
> 
> 96? Do you assume no use of rtcp-mux?

I suppose you must be referring to [5761#4]:

   Values below 64
   MAY be used if that is insufficient, in which case it is RECOMMENDED
   that payload type numbers that are not statically assigned by be
   used first.

While this works on paper, most media libraries are likely to have many
of those statically bound to the formats from 3551. This would bring us
down to 61. Even then going below 96 is still likely to be problematic
for many such libraries.

This actually reminds me how recently (I believe it was in Boston)
someone advised that in trickle ICE, even though 3264 allowed it, we
shouldn't be using 0.0.0.0 in descriptions with no candidates. This was
because (from the notes) "otherwise, you have to add special purpose
code to existing SDP libraries".

Emil


-- 
https://jitsi.org