Re: [rtcweb] Plan A, respun

Eric Rescorla <ekr@rtfm.com> Thu, 16 May 2013 23:29 UTC

Return-Path: <ekr@rtfm.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 1D68421F8F41 for <rtcweb@ietfa.amsl.com>; Thu, 16 May 2013 16:29:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.976
X-Spam-Level:
X-Spam-Status: No, score=-102.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, 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 VltPjdjKCy3B for <rtcweb@ietfa.amsl.com>; Thu, 16 May 2013 16:29:02 -0700 (PDT)
Received: from mail-qe0-f52.google.com (mail-qe0-f52.google.com [209.85.128.52]) by ietfa.amsl.com (Postfix) with ESMTP id 1DE3621F8470 for <rtcweb@ietf.org>; Thu, 16 May 2013 16:29:02 -0700 (PDT)
Received: by mail-qe0-f52.google.com with SMTP id 1so2316242qec.11 for <rtcweb@ietf.org>; Thu, 16 May 2013 16:29:01 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:x-originating-ip:in-reply-to:references :from:date:message-id:subject:to:cc:content-type:x-gm-message-state; bh=4wZY6t2v+9T1KbUnR0toY3Dza4xLDBBMe2afxB6BLz8=; b=C/WmmCkukLRItZe0cXNkITb5uisF+y7Wm2rpVZALeg7mHNUT5dOgiYQxRRby2x/3rP 2uuS26IWtfm9YVpnFQUK0IcRrnDUKHC/P4uOz+tNgYEL7Ngqyw46fbYmXhiMOrGYKZIf CZHexfGORlEskumx9KGE6mVfjnj4MaCj68zuECri+WYe8hy7mhirIIkQj1TWANksqHWO GRJ+llXK9w5VSh6/ybl3+y7yv79Cf0olz410Nx0QK+wwbRSYqD43Yo9iqHdq+3++pkxF ZvsSBD6KsLrx2yjapDt6wEXgZVxGhZVgDW4PO3JYjGUtW5/rSeyivoYjwXrGNYje+v9x aqIA==
X-Received: by 10.49.75.134 with SMTP id c6mr8105902qew.47.1368746941464; Thu, 16 May 2013 16:29:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.85.130 with HTTP; Thu, 16 May 2013 16:28:20 -0700 (PDT)
X-Originating-IP: [74.95.2.170]
In-Reply-To: <5195304B.10706@alvestrand.no>
References: <51894846.3090102@nostrum.com> <518A304A.1030609@alvestrand.no> <518F6338.8070903@jitsi.org> <518F83E5.4060209@alvestrand.no> <519519DB.6050702@nostrum.com> <519524EA.3000509@alvestrand.no> <51952860.5030906@nostrum.com> <5195304B.10706@alvestrand.no>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 16 May 2013 16:28:20 -0700
Message-ID: <CABcZeBO+miF-euyyKFDrpMUdnV-Ej2QaZgKmiMc2Yp08QUyz7A@mail.gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: multipart/alternative; boundary="047d7bdc8d903bfa2204dcde3bb3"
X-Gm-Message-State: ALoCoQmoOqFlDqfX3RAivaHNFTbIxsOQY/FF2bBo/iCNch7Dz30WsdqnCA8Yj6F6bE5ceaItGfVM
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 23:29:08 -0000

On Thu, May 16, 2013 at 12:15 PM, Harald Alvestrand <harald@alvestrand.no>wrote:
>
>  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
>>>
>>
>> And, to be clear, it's not a cliff. For any given session (without
>> a=ssrc:), you have to allocate ceiling(streams/96) ports. It's not like you
>> go from using one port to using 97 ports when you add the 97th stream. You
>> go from one port to two, which will handle 192 streams.
>>
>
> Going from one port to two ports is a cliff.
> We may have differing opinions on how tall it is.


Harald,

I am not following how this is a discriminating factor between Plan A and
Plan B.

In both Plan A and Plan B, any media stream which is intended to be
independently processable by a legacy endpoint must appear on its
own m-line. That means it must also have its own independent ports,
even if you are hoping to eventually be able to mux it via BUNDLE.

In both Plan A and Plan B, it is possible to indicate additional media
streams that are not processable by a legacy endpoint but that
will be processable by a new endpoint:

- In Plan A, this is done by marking them bundle-only
- In Plan B, this is done by having them be additional SSRCs on one
  of the extant m-lines.



Regardless of Plan A versus Plan B, bundle contemplates having
multiple media flows on the same media 5-tuple. Thus, it must
be possible to demux the flows somehow. As I read Plan A,
it proposes using both PT and SSRC to demux whereas plan B
only wants to use SSRC? So, the implication is that a Plan A
endpoint must:

1. Demux on both PT and SSRC (this is trivial, I think you will agree)
2. When acting as offerer, either always offer SSRC or conditionally
offer SSRC when the # of PTs is excessive.

I don't understand why you think that plan A means more ports than
plan B. Presumably we can simply specify that bundle requires
SSRC muxing, in which case plan A and plan B behave identically.

What am I missing?

-Ekr