RE: [Sip] Comments on draft-rosenberg-sip-reg-00

["Dean Willis" <dean.willis@softarmor.com>]

Mark said:
> Secondly, I think in case an administrator wants a device to 
> re-authenticate, the registration of the corresponding 
> contact should not move to the terminated state. Instead, 
> another event (for example
> "re-authenticate") similar to the "refresh" event should be 
> introduced. When this event occurs, the device is notified 
> and the duration for which the contact remains registered is 
> reduced and if the device fails to re-register, the 
> registration is moved to the terminated state e.g. via the 
> "expired" event.

As I understand it, we want a UA to still work "properly" for a while
after it has been asked to reauthenticate.

If the proxy actually terminates the registration, one might assume it
deletes the associated contact from its storage. An incoming request
(say, INVITE) that arrives at the proxy between this deletion and the
reinsertion of the contact following a new registration from the UA
would then be handled as if the UA was not registered (as in "turned
off").

So, I believe Mark's concerns here are valid and we do need another
state in the FSM.

--
Dean


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