RE: [xcon] Question about draft-ietf-xcon-common-data-model-05

Hi Paul,

Actually a conference participant has two methods to 'subscribe' himself to the floor events. One method is using offer/answer exchange mechanism (rfc3264) using SIP INVITE and BFCP parameters in the SDP (rfc4583). The other method is a general authorization mechanism described in section 9 of rfc4582 and in draft-ietf-xcon-bfcp-connection-05 draft.  
When we talk about 'subscription' in chapter 4.4 we're talking about those two connection methods. Future documentation may define additional connection mechanisms.

Cheers,

Oscar

________________________________

From: paul [mailto:baohongqing@huawei.com] 
Sent: 19. heinäkuuta 2007 5:27
To: Oscar Novo (JO/LMF)
Cc: xcon@ietf.org
Subject: [xcon] Question about draft-ietf-xcon-common-data-model-05

Hi  Oscar 

I have a question on this draft.

In chapter 4.4 it said:

   "The <allow-floor-events> element represents a boolean action.  If set

   to TRUE, the focus is instructed to accept the subscription to floor

   control events.  If set to FALSE, the focus is instructed to reject

   the subscription.  If this element is undefined, it has a default

   value of FALSE, causing the subscription to floor control events to

   be rejected."

Does "subscription" here mean the SIP SUBSCRIBE request initiated subscription?

However I know the BFCP protocol is used for floor control, and there is no concept of subscription.