Experience from implementing a new packet discard classification scheme
draft-evans-discardclass-03
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | John Evans , Oleksandr Pylypenko | ||
| Last updated | 2023-08-15 | ||
| Replaced by | draft-opsawg-evans-discardmodel | ||
| 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-opsawg-evans-discardmodel | |
| 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
Router reported packet loss is the primary signal of when a network is not doing its job. Some packet loss is normal or intended in TCP/ IP networks, however. To minimise network packet loss through automated network operations we need clear and accurate signals of all packets which are dropped and why. This document describes our experience from implementing a packet loss classification scheme to provide these signals and enable automated network mitigation of unintended packet loss.
Authors
John Evans
Oleksandr Pylypenko
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)