RFC 6809
Mechanism to Indicate Support of Features and Capabilities in the Session Initiation Protocol (SIP), November 2012
- File formats:
- Status:
- PROPOSED STANDARD
- Authors:
- C. Holmberg
I. Sedlacek
H. Kaplan - Stream:
- IETF
- Source:
- sipcore (rai)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC6809
Discuss this RFC: Send questions or comments to the mailing list sipcore@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 6809
Abstract
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]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.