<p dir="ltr">This RFC specifies how a host can use IPv6 RA Prefix Information Options to influence host source address selection and first hop router selection when there are multiple first hop routers in a multi-homed network.</p>
<p dir="ltr">This could be seen as the routing system providing hints to hosts on the topology of the network, so that hosts can pick a router that will give them better service, and a source address that will pass through upstream BCP38 filters or middleboxes that effectively filter on source addresses such as network firewalls.</p>
<div class="gmail_quote">---------- Forwarded message ----------<br>From: <<a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>><br>Date: 29 Nov. 2016 13:49<br>Subject: RFC 8028 on First-Hop Router Selection by Hosts in a Multi-Prefix Network<br>To: <<a href="mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>>, <<a href="mailto:rfc-dist@rfc-editor.org">rfc-dist@rfc-editor.org</a>><br>Cc: <<a href="mailto:drafts-update-ref@iana.org">drafts-update-ref@iana.org</a>>, <<a href="mailto:ipv6@ietf.org">ipv6@ietf.org</a>>, <<a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>><br><br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">A new Request for Comments is now available in online RFC libraries.<br>
<br>
<br>
RFC 8028<br>
<br>
Title: First-Hop Router Selection by Hosts<br>
in a Multi-Prefix Network<br>
Author: F. Baker, B. Carpenter<br>
Status: Standards Track<br>
Stream: IETF<br>
Date: November 2016<br>
Mailbox: <a href="mailto:fredbaker.ietf@gmail.com">fredbaker.ietf@gmail.com</a>,<br>
<a href="mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a><br>
Pages: 13<br>
Characters: 30987<br>
Updates: RFC 4861<br>
<br>
I-D Tag: draft-ietf-6man-multi-homed-<wbr>host-10.txt<br>
<br>
URL: <a href="https://www.rfc-editor.org/info/rfc8028" rel="noreferrer" target="_blank">https://www.rfc-editor.org/<wbr>info/rfc8028</a><br>
<br>
DOI: 10.17487/RFC8028<br>
<br>
This document describes expected IPv6 host behavior in a scenario<br>
that has more than one prefix, each allocated by an upstream network<br>
that is assumed to implement BCP 38 ingress filtering, when the host<br>
has multiple routers to choose from. It also applies to other<br>
scenarios such as the usage of stateful firewalls that effectively<br>
act as address-based filters. Host behavior in choosing a first-hop<br>
router may interact with source address selection in a given<br>
implementation. However, the selection of the source address for a<br>
packet is done before the first-hop router for that packet is chosen.<br>
Given that the network or host is, or appears to be, multihomed with<br>
multiple provider-allocated addresses, that the host has elected to<br>
use a source address in a given prefix, and that some but not all<br>
neighboring routers are advertising that prefix in their Router<br>
Advertisement Prefix Information Options, this document specifies to<br>
which router a host should present its transmission. It updates RFC<br>
4861.<br>
<br>
This document is a product of the IPv6 Maintenance Working Group of the IETF.<br>
<br>
This is now a Proposed Standard.<br>
<br>
STANDARDS TRACK: This document specifies an Internet Standards Track<br>
protocol for the Internet community, and requests discussion and suggestions<br>
for improvements. Please refer to the current edition of the Official<br>
Internet Protocol Standards (<a href="https://www.rfc-editor.org/standards" rel="noreferrer" target="_blank">https://www.rfc-editor.org/<wbr>standards</a>) for the<br>
standardization state and status of this protocol. Distribution of this<br>
memo is unlimited.<br>
<br>
This announcement is sent to the IETF-Announce and rfc-dist lists.<br>
To subscribe or unsubscribe, see<br>
<a href="https://www.ietf.org/mailman/listinfo/ietf-announce" rel="noreferrer" target="_blank">https://www.ietf.org/mailman/<wbr>listinfo/ietf-announce</a><br>
<a href="https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist" rel="noreferrer" target="_blank">https://mailman.rfc-editor.<wbr>org/mailman/listinfo/rfc-dist</a><br>
<br>
For searching the RFC series, see <a href="https://www.rfc-editor.org/search" rel="noreferrer" target="_blank">https://www.rfc-editor.org/<wbr>search</a><br>
For downloading RFCs, see <a href="https://www.rfc-editor.org/retrieve/bulk" rel="noreferrer" target="_blank">https://www.rfc-editor.org/<wbr>retrieve/bulk</a><br>
<br>
Requests for special distribution should be addressed to either the<br>
author of the RFC in question, or to <a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>. Unless<br>
specifically noted otherwise on the RFC itself, all RFCs are for<br>
unlimited distribution.<br>
<br>
<br>
The RFC Editor Team<br>
Association Management Solutions, LLC<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>--------<br>
IETF IPv6 working group mailing list<br>
<a href="mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
Administrative Requests: <a href="https://www.ietf.org/mailman/listinfo/ipv6" rel="noreferrer" target="_blank">https://www.ietf.org/mailman/<wbr>listinfo/ipv6</a><br>
------------------------------<wbr>------------------------------<wbr>--------<br>
</blockquote></div>