Guidance to limit size of protocol headers in packets
draft-herbert-int-area-limits-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Tom Herbert | ||
| Last updated | 2017-02-11 (Latest revision 2016-08-10) | ||
| 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 specification provides guidance for limiting the size of protocol headers in packets. Intermediate nodes that perform deep packet inspection (DPI), particularly hardware implementations, are often limited as to how many bytes of protocol headers they can process. We recommend that 256 bytes be established as the minimum number of bytes of headers that intermediate nodes are expected to be able to process. This limit is explicitly not intended to be a standard requirement, however it can be used as a guideline in hardware design, protocol design, as well as a useful constraint in implementation or configuration.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)