RE: [AVT] Retransmission draft

"Rolf Hakenberg" <hakenberg@panasonic.de> Tue, 16 December 2003 13:03 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13825 for <avt-archive@odin.ietf.org>; Tue, 16 Dec 2003 08:03:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AWEr3-0000fV-7D for avt-archive@odin.ietf.org; Tue, 16 Dec 2003 08:03:14 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBGD3DT3002563 for avt-archive@odin.ietf.org; Tue, 16 Dec 2003 08:03:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AWEqs-0000en-D6; Tue, 16 Dec 2003 08:03:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AWEqa-0000eY-A9 for avt@optimus.ietf.org; Tue, 16 Dec 2003 08:02:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13806 for <avt@ietf.org>; Tue, 16 Dec 2003 08:02:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AWEqZ-0000eP-00 for avt@ietf.org; Tue, 16 Dec 2003 08:02:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AWEqX-0000eD-00 for avt@ietf.org; Tue, 16 Dec 2003 08:02:42 -0500
Received: from mail.pel.panasonic.de ([194.162.191.12]) by ietf-mx with esmtp (Exim 4.12) id 1AWEqX-0000e1-00 for avt@ietf.org; Tue, 16 Dec 2003 08:02:41 -0500
Received: from MCOMLAP3 ([10.10.150.80]) by mail.pel.panasonic.de with Microsoft SMTPSVC(5.0.2195.6713); Tue, 16 Dec 2003 14:02:16 +0100
From: Rolf Hakenberg <hakenberg@panasonic.de>
To: Colin Perkins <csp@csperkins.org>
Cc: gamze@vidiator.com, rey@panasonic.de, avt@ietf.org, David.Leon@nokia.com, viktor.varsa@nokia.com, magnus.westerlund@era.ericsson.se
Subject: RE: [AVT] Retransmission draft
Date: Tue, 16 Dec 2003 14:02:15 +0100
Message-ID: <KOEBJFEGEMJGMHKFMNKPEEGJJFAA.hakenberg@panasonic.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <20031207191302.665669f8.csp@csperkins.org>
X-OriginalArrivalTime: 16 Dec 2003 13:02:16.0062 (UTC) FILETIME=[D468B1E0:01C3C3D4]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
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>
Content-Transfer-Encoding: 7bit

Dear Colin and all,

> > At the last 3GPP SA4 meeting there was a consensus on to make RTP
> > Retransmission a working assumption in PSS Rel-6, subject to
> the concerns
> > on server complexity and delay being addressed at the next meeting.
>
> Do you expect addressing these concerns to require changes to the draft?

No, I do not expect this to happen.

The comments and concerns expressed at 3GPP have been quite specific to the
3GPP PSS (packet based streaming)environment and proposed use of RTP RTX in
this requirement. One question for example was the correlation of RTP RTX
with retransmission in the radio link control (RLC) layer considering the
RLC discard timer and possible additional delay introduced by RTP RTX.

Questions on complexity are very much implementation dependent and the draft
already provides good general information about this issue in chapter 10. I
do not see a need to elaborate any further on this issue in the draft.

FYI: If 3GPP finds any information important for an implementor of RTP RTX
in a 3GPP PSS environment, it has means to put this information as
"informative parts" into the 3GPP specifiction.


Best Regards,
Rolf.


>
> > Important for our current discussion on potential IPRs and how to
> > progress the draft is the fact that there was no condition on the IPR
> > issues, but in fact conditions that the draft should move to RFC on
> > standards track before the finalisation of 3GPP Rel-6.
>
> Moving to the standards track requires resolution of the IPR issue within
> AVT, of course.
>
> --
> Colin Perkins
> http://csperkins.org/
>


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