RFC3261: SIP:8.1.1.9支持和请求

8.1.1.9 Supported and Require
8.1.1.9支持和请求

   If the UAC supports extensions to SIP that can be applied by the server to the response, the UAC SHOULD include a Supported header field in the request listing the option tags (Section 19.2) for those extensions.

​如果UAC支持服务器可应用于响应的SIP扩展，则UAC应在请求中包括一个支持的报头字段，列出这些扩展的选项标签（第19.2节）。

   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 field in a request, since they too are often used to document vendor-defined extensions.

列出的选项标记必须仅引用在标准跟踪RFC中定义的扩展。这是为了防止服务器为了接收服务而坚持要求客户端实现非标准的、供应商定义的功能。实验性和信息性RFC定义的扩展被明确排除在请求中支持的报头字段之外，因为它们也经常用于记录供应商定义的扩展。

   If the UAC wishes to insist that a UAS understand an extension that the UAC will apply to the request in order to process the request, it MUST insert a Require header field into the request listing the option tag for that extension.  If the UAC wishes to apply an extension to the request and insist that any proxies that are traversed understand that extension, it MUST insert a Proxy-Require header field into the request listing the option tag for that extension.

如果UAC希望坚持要求UAS理解UAC将应用于请求的扩展以便处理请求，则必须在请求中插入Require报头字段，列出该扩展的选项标记。如果UAC希望对请求应用扩展，并坚持要求所遍历的任何代理都了解该扩展，则必须在请求中插入一个Proxy Require头字段，列出该扩展的选项标记。

   As with the Supported header field, the option tags in the Require and Proxy-Require header fields MUST only refer to extensions defined in standards-track RFCs.

与支持的报头字段一样，Require和Proxy Require标头字段中的选项标记必须仅引用标准跟踪RFC中定义的扩展。