Using Conditional Router Advertisements for Enterprise Multihoming
draft-ietf-v6ops-conditional-ras-08

Document Type Active Internet-Draft (v6ops WG)
Last updated 2018-08-30 (latest revision 2018-08-21)
Replaces draft-linkova-v6ops-conditional-ras
Stream IETF
Intended RFC status Informational
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Russ White
Shepherd write-up Show (last changed 2018-07-31)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Warren Kumari
Send notices to Russ White <russ@riw.us>
IANA IANA review state IANA OK - No Actions Needed
IANA action state No IANA Actions
RFC Editor RFC Editor state RFC-EDITOR
IPv6 Operations                                               J. Linkova
Internet-Draft                                                    Google
Intended status: Informational                                M. Stucchi
Expires: February 22, 2019                                      RIPE NCC
                                                         August 21, 2018

   Using Conditional Router Advertisements for Enterprise Multihoming
                  draft-ietf-v6ops-conditional-ras-08

Abstract

   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 the "ietf-rtgwg-
   enterprise-pa-multihoming" draft 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 "ietf-rtgwg-enterprise-pa-
   multihoming" document proposes a solution to this problem by
   introducing a new routing functionality (Source Address Dependent
   Routing) to solve the uplink selection issue and using Router
   Advertisements to influence the host source address selection.  While
   the above-mentioned document focuses on solving the general problem
   and on covering various complex use cases, this document adopts the
   approach proposed in the "ietf-rtgwg-enterprise-pa-multihoming" draft
   to provide a solution for a limited number of common use cases.  In
   particular, the focus is on scenarios where 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 RFC8028.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Linkova & Stucchi       Expires February 22, 2019               [Page 1]
Internet-Draft               Conditional RAs                 August 2018

   This Internet-Draft will expire on February 22, 2019.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   2.  Common Enterprise Multihoming Scenarios . . . . . . . . . . .   4
     2.1.  Two ISP Uplinks, Primary and Backup . . . . . . . . . . .   4
     2.2.  Two ISP Uplinks, Used for Load Balancing  . . . . . . . .   5
   3.  Conditional Router Advertisements . . . . . . . . . . . . . .   5
     3.1.  Solution Overview . . . . . . . . . . . . . . . . . . . .   5
       3.1.1.  Uplink Selection  . . . . . . . . . . . . . . . . . .   5
       3.1.2.  Source Address Selection and Conditional RAs  . . . .   5
     3.2.  Example Scenarios . . . . . . . . . . . . . . . . . . . .   8
       3.2.1.  Single Router, Primary/Backup Uplinks . . . . . . . .   8
       3.2.2.  Two Routers, Primary/Backup Uplinks . . . . . . . . .   9
       3.2.3.  Single Router, Load Balancing Between Uplinks . . . .  12
       3.2.4.  Two Router, Load Balancing Between Uplinks  . . . . .  12
       3.2.5.  Topologies with Dedicated Border Routers  . . . . . .  13
       3.2.6.  Intra-Site Communication during Simultaneous Uplinks
               Outage  . . . . . . . . . . . . . . . . . . . . . . .  15
       3.2.7.  Uplink Damping  . . . . . . . . . . . . . . . . . . .  15
       3.2.8.  Routing Packets when the Corresponding Uplink is
               Unavailable . . . . . . . . . . . . . . . . . . . . .  16
     3.3.  Solution Limitations  . . . . . . . . . . . . . . . . . .  16
Show full document text