Indefensible Neighbor Discovery
draft-jaeggli-v6ops-indefensible-nd-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Joel Jaeggli | ||
| Last updated | 2019-01-03 (Latest revision 2018-07-02) | ||
| 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
NDP resource exhastion is a problem which cannot fundamently be addressed through limited protocol changes or implementation tweaks; mitigations proposed in RFC 6583 [RFC6583] may well prevent the outright failure of a device under duress. This draft discusses some mitigations which have or can be employeed by networks looking to reduce or eliminate the exposure of the Neighbor Discovery Process.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)