Re: [codec] #5: Mention in requirements, FAX?

Marc Petit-Huguenin <petithug@acm.org> Fri, 02 April 2010 14:32 UTC

Return-Path: <petithug@acm.org>
X-Original-To: codec@core3.amsl.com
Delivered-To: codec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3BB333A6784 for <codec@core3.amsl.com>; Fri, 2 Apr 2010 07:32:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.392
X-Spam-Level:
X-Spam-Status: No, score=-100.392 tagged_above=-999 required=5 tests=[AWL=0.743, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v9LE2IPuKx3I for <codec@core3.amsl.com>; Fri, 2 Apr 2010 07:32:46 -0700 (PDT)
Received: from server.implementers.org (server.implementers.org [69.55.225.91]) by core3.amsl.com (Postfix) with ESMTP id BC4103A688D for <codec@ietf.org>; Fri, 2 Apr 2010 07:32:45 -0700 (PDT)
Received: by server.implementers.org (Postfix, from userid 1001) id 436B9DC0401A; Fri, 2 Apr 2010 14:33:19 +0000 (UTC)
Received: from [192.168.2.3] (server.implementers.org [127.0.0.1]) by server.implementers.org (Postfix) with ESMTPA id EE8FCDC04018; Fri, 2 Apr 2010 14:33:17 +0000 (UTC)
Message-ID: <4BB6002C.9090303@acm.org>
Date: Fri, 02 Apr 2010 07:33:16 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100307 Iceowl/1.0b1 Icedove/3.0.3
MIME-Version: 1.0
To: codec@ietf.org
References: <05542EC42316164383B5180707A489EE1D0AA5F54E@EMBX02-HQ.jnpr.net> <4BAF776D.20904@acm.org> <6e9223711003281100q7e1f7ac0pd548a2ab40e95ba4@mail.gmail.com> <4BAF9E7B.1070708@acm.org> <4BB58E31.2050809@coppice.org> <617DF0128820F9458AC39149A627EE6C01A2A21146@MBX.dialogic.com> <m2o6e9223711004020653jb5d773eejdea1ec98367c7ff0@mail.gmail.com> <4BB5F7B6.1080808@stpeter.im> <q2j6e9223711004020701u5151687dx7c5be128e3517560@mail.gmail.com> <0BD7AE28-298A-4586-9FB4-33925A8F8B8C@freeswitch.org> <003601cad26f$c376b520$4a641f60$@de>
In-Reply-To: <003601cad26f$c376b520$4a641f60$@de>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Subject: Re: [codec] #5: Mention in requirements, FAX?
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Codec WG <codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/codec>
List-Post: <mailto:codec@ietf.org>
List-Help: <mailto:codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Apr 2010 14:32:47 -0000

On 04/02/2010 07:21 AM, Christian Hoene wrote:
> Hi guys,
> 
> just for the notes. Testing Fax (http://en.wikipedia.org/wiki/Fax#History) is definitely out of scope?

And V8bis? V.21? V.25? V.32/V32bis?  V.18?  SS5?

All this stuff should be out of scope and the text should say that terminals
that needs this MUST do it out of band, so no tests are needed.

> 
> Christian
> 
> ---------------------------------------------------------------
> Dr.-Ing. Christian Hoene
> Interactive Communication Systems (ICS), University of Tübingen 
> Sand 13, 72076 Tübingen, Germany, Phone +49 7071 2970532 
> http://www.net.uni-tuebingen.de/
> 
> 
>> -----Original Message-----
>> From: codec-bounces@ietf.org [mailto:codec-bounces@ietf.org] On Behalf Of Brian West
>> Sent: Friday, April 02, 2010 4:10 PM
>> To: stephen botzko
>> Cc: codec@ietf.org
>> Subject: Re: [codec] #5: Mention DTMF in requirements
>>
>> But Codecs themselves do not detect DTMF.  Thats the job of the DTMF detector.  NOT the codec.  In all
>> my work with codecs I have not once seen one that knows anything about DTMF.  And if the codec is too
>> lossy inband is out of the question.
>>
>> /b
>>
>> On Apr 2, 2010, at 9:01 AM, stephen botzko wrote:
>>
>>> I heard no decision as to DTMF tone encoding.
>>>
>>> As far as I am concerned, the question of whether the codec MUST encode DTMF tones accurately enough
>> to be detected at the decoder output (or SHOULD or non-requirement) is still open.
>>>
>>> That question clearly is in-scope, and has nothing to do with signaling.
>>>
>>> Stephen Botzko
>>
>> _______________________________________________
>> codec mailing list
>> codec@ietf.org
>> https://www.ietf.org/mailman/listinfo/codec
> 
> _______________________________________________
> codec mailing list
> codec@ietf.org
> https://www.ietf.org/mailman/listinfo/codec
> 


-- 
Marc Petit-Huguenin
Personal email: marc@petit-huguenin.org
Professional email: petithug@acm.org
Blog: http://blog.marc.petit-huguenin.org