Re: [sipcore] 4244bis: Describing redirections

 It's "mp" and "rc". The "other" you mention below is "rc". 

 You tag it with "mp" when you know for certain that 
the target user represented by the R-URI is different 
from one before. Otherwise you simply tag it with "rc".

 If the URI doesn't change when forwarded due to 
the Route header, you simply don't tag it because 
R-URI did not change. We used to have a tag called 
"np" (no-op) for that.

 Regards
  Shida

On Jul 8, 2011, at 4:07 AM, Worley, Dale R (Dale) wrote:

>> From: Hadriel Kaplan [HKaplan@acmepacket.com] 
>> 
>> That's why I proposed always adding the "rc" param when the req-uri is
>> changed, regardless of how it was changed (except for the case of
>> "mp"), so that the dotted-number pointer can always be there.
>> 
>> In other words, don't have "rc", "gr" and "hi" - just "rc" and "mp",
>> where "rc" now means 'req-uri changed'.  Because it doesn't actually
>> matter how the req-uri got changed. (it's not reliably useful info to
>> the UAS)
> 
> Essentially, that proposal is to have two cases, "mp" and other.  That
> does the job.  In any case, we need to have a way of tagging "other".
> I'm not really sure that we need to distinguish any cases.
> 
> I think that the way to "solve" this question is to examine the
> application logic -- what cases do we need to distinguish to ensure
> that the application logic can make the decisions that people want to
> make?
> 
> I've posted alternative application logic, but I suspect that version
> is shaky too.  Others needs to review it.
> 
> Dale
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore