| < draft-ietf-mediactrl-ivr-control-package-10.txt | draft-ietf-mediactrl-ivr-control-package-11.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: July 8, 2011 Rain Willow Communications | Expires: July 10, 2011 Rain Willow Communications | |||
| C. Boulton | C. Boulton | |||
| NS-Technologies | NS-Technologies | |||
| January 4, 2011 | January 6, 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-10 | draft-ietf-mediactrl-ivr-control-package-11 | |||
| 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 July 8, 2011. | This Internet-Draft will expire on July 10, 2011. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2011 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 | |||
| skipping to change at page 82, line 18 ¶ | skipping to change at page 82, line 18 ¶ | |||
| where "type-name" and "subtype-name" are defined in Section 4.2 of | where "type-name" and "subtype-name" are defined in Section 4.2 of | |||
| [RFC4288], "parameter-name" is defined in Section 4.3 of [RFC4288] | [RFC4288], "parameter-name" is defined in Section 4.3 of [RFC4288] | |||
| and "value" is defined in Section 5.1 of [RFC2045]. | 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 code ([RFC5646]) and matched according to | |||
| where the language code is required and a country code or other | RFC4647 ([RFC4647]). | |||
| subtag identifier is optional. | ||||
| 4.6.12. DateTime | 4.6.12. DateTime | |||
| A string formated according to the XML schema definition of a | A string formated according to the XML schema definition of a | |||
| dateTime type ([XMLSchema:Part2]). | dateTime type ([XMLSchema:Part2]). | |||
| 5. Formal Syntax | 5. Formal Syntax | |||
| This section defines the XML schema for IVR Control Package. The | This section defines the XML schema for IVR Control Package. The | |||
| schema is normative. | schema is normative. | |||
| skipping to change at page 137, 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 -11 and -10 versions | ||||
| (addressing remaining IESG DISCUSS and comments): | ||||
| o 4.6.11 Language Identifier: deleted statement "where the language | ||||
| code is required and a country code or other subtag identifier is | ||||
| optional" and clarified that RFC 4647 specifies the matching | ||||
| procedure. | ||||
| The following are the changes between the -10 and -09 versions | The following are the changes between the -10 and -09 versions | |||
| (addressing remaining IESG DISCUSS and comments): | (addressing remaining IESG DISCUSS and comments): | |||
| o 4.3.1.4: <record>: modified the description of the append | 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 | operation so that it is specified for the HTTP/HTTPS case to allow | |||
| interoperability. The modification permits use of POST so that | interoperability. The modification permits use of POST so that | |||
| the HTTP server can do the appending, but implementation SHOULD | the HTTP server can do the appending, but implementation SHOULD | |||
| support a GET/PUT model where the media server performs the | support a GET/PUT model where the media server performs the | |||
| appending. | appending. | |||
| End of changes. 6 change blocks. | ||||
| 7 lines changed or deleted | 14 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/ | ||||