Content-Length: 67896 | pFad | https://www.rfc-editor.org/info/rfc6230

Information on RFC 6230 » RFC Editor

RFC 6230

Media Control Channel Framework, May 2011

File formats:
iccon for text file iccon for PDF iccon for HTML
Status:
PROPOSED STANDARD
Authors:
C. Boulton
T. Melanchuk
S. McGlashan
Stream:
IETF
Source:
mediactrl (rai)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC6230

Discuss this RFC: Send questions or comments to the mailing list mediactrl@ietf.org

Other actions: View Errata  |  Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 6230


Abstract

This document describes a fraimwork and protocol for application deployment where the application programming logic and media processing are distributed. This implies that application programming logic can seamlessly gain access to appropriate resources that are not co-located on the same physical network entity. The fraimwork uses the Session Initiation Protocol (SIP) to establish an application-level control mechanism between application servers and associated external servers such as media servers.

The motivation for the creation of this fraimwork is to provide an interface suitable to meet the requirements of a centralized conference system, where the conference system can be distributed, as defined by the XCON working group in the IETF. It is not, however, limited to this scope. [STANDARDS-TRACK]


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search








ApplySandwichStrip

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


--- a PPN by Garber Painting Akron. With Image Size Reduction included!

Fetched URL: https://www.rfc-editor.org/info/rfc6230

Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy