Re: [codec] #5: Mention in requirements, FAX?
stephen botzko <stephen.botzko@gmail.com> Fri, 02 April 2010 14:58 UTC
Return-Path: <stephen.botzko@gmail.com>
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 16EC23A6A2D for <codec@core3.amsl.com>; Fri, 2 Apr 2010 07:58:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.052
X-Spam-Level:
X-Spam-Status: No, score=-1.052 tagged_above=-999 required=5 tests=[AWL=0.416, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 cBzQuc-rr7uQ for <codec@core3.amsl.com>; Fri, 2 Apr 2010 07:58:32 -0700 (PDT)
Received: from mail-yw0-f200.google.com (mail-yw0-f200.google.com [209.85.211.200]) by core3.amsl.com (Postfix) with ESMTP id 12AB23A6A0E for <codec@ietf.org>; Fri, 2 Apr 2010 07:58:31 -0700 (PDT)
Received: by ywh38 with SMTP id 38so1443693ywh.29 for <codec@ietf.org>; Fri, 02 Apr 2010 07:59:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=kKRM9r03IIhHqU9WFdNbVUSnK/tshZb8U64MqPA0naE=; b=YOwRCPtLMg6C6Z+Mkf2i8q4D2km1g3VsjpAwnFm4NEdyxNChdHMDT76mqja2sUtVQp 0mcqA6CeWzUcgCA5BTy3teJq7ypFyFv4ReifvVYXPWA7a5zjZXCveR7pYcTqsD0jZCL2 Xt7RmTFuc1DBAQY2nHrxYPkEiYZsbDgdskQtg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=DkWo187wWcoR2aDXK1/AqWeiqiV3GS3iBJid9UqtGJGGy/utpDtNKExo8E0ppuvmI1 W02UfpXYhODTIIcwSk6UXJYeJsUdLADE312Onu5V+zMR2mU7WmN7zAmq3QixPngZJC5L FLKAXAg5mlbQP1T/ElTihxl36mc5wDv3JytiA=
MIME-Version: 1.0
Received: by 10.231.85.133 with HTTP; Fri, 2 Apr 2010 07:59:01 -0700 (PDT)
In-Reply-To: <C7DB51C9.13E3C%mknappe@juniper.net>
References: <4BB6002C.9090303@acm.org> <C7DB51C9.13E3C%mknappe@juniper.net>
Date: Fri, 02 Apr 2010 10:59:01 -0400
Received: by 10.101.184.7 with SMTP id l7mr6070477anp.214.1270220342093; Fri, 02 Apr 2010 07:59:02 -0700 (PDT)
Message-ID: <m2z6e9223711004020759h4907d7a4j574b9bba509358c2@mail.gmail.com>
From: stephen botzko <stephen.botzko@gmail.com>
To: Michael Knappe <mknappe@juniper.net>
Content-Type: multipart/alternative; boundary="001636988b1747dfe5048342380f"
Cc: "codec@ietf.org" <codec@ietf.org>
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:58:34 -0000
Perhaps we are using "scope" for two different things? For me, "out of scope" means outside the working group charter. "in-band fax carriage" is in scope from a charter perspective, though I agree it is a non-requirement for the codec. Automated switchover is clearly outside the charter, so it is out of scope (in my definition). The reason this might matter: Things that are "out of scope" of the charter shouldn't be discussed on the list at all. Debates about non-requirements and requirements of course should be on the list. Stephen Botzko On Fri, Apr 2, 2010 at 10:48 AM, Michael Knappe <mknappe@juniper.net> wrote: > Agreed. In-band fax carriage should not be in the scope of the codec, and > the automated switchover to mechanisms like T.38 should also be outside the > scope of our work. > > Mike > > > On 4/2/10 7:33 AM, "Marc Petit-Huguenin" <petithug@acm.org> wrote: > > > 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 > >> > > > > _______________________________________________ > codec mailing list > codec@ietf.org > https://www.ietf.org/mailman/listinfo/codec >
- [codec] #5: Mention DTMF in requirements codec issue tracker
- Re: [codec] #5: Mention DTMF in requirements codec issue tracker
- Re: [codec] #5: Mention DTMF in requirements Christian Hoene
- Re: [codec] #5: Mention DTMF in requirements stephen botzko
- Re: [codec] #5: Mention DTMF in requirements Michael Knappe
- Re: [codec] #5: Mention DTMF in requirements, Tes… Christian Hoene
- Re: [codec] #5: Mention DTMF in requirements Marc Petit-Huguenin
- Re: [codec] #5: Mention DTMF in requirements stephen botzko
- Re: [codec] #5: Mention DTMF in requirements Marc Petit-Huguenin
- Re: [codec] #5: Mention DTMF in requirements, Tes… Wyss, Felix
- Re: [codec] #5: Mention DTMF in requirements, Tes… Steve Underwood
- Re: [codec] #5: Mention DTMF in requirements Steve Underwood
- Re: [codec] #5: Mention DTMF in requirements James Rafferty
- Re: [codec] #5: Mention DTMF in requirements stephen botzko
- Re: [codec] #5: Mention DTMF in requirements Peter Saint-Andre
- Re: [codec] #5: Mention DTMF in requirements James Rafferty
- Re: [codec] #5: Mention DTMF in requirements stephen botzko
- Re: [codec] #5: Mention DTMF in requirements Brian West
- Re: [codec] #5: Mention DTMF in requirements Brian West
- Re: [codec] #5: Mention DTMF in requirements Brian West
- Re: [codec] #5: Mention DTMF in requirements Brian West
- Re: [codec] #5: Mention DTMF in requirements Michael Knappe
- Re: [codec] #5: Mention in requirements, FAX? Christian Hoene
- Re: [codec] #5: Mention in requirements, FAX? James Rafferty
- Re: [codec] #5: Mention DTMF in requirements Christian Hoene
- Re: [codec] #5: Mention in requirements, FAX? Marc Petit-Huguenin
- Re: [codec] #5: Mention in requirements, FAX? Michael Knappe
- Re: [codec] #5: Mention DTMF in requirements stephen botzko
- Re: [codec] #5: Mention in requirements, FAX? stephen botzko
- Re: [codec] #5: Mention in requirements, FAX? Michael Knappe
- Re: [codec] #5: Mention DTMF in requirements Christian Hoene
- Re: [codec] #5: Mention DTMF in requirements stephen botzko
- Re: [codec] #5: Mention DTMF in requirements James Rafferty
- Re: [codec] #5: Mention DTMF in requirements Raymond (Juin-Hwey) Chen
- Re: [codec] #5: Mention DTMF in requirements Roman Shpount
- Re: [codec] #5: Mention DTMF in requirements Marc Petit-Huguenin
- Re: [codec] #5: Mention DTMF in requirements Wyss, Felix
- Re: [codec] #5: Mention DTMF in requirements stephen botzko
- Re: [codec] #5: Mention DTMF in requirements Roman Shpount
- Re: [codec] #5: Mention DTMF in requirements Roman Shpount
- Re: [codec] #5: Mention DTMF in requirements stephen botzko
- Re: [codec] #5: Mention DTMF in requirements Marc Petit-Huguenin
- Re: [codec] #5: Mention DTMF in requirements Raymond (Juin-Hwey) Chen
- Re: [codec] #5: Mention DTMF in requirements Brian West
- Re: [codec] #5: Mention DTMF in requirements Raymond (Juin-Hwey) Chen
- Re: [codec] #5: Mention DTMF in requirements Raymond (Juin-Hwey) Chen
- Re: [codec] #5: Mention DTMF in requirements Raymond (Juin-Hwey) Chen
- Re: [codec] #5: Mention DTMF in requirements Raymond (Juin-Hwey) Chen
- Re: [codec] #5: Mention DTMF in requirements Roman Shpount
- Re: [codec] #5: Mention DTMF in requirements Benjamin M. Schwartz
- Re: [codec] #5: Mention DTMF in requirements Roman Shpount
- Re: [codec] #5: Mention DTMF in requirements Peter Saint-Andre
- Re: [codec] #5: Mention DTMF in requirements codec issue tracker
- Re: [codec] #5: Mention DTMF in requirements stephen botzko
- Re: [codec] #5: Mention DTMF in requirements Raymond (Juin-Hwey) Chen
- Re: [codec] #5: Mention DTMF in requirements Kevin P. Fleming
- Re: [codec] #5: Mention DTMF in requirements stephen botzko
- Re: [codec] #5: Mention DTMF in requirements Koen Vos
- Re: [codec] #5: Mention DTMF in requirements stephen botzko
- Re: [codec] #5: Mention DTMF in requirements Wyss, Felix
- Re: [codec] #5: Mention DTMF in requirements stephen botzko
- Re: [codec] #5: Mention DTMF in requirements Michael Knappe
- Re: [codec] #5: Mention DTMF in requirements codec issue tracker