Packet loss resiliency for Router Solicitations
draft-krishnan-6man-resilient-rs-01
| Document | Type |
Replaced Internet-Draft
(6man WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Suresh Krishnan , Dmitry Anipko , Dave Thaler | ||
| Last updated | 2013-05-10 (Latest revision 2012-07-16) | ||
| Replaced by | draft-ietf-6man-resilient-rs | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-6man-resilient-rs | |
| Consensus boilerplate | Unknown | ||
| 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
When an interface on a host is initialized, the host transmits Router Solicitations in order to minimize the amount of time it needs to wait until the next unsolicited multicast Router Advertisement is received. In certain scenarios, these router solicitations transmitted by the host might be lost. This document specifies a mechanism for hosts to cope with the loss of the initial Router Solicitations. Furthermore, on some links, unsolicited multicast Router Advertisements are never sent and the mechanism in this document is intended to work even in such scenarios.
Authors
Suresh Krishnan
Dmitry Anipko
Dave Thaler
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)