State Migration
draft-gu-opsawg-policies-migration-02

 
Document Type Expired Internet-Draft (individual)
Last updated 2012-09-05 (latest revision 2012-03-04)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-gu-opsawg-policies-migration-02.txt

Abstract

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.

Authors

Gu Yingjie (guyingjie@huawei.com)
Chen Li (lichenyj@chinamobile.com)
Kai Li (leekai@ctbri.com.cn)
Zhuo Zhiqiang (zhuozq@ruijie.com.cn)
Dacheng Zhang (zhangdacheng@huawei.com)

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