Use of ALTO for Determining Service Edge
draft-contreras-alto-service-edge-00

Document Type Active Internet-Draft (individual)
Last updated 2019-11-04
Stream (None)
Intended RFC status (None)
Formats plain text pdf 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)
ALTO WG                                                    LM. Contreras
Internet-Draft                                                Telefonica
Intended status: Informational                                 D. Lachos
Expires: May 7, 2020                                       C. Rothenberg
                                                                 Unicamp
                                                        November 4, 2019

                Use of ALTO for Determining Service Edge
                  draft-contreras-alto-service-edge-00

Abstract

   Service providers are starting to deploy and interconnect computing
   capabilities across the network for hosting network functions and
   applications.  In distributed computing environments, both computing
   and topological information are necessary in order to determine the
   more convenient infrastructure where to deploy such a service or
   application.  This document raises an initial approach towards the
   use of ALTO to provide such information and assist in the selection
   of proper execution environments.

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 May 7, 2020.

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
   publication of this document.  Please review these documents

Contreras, et al.          Expires May 7, 2020                  [Page 1]
Internet-Draft      ALTO for Determining Service Edge      November 2019

   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.  Computing needs . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Usage of ALTO for determining where to deploy a function or
       application . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Compute information in ALTO . . . . . . . . . . . . . . .   4
     3.2.  Association of compute capabilities to network topology .   4
     3.3.  ALTO architecture for determining serve edge  . . . . . .   5
   4.  Definition of flavors in ALTO property map  . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  Conclusions . . . . . . . . . . . . . . . . . . . . . . . . .   7
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   The advent of virtualization is enabling the operators with a dynamic
   instantiation of network functions and applications by using
   different techniques on top of commoditized computation
   infrastructures, permitting a flexible and on-demand deployment of
   services, aligned with the actual needs observed as demanded by the
   customers.

   Operators are starting to deploy distributed computing environments
   in different parts of the network with the objective of addressing
   the different service needs in terms of latency, bandwidth,
   processing capabilities, etc.  This is translated in the emergence of
   a number of data centers of different sizes (e.g., large, medium,
   small) characterized by distinct dimension of CPUs, memory and
   storage capabilities, as well as bandwidth capacity for forwarding
   the traffic generated in and out the corresponding data center.

   The probable future situation, with the generalization and
   proliferation of the edge computing approach, will increase the
   potential footprint where a function or application can be deployed.
   These different dimensioning rules result in a different unitary cost
   per CPU, memory, and storage in each computing environment because of
Show full document text