IPv6 DOTS Signal Option
draft-francois-ipv6-dots-signal-option-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jérôme François , Abdelkader Lahmadi , Giovane Moura , Marco Davids | ||
| Last updated | 2016-09-22 (Latest revision 2016-03-21) | ||
| 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 document describes a delivery mechanism based on the IPv6 Hop- by-Hop options extension header type to carry a DOTS client signal message over a congested network due to a DDoS attack. The specified mechanism allows the DOTS client signal message to be included using an opportunistic way in outgoing IPv6 packets traveling then through the network to reach a DOTS server or relay.
Authors
Jérôme François
Abdelkader Lahmadi
Giovane Moura
Marco Davids
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)