database logo graphic

RFC 5688

"A Session Initiation Protocol (SIP) Media Feature Tag for MIME Application Subtypes", January 2010

Canonical URL:
http://www.rfc-editor.org/rfc/rfc5688.txt
This document is also available in this non-normative format: PDF.
Status:
PROPOSED STANDARD
Author:
J. Rosenberg
Stream:
IETF
Source:
NON WORKING GROUP

Cite this RFC: TXT  |  XML

Other actions: Find Errata (if any)  |  Submit Errata  |  Find IPR Disclosures from the IETF


Abstract

The caller preferences specification for the Session Initiation Protocol (SIP) allows a caller to express preferences that the call be routed to a User Agent (UA) with particular capabilities. Similarly, a specification exists to allow a UA to indicate its capabilities in a registration. Amongst those capabilities are the type of media streams the agent supports, described as top-level MIME types. The 'application' MIME type is used to describe a broad range of stream types, and it provides insufficient granularity as a capability. This specification allows a UA to indicate which application subtypes the agent supports. [STANDARDS-TRACK]


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Go to the RFC Editor Homepage.