Re: [Sip] INFO

Adam Roach <adam@nostrum.com> Thu, 27 September 2007 14:59 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IauqH-0006xe-Fe; Thu, 27 Sep 2007 10:59:53 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1IauqG-0006vG-8C for sip-confirm+ok@megatron.ietf.org; Thu, 27 Sep 2007 10:59:52 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IauqF-0006v8-S4 for sip@ietf.org; Thu, 27 Sep 2007 10:59:51 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IauqF-0003xq-EZ for sip@ietf.org; Thu, 27 Sep 2007 10:59:51 -0400
Received: from orthrus.local (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.1/8.14.1) with ESMTP id l8RExoBI079128 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Sep 2007 09:59:50 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <46FBC56B.6000505@nostrum.com>
Date: Thu, 27 Sep 2007 09:59:55 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
MIME-Version: 1.0
To: Dale.Worley@comcast.net
Subject: Re: [Sip] INFO
References: <6FC4416DDE56C44DA0AEE67BC7CA437116A57D59@zrc2hxm2.corp.nortel.com><C3184CEC.B881%eburger@bea.com><6FC4416DDE56C44DA0AEE67BC7CA437116DFF008@zrc2hxm2.corp.nortel.com><46F7D719.2070004@nostrum.com><0a5401c8005c$a80fad10$800101df@acmepacket.com><46FAA68A.1090408@nostrum.com><0af301c8007c$94d37590$800101df@acmepacket.com><46FAC69C.4070402@nostrum.com><6FC4416DDE56C44DA0AEE67BC7CA437116FF8169@zrc2hxm2.corp.nortel.com><46FAE230.1070807@nostrum.com><6FC4416DDE56C44DA0AEE67BC7CA437116FF8412@zrc2hxm2.corp.nortel.com> <46FBAD3D.3090109@nostrum.com> <CA9998CD4A020D418654FCDEF4E707DF0237D9B1@esealmw113.eemea.ericsson.se> <46FBBA78.7070903@nostrum.com> <200709271439.l8REd4LE030665@dragon.ariadne.com>
In-Reply-To: <200709271439.l8REd4LE030665@dragon.ariadne.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
X-Virus-Scanned: ClamAV 0.91.2/4411/Wed Sep 26 16:43:35 2007 on shaman.nostrum.com
X-Virus-Status: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: sip@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

On 9/27/07 9:39 AM, Dale.Worley@comcast.net wrote:
> I'm not sure what that search does, but it doesn't turn up the
> document you're looking for, viz.:
> http://tools.ietf.org/html/draft-ietf-mmusic-sip-info-method-00, which
> proposed a new SIP method "INFO" to carry DTMF digits and such
> information:
>   

It gives DTMF as an _example_ of the kind of information that might be 
carried by INFO. It doesn't give even the remotest amount of technical 
detail about how one might do so.

At the time, there was an ensuing debate about the appropriateness of 
using INFO in this way, in which we developed a consensus that INFO 
really isn't the right tool for the job.

Unfortunately, when the naive answer is also the wrong answer, it seems 
impossible to ever put a decision to bed -- which is why we now hear the 
slow "clack... clack... clack" of the whole working group going up the 
initial slope of the "DTMF in INFO argument" roller coaster for the 
hojillionth time. Hold on tightly; it's not a fun ride...

/a


_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip