Media Server Markup Language (MSML)
draft-saleem-msml-09

quot;/> 
 <xs:element name="stream" substitutionGroup="stateParameter"> 
  <xs:complexType> 
   <xs:complexContent> 
    <xs:extension base="stateParameterType"> 
     <xs:all> 
      <xs:element name="clamp" minOccurs="0"> 
       <xs:complexType> 
        <xs:attribute name="dtmf" type="boolean.datatype"/> 
        <xs:attribute name="tones" type="boolean.datatype"/> 
       </xs:complexType> 
      </xs:element> 
      <xs:element name="gain" minOccurs="0"> 
       <xs:complexType> 
        <xs:attribute name="amt" use="optional"> 
         <xs:simpleType> 
          <xs:restriction base="xs:integer"> 
           <xs:minInclusive value="-96"/> 
           <xs:maxInclusive value="96"/> 
          </xs:restriction> 
         </xs:simpleType> 
        </xs:attribute> 
        <xs:attribute name="agc" type="boolean.datatype"/> 
        <xs:attribute name="tgtlvl" use="optional"> 
         <xs:simpleType> 
          <xs:restriction base="xs:nonPositiveInteger"> 
           <xs:minInclusive value="-40"/> 
           <xs:maxInclusive value="0"/> 
          </xs:restriction> 
         </xs:simpleType> 
        </xs:attribute> 
        <xs:attribute name="maxgain" default="10"> 
         <xs:simpleType> 
          <xs:restriction base="xs:nonNegativeInteger"> 
           <xs:minInclusive value="0"/> 
           <xs:maxInclusive value="40"/> 
          </xs:restriction> 
         </xs:simpleType> 
        </xs:attribute> 
 
 
Saleem, et al.         Expires January 29 2010               [Page 174] 


Internet-draft       Media Server Markup Language         July 28 2009 
                                 (MSML) 
 
 
       </xs:complexType> 
      </xs:element> 
      <xs:element name="visual" minOccurs="0"/> 
     </xs:all> 
     <xs:attribute name="joinwith" type="independentID.datatype"  
                   use="required"/> 
     <xs:attribute name="media" use="required"> 
      <xs:simpleType> 
       <xs:restriction base="xs:string"> 
        <xs:pattern value="audio"/> 
        <xs:pattern value="video"/> 
       </xs:restriction> 
      </xs:simpleType> 
     </xs:attribute> 
     <xs:attribute name="dir" use="required"> 
      <xs:simpleType> 
       <xs:restriction base="xs:string"> 
        <xs:pattern value="from"/> 
        <xs:pattern value="to"/> 
       </xs:restriction> 
      </xs:simpleType> 
     </xs:attribute> 
     <xs:attribute name="compressed" type="boolean.datatype"/> 
     <xs:attribute name="preferred" type="boolean.datatype"  
                   default="false"/> 
     <xs:attribute name="display" type="xs:string"/> 
     <xs:attribute name="override" type="boolean.datatype"  
                   default="false"/> 
    </xs:extension> 
   </xs:complexContent> 
  </xs:complexType> 
 </xs:element> 
</xs:schema> 
    
18.   Security Considerations 

   MSML being an XML based language, security considerations as defined 
   by RFC 3023 [i2] are applicable. 

   Media server interfaces driven using MSML are under the explicit 
   control of a SIP application server. SIP call legs are used to 
   deliver XML based MSML transactions to the media server. The security 
   and integrity of MSML transactions, whenever required, SHOULD use 
   sips: and TLS for encryption and authentication of the SIP control 
   channel used to carry MSML payloads. Further information related to 
   security, privacy, and integrity of MSML media types is described in 
   the IANA Considerations section. 

 
 
Saleem, et al.         Expires January 29 2010               [Page 175] 


Internet-draft       Media Server Markup Language         July 28 2009 
                                 (MSML) 
 
 
   Media streams, such as audio/video, MAY optionally be protected, 
   encrypted/decrypted and authenticated, utilizing Secure Real Time 
   Protocol (SRTP), where ever media stream security is required. Media 
   negotiation establishes the required level of security and is 
   initiated by the clients, which is outside the scope of the control 
   interface specified by MSML. 

19.   IANA Considerations 

