Tonny,
I believe the non-subscribe dialog wording in 3265 was included to
accommodate REFER. It also seems that in retrospect people wish that
exception had not been made. So planning to create a non-subscribe
subscription for some other purpose would most likely be a mistake.
A key requirement is that both parties need to agree that the
subscription is being created and how the dialog is established. (There
must be a dialog.)
IMO the expiration time for the implicit subscription is one of the
messy parts of the implicit subscription. I don't know of good solutions
for it.
Paul
Tonny Kung wrote:
> Hi all,
>
> I have some questions regarding the non-SUBSCRIBE mechanism that's
> allowed in RFC3265 to create a subscription. I hope someone could clarify
> what is correct/allowed by the RFC.
>
> 1) Considering it is allowed to create an implicit subscription with
> REFER, then I assume an Event package can define any method to create a
> subscription?
>
> 2) Regarding the duration of the subscription. Is it ok to tie the
> duration to other application state of the dialog?
> For example, if an implicit subscription is created with an INVITE
> dialog, is it allowed to terminate the subscription when the INVITE dialog
> is released? Or do we have to received NOTIFY with
> Subscription-State=terminated?
>
>
> Thanks for your time.
>
> Best regards,
> Tonny
>
> ------------------------------------------------------------------------
> Yahoo! 網上安全攻略，教你如何防範黑客! *了解更多*
> <http://hk.promo.yahoo.com/security/index.html>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Sip mailing list https://www.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
_______________________________________________
Sip mailing list https://www.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
