Subject: [Sip] (no subject)

From: Purcell Michael-QA3001 <[email-masked]>
Date: Wed, 9 Jan 2002 15:29:11 -0700

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 mailing list  http://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [email-masked] for questions on current sip
Use [email-masked] for new developments on the application of sip