Multiprefix IPv6 Routing for Ingress Filters
draft-baker-6man-multiprefix-default-route-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Fred Baker | ||
| Last updated | 2007-11-07 | ||
| 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 note addresses routing in a network that supports multiple prefixes and has different DMZs, in the context of BCPs 38 and 84 (ingress filtering). It proposes a change to the way IPv6 forwarding occurs, and so should be considered carefully by the Internet community.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)