title: How to organize Istio rate limiting policy configuration
body: <p>Let me present a usecase for various independant teams deploying to a single cluster
  Team A is responsible for servics A1, A2, A3
  Team B is responsible for servics B1, B2, B3</p>
  
  <p>They both intend to apply custom Rate Limiting to their services. My Question is: </p>
  
  <p>Should/Could they both define completely different config(consisting of the following 5 yalm spec) or is part of it common? At the very least, I'm guessing the "quota instance" could be shared while the rest could be different.</p>
  
  <p>From the istio site ( <a href="https://istio.io/docs/tasks/policy-enforcement/rate-limiting/#rate-limits" rel="nofollow noreferrer">https://istio.io/docs/tasks/policy-enforcement/rate-limiting/#rate-limits</a> ) , the config is split into </p>
  
  <ul>
  <li>Client Side
  
  <ul>
  <li>QuotaSpec defines quota name and amount that the client should request.</li>
  <li>QuotaSpecBinding conditionally associates QuotaSpec with one or more services.</li>
  </ul></li>
  <li>Mixer Side
  
  <ul>
  <li>quota instance defines how quota is dimensioned by Mixer.</li>
  <li>memquota handler defines memquota adapter configuration.</li>
  <li>quota rule defines when quota instance is dispatched to t</li>
  </ul></li>
  </ul>