Re: [MEDIACTRL] Fwd: Alexey Melnikov's DISCUSS and COMMENT on draft-ietf-mediactrl-ivr-control-package-09

Eric Burger <eburger@standardstrack.com> Fri, 24 December 2010 11:10 UTC

Return-Path: <eburger@standardstrack.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 C98903A6939 for <mediactrl@core3.amsl.com>; Fri, 24 Dec 2010 03:10:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.803
X-Spam-Level:
X-Spam-Status: No, score=-101.803 tagged_above=-999 required=5 tests=[AWL=0.196, BAYES_00=-2.599, J_CHICKENPOX_34=0.6, 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 cVXB97tOSmhC for <mediactrl@core3.amsl.com>; Fri, 24 Dec 2010 03:10:44 -0800 (PST)
Received: from gs19.inmotionhosting.com (gs19.inmotionhosting.com [205.134.249.249]) by core3.amsl.com (Postfix) with ESMTP id AB1753A6927 for <mediactrl@ietf.org>; Fri, 24 Dec 2010 03:10:42 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com; h=Received:From:Mime-Version:Content-Type:Subject:Date:In-Reply-To:To:References:Message-Id:X-Mailer; b=dmQqTpURsTn4g9xc3vyAdqHGD21PlaYXZxdz7UXqaLpKRshniYSNkyD+4AK/s4m61KFuHxBihy++5XahxZy8JBy4j3xUx8JPBMa5PwLs0MxjhQCir1vUG1wmOK4qBBvk;
Received: from cpe-74-76-80-238.nycap.res.rr.com ([74.76.80.238] helo=[192.168.0.194]) by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1PW5YW-0001SI-GJ for mediactrl@ietf.org; Fri, 24 Dec 2010 03:11:29 -0800
From: Eric Burger <eburger@standardstrack.com>
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/signed; boundary="Apple-Mail-13--798124784"; protocol="application/pkcs7-signature"; micalg="sha1"
Date: Fri, 24 Dec 2010 06:12:51 -0500
In-Reply-To: <8DB220C0-4005-403D-AA80-79AB24855EA3@standardstrack.com>
To: mediactrl@ietf.org
References: <20101127180455.25998.5596.idtracker@localhost> <DC2CE305-8824-4074-96E9-8073F9428B7F@standardstrack.com> <EDC0A1AE77C57744B664A310A0B23AE21E2F347F@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <2FB20740-0036-4DA2-BF0E-71F5FA8BE514@standardstrack.com> <8DB220C0-4005-403D-AA80-79AB24855EA3@standardstrack.com>
Message-Id: <4591E136-9D8E-4C23-9BB1-934491E7DF81@standardstrack.com>
X-Mailer: Apple Mail (2.1082)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
Subject: Re: [MEDIACTRL] Fwd: Alexey Melnikov's DISCUSS and COMMENT on draft-ietf-mediactrl-ivr-control-package-09
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: Fri, 24 Dec 2010 11:10:47 -0000

Works for me. Any dissent?

On Dec 7, 2010, at 12:14 PM, Eric Burger wrote:

> Hello team...
> 
> On Dec 2, 2010, at 6:39 AM, Eric Burger wrote:
> 
>> Agreed. 
>> 
>> Any other comments on Alexey's comments? Come on folks, we are almost DONE!!!!
>> 
>> 
>> On Nov 28, 2010, at 4:59 PM, DRAGE, Keith (Keith) wrote:
>> 
>>> 10) In 9 (previously Appendix A/Section 12):
>>> 
>>> This section and its subsections are normative for somebody who chooses
>>> to implement VoiceXML as a dialog language. This in its turn means that
>>> the following references:
>>> 
>>> [RFC4627]  Crockford, D., "The application/json Media Type for
>>>           JavaScript Object Notation (JSON)", RFC 4627, July 2006.
>>> 
>>> [VXML30]   McGlashan, S., Auburn, RJ., Baggia, P., Barnett, J.,
>>>           Bodell, M., Burnett, D., Carter, J., Oshry, M., Rehor, K.,
>>>           Young, M., and R. Hosn, "Voice Extensible Markup Language
>>>           (VoiceXML) Version 3.0", W3C Working Draft, December 2008.
>>> 
>>> are Normative (they are currently Informative).
>>> This sounds to me like the text making the references needs to be redrafted, rather than making the references normative.
>>> 
>>> Surely this sort of thing is more example of how one might use the control package in a particular way to implement some things.
>>> 
>>> Keith
>>> 
>>> From: mediactrl-bounces@ietf.org [mailto:mediactrl-bounces@ietf.org] On Behalf Of Eric Burger
>>> Sent: Saturday, November 27, 2010 6:32 PM
>>> To: mediactrl@ietf.org
>>> Subject: [MEDIACTRL] Fwd: Alexey Melnikov's DISCUSS and COMMENT on draft-ietf-mediactrl-ivr-control-package-09
>>> 
>>> 
>>> 
>>> Begin forwarded message:
>>> 
>>> ----------------------------------------------------------------------
>>> DISCUSS:
>>> ----------------------------------------------------------------------
>>> 
>>> I think the document is in a pretty good shape despite the length of my comments.
>>> 
>>> Below are some blocking comments that need to be discussed and possibly addressed before I can recommend approval of this document:
>>> 
>>> 2) Use of authentication information in URIs in the "src" attribute (in multiple sectons):
>>> 
>>> E.g. in Section 4.2.1:
>>> 
>>> src:  specifies the location of an external dialog document to
>>>   prepare.  A valid value is a URI (see Section 4.6.9) including
>>>   authentication information if defined by the URI scheme (e.g.
>>>   basic access authentication in HTTP).
>>> 
>>> Is this supposed to include the password as well?
>>> If yes, how can this be represented in URIs?
>>> If not, where is this information coming from?
>>> 
>>> 8) In 4.6.10:
>>> 
>>> A string formated as a IANA MIME media type ([MIME.mediatypes]).
>>> 
>>> The latest version is an improvement, but I think you are missing parameter values in the ABNF ("=" value),
>>> where "value" is defined in RFC 2045.
>>> 
>>> 9) In 4.3.1.4:
>>> 
>>> append:  indicates whether recorded data is appended or not to a
>>>   recording location if a resource already exists.  A valid value is
>>>   a boolean (see Section 4.6.1).  A value of true indicates that
>>>   recorded data is appended to the existing resource at a recording
>>>   location.  A value of false indicates that recorded data is to
>>>   overwrite the existing resource.  The attribute is optional.  The
>>>   default value is false.
>>> 
>>> How is append/overwrite mapped to underlying protocol being used?
>>> In particular, I think this is underspecified in case of HTTP.
>>> 
>>> 10) In 9 (previously Appendix A/Section 12):
>>> 
>>> This section and its subsections are normative for somebody who chooses
>>> to implement VoiceXML as a dialog language. This in its turn means that
>>> the following references:
>>> 
>>> [RFC4627]  Crockford, D., "The application/json Media Type for
>>>           JavaScript Object Notation (JSON)", RFC 4627, July 2006.
>>> 
>>> [VXML30]   McGlashan, S., Auburn, RJ., Baggia, P., Barnett, J.,
>>>           Bodell, M., Burnett, D., Carter, J., Oshry, M., Rehor, K.,
>>>           Young, M., and R. Hosn, "Voice Extensible Markup Language
>>>           (VoiceXML) Version 3.0", W3C Working Draft, December 2008.
>>> 
>>> are Normative (they are currently Informative).
>>> 
>>> 11) BCP 18 (RFC 2277) requires that any human readable text is explicitly or implicitly tagged with a language tag. This affects the following fields in your document:
>>> 
>>> 4.2.4.  <response>
>>> 
>>> reason:  string specifying a reason for the response status.  The
>>>   attribute is optional.  There is no default value.
>>> 
>>> 4.2.5.1.  <dialogexit>
>>> 
>>> 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
>>>   value is a string (see Section 4.6.6).  The attribute is optional.
>>>   There is no default value.
>>> 
>>> 4.4.2.  <auditresponse>
>>> 
>>> reason:  string specifying a reason for the status.  The attribute is
>>>   optional.
>>> 
>>> 4.4.2.2.5.1.  <variabletype>
>>> 
>>> desc:  a string providing some textual description of the type and
>>>   format.  The attribute is optional.
>>> 
>>> Language tagging is missing here
>>> 
>>> <format>:  element with a desc attribute (optional description)
>>> 
>>> As above
>>> 
>>>   and a content model describing a supported format in the <variable>
>>>   format attribute.  The element is optional.
>>> 
>>> 
>>> While adding the xml:lang attribute to various identified places (and update the XML Schema accordingly) would be the easiest way to address that, it might not work for you as xml:lang is already used for another purpose. Other alternatives might be more suitable for you.
>>> (See <http://trac.tools.ietf.org/group/iesg/trac/wiki/TypicalAppsAreaIssues> for a bit more details)
>>> 
>>> Also note that some of the examples might have to be updated to show language tagging.
>>> 
>>> 
>>> 
>>> ----------------------------------------------------------------------
>>> COMMENT:
>>> ----------------------------------------------------------------------
>>> 
>>> 4.6.4.  Non-Negative Integer
>>> 
>>> The value space of non-negative integer is the infinite set
>>> {0,1,2,...}.
>>> 
>>> (And the same comment for positive integers)
>>> Is making this unbounded truly necessary? This might be a burden on
>>> implementations and many (most?) will limit it anyway.
>>> 
>>> _______________________________________________
>>> MEDIACTRL mailing list
>>> MEDIACTRL@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mediactrl
>>> Supplemental Web Site:
>>> http://www.standardstrack.com/ietf/mediactrl
>> 
>> _______________________________________________
>> MEDIACTRL mailing list
>> MEDIACTRL@ietf.org
>> https://www.ietf.org/mailman/listinfo/mediactrl
>> Supplemental Web Site:
>> http://www.standardstrack.com/ietf/mediactrl
> 
> _______________________________________________
> MEDIACTRL mailing list
> MEDIACTRL@ietf.org
> https://www.ietf.org/mailman/listinfo/mediactrl
> Supplemental Web Site:
> http://www.standardstrack.com/ietf/mediactrl