Operational Issues Associated With Long IPv6 Header Chains
draft-wkumari-long-headers-02
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Warren "Ace" Kumari , Joel Jaeggli , Ron Bonica | ||
| Last updated | 2014-04-24 (Latest revision 2013-10-21) | ||
| RFC stream | (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 memo specifies requirements for IPv6 forwarders as they process packets with long header chains. It also provides guidance for application developers whose applications might rely on long headers chains. As background, this memo explains how many ASIC-based IPv6 forwarders process packets and why processing of packets with long header chains might be problematic.
Authors
Warren "Ace" Kumari
Joel Jaeggli
Ron Bonica
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)