Host routing in a multi-prefix network
draft-baker-6man-multi-homed-host-03
| Document | Type | Replaced Internet-Draft (6man WG) | |
|---|---|---|---|
| Authors | Fred Baker , Brian Carpenter | ||
| Last updated | 2015-10-14 (latest revision 2015-09-03) | ||
| Replaced by | RFC 8028 | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-6man-multi-homed-host | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-baker-6man-multi-homed-host-03.txt
Abstract
This note describes expected IPv6 host behavior in a network that has more than one prefix, each allocated by an upstream network that implements BCP 38 ingress filtering, when the host has multiple routers to choose from. It also applies to other scenarios such as the usage of stateful firewalls that effectively act as address-based filters. This host behavior may interact with source address selection in a given implementation, but logically follows it. Given that the network or host is, or appears to be, multihomed with multiple provider-allocated addresses, that the host has elected to use a source address in a given prefix, and that some but not all neighboring routers are advertising that prefix in their Router Advertisement Prefix Information Options, this document specifies to which router a host should present its transmission. It updates RFC 4861.
Authors
Fred Baker
(fred@cisco.com)
Brian Carpenter
(brian.e.carpenter@gmail.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)