Re: [MEDIACTRL] Weird stuff in RFC 5552

"Henry Lum" <Henry.Lum@alcatel-lucent.com> Mon, 24 January 2011 15:54 UTC

Return-Path: <Henry.Lum@alcatel-lucent.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 C17133A6AF8 for <mediactrl@core3.amsl.com>; Mon, 24 Jan 2011 07:54:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.084
X-Spam-Level:
X-Spam-Status: No, score=-6.084 tagged_above=-999 required=5 tests=[AWL=0.515, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 3GmzISJF7ftu for <mediactrl@core3.amsl.com>; Mon, 24 Jan 2011 07:54:21 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id 542FD3A6AC3 for <mediactrl@ietf.org>; Mon, 24 Jan 2011 07:54:21 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id p0OFv8B1008494 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 24 Jan 2011 09:57:09 -0600 (CST)
Received: from relay-out1.wc.genesyslab.com (relay-out1.wc.genesyslab.com [172.22.70.114]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p0OFv7ZC011116 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 24 Jan 2011 09:57:08 -0600
Received: from g2.genesyslab.com (g2.genesyslab.com [192.168.20.138]) by relay-out1.wc.genesyslab.com (8.13.8+Sun/8.13.8) with ESMTP id p0OFv65e006388; Mon, 24 Jan 2011 07:57:06 -0800 (PST)
Received: from NAHALD.us.int.genesyslab.com ([192.168.20.92]) by g2.genesyslab.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 24 Jan 2011 07:57:06 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 24 Jan 2011 07:57:05 -0800
Message-ID: <059AF07365DC474393A19A3AF187DF7406989992@NAHALD.us.int.genesyslab.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B220A1767C4@DC-US1MBEX4.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [MEDIACTRL] Weird stuff in RFC 5552
Thread-Index: AQHLuE/7mxHARwv4XU23rRG0rNUwj5PgTPXw
References: <CD5674C3CD99574EBA7432465FC13C1B220A1767C4@DC-US1MBEX4.global.avaya.com>
From: "Henry Lum" <Henry.Lum@alcatel-lucent.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>, <mediactrl@ietf.org>
X-OriginalArrivalTime: 24 Jan 2011 15:57:06.0931 (UTC) FILETIME=[59D34430:01CBBBDF]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Subject: Re: [MEDIACTRL] Weird stuff in RFC 5552
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: Mon, 24 Jan 2011 15:54:22 -0000

VXML2 does define a si (screening indicator) property in each element in
the session.connection.redirect. But you are correct that RFC4244 makes
no reference to screening indicator at all for Histroy-Info header so
our implementation ends up always setting it to undefined.

Regards,
Henry

> -----Original Message-----
> From: mediactrl-bounces@ietf.org [mailto:mediactrl-bounces@ietf.org]
On
> Behalf Of Worley, Dale R (Dale)
> Sent: Wednesday, January 19, 2011 10:13 PM
> To: mediactrl@ietf.org
> Subject: [MEDIACTRL] Weird stuff in RFC 5552
> 
> Looking at an erratum to RFC 5552 ("SIP Interface to VoiceXML Media
> Services"), I ran into the following oddities in the definition of the
> following two componets of the elements of the
> session.connection.redirect array:
> 
>       *  uri - Set to the hi-targeted-to-uri value of the History-Info
>          entry
> 
> This is badly phrased:  Strictly speaking, the hi-targeted-to-uri
> contains "header parameters", including "Reason" and "Privacy", which
> are not derived from the request-URI of the corresponding INVITE, and
> are not meaningful considered as part of that URI.  So this definition
> should be "Set to the hi-targeted-to-uri value, without 'headers', of
> the History-Info entry"
> 
>       *  si - Set to the value of the "si" parameter if it exists,
>          undefined otherwise
> 
> I can find no reference to the "si" value in VXML 2.0, RFC 4244, or in
> draft-ietf-sipcore-rfc4244bis-02 -- is this entry a mistake?
> Ironically, taken verbatim, this definition requires the "si" value to
> always be undefined, which is the same effect as if its definition
> were deleted from the RFC.
> 
> What do people think of this?  Should these be fixed by an erratum?
> What was really meant?
> 
> Dale
> _______________________________________________
> MEDIACTRL mailing list
> MEDIACTRL@ietf.org
> https://www.ietf.org/mailman/listinfo/mediactrl
> Supplemental Web Site:
> http://www.standardstrack.com/ietf/mediactrl

					
-------------------------------------------------------------------------------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain confidential and proprietary information of Alcatel-Lucent and/or its affiliated entities. Access by the intended recipient only is authorized. Any liability arising from any party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately, destroy the original transmission and its attachments and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or its affiliated entities.