Re: [MEDIACTRL] ISSUE 1 - IVR Package - HTTP/HTTPS mandatory

Eric Burger <eburger@standardstrack.com> Fri, 24 September 2010 00:28 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 5AAC73A682C for <mediactrl@core3.amsl.com>; Thu, 23 Sep 2010 17:28:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.434
X-Spam-Level:
X-Spam-Status: No, score=-102.434 tagged_above=-999 required=5 tests=[AWL=0.165, 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 jmvnsX49eC-T for <mediactrl@core3.amsl.com>; Thu, 23 Sep 2010 17:28:50 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19.inmotionhosting.com [205.134.249.249]) by core3.amsl.com (Postfix) with ESMTP id 647B83A6804 for <mediactrl@ietf.org>; Thu, 23 Sep 2010 17:28:50 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com; h=Received:Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc:Message-Id:References:To:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=qxK2F1OC/h4Vrtw55kYiky27OHCD+aw7PexlZESOER3jb3Q8NJB8wPLVKzoB6lae2RTknbd14ODfARsBYV2DkkNKwNgQcmdoxx+0drGxW+SO5VN8NNXrmxRJmNFovoyQ;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.101]) by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1Oyvqy-00048s-24; Thu, 23 Sep 2010 17:09:28 -0700
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: multipart/signed; boundary=Apple-Mail-39--120470330; protocol="application/pkcs7-signature"; micalg=sha1
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <AANLkTin=v+tPJi3ou3qE1PWYmnAmsOMXmOk9_Viefqeh@mail.gmail.com>
Date: Thu, 23 Sep 2010 17:21:31 -0400
Message-Id: <EC2DA1E2-E308-4E53-A248-4319F9721C80@standardstrack.com>
References: <ActDnRlDjBHIu9ftTkyZ/98X4ef9ng==> <06CE0E5A-2922-4CF8-90B4-7623807B7352@hp.com> <AANLkTin=v+tPJi3ou3qE1PWYmnAmsOMXmOk9_Viefqeh@mail.gmail.com>
To: Victor Paulsamy <vpaulsamy@ditechnetworks.com>
X-Mailer: Apple Mail (2.1081)
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
X-Source:
X-Source-Args:
X-Source-Dir:
Cc: Melnikov Alexey <alexey.melnikov@isode.com>, mediactrl@ietf.org, mediactrl-chairs@tools.ietf.org, draft-ietf-mediactrl-ivr-control-package@tools.ietf.org
Subject: Re: [MEDIACTRL] ISSUE 1 - IVR Package - HTTP/HTTPS mandatory
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 Sep 2010 00:28:53 -0000

Both.

On Aug 26, 2010, at 4:20 PM, Victor Paulsamy wrote:

> Is it mandatory to support both or either?
> 
> --victor
> 
> On Tue, Aug 24, 2010 at 7:59 AM, McGlashan, Scott <scott.mcglashan@hp.com> wrote:
> Hi All,
> 
> As part of our IESG review of the IVR package the following issue has been identified:
> 
> 1) In Section 4:
> 
>   The MS MUST
>   support one or more schemes using communication protocols suitable
>   for fetching resources (e.g.  HTTP).
> 
> I don't think this is good enough for interoperability. You should specify a
> mandatory to implement protocol for fetching resources.
> I suggest you mandate
> use of HTTP and HTTPS. (The latter is important for providing data
> confidentiality)
> 
> The same issue is relevant in section 4.3.1.4 - a mandatory to implement
> protocol for recording data.
> 
> Are we happy to mandate the use of HTTP and HTTPS in the context of fetching dialog documents and resources as well as recordings?
> This seems a reasonable change to us but would affect implementations which don't already support these protocols. Let us know if you have any objections to this change.
> 
> thanks
> 
> Scott
> _______________________________________________
> 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