Network Slicing with Flexible Traffic Engineering
draft-zzhang-teas-network-slicing-with-flex-te-00

Document Type Active Internet-Draft (individual)
Last updated 2020-07-13
Stream (None)
Intended RFC status (None)
Formats plain text 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)
TEAS                                                            Z. Zhang
Internet-Draft                                                  S. Hegde
Intended status: Standards Track                        Juniper Networks
Expires: January 14, 2021                                       A. Gulko
                                                               Refinitiv
                                                           July 13, 2020

           Network Slicing with Flexible Traffic Engineering
           draft-zzhang-teas-network-slicing-with-flex-te-00

Abstract

   This document specifies procedures and signaling enhancements to
   Flexible Algoirthm to ease provisoning and to scale it better via
   Flexible Traffic Engineering, which is an integration of Flexible
   Algorithm and Segment Routing [RFC8402] Traffic Engineering (SR-TE).

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "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."

   This Internet-Draft will expire on January 14, 2021.

Copyright Notice

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

Zhang, et al.           Expires January 14, 2021                [Page 1]
Internet-Draft            slicing-with-flex-te                 July 2020

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  FlexAlgo Background . . . . . . . . . . . . . . . . . . .   3
     1.2.  Central Provisioning and Signaling of FlexAlgo  . . . . .   4
     1.3.  Flexible Traffic Engineering (FlexTE) and Targeted
           Signaling . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.4.  Traffic Isolation and FlexAlgo/FlexTE . . . . . . . . . .   5
   2.  Specification . . . . . . . . . . . . . . . . . . . . . . . .   6
     2.1.  Southbound BGP-LS Encoding of FAD . . . . . . . . . . . .   6
     2.2.  Southbound BGP-LS Encoding of Link Administrative Group
           Information . . . . . . . . . . . . . . . . . . . . . . .   7
     2.3.  OSPF/ISIS Encoding of Link Administrative Group
           Information for Cetralized Advertisement  . . . . . . . .   7
     2.4.  FlexAlgo and Link AG Signaling from Controllers . . . . .   8
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   [dong-network-slicing-problem-statement] defines Network Slicing
   Problem Statement for IP/MPLS networks.  While Virtual Private
   Networks (VPNs) have been widely deployed to provide many different
   virtual networks on the same physical operator network, and can be
   reused to provide network slicing service to applications, currently
   those VPNs share the same underlay operator network without any
   separation and isolation.

   Multi-Topology Routing (MTR) [RFC4915] [RFC5120] provides a mechanism
   to have a set of independent IP topologies referred to as Multi-
   Topologies (MTs) over the same underlay network.  It can be used to
   provide separation and isolation required by network slicing, though
Show full document text