RFC 5707 on Media Server Markup Language (MSML)

rfc-editor@rfc-editor.org Thu, 04 February 2010 01:47 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id A17CD28C127 for <ietf-announce@core3.amsl.com>; Wed, 3 Feb 2010 17:47:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.053
X-Spam-Status: No, score=-2.053 tagged_above=-999 required=5 tests=[AWL=-0.065, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id 7lntY-8P1mqB for <ietf-announce@core3.amsl.com>; Wed, 3 Feb 2010 17:47:08 -0800 (PST)
Received: from rfc-editor.org (rfcpa []) by core3.amsl.com (Postfix) with ESMTP id CED2228C112 for <ietf-announce@ietf.org>; Wed, 3 Feb 2010 17:47:08 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id C939113000E; Wed, 3 Feb 2010 17:47:52 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5707 on Media Server Markup Language (MSML)
From: rfc-editor@rfc-editor.org
Message-Id: <20100204014752.C939113000E@rfc-editor.org>
Date: Wed, 3 Feb 2010 17:47:52 -0800 (PST)
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2010 01:47:09 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 5707

        Title:      Media Server Markup Language (MSML) 
        Author:     A. Saleem, Y. Xin,
                    G. Sharratt
        Status:     Informational
        Date:       February 2010
        Mailbox:    adnan.saleem@RadiSys.com, 
        Pages:      184
        Characters: 376984
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-saleem-msml-09.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5707.txt

The Media Server Markup Language (MSML) is used to control and invoke
many different types of services on IP media servers.  The MSML control
interface was initially driven by RadiSys with subsequent significant
contributions from Intel, Dialogic, and others in the
industry.  Clients can use it to define how multimedia sessions
interact on a media server and to apply services to individuals or
groups of users.  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.  Transformation of media
streams to and from users or conferences as well as interactive voice
response (IVR) dialogs are examples of such interactions, which are
specified using MSML.  MSML clients may also invoke dialogs with
individual users or with groups of conference participants using
VoiceXMLThis document is not an Internet Standards Track 
specification; it is published for informational purposes.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC