Re: [MEDIACTRL] ISSUE 3 - IVR Package - <variable>/<variabletype> interoperability

Victor Paulsamy <vpaulsamy@ditechnetworks.com> Thu, 07 October 2010 20:13 UTC

Return-Path: <vpaulsamy@ditechnetworks.com>
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 EB9583A6FE1 for <mediactrl@core3.amsl.com>; Thu, 7 Oct 2010 13:13:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.976
X-Spam-Level:
X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 hskYhvH33cCa for <mediactrl@core3.amsl.com>; Thu, 7 Oct 2010 13:13:09 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id 0F1793A6E6A for <mediactrl@ietf.org>; Thu, 7 Oct 2010 13:13:08 -0700 (PDT)
Received: by ewy21 with SMTP id 21so216064ewy.31 for <mediactrl@ietf.org>; Thu, 07 Oct 2010 13:14:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.213.17.199 with SMTP id t7mr837322eba.90.1286482450469; Thu, 07 Oct 2010 13:14:10 -0700 (PDT)
Received: by 10.213.28.73 with HTTP; Thu, 7 Oct 2010 13:14:10 -0700 (PDT)
In-Reply-To: <C8D3601A.9394%Scott.McGlashan@hp.com>
References: <C8D3601A.9394%Scott.McGlashan@hp.com>
Date: Fri, 8 Oct 2010 03:14:10 +0700
Message-ID: <AANLkTikUAn3L6sxs+O5dFrtPNOOUMeTxCRfw+0TcPSW3@mail.gmail.com>
From: Victor Paulsamy <vpaulsamy@ditechnetworks.com>
To: "McGlashan, Scott" <scott.mcglashan@hp.com>
Content-Type: multipart/alternative; boundary=0015174c12aa7852e204920c89dc
Cc: "Alexey@core3.amsl.com" <Alexey@core3.amsl.com>, "mediactrl-chairs@tools.ietf.org" <mediactrl-chairs@tools.ietf.org>, "draft-ietf-mediactrl-ivr-control-package@tools.ietf.org" <draft-ietf-mediactrl-ivr-control-package@tools.ietf.org>, "mediactrl@ietf.org" <mediactrl@ietf.org>, "stpeter@stpeter.im" <stpeter@stpeter.im>, Melnikov <alexey.melnikov@isode.com>
Subject: Re: [MEDIACTRL] ISSUE 3 - IVR Package - <variable>/<variabletype> interoperability
X-BeenThere: mediactrl@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Control WG Discussion List <mediactrl.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mediactrl>, <mailto:mediactrl-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mediactrl>
List-Post: <mailto:mediactrl@ietf.org>
List-Help: <mailto:mediactrl-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mediactrl>, <mailto:mediactrl-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Oct 2010 20:13:11 -0000

I like to see option # 2 as well.

--victor

On Thu, Oct 7, 2010 at 4:31 PM, McGlashan, Scott <scott.mcglashan@hp.com>wrote:

> Hi All,
>
> As part of our IESG review of the IVR package the following issues have
> been identified:
>
> (a) 4.3.1.1.1.  <variable>
>
>   A <variable> element has the following attributes:
>
>   value:  specifies the string to be rendered.  A valid value is a
>      string (see Section 4.6.6).  The attribute is mandatory.
>
>   type:  specifies the type to use for rendering.  A valid value is a
>      string (see Section 4.6.6).  The attribute is mandatory.
>
>   format:  specifies format information to use in conjunction with the
>      type for the rendering.  A valid value is a string (see
>      Section 4.6.6).  The attribute is optional.  There is no default
>      value.
>
>  Are these defined somewhere in more details?
>
>   For example, the MS could support <variable> type/format combinations
>   such as:
>
>  Is this the complete list?
>
>
> (b) Please clarify how implementations will achieve interoperability with
> regard to the <variable> element, given that there are no registries or
> specification for the 'type' and 'format' attributes. This applies also to
> the <variabletype> element.
>
>
> We need some input from the mailing list on how we should proceed with this
> one: some options
>
> 1. Strengthen our descriptions of date, time and digits format/types. Limit
> interoperability requirements to these 3 types.
>
> 2. As 1), but introduce registry for adding additional types.
>
> 3. Delete the <variable> and <variabletype> elements.
>
>
> I would like WG input on these options. My preference is for option 2 (or
> option 1 as 2nd choice).
>
> Thanks
>
> Scott
>
>
> _______________________________________________
> MEDIACTRL mailing list
> MEDIACTRL@ietf.org
> https://www.ietf.org/mailman/listinfo/mediactrl
> Supplemental Web Site:
> http://www.standardstrack.com/ietf/mediactrl
>