< draft-ietf-mediactrl-ivr-control-package-09.txt   draft-ietf-mediactrl-ivr-control-package-10.txt >
Network Working Group S. McGlashan Network Working Group S. McGlashan
Internet-Draft Hewlett-Packard Internet-Draft Hewlett-Packard
Intended status: Standards Track T. Melanchuk Intended status: Standards Track T. Melanchuk
Expires: May 15, 2011 Rain Willow Communications Expires: July 8, 2011 Rain Willow Communications
C. Boulton C. Boulton
NS-Technologies NS-Technologies
November 11, 2010 January 4, 2011
An Interactive Voice Response (IVR) Control Package for the Media An Interactive Voice Response (IVR) Control Package for the Media
Control Channel Framework Control Channel Framework
draft-ietf-mediactrl-ivr-control-package-09 draft-ietf-mediactrl-ivr-control-package-10
Abstract Abstract
This document defines a Media Control Channel Framework Package for This document defines a Media Control Channel Framework Package for
Interactive Voice Response (IVR) dialog interaction on media Interactive Voice Response (IVR) dialog interaction on media
connections and conferences. The package defines dialog management connections and conferences. The package defines dialog management
request elements for preparing, starting and terminating dialog request elements for preparing, starting and terminating dialog
interactions, as well as associated responses and notifications. interactions, as well as associated responses and notifications.
Dialog interactions are specified in a dialog language. This package Dialog interactions are specified in a dialog language. This package
defines a lightweight IVR dialog language (supporting prompt defines a lightweight IVR dialog language (supporting prompt
skipping to change at page 1, line 44 skipping to change at page 1, line 44
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 15, 2011. This Internet-Draft will expire on July 8, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 20 skipping to change at page 3, line 20
3.1. Control Package Name . . . . . . . . . . . . . . . . . . 11 3.1. Control Package Name . . . . . . . . . . . . . . . . . . 11
3.2. Framework Message Usage . . . . . . . . . . . . . . . . . 11 3.2. Framework Message Usage . . . . . . . . . . . . . . . . . 11
3.3. Common XML Support . . . . . . . . . . . . . . . . . . . 12 3.3. Common XML Support . . . . . . . . . . . . . . . . . . . 12
3.4. CONTROL Message Body . . . . . . . . . . . . . . . . . . 12 3.4. CONTROL Message Body . . . . . . . . . . . . . . . . . . 12
3.5. REPORT Message Body . . . . . . . . . . . . . . . . . . . 12 3.5. REPORT Message Body . . . . . . . . . . . . . . . . . . . 12
3.6. Audit . . . . . . . . . . . . . . . . . . . . . . . . . . 13 3.6. Audit . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.7. Examples . . . . . . . . . . . . . . . . . . . . . . . . 13 3.7. Examples . . . . . . . . . . . . . . . . . . . . . . . . 13
4. Element Definitions . . . . . . . . . . . . . . . . . . . . . 14 4. Element Definitions . . . . . . . . . . . . . . . . . . . . . 14
4.1. <mscivr> . . . . . . . . . . . . . . . . . . . . . . . . 15 4.1. <mscivr> . . . . . . . . . . . . . . . . . . . . . . . . 15
4.2. Dialog Management Elements . . . . . . . . . . . . . . . 16 4.2. Dialog Management Elements . . . . . . . . . . . . . . . 16
4.2.1. <dialogprepare> . . . . . . . . . . . . . . . . . . . 19 4.2.1. <dialogprepare> . . . . . . . . . . . . . . . . . . . 20
4.2.2. <dialogstart> . . . . . . . . . . . . . . . . . . . . 22 4.2.2. <dialogstart> . . . . . . . . . . . . . . . . . . . . 23
4.2.2.1. <subscribe> . . . . . . . . . . . . . . . . . . . 25 4.2.2.1. <subscribe> . . . . . . . . . . . . . . . . . . . 26
4.2.2.1.1. <dtmfsub> . . . . . . . . . . . . . . . . . . 26 4.2.2.1.1. <dtmfsub> . . . . . . . . . . . . . . . . . . 27
4.2.2.2. <stream> . . . . . . . . . . . . . . . . . . . . 27 4.2.2.2. <stream> . . . . . . . . . . . . . . . . . . . . 28
4.2.2.2.1. <region> . . . . . . . . . . . . . . . . . . 28 4.2.2.2.1. <region> . . . . . . . . . . . . . . . . . . 29
4.2.2.2.2. <priority> . . . . . . . . . . . . . . . . . 28 4.2.2.2.2. <priority> . . . . . . . . . . . . . . . . . 29
4.2.3. <dialogterminate> . . . . . . . . . . . . . . . . . . 29 4.2.3. <dialogterminate> . . . . . . . . . . . . . . . . . . 30
4.2.4. <response> . . . . . . . . . . . . . . . . . . . . . 30 4.2.4. <response> . . . . . . . . . . . . . . . . . . . . . 31
4.2.5. <event> . . . . . . . . . . . . . . . . . . . . . . . 31 4.2.5. <event> . . . . . . . . . . . . . . . . . . . . . . . 32
4.2.5.1. <dialogexit> . . . . . . . . . . . . . . . . . . 31 4.2.5.1. <dialogexit> . . . . . . . . . . . . . . . . . . 32
4.2.5.2. <dtmfnotify> . . . . . . . . . . . . . . . . . . 33 4.2.5.2. <dtmfnotify> . . . . . . . . . . . . . . . . . . 34
4.2.6. <params> . . . . . . . . . . . . . . . . . . . . . . 33 4.2.6. <params> . . . . . . . . . . . . . . . . . . . . . . 35
4.2.6.1. <param> . . . . . . . . . . . . . . . . . . . . . 34 4.2.6.1. <param> . . . . . . . . . . . . . . . . . . . . . 35
4.3. IVR Dialog Elements . . . . . . . . . . . . . . . . . . . 35 4.3. IVR Dialog Elements . . . . . . . . . . . . . . . . . . . 36
4.3.1. <dialog> . . . . . . . . . . . . . . . . . . . . . . 36 4.3.1. <dialog> . . . . . . . . . . . . . . . . . . . . . . 38
4.3.1.1. <prompt> . . . . . . . . . . . . . . . . . . . . 39 4.3.1.1. <prompt> . . . . . . . . . . . . . . . . . . . . 40
4.3.1.1.1. <variable> . . . . . . . . . . . . . . . . . 40 4.3.1.1.1. <variable> . . . . . . . . . . . . . . . . . 42
4.3.1.1.1.1. Date type . . . . . . . . . . . . . . . . 41 4.3.1.1.1.1. Date type . . . . . . . . . . . . . . . . 43
4.3.1.1.1.2. Time type . . . . . . . . . . . . . . . . 42 4.3.1.1.1.2. Time type . . . . . . . . . . . . . . . . 44
4.3.1.1.1.3. Digits type . . . . . . . . . . . . . . . 43 4.3.1.1.1.3. Digits type . . . . . . . . . . . . . . . 44
4.3.1.1.2. <dtmf> . . . . . . . . . . . . . . . . . . . 43 4.3.1.1.2. <dtmf> . . . . . . . . . . . . . . . . . . . 45
4.3.1.1.3. <par> . . . . . . . . . . . . . . . . . . . . 44 4.3.1.1.3. <par> . . . . . . . . . . . . . . . . . . . . 45
4.3.1.1.3.1. <seq> . . . . . . . . . . . . . . . . . . 46 4.3.1.1.3.1. <seq> . . . . . . . . . . . . . . . . . . 47
4.3.1.2. <control> . . . . . . . . . . . . . . . . . . . . 47 4.3.1.2. <control> . . . . . . . . . . . . . . . . . . . . 49
4.3.1.3. <collect> . . . . . . . . . . . . . . . . . . . . 50 4.3.1.3. <collect> . . . . . . . . . . . . . . . . . . . . 51
4.3.1.3.1. <grammar> . . . . . . . . . . . . . . . . . . 53 4.3.1.3.1. <grammar> . . . . . . . . . . . . . . . . . . 54
4.3.1.4. <record> . . . . . . . . . . . . . . . . . . . . 54 4.3.1.4. <record> . . . . . . . . . . . . . . . . . . . . 56
4.3.1.5. <media> . . . . . . . . . . . . . . . . . . . . . 58 4.3.1.5. <media> . . . . . . . . . . . . . . . . . . . . . 60
4.3.2. Exit Information . . . . . . . . . . . . . . . . . . 60 4.3.2. Exit Information . . . . . . . . . . . . . . . . . . 61
4.3.2.1. <promptinfo> . . . . . . . . . . . . . . . . . . 60 4.3.2.1. <promptinfo> . . . . . . . . . . . . . . . . . . 61
4.3.2.2. <controlinfo> . . . . . . . . . . . . . . . . . . 60 4.3.2.2. <controlinfo> . . . . . . . . . . . . . . . . . . 62
4.3.2.2.1. <controlmatch> . . . . . . . . . . . . . . . 60 4.3.2.2.1. <controlmatch> . . . . . . . . . . . . . . . 62
4.3.2.3. <collectinfo> . . . . . . . . . . . . . . . . . . 60 4.3.2.3. <collectinfo> . . . . . . . . . . . . . . . . . . 62
4.3.2.4. <recordinfo> . . . . . . . . . . . . . . . . . . 61 4.3.2.4. <recordinfo> . . . . . . . . . . . . . . . . . . 62
4.3.2.4.1. <mediainfo> . . . . . . . . . . . . . . . . . 61 4.3.2.4.1. <mediainfo> . . . . . . . . . . . . . . . . . 63
4.4. Audit Elements . . . . . . . . . . . . . . . . . . . . . 62 4.4. Audit Elements . . . . . . . . . . . . . . . . . . . . . 63
4.4.1. <audit> . . . . . . . . . . . . . . . . . . . . . . . 62 4.4.1. <audit> . . . . . . . . . . . . . . . . . . . . . . . 64
4.4.2. <auditresponse> . . . . . . . . . . . . . . . . . . . 64 4.4.2. <auditresponse> . . . . . . . . . . . . . . . . . . . 65
4.4.2.1. <codecs> . . . . . . . . . . . . . . . . . . . . 65 4.4.2.1. <codecs> . . . . . . . . . . . . . . . . . . . . 67
4.4.2.1.1. <codec> . . . . . . . . . . . . . . . . . . . 66 4.4.2.1.1. <codec> . . . . . . . . . . . . . . . . . . . 68
4.4.2.2. <capabilities> . . . . . . . . . . . . . . . . . 67 4.4.2.2. <capabilities> . . . . . . . . . . . . . . . . . 68
4.4.2.2.1. <dialoglanguages> . . . . . . . . . . . . . . 68 4.4.2.2.1. <dialoglanguages> . . . . . . . . . . . . . . 70
4.4.2.2.2. <grammartypes> . . . . . . . . . . . . . . . 69 4.4.2.2.2. <grammartypes> . . . . . . . . . . . . . . . 71
4.4.2.2.3. <recordtypes> . . . . . . . . . . . . . . . . 69 4.4.2.2.3. <recordtypes> . . . . . . . . . . . . . . . . 71
4.4.2.2.4. <prompttypes> . . . . . . . . . . . . . . . . 69 4.4.2.2.4. <prompttypes> . . . . . . . . . . . . . . . . 71
4.4.2.2.5. <variables> . . . . . . . . . . . . . . . . . 70 4.4.2.2.5. <variables> . . . . . . . . . . . . . . . . . 72
4.4.2.2.5.1. <variabletype> . . . . . . . . . . . . . 70 4.4.2.2.5.1. <variabletype> . . . . . . . . . . . . . 72
4.4.2.2.6. <maxpreparedduration> . . . . . . . . . . . . 71 4.4.2.2.6. <maxpreparedduration> . . . . . . . . . . . . 73
4.4.2.2.7. <maxrecordduration> . . . . . . . . . . . . . 71 4.4.2.2.7. <maxrecordduration> . . . . . . . . . . . . . 73
4.4.2.3. <dialogs> . . . . . . . . . . . . . . . . . . . . 71 4.4.2.3. <dialogs> . . . . . . . . . . . . . . . . . . . . 73
4.4.2.3.1. <dialogaudit> . . . . . . . . . . . . . . . . 71 4.4.2.3.1. <dialogaudit> . . . . . . . . . . . . . . . . 73
4.5. Response Status Codes . . . . . . . . . . . . . . . . . . 72 4.5. Response Status Codes . . . . . . . . . . . . . . . . . . 74
4.6. Type Definitions . . . . . . . . . . . . . . . . . . . . 78 4.6. Type Definitions . . . . . . . . . . . . . . . . . . . . 80
5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 81 5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 83
6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 108 6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 110
6.1. AS-MS Dialog Interaction Examples . . . . . . . . . . . . 108 6.1. AS-MS Dialog Interaction Examples . . . . . . . . . . . . 110
6.1.1. Starting an IVR dialog . . . . . . . . . . . . . . . 108 6.1.1. Starting an IVR dialog . . . . . . . . . . . . . . . 110
6.1.2. IVR dialog fails to start . . . . . . . . . . . . . . 109 6.1.2. IVR dialog fails to start . . . . . . . . . . . . . . 111
6.1.3. Preparing and starting an IVR dialog . . . . . . . . 109 6.1.3. Preparing and starting an IVR dialog . . . . . . . . 111
6.1.4. Terminating a dialog . . . . . . . . . . . . . . . . 110 6.1.4. Terminating a dialog . . . . . . . . . . . . . . . . 112
6.2. IVR Dialog Examples . . . . . . . . . . . . . . . . . . . 111 6.2. IVR Dialog Examples . . . . . . . . . . . . . . . . . . . 113
6.2.1. Playing announcements . . . . . . . . . . . . . . . . 111 6.2.1. Playing announcements . . . . . . . . . . . . . . . . 113
6.2.2. Prompt and collect . . . . . . . . . . . . . . . . . 112 6.2.2. Prompt and collect . . . . . . . . . . . . . . . . . 114
6.2.3. Prompt and record . . . . . . . . . . . . . . . . . . 114 6.2.3. Prompt and record . . . . . . . . . . . . . . . . . . 116
6.2.4. Runtime controls . . . . . . . . . . . . . . . . . . 115 6.2.4. Runtime controls . . . . . . . . . . . . . . . . . . 117
6.2.5. Subscriptions and notifications . . . . . . . . . . . 116 6.2.5. Subscriptions and notifications . . . . . . . . . . . 118
6.2.6. Dialog repetition until DTMF collection complete . . 116 6.2.6. Dialog repetition until DTMF collection complete . . 118
6.3. Other Dialog Languages . . . . . . . . . . . . . . . . . 117 6.3. Other Dialog Languages . . . . . . . . . . . . . . . . . 119
6.4. Foreign Namespace Attributes and Elements . . . . . . . . 118 6.4. Foreign Namespace Attributes and Elements . . . . . . . . 120
7. Security Considerations . . . . . . . . . . . . . . . . . . . 120 7. Security Considerations . . . . . . . . . . . . . . . . . . . 122
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 123 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 125
8.1. Control Package Registration . . . . . . . . . . . . . . 123 8.1. Control Package Registration . . . . . . . . . . . . . . 125
8.2. URN Sub-Namespace Registration . . . . . . . . . . . . . 123 8.2. URN Sub-Namespace Registration . . . . . . . . . . . . . 125
8.3. XML Schema Registration . . . . . . . . . . . . . . . . . 124 8.3. XML Schema Registration . . . . . . . . . . . . . . . . . 126
8.4. MIME Media Type Registration for 8.4. MIME Media Type Registration for
'application/msc-ivr+xml' . . . . . . . . . . . . . . . . 124 'application/msc-ivr+xml' . . . . . . . . . . . . . . . . 126
8.5. IVR Prompt Variable Type Registration Information . . . . 125 8.5. IVR Prompt Variable Type Registration Information . . . . 127
9. Using VoiceXML as a dialog language . . . . . . . . . . . . . 127 9. Using VoiceXML as a dialog language . . . . . . . . . . . . . 129
10. Change Summary . . . . . . . . . . . . . . . . . . . . . . . 135 10. Change Summary . . . . . . . . . . . . . . . . . . . . . . . 137
11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 151 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 154
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 152 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 155
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 153 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 156
13.1. Normative References . . . . . . . . . . . . . . . . . . 153 13.1. Normative References . . . . . . . . . . . . . . . . . . 156
13.2. Informative References . . . . . . . . . . . . . . . . . 154 13.2. Informative References . . . . . . . . . . . . . . . . . 157
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 157 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 160
1. Introduction 1. Introduction
The Media Control Channel Framework The Media Control Channel Framework
([I-D.ietf-mediactrl-sip-control-framework]) provides a generic ([I-D.ietf-mediactrl-sip-control-framework]) provides a generic
approach for establishment and reporting capabilities of remotely approach for establishment and reporting capabilities of remotely
initiated commands. The Channel Framework - an equivalent term for initiated commands. The Channel Framework - an equivalent term for
the Media Control Channel Framework - utilizes many functions the Media Control Channel Framework - utilizes many functions
provided by the Session Initiation Protocol [RFC3261] (SIP) for the provided by the Session Initiation Protocol [RFC3261] (SIP) for the
rendezvous and establishment of a reliable channel for control rendezvous and establishment of a reliable channel for control
skipping to change at page 14, line 42 skipping to change at page 14, line 42
additional capabilities by means of attributes and elements from additional capabilities by means of attributes and elements from
other (foreign) namespaces. Attributes and elements from foreign other (foreign) namespaces. Attributes and elements from foreign
namespaces are not described in this section. namespaces are not described in this section.
Some elements in this control package contain attributes whose value Some elements in this control package contain attributes whose value
is a URI. These elements include: <dialogprepare> (Section 4.2.1), is a URI. These elements include: <dialogprepare> (Section 4.2.1),
<dialogstart> (Section 4.2.2), <media> (Section 4.3.1.5), <grammar> <dialogstart> (Section 4.2.2), <media> (Section 4.3.1.5), <grammar>
(Section 4.3.1.3.1), and <record> (Section 4.3.1.4). The MS MUST (Section 4.3.1.3.1), and <record> (Section 4.3.1.4). The MS MUST
support both HTTP ([RFC2616]) and HTTPS ([RFC2818]) protocol schemes support both HTTP ([RFC2616]) and HTTPS ([RFC2818]) protocol schemes
for fetching and uploading resources and the MS MAY support other for fetching and uploading resources and the MS MAY support other
schemes. schemes. The implementation SHOULD support storage of authentication
information as part of its configuration, including security
certificates for use with HTTPS. If the implementation wants to
support user authentication, user certifications and passwords can
also be stored as part of its configuration or the implementation can
extend the schema (adding, for example, an http-password attribute in
its own namespace) and then map user authentication information onto
the appropriate headers following the HTTP authentication model
([RFC2616]).
Some elements in this control package contain attributes whose value Some elements in this control package contain attributes whose value
is descriptive text. Since the descriptive text is for diagnostic is descriptive text primarily for diagnostic use. The implementation
use only, and is neither a protocol element nor intended for user can indicated the language used in the descriptive text by means of a
display, the descriptive text does not require a language indicator 'desclang' attribute ([RFC2277]). The desclang attribute can appear
such as a language tag ([RFC2277]) and thus does not carry one. on the root element as well as selected subordinate elements (see
These comprise: the reason attribute on <response> (Section 4.2.4), Section 4.1). The desclang attribute value on the root element
<dialogexit> (Section 4.2.5.1) and <auditresponse> (Section 4.4.2); applies to all desclang attributes in subordinate elements unless the
desc attribute on <variabletype> and <format> (Section 4.4.2.2.5.1). subordinate element has an explicit desclang attribute which
overrides it.
Usage examples are provided in Section 6. Usage examples are provided in Section 6.
4.1. <mscivr> 4.1. <mscivr>
The <mscivr> element has the following attributes (in addition to The <mscivr> element has the following attributes (in addition to
standard XML namespace attributes such as xmlns): standard XML namespace attributes such as xmlns):
version: a string specifying the mscivr package version. The value version: a string specifying the mscivr package version. The value
is fixed as '1.0' for this version of the package. The attribute is fixed as '1.0' for this version of the package. The attribute
is mandatory. is mandatory.
desclang: specifies the language used in descriptive text attributes
of subordinate elements (unless the subordinate element provides a
desclang attribute which overrides the value for its descriptive
text attributes). The descriptive text attributes on subordinate
elements include: the reason attribute on <response>
(Section 4.2.4), <dialogexit> (Section 4.2.5.1) and
<auditresponse> (Section 4.4.2); desc attribute on <variabletype>
and <format> (Section 4.4.2.2.5.1). A valid value is a language
identifier (Section 4.6.11). The attribute is optional. The
default value is i-default (BCP47 [RFC5646]).
The <mscivr> element has the following defined child elements, only The <mscivr> element has the following defined child elements, only
one of which can occur: one of which can occur:
1. dialog management elements defined in Section 4.2: 1. dialog management elements defined in Section 4.2:
<dialogprepare> prepare a dialog. See Section 4.2.1 <dialogprepare> prepare a dialog. See Section 4.2.1
<dialogstart> start a dialog. See Section 4.2.2 <dialogstart> start a dialog. See Section 4.2.2
<dialogterminate> terminate a dialog. See Section 4.2.3 <dialogterminate> terminate a dialog. See Section 4.2.3
skipping to change at page 16, line 12 skipping to change at page 16, line 34
and a response from the MS that the dialog started successfully: and a response from the MS that the dialog started successfully:
<mscivr version="1.0" xmlns="urn:ietf:params:xml:ns:msc-ivr"> <mscivr version="1.0" xmlns="urn:ietf:params:xml:ns:msc-ivr">
<response status="200" dialogid="d1"/> <response status="200" dialogid="d1"/>
</mscivr> </mscivr>
and finally a notification from the MS indicating that the dialog and finally a notification from the MS indicating that the dialog
exited upon completion of playing the prompt: exited upon completion of playing the prompt:
<mscivr version="1.0" xmlns="urn:ietf:params:xml:ns:msc-ivr"> <mscivr version="1.0" xmlns="urn:ietf:params:xml:ns:msc-ivr"
<event dialogid="d1"> desclang="en">
<dialogexit status="1"> <event dialogid="d1">
<promptinfo termmode="completed"/> <dialogexit status="1" reason="successful completion of the dialog">
</dialogexit> <promptinfo termmode="completed"/>
</event> </dialogexit>
</mscivr> </event>
</mscivr>
The language of the descriptive text in the reason attribute of
<dialogexit> is explicitly indicated by the desclang attribute of the
<mscivr> root element.
4.2. Dialog Management Elements 4.2. Dialog Management Elements
This section defines the dialog management XML elements for this This section defines the dialog management XML elements for this
control package. These elements are divided into requests, responses control package. These elements are divided into requests, responses
and notifications. and notifications.
Request elements are sent to the MS to request a specific dialog Request elements are sent to the MS to request a specific dialog
operation to be executed. The following request elements are operation to be executed. The following request elements are
defined: defined:
skipping to change at page 30, line 18 skipping to change at page 31, line 18
<response> element. <response> element.
The <response> element has following attributes: The <response> element has following attributes:
status: numeric code indicating the response status. Valid values status: numeric code indicating the response status. Valid values
are defined in Section 4.5. The attribute is mandatory. are defined in Section 4.5. The attribute is mandatory.
reason: string specifying a reason for the response status. The reason: string specifying a reason for the response status. The
attribute is optional. There is no default value. attribute is optional. There is no default value.
desclang: specifies the language used in the value of the the reason
attribute. A valid value is a language identifier
(Section 4.6.11). The attribute is optional. If not specified,
the value of the desclang attribute on <mscivr> (Section 4.1)
applies.
dialogid: string identifying the dialog. If the request specifies a dialogid: string identifying the dialog. If the request specifies a
dialogid, then that value is used. Otherwise, with dialogid, then that value is used. Otherwise, with
<dialogprepare> and <dialogstart> requests, the dialogid generated <dialogprepare> and <dialogstart> requests, the dialogid generated
by the MS is used. If there is no available dialogid because the by the MS is used. If there is no available dialogid because the
request is syntactically invalid (e.g. a <dialogterminate> request request is syntactically invalid (e.g. a <dialogterminate> request
with no dialogid attribute specified), then the value is the empty with no dialogid attribute specified), then the value is the empty
string. The attribute is mandatory. string. The attribute is mandatory.
connectionid: string identifying the SIP dialog connection connectionid: string identifying the SIP dialog connection
associated with the dialog (see Section 16.1 of associated with the dialog (see Section 16.1 of
skipping to change at page 32, line 26 skipping to change at page 33, line 33
where new status codes are assigned using the Standards Action where new status codes are assigned using the Standards Action
process defined in [RFC5226]. The AS MUST treat any status code process defined in [RFC5226]. The AS MUST treat any status code
it does not recognize as being equivalent to 4 (dialog execution it does not recognize as being equivalent to 4 (dialog execution
error). The attribute is mandatory. error). The attribute is mandatory.
reason: a textual description which the MS SHOULD use to provide a reason: a textual description which the MS SHOULD use to provide a
reason for the status code; e.g. details about an error. A valid reason for the status code; e.g. details about an error. A valid
value is a string (see Section 4.6.6). The attribute is optional. value is a string (see Section 4.6.6). The attribute is optional.
There is no default value. There is no default value.
desclang: specifies the language used in the value of the the reason
attribute. A valid value is a language identifier
(Section 4.6.11). The attribute is optional. If not specified,
the value of the desclang attribute on <mscivr> (Section 4.1)
applies.
The <dialogexit> element has the following sequence of child The <dialogexit> element has the following sequence of child
elements: elements:
<promptinfo>: report information (Section 4.3.2.1) about the prompt <promptinfo>: report information (Section 4.3.2.1) about the prompt
execution in an IVR <dialog>. The element is optional. execution in an IVR <dialog>. The element is optional.
<controlinfo>: reports information (Section 4.3.2.2) about the <controlinfo>: reports information (Section 4.3.2.2) about the
control execution in an IVR <dialog>. The element is optional. control execution in an IVR <dialog>. The element is optional.
<collectinfo>: reports information (Section 4.3.2.3) about the <collectinfo>: reports information (Section 4.3.2.3) about the
skipping to change at page 56, line 5 skipping to change at page 57, line 17
itself. This parameter is ignored if the vadfinal attribute has itself. This parameter is ignored if the vadfinal attribute has
the value false. A valid value is a Time Designation (see the value false. A valid value is a Time Designation (see
Section 4.6.7). The attribute is optional. The default value is Section 4.6.7). The attribute is optional. The default value is
5s. 5s.
append: indicates whether recorded data is appended or not to a append: indicates whether recorded data is appended or not to a
recording location if a resource already exists. A valid value is recording location if a resource already exists. A valid value is
a boolean (see Section 4.6.1). A value of true indicates that a boolean (see Section 4.6.1). A value of true indicates that
recorded data is appended to the existing resource at a recording recorded data is appended to the existing resource at a recording
location. A value of false indicates that recorded data is to location. A value of false indicates that recorded data is to
overwrite the existing resource. The mapping of the append overwrite the existing resource. The attribute is optional. The
operation onto the upload protocol scheme is implementation- default value is false.
specific. The attribute is optional. The default value is false.
When a recording location is specified using the HTTP or HTTPS
protocol, the recording operation SHOULD be performed using the
HTTP GET and PUT methods, unless the HTTP server provides a
special interface for recording uploads and appends (e.g. using
POST). When the append attribute has the value false, the
recording data is uploaded to the specified location using HTTP
PUT and replaces any data at that location on the HTTP origin
server. When append has the value true, the existing data (if
any) is first downloaded from the specified location using HTTP
GET, then the recording data is appended to the existing recording
(note that this might require codec conversion and modification to
the existing data), then the combined recording is uploaded to the
specified location using HTTP PUT. HTTP errors are handled as
described in [RFC2616].
When the recording location is specified using protocols other
than HTTP or HTTPS, the mapping of the append operation onto the
upload protocol scheme is implementation-specific.
If either the vadinitial or vadfinal attribute is set to true and the If either the vadinitial or vadfinal attribute is set to true and the
MS does not support VAD, the MS sends a <response> with a 434 status MS does not support VAD, the MS sends a <response> with a 434 status
code (Section 4.5). code (Section 4.5).
The <record> element has the following child element (0 or more The <record> element has the following child element (0 or more
occurrences): occurrences):
<media>: specifies the location and type of the media resource for <media>: specifies the location and type of the media resource for
uploading recorded data (see Section 4.3.1.5). The MS MUST uploading recorded data (see Section 4.3.1.5). The MS MUST
skipping to change at page 64, line 4 skipping to change at page 65, line 30
In this example, only capabilities are to be audited: In this example, only capabilities are to be audited:
<mscivr version="1.0" xmlns="urn:ietf:params:xml:ns:msc-ivr"> <mscivr version="1.0" xmlns="urn:ietf:params:xml:ns:msc-ivr">
<audit dialogs="false"/> <audit dialogs="false"/>
</mscivr> </mscivr>
With this example, only a specific dialog is to be audited: With this example, only a specific dialog is to be audited:
<mscivr version="1.0" xmlns="urn:ietf:params:xml:ns:msc-ivr"> <mscivr version="1.0" xmlns="urn:ietf:params:xml:ns:msc-ivr">
<audit capabilities="false" dialogid="d4"/> <audit capabilities="false" dialogid="d4"/>
</mscivr> </mscivr>
4.4.2. <auditresponse> 4.4.2. <auditresponse>
The <auditresponse> element describes a response to a <audit> The <auditresponse> element describes a response to a <audit>
request. request.
The <auditresponse> element has the following attributes: The <auditresponse> element has the following attributes:
status: numeric code indicating the audit response status. The status: numeric code indicating the audit response status. The
attribute is mandatory. Valid values are defined in Section 4.5. attribute is mandatory. Valid values are defined in Section 4.5.
reason: string specifying a reason for the status. The attribute is reason: string specifying a reason for the status. The attribute is
optional. optional.
desclang: specifies the language used in the value of the the reason
attribute. A valid value is a language identifier
(Section 4.6.11). The attribute is optional. If not specified,
the value of the desclang attribute on <mscivr> (Section 4.1)
applies.
The <auditresponse> element has the following sequence of child The <auditresponse> element has the following sequence of child
elements: elements:
<capabilities> element (Section 4.4.2.2) describing capabilities of <capabilities> element (Section 4.4.2.2) describing capabilities of
the package. The element is optional. the package. The element is optional.
<dialogs> element (Section 4.4.2.3) describing information about <dialogs> element (Section 4.4.2.3) describing information about
managed dialogs. The element is optional. managed dialogs. The element is optional.
For example, a successful response to a <audit> request requesting For example, a successful response to a <audit> request requesting
skipping to change at page 70, line 45 skipping to change at page 72, line 45
<variable> supported type. <variable> supported type.
The <variabletype> element has the following attributes: The <variabletype> element has the following attributes:
type: indicates a supported value associated with the type attribute type: indicates a supported value associated with the type attribute
of <variable> element. The attribute is manadatory. of <variable> element. The attribute is manadatory.
desc: a string providing some textual description of the type and desc: a string providing some textual description of the type and
format. The attribute is optional. format. The attribute is optional.
desclang: specifies the language used in the value of the the desc
attribute. A valid value is a language identifier
(Section 4.6.11). The attribute is optional. If not specified,
the value of the desclang attribute on <mscivr> (Section 4.1)
applies.
The <variabletype> element has the following sequence of child The <variabletype> element has the following sequence of child
elements (0 or more occurrences): elements (0 or more occurrences):
<format>: element with a desc attribute (optional description) and a <format>: element with a desc attribute (optional description),
desclang (optional language identifier for the description) and a
content model describing a supported format in the <variable> content model describing a supported format in the <variable>
format attribute. The element is optional. format attribute. The element is optional.
4.4.2.2.6. <maxpreparedduration> 4.4.2.2.6. <maxpreparedduration>
The <maxpreparedduration> element describes the maximum duration for The <maxpreparedduration> element describes the maximum duration for
a dialog to remain in the prepared state (Section 4.2) following a a dialog to remain in the prepared state (Section 4.2) following a
<dialogprepare> (Section 4.2.1) request. <dialogprepare> (Section 4.2.1) request.
The <maxpreparedduration> element has no attributes. The <maxpreparedduration> element has no attributes.
skipping to change at page 79, line 5 skipping to change at page 81, line 14
4.6.3. DTMFString 4.6.3. DTMFString
A String composed of one or more DTMFChars. A String composed of one or more DTMFChars.
4.6.4. Non-Negative Integer 4.6.4. Non-Negative Integer
The value space of non-negative integer is the infinite set The value space of non-negative integer is the infinite set
{0,1,2,...} as defined in Section 3.3.20 of [XMLSchema:Part2]. {0,1,2,...} as defined in Section 3.3.20 of [XMLSchema:Part2].
Implementation Note: It is RECOMMENDED that implementations at least
support a maximum value of a 32 bit integer (2,147,483,647).
4.6.5. Positive Integer 4.6.5. Positive Integer
The value space of positive integer is the infinite set {1,2,...} as The value space of positive integer is the infinite set {1,2,...} as
defined in Section 3.3.25 of [XMLSchema:Part2]. defined in Section 3.3.25 of [XMLSchema:Part2].
Implementation Note: It is RECOMMENDED that implementations at least
support a maximum value of a 32 bit integer (2,147,483,647).
4.6.6. String 4.6.6. String
A string in the character encoding associated with the XML element as A string in the character encoding associated with the XML element as
defined in Section 3.2.1 of [XMLSchema:Part2]. defined in Section 3.2.1 of [XMLSchema:Part2].
4.6.7. Time Designation 4.6.7. Time Designation
A time designation consists of a non-negative real number followed by A time designation consists of a non-negative real number followed by
a time unit identifier. a time unit identifier.
skipping to change at page 79, line 39 skipping to change at page 82, line 5
4.6.9. URI 4.6.9. URI
Uniform Resource Indicator as defined in [RFC3986]. Uniform Resource Indicator as defined in [RFC3986].
4.6.10. MIME Media Type 4.6.10. MIME Media Type
A string formated as an IANA MIME media type ([MIME.mediatypes]). A string formated as an IANA MIME media type ([MIME.mediatypes]).
The ABNF ([RFC5234]) production for the string is: The ABNF ([RFC5234]) production for the string is:
type-name "/" subtype-name *(";" parameter-name) type-name "/" subtype-name *(";" parameter)
where "type-name" and "subtype-name" are defined in Section 4.2, and parameter = parameter-name "=" value
"parameter-name" in Section 4.3, of [RFC4288].
where "type-name" and "subtype-name" are defined in Section 4.2 of
[RFC4288], "parameter-name" is defined in Section 4.3 of [RFC4288]
and "value" is defined in Section 5.1 of [RFC2045].
4.6.11. Language Identifier 4.6.11. Language Identifier
A language identifier labels information content as being of a A language identifier labels information content as being of a
particular human language variant. Following the XML specification particular human language variant. Following the XML specification
for language identification [XML], a legal language identifier is for language identification [XML], a legal language identifier is
identified by a RFC5646 ([RFC5646]) and RFC4647 ([RFC4647]) code identified by a RFC5646 ([RFC5646]) and RFC4647 ([RFC4647]) code
where the language code is required and a country code or other where the language code is required and a country code or other
subtag identifier is optional. subtag identifier is optional.
skipping to change at page 81, line 32 skipping to change at page 83, line 32
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace="urn:ietf:params:xml:ns:msc-ivr" <xsd:schema targetNamespace="urn:ietf:params:xml:ns:msc-ivr"
elementFormDefault="qualified" blockDefault="#all" elementFormDefault="qualified" blockDefault="#all"
xmlns="urn:ietf:params:xml:ns:msc-ivr" xmlns="urn:ietf:params:xml:ns:msc-ivr"
xmlns:fw="urn:ietf:params:xml:ns:control:framework-attributes" xmlns:fw="urn:ietf:params:xml:ns:control:framework-attributes"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:annotation> <xsd:annotation>
<xsd:documentation> <xsd:documentation>
IETF MediaCtrl IVR 1.0 (20101020) IETF MediaCtrl IVR 1.0 (20110104)
This is the schema of the IETF MediaCtrl IVR control This is the schema of the IETF MediaCtrl IVR control
package. package.
The schema namespace is urn:ietf:params:xml:ns:msc-ivr The schema namespace is urn:ietf:params:xml:ns:msc-ivr
</xsd:documentation> </xsd:documentation>
</xsd:annotation> </xsd:annotation>
<!-- <!--
skipping to change at page 83, line 25 skipping to change at page 85, line 25
<xsd:element ref="response" /> <xsd:element ref="response" />
<xsd:element ref="event" /> <xsd:element ref="event" />
<xsd:element ref="audit" /> <xsd:element ref="audit" />
<xsd:element ref="auditresponse" /> <xsd:element ref="auditresponse" />
<xsd:any namespace="##other" minOccurs="0" <xsd:any namespace="##other" minOccurs="0"
maxOccurs="unbounded" processContents="lax" /> maxOccurs="unbounded" processContents="lax" />
</xsd:choice> </xsd:choice>
</xsd:sequence> </xsd:sequence>
<xsd:attribute name="version" type="version.datatype" <xsd:attribute name="version" type="version.datatype"
use="required" /> use="required" />
<xsd:attribute name="desclang" type="xsd:language"
default="i-default" />
</xsd:extension> </xsd:extension>
</xsd:complexContent> </xsd:complexContent>
</xsd:complexType> </xsd:complexType>
<xsd:element name="mscivr" type="mscivrType" /> <xsd:element name="mscivr" type="mscivrType" />
<!-- <!--
##################################################### #####################################################
DIALOG MANAGEMENT TYPES DIALOG MANAGEMENT TYPES
skipping to change at page 85, line 35 skipping to change at page 87, line 37
<xsd:complexType name="responseType"> <xsd:complexType name="responseType">
<xsd:complexContent> <xsd:complexContent>
<xsd:extension base="Tcore"> <xsd:extension base="Tcore">
<xsd:sequence> <xsd:sequence>
<xsd:any namespace="##other" minOccurs="0" <xsd:any namespace="##other" minOccurs="0"
maxOccurs="unbounded" processContents="lax" /> maxOccurs="unbounded" processContents="lax" />
</xsd:sequence> </xsd:sequence>
<xsd:attribute name="status" type="status.datatype" <xsd:attribute name="status" type="status.datatype"
use="required" /> use="required" />
<xsd:attribute name="reason" type="xsd:string" /> <xsd:attribute name="reason" type="xsd:string" />
<xsd:attribute name="desclang" type="xsd:language"/>
<xsd:attribute name="dialogid" <xsd:attribute name="dialogid"
type="dialogid.datatype" use="required" /> type="dialogid.datatype" use="required" />
<xsd:attributeGroup ref="fw:framework-attributes" /> <xsd:attributeGroup ref="fw:framework-attributes" />
</xsd:extension> </xsd:extension>
</xsd:complexContent> </xsd:complexContent>
</xsd:complexType> </xsd:complexType>
<xsd:element name="response" type="responseType" /> <xsd:element name="response" type="responseType" />
<!-- event --> <!-- event -->
skipping to change at page 86, line 41 skipping to change at page 88, line 44
<xsd:element ref="recordinfo" minOccurs="0" <xsd:element ref="recordinfo" minOccurs="0"
maxOccurs="1" /> maxOccurs="1" />
<xsd:element ref="params" minOccurs="0" <xsd:element ref="params" minOccurs="0"
maxOccurs="1" /> maxOccurs="1" />
<xsd:any namespace="##other" minOccurs="0" <xsd:any namespace="##other" minOccurs="0"
maxOccurs="unbounded" processContents="lax" /> maxOccurs="unbounded" processContents="lax" />
</xsd:sequence> </xsd:sequence>
<xsd:attribute name="status" <xsd:attribute name="status"
type="xsd:nonNegativeInteger" use="required" /> type="xsd:nonNegativeInteger" use="required" />
<xsd:attribute name="reason" type="xsd:string" /> <xsd:attribute name="reason" type="xsd:string" />
<xsd:attribute name="desclang" type="xsd:language"/>
</xsd:extension> </xsd:extension>
</xsd:complexContent> </xsd:complexContent>
</xsd:complexType> </xsd:complexType>
<xsd:element name="dialogexit" type="dialogexitType" /> <xsd:element name="dialogexit" type="dialogexitType" />
<!-- dtmfnotify--> <!-- dtmfnotify-->
<xsd:complexType name="dtmfnotifyType"> <xsd:complexType name="dtmfnotifyType">
<xsd:complexContent> <xsd:complexContent>
<xsd:extension base="Tcore"> <xsd:extension base="Tcore">
<xsd:sequence> <xsd:sequence>
<xsd:any namespace="##other" minOccurs="0" <xsd:any namespace="##other" minOccurs="0"
maxOccurs="unbounded" processContents="lax" /> maxOccurs="unbounded" processContents="lax" />
</xsd:sequence> </xsd:sequence>
<xsd:attribute name="matchmode" <xsd:attribute name="matchmode"
skipping to change at page 99, line 4 skipping to change at page 101, line 9
<xsd:element ref="capabilities" minOccurs="0" <xsd:element ref="capabilities" minOccurs="0"
maxOccurs="1" /> maxOccurs="1" />
<xsd:element ref="dialogs" minOccurs="0" <xsd:element ref="dialogs" minOccurs="0"
maxOccurs="1" /> maxOccurs="1" />
<xsd:any namespace="##other" minOccurs="0" <xsd:any namespace="##other" minOccurs="0"
maxOccurs="unbounded" processContents="lax" /> maxOccurs="unbounded" processContents="lax" />
</xsd:sequence> </xsd:sequence>
<xsd:attribute name="status" type="status.datatype" <xsd:attribute name="status" type="status.datatype"
use="required" /> use="required" />
<xsd:attribute name="reason" type="xsd:string" /> <xsd:attribute name="reason" type="xsd:string" />
<xsd:attribute name="desclang" type="xsd:language"/>
</xsd:extension> </xsd:extension>
</xsd:complexContent> </xsd:complexContent>
</xsd:complexType> </xsd:complexType>
<xsd:element name="auditresponse" type="auditresponseType" /> <xsd:element name="auditresponse" type="auditresponseType" />
<!-- codec --> <!-- codec -->
<xsd:complexType name="codecType"> <xsd:complexType name="codecType">
<xsd:complexContent> <xsd:complexContent>
skipping to change at page 102, line 46 skipping to change at page 105, line 4
<xsd:element name="variables" type="variablesType" /> <xsd:element name="variables" type="variablesType" />
<xsd:complexType name="variabletypeType"> <xsd:complexType name="variabletypeType">
<xsd:complexContent> <xsd:complexContent>
<xsd:extension base="Tcore"> <xsd:extension base="Tcore">
<xsd:sequence> <xsd:sequence>
<xsd:element ref="format" minOccurs="0" <xsd:element ref="format" minOccurs="0"
maxOccurs="unbounded" /> maxOccurs="unbounded" />
<xsd:any namespace="##other" minOccurs="0" <xsd:any namespace="##other" minOccurs="0"
maxOccurs="unbounded" processContents="lax" /> maxOccurs="unbounded" processContents="lax" />
</xsd:sequence> </xsd:sequence>
<xsd:attribute name="type" type="xsd:string" use="required" /> <xsd:attribute name="type" type="xsd:string" use="required" />
<xsd:attribute name="desc" type="xsd:string"/> <xsd:attribute name="desc" type="xsd:string"/>
<xsd:attribute name="desclang" type="xsd:language"/>
</xsd:extension> </xsd:extension>
</xsd:complexContent> </xsd:complexContent>
</xsd:complexType> </xsd:complexType>
<xsd:element name="variabletype" type="variabletypeType" /> <xsd:element name="variabletype" type="variabletypeType" />
<!-- format --> <!-- format -->
<!-- doesn't extend tCore since its content model is mixed --> <!-- doesn't extend tCore since its content model is mixed -->
<xsd:complexType name="formatType" mixed="true"> <xsd:complexType name="formatType" mixed="true">
<xsd:sequence> <xsd:sequence>
<xsd:any namespace="##other" minOccurs="0" <xsd:any namespace="##other" minOccurs="0"
maxOccurs="unbounded" processContents="lax" /> maxOccurs="unbounded" processContents="lax" />
</xsd:sequence> </xsd:sequence>
<xsd:attribute name="desc" type="xsd:string" /> <xsd:attribute name="desc" type="xsd:string" />
<xsd:attribute name="desclang" type="xsd:language"/>
<xsd:anyAttribute namespace="##other" processContents="lax" /> <xsd:anyAttribute namespace="##other" processContents="lax" />
</xsd:complexType> </xsd:complexType>
<xsd:element name="format" type="formatType" /> <xsd:element name="format" type="formatType" />
<!-- maxpreparedduration --> <!-- maxpreparedduration -->
<xsd:element name="maxpreparedduration" <xsd:element name="maxpreparedduration"
type="timedesignation.datatype"/> type="timedesignation.datatype"/>
skipping to change at page 135, line 9 skipping to change at page 137, line 9
raise an error event in the VoiceXML dialog execution context: an raise an error event in the VoiceXML dialog execution context: an
error.unsupported.transfer.blind event if blind transfer is error.unsupported.transfer.blind event if blind transfer is
requested, error.unsupported.transfer.bridge if bridge transfer is requested, error.unsupported.transfer.bridge if bridge transfer is
requested, or error.unsupported.transfer.consultation if consultation requested, or error.unsupported.transfer.consultation if consultation
transfer is requested. transfer is requested.
10. Change Summary 10. Change Summary
Note to RFC Editor: Please remove this whole section. Note to RFC Editor: Please remove this whole section.
The following are the changes between the -10 and -09 versions
(addressing remaining IESG DISCUSS and comments):
o 4.3.1.4: <record>: modified the description of the append
operation so that it is specified for the HTTP/HTTPS case to allow
interoperability. The modification permits use of POST so that
the HTTP server can do the appending, but implementation SHOULD
support a GET/PUT model where the media server performs the
appending.
o 4.0: Clarified that the implementation should support storage of
authentication information for HTTP requests and described some
options for how it can do this.
o 4.0, 4.1, etc: Added language tags to identify the language of
descriptive text attributes. A desclang attribute is added to the
root element and has a default value of i-default. Subordinate
elements with descriptive text attributes also have this attribute
defined - if it is not specified on the subordinate element, then
the desclang value on the root element applies. Added example of
desclang in 4.1.
o 5: Updated schema with desclang attributes
o Section 4.6.10: Corrected ABNF definition of IANA MIME media type
to allow parameter values.
o References: Updated JSON (RFC4627) reference to normative.
o 4.6.4, 4,6,5: Added note recommending that implementations support
at least a maximum value of a 32 bit integer for nonnegative and
positive integer type (W3C state they are infinite sets).
The following are the changes between the -09 and -08 versions The following are the changes between the -09 and -08 versions
(primarily addressing IESG DISCUSS, comments and nits): (primarily addressing IESG DISCUSS, comments and nits):
o 3.1: Aligned Control Package Name/Version with last Control o 3.1: Aligned Control Package Name/Version with last Control
Framework verbage. Framework verbage.
o 4.0: Modified communications protocol requirements so that a MS o 4.0: Modified communications protocol requirements so that a MS
MUST support both HTTP and HTTPS for fetching resources and MUST support both HTTP and HTTPS for fetching resources and
uploading recordings. Added statement to relevant element uploading recordings. Added statement to relevant element
definitions. definitions.
skipping to change at page 153, line 22 skipping to change at page 156, line 22
draft-ietf-mediactrl-sip-control-framework-12 (work in draft-ietf-mediactrl-sip-control-framework-12 (work in
progress), September 2010. progress), September 2010.
[RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail [RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part One: Format of Internet Message Extensions (MIME) Part One: Format of Internet Message
Bodies", RFC 2045, November 1996. Bodies", RFC 2045, November 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2277] Alvestrand, H., "IETF Policy on Character Sets and
Languages", BCP 18, RFC 2277, January 1998.
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000. [RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000.
[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media
Types", RFC 3023, January 2001. Types", RFC 3023, January 2001.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
skipping to change at page 153, line 44 skipping to change at page 156, line 47
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, January 2005. RFC 3986, January 2005.
[RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and
Registration Procedures", BCP 13, RFC 4288, December 2005. Registration Procedures", BCP 13, RFC 4288, December 2005.
[RFC4574] Levin, O. and G. Camarillo, "The Session Description [RFC4574] Levin, O. and G. Camarillo, "The Session Description
Protocol (SDP) Label Attribute", RFC 4574, August 2006. Protocol (SDP) Label Attribute", RFC 4574, August 2006.
[RFC4627] Crockford, D., "The application/json Media Type for
JavaScript Object Notation (JSON)", RFC 4627, July 2006.
[RFC4647] Phillips, A. and M. Davis, "Matching of Language Tags", [RFC4647] Phillips, A. and M. Davis, "Matching of Language Tags",
BCP 47, RFC 4647, September 2006. BCP 47, RFC 4647, September 2006.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, January 2008. Specifications: ABNF", STD 68, RFC 5234, January 2008.
skipping to change at page 154, line 24 skipping to change at page 157, line 31
and S. Tryphonas, "Voice Extensible Markup Language and S. Tryphonas, "Voice Extensible Markup Language
(VoiceXML) Version 2.0", W3C Recommendation, March 2004. (VoiceXML) Version 2.0", W3C Recommendation, March 2004.
[VXML21] Oshry, M., Auburn, RJ., Baggia, P., Bodell, M., Burke, D., [VXML21] Oshry, M., Auburn, RJ., Baggia, P., Bodell, M., Burke, D.,
Burnett, D., Candell, E., Carter, J., McGlashan, S., Lee, Burnett, D., Candell, E., Carter, J., McGlashan, S., Lee,
A., Porter, B., and K. Rehor, "Voice Extensible Markup A., Porter, B., and K. Rehor, "Voice Extensible Markup
Language (VoiceXML) Version 2.1", W3C Recommendation, Language (VoiceXML) Version 2.1", W3C Recommendation,
June 2007. June 2007.
[W3C.REC-SMIL2-20051213] [W3C.REC-SMIL2-20051213]
Koivisto, A., Bulterman, D., Michel, T., Layaida, N., Koivisto, A., Bulterman, D., Michel, T., Mullender, S.,
Zucker, D., Jansen, J., Mullender, S., and G. Grassel, Zucker, D., Jansen, J., Layaida, N., and G. Grassel,
"Synchronized Multimedia Integration Language (SMIL 2.1)", "Synchronized Multimedia Integration Language (SMIL 2.1)",
World Wide Web Consortium Recommendation REC-SMIL2- World Wide Web Consortium Recommendation REC-SMIL2-
20051213, December 2005, 20051213, December 2005,
<http://www.w3.org/TR/2005/REC-SMIL2-20051213>. <http://www.w3.org/TR/2005/REC-SMIL2-20051213>.
[XML] Bray, T., Paoli, J., Sperberg-McQueen, C M., Maler, E., [XML] Bray, T., Paoli, J., Sperberg-McQueen, C M., Maler, E.,
and F. Yergeau, "Extensible Markup Language (XML) 1.0 and F. Yergeau, "Extensible Markup Language (XML) 1.0
(Third Edition)", W3C Recommendation, February 2004. (Third Edition)", W3C Recommendation, February 2004.
[XMLSchema:Part2] [XMLSchema:Part2]
skipping to change at page 155, line 8 skipping to change at page 158, line 15
[I-D.ietf-mediactrl-mixer-control-package] [I-D.ietf-mediactrl-mixer-control-package]
McGlashan, S., Melanchuk, T., and C. Boulton, "A Mixer McGlashan, S., Melanchuk, T., and C. Boulton, "A Mixer
Control Package for the Media Control Channel Framework", Control Package for the Media Control Channel Framework",
draft-ietf-mediactrl-mixer-control-package-11 (work in draft-ietf-mediactrl-mixer-control-package-11 (work in
progress), February 2010. progress), February 2010.
[I-D.ietf-xcon-common-data-model] [I-D.ietf-xcon-common-data-model]
Novo, O., Camarillo, G., Morgan, D., and J. Urpalainen, Novo, O., Camarillo, G., Morgan, D., and J. Urpalainen,
"Conference Information Data Model for Centralized "Conference Information Data Model for Centralized
Conferencing (XCON)", draft-ietf-xcon-common-data-model-20 Conferencing (XCON)", draft-ietf-xcon-common-data-model-22
(work in progress), October 2010. (work in progress), December 2010.
[IANA] "IANA registry for RTP Payload Types", [IANA] "IANA registry for RTP Payload Types",
<http://www.iana.org/assignments/rtp-parameters>. <http://www.iana.org/assignments/rtp-parameters>.
[MIME.mediatypes] [MIME.mediatypes]
"IANA registry for MIME Media Types", "IANA registry for MIME Media Types",
<http://www.iana.org/assignments/media-types/>. <http://www.iana.org/assignments/media-types/>.
[RFC2277] Alvestrand, H., "IETF Policy on Character Sets and
Languages", BCP 18, RFC 2277, January 1998.
[RFC2897] Cromwell, D., "Proposal for an MGCP Advanced Audio [RFC2897] Cromwell, D., "Proposal for an MGCP Advanced Audio
Package", RFC 2897, August 2000. Package", RFC 2897, August 2000.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
June 2002. June 2002.
[RFC4240] Burger, E., Van Dyke, J., and A. Spitzer, "Basic Network [RFC4240] Burger, E., Van Dyke, J., and A. Spitzer, "Basic Network
Media Services with SIP", RFC 4240, December 2005. Media Services with SIP", RFC 4240, December 2005.
skipping to change at page 155, line 46 skipping to change at page 158, line 50
[RFC4267] Froumentin, M., "The W3C Speech Interface Framework Media [RFC4267] Froumentin, M., "The W3C Speech Interface Framework Media
Types: application/voicexml+xml, application/ssml+xml, Types: application/voicexml+xml, application/ssml+xml,
application/srgs, application/srgs+xml, application/ application/srgs, application/srgs+xml, application/
ccxml+xml, and application/pls+xml", RFC 4267, ccxml+xml, and application/pls+xml", RFC 4267,
November 2005. November 2005.
[RFC4281] Gellens, R., Singer, D., and P. Frojdh, "The Codecs [RFC4281] Gellens, R., Singer, D., and P. Frojdh, "The Codecs
Parameter for "Bucket" Media Types", RFC 4281, Parameter for "Bucket" Media Types", RFC 4281,
November 2005. November 2005.
[RFC4627] Crockford, D., "The application/json Media Type for
JavaScript Object Notation (JSON)", RFC 4627, July 2006.
[RFC4730] Burger, E. and M. Dolly, "A Session Initiation Protocol [RFC4730] Burger, E. and M. Dolly, "A Session Initiation Protocol
(SIP) Event Package for Key Press Stimulus (KPML)", (SIP) Event Package for Key Press Stimulus (KPML)",
RFC 4730, November 2006. RFC 4730, November 2006.
[RFC4733] Schulzrinne, H. and T. Taylor, "RTP Payload for DTMF [RFC4733] Schulzrinne, H. and T. Taylor, "RTP Payload for DTMF
Digits, Telephony Tones, and Telephony Signals", RFC 4733, Digits, Telephony Tones, and Telephony Signals", RFC 4733,
December 2006. December 2006.
[RFC4855] Casner, S., "Media Type Registration of RTP Payload [RFC4855] Casner, S., "Media Type Registration of RTP Payload
Formats", RFC 4855, February 2007. Formats", RFC 4855, February 2007.
 End of changes. 40 change blocks. 
127 lines changed or deleted 241 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/