[ippm] FYI - Draft PMOL Charter for discussion (on pmol@ietf.org)

Al Morton <acmorton@att.com> Fri, 21 September 2007 13:27 UTC

Return-path: <ippm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IYiXj-0005zC-5w; Fri, 21 Sep 2007 09:27:39 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IYiXh-0005xm-3g for ippm@ietf.org; Fri, 21 Sep 2007 09:27:37 -0400
Received: from mail121.messagelabs.com ([216.82.241.195]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IYiXg-0003J2-EL for ippm@ietf.org; Fri, 21 Sep 2007 09:27:36 -0400
X-VirusChecked: Checked
X-Env-Sender: acmorton@att.com
X-Msg-Ref: server-13.tower-121.messagelabs.com!1190381254!24924642!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.128.149]
Received: (qmail 6425 invoked from network); 21 Sep 2007 13:27:35 -0000
Received: from sbcsmtp9.sbc.com (HELO flph024.enaf.ffdc.sbc.com) (144.160.128.149) by server-13.tower-121.messagelabs.com with AES256-SHA encrypted SMTP; 21 Sep 2007 13:27:35 -0000
Received: from enaf.ffdc.sbc.com (localhost.localdomain [127.0.0.1]) by flph024.enaf.ffdc.sbc.com (8.14.0/8.14.0) with ESMTP id l8LDRYbq007460 for <ippm@ietf.org>; Fri, 21 Sep 2007 06:27:34 -0700
Received: from flph023.ffdc.sbc.com (flph023.ffdc.sbc.com [150.234.117.36]) by flph024.enaf.ffdc.sbc.com (8.14.0/8.14.0) with ESMTP id l8LDRTvi007427 for <ippm@ietf.org>; Fri, 21 Sep 2007 06:27:29 -0700
Received: from ffdc.sbc.com (localhost.localdomain [127.0.0.1]) by flph023.ffdc.sbc.com (8.14.0/8.14.0) with ESMTP id l8LDRTuG000905 for <ippm@ietf.org>; Fri, 21 Sep 2007 06:27:29 -0700
Received: from maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by flph023.ffdc.sbc.com (8.14.0/8.14.0) with ESMTP id l8LDRQUO000886 for <ippm@ietf.org>; Fri, 21 Sep 2007 06:27:26 -0700
Message-Id: <200709211327.l8LDRQUO000886@flph023.ffdc.sbc.com>
Received: from acmt.att.com (acmt.mt.att.com[135.16.251.73](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20070921132725gw10010gb5e>; Fri, 21 Sep 2007 13:27:25 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 21 Sep 2007 09:26:58 -0400
To: ippm@ietf.org
From: Al Morton <acmorton@att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 1.5 (+)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc:
Subject: [ippm] FYI - Draft PMOL Charter for discussion (on pmol@ietf.org)
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org >
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org ?subject=unsubscribe>
List-Post: <mailto:ippm@ietf.org >
List-Help: <mailto:ippm-request@ietf.org ?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org ?subject=subscribe>
Errors-To: ippm-bounces@ietf.org

IPPM WG - FYI

Here's the initial draft of the PMOL charter.
Please post any comments on pmol@ietf.org

Al

Proposed Charter (0.0)

Performance Metrics at Other Layers WG (PMOL)

There are often uncertainties about the performance and
suitability of new technologies and applications for their intended
audience, and the Internet is no exception. Most uncertainties are
effectively addressed through quantified assessment of key performance
indicators.  Standardized performance metrics add the desirable features
of consistent implementation, interpretation, and comparison.

Although the IETF has two Working Groups dedicated to the development
of performance metrics, they each have 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 live IP networks, 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 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 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 includes the motivation
    of work to define performance metrics for applications transported
    on IETF-specified protocols, and how that work fills a need and a gap
    in IETF-chartered work. The framework will describe the necessary
    elements of performance metric drafts and the various types of metrics
    that may be prepared in this work. 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 a
    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 in 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).

Milestones
June 08  SIP Performance Metrics Draft to AD Review
Sept 08  PMOL Framework and Guidelines Draft to AD Review


_______________________________________________
ippm mailing list
ippm@ietf.org 
https://www1.ietf.org/mailman/listinfo/ippm