anchor.diff:  OK
   </pre>
   
  -###<a name="list-policies"></a>List Policies
  +### <a name="list-policies"></a> List Policies
   
   You can list all the policies in your space, or just the policies for which a single app is the source:
   
  
positive.code: 
  <% if vars.product_name.include? "CF" %>
  
  ###<a name="grant"></a>Grant Permissions
  
  CF admins use the following UAA scopes to grant specific users or groups permissions to configure network policies:
  
  
negative.code: OK
  </pre>
  
  
  ## <a name="discovery"></a> App Service Discovery
  
  When app service discovery is enabled, apps pushed to <%= vars.product_full %> can establish container-to-container communications through a known route served by internal BOSH DNS. This allows front end apps to easily connect with back end apps.
  
  To establish container-to-container communications between a front end and back end app, a developer:
  
  1. Launches a back-end app that publishes a local endpoint.
  1. Maps a named route to the endpoint.
  1. Creates a network policy that allows direct traffic from the front-end to the back-end app.
  1. Launches the front-end app.
  
  See [Cats and Dogs with Service Discovery](https://github.com/cloudfoundry/cf-networking-examples/blob/master/docs/c2c-with-service-discovery.md) in GitHub for an example, written in Go, that demonstrates communication between front end and back end apps.
  
  <% if vars.product_name.include? "CF" %>
  
  ### <a name="enable-discovery"></a> Enable App Service Discovery
  
  To enable app service discovery, <%= vars.enable_c2c_discovery %>.
  
  