Re: [rtcweb] Plan A, respun

Adam Roach <adam@nostrum.com> Wed, 08 May 2013 15:51 UTC

Return-Path: <adam@nostrum.com>
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 8D30E21F8F20 for <rtcweb@ietfa.amsl.com>; Wed, 8 May 2013 08:51:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.199
X-Spam-Level:
X-Spam-Status: No, score=-102.199 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_14=0.6, SPF_PASS=-0.001, 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 w3uTCuN+EXWF for <rtcweb@ietfa.amsl.com>; Wed, 8 May 2013 08:51:23 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id EDA7421F8960 for <rtcweb@ietf.org>; Wed, 8 May 2013 08:51:22 -0700 (PDT)
Received: from Orochi.local (99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r48FpLc6057296 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <rtcweb@ietf.org>; Wed, 8 May 2013 10:51:22 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <518A7479.10208@nostrum.com>
Date: Wed, 08 May 2013 10:51:21 -0500
From: Adam Roach <adam@nostrum.com>
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: rtcweb@ietf.org
References: <51894846.3090102@nostrum.com> <518A304A.1030609@alvestrand.no>
In-Reply-To: <518A304A.1030609@alvestrand.no>
Content-Type: multipart/alternative; boundary="------------050501080803050108050606"
Received-SPF: pass (shaman.nostrum.com: 99.152.145.110 is authenticated by a trusted mechanism)
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: Wed, 08 May 2013 15:51:23 -0000

On 5/8/13 06:00, Harald Alvestrand wrote:
> To put a blunt point on it: Either send less than ~32 streams, or give 
> a=ssrc attributes.

Let's call it 96, just to keep reality involved in the conversation (cf. 
RFC 3551, section 3, para 7; as updated by RFC 5761, section 4, para 10).

I'll also point out that you can always have more than one bundle; so, 
if you're willing to burn two ports rather than just one, you can double 
this to 192. Repeat as necessary.

> To me, that measn we're mandating one mechanism (PT values) for small 
> numbers of flows...

Uh... no? Small numbers of flows can use a=ssrc. They just lose some 
flexibility by doing so.

> ...and another mechanism (a=ssrc) for large numbers of flows - such 
> mechanism changes usually have "interesting" properties in what 
> happens at the changeover point.

Given the actual limit here is 96 *per* *port*, I'd be more inclined to 
characterize it as:

  * One very flexible mechanism for small, medium, and moderately large
    numbers of streams, and
  * Another less flexible mechanism for sessions of arbitrary size,
    including small numbers of streams


/a