[MEDIACTRL] some corrections to mrb-04
"MUNSON, GARY A, ATTLABS" <gm3472@att.com> Thu, 13 May 2010 21:26 UTC
Return-Path: <gm3472@att.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 CEB913A6D17 for <mediactrl@core3.amsl.com>; Thu, 13 May 2010 14:26:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.999
X-Spam-Level:
X-Spam-Status: No, score=-103.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4, 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 L3He2YwJ2erf for <mediactrl@core3.amsl.com>; Thu, 13 May 2010 14:26:39 -0700 (PDT)
Received: from mail121.messagelabs.com (mail121.messagelabs.com [216.82.242.3]) by core3.amsl.com (Postfix) with ESMTP id B5BB33A6811 for <mediactrl@ietf.org>; Thu, 13 May 2010 14:26:36 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: gm3472@att.com
X-Msg-Ref: server-4.tower-121.messagelabs.com!1273785980!31069184!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 25886 invoked from network); 13 May 2010 21:26:20 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-4.tower-121.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 May 2010 21:26:20 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o4DLQ2we023018 for <mediactrl@ietf.org>; Thu, 13 May 2010 17:26:02 -0400
Received: from gaalpa1msgusr7b.ugd.att.com (gaalpa1msgusr7b.ugd.att.com [135.53.26.16]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o4DLPxo7022895 for <mediactrl@ietf.org>; Thu, 13 May 2010 17:25:59 -0400
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: Thu, 13 May 2010 17:26:12 -0400
Message-ID: <2F41EF28ED42A5489E41742244C9117C02574A31@gaalpa1msgusr7b.ugd.att.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: some corrections to mrb-04
Thread-Index: Acry4ukqkQXkXlicSzeph7WZI2N9gg==
From: "MUNSON, GARY A, ATTLABS" <gm3472@att.com>
To: mediactrl@ietf.org, Lorenzo Miniero <lorenzo@meetecho.com>, Chris Boulton <chris@ns-technologies.com>
Cc: "EPLEY, BOB (ATTLABS)" <be1891@att.com>
Subject: [MEDIACTRL] some corrections to mrb-04
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, 13 May 2010 21:26:40 -0000
Hi Lorenzo, Chris, My colleague Bob Epley was reviewing -mrb-04, and we believe the following are corrections needed: 1) Section 5.2.3, at the beginning talks about a <session-info> in the response from MRB, whereas it should be <response-session-info>. Additionally, there, the <media-server-address> as a child element is not included, whereas it is included in 5.2.5.1.1. and in the XML schema as a child element of <response-session-info>. 2) Section 5.2.5.1.1 talks about including <response-session-info> in a response from MRB to an update request, whereas that element should also be present in a (successful) response to the initial request. Additionally, 5.2.3 says the <session-response> element MUST be present in a successful response, whereas in 5.2.5.1.1 it is stated that the element MAY be present. Can't tell whether those statements conflict, or at the least the latter needs clarification. 3) Section 5.2.4.1.1.1 (on <session-info>) and 5.2.5.1.1 (on <response-session-info>) both talk about a <max-prepared-duration> element. That doesn't belong and should be replaced with <session-info> and <response-session-info> statements as appropriate. 4) The Query example in Section 6.2.1 has the client query containing a <session-info> element, but this would not be present in an initial query. In which case it would be useful to clarify in the text around the example or alternatively that element should be removed from the message content. And, at any rate, the <session-info> there only shows one child element, not three. 5) The <response-session-info> element in the MRB response message content in the example in 6.2.1 should include an <expires>. Cheers, Gary
- [MEDIACTRL] some corrections to mrb-04 MUNSON, GARY A, ATTLABS
- Re: [MEDIACTRL] some corrections to mrb-04 Lorenzo Miniero