Browse Prior Art Database

Media Resource Control Protocol Version 2 (MRCPv2) (RFC6787)

IP.com Disclosure Number: IPCOM000223244D
Original Publication Date: 2012-Nov-01
Included in the Prior Art Database: 2012-Nov-14

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

D. Burnett: AUTHOR [+2]

Abstract

MRCPv2 is designed to allow a client device to control media processing resources on the network. Some of these media processing resources include speech recognition engines, speech synthesis engines, speaker verification, and speaker identification engines. MRCPv2 enables the implementation of distributed Interactive Voice Response platforms using VoiceXML [W3C.REC-voicexml20-20040316] browsers or other client applications while maintaining separate back-end speech processing capabilities on specialized speech processing servers. MRCPv2 is based on the earlier Media Resource Control Protocol (MRCP) [RFC4463] developed jointly by Cisco Systems, Inc., Nuance Communications, and Speechworks, Inc. Although some of the method names are similar, the way in which these methods are communicated is different. There are also more resources and more methods for each resource. The first version of MRCP was essentially taken only as input to the development of this protocol. There is no expectation that an MRCPv2 client will work with an MRCPv1 server or vice versa. There is no migration plan or gateway definition between the two protocols.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 1% of the total text.

Internet Engineering Task Force (IETF)                        D. Burnett Request for Comments: 6787                                         Voxeo Category: Standards Track                                  S. Shanmugham ISSN: 2070-1721                                      Cisco Systems, Inc.                                                            November 2012

            Media Resource Control Protocol Version 2 (MRCPv2)

Abstract

   The Media Resource Control Protocol Version 2 (MRCPv2) allows client    hosts to control media service resources such as speech synthesizers,    recognizers, verifiers, and identifiers residing in servers on the    network.  MRCPv2 is not a "stand-alone" protocol -- it relies on    other protocols, such as the Session Initiation Protocol (SIP), to    coordinate MRCPv2 clients and servers and manage sessions between    them, and the Session Description Protocol (SDP) to describe,    discover, and exchange capabilities.  It also depends on SIP and SDP    to establish the media sessions and associated parameters between the    media source or sink and the media server.  Once this is done, the    MRCPv2 exchange operates over the control session established above,    allowing the client to control the media processing resources on the    speech resource server.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc6787.

Copyright Notice

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

   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

Burnett & Shanmugham         Standards Track                    [Page 1]
 RFC 6787                         MRCPv2                    November 2012

    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    th...