Subject: [sipcore] draft-ietf-sipcore-rfc3265bis-03: comments concerning RFC 5057

From: Brett Tate <[email-masked]>
Date: Wed, 14 Sep 2011 05:17:33 -0700

Concerning the following draft-ietf-sipcore-rfc3265bis-03 section 4.1.2.2 snippet indicating subscriber "MUST consider the subscription terminated", the draft should potentially better indicate that the MUST does not preempt the RFC 5057 notes (such as for 482 and 483) which indicate situations where the dialog would not be terminated.

Section 4.1.2.2: "If a SUBSCRIBE request to refresh a subscription receives a 404, 405, 410, 416, 480-485, 489, 501, or 604 response, the subscriber MUST consider the subscription terminated.  (See [RFC5057] for further details and notes about the effect of error codes on dialogs and usages within dialog, such as subscriptions)."

Do the RFC 5057 notes for 482 edge condition still apply?  It indicates an RFC 3263 advancing situation which might trigger a 482 response and allow the subscription to remain.  If the RFC 5057 notes for 482 edge condition still apply, is it adequately indicated within the above snippet?

Thanks,
Brett