A Framework and Problem Statement for Flow-associated Middlebox State Migration
draft-gu-statemigration-framework-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Gu Yingjie , Melinda Shore , Senthil Sivakumar | ||
| Last updated | 2013-04-24 (Latest revision 2012-10-21) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document presents an initial framework and discussion of the problem of transferring middlebox (for example, firewall or NAT) flow-coupled state from one middlebox to another while the flow is still active. This has most recently come up in the context of virtual machine (VM) migration between hypervisors, but it is a problem that has appeared in other situations, as well. We present some of the parameters of the problem, define some language for discussing the problem, and begin to identify a path forward for addressing it.
Authors
Gu Yingjie
Melinda Shore
Senthil Sivakumar
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)