[bfcpbis] 4582bis terminology

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 20 September 2018 10:48 UTC

Return-Path: <christer.holmberg@ericsson.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 6698D130E94 for <bfcpbis@ietfa.amsl.com>; Thu, 20 Sep 2018 03:48:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level:
X-Spam-Status: No, score=-4.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ug2oryrxxyH3 for <bfcpbis@ietfa.amsl.com>; Thu, 20 Sep 2018 03:48:24 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9989F130E74 for <bfcpbis@ietf.org>; Thu, 20 Sep 2018 03:48:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1537440501; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=1lAcLuqdCFPfGaahw2ojZX+imCosyjsdyNAdSiv7ID8=; b=UmwOmj6yj8Xo3t3O87QasT6UpkHQestXziOezCMc3QbSaV5cWGmLMDQAXP61Nyzv MaQazDiV6RZopbfPRNRp6y8M55dARSO+ivs6zBdi6LBl7BzdeXg9WjEUlHaUKbed w6rt75s9KIjpdtZKpEbE9MVhnB0xZDs2Zxu9QDkiU7s=;
X-AuditID: c1b4fb2d-223ff700000055ff-88-5ba37af52682
Received: from ESESSMB503.ericsson.se (Unknown_Domain [153.88.183.121]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id D8.28.22015.5FA73AB5; Thu, 20 Sep 2018 12:48:21 +0200 (CEST)
Received: from ESESBMB503.ericsson.se (153.88.183.170) by ESESSMB503.ericsson.se (153.88.183.164) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Thu, 20 Sep 2018 12:48:21 +0200
Received: from ESESBMB503.ericsson.se ([153.88.183.186]) by ESESBMB503.ericsson.se ([153.88.183.186]) with mapi id 15.01.1466.003; Thu, 20 Sep 2018 12:48:21 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "bfcpbis@ietf.org" <bfcpbis@ietf.org>
Thread-Topic: 4582bis terminology
Thread-Index: AQHUUM9yVmPSRAJRZU+XPcGDlhOPUg==
Date: Thu, 20 Sep 2018 10:48:21 +0000
Message-ID: <0B376859-5F1E-4612-83EF-F8BA4ADEAF2B@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.0.180812
x-originating-ip: [153.88.183.157]
Content-Type: multipart/alternative; boundary="_000_0B3768595F1E461283EFF8BA4ADEAF2Bericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpnkeLIzCtJLcpLzFFi42KZGbG9Uvdr1eJog12nzSz+rTvK5MDosWTJ T6YAxigum5TUnMyy1CJ9uwSujLkv57EVvK2oOPfoEHMD46nSLkZODgkBE4lbF5oZuxi5OIQE jjJKTNn1iQ3C+cYosfnAYhYIZxmjxMWew0BlHBxsAhYS3f+0QbpFBDQlNm+/ywRiCwvISEyd e4kRIq4oceHjUyYIW0/izJFdYDaLgKpEx9JGsBpeAXuJCYvfsIHYjAJiEt9PrQGrYRYQl7j1 ZD4TxHUCEkv2nGeGsEUlXj7+xwpygqiAvsS0ywEQYSWJLb1bmEDCzALJEr/vq0FMF5Q4OfMJ ywRG4VlIhs5CqJqFpAoirCmxfpc+RLWixJTuh+wQtoZE65y5ULa1REPTMWZkNQsYOVYxihan FhfnphsZ66UWZSYXF+fn6eWllmxiBEbPwS2/dXcwrn7teIhRgINRiYd3U9HiaCHWxLLiytxD jBIczEoivP8TgUK8KYmVValF+fFFpTmpxYcYpTlYlMR59VbtiRISSE8sSc1OTS1ILYLJMnFw SjUwzkz5Gm0Tw6x+LnnlNrf5LGKX4rlPehW/qDU3dO5gnMevcrBN/9Vq76x1jbuNH3+2FowP M08sW1wlMqmQ3yFwinnzjY65pteeTDjrmKEi9svwwdzi8kX+H49PyvyxOK3QrydD5aTYjp2r pr2xWfL4f/eJZctfqK5c8bn+BetS2Z1RtzKvTLpTosRSnJFoqMVcVJwIACwDJL+aAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/bfcpbis/1rcWswov0J5xIYQH6kkgsWefv0k>
Subject: [bfcpbis] 4582bis terminology
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 20 Sep 2018 10:48:29 -0000

Hi,

I took a look at the 4582bis terminology, and I am a little confused.

We have the following definitions:


   Client: A floor participant or a floor chair that communicates with a

   floor control server using BFCP.


   Floor Control Server: A logical entity that maintains the state of

   the floor(s), including which floors exists, who the floor chairs

   are, who holds a floor, etc.  Requests to manipulate a floor are

   directed at the floor control server.  The floor control server of a

   conference may perform other logical roles (e.g., floor participant)

   in another conference.

So far, so good, I think. 4582bis does not define “client” and “server” as roles, though.

Then there is:

   Floor Chair: A logical entity that manages one floor (grants, denies,
   or revokes a floor).  An entity that assumes the logical role of a
   floor chair for a given transaction may assume a different role
   (e.g., floor participant) for a different transaction.  The roles of
   floor chair and floor participant are defined on a transaction-by-
   transaction basis.  BFCP transactions are defined in Section 8.

Still ok, I think. The chair is per transaction, so both a client and server can act as floor chair.

But, then there is:


   Floor Participant: A logical entity that requests floors, and

   possibly information about them, from a floor control server.  An

   entity that assumes the logical role of a floor participant for a

   given transaction may assume a different role (e.g., a floor chair)

   for a different transaction.

First, it says that a floor participant request floors from a floor control server. My understanding of that is that the floor participant is always the client, which means it stays the same throughout the session (due to the c-s removal in 4583bis).

Second, the text says that the role is per transaction, which would mean the client/server thing is also per transaction.

Is there a bug? Should the text say:


   Floor Participant: A logical entity that requests floors, and

   possibly information about them, from a floor chair.


Regards,

Christer