ISSU Benchmarking Methodology
draft-banks-bmwg-issu-meth-05
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Sarah Banks , Fernando Calabria , Gery Czirjak , Ramdas Machat | ||
| Last updated | 2015-04-11 (Latest revision 2014-10-08) | ||
| Replaced by | RFC 7654 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-bmwg-issu-meth | |
| 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
Modern forwarding devices attempt to minimize any control and data plane disruptions while performing planned software changes, by implementing a technique commonly known as an In Service Software Upgrade (ISSU). This document specifies a set of common methodologies and procedures designed to characterize the overall behavior of a Device Under Test (DUT), subject to an ISSU event.
Authors
Sarah Banks
Fernando Calabria
Gery Czirjak
Ramdas Machat
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)