> No, it is not valid behavior. The Allow header should contain only
> methods that are "allowed" and supported by the UA. It is particularly
> problematic when you consider that RFC 5057 indicates that a 405
> response destroys the INVITE usage.
As the following RFC 5057 snippet indicates, only the transaction would be
affected since UPDATE is not integral to the usage.
(3) 405 Method Not Allowed:
501 Not Implemented:
Either of these responses would be aberrant in our example
scenario since support for the NOTIFY method is required by the
usage. In this case, the UA knows the condition is unrecoverable
and should stop sending NOTIFYs on the usage. Any refresh
subscriptions should be rejected. In general, these errors will
affect at most the usage. If the request was not integral to the
usage (it used an unknown method, or was an INFO inside an INVITE
usage, for example), only the transaction will be affected.
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
