RFC 5022 on Media Server Control Markup Language (MSCML) and Protocol

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

        
        RFC 5022

        Title:      Media Server Control Markup Language 
                    (MSCML) and Protocol 
        Author:     J. Van Dyke, E. Burger,
                    Ed., A. Spitzer
        Status:     Informational
        Date:       September 2007
        Mailbox:    jvandyke@cantata.com, 
                    eburger@standardstrack.com, 
                    woof@pingtel.com
        Pages:      81
        Characters: 184482
        Obsoletes:  RFC4722
        See-Also:   

        I-D Tag:    none

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

Media Server Control Markup Language (MSCML) is a markup language
used in conjunction with SIP to provide advanced conferencing and
interactive voice response (IVR) functions.  MSCML presents an
application-level control model, as opposed to device-level control
models.  One use of this protocol is for communications between a
conference focus and mixer in the IETF SIP Conferencing Framework.  This 
memo provides information for the Internet community.


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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

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

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



_______________________________________________

IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

[Index of Archives]     [IETF]     [IETF Discussion]     [Linux Kernel]

  Powered by Linux