19.1    IANA registrations for 'application' MIME Media Type 

   The following registrations are planned: 

   Type Name: "application" 

   Subtype names: 

         'application/vnd.radisys.msml+xml', 

         'application/vnd.radisys.moml+xml', 

         'application/vnd.radisys.msml-conf+xml', 

         'application/vnd.radisys.msml-dialog+xml', 

         'application/vnd.radisys.msml-dialog-base+xml', 

         'application/vnd.radisys.msml-dialog-group+xml', 

         'application/vnd.radisys.msml-dialog-speech+xml', 

         'application/vnd.radisys.msml-dialog-transform+xml', 

         'application/vnd.radisys.msml-dialog-fax-detect+xml', 

         'application/vnd.radisys.msml-dialog-fax-sendrecv+xml', 

         'application/vnd.radisys.msml-audit+xml', 

         'application/vnd.radisys.msml-audit-conf+xml', 

         'application/vnd.radisys.msml-audit-conn+xml', 

         'application/vnd.radisys.msml-audit-dialog+xml', 

         'application/vnd.radisys.msml-audit-stream+xml' 

   Required parameters: none 
 
 
Saleem, et al.         Expires January 29 2010               [Page 176] 


Internet-draft       Media Server Markup Language         July 28 2009 
                                 (MSML) 
 
 
   Optional parameters: charset 

         charset semantics as specified in RFC 3023 [i2] for 
         "application/xml" media type. 

   Encoding considerations: 

         As specified in RFC 3023 [i2]. 

   Security Considerations: 

         Media types included in this section are XML based, as such 
         security considerations as defined by RFC 3023 [i12] are 
         applicable. 

         These media types do not contain active or executable content 
         as the content itself merely provides control of the underlying 
         media streams. 

         Secure exchange of content associated with these media types 
         for purposes of authentication and privacy, whenever 
         applicable, shall require the establishment of a secure control 
         channel using sips: and TLS. 

         Privacy and integrity of media content associated with these 
         media types shall be considered when applications using these 
         media types is exchanging personal information such as personal 
         identification codes or conference access codes. Whenever such 
         content is deemed to require secure transport and 
         authentication a secure channel using sips: and TLS MUST be 
         used, as these media types themselves provide no such inherent 
         mechanisms for security. 

   Interoperability considerations: 

         As specified in RFC 3023 [i2] and as specified within this 
         document. 

   Published specification: RFC XXXX (this internet draft) 

   Intended applications for these media types: 

         Multimedia Conferencing, Interactive Voice Response systems 

   Additional information: 

         Magic number(s): None 

 
 
Saleem, et al.         Expires January 29 2010               [Page 177] 


Internet-draft       Media Server Markup Language         July 28 2009 
                                 (MSML) 
 
 
         File extension(s): None 

         Macintosh file type code(s): None 

   Person & email address to contact for further information: 

         Adnan Saleem: <mailto:adnan.saleem@radisys.com> 

   Intended usage: COMMON 

19.2    IANA registrations for 'text' MIME Media Type  

   The following registrations are planned: 

         'text/vnd.radisys.msml-basic-layout' 

   Required parameters: none 

   Optional parameters: charset 

         charset semantics as specified in RFC 3023 [i2] for "text/xml" 
         media type. 

   Encoding considerations: As specified in RFC 3023 [i2]. 

   Security Considerations: 

         Media types included in this section are XML based, as such 
         security considerations as defined by RFC 3023 [i12] are 
         applicable. 

         The media type defined in this section does not contain active 
         or executable content. The media type defines only a visual 
         layout scheme of a video conference. Establishment of active 
         connections associated with the video conference are outside 
         the scope of this media type. 

         Since this media type only defines a visual layout scheme, with 
         no reference or information about client connections or 
         participants within the conference, privacy and integrity 
         concerns are not applicable to this media type. 

   Interoperability considerations:  

         As specified in RFC 3023 [i2] and as specified within this 
         document. 

   Published specification: RFC XXXX (this internet draft) 
 
 
Saleem, et al.         Expires January 29 2010               [Page 178] 


Internet-draft       Media Server Markup Language         July 28 2009 
                                 (MSML) 
 
 
   Intended applications for these media types: 

         Multimedia Conferencing, Interactive Voice Response systems 

   Additional information: 

         Magic number(s): None 

         File extension(s): None 

         Macintosh file type code(s): None 

   Person & email address to contact for further information: 

         Adnan Saleem: <mailto:adnan.saleem@radisys.com> 

   Intended usage: COMMON 

    

