AW: [AVT] Working group last call: draft-ietf-avt-rtp-clearmode-02.txt

"Kreuter Ruediger" <Ruediger.Kreuter@siemens.com> Sat, 20 September 2003 13:54 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05051 for <avt-archive@odin.ietf.org>; Sat, 20 Sep 2003 09:54:56 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A0Nj9-0000G0-MF for avt-archive@odin.ietf.org; Fri, 19 Sep 2003 12:03:25 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h8JG3NNh000977 for avt-archive@odin.ietf.org; Fri, 19 Sep 2003 12:03:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A0Niu-00005L-Sz; Fri, 19 Sep 2003 12:03:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A0NiS-0008Ml-HN for avt@optimus.ietf.org; Fri, 19 Sep 2003 12:02:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04301 for <avt@ietf.org>; Fri, 19 Sep 2003 12:02:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A0J0j-0005Bq-00 for avt@ietf.org; Fri, 19 Sep 2003 07:01:13 -0400
Received: from thoth.sbs.de ([192.35.17.2]) by ietf-mx with esmtp (Exim 4.12) id 1A0Ise-0003Z8-00 for avt@ietf.org; Fri, 19 Sep 2003 06:52:52 -0400
Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by thoth.sbs.de (8.11.7/8.11.7) with ESMTP id h8JAqq507407 for <avt@ietf.org>; Fri, 19 Sep 2003 12:52:52 +0200 (MEST)
Received: from demchh202e.mchh.siemens.de (mchh2g1e.mchh.siemens.de [139.21.200.101]) by mail1.siemens.de (8.11.7/8.11.7) with ESMTP id h8JAqq621346 for <avt@ietf.org>; Fri, 19 Sep 2003 12:52:52 +0200 (MEST)
Subject: AW: [AVT] Working group last call: draft-ietf-avt-rtp-clearmode-02.txt
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Date: Fri, 19 Sep 2003 12:51:56 +0200
Message-ID: <7C222247E93DB64FA0078E8A4426435C286A90@mchh2g1e.mchh.siemens.de>
x-mimeole: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
Thread-Topic: [AVT] Working group last call: draft-ietf-avt-rtp-clearmode-02.txt
Thread-Index: AcN+AjA45oG9c9fsSwWqUxZTYNcfDAAmELLR
From: Kreuter Ruediger <Ruediger.Kreuter@siemens.com>
To: Linus Walleij <triad@df.lth.se>, avt@ietf.org
Content-Transfer-Encoding: base64
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: base64

I could add the following paragraph between the current
4th and 5th:
 
"Clearmode is not restricted to the examples described
 above. It can be used by any application, that does not
 need an encoding/decoding for transfer via a RTP
 connection."
 
and delete "VoIP-related " in the "Applications" section 
of chapter 4.
 
-> This should clarify, that Clearmode is not restricted
    to VoIP.
 
 
I agree that VoIP is stressed a little bit in this draft.
This is because it is the initiator. If you have any 
existing application besides VoIP, that uses Clearmode 
(will likely be named otherwise), I would be glad to 
add it as an example in chapter 4.
 
Regards,
Ruediger
 

	-----Ursprüngliche Nachricht----- 
	Von: Linus Walleij [mailto:triad@df.lth.se] 
	Gesendet: Do 18.09.2003 18:29 
	An: avt@ietf.org 
	Cc: 
	Betreff: Re: [AVT] Working group last call: draft-ietf-avt-rtp-clearmode-02.txt
	
	

	Here is an outsider review:
	
	This part in the introduction
	
	   ISDN wideband speech terminals do not rely on a voice data
	   processing, like echo cancellation or dual tone multifrequency (DTMF)
	   detection, within a VoIP media gateway.  And ISDN data terminals e.g.
	   will produce data streams that are not compatible with a non-linear
	   encoding as is used for voice.
	
	is worded like ISDN would be the only thing to be tunneled in clearmode.
	Maybe it could be formulated as a neutral means for tunneling, listing
	ISDN as *one* such /telephony/ application, if there may (in theory) be
	other possible applications.
	
	It should be noted if it is the intention of the authors that clearmode is
	only to be used for voice transfer, or if it is applicable to other RTP
	transfers at 64kbit as well, e.g. single-channel lossy ISDN data transfer
	or anything else coming in at 64kbit/second. The above quoted paragraph
	gives the impression that also data streams are allowed, while the draft
	mostly talks about VoIP.
	
	Yours,
	Linus Walleij
	
	
	_______________________________________________
	Audio/Video Transport Working Group
	avt@ietf.org
	https://www1.ietf.org/mailman/listinfo/avt