[bfcpbis] Misplaced text in draft-ietf-bfcpbis-rfc4582bis-03

"Horvath, Ernst" <ernst.horvath@siemens-enterprise.com> Mon, 25 June 2012 15:34 UTC

Return-Path: <ernst.horvath@siemens-enterprise.com>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D28411E808F for <bfcpbis@ietfa.amsl.com>; Mon, 25 Jun 2012 08:34:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FlHXtMfQ97YX for <bfcpbis@ietfa.amsl.com>; Mon, 25 Jun 2012 08:34:03 -0700 (PDT)
Received: from senmx11-mx.siemens-enterprise.com (senmx11-mx.siemens-enterprise.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id 7C2BD11E808D for <bfcpbis@ietf.org>; Mon, 25 Jun 2012 08:34:03 -0700 (PDT)
Received: from MCHP02HTC.global-ad.net (unknown [172.29.42.235]) by senmx11-mx.siemens-enterprise.com (Server) with ESMTP id 3E6B41EB8432 for <bfcpbis@ietf.org>; Mon, 25 Jun 2012 17:34:02 +0200 (CEST)
Received: from MCHP03MSX.global-ad.net ([169.254.2.115]) by MCHP02HTC.global-ad.net ([172.29.42.235]) with mapi id 14.01.0339.001; Mon, 25 Jun 2012 17:34:02 +0200
From: "Horvath, Ernst" <ernst.horvath@siemens-enterprise.com>
To: "bfcpbis@ietf.org" <bfcpbis@ietf.org>
Thread-Topic: Misplaced text in draft-ietf-bfcpbis-rfc4582bis-03
Thread-Index: Ac1S5/HkYI/piRinSlOhwdh8xyarUg==
Date: Mon, 25 Jun 2012 15:34:01 +0000
Message-ID: <C2BCA7974025BD459349BED0D06E48BB01842B@MCHP03MSX.global-ad.net>
Accept-Language: de-AT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.26.0.183]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [bfcpbis] Misplaced text in draft-ietf-bfcpbis-rfc4582bis-03
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bfcpbis>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jun 2012 15:34:04 -0000

I think some text needs to be shifted into a different section, as detailed below.

Sections 10.1.2 and 10.2.2 both start with a sentence
  "When communicating over unreliable transport and upon receiving a
   [FloorRequest/FloorRelease] from a participant, the floor control server MUST
   respond with a FloorRequestStatus message within the transaction
   failure window to complete the transaction."
These statements put a normative requirement on the floor control server and should therefore go into section 13.1 and 13.4, respectively.

Similarly, the sentence
  "When communicating over unreliable transport and upon receiving a
   ChairAction from a participant, the floor control server MUST respond
   with a ChairActionAck message within the transaction failure window
   to complete the transaction."
from 11.2 belongs into section 13.6. In addition, "from a participant" should rather be "from a chair" in that sentence.

The same applies to
- 12.1.2, where the 1st sentence should go into 13.5;
- 12.2.2, where the 1st sentence should go into 13.2;
- 12.3.2, where the 1st sentence should go into 13.3;
- 12.4.2, where the 1st sentence should go into 13.7.

Furthermore, section 13.1.3 specifies participant behaviour and should be moved into section 10.1, possibly under the heading "Reception of a Subsequent FloorRequestStatus Message".
What could be covered in 13.1.3 (or as part of 13.1.2) instead is retransmission of a subsequent FloorRequestStatus message, which is currently not specified explicitly.

Simlarly for 13.5.3, which should go into 12.1; retransmission of subsequent FloorStatus messages could be covered in 13.5.3 instead.

13.9 is also in the wrong section, but this subsection will disappear anyway if ErrorAck is removed as a whole.

Regards,
Ernst