Restrict linking and creation of extended auxiliary resources

There is a gap in the spec that would allow auxiliary resources to have their own Resource Description or Web Access Control auxiliary resources. Neither the lifecycle or the access controls on the extended auxiliary resources are prescribed. Until there are significant use cases for open-ended linking of auxiliary resources, and in order to restrict server implementations to be in a situation without conformance criteria to go with, we need to prescribe (something along these lines):

Servers MUST NOT use a link relation to advertise a Resource Description or Web Access Control auxiliary resource for auxiliary resources.

Shape auxiliary resources are necessary for Resource Description and Web Access Control auxiliary resources. Unless there is a significant use case for Shape Validation auxiliary resources to have their own Shape Validation auxiliary resources, I'd also suggest:

Servers MUST NOT use a link relation to advertise a Shape Validation auxiliary resource for other Shape Validation auxiliary resources.

Start by reading the specification sections that define auxiliary resources, Resource Description, Web Access Control, and Shape Validation links. Check whether the proposed prohibitions cover each auxiliary-resource type and whether significant use cases or conformance criteria are documented; done means the specification contains an agreed normative restriction or a recorded rationale for not adding one.