Re: [AVTCORE] draft-westerlund-avtcore-multiplex-architecture-01 - same SSRC for SVC

"Roni Even" <ron.even.tlv@gmail.com> Sat, 17 March 2012 09:11 UTC

Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6017121F8652 for <avt@ietfa.amsl.com>; Sat, 17 Mar 2012 02:11:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.029
X-Spam-Level:
X-Spam-Status: No, score=-3.029 tagged_above=-999 required=5 tests=[AWL=-0.030, BAYES_00=-2.599, J_CHICKENPOX_16=0.6, RCVD_IN_DNSWL_LOW=-1]
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 l5CaoKmWTScs for <avt@ietfa.amsl.com>; Sat, 17 Mar 2012 02:11:30 -0700 (PDT)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9B1A221F8646 for <avt@ietf.org>; Sat, 17 Mar 2012 02:11:07 -0700 (PDT)
Received: by wibhj6 with SMTP id hj6so1445225wib.13 for <avt@ietf.org>; Sat, 17 Mar 2012 02:11:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; bh=k3S2AZcqgCwH1tjUIWQPPgTzUgqHxpW/xRg+2WzE2Z0=; b=lWmNmCYNnQ92UVJa2M1EkDPpLBNYOhGw7tGNv7PEjwkqlXdkxy4IdcrDUTylaWkqal btV7Gnqwe4oHJDXxexC40RdmvPKJEoXf7eHg6mqyw+yBY3A+faJmNDFnWwPmnwaMcvEu hG08pyhhcmJE+y+sSohWAyscs15YQWrvlVpgDvhKq9xhxounwK6QylJC9VgF3UaouTim PbqgACaYUzNuqbX22eeSiAr1KWooEgKAS4LgGdv/M+M4bOOni5mU8UJqVMi/Fd8mpwgh tOcwMvX+CTLYxOBV/iKA+nP8z0XT9jiadatPSAPgR8Ovl4z5jjOG6OjIIvRhwDyMr4pU p6vg==
Received: by 10.180.78.233 with SMTP id e9mr5103927wix.0.1331975466795; Sat, 17 Mar 2012 02:11:06 -0700 (PDT)
Received: from windows8d787f9 (bzq-79-179-219-130.red.bezeqint.net. [79.179.219.130]) by mx.google.com with ESMTPS id fl2sm9789551wib.4.2012.03.17.02.11.04 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 17 Mar 2012 02:11:05 -0700 (PDT)
From: Roni Even <ron.even.tlv@gmail.com>
To: 'Magnus Westerlund' <magnus.westerlund@ericsson.com>
References: <4f62249b.8a0eb40a.628f.6e47@mx.google.com> <4F62EE9F.8080204@ericsson.com> <4f634347.2614b40a.036d.fffff329@mx.google.com> <4F635700.8050505@ericsson.com>
In-Reply-To: <4F635700.8050505@ericsson.com>
Date: Sat, 17 Mar 2012 11:10:06 +0200
Message-ID: <4f645529.2266b40a.193a.fffff25e@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac0DhmUVMz8kwP7vQmKnctJhrnkAxQAlIh2Q
Content-Language: en-us
Cc: 'IETF AVTCore WG' <avt@ietf.org>
Subject: Re: [AVTCORE] draft-westerlund-avtcore-multiplex-architecture-01 - same SSRC for SVC
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Mar 2012 09:11:31 -0000

Hi,
I will just address the SVC multiplexing issue and start a different thread
on the session and ssrc multiplexing and the relation between RTP session
and the transport infrastructure used which is also discussed in
draft-alvestrand-rtp-sess-neutral-00.

As for the SVC example in the document, I think that the reason for MST mode
is because the idea is to use the session multiplexing based on different
UDP ports to divide the streams, for example in multicast allowing the users
to join just the relevant multicast groups. IF you want SSRC multiplexing in
SVC you can use SST (Single Session Transmission) mode and I think this is
the reason there is no need to address SSRC multiplexing using multiple
sessions to a single UDP receive port is not discussed.

What I am saying is that the example in 3.2 is not correct since it was not
addressed on purpose being non relevant use for MST.
Roni Even

> -----Original Message-----
> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> Sent: Friday, March 16, 2012 5:07 PM
> To: Roni Even
> Cc: 'IETF AVTCore WG'
> Subject: Re: [AVTCORE] draft-westerlund-avtcore-multiplex-architecture-
> 01 - same SSRC
> 
> On 2012-03-16 14:41, Roni Even wrote:
> > Hi Magnus,
> > I thought that RFC5583 is used to signal the media decoding
> dependency
> > between the different sessions as mentioned in section 7.2.3 of RFC
> 6190.
> > I also think that this allows you to provide also the SSRC value of
> > the different RTP streams.
> 
> No, to my understanding RFC 5583 only defines how the media description
> grouping to indicate which m= lines that contains dependent media. And
> the a=depend SDP attribute links which RTP payload types in the
> respective media descriptions. There is no linking of the SSRCs. So
> when there is more than one SSRC with a given CNAME you have no other
> defined method than to use the same SSRC value across sessions.
> 
> Cheers
> 
> Magnus Westerlund
> 
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone  +46 10 7148287
> Färögatan 6                | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------