Re: [rtcweb] Plan A, respun

The paragraph that worries me most is this one:

    Offerers conformant to this specification MUST do one of the
    following:

    o  Use non-overlapping PT values for each m-line in any given bundle
       group.

    o  Provide distinct a=ssrc attributes for each m-line which uses
       overlapping PT values with any other m-line.  [Technically, this
       is a general case of the previous point.]

To put a blunt point on it: Either send less than ~32 streams, or give 
a=ssrc attributes.

To me, that measn we're mandating one mechanism (PT values) for small 
numbers of flows, and another mechanism (a=ssrc) for large numbers of 
flows - such mechanism changes usually have "interesting" properties in 
what happens at the changeover point.

It would seem to me to be architecturally cleaner to insist that a=ssrc 
be used always.
But in that case, I have a very large difficulty seeing the important 
advantage this has over Plan B.

On 05/07/2013 08:30 PM, Adam Roach wrote:
> In order to facilitate discussion between the two SDP format 
> alternatives we're considering, I've put together a document that more 
> clearly spells out the Plan A approach as we originally envisioned it. 
> Note that this is a slightly different approach than Cullen outlined 
> in Orlando. I fear the Orlando approach may have suffered from its 
> attempts to incorporate some elements of Plan B in an attempt to 
> appease proponents of that approach; and, in doing so, lost some of 
> its clean architecture.
>
> The cleaned up, new-and-improved description of the Plan A approach is 
> available here:
>
> http://www.ietf.org/id/draft-roach-rtcweb-plan-a-00.txt
>
> Note that we've omitted discussion of glare reduction from that 
> document, as I believe that mid-session glare can be completely 
> avoided by applications implementing a set of non-normative behaviors. 
> These behaviors are described in the a separate companion document:
>
> http://www.ietf.org/id/draft-roach-rtcweb-glareless-add-00.txt
>
> Thanks.
>
> /a
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb