Use of IP Router Alert Considered Dangerous
draft-rahman-rtg-router-alert-dangerous-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | David Ward , Reshad Rahman | ||
| Last updated | 2008-10-17 | ||
| 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 provides guidelines to address security concerns which arise with the use of IP Router Alert option [RFC2113] and [RFC2711]. RSVP,[RFC2205] and [RFC3209], and IGMP [RFC3376] are some of the protocols which make use of the IP Router Alert option. IP datagrams carrying the Router Alert option are usually examined in a router's "slow path" and an excess of such datagrams can cause performance degradation or packet drops in a router's "slow path".
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)