%% You should probably cite rfc6787 instead of this I-D.
@techreport{ietf-speechsc-mrcpv2-28,
    number =    {draft-ietf-speechsc-mrcpv2-28},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-speechsc-mrcpv2/28/},
    author =    {Daniel C. Burnett and Saravanan Shanmugham},
    title =     {{Media Resource Control Protocol Version 2 (MRCPv2)}},
    pagetotal = 224,
    year =      2012,
    month =     aug,
    day =       28,
    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. {[}STANDARDS-TRACK{]}},
}