Conflicting statements for the configuration entities removal in the DASH design considerations

[aputriax]

DASH HLD design consideration contains the following statements:

11. During VNET or ENI delete, implementation must support ability to delete all mappings or routes in a single API call.
12. Add and Delete APIs are idempotent. As an example, deleting an object that doesn't exists shall not return an error.
13. During a delete operation, if there is a dependency (E.g. mappings still present when a VNET is deleted), implementation shall return error and shall not perform any force-deletions or delete dependencies implicitly.

Looks like 11 conflicts with 13. Should we allow deletion of ENI if mappings exist or return SAI_STATUS_OBJECT_IN_USE?

FYI: BMv2 allows deletion of ENI in this case but then it does not conform with requirement 12 since it fails on the additional deletion attempt.