Limits on Sending and Processing IPv6 Extension Headers
draft-ietf-6man-eh-limits-19
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Tom Herbert | ||
| Last updated | 2025-11-02 (Latest revision 2025-02-27) | ||
| RFC stream | (None) | ||
| Intended RFC status | Informational | ||
| Formats | |||
| Reviews |
INTDIR Telechat review
by Jean-Michel Combes
Almost ready
TSVART Telechat review
(of
-18)
by Gorry Fairhurst
Ready w/issues
GENART IETF Last Call review
(of
-17)
by Peter Yee
Ready w/nits
ARTART IETF Last Call review
(of
-16)
by John Levine
Ready w/nits
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | No | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | Erik Kline | ||
| Send notices to | suresh.krishnan@gmail.com | ||
| IANA | IANA review state | IANA OK - No Actions Needed |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document defines various limits that may be applied to receiving, sending, and otherwise processing packets that contain IPv6 extension headers. Limits are pragmatic to facilitate interoperability amongst hosts and routers, thereby increasing the deployability of extension headers. The limits described herein establish the minimum baseline of support for use of extension headers on the Internet. If it is known that all communicating parties for a particular communication, including destination hosts and any routers in the path, are capable of supporting more than the baseline then these default limits may be freely exceeded.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)