RFC 8028 on First-Hop Router Selection by Hosts in a Multi-Prefix Network
rfc-editor@rfc-editor.org Tue, 29 November 2016 02:47 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94F2B12A27D; Mon, 28 Nov 2016 18:47:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.699
X-Spam-Level:
X-Spam-Status: No, score=-105.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mYL5OfC5o90G; Mon, 28 Nov 2016 18:47:40 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCD9112A277; Mon, 28 Nov 2016 18:47:38 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id B11F0B8018E; Mon, 28 Nov 2016 18:47:38 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8028 on First-Hop Router Selection by Hosts in a Multi-Prefix Network
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20161129024738.B11F0B8018E@rfc-editor.org>
Date: Mon, 28 Nov 2016 18:47:38 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/HJLzudW6nm08T9rIjqMRlU13RJg>
Cc: drafts-update-ref@iana.org, ipv6@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Nov 2016 02:47:56 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8028
Title: First-Hop Router Selection by Hosts
in a Multi-Prefix Network
Author: F. Baker, B. Carpenter
Status: Standards Track
Stream: IETF
Date: November 2016
Mailbox: fredbaker.ietf@gmail.com,
brian.e.carpenter@gmail.com
Pages: 13
Characters: 30987
Updates: RFC 4861
I-D Tag: draft-ietf-6man-multi-homed-host-10.txt
URL: https://www.rfc-editor.org/info/rfc8028
DOI: 10.17487/RFC8028
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.
This document is a product of the IPv6 Maintenance Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC