Re: [bfcpbis] 4582bis terminology

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 21 September 2018 17:01 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 E640D130E4A for <bfcpbis@ietfa.amsl.com>; Fri, 21 Sep 2018 10:01:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.309
X-Spam-Level:
X-Spam-Status: No, score=-4.309 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, URIBL_BLOCKED=0.001] 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 WOOpSm5UgqVA for <bfcpbis@ietfa.amsl.com>; Fri, 21 Sep 2018 10:01:54 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (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 1E69D1277CC for <bfcpbis@ietf.org>; Fri, 21 Sep 2018 10:01:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1537549310; 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=TCJXCuuR/dMSCkc2DLwkJZ2i7kgfxAYaJ18dMDnUA6c=; b=X+4CPPIffhKnxNid9DK7phC9Vjq408Onzt+dlbaRCCiuC2A4Fx+y7Uf0dCOICOcf Nft3gIC4BBQ4galUhgJvLh9X4rQJHFZwJw61kZUtLV1zuAdMNeQzFbN1g2MN2KRa xQcjJEXxijjdc8zuTztneAtzGWstkl+ThyAbMWCE9gQ=;
X-AuditID: c1b4fb30-3cd869c0000055da-13-5ba523fe396c
Received: from ESESBMB504.ericsson.se (Unknown_Domain [153.88.183.117]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id D6.CF.21978.EF325AB5; Fri, 21 Sep 2018 19:01:50 +0200 (CEST)
Received: from ESESBMB503.ericsson.se (153.88.183.170) by ESESBMB504.ericsson.se (153.88.183.171) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Fri, 21 Sep 2018 19:01:48 +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; Fri, 21 Sep 2018 19:01:48 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Alan Ford <alan.ford@gmail.com>
CC: "bfcpbis@ietf.org" <bfcpbis@ietf.org>
Thread-Topic: [bfcpbis] 4582bis terminology
Thread-Index: AQHUUM9yVmPSRAJRZU+XPcGDlhOPUqT5O0iAgAEdqoCAABANAIAAjkGg
Date: Fri, 21 Sep 2018 17:01:48 +0000
Message-ID: <270a3fcffc51424ab8a75ce50a278bec@ericsson.com>
References: <0B376859-5F1E-4612-83EF-F8BA4ADEAF2B@ericsson.com> <35342C90-DFDC-4EF2-A0A6-3E6375807498@gmail.com> <82FBA811-E52E-433E-A36A-D2A0E86C949C@ericsson.com> <D77C104C-FA05-49AF-BDF7-62AF96B1E089@gmail.com>
In-Reply-To: <D77C104C-FA05-49AF-BDF7-62AF96B1E089@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.153]
Content-Type: multipart/alternative; boundary="_000_270a3fcffc51424ab8a75ce50a278becericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrAIsWRmVeSWpSXmKPExsUyM2J7qe4/5aXRBh0reS1WnlvBbPFv3VEm ByaPnbPusnssWfKTKYApissmJTUnsyy1SN8ugStj0r7FbAWvZjFV3D26hq2Bcctkpi5GTg4J AROJEx8aGLsYuTiEBI4ySnT2z2QFSQgJfGOUWHZRFiKxjFFiwYyXbF2MHBxsAhYS3f+0QUwR AWWJ5bPAypkFNCWuHt7FCGILC2hJLD19ESwuIqAtcXLlEyaIcjeJG1e0QMIsAqoSU6etYgGx eQWsJU6cngR1wm1Gic0P74MlOAVsJVb+nA9mMwqISXw/tYYJYpe4xK0n86HuF5BYsuc8M4Qt KvHy8T9WCFtJYu+x6ywQ9ckSJy8tYYJYJihxcuYTlgmMorOQjJqFpGwWkrJZQGeDvLZ+lz5E iaLElO6H7BC2hkTrnLnsyOILGNlXMYoWpxYn5aYbGemlFmUmFxfn5+nlpZZsYgTG28Etvw12 ML587niIUYCDUYmHt1tuabQQa2JZcWXuIUYJDmYlEd4cBqAQb0piZVVqUX58UWlOavEhRmkO FiVxXgu/zVFCAumJJanZqakFqUUwWSYOTqkGRnWhdJ/Zl/htd+21VEgr5V3fs3jdlnST8kP7 u26zS3Wcrdry2NPBuvlelmtgR6q2YP4eY4nMbof44Og/S7P51q4qfcWY8OjSpMd9Nat3hqqw 1Hy08U3lZyyxELpw7qBCqeHtZNV3GSGvgwUi5Pa//HXqCY/sSm2uvOrvixKCnCsMtEMe/9uo xFKckWioxVxUnAgAo+PIZLMCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/bfcpbis/2XFW2YXkIeh8mNpNKFJzGQVldb8>
Subject: Re: [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: Fri, 21 Sep 2018 17:01:57 -0000

Hi,

>I see your point but “role” is used sparingly in 4583bis, and is specific to 4583bis.

Yes, but “client” and “server” are the same things in both specs, so I thought we could align the terminology.

Anyway, if people are ok with the current text, I won’t object :)

Regards,

Christer


On 21 Sep 2018, at 07:23, Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.holmberg@ericsson.com>> wrote:

Hi Alan,

Thanks for your input. My understanding of what is deployed is similar as yours.

>The problem, I think, is with the text about different roles being determined per-transaction. That doesn’t really map to the way BFCP is
>used in the real world, but fundamentally the protocol (4582bis) doesn’t prevent the three logical entities all passing messages and changing
>roles. We only nail this down to fixed roles in 4583bis through the SDP exchange.

Also note that, in 4582bis, “client” and “server” are not defined as roles (“participant” and “chair” are the defined roles).

However, 4583bis defines “client” and “server” as roles. Should we remove “role” from 4583bis and only talk about “client” and “server”?

Regards,

Christer


On 20 Sep 2018, at 11:48, Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.holmberg@ericsson.com>> wrote:

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
_______________________________________________
bfcpbis mailing list
bfcpbis@ietf.org<mailto:bfcpbis@ietf.org>
https://www.ietf.org/mailman/listinfo/bfcpbis