Dean,
Regarding
We also have a related operation:
4) Request redirection, which informs an upstream node about a new
identity to target instead of the original.
Redirection does not always imply a new identity, it could be an
alternative Contact for the same identity. The thing is that we cannot
easily distinguish between these, since both use the same response code
(302). So it can be either rerouting or retargeting. For the problem at
hand this makes no difference though, in any case the request URI is
replaced.
BTW what happened to the 'opaque' parameter solution that was part of a
GRUU draft some versions ago? A special URI parameter that survives
rerouting/retargeting would avoid introducing yet another identity
header, and also detection-of-support issues.
Regards,
Jeroen
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
