[AVT] RTP topologies and terms

<Ye-Kui.Wang@nokia.com> Tue, 11 September 2007 22:13 UTC

Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IVDza-0000hI-4j; Tue, 11 Sep 2007 18:13:58 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IVDzY-0000hC-Q5 for avt@ietf.org; Tue, 11 Sep 2007 18:13:56 -0400
Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IVDzY-0002lR-94 for avt@ietf.org; Tue, 11 Sep 2007 18:13:56 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145]) by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l8BMDrWm020439 for <avt@ietf.org>; Wed, 12 Sep 2007 01:13:54 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 12 Sep 2007 01:13:53 +0300
Received: from trebe101.NOE.Nokia.com ([172.22.124.61]) by esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 12 Sep 2007 01:13:53 +0300
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 12 Sep 2007 01:13:48 +0300
Message-ID: <1C1F3D15859526459B4DD0A7A9B2268B03D7A7AC@trebe101.NOE.Nokia.com>
In-Reply-To: <46E509CB.6040206@ericsson.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: RTP topologies and terms
Thread-Index: AcfzilYrmVv8L+duSbGJQl5igwLE/wBMgljQ
References: <E1ITgU2-0004uI-19@stiedprstage1.ietf.org> <46E509CB.6040206@ericsson.com>
From: Ye-Kui.Wang@nokia.com
To: avt@ietf.org
X-OriginalArrivalTime: 11 Sep 2007 22:13:53.0425 (UTC) FILETIME=[09D64010:01C7F4C1]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Subject: [AVT] RTP topologies and terms
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Dear RTP Experts,

Could anyone help to clarify the following: what is the RTP topology,
and what is the right term for end-point B?

The topology is as follows:

      +----+           +---+             +---+
       | A  |=====>| B | ----------->| C |
      +----+           +---+             +---+

- A sends a scalable bitstream of multiple layers using multiple RTP
sessions (layered multicast).
- B aggregates the input RTP streams from the multiple RTP sessions to
one RTP stream and sends to C. 

I failed to map the topology to any of those (or their combinations)
mentioned in draft-ietf-avt-topologies-06.txt , where all seem talking
about end points within one RTP session. Also I am wondering whether B
can be called a translator, mixer or (RTCP terminating) MCU? There are
multiple RTP sessions between A and B, and there seems to be only one
RTP sessions between B and C, therefore B terminates RTP sessions. If
this is true, then B can neither be called translator nor mixer,
according to the comment made by Colin earlier (on August 18 2007 in the
AVT reflector that "Neither an RTP translator or a RTP mixer terminate
the RTP session."). Or is it so that the one RTP stream from B to C are
still of multiple sessions (hence B does not terminate RTP sessions)?

BR, YK

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt