XCON Interim Meeting Boston, MA May 26, 2004

Note Well All statements related to the activities of the IETF and addressed to the IETF are subject to all provisions of Section 10 of RFC 2026 and Sections 3 through 6 of RFC 3667, which grant to the IETF and its participants certain licenses and rights in such statements. Such statements include verbal statements in IETF meetings, as well as written and electronic communications made at any time or place, which are addressed to: –the IETF plenary session, –any IETF working group or portion thereof, –the IESG, or any member thereof on behalf of the IESG, –the IAB or any member thereof on behalf of the IAB, –any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, –the RFC Editor or the Internet-Drafts function Statements made outside of an IETF meeting, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not subject to these provisions.

Agenda 9:00 - 9:10 Chairs: Floor Control Protocol Requirements draft-ietf-xcon-floor-control-req-00.txt 9: :00 Gonzalo Camarillo: Floor Control Protocol Proposal draft-camarillo-xcon-bfcp-00.txt 11: :20 Orit Levin: Conference Package Updates draft-ietf-sipping-conference-package-04.txt 11: :45 Hisham Khartabil: Conference Policy Control (And Lunch) draft-koskelainen-xcon-xcap-cpcp-usage-02.txt 13: :00 Aki Niemi: Common Policy for Conference Policy Auth. draft-niemi-xcon-cpcp-rules-00.txt 14: :00 Chairs et al.: Plan Forward for Media Policy

Floor Control Protocol Requirements Last call completed. Only one issue to be resolved: who can see the floor chair identitity (e.g. whether it is hidden, known by some subset of users or by all users). Proposed solution: when floor is created (via CPCP etc), the creator defines floor chair identity as hidden/public.