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. 

[Chris Boulton] Oscar - it might be worth expanding this text to clearly
state and reference the current subscription mechanisms (or point to the
appropriate section).

Chris.

Information contained in this e-mail and any attachments are intended for the use of the addressee only, and may contain confidential information of Ubiquity Software Corporation. All unauthorized use, disclosure or distribution is strictly prohibited.  If you are not the addressee, please notify the sender immediately and destroy all copies of this email. Ubiquity Software Corporation plc, a company registered under the laws of England and Wales, Registration 2719723, registered offices at Eastern Business Park, Building 3, Wern Fawr Lane, St. Mellons, Cardiff CF3 5EA, Wales, United Kingdom.