Media Server Control Language and Protocol Thoughts

Document Type Expired Internet-Draft (individual)
Author Eric Burger 
Last updated 2006-06-06 (latest revision 2005-07-11)
Stream (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


IP mutli-function Media Server control is a problem that has slowly bubbled up in importance over the past four years. A driver in the IETF is the requirements generated by the XCON framework. Many approaches have been proposed. Some of these proposals are device- controlled-oriented, such as H.248. Others are server-oriented, using SIP and application-oriented markup. Before rushing headlong into a framework for a solution, it is time to step back and try to understand just what the scope of the problem is. Once consensus is reached, we can then move forward with a framework for a solution. This document describes a number of existing approaches and proposals to solve the Application Server - Media Server protocol problem, their characteristics and benefits and drawbacks.


Eric Burger (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)