RE: [AVT] RTP streaming and adaptation to AVC of an SVC temporalscalable bitstream - Packet loss

<Ye-Kui.Wang@nokia.com> Sun, 19 August 2007 05:35 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 1IMdRQ-00051S-CC; Sun, 19 Aug 2007 01:35:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IMdRN-0004ld-6C for avt@ietf.org; Sun, 19 Aug 2007 01:35:09 -0400
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IMdRL-0004rE-JU for avt@ietf.org; Sun, 19 Aug 2007 01:35:09 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l7J5Z0S8027563; Sun, 19 Aug 2007 08:35:01 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 19 Aug 2007 08:34:59 +0300
Received: from trebe101.NOE.Nokia.com ([172.22.124.61]) by esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 19 Aug 2007 08:34:59 +0300
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] RTP streaming and adaptation to AVC of an SVC temporalscalable bitstream - Packet loss
x-mimeole: Produced By Microsoft Exchange V6.5
Date: Sun, 19 Aug 2007 08:34:57 +0300
Message-ID: <1C1F3D15859526459B4DD0A7A9B2268B03BE988E@trebe101.NOE.Nokia.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [AVT] RTP streaming and adaptation to AVC of an SVC temporalscalable bitstream - Packet loss
Thread-Index: AcfhwpAgOTvCIo7CQnaNxXxJvXRGhQAHZb3QABB3MzA=
References: <009001c7e0dc$b114dd30$11010a0a@bsoft007> <1C1F3D15859526459B4DD0A7A9B2268B03BE988B@trebe101.NOE.Nokia.com> <78541B84-1BC4-4586-9B2D-A8E8A7707416@csperkins.org>
From: Ye-Kui.Wang@nokia.com
To: csp@csperkins.org
X-OriginalArrivalTime: 19 Aug 2007 05:34:59.0612 (UTC) FILETIME=[AEFFE5C0:01C7E222]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: avt@ietf.org
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

 
OK, forget about my naïve question, because I found the following sentence in RFC 3550, "If multiple data packets are re-encoded into one, or vice versa, a translator MUST assign new sequence numbers to the outgoing packets." 

BR, YK 

>-----Original Message-----
>From: Wang Ye-Kui (Nokia-NRC/Tampere) 
>Sent: Sunday, August 19, 2007 12:59 AM
>To: 'ext Colin Perkins'
>Cc: daniele@bsoft.info; avt@ietf.org
>Subject: RE: [AVT] RTP streaming and adaptation to AVC of an 
>SVC temporalscalable bitstream - Packet loss
>
>
>Hi Colin, 
>
>Thanks for your clarification. But according to the following 
>sentence copied from Daniele's email, 
>
>"... then the SVCtoAVC adapter doesn't know whether this loss 
>has to be signaled to the receiver, i.e. whether it must 
>insert a sequence number gap in the outcoming RTP stream...", 
>
>the SVCtoAVC adapter uses a different RTP sequence number 
>value space for the outcoming RTP steam than the incoming RTP 
>stream. Is this what a translator can do? It is not clear how 
>the SVCtoAVC adapter handles the CC, SSRC and CSRC fields and 
>RTCP traffic, though. 
>
>BR, YK
>
>>-----Original Message-----
>>From: ext Colin Perkins [mailto:csp@csperkins.org]
>>Sent: Saturday, August 18, 2007 9:07 PM
>>To: Wang Ye-Kui (Nokia-NRC/Tampere)
>>Cc: daniele@bsoft.info; avt@ietf.org
>>Subject: Re: [AVT] RTP streaming and adaptation to AVC of an SVC 
>>temporalscalable bitstream - Packet loss
>>
>>On 18 Aug 2007, at 18:36, <Ye-Kui.Wang@nokia.com> wrote:
>>> In your example the SVCtoAVC adapter is an RTP mixer, which
>>terminates
>>> the RTP session between the sender and itself and restarts
>>another RTP
>>> session between itself and the receiver.
>>> Therefore the RTP sequence number needs to be updated for the base 
>>> layer packets anyway.
>>
>>If the SVCtoAVC adapter is a transcoder from an SVC stream to an AVC 
>>stream, it will be an RTP translator, not an RTP mixer.
>>Neither an RTP translator or a RTP mixer terminate the RTP 
>session. RFC 
>>3550 and draft-ietf-avt-topologies-06.txt discuss this in more detail.
>>
>>--
>>Colin Perkins
>>http://csperkins.org/
>>
>>
>>

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