RE: [Sip] Subscribe/Notify and Refer/Notify

[Adam Roach <adam@dynamicsoft.com>]

> However, to start with, can we have the doubts (in my previous email)
> cleared by the 
> author in this list ?

Sorry; I thought that, since you sent the same note to me privately,
you wanted a private response (which I provided). Comments inline.

> In this case, subscription and dialog are created before 
> getting 2xx for the
> intial SUBSCRIBE.
> However, if Subscriber doesn't get any final response and the 
> transaction
> timer for SUBSCRIBE
> transaction times out, what should be the action on the part 
> of subscriber :
> a) Remove the subscription
> b) Keep the subscription and remove the SUBSCRIBE transaction 
> gracefully.

b. 

Ambiguity noted; this will be clarified in the next version of the
document.

> ii) As per the Refer/Notify draft, the subscription expiry 
> time, before the
> Subscriber gets NOTIFY
>    depends on "Refer-To" header.
> 
>   E.g., in the draft, this line is mentioned :
>     Subscription-State: active;expires=(depends on Refer-To URI)
>    a) What exactly is meant by this ? 

I'll let Robert address this one. (Is this an ambiguity in
the REFER draft, or did Amit miss something?)

>    b) If no NOTIFY is received before the REFER (Refer/2xx) 
> transaction
> times  out, does that mean that subscription/dialog
>    is automatically removed ? OR is subscriber supposed to 
> wait for the
> NOTIFY till some "Configured" time ?

If the REFER times out, assume the subscription did not succeed.
Note that the dialog may or may not disappear, depending on whether
the REFER was sent on an existing dialog; see the dialog handling
mentioned in RFC 3265.

In general, RFCs don't cover all possible failure cases; it's assumed
that implementors will think through the ramifications of the
decisions they make, and try to make things behave in a sensible
fashion. This seems to be one of those cases.

/a
_______________________________________________
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