ALTO Traffic Engineering Cost Metrics
draft-wu-alto-te-metrics-04

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-07-22
Replaced by draft-ietf-alto-performance-metrics
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 Working Group                                                 Q. Wu
Internet-Draft                                                    Huawei
Intended status: Standards Track                                 Y. Yang
Expires: January 23, 2015                                Yale University
                                                                  Y. Lee
                                                                D. Dhody
                                                                  Huawei
                                                          S. Randriamasy
                                                          Alcatel-Lucent
                                                           July 22, 2014

                 ALTO Traffic Engineering Cost Metrics
                      draft-wu-alto-te-metrics-04

Abstract

   Cost Metric is a basic concept in Application-Layer Traffic
   Optimization (ALTO).  It is used in both the Cost Map Service and the
   Endpoint Cost Service.  Future extensions to ALTO may also use Cost
   Metric.

   Different applications may benefit from different Cost Metrics.  For
   example, a Resource Consumer may prefer Resource Providers that have
   low delay to the Resource Consumer.  However the base ALTO protocol
   [ALTO] has defined only a single cost metric, i.e., the generic
   "routingcost" metric (Sec. 14.2 of ALTO base specification [ALTO]).

   In this document, we define eleven Cost Metrics, derived from OSPF-TE
   and ISIS-TE, to measure network delay, jitter, packet loss, hop
   count, and bandwidth.  The metrics defined in this document provide a
   relatively comprehensive set of Cost Metrics for ALTO focusing on
   traffic engineering (TE).  Additional Cost Metrics such as financial
   cost metrics may be defined in other documents.

   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

Wu, et al.              Expires January 23, 2015                [Page 1]
Internet-Draft               ALTO TE Metrics                   July 2014

   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 23, 2015.

Copyright Notice

   Copyright (c) 2014 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.  Data sources, computation of defined cost metrics . . . . . .   4
     2.1.  Data sources  . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Computation of metrics  . . . . . . . . . . . . . . . . .   4
   3.  Metric: Delay . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Metric: Delay Jitter  . . . . . . . . . . . . . . . . . . . .   6
   5.  Metric: Packet Loss . . . . . . . . . . . . . . . . . . . . .   8
   6.  Metric: Hop Count . . . . . . . . . . . . . . . . . . . . . .  10
   7.  Metric: Bandwidth . . . . . . . . . . . . . . . . . . . . . .  12
   8.  Metric: Maximum Bandwidth . . . . . . . . . . . . . . . . . .  13
   9.  Metric: Maximum Reservable Bandwidth  . . . . . . . . . . . .  15
   10. Metric: Unreserved Bandwidth  . . . . . . . . . . . . . . . .  16
   11. Metric: Residue Bandwidth . . . . . . . . . . . . . . . . . .  19
   12. Metric: Available Bandwidth . . . . . . . . . . . . . . . . .  20
   13. Metric: Utilized Bandwidth  . . . . . . . . . . . . . . . . .  22
   14. Security Considerations . . . . . . . . . . . . . . . . . . .  24
   15. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  25
   16. References  . . . . . . . . . . . . . . . . . . . . . . . . .  25
     16.1.  Normative References . . . . . . . . . . . . . . . . . .  25
Show full document text