The acl:Control mode indicates the user/role who has permission to modify an ACL. As it is part of the SOLID WAC spec, it needs to be implemented.
According to the SOLID/WAC: acl:Control is a special-case access mode that gives an agent the ability to view and modify the ACL of a resource. Note that it doesn't automatically imply that the agent has acl:Read or acl:Write access to the resource itself, just to its corresponding ACL document. For example, a resource owner may disable their own Write access (to prevent accidental over-writing of a resource by an app), but be able to change their access levels at a later point (since they retain acl:Control access).
Thus for this ticket to be consider complete the following must be true:
1. In order to view, create or modify an ACL Resource (ACL A) of a given Resource (Resource B) , the client must have acl:Control permission on Resource B.
2. If the previous test fails, a 403 (Forbidden) code should be returned.