Re: [MEDIACTRL] Weird stuff in RFC 5552

"Worley, Dale R (Dale)" <dworley@avaya.com> Tue, 25 January 2011 21:14 UTC

Return-Path: <dworley@avaya.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 B9FCD3A68C6 for <mediactrl@core3.amsl.com>; Tue, 25 Jan 2011 13:14:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.539
X-Spam-Level:
X-Spam-Status: No, score=-102.539 tagged_above=-999 required=5 tests=[AWL=0.060, 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 gHn5htYqoM0m for <mediactrl@core3.amsl.com>; Tue, 25 Jan 2011 13:14:14 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id EA63A3A68AD for <mediactrl@ietf.org>; Tue, 25 Jan 2011 13:14:13 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAF7MPk3GmAcF/2dsb2JhbACkcXOjfQKZEYVPBIUXinI
X-IronPort-AV: E=Sophos;i="4.60,376,1291611600"; d="scan'208";a="261439799"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 25 Jan 2011 16:17:12 -0500
X-IronPort-AV: E=Sophos;i="4.60,376,1291611600"; d="scan'208";a="574717519"
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by co300216-co-erhwest-out.avaya.com with ESMTP; 25 Jan 2011 16:17:12 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.215]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Tue, 25 Jan 2011 16:17:11 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Henry Lum <Henry.Lum@alcatel-lucent.com>, "mediactrl@ietf.org" <mediactrl@ietf.org>
Date: Tue, 25 Jan 2011 16:16:48 -0500
Thread-Topic: [MEDIACTRL] Weird stuff in RFC 5552
Thread-Index: AQHLuE/7mxHARwv4XU23rRG0rNUwj5PgTPXwgAHsxX8=
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B220A1767E5@DC-US1MBEX4.global.avaya.com>
References: <CD5674C3CD99574EBA7432465FC13C1B220A1767C4@DC-US1MBEX4.global.avaya.com>, <059AF07365DC474393A19A3AF187DF7406989992@NAHALD.us.int.genesyslab.com>
In-Reply-To: <059AF07365DC474393A19A3AF187DF7406989992@NAHALD.us.int.genesyslab.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
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: Tue, 25 Jan 2011 21:14:14 -0000

> From: Henry Lum
> 
> 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.

Assuming that the "screening indicator" is intended to prevent the
recipient from knowing the origin, the "si" properties should be
driven by the "Privacy" headers encoded into the History-Info.

Dale