[alto] Status update //RE: I-D Action: draft-ietf-alto-performance-metrics-05.txt

Qin Wu <bill.wu@huawei.com> Mon, 22 October 2018 01:15 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 298E312F1AC for <alto@ietfa.amsl.com>; Sun, 21 Oct 2018 18:15:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 0b9Vkj9UiTSq for <alto@ietfa.amsl.com>; Sun, 21 Oct 2018 18:15:32 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7EF2120072 for <alto@ietf.org>; Sun, 21 Oct 2018 18:15:31 -0700 (PDT)
Received: from lhreml706-cah.china.huawei.com (unknown []) by Forcepoint Email with ESMTP id 7D2D6C8EC6506 for <alto@ietf.org>; Mon, 22 Oct 2018 02:15:27 +0100 (IST)
Received: from NKGEML411-HUB.china.huawei.com ( by lhreml706-cah.china.huawei.com ( with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 22 Oct 2018 02:15:28 +0100
Received: from NKGEML513-MBX.china.huawei.com ([]) by nkgeml411-hub.china.huawei.com ([]) with mapi id 14.03.0415.000; Mon, 22 Oct 2018 09:15:22 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "alto@ietf.org" <alto@ietf.org>
Thread-Topic: Status update //RE: [alto] I-D Action: draft-ietf-alto-performance-metrics-05.txt
Thread-Index: AQHUaaRRSPBLS2HN9Eq6xIPwkufpg6UqdX1A
Date: Mon, 22 Oct 2018 01:15:22 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA9B0B8CBE@nkgeml513-mbx.china.huawei.com>
References: <154017073595.10657.7642714774728414581@ietfa.amsl.com>
In-Reply-To: <154017073595.10657.7642714774728414581@ietfa.amsl.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/C68CeTRw6rYypBhQA12ExalqHzI>
Subject: [alto] Status update //RE: I-D Action: draft-ietf-alto-performance-metrics-05.txt
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/alto/>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2018 01:15:34 -0000

The main changes in v-(05) are to remove duplicated text for PDV cost metric and add throughput cost metric to align with cost calendar draft.
The diff is:

发件人: alto [mailto:alto-bounces@ietf.org] 代表 internet-drafts@ietf.org
发送时间: 2018年10月22日 9:12
收件人: i-d-announce@ietf.org
抄送: alto@ietf.org
主题: [alto] I-D Action: draft-ietf-alto-performance-metrics-05.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF.

        Title           : ALTO Performance Cost Metrics
        Authors         : Qin Wu
                          Y. Richard Yang
                          Young Lee
                          Dhruv Dhody
                          Sabine Randriamasy
	Filename        : draft-ietf-alto-performance-metrics-05.txt
	Pages           : 26
	Date            : 2018-10-21

   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.

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

   This document, proposes a set of Cost Metrics, derived and aggregated
   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.  It currently documents Network Performance Cost Metrics
   reporting on network delay, jitter, packet loss, hop count, and
   bandwidth.  These metrics may be exposed by an ALTO Server to allow
   applications to determine "where" to connect based on network
   performance criteria.  Additional Cost Metrics involving ISP specific
   considerations or other network technologies may be documented in
   further versions of this draft.


The IETF datatracker status page for this draft is:

There are also htmlized versions available at:

A diff from the previous version is available at:

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:

alto mailing list