datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

MSML Package for the Media Control Channel Framework
draft-saleem-mediactrl-msml-package-03

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2014-01-02
Intended RFC status: Unknown
Other versions: plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

Network Working Group                                         A. Saleem
Internet Draft                                                  S. Dunn
Intended status: Informational                                  Radisys
Expires: July 2014                                      January 2, 2014

           MSML Package for the Media Control Channel Framework
                draft-saleem-mediactrl-msml-package-03.txt

Abstract

   The Media Server Markup Language [RFC5707] is used to control and
   invoke many different types of services on IP media servers. MSML can
   be used, for example, to control media server conferencing features
   such as video layout and audio mixing, create sidebar conferences or
   personal mixes, and set the properties of media streams.  As well,
   clients can use MSML to define media processing dialogs, which may be
   used as parts of application interactions with users or conferences.
   This document describes the use of MSML [RFC5707] language used
   within the context of Media Control Channel Framework [RFC6230]. The
   use of MSML [RFC5707] is described here as a standalone package for
   use within and compliant with the Media Control Channel Framework
   [RFC6230].

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF). Note that other groups may also distribute working
   documents as Internet-Drafts. The list of current Internet-Drafts is
   at http://datatracker.ietf.org/drafts/current.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time. It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 1, 2014.

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors. All rights reserved.

<Saleem, et al.>       Expires July 1, 2014                 [Page 1]
Internet-Draft  MSML Package for Media Control Channel        January 2014

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document. Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document. Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1. Introduction...................................................2
   2. Control Package Definition.....................................3
      2.1. Control Package Name......................................3
      2.2. Framework Message Usage...................................3
      2.3. Common XML Support........................................4
      2.4. CONTROL Message Body......................................4
      2.5. REPORT Message Body.......................................5
      2.6. Audit.....................................................5
      2.7. Examples..................................................6
         2.7.1. Audio Conference with Active Speaker Notification....6
   3. Element Definitions............................................7
   4. Formal Syntax..................................................7
   5. Security Considerations........................................8
   6. IANA Considerations............................................8
      6.1. Control Package Registration..............................8
      6.2. URN Sub-Namespace Registration............................8
      6.3. XML Schema Registration...................................8
   7. References.....................................................8
      7.1. Normative References......................................8
      7.2. Informative References....................................9
   8. Acknowledgments................................................9

1. Introduction

   The architectural framework for media server control is described in
   [RFC5567] and forms the basis for Media Control Channel Framework
   [RFC6230]. In this framework, SIP is used by application servers to
   both terminate media streams on media servers and to create and
   manage media server control channels between themselves and media
   servers.

   The SIP based control channel framework is described in [RFC6230]. It
   describes the establishment (via SDP negotiation), use, and
   termination of a reliable transport (TCP) connection between

[include full document text]