Multi-domain Service Function Chaining with ALTO
draft-lachos-multi-domain-sfc-alto-00

Document Type Active Internet-Draft (individual)
Last updated 2018-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)
SFC WG                                                         D. Lachos
Internet-Draft                                                   Unicamp
Intended status: Informational                                  Q. Xiang
Expires: January 3, 2019                          Tongji/Yale University
                                                           C. Rothenberg
                                                                 Unicamp
                                                                 Y. Yang
                                                  Tongji/Yale University
                                                            July 2, 2018

            Multi-domain Service Function Chaining with ALTO
                 draft-lachos-multi-domain-sfc-alto-00

Abstract

   Currently, Service Function Chaining (SFC) that span domains with
   different technology, administration or ownership are being defined
   by the SFC WG.  This document focuses on how the Application Layer
   Traffic Optimization (ALTO) protocol can be used to advertise and
   discover abstract topology, resource and service information from
   different domains, and then compute inter-domain service function
   paths.  Another important concern of this draft is to initiate a
   discussion (ALTO, SFC as well as other WGs) regarding if, how, and
   under what conditions ALTO can be useful to improve the multi-domain
   SFC process.

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 RFC 2119 [RFC2119].

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

Lachos, et al.           Expires January 3, 2019                [Page 1]
Internet-Draft         Multi-domain SFC with ALTO              July 2018

   This Internet-Draft will expire on January 3, 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Context and Motivation  . . . . . . . . . . . . . . . . . . .   3
     3.1.  Standardization Activities  . . . . . . . . . . . . . . .   4
     3.2.  Research projects . . . . . . . . . . . . . . . . . . . .   4
   4.  ALTO for Multi-domain SFC . . . . . . . . . . . . . . . . . .   5
     4.1.  Advantages of using ALTO  . . . . . . . . . . . . . . . .   5
       4.1.1.  Inter-domain info discovery with ALTO Property Map  .   6
       4.1.2.  Inter-domain path computation with ALTO Cost Map  . .   6
   5.  Motivating Use Cases  . . . . . . . . . . . . . . . . . . . .   7
     5.1.  ALTO as part of the SFC eXchange Platform . . . . . . . .   7
     5.2.  Resource Orchestration for Multi-Domain, Geo-Distributed
           Data Analytics  . . . . . . . . . . . . . . . . . . . . .   8
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   8.  Summary and Outlook . . . . . . . . . . . . . . . . . . . . .  11
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  11
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  12
     10.2.  Informative References . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   The delivery of end-to-end services often requires various Service
   functions (SFs) or Virtual Network Functions (VNFs).  Service
   Function Chaining (SFC) is constructed as an abstract sequence of SFs
Show full document text