Skip to main content

Mechanism to Indicate Support of Features and Capabilities in the Session Initiation Protocol (SIP)
RFC 6809

Revision differences

Document history

Date By Action
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'This specification defines a new SIP header field, Feature-Caps. The Feature-Caps header field conveys feature-capability indicators …
Received changes through RFC Editor sync (changed abstract to 'This specification defines a new SIP header field, Feature-Caps. The Feature-Caps header field conveys feature-capability indicators that are used to indicate support of features and capabilities for SIP entities that are not represented by the Uniform Resource Identifier (URI) of the Contact header field.

SIP entities that are represented by the URI of the SIP Contact header field can convey media feature tags in the Contact header field to indicate support of features and capabilities.

This specification also defines feature-capability indicators and creates a new IANA registry, "Proxy-Feature Feature-Capability Indicator Trees", for registering feature-capability indicators. [STANDARDS-TRACK]')
2015-10-14
(System) Notify list changed from sipcore-chairs@ietf.org, draft-ietf-sipcore-proxy-feature@ietf.org to (None)
2013-02-27
(System) IANA registries were updated to include RFC6809
2012-11-27
(System) RFC published