RFC 8028: First-Hop Router Selection by Hosts in a Multi-Prefix Network
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8028
- Published
- November 2016
- Authors
- F. Baker; B. Carpenter
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 13
- Also known as
- —
- Updates:
- RFC 4861
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8026Unified IPv4-in-IPv6 Softwire Customer Premises Equipment (CPE): A DHCPv6-Based Prioritization MechanismCurrent
November 2016
- RFC 8025IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) Paging DispatchCurrent
November 2016
- RFC 8021Generation of IPv6 Atomic Fragments Considered HarmfulCurrent
January 2017
- RFC 8039Multipath Time SynchronizationCurrent
December 2016
- RFC 8046Host Mobility with the Host Identity ProtocolCurrent
February 2017
- RFC 8047Host Multihoming with the Host Identity ProtocolCurrent
February 2017
- RFC 8005Host Identity Protocol (HIP) Domain Name System (DNS) ExtensionCurrent
October 2016
- RFC 8004Host Identity Protocol (HIP) Rendezvous ExtensionCurrent
October 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?