RIFT -- Motivation, Additional Requirements and Use Cases in User Access Networks
draft-filyurin-rift-access-networks-00

Document Type Active Internet-Draft (individual)
Last updated 2018-06-13
Stream (None)
Intended RFC status (None)
Formats plain text 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)
RIFT Working Group                                      Y. Filyurin, Ed.
Internet-Draft                                              Bloomberg LP
Intended status: Informational                             June 13, 2018
Expires: December 15, 2018

RIFT -- Motivation, Additional Requirements and Use Cases in User Access
                                Networks
                 draft-filyurin-rift-access-networks-00

Abstract

   RIFT is a new specialized dynamic routing protocol originally
   designed for Clos and Fat Tree Data Center networks.  It is designed
   to work on multilevel network topologies in which nodes in certain
   level will only connect to nodes in one upper or lower level with
   optional and non-contiguous intra-level connectivity.

   While the protocol was originally designed to meet the needs of
   Massively Scalable Data Centers, its ability to automatically prune
   the information distribution from higher levels to lower levels, as
   well as provide optimal routing for intra and inter-level traffic
   makes it a good match for user access networks, or any network that
   combines end user access and various compute enabling various network
   service for these end users.  Current directions in distributed
   computing seek to blur even that distinction.  Large distributed
   networks can be created, where virtual compute units can be in all
   tiers, combining and crossing many requirements for DC or User Access
   design.  This draft seeks to analyze these requirements.

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."

   This Internet-Draft will expire on December 15, 2018.

Filyurin                Expires December 15, 2018               [Page 1]
Internet-Draft                     XX                          June 2018

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.  Definitions of Terms Used in This Memo  . . . . . . . . . . .   2
   2.  Authors . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Additional Requirements for RIFT Access Networks  . . . . . .   4
   5.  Network Slicing . . . . . . . . . . . . . . . . . . . . . . .   4
     5.1.  Overall Network Slicing . . . . . . . . . . . . . . . . .   5
     5.2.  Identification and Propagation of Slice Information . . .   5
     5.3.  Network Instances and RIB and FIB Requirement . . . . . .   6
     5.4.  Network Instances and Control Plane . . . . . . . . . . .   7
     5.5.  Network Instances and Forwarding  . . . . . . . . . . . .   9
   6.  External Routing Information  . . . . . . . . . . . . . . . .  10
   7.  RIFT and Endpoint Address Mobility  . . . . . . . . . . . . .  11
     7.1.  Mobility Use Cases  . . . . . . . . . . . . . . . . . . .  11
   8.  Border Nodes and Superspine East/West traffic . . . . . . . .  12
   9.  Border Nodes and Superspine East/West traffic . . . . . . . .  13
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  14
   11. Conclusions . . . . . . . . . . . . . . . . . . . . . . . . .  14
   12. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
   13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  15
   14. References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     14.1.  Normative References . . . . . . . . . . . . . . . . . .  15
     14.2.  Informative References . . . . . . . . . . . . . . . . .  15
     14.3.  URIs . . . . . . . . . . . . . . . . . . . . . . . . . .  16
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  16

1.  Definitions of Terms Used in This Memo

   MSDC -   Massively Scalable Data Center

   IGP -   Interior Gateway Protocol

Show full document text