Re: [MMUSIC] Unified Plan for SDP Handling - multiple media sources

Martin Thomson <martin.thomson@gmail.com> Thu, 18 July 2013 02:21 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 994FE21F9943 for <mmusic@ietfa.amsl.com>; Wed, 17 Jul 2013 19:21:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.924
X-Spam-Level:
X-Spam-Status: No, score=-1.924 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, NO_RELAYS=-0.001]
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 GVhnsDlun1lZ for <mmusic@ietfa.amsl.com>; Wed, 17 Jul 2013 19:21:23 -0700 (PDT)
Received: from mail-we0-x231.google.com (mail-we0-x231.google.com [IPv6:2a00:1450:400c:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id C417521F96EF for <mmusic@ietf.org>; Wed, 17 Jul 2013 19:21:22 -0700 (PDT)
Received: by mail-we0-f177.google.com with SMTP id m19so2400925wev.22 for <mmusic@ietf.org>; Wed, 17 Jul 2013 19:21:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=U3yR16LlqXZggpVXkKqLXK7ZVsLEvYZvGbd6RQn8UPQ=; b=jiUWsykdNUl/bMj2HdopX/CGvkYMc/AV3gJR9nS9KsIm5ElnHdgdcHRnegN9BfM1LR Dlebf9V+AV0xx88/CubZbIjX/jbPfEuf8cnEC549gibUrmy1HqMPn9C1Q2/psrf6ZOsu 5WUDD14LMgVaKsVTIdbDbTTq8C3GAXpWeg1QZj2/fh0JBt+q8HLtCVJrb6dlfJ63RwjG hDuihYUAaHkmClwfUnRznSzNVbVzaUaeUnOE7IvDbEH+OqIWUtCPNs1yB3cV6CZT2b9T uMcKeiHcFMGC6AsSv4hFUC7b91UzIm4NmJNpzNvj2CMHsphyKsoFJJqkhN/0viRl4/6c R/qA==
MIME-Version: 1.0
X-Received: by 10.180.9.212 with SMTP id c20mr17623670wib.65.1374114081927; Wed, 17 Jul 2013 19:21:21 -0700 (PDT)
Received: by 10.194.60.46 with HTTP; Wed, 17 Jul 2013 19:21:21 -0700 (PDT)
In-Reply-To: <51E71052.7010206@nostrum.com>
References: <00ad01ce826e$43666300$ca332900$@gmail.com> <CABkgnnVWL71QPOjqxXJCEr1NK93JOwpmY_CgiObpcUdfaDk2jA@mail.gmail.com> <AE206958-4085-4B6C-A747-D4D60C5CD7FE@vidyo.com> <51E61C99.8040305@nostrum.com> <A0791C6A-9F74-4FA6-BD6B-FCBAF9A5E966@vidyo.com> <51E71052.7010206@nostrum.com>
Date: Wed, 17 Jul 2013 19:21:21 -0700
Message-ID: <CABkgnnVVFxYtMcn06iS1J7_4PaLsEXwCcy-OWG6CmWsFXRsNKg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Adam Roach <adam@nostrum.com>
Content-Type: text/plain; charset="UTF-8"
Cc: Jonathan Lennox <jonathan@vidyo.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Unified Plan for SDP Handling - multiple media sources
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jul 2013 02:21:23 -0000

On 17 July 2013 14:44, Adam Roach <adam@nostrum.com> wrote:
> On 7/17/13 16:40, Jonathan Lennox wrote:
>>
>> That said, what I still don't see is, if you have the correlator, why you
>> then actually need to send the a=ssrc in the SDP at all? The correlator
>> should be sufficient for disambiguation, and it lets the sender switch the
>> ssrc it's sending for an m-line without needing a fresh offer/answer.
>
>
> That might be worth exploring. I honestly haven't given it a whole lot of
> thought. Perhaps Justin or Martin have a more well-formed opinion on the
> topic?

I did consider this, but there are several reasons that I prefer to
have signaling.  The main one being that it is the only guaranteed way
to get this information through.  In the happy cases, the RTP header
is enough, but if you are losing packets at session startup (a real
possibility in some configurations), or RTP header extensions are
being dropped, or you need to communicate about an in progress stream
and can't guarantee that you can cause the sender to re-send a few
packets with the header extension, or ...

Basically, there are too many ways for the RTP extension to break.
Not enough that it isn't hugely valuable for dealing with the race,
but it can't be the only mechanism that you rely on.