From Internet-Drafts@ietf.org Tue Jan 4 09:30:04 2011 Return-Path: X-Original-To: mediactrl@core3.amsl.com Delivered-To: mediactrl@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0BE193A6D02; Tue, 4 Jan 2011 09:30:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.549 X-Spam-Level: X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bRL+8kf6isou; Tue, 4 Jan 2011 09:30:01 -0800 (PST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DA15A3A6C0B; Tue, 4 Jan 2011 09:30:01 -0800 (PST) MIME-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 3.10 Message-ID: <20110104173001.20752.55949.idtracker@localhost> Date: Tue, 04 Jan 2011 09:30:01 -0800 Cc: mediactrl@ietf.org Subject: [MEDIACTRL] I-D Action:draft-ietf-mediactrl-ivr-control-package-10.txt X-BeenThere: mediactrl@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Control WG Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jan 2011 17:30:04 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Media Server Control Working Group of the IETF. Title : An Interactive Voice Response (IVR) Control Package for the Media Control Channel Framework Author(s) : S. McGlashan, et al. Filename : draft-ietf-mediactrl-ivr-control-package-10.txt Pages : 160 Date : 2011-01-04 This document defines a Media Control Channel Framework Package for Interactive Voice Response (IVR) dialog interaction on media connections and conferences. The package defines dialog management request elements for preparing, starting and terminating dialog interactions, as well as associated responses and notifications. Dialog interactions are specified in a dialog language. This package defines a lightweight IVR dialog language (supporting prompt playback, runtime controls, Dual-Tone Multi-Frequency (DTMF) collection and media recording) and allows other dialog languages to be used. The package also defines elements for auditing package capabilities and IVR dialogs. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mediactrl-ivr-control-package-10.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-mediactrl-ivr-control-package-10.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2011-01-04091549.I-D@ietf.org> --NextPart-- From Internet-Drafts@ietf.org Tue Jan 4 09:30:08 2011 Return-Path: X-Original-To: mediactrl@core3.amsl.com Delivered-To: mediactrl@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2E8573A6D05; Tue, 4 Jan 2011 09:30:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.556 X-Spam-Level: X-Spam-Status: No, score=-102.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hiJmmeurbE7w; Tue, 4 Jan 2011 09:30:04 -0800 (PST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7520F3A6D03; Tue, 4 Jan 2011 09:30:02 -0800 (PST) MIME-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 3.10 Message-ID: <20110104173002.20752.800.idtracker@localhost> Date: Tue, 04 Jan 2011 09:30:02 -0800 Cc: mediactrl@ietf.org Subject: [MEDIACTRL] I-D Action:draft-ietf-mediactrl-mixer-control-package-13.txt X-BeenThere: mediactrl@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Control WG Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jan 2011 17:30:08 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Media Server Control Working Group of the IETF. Title : A Mixer Control Package for the Media Control Channel Framework Author(s) : S. McGlashan, et al. Filename : draft-ietf-mediactrl-mixer-control-package-13.txt Pages : 104 Date : 2011-01-04 This document defines a Media Control Channel Framework Package for managing mixers for media conferences and connections. The package defines request elements for managing conference mixers, managing mixers between conferences and/or connections, as well as associated responses and notifications. The package also defines elements for auditing package capabilities and mixers. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mediactrl-mixer-control-package-13.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-mediactrl-mixer-control-package-13.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2011-01-04091601.I-D@ietf.org> --NextPart-- From Internet-Drafts@ietf.org Thu Jan 6 06:00:03 2011 Return-Path: X-Original-To: mediactrl@core3.amsl.com Delivered-To: mediactrl@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 553583A6F20; Thu, 6 Jan 2011 06:00:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.563 X-Spam-Level: X-Spam-Status: No, score=-102.563 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gkUaVyqWq2QK; Thu, 6 Jan 2011 06:00:01 -0800 (PST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DEDD53A6E3C; Thu, 6 Jan 2011 06:00:01 -0800 (PST) MIME-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 3.10 Message-ID: <20110106140001.22492.44095.idtracker@localhost> Date: Thu, 06 Jan 2011 06:00:01 -0800 Cc: mediactrl@ietf.org Subject: [MEDIACTRL] I-D Action:draft-ietf-mediactrl-ivr-control-package-11.txt X-BeenThere: mediactrl@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Control WG Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jan 2011 14:00:03 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Media Server Control Working Group of the IETF. Title : An Interactive Voice Response (IVR) Control Package for the Media Control Channel Framework Author(s) : S. McGlashan, et al. Filename : draft-ietf-mediactrl-ivr-control-package-11.txt Pages : 160 Date : 2011-01-06 This document defines a Media Control Channel Framework Package for Interactive Voice Response (IVR) dialog interaction on media connections and conferences. The package defines dialog management request elements for preparing, starting and terminating dialog interactions, as well as associated responses and notifications. Dialog interactions are specified in a dialog language. This package defines a lightweight IVR dialog language (supporting prompt playback, runtime controls, Dual-Tone Multi-Frequency (DTMF) collection and media recording) and allows other dialog languages to be used. The package also defines elements for auditing package capabilities and IVR dialogs. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mediactrl-ivr-control-package-11.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-mediactrl-ivr-control-package-11.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2011-01-06055642.I-D@ietf.org> --NextPart-- From Internet-Drafts@ietf.org Thu Jan 6 06:00:04 2011 Return-Path: X-Original-To: mediactrl@core3.amsl.com Delivered-To: mediactrl@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AB65A3A6F15; Thu, 6 Jan 2011 06:00:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.566 X-Spam-Level: X-Spam-Status: No, score=-102.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1lQmyMhxzmvl; Thu, 6 Jan 2011 06:00:03 -0800 (PST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5F80B3A6F1D; Thu, 6 Jan 2011 06:00:02 -0800 (PST) MIME-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 3.10 Message-ID: <20110106140002.22492.19843.idtracker@localhost> Date: Thu, 06 Jan 2011 06:00:02 -0800 Cc: mediactrl@ietf.org Subject: [MEDIACTRL] I-D Action:draft-ietf-mediactrl-mixer-control-package-14.txt X-BeenThere: mediactrl@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Control WG Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jan 2011 14:00:05 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Media Server Control Working Group of the IETF. Title : A Mixer Control Package for the Media Control Channel Framework Author(s) : S. McGlashan, et al. Filename : draft-ietf-mediactrl-mixer-control-package-14.txt Pages : 105 Date : 2011-01-06 This document defines a Media Control Channel Framework Package for managing mixers for media conferences and connections. The package defines request elements for managing conference mixers, managing mixers between conferences and/or connections, as well as associated responses and notifications. The package also defines elements for auditing package capabilities and mixers. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mediactrl-mixer-control-package-14.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-mediactrl-mixer-control-package-14.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2011-01-06055651.I-D@ietf.org> --NextPart-- From dworley@avaya.com Fri Jan 7 07:50:17 2011 Return-Path: X-Original-To: mediactrl@core3.amsl.com Delivered-To: mediactrl@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6C9C03A6912 for ; Fri, 7 Jan 2011 07:50:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.513 X-Spam-Level: X-Spam-Status: No, score=-102.513 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X-Vpk1o4qUul for ; Fri, 7 Jan 2011 07:50:16 -0800 (PST) Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 2F2653A6905 for ; Fri, 7 Jan 2011 07:50:15 -0800 (PST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAObFJk3GmAcF/2dsb2JhbACkKHOmBwKWG4VMBIRniVo X-IronPort-AV: E=Sophos;i="4.60,289,1291611600"; d="scan'208";a="258508655" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 07 Jan 2011 10:52:14 -0500 X-IronPort-AV: E=Sophos;i="4.60,289,1291611600"; d="scan'208";a="567595205" Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by co300216-co-erhwest-out.avaya.com with ESMTP; 07 Jan 2011 10:52:14 -0500 Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.90]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Fri, 7 Jan 2011 10:52:13 -0500 From: "Worley, Dale R (Dale)" To: "mediactrl@ietf.org" , Robert Sparks Date: Fri, 7 Jan 2011 10:51:40 -0500 Thread-Topic: RFC errata report on erratum 1994 to RFC 5552 (SIP Interface to VoiceXML Media Services) Thread-Index: AQHLroLZ9gfotw/lG0upxAEL6Ibh+A== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [MEDIACTRL] RFC errata report on erratum 1994 to RFC 5552 (SIP Interface to VoiceXML Media Services) X-BeenThere: mediactrl@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Control WG Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jan 2011 15:50:17 -0000 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RFC5552, "SIP Interface to VoiceXML Media Services" Source of RFC: mediactrl (rai) Errata ID: 1994 Status: Reported Type: Technical Reported By: Henry Lum Date Reported: 2010-01-04 Section 2.4 says: session.connection.redirect: This array is populated by information contained in the History-Info [RFC4244] header in the initial INVITE or is otherwise undefined. Each entry (hi-entry) in the History-Info header is mapped, in reverse order, into an element of the session.connection.redirect array. It should say: session.connection.redirect: This array is populated by information contained in the History-Info [RFC4244] header in the initial INVITE or is otherwise undefined. Each entry (hi-entry) in the History-Info header is mapped, in order appeared in the History-Info header, into an element of the session.connection.redirect array. Notes: The elements in the History info header is designed as a tree-like structure from the origination to the destination where each forwarding proxy appends to the end of the header and add an index. The original RFC text requires that the elements to be shown in VXML session.connection.redirect array in reverse order and this is incorrect based on the definition of session.connection.redirect. The first element in the array should be the original called number which maps to index=3D1 in history-info, and the last element should be the last redirected number which is the last element in history-info. ---------------------------------------------------------------------- Recommended status: (correct) Verified The definition of session.connection.redirect from the VXML 2.0 specification (http://www.w3.org/TR/2004/REC-voicexml20-20040316/) is: session.connection.redirect This variable is an array representing the connection redirection paths. The first element is the original called number, the last element is the last redirected number. Each element of the array contains a uri, pi (presentation information), si (screening information), and reason property. The reason property can be either "unknown", "user busy", "no reply", "deflection during alerting", "deflection immediate response", "mobile subscriber not reachable". As such, copying the History-Info values into session.connection.redirect in the same order is somewhat more correct, as the first History-Info value should be the original request-URI. But History-Info may contain other values other than the ones that are ancestral to the INVITE containing it, and assembling the correct redirection sequence may require some additional processing. Also, the definition of History-Info is being updated (draft-ietf-sipcore-rfc4244bis) to provide better recording of redirection sequences. Documenting how to extract the redirection sequence in a way that would work in all cases is a significant piece of work. Currently, the best straightforward specification is to map the elements in forward order: session.connection.redirect: This array is populated by information contained in the History-Info [RFC4244] header in the initial INVITE or is otherwise undefined. Entries (hi-entry) in the History-Info header are mapped, in order they appear in the History-Info header, into elements of the session.connection.redirect array. It appears that definitions of the component values of the array elements need amending as well: * uri - Set to the hi-targeted-to-uri value of the History-Info entry Strictly speaking, the hi-targeted-to-uri contains "header parameters", including "Reason" and "Privacy", which are not derived from the request-URI of the corresponding INVITE, and are not meaningful considered as part of that URI. So this definition should be "Set to the hi-targeted-to-uri value, without 'headers', of the History-Info entry" * si - Set to the value of the "si" parameter if it exists, undefined otherwise I can find no reference to the "si" value in VXML 2.0, RFC 4244, or in draft-ietf-sipcore-rfc4244bis-02 -- is this entry a mistake? Ironically, taken verbatim, this definition requires the "si" value to always be undefined, which is the same effect as if its definition were deleted from the RFC. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Dale From rjsparks@nostrum.com Tue Jan 11 08:02:43 2011 Return-Path: X-Original-To: mediactrl@core3.amsl.com Delivered-To: mediactrl@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 97B623A6A4E for ; Tue, 11 Jan 2011 08:02:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.567 X-Spam-Level: X-Spam-Status: No, score=-102.567 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Q-zR6TbHqst for ; Tue, 11 Jan 2011 08:02:42 -0800 (PST) Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 6E4743A6809 for ; Tue, 11 Jan 2011 08:02:42 -0800 (PST) Received: from dn3-177.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p0BG4wZE093229 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Tue, 11 Jan 2011 10:04:58 -0600 (CST) (envelope-from rjsparks@nostrum.com) From: Robert Sparks Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Tue, 11 Jan 2011 10:04:57 -0600 Message-Id: <08514691-9B12-4902-AF58-DD9364D52023@nostrum.com> To: mediactrl@ietf.org Mime-Version: 1.0 (Apple Message framework v1082) X-Mailer: Apple Mail (2.1082) Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism) Subject: [MEDIACTRL] Finishing the approval of -ivr-control-package X-BeenThere: mediactrl@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Control WG Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jan 2011 16:02:43 -0000 All - In the process of resolving the issues raised in IETF LC/IESG review of = draft-ietf-mediactrl-ivr-control-package, RFC4627 ("The application/json Media Type for JavaScript Object Notation = (JSON)") moved to a normative reference. BPC 97 (RFC 3967) allows this kind of reference (a "downref" = from a PS document to an Informational document), but requires that it be explicitly documented as part of an = IETF LC.=20 To wrap this up quickly and get this document into the RFC Editor queue, = I'll request a new (the 3rd) last call for=20 this document, focusing only on the downref. Watch for the announcement = of that LC shortly. RjS= From iesg-secretary@ietf.org Tue Jan 11 09:21:16 2011 Return-Path: X-Original-To: mediactrl@core3.amsl.com Delivered-To: mediactrl@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 02F4F3A6A5E; Tue, 11 Jan 2011 09:21:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.358 X-Spam-Level: X-Spam-Status: No, score=-102.358 tagged_above=-999 required=5 tests=[AWL=0.241, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q9lWw2tRj+mV; Tue, 11 Jan 2011 09:21:15 -0800 (PST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0B6B23A677E; Tue, 11 Jan 2011 09:21:15 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 3.10 Message-ID: <20110111172115.6719.55744.idtracker@localhost> Date: Tue, 11 Jan 2011 09:21:15 -0800 Cc: mediactrl@ietf.org Subject: [MEDIACTRL] Additional Last Call: (An Interactive Voice Response (IVR) Control Package for the Media Control Channel Framework) to Proposed Standard X-BeenThere: mediactrl@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Control WG Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jan 2011 17:21:16 -0000 The IESG has received a request from the Media Server Control WG (mediactrl) to consider the following document: - 'An Interactive Voice Response (IVR) Control Package for the Media Control Channel Framework' as a Proposed Standard Last calls were earlier issued on versions -08 and -09 of this document. As part of resolving comments from earlier IETF last calls and IESG review, the reference to RFC4627 ("The application/json Media Type for JavaScript Object Notation (JSON)") was made Normative introducing a downref (see BCP 97). This last call requests comments on whether this downward reference is appropriate in a standards track publication. The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2011-01-25. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-mediactrl-ivr-control-package/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-mediactrl-ivr-control-package/ No IPR declarations have been submitted directly on this I-D. From iesg-secretary@ietf.org Tue Jan 11 13:53:07 2011 Return-Path: X-Original-To: mediactrl@core3.amsl.com Delivered-To: mediactrl@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8D36D3A6AB2; Tue, 11 Jan 2011 13:53:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.486 X-Spam-Level: X-Spam-Status: No, score=-102.486 tagged_above=-999 required=5 tests=[AWL=0.113, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bEjaQFUa1qcN; Tue, 11 Jan 2011 13:53:06 -0800 (PST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 52A703A6AB1; Tue, 11 Jan 2011 13:53:05 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 3.10 Message-ID: <20110111215305.22580.17540.idtracker@localhost> Date: Tue, 11 Jan 2011 13:53:05 -0800 Cc: mediactrl mailing list , Internet Architecture Board , mediactrl chair , RFC Editor Subject: [MEDIACTRL] Protocol Action: 'A Mixer Control Package for the Media Control Channel Framework' to Proposed Standard (draft-ietf-mediactrl-mixer-control-package-14.txt) X-BeenThere: mediactrl@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Control WG Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jan 2011 21:53:07 -0000 The IESG has approved the following document: - 'A Mixer Control Package for the Media Control Channel Framework' (draft-ietf-mediactrl-mixer-control-package-14.txt) as a Proposed Standard This document is the product of the Media Server Control Working Group. The IESG contact persons are Robert Sparks and Gonzalo Camarillo. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-mediactrl-mixer-control-package/ Technical Summary This document defines a Media Control Channel Framework Package for managing mixers for media conferences and connections. The package defines request elements for managing conference mixers, managing mixers between conferences and/or connections, as well as associated responses and notifications. The package also defines elements for auditing package capabilities and mixers. Working Group Summary There was significant working group participation in the creation of this document and it has strong consensus Document Quality There are at least four independent implementations of the control package described by this document. This document has been stable for several versions, with small changes in each revision, discussed on the mailing list. Most of the recent changes have been suggested based on implementer experience. Shawn Emery performed an early sec-dir review at the request of the chairs. Type review for the media type defined in this document was requested June 18, 2009. Personnel Spencer Dawkins is the document shepherd. Robert Sparks is the responsible Area Director. RFC Editor Note In Section 4, 6th paragraph: OLD: Some elements in this control package contain attributes whose value is descriptive text primarily for diagnostic use. The implementation can indicated the language used in the descriptive text by means of a 'desclang' attribute ([RFC2277]). NEW: Some elements in this control package contain attributes whose value is descriptive text primarily for diagnostic use. The implementation can indicated the language used in the descriptive text by means of a 'desclang' attribute ([RFC5646],[RFC2277]). From dworley@avaya.com Wed Jan 19 19:06:22 2011 Return-Path: X-Original-To: mediactrl@core3.amsl.com Delivered-To: mediactrl@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A13E3A7085 for ; Wed, 19 Jan 2011 19:06:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.534 X-Spam-Level: X-Spam-Status: No, score=-102.534 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hDs83pfqX8Ly for ; Wed, 19 Jan 2011 19:06:20 -0800 (PST) Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 3280F3A7080 for ; Wed, 19 Jan 2011 19:06:19 -0800 (PST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAJI2N02HCzI1/2dsb2JhbACkSnOkNwKYVYVQBIRviW4 X-IronPort-AV: E=Sophos;i="4.60,347,1291611600"; d="scan'208";a="228367054" Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 19 Jan 2011 22:08:59 -0500 X-IronPort-AV: E=Sophos;i="4.60,347,1291611600"; d="scan'208";a="586135602" Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 19 Jan 2011 22:08:58 -0500 Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.215]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Wed, 19 Jan 2011 22:08:58 -0500 From: "Worley, Dale R (Dale)" To: "mediactrl@ietf.org" , Robert Sparks Date: Wed, 19 Jan 2011 22:08:18 -0500 Thread-Topic: Revised RFC errata report on erratum 1994 to RFC 5552 (SIP Interface to VoiceXML Media Services) Thread-Index: AQHLuE9gqGTu8rbdmkKjlG+EA8GN3Q== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [MEDIACTRL] Revised RFC errata report on erratum 1994 to RFC 5552 (SIP Interface to VoiceXML Media Services) X-BeenThere: mediactrl@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Control WG Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2011 03:06:22 -0000 This revision incorporates Mark Scott's suggestion of 4 Jan 2010. This revision removes discussion of the "uri" and "si" values, which will be handled elsewhere. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RFC5552, "SIP Interface to VoiceXML Media Services" Source of RFC: mediactrl (rai) Errata ID: 1994 Status: Reported Type: Technical Reported By: Henry Lum Date Reported: 2010-01-04 Section 2.4 says: session.connection.redirect: This array is populated by information contained in the History-Info [RFC4244] header in the initial INVITE or is otherwise undefined. Each entry (hi-entry) in the History-Info header is mapped, in reverse order, into an element of the session.connection.redirect array. It should say: session.connection.redirect: This array is populated by information contained in the History-Info [RFC4244] header in the initial INVITE or is otherwise undefined. Each entry (hi-entry) in the History-Info header is mapped, in order appeared in the History-Info header, into an element of the session.connection.redirect array. Notes: The elements in the History info header is designed as a tree-like structure from the origination to the destination where each forwarding proxy appends to the end of the header and add an index. The original RFC text requires that the elements to be shown in VXML session.connection.redirect array in reverse order and this is incorrect based on the definition of session.connection.redirect. The first element in the array should be the original called number which maps to index=3D1 in history-info, and the last element should be the last redirected number which is the last element in history-info. ---------------------------------------------------------------------- Recommended status: (correct) Verified The definition of session.connection.redirect from the VXML 2.0 specification (http://www.w3.org/TR/2004/REC-voicexml20-20040316/) is: session.connection.redirect This variable is an array representing the connection redirection paths. The first element is the original called number, the last element is the last redirected number. Each element of the array contains a uri, pi (presentation information), si (screening information), and reason property. The reason property can be either "unknown", "user busy", "no reply", "deflection during alerting", "deflection immediate response", "mobile subscriber not reachable". As such, copying the History-Info values into session.connection.redirect in the same order is somewhat more correct, as the first History-Info value should be the original request-URI. But History-Info may contain other values other than the ones that are ancestral to the INVITE containing it, and assembling the correct redirection sequence may require some additional processing. Also, the definition of History-Info is being updated (draft-ietf-sipcore-rfc4244bis) to provide better recording of redirection sequences. Documenting how to extract the redirection sequence in a way that would work in all cases is a significant piece of work. Currently, the best straightforward specification is to map the elements in forward order: session.connection.redirect: This array is populated by information contained in the History-Info [RFC4244] header in the initial INVITE or is otherwise undefined. Each entry (hi-entry) in the History-Info header is mapped, in order, into an element of the session.connection.redirect array. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Dale From dworley@avaya.com Wed Jan 19 19:10:55 2011 Return-Path: X-Original-To: mediactrl@core3.amsl.com Delivered-To: mediactrl@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 21DCB3A708B for ; Wed, 19 Jan 2011 19:10:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.535 X-Spam-Level: X-Spam-Status: No, score=-102.535 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id idUOi70RhePv for ; Wed, 19 Jan 2011 19:10:54 -0800 (PST) Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (nj300815-nj-outbound.net.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id A6C053A7089 for ; Wed, 19 Jan 2011 19:10:53 -0800 (PST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAII3N03GmAcF/2dsb2JhbACkSnOkPgKYVYVQBIRviW4 X-IronPort-AV: E=Sophos;i="4.60,347,1291611600"; d="scan'208";a="55153458" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 19 Jan 2011 22:13:19 -0500 X-IronPort-AV: E=Sophos;i="4.60,347,1291611600"; d="scan'208";a="572918127" Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by co300216-co-erhwest-out.avaya.com with ESMTP; 19 Jan 2011 22:13:19 -0500 Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.215]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Wed, 19 Jan 2011 22:13:18 -0500 From: "Worley, Dale R (Dale)" To: "mediactrl@ietf.org" Date: Wed, 19 Jan 2011 22:12:35 -0500 Thread-Topic: Weird stuff in RFC 5552 Thread-Index: AQHLuE/7mxHARwv4XU23rRG0rNUwjw== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [MEDIACTRL] Weird stuff in RFC 5552 X-BeenThere: mediactrl@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Control WG Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2011 03:10:55 -0000 Looking at an erratum to RFC 5552 ("SIP Interface to VoiceXML Media Services"), I ran into the following oddities in the definition of the following two componets of the elements of the session.connection.redirect array: * uri - Set to the hi-targeted-to-uri value of the History-Info entry This is badly phrased: Strictly speaking, the hi-targeted-to-uri contains "header parameters", including "Reason" and "Privacy", which are not derived from the request-URI of the corresponding INVITE, and are not meaningful considered as part of that URI. So this definition should be "Set to the hi-targeted-to-uri value, without 'headers', of the History-Info entry" * si - Set to the value of the "si" parameter if it exists, undefined otherwise I can find no reference to the "si" value in VXML 2.0, RFC 4244, or in draft-ietf-sipcore-rfc4244bis-02 -- is this entry a mistake? Ironically, taken verbatim, this definition requires the "si" value to always be undefined, which is the same effect as if its definition were deleted from the RFC. What do people think of this? Should these be fixed by an erratum? What was really meant? Dale From Henry.Lum@alcatel-lucent.com Mon Jan 24 07:54:22 2011 Return-Path: X-Original-To: mediactrl@core3.amsl.com Delivered-To: mediactrl@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C17133A6AF8 for ; Mon, 24 Jan 2011 07:54:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.084 X-Spam-Level: X-Spam-Status: No, score=-6.084 tagged_above=-999 required=5 tests=[AWL=0.515, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3GmzISJF7ftu for ; Mon, 24 Jan 2011 07:54:21 -0800 (PST) Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id 542FD3A6AC3 for ; Mon, 24 Jan 2011 07:54:21 -0800 (PST) Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id p0OFv8B1008494 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 24 Jan 2011 09:57:09 -0600 (CST) Received: from relay-out1.wc.genesyslab.com (relay-out1.wc.genesyslab.com [172.22.70.114]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p0OFv7ZC011116 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 24 Jan 2011 09:57:08 -0600 Received: from g2.genesyslab.com (g2.genesyslab.com [192.168.20.138]) by relay-out1.wc.genesyslab.com (8.13.8+Sun/8.13.8) with ESMTP id p0OFv65e006388; Mon, 24 Jan 2011 07:57:06 -0800 (PST) Received: from NAHALD.us.int.genesyslab.com ([192.168.20.92]) by g2.genesyslab.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 24 Jan 2011 07:57:06 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 24 Jan 2011 07:57:05 -0800 Message-ID: <059AF07365DC474393A19A3AF187DF7406989992@NAHALD.us.int.genesyslab.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [MEDIACTRL] Weird stuff in RFC 5552 Thread-Index: AQHLuE/7mxHARwv4XU23rRG0rNUwj5PgTPXw References: From: "Henry Lum" To: "Worley, Dale R (Dale)" , X-OriginalArrivalTime: 24 Jan 2011 15:57:06.0931 (UTC) FILETIME=[59D34430:01CBBBDF] X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39 X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12 Subject: Re: [MEDIACTRL] Weird stuff in RFC 5552 X-BeenThere: mediactrl@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Control WG Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2011 15:54:22 -0000 VXML2 does define a si (screening indicator) property in each element in the session.connection.redirect. But you are correct that RFC4244 makes no reference to screening indicator at all for Histroy-Info header so our implementation ends up always setting it to undefined. Regards, Henry > -----Original Message----- > From: mediactrl-bounces@ietf.org [mailto:mediactrl-bounces@ietf.org] On > Behalf Of Worley, Dale R (Dale) > Sent: Wednesday, January 19, 2011 10:13 PM > To: mediactrl@ietf.org > Subject: [MEDIACTRL] Weird stuff in RFC 5552 >=20 > Looking at an erratum to RFC 5552 ("SIP Interface to VoiceXML Media > Services"), I ran into the following oddities in the definition of the > following two componets of the elements of the > session.connection.redirect array: >=20 > * uri - Set to the hi-targeted-to-uri value of the History-Info > entry >=20 > This is badly phrased: Strictly speaking, the hi-targeted-to-uri > contains "header parameters", including "Reason" and "Privacy", which > are not derived from the request-URI of the corresponding INVITE, and > are not meaningful considered as part of that URI. So this definition > should be "Set to the hi-targeted-to-uri value, without 'headers', of > the History-Info entry" >=20 > * si - Set to the value of the "si" parameter if it exists, > undefined otherwise >=20 > I can find no reference to the "si" value in VXML 2.0, RFC 4244, or in > draft-ietf-sipcore-rfc4244bis-02 -- is this entry a mistake? > Ironically, taken verbatim, this definition requires the "si" value to > always be undefined, which is the same effect as if its definition > were deleted from the RFC. >=20 > What do people think of this? Should these be fixed by an erratum? > What was really meant? >=20 > Dale > _______________________________________________ > MEDIACTRL mailing list > MEDIACTRL@ietf.org > https://www.ietf.org/mailman/listinfo/mediactrl > Supplemental Web Site: > http://www.standardstrack.com/ietf/mediactrl =09 -------------------------------------------------------------------------= ------------------------------------------ CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain co= nfidential and proprietary information of Alcatel-Lucent and/or its affil= iated entities. Access by the intended recipient only is authorized. Any = liability arising from any party acting, or refraining from acting, on an= y information contained in this e-mail is hereby excluded. If you are not= the intended recipient, please notify the sender immediately, destroy th= e original transmission and its attachments and do not disclose the conte= nts to any other person, use it for any purpose, or store or copy the inf= ormation in any medium. Copyright in this e-mail and any attachments belo= ngs to Alcatel-Lucent and/or its affiliated entities. =09 From iesg-secretary@ietf.org Tue Jan 25 09:04:10 2011 Return-Path: X-Original-To: mediactrl@core3.amsl.com Delivered-To: mediactrl@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CF4E93A6817; Tue, 25 Jan 2011 09:04:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ix7sD4IbnQNY; Tue, 25 Jan 2011 09:04:10 -0800 (PST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5F2733A6839; Tue, 25 Jan 2011 09:04:09 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 3.10 Message-ID: <20110125170409.553.41463.idtracker@localhost> Date: Tue, 25 Jan 2011 09:04:09 -0800 Cc: mediactrl mailing list , Internet Architecture Board , mediactrl chair , RFC Editor Subject: [MEDIACTRL] Protocol Action: 'An Interactive Voice Response (IVR) Control Package for the Media Control Channel Framework' to Proposed Standard (draft-ietf-mediactrl-ivr-control-package-11.txt) X-BeenThere: mediactrl@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Control WG Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2011 17:04:10 -0000 The IESG has approved the following document: - 'An Interactive Voice Response (IVR) Control Package for the Media Control Channel Framework' (draft-ietf-mediactrl-ivr-control-package-11.txt) as a Proposed Standard This document is the product of the Media Server Control Working Group. The IESG contact persons are Robert Sparks and Gonzalo Camarillo. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-mediactrl-ivr-control-package/ Technical Summary This document defines a Media Control Channel Framework Package for Interactive Voice Response (IVR) dialog interaction on media connections and conferences. The package defines dialog management request elements for preparing, starting and terminating dialog interactions, as well as associated responses and notifications. Dialog interactions are specified in a dialog language. This package defines a lightweight IVR dialog language (supporting prompt playback, runtime controls, DTMF collect and media recording) and allows other dialog languages to be used. The package also defines elements for auditing package capabilities and IVR dialogs. Working Group Summary There was significant working group participation in the creation of this document and it represents a strong consensus. Document Quality There are at least four independent implementations of the control package described by this document. This document has been stable for several versions, with small changes in each revision, discussed on the mailing list. Most of the recent changes have been suggested based on implementer experience. Type review for the media types defined in this document was requested June 18, 2009. The document has had RAI expert review (by Ben Campbell) and early SECDIR review (by Donald Eastlake). Personnel Spencer Dawkins is the Document Shepherd. Robert Sparks is the responsible Area Director. RFC Editor Note In Section 4, 7th paragraph: OLD: Some elements in this control package contain attributes whose value is descriptive text primarily for diagnostic use. The implementation can indicated the language used in the descriptive text by means of a 'desclang' attribute ([RFC2277]). NEW: Some elements in this control package contain attributes whose value is descriptive text primarily for diagnostic use. The implementation can indicated the language used in the descriptive text by means of a 'desclang' attribute ([RFC5646],[RFC2277]). From dworley@avaya.com Tue Jan 25 13:14:14 2011 Return-Path: X-Original-To: mediactrl@core3.amsl.com Delivered-To: mediactrl@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B9FCD3A68C6 for ; Tue, 25 Jan 2011 13:14:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.539 X-Spam-Level: X-Spam-Status: No, score=-102.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gHn5htYqoM0m for ; Tue, 25 Jan 2011 13:14:14 -0800 (PST) Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id EA63A3A68AD for ; Tue, 25 Jan 2011 13:14:13 -0800 (PST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAF7MPk3GmAcF/2dsb2JhbACkcXOjfQKZEYVPBIUXinI X-IronPort-AV: E=Sophos;i="4.60,376,1291611600"; d="scan'208";a="261439799" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 25 Jan 2011 16:17:12 -0500 X-IronPort-AV: E=Sophos;i="4.60,376,1291611600"; d="scan'208";a="574717519" Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by co300216-co-erhwest-out.avaya.com with ESMTP; 25 Jan 2011 16:17:12 -0500 Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.215]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Tue, 25 Jan 2011 16:17:11 -0500 From: "Worley, Dale R (Dale)" To: Henry Lum , "mediactrl@ietf.org" Date: Tue, 25 Jan 2011 16:16:48 -0500 Thread-Topic: [MEDIACTRL] Weird stuff in RFC 5552 Thread-Index: AQHLuE/7mxHARwv4XU23rRG0rNUwj5PgTPXwgAHsxX8= Message-ID: References: , <059AF07365DC474393A19A3AF187DF7406989992@NAHALD.us.int.genesyslab.com> In-Reply-To: <059AF07365DC474393A19A3AF187DF7406989992@NAHALD.us.int.genesyslab.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [MEDIACTRL] Weird stuff in RFC 5552 X-BeenThere: mediactrl@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Control WG Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2011 21:14:14 -0000 > From: Henry Lum >=20 > VXML2 does define a si (screening indicator) property in each element in > the session.connection.redirect. But you are correct that RFC4244 makes > no reference to screening indicator at all for Histroy-Info header so > our implementation ends up always setting it to undefined. Assuming that the "screening indicator" is intended to prevent the recipient from knowing the origin, the "si" properties should be driven by the "Privacy" headers encoded into the History-Info. Dale From keith.drage@alcatel-lucent.com Wed Jan 26 02:06:31 2011 Return-Path: X-Original-To: mediactrl@core3.amsl.com Delivered-To: mediactrl@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E05C03A6971 for ; Wed, 26 Jan 2011 02:06:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.606 X-Spam-Level: X-Spam-Status: No, score=-105.606 tagged_above=-999 required=5 tests=[AWL=0.643, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iDUa9mBK-0cd for ; Wed, 26 Jan 2011 02:06:31 -0800 (PST) Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by core3.amsl.com (Postfix) with ESMTP id D50433A63EB for ; Wed, 26 Jan 2011 02:06:30 -0800 (PST) Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id p0QA9AVY013627 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 26 Jan 2011 11:09:23 +0100 Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Wed, 26 Jan 2011 11:09:02 +0100 From: "DRAGE, Keith (Keith)" To: "Worley, Dale R (Dale)" , "LUM, Henry (Henry)" , "mediactrl@ietf.org" Date: Wed, 26 Jan 2011 11:09:01 +0100 Thread-Topic: [MEDIACTRL] Weird stuff in RFC 5552 Thread-Index: AQHLuE/7mxHARwv4XU23rRG0rNUwj5PgTPXwgAHsxX+AANSTUA== Message-ID: References: , <059AF07365DC474393A19A3AF187DF7406989992@NAHALD.us.int.genesyslab.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80 Subject: Re: [MEDIACTRL] Weird stuff in RFC 5552 X-BeenThere: mediactrl@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Control WG Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jan 2011 10:06:32 -0000 Screening indicators, as defined in the ISDN, are nothing whatsoever to do = with privacy. Keith -----Original Message----- From: mediactrl-bounces@ietf.org [mailto:mediactrl-bounces@ietf.org] On Beh= alf Of Worley, Dale R (Dale) Sent: 25 January 2011 21:17 To: LUM, Henry (Henry); mediactrl@ietf.org Subject: Re: [MEDIACTRL] Weird stuff in RFC 5552 > From: Henry Lum >=20 > VXML2 does define a si (screening indicator) property in each element in > the session.connection.redirect. But you are correct that RFC4244 makes > no reference to screening indicator at all for Histroy-Info header so > our implementation ends up always setting it to undefined. Assuming that the "screening indicator" is intended to prevent the recipient from knowing the origin, the "si" properties should be driven by the "Privacy" headers encoded into the History-Info. Dale _______________________________________________ MEDIACTRL mailing list MEDIACTRL@ietf.org https://www.ietf.org/mailman/listinfo/mediactrl Supplemental Web Site: http://www.standardstrack.com/ietf/mediactrl From Mark.Scott@alcatel-lucent.com Wed Jan 26 07:00:16 2011 Return-Path: X-Original-To: mediactrl@core3.amsl.com Delivered-To: mediactrl@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B91363A67C0 for ; Wed, 26 Jan 2011 07:00:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fNoFARR5dntk for ; Wed, 26 Jan 2011 07:00:15 -0800 (PST) Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id 8E4D13A67AE for ; Wed, 26 Jan 2011 07:00:15 -0800 (PST) Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id p0QF2nuA002917 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 26 Jan 2011 09:02:49 -0600 (CST) Received: from relay-out2.dc (relay-out2.dc.genesyslab.com [172.22.68.188]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p0QF2gNl012188 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 26 Jan 2011 09:02:44 -0600 Received: from g2.genesyslab.com (g2.genesyslab.com [192.168.20.138]) by relay-out2.dc (8.13.8+Sun/8.13.8) with ESMTP id p0QF2eKh027465; Wed, 26 Jan 2011 07:02:41 -0800 (PST) Received: from SARUMAN.us.int.genesyslab.com ([192.168.20.90]) by g2.genesyslab.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 26 Jan 2011 07:02:40 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 26 Jan 2011 07:02:40 -0800 Message-ID: In-Reply-To: <46D1E17C154D3D489BB916C274FAFF37046E5E35DA@SARUMAN.us.int.genesyslab.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Technical Errata Reported] RFC5552 (1994) Thread-Index: AcqNYeRfgrPUjrt0RQWa+YPoa3HREAAAxmLATAE+2pA= References: <201001041716.o04HGdG8006219@boreas.isi.edu> <46D1E17C154D3D489BB916C274FAFF37046E5E35DA@SARUMAN.us.int.genesyslab.com> From: "Mark Scott" To: "RFC Errata System" , , , , , X-OriginalArrivalTime: 26 Jan 2011 15:02:40.0553 (UTC) FILETIME=[13BD0990:01CBBD6A] X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33 X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11 Cc: Henry Lum , mediactrl@ietf.org Subject: Re: [MEDIACTRL] [Technical Errata Reported] RFC5552 (1994) X-BeenThere: mediactrl@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Control WG Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jan 2011 15:00:16 -0000 Hi Everyone, I'm resending this mail of more than a year ago, as Robert Sparks was kind enough to point out in a review that it seemed likely that the list members had actually not received it! Regards, Mark. -----Original Message----- From: Mark Scott=20 Sent: Monday, January 04, 2010 12:43 PM To: RFC Errata System; daveburke@google.com; rjsparks@nostrum.com; fluffy@cisco.com; eburger@standardstrack.com; spencer@wonderhamster.org Cc: Henry Lum; mediactrl@ietf.org Subject: RE: [Technical Errata Reported] RFC5552 (1994) I agree that the correction is valid, although I would make a slight grammatical change to the correct text, as follows: Corrected Text -------------- session.connection.redirect: This array is populated by information contained in the History-Info [RFC4244] header in the initial INVITE or is otherwise undefined. Each entry (hi-entry) in the History-Info header is mapped, in order, into an element of the=20 session.connection.redirect array. Regards, Mark. -----Original Message----- From: RFC Errata System [mailto:rfc-editor@rfc-editor.org]=20 Sent: January-04-10 12:17 PM To: daveburke@google.com; Mark Scott; rjsparks@nostrum.com; fluffy@cisco.com; eburger@standardstrack.com; spencer@wonderhamster.org Cc: Henry Lum; mediactrl@ietf.org; rfc-editor@rfc-editor.org Subject: [Technical Errata Reported] RFC5552 (1994) The following errata report has been submitted for RFC5552, "SIP Interface to VoiceXML Media Services". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=3D5552&eid=3D1994 -------------------------------------- Type: Technical Reported by: Henry Lum Section: 2.4 Original Text ------------- session.connection.redirect: This array is populated by information contained in the History-Info [RFC4244] header in the initial INVITE or is otherwise undefined. Each entry (hi-entry) in the History-Info header is mapped, in reverse order, into an element of the session.connection.redirect array. Corrected Text -------------- session.connection.redirect: This array is populated by information contained in the History-Info [RFC4244] header in the initial INVITE or is otherwise undefined. Each entry (hi-entry) in the History-Info header is mapped, in order appeared in the History-Info header, into an element of the session.connection.redirect array. Notes ----- The elements in the History info header is designed as a tree-like structure from the origination to the destination where each forwarding proxy appends to the end of the header and add an index. The original RFC text requires that the elements to be shown in VXML session.connection.redirect array in reverse order and this is incorrect based on the definition of session.connection.redirect. The first element in the array should be the original called number which maps to index=3D1 in history-info, and the last element should be the last redirected number which is the last element in history-info. Instructions: ------------- This errata is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary.=20 -------------------------------------- RFC5552 (draft-ietf-mediactrl-vxml-04) -------------------------------------- Title : SIP Interface to VoiceXML Media Services Publication Date : May 2009 Author(s) : D. Burke, M. Scott Category : PROPOSED STANDARD Source : Media Server Control Area : Real-time Applications and Infrastructure Stream : IETF Verifying Party : IESG =09 -------------------------------------------------------------------------= ------------------------------------------ CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain co= nfidential and proprietary information of Alcatel-Lucent and/or its affil= iated entities. Access by the intended recipient only is authorized. Any = liability arising from any party acting, or refraining from acting, on an= y information contained in this e-mail is hereby excluded. If you are not= the intended recipient, please notify the sender immediately, destroy th= e original transmission and its attachments and do not disclose the conte= nts to any other person, use it for any purpose, or store or copy the inf= ormation in any medium. Copyright in this e-mail and any attachments belo= ngs to Alcatel-Lucent and/or its affiliated entities. =09