The case against Hop-by-Hop options
draft-krishnan-ipv6-hopbyhop-05
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2010-10-22 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-krishnan-ipv6-hopbyhop-05.txt
https://www.ietf.org/archive/id/draft-krishnan-ipv6-hopbyhop-05.txt
Abstract
The Hop-by-Hop option header is a type of IPv6 extension header that has been defined in the IPv6 protocol specification. The contents of this header need to be processed by every node along the path of an IPv6 datagram.This draft highlights the characteristics of this extension header which make it prone to Denial of Service attacks and proposes solutions to minimize such attacks.
Authors
Suresh Krishnan (suresh.krishnan@ericsson.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)