The CU describes the use of the Read Service including the requirement to support IndexRanges within the reads:
... This includes use of an IndexRange to select a single element or a range of elements when the Attribute value is an array. ...

This CU is used by multiple Profiles and e.g. "Attribute Read Client Facet" and the "AddressSpace Lookup Client Facet". Where the requirement to support IndexRanges does make sense when reading the value to process the data it does not make sense for a client which is only utilizing the Read to show detailed information in a UA browser or to gain additional information about a value e.g. EURanges.

Proposal is to move the IndexRange requirement into a separate CU which then can be included as mandatory in the Attribute Read Client Facet (no difference to the current requirement) but not being listed in the AddressSpace Lookup Client Facet (different from the current requirement).