> From: Brett Tate <br...@broadsoft.com> > Draft-sparks-sipcore-refer-explicit-subscription intends to deprecate the > use of 202 for a REFER response (i.e. updating RFC 3515).
Specifically, 202 is deprecated in favor of 200. > If you think (or know) it will cause interoperability issues, please > express your concerns and/or update code as needed. I see in section 3.8 of draft-sparks-sipcore-refer-explicit-subscription-02: The 'Refer-Events-At' header field is only meaningful in a 200 response to a REFER request. If it appears in the header of any other SIP message, its meaning is undefined and it MUST be ignored. It seems to me that this is dangerously strict, and should say "is only meaningful in a *2xx* response to a REFER request". Dale _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
