RE: [AVT] I-D ACTION:draft-ietf-avt-tcrtp-08.txt

"Yaakov Stein" <yaakov_s@rad.com> Mon, 20 September 2004 10:07 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16752 for <avt-archive@ietf.org>; Mon, 20 Sep 2004 06:07:12 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C9LAs-0001yQ-MN for avt-archive@ietf.org; Mon, 20 Sep 2004 06:13:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C9L2u-0005oQ-Mo; Mon, 20 Sep 2004 06:05:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C9L0Q-0005Oj-G0 for avt@megatron.ietf.org; Mon, 20 Sep 2004 06:02:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16431 for <avt@ietf.org>; Mon, 20 Sep 2004 06:02:42 -0400 (EDT)
Received: from radmail1.rad.co.il ([62.0.23.193] helo=antivir1.rad.co.il) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C9L6X-0001qV-4X for avt@ietf.org; Mon, 20 Sep 2004 06:09:06 -0400
Received: from antivir1.rad.co.il ([127.0.0.1]) by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id i8KA25S8001745 for <avt@ietf.org>; Mon, 20 Sep 2004 12:02:05 +0200 (IST)
Received: from exrad2.ad.rad.co.il (exrad2 [192.114.24.112]) by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id i8KA255J001742 for <avt@ietf.org>; Mon, 20 Sep 2004 12:02:05 +0200 (IST)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] I-D ACTION:draft-ietf-avt-tcrtp-08.txt
Date: Mon, 20 Sep 2004 12:59:02 +0300
Message-ID: <27A0F290348F8E45AEF79889DDE65A5203063C17@exrad2.ad.rad.co.il>
Thread-Topic: [AVT] I-D ACTION:draft-ietf-avt-tcrtp-08.txt
Thread-Index: AcSZztHpvBt6ApZTQoSyQEH4mPAOLwFJ7gzg
From: Yaakov Stein <yaakov_s@rad.com>
To: avt@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: quoted-printable
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: quoted-printable

 
While I completely agree with the motivation behind this draft,
I have problems with the proposed technique.

In section 1.1 we find:

   While some voice-over-packet technologies such as Voice over 
   ATM (VoAAL2, [I.363.2]) and Voice over MPLS provide bandwidth 
   efficiencies because both technologies lack IP, UDP, and RTP 
   headers, neither VoATM nor VoMPLS provide direct access to voice-
   over-packet services available to Voice over IP.  

The savings of VoATM and VoMPLS (and now ITU Y.1414) are mainly 
due to multiplexing multiple channels into a packet with a single
header,
and not merely to not having the RTP/UDP/IP headers.
Indeed, the significance of the overhead diminishes with the number
of multiplexed channels.

So to solve the efficiency problem we need a simple method to multiplex
multiple
channels into a single packet, such as the mechanisms specified in
Y.1414.

The TCRTP draft indeed uses standard mechanisms to multiplexing
channels, 
but, its mechanisms are needlessly complex 
(compression techniques to reduce the overhead, then PPP muxing to
combine them, 
then placing the resulting stream into an L2TP tunnel, and then
performing a further 
header compression on the L2TP/IP headers). 

Why should we go to such lengths when much simpler mechanisms can be
used?

Y(J)S

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