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

Tom Kristensen <tomkrist@cisco.com> Tue, 26 June 2012 12:22 UTC

Return-Path: <tomkrist@cisco.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 6BE8221F85A1 for <bfcpbis@ietfa.amsl.com>; Tue, 26 Jun 2012 05:22:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 wMIAzbeozeUe for <bfcpbis@ietfa.amsl.com>; Tue, 26 Jun 2012 05:22:13 -0700 (PDT)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id 381DF21F853B for <bfcpbis@ietf.org>; Tue, 26 Jun 2012 05:22:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=tomkrist@cisco.com; l=2540; q=dns/txt; s=iport; t=1340713333; x=1341922933; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=rCMmkql5GCY2x2O4F3dd3axfYK3om7QEaqAc5V9m1Ac=; b=Uwo6MzFytBdZz9eFTNkVeLznXJ8ZURNqimqWm8HzEFfRRSgoOm7zhIkg 0x6i89l3h1z4gbIEzhGv8GoyJWCLYGYtQhCj/MfAM8Lx9bvthTCRZX1a0 FZEwQp5JNmdrxgSHKyiYNbKRgXgG6x/YGgJMaOUSINObj8Ie/oetPUmlv s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAFGo6U+Q/khM/2dsb2JhbABFtiuBB4IYAQEBBAEBAQ8BJTYKARALGAkWDwkDAgECARUwBg0BBQIBAR6HaQuYQaBABIszhgQDlTGFVohHgWaCYQ
X-IronPort-AV: E=Sophos;i="4.77,477,1336348800"; d="scan'208";a="6196616"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-4.cisco.com with ESMTP; 26 Jun 2012 12:22:12 +0000
Received: from [10.54.86.31] (dhcp-10-54-86-31.cisco.com [10.54.86.31]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q5QCMBN3017971; Tue, 26 Jun 2012 12:22:12 GMT
Message-ID: <4FE9A973.9090709@cisco.com>
Date: Tue, 26 Jun 2012 14:22:11 +0200
From: Tom Kristensen <tomkrist@cisco.com>
Organization: Cisco
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.15) Gecko/20101027 Fedora/3.0.10-1.fc12 Lightning/1.0b2pre Thunderbird/3.0.10
MIME-Version: 1.0
To: "Horvath, Ernst" <ernst.horvath@siemens-enterprise.com>
References: <C2BCA7974025BD459349BED0D06E48BB01842B@MCHP03MSX.global-ad.net>
In-Reply-To: <C2BCA7974025BD459349BED0D06E48BB01842B@MCHP03MSX.global-ad.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "bfcpbis@ietf.org" <bfcpbis@ietf.org>
Subject: Re: [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: Tue, 26 Jun 2012 12:22:20 -0000

The changes you propose below seems to make sense and will keep the 
logic partitioning of the text with regards to requirements/behaviour 
for the different roles in the separate sections:

10.  Floor Participant Operations
11.  Chair Operations
12.  General Client Operations
13.  Floor Control Server Operations

I no objections are received, I'll proceed to shuffle the text across 
according to your comments; thank you very much!

-- Tom

On 06/25/2012 05:34 PM, Horvath, Ernst wrote:
> 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
> _______________________________________________
> bfcpbis mailing list
> bfcpbis@ietf.org
> https://www.ietf.org/mailman/listinfo/bfcpbis
>