First-Hop Router Selection by Hosts in a Multi-Prefix Network
RFC 8028, “First-Hop Router Selection by Hosts in a Multi-Prefix Network”, is a Proposed Standard document published in November 2016 by F. Baker, B. Carpenter. It updates RFC 4861. The canonical text is published by the RFC Editor.
Abstract
This document describes expected IPv6 host behavior in a scenario that has more than one prefix, each allocated by an upstream network that is assumed to implement 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. Host behavior in choosing a first-hop router may interact with source address selection in a given implementation. However, the selection of the source address for a packet is done before the first-hop router for that packet is chosen. 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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8028 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8027 DNSSEC Roadblock Avoidance
- RFC 8026 Unified IPv4-in-IPv6 Softwire Customer Premises Equipment : A DHCPv6-Based Prioritization Mechanism
- RFC 8030 Generic Event Delivery Using HTTP Push
- RFC 8025 IPv6 over Low-Power Wireless Personal Area Network Paging Dispatch
- RFC 8031 Curve25519 and Curve448 for the Internet Key Exchange Protocol Version 2 Key Agreement
- RFC 8024 Multi-Chassis Passive Optical Network Protection in MPLS
- RFC 8023 Report from the Workshop and Prize on Root Causes and Mitigation of Name Collisions
- RFC 8022 A YANG Data Model for Routing Management