Re: [Sipping] New I-D - Private Header Extension to SIP for Support of Mobility Operations

["Anton Tveretin" <fas_vm at surguttel.ru>]

What's about call linkage? I.e. how to check that the new dialog belongs to
the same call? I think it can be done in two ways:
1. to reuse dialog-id;
2. to indicate the previous dialog-id in the Replaces: header.
This should be clearly stated. As a consequence for (case 1), if the route
does not change, there will be no BYE. If B2BUAs change dialog-id, case 1
will not work. (Case 2 might sometimes).
I also think that such operation is not required for the Simple SIP and this
should be clearly stated.
If this header is purely informative (to my mind it is), why a Require:
option tag?
Best regards, Anton.

_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sip at ietf.org for new developments of core SIP