Loosen the specification for java.security.SecurityPermission, java.lang.RuntimePermission, and javax.security.auth.AuthPermission to explicitly allow for other named permissions to be used.

The current specification of these classes states "The following table lists all the possible SecurityPermission target names ..." and "The following table lists all the possible RuntimePermission target names ..." which implies that unless the permission target is listed in the table, it cannot be used.

However, there is no such enforcement in the implementation, and it is useful and somewhat common for applications/libraries to create their own permission target names.

We should relax the specification and provide recommendations for naming to avoid name clashes (example, use the reversed domain name syntax).