RFC 8678 on Enterprise Multihoming using Provider-Assigned IPv6 Addresses without Network Prefix Translation: Requirements and Solutions
rfc-editor@rfc-editor.org Thu, 19 December 2019 06:07 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71CD8120091; Wed, 18 Dec 2019 22:07:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 8UgiyfnttEBj; Wed, 18 Dec 2019 22:07:13 -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 E15FF120018; Wed, 18 Dec 2019 22:07:13 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id B2C0AF40723; Wed, 18 Dec 2019 22:06:54 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8678 on Enterprise Multihoming using Provider-Assigned IPv6 Addresses without Network Prefix Translation: Requirements and Solutions
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, rtgwg@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20191219060654.B2C0AF40723@rfc-editor.org>
Date: Wed, 18 Dec 2019 22:06:54 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/dYXGRf7OXQFmtTYDRUva8rWBlmA>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Dec 2019 06:07:15 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8678
Title: Enterprise Multihoming using Provider-Assigned
IPv6 Addresses without Network Prefix Translation:
Requirements and Solutions
Author: F. Baker,
C. Bowers,
J. Linkova
Status: Informational
Stream: IETF
Date: December 2019
Mailbox: FredBaker.IETF@gmail.com,
cbowers@juniper.net,
furry@google.com
Pages: 43
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-rtgwg-enterprise-pa-multihoming-12.txt
URL: https://www.rfc-editor.org/info/rfc8678
DOI: 10.17487/RFC8678
Connecting an enterprise site to multiple ISPs over IPv6 using
provider-assigned addresses is difficult without the use of some form
of Network Address Translation (NAT). Much has been written on this
topic over the last 10 to 15 years, but it still remains a problem
without a clearly defined or widely implemented solution. Any
multihoming solution without NAT requires hosts at the site to have
addresses from each ISP and to select the egress ISP by selecting a
source address for outgoing packets. It also requires routers at the
site to take into account those source addresses when forwarding
packets out towards the ISPs.
This document examines currently available mechanisms for providing a
solution to this problem for a broad range of enterprise topologies.
It covers the behavior of routers to forward traffic by taking into
account source address, and it covers the behavior of hosts to select
appropriate default source addresses. It also covers any possible
role that routers might play in providing information to hosts to
help them select appropriate source addresses. In the process of
exploring potential solutions, this document also makes explicit
requirements for how the solution would be expected to behave from
the perspective of an enterprise site network administrator.
This document is a product of the Routing Area Working Group Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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