RE: [Sipping] Request / Response (RPC-like) exchange in SIP?

<Markus.Isomaki@nokia.com> Mon, 18 September 2006 19:52 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GPP9z-0005h4-La; Mon, 18 Sep 2006 15:52:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GPP9y-0005gl-MD; Mon, 18 Sep 2006 15:52:06 -0400
Received: from mgw-ext12.nokia.com ([131.228.20.171]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GPP9x-00050J-5u; Mon, 18 Sep 2006 15:52:06 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145]) by mgw-ext12.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id k8IJpGoG008504; Mon, 18 Sep 2006 22:52:04 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 18 Sep 2006 22:51:55 +0300
Received: from esebe101.NOE.Nokia.com ([172.21.138.215]) by esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 18 Sep 2006 22:51:54 +0300
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: [Sipping] Request / Response (RPC-like) exchange in SIP?
Date: Mon, 18 Sep 2006 22:51:53 +0300
Message-ID: <C84E0A4ABA6DD74DA5221E0833A35DF3077F7B6D@esebe101.NOE.Nokia.com>
In-Reply-To: <200609181939.k8IJdFPh009774@dragon.ariadne.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sipping] Request / Response (RPC-like) exchange in SIP?
Thread-Index: AcbbWnnu6G8lTx2KQCmh9OgPkpDN+AAAEpgA
From: Markus.Isomaki@nokia.com
To: sipping-bounces@ietf.org, sipping@ietf.org
X-OriginalArrivalTime: 18 Sep 2006 19:51:54.0649 (UTC) FILETIME=[E45DB090:01C6DB5B]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Errors-To: sipping-bounces@ietf.org

Hi,

I agree that there are several use cases for this type of method. It
seems that there are actually very few solutions that would allow a
client to reach a server that is on a host that does not have a
permanent DNS entry and is behind a NAT. People are already using
MESSAGE and INFO for this, so why not specify something that is really
intended for the purpose.

Markus

>-----Original Message-----
>From: ext sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] 
>Sent: 18 September, 2006 22:39
>To: sipping@ietf.org
>Subject: Re: [Sipping] Request / Response (RPC-like) exchange in SIP?
>
>   From: steven.d.whitehead@verizon.com
>
>   So what do people think about an RPC-like request/response 
>mechanism for
>   SIP?
>
>Interestingly, we've just been discussing this on the MIG 
>mailing list.  My position is that there are occasional needs 
>for "RPC-like"
>requests, and that all of the existing SIP methods carry 
>implicit assumptions which are violated by RPC-like requests.  
>Hence, I am advocating the creation of a new method.
>
>Dale
>
>_______________________________________________
>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 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