ALTO Implementations and Use Cases: A Brief Survey
draft-chen-alto-survey-00

Document Type Active Internet-Draft (individual)
Last updated 2018-07-02
Stream (None)
Intended RFC status (None)
Formats plain text 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)
ALTO WG                                                          S. Chen
Internet-Draft                                                    X. Lin
Intended status: Informational                         Tongji University
Expires: January 3, 2019                                       D. Lachos
                                                                 Unicamp
                                                                 Y. Yang
                                                  Tongji/Yale University
                                                           C. Rothenberg
                                                                 Unicamp
                                                            July 2, 2018

           ALTO Implementations and Use Cases: A Brief Survey
                       draft-chen-alto-survey-00

Abstract

   This document provides a comprehensive survey of ALTO, including
   current ALTO implementations and ALTO used in the literature work.
   This document identifies possible challenges and future opportunities
   of ALTO.

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 http://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 3, 2019.

Chen, et al.             Expires January 3, 2019                [Page 1]
Internet-Draft                 ALTO Survey                     July 2018

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
   (http://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
     1.1.  ALTO Background . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Goals and Scope . . . . . . . . . . . . . . . . . . . . .   3
     1.3.  Document Organization . . . . . . . . . . . . . . . . . .   3
   2.  ALTO Implementations  . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Services Implemented in Projects  . . . . . . . . . . . .   3
     2.2.  ALTO in Software Defined Mobile Networks  . . . . . . . .   4
     2.3.  Recognized Issues and Future Work . . . . . . . . . . . .   4
   3.  ALTO in Literature/Use Cases  . . . . . . . . . . . . . . . .   5
     3.1.  Peer Selection  . . . . . . . . . . . . . . . . . . . . .   6
       3.1.1.  Peer Selection in P2P . . . . . . . . . . . . . . . .   6
       3.1.2.  Surrogate Selection in CDN  . . . . . . . . . . . . .   6
       3.1.3.  Downstream CDN Selection in CDNI  . . . . . . . . . .   6
       3.1.4.  Cache Selection in Hybrid CDN-P2P System  . . . . . .   6
       3.1.5.  Mobile Edge Caching . . . . . . . . . . . . . . . . .   7
     3.2.  Path Selection  . . . . . . . . . . . . . . . . . . . . .   7
       3.2.1.  Path Selection in MPTS-AR . . . . . . . . . . . . . .   7
     3.3.  Resource Placement  . . . . . . . . . . . . . . . . . . .   8
       3.3.1.  Virtualized Service Function Chain Placement  . . . .   8
       3.3.2.  Intelligent Virtual Machine Placement . . . . . . . .   8
       3.3.3.  Service Placement in IoT  . . . . . . . . . . . . . .   8
     3.4.  Measure Results Interface . . . . . . . . . . . . . . . .   8
       3.4.1.  An Interface to Query on the LMAP measure results . .   8
   4.  Challenges and Research Opportunities . . . . . . . . . . . .   9
     4.1.  Possible New Address Format . . . . . . . . . . . . . . .   9
     4.2.  Mistrust between entities . . . . . . . . . . . . . . . .   9
     4.3.  Bidirectional Network/Application collaboration . . . . .   9
   5.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   9
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
Show full document text