In section 8.1.1.8 of draft RFC2543bis-05: it says
The option-tags listed MUST only refer to extensions defined in
standards track RFCs. This is to prevent servers from insisting that
clients implement non-standard, vendor defined features in order to
receive service. Extensions defined by experimental and informational
RFCs are explicitly excluded from usage with the Supported header in
a request, since they too are often used to document vendor defined
extensions.
The above paragraph excludes the use of header Supported (section 22.35) for
"standards track RFCs". From the text "prevent servers from insisting" I assume the
exclusion should also apply to headers: Require (section 22.30), and Proxy-Require
(section 22.28).
That being the case, how do we communicate support for "experimental and
informational" extensions?
Thanks Mike Purcell
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