19.3    URN Sub-Namespace Registration 

   The namespace URI for elements defined within this specification is 

   a URN [i10]. It uses the namespace identifier 'ietf' defined by [i11] 
   and extended by RFC 3688 [i12]. 

   The following registrations of URN Sub-Namespaces are planned: 

   XML namespace: urn:ietf:params:xml:ns:msml 

   XML: 

   BEGIN 

   <?xml version="1.0"?> 

   <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" 

   "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> 

   <html xmlns="http://www.w3.org/1999/xhtml"> 

     <head> 

         <meta http-equiv="content-type" 

               content="text/html;charset=iso-8859-1"/> 
 
 
Saleem, et al.         Expires January 29 2010               [Page 179] 


Internet-draft       Media Server Markup Language         July 28 2009 
                                 (MSML) 
 
 
         <title>Media Server Markup Language Namespace</title>  

     </head>  

     <body>  

        <h1>Namespace for Media Server Markup Language</h1>  

        <h2>urn:ietf:params:xml:ns:msml</h2> 

        <p>See MSML <a href="[[[URL of published RFC]]]">RFCXXXX</a></p> 

     </body>  

   </html> 

   END 

19.4    XML Schema Registration 

   This section registers an XML schema per the procedures in [i12]. 

   URI: urn:ietf:params:xml:schema:msml 

   Registrant Contact: 

         Adnan Saleem (adnan.saleem@radisys.com) and authors listed 
         within this document. 

   The XML for this schema can be found as the sole content of Section 
   18. 

20.   Normative References 

   [n1] J. Rosenberg, H. Schulzrinne, G. Camarillo, A. Johnston, J. 
   Peterson, R. Sparks, M. Handley, and E. Schooler, "SIP: Session 
   Initiation Protocol", RFC3261, Internet Engineering Task Force, June 
   2002. 

   [n2] Bray, T., Paoli, J., Sperberg-McQueen, C., and E. Maler, 
   "Extensible Markup Language (XML) 1.0 (Second Edition)," W3C 
   FirstEdition REC-xml-20001006, October 2000. 

   [n3] World Wide Web Consortium, "Speech Recognition Grammar 
   Specification Version 1.0" (SRGS), W3C Candidate Recommendation, 
   March 16, 2004 

 
 
Saleem, et al.         Expires January 29 2010               [Page 180] 


Internet-draft       Media Server Markup Language         July 28 2009 
                                 (MSML) 
 
 
   [n4] World Wide Web Consortium, "Natural Language Semantics Markup 
   Language (NLSML) for the Speech Interface Framework", W3C Working 
   Draft 20, November 2000.  

   [n5] World Wide Web Consortium, "Voice Extensible Markup Language 
   (VoiceXML) Version 2.0, W3C Candidate Recommendation, March 16, 2004 

   [n6] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 
   Resource Identifiers (URI): Generic Syntax," RFC 2396, Internet 
   Engineering Task Force, August 1998. 

   [n7] E. Burger, J. Van Dyke, A. Spitzer, "Basic Network Media 
   Services with SIP", RFC 4240, Internet Engineering Task Force, 
   December 2005  

   [n8] E. Levinson, "Content-ID and Message-ID Uniform Resource 
   Locators", RFC 2392, Internet Engineering Task Force, August 1998. 

   [n9] Handley, M. and V. Jacobson, "SDP: Session Description 
   Protocol," RFC 2327, Internet Engineering Task Force, April 1998. 

   [n10] Bos, B., Lie, H., Tantek, C., and Hickson, I., "Cascading Style 
   Sheets, level 2 (CSS2) Specification," W3C REC CR-CSS21-, July 2007. 

   [n11] Burnett, D., Walker, M., and Hunt, A., "Speech Synthesis Markup 
   Language (SSML) Version 1.0", W3C Recommendation, 7 September 2004. 

