An Architecture for Network Function Interconnect
draft-bookham-rtgwg-nfix-arch-01

Document Type Active Internet-Draft (individual)
Last updated 2020-06-24
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized 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)
RTG Working Group                                        C. Bookham, Ed.
Internet-Draft                                                  A. Stone
Intended status: Informational                                     Nokia
Expires: December 26, 2020                                   J. Tantsura
                                                                  Apstra
                                                              M. Durrani
                                                             Equinix Inc
                                                             B. Decraene
                                                                  Orange
                                                           June 24, 2020

           An Architecture for Network Function Interconnect
                    draft-bookham-rtgwg-nfix-arch-01

Abstract

   The emergence of technologies such as 5G, the Internet of Things
   (IoT), and Industry 4.0, coupled with the move towards network
   function virtualization, means that the service requirements demanded
   from networks are changing.  This document describes an architecture
   for a Network Function Interconnect (NFIX) that allows for
   interworking of physical and virtual network functions in a unified
   and scalable manner across wide-area network and data center domains
   while maintaining the ability to deliver against SLAs.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in BCP 14
   [RFC2119][RFC8174] when, and only when, they appear in all capitals,
   as shown here.

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

Bookham, et al.         Expires December 26, 2020               [Page 1]
Internet-Draft        Network Function Interconnect            June 2020

   This Internet-Draft will expire on December 26, 2020.

Copyright Notice

   Copyright (c) 2020 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
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Theory of Operation . . . . . . . . . . . . . . . . . . . . .   7
     5.1.  VNF Assumptions . . . . . . . . . . . . . . . . . . . . .   7
     5.2.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   8
     5.3.  Use of a Centralized Controller . . . . . . . . . . . . .   9
     5.4.  Routing and LSP Underlay  . . . . . . . . . . . . . . . .  11
       5.4.1.  Intra-Domain Routing  . . . . . . . . . . . . . . . .  11
       5.4.2.  Inter-Domain Routing  . . . . . . . . . . . . . . . .  13
       5.4.3.  Intra-Domain and Inter-Domain Traffic-Engineering . .  14
     5.5.  Service Layer . . . . . . . . . . . . . . . . . . . . . .  17
     5.6.  Service Differentiation . . . . . . . . . . . . . . . . .  19
     5.7.  Automated Service Activation  . . . . . . . . . . . . . .  20
     5.8.  Service Function Chaining . . . . . . . . . . . . . . . .  21
     5.9.  Stability and Availability  . . . . . . . . . . . . . . .  23
       5.9.1.  IGP Reconvergence . . . . . . . . . . . . . . . . . .  23
       5.9.2.  Data Center Reconvergence . . . . . . . . . . . . . .  23
       5.9.3.  Exchange of Inter-Domain Routes . . . . . . . . . . .  24
       5.9.4.  Controller Redundancy . . . . . . . . . . . . . . . .  24
       5.9.5.  Path and Segment Liveliness . . . . . . . . . . . . .  26
     5.10. Scalability . . . . . . . . . . . . . . . . . . . . . . .  28
       5.10.1.  Asymmetric Model B for VPN Families  . . . . . . . .  30
Show full document text