Use-case and Requirements for Multi-domain Operation Plane Change
draft-suzuki-teas-actn-multidomain-opc-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Toshiaki Suzuki | ||
| Last updated | 2016-01-06 (Latest revision 2015-07-05) | ||
| 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 provides a use-case and requirements that address the need for facilitating dynamic change of an operation plane, which includes virtually prepared multiple networks and/or data transmission paths, from a current operation one to a backup one during scheduled maintenance or an emergency such as a network disaster. Specifically, the necessity of interfaces to establish consistent end-to-end data transmission paths over multiple domain networks is addressed.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)