Re: [MMUSIC] Some more APPID questions

"Roni Even" <ron.even.tlv@gmail.com> Mon, 04 November 2013 08:05 UTC

Return-Path: <ron.even.tlv@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 59BFC11E80F2 for <mmusic@ietfa.amsl.com>; Mon, 4 Nov 2013 00:05:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 qcm2Ojzv+NyH for <mmusic@ietfa.amsl.com>; Mon, 4 Nov 2013 00:05:20 -0800 (PST)
Received: from mail-bk0-x233.google.com (mail-bk0-x233.google.com [IPv6:2a00:1450:4008:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 8441E11E8109 for <mmusic@ietf.org>; Mon, 4 Nov 2013 00:05:20 -0800 (PST)
Received: by mail-bk0-f51.google.com with SMTP id my12so912358bkb.10 for <mmusic@ietf.org>; Mon, 04 Nov 2013 00:05:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:thread-index :content-language; bh=EwgLs5L1np9odX65PjpFVy0Sf0z5VUcuJC1jypkFxCk=; b=Ioj/e/4n4PJ3BTR895mLiiPN/pX6hQNmxvIr6pDUeL2aY7tkj3BZmXj31zp4Y4ZHLc avNA1y54ycCw5qWCDhA3lgo69hNAoHOXPg5wK2v0coZz2C2mKTHORbrgX7yM6FgRBxFD oaM2PxcXfOGV8xxL5Rrqxf6CH4qduVtU/TwEsrak9lXzh6+tb8HU9FJzgTlwtreQXLAY enH5gSM66SlPpHXnKwwaaG+zsySCJYRaoZOT+LJdML18otmU3ebio1twGT1yRxsLTTtH 6r+MRzzsp83SO+0tHJJhKE1Iy1n4VJihzQ+O0UYJRc3FPsJ122Qy3VGO9U8bGJPWK1wd L++A==
X-Received: by 10.205.64.16 with SMTP id xg16mr306766bkb.42.1383552319439; Mon, 04 Nov 2013 00:05:19 -0800 (PST)
Received: from RoniE ([2001:67c:370:144:345d:3cd8:6b09:4b9c]) by mx.google.com with ESMTPSA id zl3sm13744062bkb.4.2013.11.04.00.05.17 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 04 Nov 2013 00:05:18 -0800 (PST)
From: Roni Even <ron.even.tlv@gmail.com>
To: 'Harald Alvestrand' <harald@alvestrand.no>, 'mmusic' <mmusic@ietf.org>
References: <52769448.7080606@alvestrand.no> <017001ced8de$a268f590$e73ae0b0$@gmail.com> <5276CE8B.8050809@alvestrand.no> <017801ced8e4$f6e021b0$e4a06510$@gmail.com> <5276E95B.5040909@alvestrand.no>
In-Reply-To: <5276E95B.5040909@alvestrand.no>
Date: Mon, 04 Nov 2013 10:02:01 +0200
Message-ID: <023401ced934$26bab4a0$74301de0$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQEJHLPXYj78WEr4Hhkvk0KFWNmBAwIZtPtxAkM5Q+cA47rwcgISIw/3m2WXMPA=
Content-Language: en-us
Subject: Re: [MMUSIC] Some more APPID questions
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: Mon, 04 Nov 2013 08:05:21 -0000

Harald,

If you map appID:45 to SSRC B also in RTP header and afterwards have
appID:45 map to SSRC A it means that you replaced SSRC B with SSRC A for
appId 45. The example is if appId 45 is the active speaker and it starts
from left camera with SSRC B and changes to right camera with SSRC A.

What is allowed is to have appID 45 and appID 27 both map to SSRC A. example
is appID 45 is active speaker and appID 27 is left camera and left camera is
the current active speaker.

Roni

> -----Original Message-----
> From: Harald Alvestrand [mailto:harald@alvestrand.no]
> Sent: 04 November, 2013 2:25 AM
> To: Roni Even; 'mmusic'
> Subject: Re: [MMUSIC] Some more APPID questions
> 
> On 11/03/2013 11:35 PM, Roni Even wrote:
> >
> >> -----Original Message-----
> >> From: Harald Alvestrand [mailto:harald@alvestrand.no]
> >> Sent: 04 November, 2013 12:31 AM
> >> To: Roni Even; 'mmusic'
> >> Subject: Re: [MMUSIC] Some more APPID questions
> >>
> >> On 11/03/2013 10:49 PM, Roni Even wrote:
> >>> Hi Harald,
> >>> The current draft is still not mature enough and the presentation
> >>> will have some information which is not there and some of the text
> >>> in the
> >>> 00 version that is not in the 01 version may come back.
> >>>
> >>> An SSRC can have multiple appIds example is in a three camera system
> >>> one appID for active speaker which is now the left camera having a
> >>> different appID
> >>>
> >>> The uniqueness of appID should be per media packet stream.
> >>>
> >> so if you have
> >>
> >> ssrc A: appid 45
> >> ssrc B: appid 27
> >>
> >> this means exactly the same thing as
> >>
> >> ssrc A: appid 45
> >> ssrc B: appid 45
> >>
> >> ?
> >>
> >> This seems to create issues when you have a single appid that is
> >> moving
> > around
> >> between SSRCs.
> > [Roni Even] The mapping from AppID to SSRC should be in SDES or RTP
> > header extension, example is appID 45 that can be first SSRC A and
> > then SSRC B if appId represent the active speaker.
> >
> 
> But if uniqueness of appids is per SSRC, then SSRC B might already be
using
> appid 45 for something else.
> 
> If we're using an appid for some property that can jump around between
> SSRCs, the uniqueness of that appid must be guaranteed over the whole
context
> it's jumping around inside, I think. I'm worried if I can't figure out
what that
> context is.
> 
> --
> Surveillance is pervasive. Go Dark.