ALTO-based Broker-assisted Multi-domain Orchestration
draft-lachosrothenberg-alto-brokermdo-02

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02

ALTO WG                                                        D. Lachos
Internet-Draft                                             C. Rothenberg
Intended status: Informational                                   Unicamp
Expires: September 12, 2019                               March 11, 2019

         ALTO-based Broker-assisted Multi-domain Orchestration
                draft-lachosrothenberg-alto-brokermdo-02

Abstract

   Evolving networking scenarios (e.g., 5G) demand new multiple
   administrative domain (aka multi-domain) orchestration models.  This
   document proposes a new broker-plane approach working on top of per-
   domain management and orchestration functions to coordinate the
   delivery of a multi-operator End-to-End Network Service (E2ENS).
   This proposed design resorts to the Application-Layer Traffic
   Optimization (ALTO) protocol to offer topology and resource
   information from different administrative domains.  The ALTO services
   with the proposed protocol extension offer aggregated views on
   various types of resources contributing to a more simple and scalable
   solution.

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 September 12, 2019.

Copyright Notice

   Copyright (c) 2019 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

Lachos & Rothenberg    Expires September 12, 2019               [Page 1]
Internet-Draft    ALTO-based Multi-domain Orchestration       March 2019

   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.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Problem Statement and Challenges  . . . . . . . . . . . . . .   5
   5.  Proposed Approach . . . . . . . . . . . . . . . . . . . . . .   6
     5.1.  Inter-domain Resource (IdR) Component . . . . . . . . . .   7
     5.2.  Inter-domain Topology (IdT) Component . . . . . . . . . .   7
     5.3.  ALTO Server Functionalities . . . . . . . . . . . . . . .   7
     5.4.  Filtered Cost Map Extension . . . . . . . . . . . . . . .   8
       5.4.1.  Accept Input Parameters . . . . . . . . . . . . . . .   8
       5.4.2.  Response  . . . . . . . . . . . . . . . . . . . . . .   9
     5.5.  Examples of Message Exchange  . . . . . . . . . . . . . .   9
       5.5.1.  Property Map Service  . . . . . . . . . . . . . . . .   9
       5.5.2.  Filtered Cost Map Service . . . . . . . . . . . . . .  10
   6.  Discussion  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     6.1.  Benefits  . . . . . . . . . . . . . . . . . . . . . . . .  14
     6.2.  Open Issues . . . . . . . . . . . . . . . . . . . . . . .  14
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  15
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  15
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  15
     10.2.  Informative References . . . . . . . . . . . . . . . . .  16
     10.3.  URIs . . . . . . . . . . . . . . . . . . . . . . . . . .  18
   Appendix A.  Proof of Concept Use Case Implementation . . . . . .  18
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  22

1.  Introduction

   Envisioned 5G network architectures and related service models
   consider broader cooperation between stakeholders in order to provide
   flexible multi-operator multi-domain services.  These multi-provider
   orchestration operations will require the information exchange across
   Multi-domain Orchestrators (MdOs).  The key information to be
   exchanged between MdOs includes the abstract network topology,