Ingress Filtering, Site Multihoming, and Source Address Selection
draft-draves-ipngwg-ingress-filtering-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Richard P. Draves | ||
| Last updated | 2001-05-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 draft discusses some issues surrounding ingress filtering by IPs, site multihoming, and source address selection. The problem is that in a site which has prefixes from multiple ISPs, the source address selected by a host might be inconsistent with the egress ISP for a particular destination address. If the ISP deploys source- address-based ingress filtering, the host will be unable to communicate with the destination. The draft proposes some possible approaches towards a solution.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)