[Sipping] RE: [Sip] Sending SOAP over SIP
"Neil Deason" <ndeason@ubiquity.net> Tue, 14 May 2002 21:04 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06897 for <sipping-archive@odin.ietf.org>; Tue, 14 May 2002 17:04:25 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id RAA24530 for sipping-archive@odin.ietf.org; Tue, 14 May 2002 17:04:39 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA19091; Tue, 14 May 2002 04:55:50 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA19052 for <sipping@optimus.ietf.org>; Tue, 14 May 2002 04:55:41 -0400 (EDT)
Received: from gbnewp0915s1.eu.ubiquity.net (news.ubiquity.net [194.202.146.92]) by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA09830 for <sipping@ietf.org>; Tue, 14 May 2002 04:55:27 -0400 (EDT)
Received: from mailhost.eu.ubiquity.net by gbnewp0915s1.eu.ubiquity.net via smtpd (for odin.ietf.org [132.151.1.176]) with SMTP; 14 May 2002 08:56:02 UT
Received: from gbnewp1014m ([193.195.52.232]) by GBNEWP0758M.eu.ubiquity.net with Microsoft SMTPSVC(5.0.2195.4905); Tue, 14 May 2002 09:57:47 +0100
From: Neil Deason <ndeason@ubiquity.net>
To: Ignacio.Almar@nokia.com, "Sipping (E-mail)" <sipping@ietf.org>
Date: Tue, 14 May 2002 09:57:46 +0100
Message-ID: <BFEOLJKHNLJMCACGBPOOOENMDJAA.ndeason@ubiquity.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <05C8D36DA4EF684D8BD4E309B1CD5AF166DFC7@maebe001.NOE.Nokia.com>
X-OriginalArrivalTime: 14 May 2002 08:57:47.0139 (UTC) FILETIME=[6B0BED30:01C1FB25]
Content-Transfer-Encoding: 7bit
Subject: [Sipping] RE: [Sip] Sending SOAP over SIP
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit
[Moved to SIPPING list from SIP] > -----Original Message----- > From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of > Ignacio.Almar@nokia.com > Sent: 13 May 2002 17:24 > To: sip@ietf.org > Subject: [Sip] Sending SOAP over SIP > > Thanks in advance. > > To send SOAP over HTTP, the tag 'SOAPAction' is sent in > the HTTP headers when sending SOAP requests to identify the > intent of the request. This header can be used by the > Firewalls and Proxies to filter the SOAP Message. In HTTP > this field is defined as mandatory, so the client MUST > include this field in the HTTP header when sending a SOAP > message. SOAP can be sent over HTTP as a > ContentType=text/xml, and over SIP with the same content type. SOAPAction is a feature of the HTTP specific binding for the transport of SOAP. So it is not an inevitability that any binding for SIP should support it. Indeed the WSDL spec says: "For other SOAP protocol bindings, it [SOAPAction] MUST NOT be specified". Do you have a particular case in mind where you think it would be required in SIP? > In SIP, to allow the appropiate filtering by proxies > there should be defined a SOAPAction field as mandatory in > the client request. Do you think if there is something > defined regarding this ? Nothing is presently defined. You could be add it as an extension header of course. Note you will need to accept the IESG implications that the protocol you are then using is no longer "SIP". > Another option to let the proxies identify that a SOAP > message is inside the SIP message would be to define a > ContentType=text/soap+xml, but I think that this is not > defined currently in IANA. This is an option - although you are in the grey area of whether this is a 'proxy' as it is not treating payloads opaquely. BTW - http://www.ietf.org/internet-drafts/draft-baker-soap-media-reg-00.txt proposes the use of Content-Type "application/xml+soap". > Note that I am trying to avoid the use of a proprietary > format, but I am pointing a general format of sending SOAP > over SIP. And also, I am referring to individual sessionless > calls, including the SOAP code in a single SIP call, not > using a SIP call to establish a session (INVITE) and > afterwards send a message using HTTP. > Use sipping@ietf.org for new developments on the application of sip Hmmm sounds familiar. Long since expired, but archived in various places: http://www.cs.columbia.edu/~hgs/sip/drafts/draft-deason-sip-soap-00.txt Also implemented by certain well known large vendors, or so I am lead to believe. Does anyone want this revived? Using SIP as a transport for SOAP can lead to problems with large messages or lots of messages because of the potential for SIP to use UDP as an underlying transport protocol. This leads me to feel that a better alternative for the coexistence of SIP and SOAP is to use SIP to set up sessions of SOAP messages run over IMTP. http://www.ietf.org/internet-drafts/draft-deason-sipping-soap-sessions-0 0.txt Cheers, Neil. -- Neil Deason 303 Twin Dolphin Drive Ubiquity Software Corporation Suite 600 http://www.ubiquity.net Redwood City ndeason@ubiquity.net CA 94065 USA _______________________________________________ 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
- [Sipping] RE: [Sip] Sending SOAP over SIP Neil Deason