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

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Tue, 26 June 2012 18:16 UTC

Return-Path: <eckelcu@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 1FA9B21F8567 for <bfcpbis@ietfa.amsl.com>; Tue, 26 Jun 2012 11:16:17 -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 EXRe4270hfeG for <bfcpbis@ietfa.amsl.com>; Tue, 26 Jun 2012 11:16:16 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 1ECB811E809B for <bfcpbis@ietf.org>; Tue, 26 Jun 2012 11:16:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=3187; q=dns/txt; s=iport; t=1340734576; x=1341944176; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=FVMVz1PGfStXUe/e4YjAXB12mc3vjrJUBGMlu8k48S0=; b=apAN++qQrsGht0lz452K9Y/hNVB5PbNixGqajaXPp1FLvVeIsYBWVNAR G2YVS76ZGla2aABPxo9/PUDrnyg+HYJlgqJ/UcQG6mXG98jtJNoy/+qxW I4Xaww8TnFK/HpFKTc2o5CRn8/A8sYnLTK74juGukr8XYjXFYfi9fn3wn Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EACP76U+tJV2Y/2dsb2JhbABEtjWBB4IYAQEBAwEBAQEPASc0CwwEAgEIEQQBAQEKFAkHJwsUCQgBAQQOBQgah2QEAQuZCqBABIs3hSRgA6NPgWaCXw
X-IronPort-AV: E=Sophos;i="4.77,478,1336348800"; d="scan'208";a="95956361"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-1.cisco.com with ESMTP; 26 Jun 2012 18:16:15 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q5QIGFPW025546 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 26 Jun 2012 18:16:15 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.248]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.02.0298.004; Tue, 26 Jun 2012 13:16:15 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Tom Kristensen (tomkrist)" <tomkrist@cisco.com>, "Horvath, Ernst" <ernst.horvath@siemens-enterprise.com>
Thread-Topic: [bfcpbis] Misplaced text in draft-ietf-bfcpbis-rfc4582bis-03
Thread-Index: Ac1S5/HkYI/piRinSlOhwdh8xyarUgA2EaWAAAHhcAA=
Date: Tue, 26 Jun 2012 18:14:55 +0000
Message-ID: <92B7E61ADAC1BB4F941F943788C08828022523@xmb-aln-x08.cisco.com>
References: <C2BCA7974025BD459349BED0D06E48BB01842B@MCHP03MSX.global-ad.net> <4FE9A973.9090709@cisco.com>
In-Reply-To: <4FE9A973.9090709@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [171.68.122.35]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-18996.004
x-tm-as-result: No--45.861700-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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 18:16:17 -0000

Works for me.

Cheers,
Charles

> -----Original Message-----
> From: bfcpbis-bounces@ietf.org [mailto:bfcpbis-bounces@ietf.org] On
> Behalf Of Tom Kristensen (tomkrist)
> Sent: Tuesday, June 26, 2012 5:22 AM
> To: Horvath, Ernst
> Cc: bfcpbis@ietf.org
> Subject: Re: [bfcpbis] Misplaced text in draft-ietf-bfcpbis-rfc4582bis-03
> 
> 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
> >
> 
> _______________________________________________
> bfcpbis mailing list
> bfcpbis@ietf.org
> https://www.ietf.org/mailman/listinfo/bfcpbis