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

Shida Schubert <shida@ntt-at.com> Tue, 19 September 2006 00:19 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GPTL3-0006n1-Au; Mon, 18 Sep 2006 20:19:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GPTL1-0006mt-MX; Mon, 18 Sep 2006 20:19:47 -0400
Received: from agnada.com ([69.36.182.244]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GPTL0-0000eu-Bb; Mon, 18 Sep 2006 20:19:47 -0400
Received: from [192.168.0.101] (S010600095b9792b5.vc.shawcable.net [24.85.243.115]) (authenticated) by agnada.com (8.11.6/8.11.6) with ESMTP id k8J0Jde03126; Mon, 18 Sep 2006 18:19:39 -0600
Message-ID: <450F379E.2080008@ntt-at.com>
Date: Mon, 18 Sep 2006 17:19:42 -0700
From: Shida Schubert <shida@ntt-at.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Markus.Isomaki@nokia.com
Subject: Re: [Sipping] Request / Response (RPC-like) exchange in SIP?
References: <C84E0A4ABA6DD74DA5221E0833A35DF3077F7B6D@esebe101.NOE.Nokia.com>
In-Reply-To: <C84E0A4ABA6DD74DA5221E0833A35DF3077F7B6D@esebe101.NOE.Nokia.com>
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: sipping-bounces@ietf.org, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: shida@ntt-at.com
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

Considering any widely adopted protocol ends up being a transport
protocol and SIP being no exception to this, it might be worth while
to evaluate something explicit for use described below.

Regards
Shida

Markus.Isomaki@nokia.com wrote:
> 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
>
>
>   


_______________________________________________
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