Using Conditional Router Advertisements for Enterprise Multihoming
draft-linkova-v6ops-conditional-ras-01

Document Type Active Internet-Draft (individual)
Last updated 2017-07-02
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
IPv6 Operations                                               J. Linkova
Internet-Draft                                                    Google
Intended status: Informational                                M. Stucchi
Expires: January 3, 2018                                    July 2, 2017

   Using Conditional Router Advertisements for Enterprise Multihoming
                 draft-linkova-v6ops-conditional-ras-01

Abstract

   This document discusses most common scenarios of connecting an
   enterprise network to multiple ISPs using an address space assigned
   by an ISP.  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.
   [I-D.ietf-rtgwg-enterprise-pa-multihoming] 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 describes how the solution proposed in
   [I-D.ietf-rtgwg-enterprise-pa-multihoming] can be adopted for 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 http://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."

   This Internet-Draft will expire on January 3, 2018.

Linkova & Stucchi        Expires January 3, 2018                [Page 1]
Internet-Draft               Conditional RAs                   July 2017

Copyright Notice

   Copyright (c) 2017 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
   (http://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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Common Enterprise Multihoming Scenarios . . . . . . . . . . .   3
     2.1.  Two ISP Uplinks, Primary and Backup . . . . . . . . . . .   3
     2.2.  Two ISP Uplinks, Used for Load Balancing  . . . . . . . .   4
   3.  Conditional Router Advertisements . . . . . . . . . . . . . .   4
     3.1.  Solution Overview . . . . . . . . . . . . . . . . . . . .   4
       3.1.1.  Uplink Selection  . . . . . . . . . . . . . . . . . .   4
       3.1.2.  Source Address Selection and Conditional RAs  . . . .   4
     3.2.  Example Scenarios . . . . . . . . . . . . . . . . . . . .   6
       3.2.1.  Single Router, Primary/Backup Uplinks . . . . . . . .   6
       3.2.2.  Two Routers, Primary/Backup Uplinks . . . . . . . . .   7
       3.2.3.  Single Router, Load Balancing Between Uplinks . . . .   9
       3.2.4.  Two Router, Load Balancing Between Uplinks  . . . . .  10
       3.2.5.  Topologies with Dedicated Border Routers  . . . . . .  10
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
     5.1.  Privacy Considerations  . . . . . . . . . . . . . . . . .  12
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  12
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  14
Show full document text