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

"McGlashan, Scott" <scott.mcglashan@hp.com> Tue, 24 August 2010 15:01 UTC

Return-Path: <scott.mcglashan@hp.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 0FC453A6B2D for <mediactrl@core3.amsl.com>; Tue, 24 Aug 2010 08:01:45 -0700 (PDT)
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 3sXxLsKylWR8 for <mediactrl@core3.amsl.com>; Tue, 24 Aug 2010 08:01:44 -0700 (PDT)
Received: from g6t0187.atlanta.hp.com (g6t0187.atlanta.hp.com [15.193.32.64]) by core3.amsl.com (Postfix) with ESMTP id 46B5A3A6B29 for <mediactrl@ietf.org>; Tue, 24 Aug 2010 08:01:44 -0700 (PDT)
Received: from G3W0630.americas.hpqcorp.net (g3w0630.americas.hpqcorp.net [16.233.58.74]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by g6t0187.atlanta.hp.com (Postfix) with ESMTPS id 15378280DD; Tue, 24 Aug 2010 15:02:17 +0000 (UTC)
Received: from G5W0602.americas.hpqcorp.net (16.228.9.185) by G3W0630.americas.hpqcorp.net (16.233.58.74) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 24 Aug 2010 15:00:33 +0000
Received: from GVW1124EXC.americas.hpqcorp.net ([16.228.24.184]) by G5W0602.americas.hpqcorp.net ([16.228.9.185]) with mapi; Tue, 24 Aug 2010 15:00:33 +0000
From: "McGlashan, Scott" <scott.mcglashan@hp.com>
To: "mediactrl@ietf.org" <mediactrl@ietf.org>
Date: Tue, 24 Aug 2010 14:59:39 +0000
Thread-Topic: ISSUE 1 - IVR Package - HTTP/HTTPS mandatory
Thread-Index: ActDnRlDjBHIu9ftTkyZ/98X4ef9ng==
Message-ID: <06CE0E5A-2922-4CF8-90B4-7623807B7352@hp.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
Cc: Alexey, Melnikov <alexey.melnikov@isode.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>
Subject: [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: Tue, 24 Aug 2010 15:01:45 -0000

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