IETF Logo Mail Archive

Re: [Sipping] Re: [Sip] INAP and SIP INFO

Jonathan Rosenberg <jdrosen@dynamicsoft.com> Wed, 25 September 2002 06:51 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16965 for <sipping-archive@odin.ietf.org>; Wed, 25 Sep 2002 02:51:44 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g8P6rFM32598 for sipping-archive@odin.ietf.org; Wed, 25 Sep 2002 02:53:15 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8P6rEv32595 for <sipping-web-archive@optimus.ietf.org>; Wed, 25 Sep 2002 02:53:14 -0400
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16916 for <sipping-web-archive@ietf.org>; Wed, 25 Sep 2002 02:51:13 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8P6mFv32372; Wed, 25 Sep 2002 02:48:15 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8P6iNv32266 for <sipping@optimus.ietf.org>; Wed, 25 Sep 2002 02:44:23 -0400
Received: from mail3.dynamicsoft.com ([63.113.44.69]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16816 for <sipping@ietf.org>; Wed, 25 Sep 2002 02:42:21 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.47]) by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g8P6hCYH029313; Wed, 25 Sep 2002 02:43:12 -0400 (EDT)
Message-ID: <3D915AFE.7000402@dynamicsoft.com>
Date: Wed, 25 Sep 2002 02:43:10 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Vijay K. Gurbani" <vkg@lucent.com>
CC: Bobby Sardana <sardana@obsoft.com>, "F.S.Salloum" <ssal@intracom.gr>, sipping@ietf.org
Subject: Re: [Sipping] Re: [Sip] INAP and SIP INFO
References: <NGBBLHKPJKCDNEIOOKKOGEIACEAA.ssal@intracom.gr> <3D8ED007.D22638A2@obsoft.com> <3D8F22F6.7030608@lucent.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

As far as I know, the draft below does not talk about "encapsulating 
INAP within INFO". It talks about INFO as one way to send DTMF, 
something which the SIP community generally has determined is NOT a good 
idea.

SIP is not a tunneling protocol, and I see little value in encapsulating 
something like INAP, which is not a "peer" of SIP, as ISUP is.

-Jonathan R.

Vijay K. Gurbani wrote:
> Bobby Sardana wrote:
> 
>> Check out the following drafts:
>>
>> 1) SIP-IN Interworking Protocol Architecture and Procedures
>> (http://www.bell-labs.com/mailing-lists/ietf-sin/draft-gurbani-sin-00.txt) 
>>
> 
> 
> That's actually pretty old; the latest one is at
> http://www.ietf.org/internet-drafts/draft-gurbani-sin-02.txt
> 
> Regards,
> 
> - vijay

-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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

v2.23.0 | Report a Bug | By Email