Re: [rtcweb] Plan A, respun

Harald Alvestrand <harald@alvestrand.no> Thu, 16 May 2013 18:27 UTC

Return-Path: <harald@alvestrand.no>
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 23AF911E814E for <rtcweb@ietfa.amsl.com>; Thu, 16 May 2013 11:27:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 gjj5JXEZ88tE for <rtcweb@ietfa.amsl.com>; Thu, 16 May 2013 11:26:54 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id AEE9711E8135 for <rtcweb@ietf.org>; Thu, 16 May 2013 11:26:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 263A239E1A6; Thu, 16 May 2013 20:26:52 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VcixxpqMZQPk; Thu, 16 May 2013 20:26:51 +0200 (CEST)
Received: from [IPv6:2001:470:de0a:27:d594:249c:4a90:3766] (unknown [IPv6:2001:470:de0a:27:d594:249c:4a90:3766]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 4534639E170; Thu, 16 May 2013 20:26:51 +0200 (CEST)
Message-ID: <519524EA.3000509@alvestrand.no>
Date: Thu, 16 May 2013 20:26:50 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
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>
In-Reply-To: <519519DB.6050702@nostrum.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: 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:27:00 -0000

Adam, this is the first time I've been compared to the Iraqi Information 
Minister... another achievement unlocked!

There are just 2 issues with your correction:

1) I don't believe your comment (or the RFCs you cite) reflect currently 
deployed reality.
I've seen the lines of code - they allocate from 32 dynamic types, not 192.
So the solution you propose is going to be incompatible with deployed 
code bases.

2) If the true limit at which one has to change allocation strategy were 
to become 96, not 32, it actually strengthens my "falling off a cliff" 
argument (unless you don't believe in applications with more than 96 
streams): This won't be a problem except in rare cases - ensuring even 
more code will be deployed that works until stressed.

I also have a confession to make: On some days, I respond to mail 
addressed to me without checking that I'm caught up on the mailing list 
that the conversation is copied to.

In this case, I responded to the mail sent directly to me on May 12 (a 
Sunday) without checking that I had also read your posting to the list 
on May 8 (Wednesday on the week before).

I suppose that's enough of a lapse in courtesy to be deserving of some 
censure.

           Harald