[PMOL] Re: A question about [Fwd: WG Review: Performance Metrics at Other Layers (pmol)]
Yangwoo Ko <newcat@icu.ac.kr> Tue, 30 October 2007 12:09 UTC
Return-path: <pmol-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Impuv-0002hg-40; Tue, 30 Oct 2007 08:09:57 -0400
Received: from pmol by megatron.ietf.org with local (Exim 4.43) id 1ImhRb-0003sb-22 for pmol-confirm+ok@megatron.ietf.org; Mon, 29 Oct 2007 23:07:07 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ImhRa-0003i7-Cw for pmol@ietf.org; Mon, 29 Oct 2007 23:07:06 -0400
Received: from sniper.icu.ac.kr ([210.107.128.51]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ImhRX-0000fN-8G for pmol@ietf.org; Mon, 29 Oct 2007 23:07:04 -0400
Received: (snipe 19899 invoked by uid 0); 30 Oct 2007 12:06:56 +0900
Received: from newcat@icu.ac.kr with Spamsniper 2.96.00 (Processed in 1.074600 secs);
Received: from unknown (HELO ?210.107.250.146?) (Z???own@210.107.250.146) by unknown with SMTP; 30 Oct 2007 12:06:55 +0900
X-SNIPER-SENDERIP: 210.107.250.146
X-SNIPER-MAILFROM: newcat@icu.ac.kr
X-SNIPER-RCPTTO: leslie@thinkingcat.com, ietf@ietf.org, pmol@ietf.org, iesg@ietf.org, yangwooko@gmail.com
Message-ID: <47269FC5.5030802@icu.ac.kr>
Date: Tue, 30 Oct 2007 12:06:45 +0900
From: Yangwoo Ko <newcat@icu.ac.kr>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Leslie Daigle <leslie@thinkingcat.com>
References: <47263CC1.8000104@thinkingcat.com>
In-Reply-To: <47263CC1.8000104@thinkingcat.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6ba8aaf827dcb437101951262f69b3de
X-Mailman-Approved-At: Tue, 30 Oct 2007 08:09:55 -0400
Cc: IESG <iesg@ietf.org>, ietf@ietf.org, pmol@ietf.org
Subject: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics at Other Layers (pmol)]
X-BeenThere: pmol@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Performance Metrics at Other Layers <pmol.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pmol>, <mailto:pmol-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pmol>
List-Post: <mailto:pmol@ietf.org>
List-Help: <mailto:pmol-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pmol>, <mailto:pmol-request@ietf.org?subject=subscribe>
Errors-To: pmol-bounces@ietf.org
Since application developers have developed many tricks to smooth out some peculiarities of network-based protocols (e.g. jitter, delay, drops and so on), it is very often hard to related the performance measured/perceived at application layer with those of underlying layers. If this WG provides guidelines (or at least hints) to get over this vagueness, I will be very happy. Regards Leslie Daigle wrote: > > > At the Application Performance Metrics BoF in > Chicago, there was a lot of discussion about whether > or how to best capture expertise in the area of performance > metrics for application to IETF protocols. > > There seemed to be 2 separate questions on the table: > > 1/ how, and > 2/ whether > > to generalize a performance metric framework for IETF > protocols. > > > The proposed PMOL WG addresses the first question -- how > to do it. > > On the second point -- the question is really about whether > the IETF community as a whole supports/values performance > metrics and will invest the effort in using any general > framework for existing/new protocols. > > I believe the folks that joined the PMOL mailing list after > the APM BoF are assuming that support is there. > > I suggest that now is an excellent time for folks _not_ > involved in the PMOL effort, but who are working on > protocols that could/should make use of its output, to > voice some opinions on whether or not this approach > is helpful/will be useful to them in future protocols. > > > Leslie. > > > -------- Original Message -------- > Subject: WG Review: Performance Metrics at Other Layers (pmol) > Date: Mon, 22 Oct 2007 14:15:02 -0400 > From: IESG Secretary <iesg-secretary@ietf.org> > Reply-To: iesg@ietf.org > To: ietf-announce@ietf.org > > A new IETF working group has been proposed in the Operations and > Management Area. The IESG has not made any determination as yet. > The following draft charter was submitted, and is provided for > informational purposes only. Please send your comments to the IESG > mailing list (iesg@ietf.org) by October 29. > > +++ > > Performance Metrics at Other Layers (pmol) > ============================================== > > Current Status: Proposed Working Group > > WG Chairs: > TBD > > Operations and Management Area: > Dan Romascanu <dromasca@avaya.com> > Ronald Bonica <rbonica@juniper.net> > > Description: > > The successful implementation and operation of IP based applications > often depends on some underlying performance measurement infrastructure > that helps service operators or network managers to recognize when > performance is unsatisfactory and identify problems affecting service > quality. Standardized performance metrics add the desirable features of > consistent implementation, interpretation, no comparison. > > The IETF has two Working Groups dedicated to the development of > performance metrics however each has strict limitations in their > charters: > > - The Benchmarking Methodology WG has addressed a range of networking > technologies and protocols in their long history (such as IEEE 802.3, > ATM, Frame Relay, and Routing Protocols), but the charter strictly > limits their Performance characterizations to the laboratory > environment. > > - The IP Performance Metrics WG has the mandate to develop metrics > applicable to the performance of Internet data delivery, but it is > specifically prohibited from developing metrics that characterize > traffic (such as a VoIP stream). > > The IETF also has current and completed activities related to the > reporting of application performance metrics (e.g. RAQMON and RTCP XR) > and is also actively involved in the development of reliable transport > protocols which would affect the relationship between IP performance and > application performance. > > Thus there is a gap in the currently chartered coverage of IETF WGs: > development of performance metrics for IP-based protocols and > applications that operate over UDP, TCP, SCTP, DCCP, Forward Error > Correction (FEC) and other robust transport protocols, and that can be > used to characterize traffic on live networks. > > The working group will focus on the completion of two RFCs: > > 1. A PMOL framework and guidelines memo that will describe the necessary > elements of performance metrics of protocols and applications > transported over IETF-specified protocols (such as the formal > definition, purpose, and units of measure) and the various types of > metrics that characterize traffic on live networks (such as metrics > derived from other metrics, possibly on lower layers). The framework > will also address the need to specify the intended audience and the > motivation for the performance metrics. There will also be guidelines > for a performance metric development process that includes entry > criteria for new proposals (how a proposal might be evaluated for > possible endorsement by a protocol development working group), and how > an successful proposal will be developed by PMOL WG in cooperation with > a protocol development WG. > > 2. A proof-of-concept RFC defining performance metrics for SIP, based on > draft-malas-performance-metrics. This memo would serve as an example of > the framework and the PMOL development process in the IETF. > > Discussion of new work proposals is strongly discouraged under the > initial charter of the PMOL WG, except to advise a protocol development > WG when they are evaluating a new work proposal for related performance > metrics. > > The PMOL WG will also be guided by a document describing how memos > defining performance metrics are intended to advance along the IETF > Standards track (draft-bradner-metricstest). > > PMOL WG will take advantage of expertise and seek to avoid overlap with > other standards development organizations, such as ETSI STQ, ITU-T SG > 12, ATIS IIF, ATIS PRQC, and others. > > Milestones > > June 08 SIP Performance Metrics Draft to IESG Review for consideration > as Proposed Standard > > Sept 08 PMOL Framework and Guidelines Draft to IESG Review for > consideration as BCP > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf-announce > _______________________________________________ PMOL mailing list PMOL@ietf.org https://www1.ietf.org/mailman/listinfo/pmol
- [PMOL] Re: A question about [Fwd: WG Review: Perf… Sam Hartman
- [PMOL] A question about [Fwd: WG Review: Performa… Leslie Daigle
- [PMOL] Re: A question about [Fwd: WG Review: Perf… Yangwoo Ko
- RE: [PMOL] Re: A question about [Fwd: WG Review: … Romascanu, Dan (Dan)
- RE: [PMOL] Re: A question about [Fwd: WG Review: … Dan Schutzer
- Re: [PMOL] Re: A question about [Fwd: WG Review: … Sam Hartman
- Re: [PMOL] Re: A question about [Fwd: WG Review: … Brian E Carpenter
- Re: [PMOL] Re: A question about [Fwd: WG Review: … David R Oran
- Re: [PMOL] Re: A question about [Fwd: WG Review: … Bill Sommerfeld
- Re: [PMOL] Re: A question about [Fwd: WG Review: … Randy Presuhn
- Re: [PMOL] Re: A question about [Fwd: WG Review: … Joe Touch
- Re: [PMOL] Re: A question about [Fwd: WG Review: … Stephen Kent
- Re: [PMOL] Re: A question about [Fwd: WG Review: … Joe Touch
- Re: [PMOL] Re: A question about [Fwd: WG Review: … Steven M. Bellovin
- Re: [PMOL] Re: A question about [Fwd: WG Review: … Sam Hartman
- Re: [PMOL] Re: A question about [Fwd: WG Review: … Steven M. Bellovin
- Re: [PMOL] Re: A question about [Fwd: WG Review: … Joe Touch
- Re: [PMOL] Re: A question about [Fwd: WG Review: … Joe Touch
- Re: [PMOL] Re: A question about [Fwd: WG Review: … Steven M. Bellovin
- Re: [PMOL] Re: A question about [Fwd: WG Review: … Joe Touch
- Re: [PMOL] Re: A question about [Fwd: WG Review: … Stephen Kent