Re: [alto] ALTO Extension: Defining a Cost Metrics document?
Qin Wu <bill.wu@huawei.com> Mon, 14 October 2013 06:30 UTC
Return-Path: <bill.wu@huawei.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A32C21E80C4 for <alto@ietfa.amsl.com>; Sun, 13 Oct 2013 23:30:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.082
X-Spam-Level:
X-Spam-Status: No, score=-6.082 tagged_above=-999 required=5 tests=[AWL=0.516, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VWG93EpraVYY for <alto@ietfa.amsl.com>; Sun, 13 Oct 2013 23:30:49 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id F2B3B21E80BB for <alto@ietf.org>; Sun, 13 Oct 2013 23:30:47 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AWT97957; Mon, 14 Oct 2013 06:30:45 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.146.0; Mon, 14 Oct 2013 07:30:05 +0100
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.146.0; Mon, 14 Oct 2013 07:30:41 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.141]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0146.000; Mon, 14 Oct 2013 14:30:36 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "Y. Richard Yang" <yry@cs.yale.edu>, IETF ALTO <alto@ietf.org>
Thread-Topic: [alto] ALTO Extension: Defining a Cost Metrics document?
Thread-Index: AQHOyGq3gKD/pIh4mkKRiMotazW0EJnzu3Ig
Date: Mon, 14 Oct 2013 06:30:35 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA43C0ACE7@nkgeml501-mbs.china.huawei.com>
References: <CANUuoLpy5Budcx+tJCeExeYC_yTcQ9J2gC7HsXcjCvhOi7p_Vg@mail.gmail.com>
In-Reply-To: <CANUuoLpy5Budcx+tJCeExeYC_yTcQ9J2gC7HsXcjCvhOi7p_Vg@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.149]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA43C0ACE7nkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "choits@etri.re.kr" <choits@etri.re.kr>
Subject: Re: [alto] ALTO Extension: Defining a Cost Metrics document?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 14 Oct 2013 06:30:53 -0000
From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] On Behalf Of Y. Richard Yang Sent: Monday, October 14, 2013 7:20 AM To: IETF ALTO Cc: choits@etri.re.kr; Qin Wu Subject: [alto] ALTO Extension: Defining a Cost Metrics document? Dear all, I am reading up on the documents that define cost metrics. The motivation is that the base ALTO protocol (http://www.ietf.org/id/draft-ietf-alto-protocol-20.txt) has defined only one Cost Metric: 'routingcost': - Defined the semantics at Sec. 6.1.1.1 of , and then listed it at Table 3. - Used "hopcount" in examples of Sec. 9.2.3 and 9.2.4, but the semantics of not formally defined. Given the aforementioned state of the base protocol, I see good value in that the WG produces a WG document that defines a relatively complete set of Cost Metrics. I particular, I read the following: - http://tools.ietf.org/html/draft-lee-alto-app-net-info-exchange-02 (Sec. 3.4 introduced three metrics: hopcount, latency, pktcost, and cost) - http://tools.ietf.org/html/draft-wu-alto-json-te-01 Defined a set of metrics: in Sec. 4. This work, as stated in the document, is motivated by - http://www.ietf.org/id/draft-ietf-ospf-te-metric-extensions-04.txt During the review of ALTO base protocol, we are suggested to document performance metrics (cost metrics) per the guideline of - RFC 6390 Guidelines for Considering New Performance Metric Development. A. Clark, B. Claise. October 2011. (Format: TXT=49930 bytes) (Also BCP0170) (Status: BEST CURRENT PRACTICE) Here a first question, I have, is whether the authors will produce a "simple" document, at the upcoming IETF, whose only purpose is to: define a set of cost metrics, including the nameing, the semantics, ... following the guideline per RFC 6390, that can benefit the base protocol. [Qin] This is exactly what I we are doing in draft-wu-alto-json-te. We are checking if we can give a complete list of cost metrics that are built based on draft-ietf-idr-ls-distribution-03,RFC5305, draft-wu-idr-te-pm-bgp<http://tools.ietf.org/id/draft-wu-idr-te-pm-bgp-02.txt>,draft-ietf-ospf-te-metric-extensions-04, draft-ietf-isis-te-metric-extensions-01. We will further generalize them to firstly have some base metrics that can applied either to the whole path or any link in the path and then have Derived metrics that are link specific. The update (v-02) will come in a few days. I feel that such a document is focused, and has good value by itself. The implications of the introducing multiple cost metrics can be explored in another document, which I will send in another email shortly. Thanks. Richard
- [alto] ALTO Extension: Defining a Cost Metrics do… Y. Richard Yang
- Re: [alto] ALTO Extension: Defining a Cost Metric… Qin Wu
- Re: [alto] ALTO Extension: Defining a Cost Metric… RANDRIAMASY, SABINE (SABINE)
- Re: [alto] ALTO Extension: Defining a Cost Metric… Y. Richard Yang
- Re: [alto] ALTO Extension: Defining a Cost Metric… RANDRIAMASY, SABINE (SABINE)
- Re: [alto] ALTO Extension: Defining a Cost Metric… Y. Richard Yang
- Re: [alto] ALTO Extension: Defining a Cost Metric… Qin Wu
- Re: [alto] ALTO Extension: Defining a Cost Metric… Y. Richard Yang
- Re: [alto] ALTO Extension: Defining a Cost Metric… Qin Wu
- Re: [alto] ALTO Extension: Defining a Cost Metric… Y. Richard Yang