Clarify whether/how navigation restrictions "propagate".

Assume we have

• Order entity related to single Customer entity
• Customer entity related to multiple Address entities
• a navigation restriction on Customers entity set which lists Addresses as filterable:false.

Now a client knows that it cannot filter Customers by Addresses.

Should a client assume that it also cannot filter Orders by Customer/Addresses?

Or would the service have to explicitly declare navigation restrictions for all entity sets with navigation paths ending in Customer/Addresses?