RFC 6809: Mechanism to Indicate Support of Features and Capabilities in the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC6809
- Published
- November 2012
- Authors
- C. Holmberg; I. Sedlacek; H. Kaplan
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7239Forwarded HTTP ExtensionCurrent
June 2014
- RFC 5658Addressing Record-Route Issues in the Session Initiation Protocol (SIP)Current
October 2009
- RFC 5625DNS Proxy Implementation GuidelinesCurrent
August 2009
- RFC 8041Use Cases and Operational Experience with Multipath TCPCurrent
January 2017
- RFC 8165Design Considerations for Metadata InsertionCurrent
May 2017
- RFC 8302Transparent Interconnection of Lots of Links (TRILL): ARP and Neighbor Discovery (ND) OptimizationCurrent
January 2018
- RFC 8828WebRTC IP Address Handling RequirementsCurrent
January 2021
- RFC 9209The Proxy-Status HTTP Response Header FieldCurrent
June 2022
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?