50 likes | 66 Vues
Conference Policy. XCON WG Hisham Khartabil hisham.khartabil@nokia.com IETF#58, Minneapolis. draft-koskelainen-xcon-cpcp-reqs-01.txt. Removed all open issues from version 00 according to mailing list comments Open issue: Need some opinions of strengths (MUSTs and SHOULDs) in requirements
E N D
Conference Policy XCON WG Hisham Khartabil hisham.khartabil@nokia.com IETF#58, Minneapolis
draft-koskelainen-xcon-cpcp-reqs-01.txt • Removed all open issues from version 00 according to mailing list comments • Open issue: • Need some opinions of strengths (MUSTs and SHOULDs) in requirements • WG item • WGLC soon after
draft-koskelainen-xcon-xcap-cpcp-usage-01.txt • Proposal uses XCAP for CPCP • Comments?
draft-koskelainen-xcon-xcap-cpcp-usage-01.txt • The list of privileges that can be assigned to users in a conference has been trimmed down considerably • Most of the privileges either allow or disallow a user read/write access to certain parts of the CPCP XML document (eg: who can add users to the dial-out list. Adding a user to the dial-out list is achieved by XCAP) • It is envisioned that a new XCAP usage document would provide a solution that CPCP can use. This solution assigns privileges using namespaces • => CPCP XML document was split into many parts using namespaces
What next? • WG item