[XCON] CPCP Issue 24: Meta Policy as separate document
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[XCON] CPCP Issue 24: Meta Policy as separate document
Many actions are defined that dictate the privileges for users in a conference:
<allow-modify-settings>
<allow-modify-information>
<allow-modify-time>
<allow-modify-authorization-rules>
<allow-modify-dol>
<allow-modify-rl>
<allow-modify-sc>
<allow-modify-fp>
<allow-modify-ms>
<allow-sidebar>
<allow-modify-dil>
Should such a policy be defined in a separate document?
The separate document indicates the privileged users and their privileges.
Advantages:
- Reduces conference policy complexity
- Separates the manipulation rules of the conference policy from the conference policy itself
Disadvantages:
- Many of the conditions have to be repeated in this new document. For example: <has-been-in-conference>. Or should this just be using identity? (I.e. privileges are only assigned for identities)
- A user has to create and manipulate 2 documents.
There was no objection to separating the document. Also the proposal that meta policy will use only identities had no objections
Regards,
Hisham
_______________________________________________
XCON mailing list
XCON at ietf.org
https://www1.ietf.org/mailman/listinfo/xcon
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.