RE: [Sip] INFO

"Mary Barnes" <mary.barnes@nortel.com> Thu, 27 September 2007 15:22 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 1IavCM-0004Z8-1T; Thu, 27 Sep 2007 11:22:42 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1IavCL-0004Y1-8k for sip-confirm+ok@megatron.ietf.org; Thu, 27 Sep 2007 11:22:41 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IavCK-0004Xl-SQ for sip@ietf.org; Thu, 27 Sep 2007 11:22:40 -0400
Received: from zcars04f.nortel.com ([47.129.242.57]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IavCK-0004m8-EQ for sip@ietf.org; Thu, 27 Sep 2007 11:22:40 -0400
Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com [47.103.123.72]) by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id l8RFMaH15216; Thu, 27 Sep 2007 15:22:37 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sip] INFO
Date: Thu, 27 Sep 2007 10:22:32 -0500
Message-ID: <E3F9D87C63E2774390FE67C924EC99BB16E79B0D@zrc2hxm1.corp.nortel.com>
In-Reply-To: <200709271439.l8REd4LE030665@dragon.ariadne.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] INFO
Thread-Index: AcgBFSkGtuyinwebSd+74aovhDsCwAAAgT3Q
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>
From: Mary Barnes <mary.barnes@nortel.com>
To: Dale.Worley@comcast.net, sip@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc:
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

And, here's another very old one:

http://quimby.gnus.org/internet-drafts/draft-choudhuri-sip-info-digit-00
.txt

Abstract:
   This document describes the mechanism how SIP INFO method can be used
   by applications that require mid session signaling for transport and 
   collection of DTMF digits.


Regards,
Mary. 

-----Original Message-----
From: Dale.Worley@comcast.net [mailto:Dale.Worley@comcast.net] 
Sent: Thursday, September 27, 2007 9:39 AM
To: sip@ietf.org
Subject: Re: [Sip] INFO

   From: Adam Roach <adam@nostrum.com>

   On 9/27/07 8:40 AM, Christer Holmberg wrote:
   > I actually DO think there was a DTMF-using-INFO draft at some point
- a
   > long time ago.

   Really?

ORLY?

 
http://www.google.com/search?q=site%3Atools.ietf.org+%22application%2Fdt
mf%22

   ...and, lest there be any confusion about how far back that archive
goes:

       http://tools.ietf.org/html/draft-ietf-mmusic-sip-01

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:

    Abstract

    This document proposes an extension to the Session Initiation
    Protocol.  This extension adds the INFO method to the SIP protocol.
    The intent of the INFO method is to allow for the carrying of
session
    related control information that is generated during a session.
    Examples of such session control information are ISUP/ISDN signaling
    messages and DTMF digits used to control telephony services.

Dale


_______________________________________________
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


_______________________________________________
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