ALTO Performance Cost Metrics
draft-ietf-alto-performance-metrics-08

Document Type Active Internet-Draft (alto WG)
Last updated 2019-11-04
Replaces draft-wu-alto-te-metrics
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
ALTO Working Group                                                 Q. Wu
Internet-Draft                                                    Huawei
Intended status: Standards Track                                 Y. Yang
Expires: May 7, 2020                                     Yale University
                                                                  Y. Lee
                                                                D. Dhody
                                                                  Huawei
                                                          S. Randriamasy
                                                         Nokia Bell Labs
                                                       November 04, 2019

                     ALTO Performance Cost Metrics
                 draft-ietf-alto-performance-metrics-08

Abstract

   Cost metric is a basic concept in Application-Layer Traffic
   Optimization (ALTO), and is used in basic services including both the
   cost map service and the endpoint cost service.

   Different applications may use different cost metrics, but the ALTO
   base protocol documents only one single cost metric, i.e., the
   generic "routingcost" metric; see Sec. 14.2 of ALTO base
   specification [RFC7285].  Hence, if the resource consumer of an
   application prefers a resource provider that offers low-delay
   delivery to the resource consumer, the base protocol does not define
   the cost metric to be used.

   ALTO cost metrics can be generic metrics and this document focuses on
   network performance metrics, including network delay, jitter, packet
   loss, hop count, and bandwidth.  Additional cost metrics may be
   documented in other documents.

   When using an ALTO performance metric, applications need additional
   information beyond the metric.  In particular, its "cost-source",
   such as it being an estimation or an SLA, is key to define the
   meaning of a performance metric.  Hence, each ALTO performance metric
   should include the "cost-source" of the metric.  To report an
   estimated value of a performance metric, the ALTO server may derive
   and aggregate from routing protocols with different granularity and
   scope, such as BGP-LS, OSPF-TE and ISIS-TE, or from end-to-end
   traffic management tools.  These metrics may then be exposed by an
   ALTO Server to allow applications to determine "where" to connect
   based on network performance criteria.

   Requirements Language The key words "MUST", "MUST NOT", "REQUIRED",
   "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",

Wu, et al.                 Expires May 7, 2020                  [Page 1]
Internet-Draft        ALTO Performance Cost Metrics        November 2019

   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 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
   (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
   2.  Network Performance Cost Metrics  . . . . . . . . . . . . . .   6
     2.1.  Cost Metric: One Way Delay (owdelay)  . . . . . . . . . .   6
       2.1.1.  Intended Semantics  . . . . . . . . . . . . . . . . .   6
       2.1.2.  Use and Example . . . . . . . . . . . . . . . . . . .   6
       2.1.3.  Measurement Considerations  . . . . . . . . . . . . .   7
     2.2.  Cost Metric: RoundTrip Time (rtt) . . . . . . . . . . . .   8
       2.2.1.  Intended Semantics  . . . . . . . . . . . . . . . . .   8
       2.2.2.  Use and Example . . . . . . . . . . . . . . . . . . .   8
       2.2.3.  Measurement Considerations  . . . . . . . . . . . . .   9
Show full document text