1. What is the nature and description of the request?
   Add an additional Fencing domain besides Cluster, DC and Other DC to RHEV-M

2. Why does the customer need this? (List the business requirements here)
   As RHEV-M already decides if a host should be fenced, it could also act as a proxy for that action as well.
   Additionally it will simplify firewall setups in some scenarios as well.

3. How would the customer like to achieve this? (List the functional requirements here)  
   Add a fourth Proxy Domain for fencing to the existing ones.
   So we would finally have:
   * RHEV-M
   * Cluster
   * DC
   * other DC
   There is no need to change the defaults. So by default the Order stays as is:
   * Cluster
   * DC

4. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.  
   Only have RHEV-M as fencing proxy and check if a fencing action work.

5. Is there already an existing RFE upstream or in Red Hat Bugzilla?  
   No.

6. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  
   Best within RHEV 3.6 lifecycle

7. Is the sales team involved in this request and do they have any additional input?  
   No

8. List any affected packages or components.  
   * fencing-agents need to be installed on RHEV-M
   * ovirt-engine

9. Would the customer be able to assist in testing this functionality if implemented?  
   Yes