21.   Informative References 

   [i1] J. Rosenberg, H. Schulzrinne, and P. Kyzivat, "Indicating User 
   Agent Capabilities in the Session Initiation Protocol (SIP)", RFC 
   3840, Internet Engineering Task Force, August 2004 

   [i2] M. Murata, S. St.Laurent, and D. Kohn, "XML Media Types," RFC 
   3023, Internet Engineering Task Force, January 2001. 

   [i3] Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson, 
   "RTP Profile for Audio and Video Conferences with Minimal Control," 
   RFC 3550, Internet Engineering Task Force, July 2003. 

   [i4] Rosenberg, J., Peterson, J., Schulzrinne, H., and G. Camarillo, 
   "Best Current Practices for Third Party Call Control (3pcc) in the 
   Session Initiation Protocol (SIP)," RFC 3725, April 2004. 

   [i5] Donovan, S., "The SIP INFO Method," RFC 2976, Internet 
   Engineering Task Force, October 2000. 

 
 
Saleem, et al.         Expires January 29 2010               [Page 181] 


Internet-draft       Media Server Markup Language         July 28 2009 
                                 (MSML) 
 
 
   [i6] Ossenbruggen, J., Rutledge, L., Saccocio, B., Schmitz, P., Kate, 
   W., Ayars, J., Bulterman, D., Cohen, A., Day, K., Hodge, E., Hoschka, 
   P., Hyche, E., Jourdan, M., Kubota, K., Lanphier, R., Laya'da, N., 
   Michel, T., and D. Newman, "Synchronized Multimedia Integration 
   Language (SMIL 2.0) Specification," W3C REC REC-smil2-20050107, 
   January 2005. 

   [i7] Freed, N. and N. Borenstein, "Multipurpose Internet Mail 
   Extensions (MIME) Part Two: Media Types," RFC 2046, November 1996. 

   [i8] Saleem, A. and Sharratt, G., "Media Sessions Markup Language" 
   Internet Draft (draft-melanchuk-sipping-msml-06), October 21, 2005. 

   [i9] Saleem, A. and Sharratt, G., "Media Objects Markup Language" 
   Internet Draft (draft-melanchuk-sipping-moml-06), October 21, 2005. 

   [i10] Moats, R., "URN Syntax", RFC 2141, Internet Engineering Task 
   Force, May 1997. 

   [i11] Moats, R., "A URN Namespace for IETF Documents", RFC 2648, 
   Internet Engineering Task Force, August 1999. 

   [i12] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 
   Internet Engineering Task Force, January 2004. 

   [i13] Boulton, C., "A Control Framework for the Session Initiation 
   Protocol (SIP)", Internet Engineering Task Force, draft-boulton-sip-
   control-framework-05 (work in Progress, February 2007. 

Acknowledgments 

   Sergiu Stambolian of Radisys provided key insights, both theoretic 
   and through development experience, on several versions of the 
   drafts.  

   Stephen Buko and George Raskulinec of Intel made numerous valuable 
   contributions towards enhancements of multimedia playback and record 
   operations. Gene Shtirmer of Intel provided review feedback on 
   several revisions and feature enhancement suggestions. 

   David Asher of NMS Communications provided valuable insights towards 
   creation of standard profiles and a modularization scheme based on 
   packages for better interoperability.  

   Gilles Compienne of Ubiquity Software has provided feedback on 
   several earlier versions of this draft. 

 
 
Saleem, et al.         Expires January 29 2010               [Page 182] 


Internet-draft       Media Server Markup Language         July 28 2009 
                                 (MSML) 
 
 
   Chris Boulton and Ben Smith, both of Ubiquity, and Michael Rice of 
   VocalData helped clarify several issues, while Bruce Walsh and Kevin 
   Fitzgerald, both of Spectel/Avaya, provided important feedback. Cliff 
   Schornak of Commetrex significantly contributed to the facsimile 
   work. Peter Danielsen of Lucent has contributed thoughtful and 
   detailed reviews for several earlier versions of the draft.

   Funding for the RFC Editor function is provided by the IETF Internet 
   Administrative Support Activity (IASA). 

Authors' Addresses 

   Adnan Saleem
   Radisys 
   4190 Still Creek Drive, Suite 300 
   Burnaby, BC, V5C 6C6 
   Canada

   Phone: +1 604 918 6376 
   Email : adnan.saleem@radisys.com 
     
   Yong Xin  
   Radisys  
   4190 Still Creek Drive, Suite 300  
   Burnaby, BC, V5C 6C6  
   Canada

   Phone: +1 604 918 6383  
   Email: yong.xin@radiSys.com 
    
   Garland Sharratt

   Email: garland.sharratt@gmail.com 
 

 
 
Saleem, et al.         Expires January 29 2010               [Page 183]