Re: [Sipping] Request for Open discussion about SIP mobility

Stefano, 

> -----Original Message-----
> From: sipping-bounces@ietf.org 
> [mailto:sipping-bounces@ietf.org] On Behalf Of Stefano Salsano
> Sent: 13 May 2008 09:11
> To: Elwell, John
> Cc: Paul Kyzivat; Ashutosh Dutta; SIPPING LIST; Mary Barnes; 
> Saverio Niccolini
> Subject: Re: [Sipping] Request for Open discussion about SIP mobility
> 
> Elwell, John wrote:
> > [JRE] This is just another instance of the general problem of B2BUAs
> > (e.g. SBCs) providing functionality to compensate for 
> endpoints that do
> > not fully support fairly basic mechanisms in SIP, namely 
> re-INVITE in
> > this particular case. It is a fact that such middleboxes do 
> exist, and
> > we can argue about whether they exist for good reasons or 
> not. However,
> > does the IETF really want to specify such work-arounds for these
> > problems, rather than trying to address the fundamental problem?
> > 
> 
> Dear John,
> 
> it is not only a problem of specifying a work-around for "basic" 
> endpoints (though this may be a useful "side-achievement"...)
> 
> In my opinion there are some conceptual reasons why we should provide 
> the possibility to handle terminal mobility on the side of the Mobile 
> Device, rather then on the side of the correspondant node. 
> The user of 
> the Mobile Device has a strong interest in the reliability and 
> performance of this mobility, and may want to control it better than 
> relying on the CN capabilities.
> 
> And as I pointed out, there are some performance issues that 
> may require 
> an improvement with respect to the curent re-INVITE mechanisms.
[JRE] I am happy as long as we do this for the right reasons. If it is
purely as a work-around for non-compliant SIP devices, I have a problem.
But it there are other sound technical reasons, such as performance, I
don't have a problem.

John
_______________________________________________
Sipping mailing list  https://www.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