Re: [MEDIACTRL] [Technical Errata Reported] RFC5552 (1994)

"Mark Scott" <Mark.Scott@alcatel-lucent.com> Wed, 26 January 2011 15:00 UTC

Return-Path: <Mark.Scott@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 B91363A67C0 for <mediactrl@core3.amsl.com>; Wed, 26 Jan 2011 07:00:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 fNoFARR5dntk for <mediactrl@core3.amsl.com>; Wed, 26 Jan 2011 07:00:15 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id 8E4D13A67AE for <mediactrl@ietf.org>; Wed, 26 Jan 2011 07:00:15 -0800 (PST)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id p0QF2nuA002917 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 26 Jan 2011 09:02:49 -0600 (CST)
Received: from relay-out2.dc (relay-out2.dc.genesyslab.com [172.22.68.188]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p0QF2gNl012188 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 26 Jan 2011 09:02:44 -0600
Received: from g2.genesyslab.com (g2.genesyslab.com [192.168.20.138]) by relay-out2.dc (8.13.8+Sun/8.13.8) with ESMTP id p0QF2eKh027465; Wed, 26 Jan 2011 07:02:41 -0800 (PST)
Received: from SARUMAN.us.int.genesyslab.com ([192.168.20.90]) by g2.genesyslab.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 26 Jan 2011 07:02:40 -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: Wed, 26 Jan 2011 07:02:40 -0800
Message-ID: <C40751D3A3DAE24192423F6BB78BF29C06A5F1CF@SARUMAN.us.int.genesyslab.com>
In-Reply-To: <46D1E17C154D3D489BB916C274FAFF37046E5E35DA@SARUMAN.us.int.genesyslab.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Technical Errata Reported] RFC5552 (1994)
Thread-Index: AcqNYeRfgrPUjrt0RQWa+YPoa3HREAAAxmLATAE+2pA=
References: <201001041716.o04HGdG8006219@boreas.isi.edu> <46D1E17C154D3D489BB916C274FAFF37046E5E35DA@SARUMAN.us.int.genesyslab.com>
From: "Mark Scott" <Mark.Scott@alcatel-lucent.com>
To: "RFC Errata System" <rfc-editor@rfc-editor.org>, <daveburke@google.com>, <rjsparks@nostrum.com>, <fluffy@cisco.com>, <eburger@standardstrack.com>, <spencer@wonderhamster.org>
X-OriginalArrivalTime: 26 Jan 2011 15:02:40.0553 (UTC) FILETIME=[13BD0990:01CBBD6A]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Cc: Henry Lum <Henry.Lum@genesyslab.com>, mediactrl@ietf.org
Subject: Re: [MEDIACTRL] [Technical Errata Reported] RFC5552 (1994)
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: Wed, 26 Jan 2011 15:00:16 -0000

Hi Everyone,

I'm resending this mail of more than a year ago, as Robert Sparks was
kind enough to point out in a review that it seemed likely that the list
members had actually not received it!

Regards,

Mark.

-----Original Message-----
From: Mark Scott 
Sent: Monday, January 04, 2010 12:43 PM
To: RFC Errata System; daveburke@google.com; rjsparks@nostrum.com;
fluffy@cisco.com; eburger@standardstrack.com; spencer@wonderhamster.org
Cc: Henry Lum; mediactrl@ietf.org
Subject: RE: [Technical Errata Reported] RFC5552 (1994)

I agree that the correction is valid, although I would make a slight
grammatical change to the correct text, as follows:

Corrected Text
--------------
session.connection.redirect:  This array is populated by information
      contained in the History-Info [RFC4244] header in the initial
      INVITE or is otherwise undefined.  Each entry (hi-entry) in the
      History-Info header is mapped, in order, into an element of the 
	session.connection.redirect array.

Regards,

Mark.

-----Original Message-----
From: RFC Errata System [mailto:rfc-editor@rfc-editor.org] 
Sent: January-04-10 12:17 PM
To: daveburke@google.com; Mark Scott; rjsparks@nostrum.com;
fluffy@cisco.com; eburger@standardstrack.com; spencer@wonderhamster.org
Cc: Henry Lum; mediactrl@ietf.org; rfc-editor@rfc-editor.org
Subject: [Technical Errata Reported] RFC5552 (1994)


The following errata report has been submitted for RFC5552,
"SIP Interface to VoiceXML Media Services".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5552&eid=1994

--------------------------------------
Type: Technical
Reported by: Henry Lum <henry.lum@genesyslab.com>

Section: 2.4

Original Text
-------------
session.connection.redirect:  This array is populated by information
      contained in the History-Info [RFC4244] header in the initial
      INVITE or is otherwise undefined.  Each entry (hi-entry) in the
      History-Info header is mapped, in reverse order, into an element
      of the session.connection.redirect array.

Corrected Text
--------------
session.connection.redirect:  This array is populated by information
      contained in the History-Info [RFC4244] header in the initial
      INVITE or is otherwise undefined.  Each entry (hi-entry) in the
      History-Info header is mapped, in order appeared in the
History-Info header, into an element of the session.connection.redirect
array.

Notes
-----
The elements in the History info header is designed as a tree-like
structure from the origination to the destination where each forwarding
proxy appends to the end of the header and add an index. The original
RFC text requires that the elements to be shown in VXML
session.connection.redirect array in reverse order and this is incorrect
based on the definition of session.connection.redirect. The first
element in the array should be the original called number which maps to
index=1 in history-info, and the last element should be the last
redirected number which is the last element in history-info.

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC5552 (draft-ietf-mediactrl-vxml-04)
--------------------------------------
Title               : SIP Interface to VoiceXML Media Services
Publication Date    : May 2009
Author(s)           : D. Burke, M. Scott
Category            : PROPOSED STANDARD
Source              : Media Server Control
Area                : Real-time Applications and Infrastructure
Stream              : IETF
Verifying Party     : IESG

					
-------------------------------------------------------------------------------------------------------------------
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.