[v6ops] RFC 8475 on Using Conditional Router Advertisements for Enterprise Multihoming

rfc-editor@rfc-editor.org Sat, 13 October 2018 00:49 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDFAA130EEE; Fri, 12 Oct 2018 17:49:32 -0700 (PDT)
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 lRl-YKjNpk5F; Fri, 12 Oct 2018 17:49:30 -0700 (PDT)
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 966D7130EF6; Fri, 12 Oct 2018 17:49:30 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 67CD6B817C0; Fri, 12 Oct 2018 17:49:10 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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, v6ops@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20181013004910.67CD6B817C0@rfc-editor.org>
Date: Fri, 12 Oct 2018 17:49:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ZTaKt5pfvSwRM1iTz2iSzZLPu5c>
Subject: [v6ops] RFC 8475 on Using Conditional Router Advertisements for Enterprise Multihoming
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Oct 2018 00:49:45 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8475

        Title:      Using Conditional Router Advertisements for 
                    Enterprise Multihoming 
        Author:     J. Linkova, 
                    M. Stucchi
        Status:     Informational
        Stream:     IETF
        Date:       October 2018
        Mailbox:    furry@google.com, 
                    mstucchi@ripe.net
        Pages:      21
        Characters: 45127
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-v6ops-conditional-ras-08.txt

        URL:        https://www.rfc-editor.org/info/rfc8475

        DOI:        10.17487/RFC8475

This document discusses the most common scenarios of connecting an
enterprise network to multiple ISPs using an address space assigned
by an ISP and how the approach proposed in "Enterprise Multihoming                         
using Provider-Assigned Addresses without Network Prefix Translation:                      
Requirements and Solution" could be applied in those scenarios.  The
problem of enterprise multihoming without address translation of any
form has not been solved yet as it requires both the network to
select the correct egress ISP based on the packet source address and
hosts to select the correct source address based on the desired
egress ISP for that traffic.  The aforementioned document proposes a
solution to this problem by introducing a new routing functionality
(Source Address Dependent Routing) to solve the uplink selection
issue.  It also proposes using Router Advertisements to influence the
host source address selection.  It focuses on solving the general
problem and covering various complex use cases, and this document
adopts its proposed approach to provide a solution for a limited
number of common use cases.  In particular, the focus of this
document is on scenarios in which an enterprise network has two
Internet uplinks used either in primary/backup mode or simultaneously
and hosts in that network might not yet properly support multihoming
as described in RFC 8028.

This document is a product of the IPv6 Operations 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