Sign in
Version 5.13.0, 2015-03-25
Report a bug

State Migration

Document type: Expired Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2012-09-05 (latest revision 2012-03-04)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Expired
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found here:


In accompany with the migration of a Virtual Machine (VM), state associated with the VM located on the Hypervisors and the network side devices (e.g., Firewalls) need to be updated in order to guarantee that the services executed on the migrated VM will not be disrupted. VM vendors have their own ways to migrate VM's state on Hypervisors, and so this is out the scope of this draft.This draft introduces the background of state migration on network devices using several application scenarios and tries to specify a clear scope for the future standardization work on state migration on network devices.


Gu Yingjie <>
Chen Li <>
Kai Li <>
Zhuo Zhiqiang <>
Dacheng Zhang <>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)