RFC3261: SIP:8.2.4应用扩展

8.2.4 Applying Extensions
8.2.4应用扩展

   A UAS that wishes to apply some extension when generating the response MUST NOT do so unless support for that extension is indicated in the Supported header field in the request.  If the desired extension is not supported, the server SHOULD rely only on baseline SIP and any other extensions supported by the client.  In rare circumstances, where the server cannot process the request without the extension, the server MAY send a 421 (Extension Required) response.  This response indicates that the proper response cannot be generated without support of a specific extension.  The needed extension(s) MUST be included in a Require header field in the response.  This behavior is NOT RECOMMENDED, as it will generally break interoperability.

希望在生成响应时应用某些扩展的UAS不得这样做，除非在请求的“支持的报头”字段中指示支持该扩展。如果不支持所需的扩展，则服务器应仅依赖于基线SIP和客户端支持的任何其他扩展。在极少数情况下，如果服务器无法在没有扩展的情况下处理请求，则服务器可能会发送421（需要扩展）响应。此响应表明，如果没有特定扩展的支持，就无法生成正确的响应。所需的扩展名必须包含在响应的Require报头字段中。不建议使用此行为，因为它通常会破坏互操作性。

   Any extensions applied to a non-421 response MUST be listed in a Require header field included in the response.  Of course, the server MUST NOT apply extensions not listed in the Supported header field in the request.  As a result of this, the Require header field in a response will only ever contain option tags defined in standards-track RFCs.

应用于非421响应的任何扩展都必须列在响应中包含的Require报头字段中。当然，服务器不得应用请求中“支持的报头”字段中未列出的扩展。因此，响应中的Require报头字段将只包含在标准跟踪RFC中定义的选项标记。