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

Document Type Active Internet-Draft (alto WG)
Authors Qin Wu  , Y. Yang  , Young Lee  , Dhruv Dhody  , Sabine Randriamasy  , Luis Contreras 
Last updated 2021-01-13
Replaces draft-wu-alto-te-metrics
Stream IETF
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Held by WG (wg milestone: Jul 2020 - Submit cost property... )
Revised I-D Needed - Issue raised by WGLC
Document shepherd Jan Seedorf
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to jan@j-f-s.de
ALTO Working Group                                                 Q. Wu
Internet-Draft                                                    Huawei
Intended status: Standards Track                                 Y. Yang
Expires: July 17, 2021                                   Yale University
                                                                  Y. Lee
                                                                 Samsung
                                                                D. Dhody
                                                                  Huawei
                                                          S. Randriamasy
                                                         Nokia Bell Labs
                                                            L. Contreras
                                                              Telefonica
                                                        January 13, 2021

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

Abstract

   Cost metric is a basic concept in Application-Layer Traffic
   Optimization (ALTO), and different applications may use different
   cost metrics.  Since the ALTO base protocol (RFC 7285) defines only a
   single cost metric (i.e., the generic "routingcost" metric), if an
   application wants to issue a cost map or an endpoint cost request to
   determine the resource provider that offers better delay performance,
   the base protocol does not define the cost metric to be used.

   This document addresses the issue by introducing network performance
   metrics, including network delay, jitter, packet loss rate, hop
   count, and bandwidth.

   There are multiple sources (e.g., estimation based on measurements or
   service-level agreement) to derive a performance metric.  This
   document introduces an additional "cost-context" field to the ALTO
   "cost-type" field to convey the source of a performance metric.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119][RFC8174] when, and only when, they appear in all
   capitals, as shown here.

Wu, et al.                Expires July 17, 2021                 [Page 1]
Internet-Draft        ALTO Performance Cost Metrics         January 2021

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 July 17, 2021.

Copyright Notice

   Copyright (c) 2021 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  . . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Performance Metric Attributes . . . . . . . . . . . . . . . .   5
     2.1.  Performance Metric Context: cost-context  . . . . . . . .   6
     2.2.  Performance Metric Statistics . . . . . . . . . . . . . .   8
   3.  Packet Performance Metrics  . . . . . . . . . . . . . . . . .   9
     3.1.  Cost Metric: One-Way Delay (delay-ow) . . . . . . . . . .  10
       3.1.1.  Base Identifier . . . . . . . . . . . . . . . . . . .  10
       3.1.2.  Value Representation  . . . . . . . . . . . . . . . .  10
       3.1.3.  Intended Semantics and Use  . . . . . . . . . . . . .  10
       3.1.4.  Cost-Context Specification Considerations . . . . . .  11
     3.2.  Cost Metric: Round-trip Delay (delay-rt)  . . . . . . . .  12
       3.2.1.  Base Identifier . . . . . . . . . . . . . . . . . . .  12
       3.2.2.  Value Representation  . . . . . . . . . . . . . . . .  12
       3.2.3.  Intended Semantics and Use  . . . . . . . . . . . . .  12

Wu, et al.                Expires July 17, 2021                 [Page 2]
Show full document text