ALTO Performance Cost Metrics
draft-ietf-alto-performance-metrics-11
ALTO Working Group Q. Wu
Internet-Draft Huawei
Intended status: Standards Track Y. Yang
Expires: December 13, 2020 Yale University
Y. Lee
Samsung
D. Dhody
Huawei
S. Randriamasy
Nokia Bell Labs
L. Contreras
Telefonica
June 11, 2020
ALTO Performance Cost Metrics
draft-ietf-alto-performance-metrics-11
Abstract
Cost metric is a basic concept in Application-Layer Traffic
Optimization (ALTO), and is used in basic ALTO services including
both the cost map service and the endpoint cost service.
Different applications may use different cost metrics, but the ALTO
base protocol [RFC7285] defines only a single cost metric, i.e., the
generic "routingcost" metric; see Sec. 14.2 of [RFC7285]. Hence, if
the ALTO client of an application wants to issue a cost map or an
endpoint cost request to determine the resource provider that offers
better delay performance (i.e., low-delay) to a resource consumer,
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. The ALTO server may derive and aggregate such
performance metrics from routing protocols such as BGP-LS, OSPF-TE
and ISIS-TE, or from end-to-end traffic management tools, and then
expose the information to allow applications to determine "where" to
connect based on network performance criteria.
There are multiple sources to derive the performance metrics. For
example, whether the metric reported is an estimation based on
measurements or it is a service-level agreement (SLA) can define the
meaning of the performance metric. Hence, an application may need
additional contextual information beyond the metric value. This
document introduces an additional "cost-context" field to the ALTO
"cost-type" field to convey such information.
Wu, et al. Expires December 13, 2020 [Page 1]
Internet-Draft ALTO Performance Cost Metrics June 2020
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
[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 December 13, 2020.
Copyright Notice
Copyright (c) 2020 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 . . . . . . . . 5
2.2. Performance Metric Statistics . . . . . . . . . . . . . . 7
3. Packet Performance Metrics . . . . . . . . . . . . . . . . . 8
3.1. Cost Metric: One-Way Delay (delay-ow) . . . . . . . . . . 9
3.1.1. Base Identifier . . . . . . . . . . . . . . . . . . . 9
Show full document text