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

Victor Paulsamy <vpaulsamy@ditechnetworks.com> Thu, 26 August 2010 20:19 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 5AD2C3A6AD7 for <mediactrl@core3.amsl.com>; Thu, 26 Aug 2010 13:19:37 -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=[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 mlqrMliuHpYG for <mediactrl@core3.amsl.com>; Thu, 26 Aug 2010 13:19:30 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 0FA2D3A6A6A for <mediactrl@ietf.org>; Thu, 26 Aug 2010 13:19:29 -0700 (PDT)
Received: by vws10 with SMTP id 10so2309394vws.31 for <mediactrl@ietf.org>; Thu, 26 Aug 2010 13:20:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.62.196 with SMTP id y4mr6550202vch.97.1282854002020; Thu, 26 Aug 2010 13:20:02 -0700 (PDT)
Received: by 10.220.122.96 with HTTP; Thu, 26 Aug 2010 13:20:01 -0700 (PDT)
In-Reply-To: <06CE0E5A-2922-4CF8-90B4-7623807B7352@hp.com>
References: <ActDnRlDjBHIu9ftTkyZ/98X4ef9ng==> <06CE0E5A-2922-4CF8-90B4-7623807B7352@hp.com>
Date: Thu, 26 Aug 2010 13:20:01 -0700
Message-ID: <AANLkTin=v+tPJi3ou3qE1PWYmnAmsOMXmOk9_Viefqeh@mail.gmail.com>
From: Victor Paulsamy <vpaulsamy@ditechnetworks.com>
To: "McGlashan, Scott" <scott.mcglashan@hp.com>
Content-Type: multipart/alternative; boundary=e0cb4e88767316d3b6048ebfb977
Cc: Melnikov <alexey.melnikov@isode.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>
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: Thu, 26 Aug 2010 20:19:37 -0000

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
>