Re: [AVTCORE] Fwd: I-D Action: draft-westerlund-avtcore-rtp-topologies-update-01.txt
Magnus Westerlund <magnus.westerlund@ericsson.com> Wed, 14 November 2012 14:57 UTC
Return-Path: <magnus.westerlund@ericsson.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 84CCD21F85ED for <avt@ietfa.amsl.com>; Wed, 14 Nov 2012 06:57:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.14
X-Spam-Level:
X-Spam-Status: No, score=-106.14 tagged_above=-999 required=5 tests=[AWL=0.109, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vuV3CRB8TVbq for <avt@ietfa.amsl.com>; Wed, 14 Nov 2012 06:57:09 -0800 (PST)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 88F4621F85EB for <avt@ietf.org>; Wed, 14 Nov 2012 06:57:08 -0800 (PST)
X-AuditID: c1b4fb30-b7f936d0000018b3-95-50a3b142a9c0
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 11.2F.06323.241B3A05; Wed, 14 Nov 2012 15:57:07 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0191.eemea.ericsson.se (153.88.115.85) with Microsoft SMTP Server id 8.3.279.1; Wed, 14 Nov 2012 15:57:06 +0100
Message-ID: <50A3B141.5000900@ericsson.com>
Date: Wed, 14 Nov 2012 15:57:05 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Roni Even <ron.even.tlv@gmail.com>
References: <20121015142026.6075.9386.idtracker@ietfa.amsl.com> <507C1C7C.8080007@ericsson.com> <060c01cdb2b0$aa047720$fe0d6560$@gmail.com>
In-Reply-To: <060c01cdb2b0$aa047720$fe0d6560$@gmail.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFuplluLIzCtJLcpLzFFi42KZGfG3Rtd54+IAg1Pb2Sxe9qxkt/jbzuzA 5LFz1l12jyVLfjIFMEVx2aSk5mSWpRbp2yVwZVxYzFvwiadizaNNLA2M67i6GDk5JARMJE48 m8kEYYtJXLi3nq2LkYtDSOAko8ShczsZIZzljBJbl25n7WLk4OAV0JZYP9MVpIFFQFXiweLj jCA2m4CFxM0fjWwgtqhAsMSeY2vB4rwCghInZz5hAbFFBNQkXq/9zAYyhllAReLt4UKQsLBA rMTGfzdYIVZ1M0qsPtfNDlLDCTRz0pdEiNskJd6+f8UMYjML6ElMudrCCGHLSzRvnQ0WFwK6 rKGpg3UCo9AsJJtnIWmZhaRlASPzKkb23MTMnPRy802MwCA9uOW3wQ7GTffFDjFKc7AoifPq qe73FxJITyxJzU5NLUgtii8qzUktPsTIxMEp1cDoulsjNe3Z/iQxgZks0c8U9OZd/RIeuvTb tdrL9+5v4cpzmZguN3dPZHDYyQKxf83XNoe/bk7UnGAmeLYydUbSvGeWPJbi6aVViS+sDWre /NZU9Y+SlFkl+Z4jbJcd/5ID/9+7u+rZqn60TZx8Rl66VmrlX4269RzvE9teztMTU1QI9Tfc P1mJpTgj0VCLuag4EQDCZXubIAIAAA==
Cc: 'IETF AVTCore WG' <avt@ietf.org>
Subject: Re: [AVTCORE] Fwd: I-D Action: draft-westerlund-avtcore-rtp-topologies-update-01.txt
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: Wed, 14 Nov 2012 14:57:09 -0000
Hi, Sorry for the delay in responding. On 2012-10-25 15:00, Roni Even wrote: > Hi Magnus, > I read the draft so to answer the questions > > 1. I think the document need also to discuss the SDES behavior (CNAME must > be forwarded to support the CSRC) specified in 7.2 and 7.3 of RFC 3550 for > the different topologies (we had recently a discussion about using SDES > messages). Yes, that is a good idea. > 2. I did not fully understand the SSRC behavior for source projecting > middlebox and how it is different from the topologies in 3.5. The difference between a RTP mixer and a source projecting mixer and its usage of SSRCs are as follow. Source projection: SSRC has a one to one relation to a CSRC RTP Mixer: Has one SSRC that carries content from potentially multiple CSRCs. The big difference is that an RTP mixer's SSRC contains either a selection or a media level mix/composition of the contributed media streams. A source projection mixer really is a way of projecting the other media sources in the conference into the RTP session between the Mixer and this particular conference participant. Does this make it clearer? 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 ----------------------------------------------------------------------
- [AVTCORE] Fwd: I-D Action: draft-westerlund-avtco… Magnus Westerlund
- Re: [AVTCORE] Fwd: I-D Action: draft-westerlund-a… Schwarz, Albrecht (Albrecht)
- Re: [AVTCORE] Fwd: I-D Action: draft-westerlund-a… Roni Even
- Re: [AVTCORE] Fwd: I-D Action: draft-westerlund-a… Magnus Westerlund
- Re: [AVTCORE] Fwd: I-D Action: draft-westerlund-a… Magnus Westerlund
- Re: [AVTCORE] Fwd: I-D Action: draft-westerlund-a… Magnus Westerlund