Re: [MMUSIC] Scope of RTP payload types in BUNDLE?

Cullen Jennings <> Wed, 05 June 2013 00:02 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 79D1421F9A3A for <>; Tue, 4 Jun 2013 17:02:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.497
X-Spam-Status: No, score=-1.497 tagged_above=-999 required=5 tests=[AWL=0.283, BAYES_00=-2.599, DATE_IN_PAST_24_48=1.219, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id t+pRWi049eTn for <>; Tue, 4 Jun 2013 17:02:07 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 2129D21F9A2B for <>; Tue, 4 Jun 2013 17:01:59 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id D76302FD7CD for <>; Tue, 4 Jun 2013 20:01:54 -0400 (EDT)
Received: from [] (unknown []) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id 5F17A22E256; Tue, 4 Jun 2013 20:01:51 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Cullen Jennings <>
In-Reply-To: <>
Date: Mon, 03 Jun 2013 16:51:19 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <>
To: Paul Kyzivat <>
X-Mailer: Apple Mail (2.1503)
Subject: Re: [MMUSIC] Scope of RTP payload types in BUNDLE?
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 05 Jun 2013 00:02:19 -0000

Imagine Alice sends  an offer containing 

On May 27, 2013, at 10:56 AM, Paul Kyzivat <> wrote:

> m=audio 49172 RTP/AVP 96
>  a=ssrc:2222
>  a=rtpmap:96 G7291/16000

Let say that an offer sent like the above. That means nothing about the SSRC for the packets that Alice will receive. And it is likely to receive RTP packets before it receives an answer in some important scenarios. 

So a RTP packet SSRC 3333 arrives. There's no information from the SSRC about what m-line it matches too (but RTCP for it can be sent). 

Now an answer from Bob arrives with 

m=audio 55555 RTP/AVP 96
 a=rtpmap:96 G7291/16000

Now a packet with SSRC 4444 arrives. That might be from Bob, but here's the rub. It might be from Charlie. If there was an SSRC collisions between Bob and Charlie, it will be awhile before some SDP shows up that says that there was a collisions and now Bob is using SSRC 5555. 

This is all a disaster and the best solutions to it IMHO would be to define a new RTP Header extension that carries and identifier and that Alice can tell Bob in the SDP offer what value to put in the identifier for the RTP from Bob to Alice. 

I've see more than one system that have stuffed that identifier in the existing CSRC field which is sort of an awful hack and sort of very cool.