1. Proposed title of this feature request  

Making a spice session persistent across client network changes
      
    3. What is the nature and description of the request?  
      
The desired behaviour would be t have a spice session be persistent across changes happening in the client network connection (e.g. when switching from wired to wireless on a laptop).

    4. Why does the customer need this? (List the business requirements here)  

It's not uncommon that users switch from working at their desk with the laptop inserted in the docking station to joining a meeting and hence being connected to the wireless network. It's very annoying and  inconvenient to have to restart the console when un-docking the laptop and moving to the wifi or vice-versa.
At our company a lot of people stay on wifi due to the fact that they need to reconnect every time when they switch between wired and wifi.
This has the drawback that when the wifi connection deteriorates the vdi-session experience receives a negative impact.
Also the competitor's virtualization environment we have also in our environment is capable of performing this feature, this is used as an argument against RHEV.
To improve the RHEV acceptance in our company this feature would definitely help.

    5. How would the customer like to achieve this? (List the functional requirements here)  

The user should be required to open the guest console only once until the session remains valid, even if they switch the client network in the meantime.
      
    6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.  

1. Open a spice session to a guest on a laptop connected to the wired network.
2. Switch to the wireless network that implies a network address change
3. Verify that the console is still functioning without the need to re-launch it. 
   
    7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

None found.
      
    8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  

As soon as possible. This issue is already biting production users.
      
    9. Is the sales team involved in this request and do they have any additional input?

No  
      
    10. List any affected packages or components.

- virt-viewer
- vdsm

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

Yes