[MEDIACTRL] Weird stuff in RFC 5552

"Worley, Dale R (Dale)" <dworley@avaya.com> Thu, 20 January 2011 03:10 UTC

Return-Path: <dworley@avaya.com>
X-Original-To: mediactrl@core3.amsl.com
Delivered-To: mediactrl@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 21DCB3A708B for <mediactrl@core3.amsl.com>; Wed, 19 Jan 2011 19:10:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.535
X-Spam-Status: No, score=-102.535 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id idUOi70RhePv for <mediactrl@core3.amsl.com>; Wed, 19 Jan 2011 19:10:54 -0800 (PST)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (nj300815-nj-outbound.net.avaya.com []) by core3.amsl.com (Postfix) with ESMTP id A6C053A7089 for <mediactrl@ietf.org>; Wed, 19 Jan 2011 19:10:53 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAII3N03GmAcF/2dsb2JhbACkSnOkPgKYVYVQBIRviW4
X-IronPort-AV: E=Sophos;i="4.60,347,1291611600"; d="scan'208";a="55153458"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 19 Jan 2011 22:13:19 -0500
X-IronPort-AV: E=Sophos;i="4.60,347,1291611600"; d="scan'208";a="572918127"
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([]) by co300216-co-erhwest-out.avaya.com with ESMTP; 19 Jan 2011 22:13:19 -0500
Received: from DC-US1MBEX4.global.avaya.com ([]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Wed, 19 Jan 2011 22:13:18 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "mediactrl@ietf.org" <mediactrl@ietf.org>
Date: Wed, 19 Jan 2011 22:12:35 -0500
Thread-Topic: Weird stuff in RFC 5552
Thread-Index: AQHLuE/7mxHARwv4XU23rRG0rNUwjw==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B220A1767C4@DC-US1MBEX4.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [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: Thu, 20 Jan 2011 03:10:55 -0000

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

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?