Improve interoperability between "in-view" zones and response-policy configuration
A customer has need to use response-policy over multiple views, where one of the primary differentiator between the views is the different response-policy for each view.
Even though the overall response-policy is different between the views, several of the zones in the statements are repeated across all views. These tend to be 3rd party zones that also tend to be quite large.
Currently declaring a zone as "in-view" makes it unable to be used in a response-policy statement, which requires replicating the zone across all of the views, duplicating the data and complicating the transfer configuration.