Re: [ippm] New IPPM charter suggestion

"Frank Brockners (fbrockne)" <fbrockne@cisco.com> Wed, 02 August 2017 15:01 UTC

Return-Path: <fbrockne@cisco.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA2DA13212E for <ippm@ietfa.amsl.com>; Wed, 2 Aug 2017 08:01:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cfMfXPoxLEwz for <ippm@ietfa.amsl.com>; Wed, 2 Aug 2017 08:01:08 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7675B131E96 for <ippm@ietf.org>; Wed, 2 Aug 2017 08:01:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10432; q=dns/txt; s=iport; t=1501686068; x=1502895668; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=pk6frt3WzZtKI/s8eRhLaQt9lXiSOleRiSbaj7iBLDg=; b=W5LRwwBfhbC3AVgwd7UuvxplaHZ9b02JifD+RIirLNUAh0H5uSzrGKmg p32pvHjjSIjSZhClkSInVUHwjZQq9YyL2p953eRlqqdSV+cGdO0N1rlk1 ygx8TinDKJMisk0priR5PFNzOgJJtGqwlxECztzrk/3Jh3VSdGha4KhRv 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DDAAAu6IFZ/4wNJK1dGQEBAQEBAQEBAQEBBwEBAQEBgy0tZG0nB44HkASBbpYQDoIELIUbAoQ1PxgBAgEBAQEBAQFrKIUYAQEBAQIBDiwrGQcEAgEIEQQBAQEVCQkHMhQJCAIEAQkJCIofCBCwJItNAQEBAQEBAQEBAQEBAQEBAQEBAQEBGAWDKIICgUyBY4MnhDAJExNThTUFn3wCh1GDTIkEghaQN4lajCABHzhMPncVh2N2hywBJYEMgQ8BAQE
X-IronPort-AV: E=Sophos;i="5.41,311,1498521600"; d="scan'208";a="277799121"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 02 Aug 2017 15:01:07 +0000
Received: from XCH-RCD-008.cisco.com (xch-rcd-008.cisco.com [173.37.102.18]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v72F17l6011248 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 2 Aug 2017 15:01:07 GMT
Received: from xch-rcd-008.cisco.com (173.37.102.18) by XCH-RCD-008.cisco.com (173.37.102.18) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 2 Aug 2017 10:01:06 -0500
Received: from xch-rcd-008.cisco.com ([173.37.102.18]) by XCH-RCD-008.cisco.com ([173.37.102.18]) with mapi id 15.00.1210.000; Wed, 2 Aug 2017 10:01:06 -0500
From: "Frank Brockners (fbrockne)" <fbrockne@cisco.com>
To: "Brian Trammell (IETF)" <ietf@trammell.ch>, IETF IPPM WG <ippm@ietf.org>
Thread-Topic: [ippm] New IPPM charter suggestion
Thread-Index: AQHTBVTo0QB8UJENj0WtkwsiKJPAc6JoH6OAgAkVrnA=
Date: Wed, 02 Aug 2017 15:01:06 +0000
Message-ID: <2198b843da404031babd41bc4e5cb386@XCH-RCD-008.cisco.com>
References: <6995DF9D-CD73-4DAB-BE04-94096A5E00F6@trammell.ch> <75B99782-03D1-4D74-9C43-C40A5C3D3FC2@trammell.ch>
In-Reply-To: <75B99782-03D1-4D74-9C43-C40A5C3D3FC2@trammell.ch>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.55.117.7]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/9JJfS9-gRhDaPBo6Lb6KqNxKBHo>
Subject: Re: [ippm] New IPPM charter suggestion
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Aug 2017 15:01:11 -0000

Thanks Brian. The changes reflect the discussion in the WG meeting in Prague - and I do support them.

Regards, Frank

-----Original Message-----
From: ippm [mailto:ippm-bounces@ietf.org] On Behalf Of Brian Trammell (IETF)
Sent: Donnerstag, 27. Juli 2017 17:16
To: IETF IPPM WG <ippm@ietf.org>
Subject: Re: [ippm] New IPPM charter suggestion

Several people have noted that viewers of the Google Doc can't see the diffs. Here's a diff -U 3 of the two charters:

--- charter-05.txt	2017-07-27 11:12:52.000000000 -0400
+++ charter-06-00.txt	2017-07-27 11:13:07.000000000 -0400
@@ -1,12 +1,19 @@
-The IP Performance Metrics (IPPM) Working Group develops and maintains standard -metrics that can be applied to the quality, performance, and reliability of -Internet data delivery services and applications running over transport layer -protocols (e.g. TCP, UDP) over IP.  Specifying network or lower layer OAM -mechanisms is out of scope of the IPPM charter.  It also develops and maintains -protocols for the measurement of these metrics. These metrics are designed such -that they can be used by network operators, end users, or independent testing -groups. Metrics developed by the IPPM WG are intended to provide unbiased -quantitative performance measurements and not a value judgement.
+
+The IP Performance Measurement (IPPM) Working Group develops and 
+maintains standard metrics that can be applied to the quality, 
+performance, and reliability of Internet data delivery services and 
+applications running over transport layer protocols (e.g. TCP, UDP) 
+over IP. It also develops and maintains methodologies and protocols for the measurement of these metrics.
+These metrics, protocols, and methodologies are designed such that they 
+can be used by network operators, end users, or independent testing 
+groups. Metrics developed by the IPPM WG are intended to provide 
+unbiased quantitative performance measurements.
+
+The IPPM WG works to foster commonality and comparability of metrics 
+and measurements across IETF protocols at different layers. Its work is 
+limited to metrics and methodologies which are applicable over 
+transport-layer protocols over IP, and does not specify encapsulations 
+required for measurements over non-IP layers.

 The IPPM WG has produced documents that define specific metrics and procedures  for accurately measuring and documenting these metrics. The working group will @@ -21,9 +28,7 @@  will require that new metric definitions state how the definition improves on an  existing metric definition, or assesses a property of network performance not  previously covered by a defined metric. Metric definitions will follow the -template given in RFC 6390. It is possible that new measurement protocols will -be needed to support new metrics; if this is the case, the working group will be -rechartered to develop these protocols.
+template given in RFC 6390.

 Additional methods will be defined for the composition and calibration of  IPPM-defined metrics, as well as active, passive and hybrid measurement methods @@ -44,11 +48,19 @@

 Agreement about the definitions of metrics and methods of measurement enables  accurate, reproducible, and equivalent results across different implementations.
-To this end, the WG will define and maintain a registry of metric definitions.
+To this end, the WG defines and maintains a registry of metric definitions.
+
 The WG encourages work which assesses the comparability of measurements of IPPM  metrics with metrics developed elsewhere. The WG also encourages work which  improves the availability of information about the context in which measurements -were taken.
+were taken, for example (but not limited to) measurement implementation 
+information, estimates of confidence in these measurements, conditions 
+on the
+network(s) on which measurements are taken, and/or information about 
+the data-plane topology of these network(s).
+
+In the interest of measurement comparability, the WG may define data 
+formats and information models for the storage and exchange of the 
+results of measurements defined within IPPM.

 The IPPM WG seeks cooperation with other appropriate standards bodies and forums  to promote consistent approaches and metrics. Within the IETF process, IPPM @@ -58,22 +70,3 @@  with the requirement of these specific metrics. The WG will, on request, provide  input to other IETF working groups on the use and implementation of these  metrics.
-
-Specific near-term milestones include:
-
-1. Advancement of protocols for one- and two-way metrics (OWAMP and TWAMP
-respectively) along the standards track.
-
-2. Update of the IPPM framework document (RFC 2330) to reflect experience with -the framework, and to cover planned future metric development.
-
-3. Definition of a registry of metric definitions to improve the equivalency of -metric results across multiple implementations.
-
-4. Publication of a rate measurement problem statement.
-
-5. Publication of documents supporting the use of IPSec to protect OWAMP / -TWAMP.
-
-6. Publication of documents related to model-based TCP bulk transfer capacity


Cheers,

Brian

> On 25 Jul 2017, at 10:47, Brian Trammell (IETF) <ietf@trammell.ch> wrote:
> 
> Greetings, all,
> 
> Following our meeting in Prague (minutes forthcoming), here's where I 
> think we are with the suggested new charter. Track changes view in 
> Google Docs at: 
> https://docs.google.com/document/d/15Q5tIcv2b6oQ9tL_dS90N_ApREZZpSJJxm
> k-Jnwx3z8/edit?usp=sharing
> 
> The new charter text, in full, appears below.
> 
> Comments?
> 
> Thanks, cheers,
> 
> Brian (as chair)
> 
> 
> The IP Performance Measurement (IPPM) Working Group develops and maintains standard metrics that can be applied to the quality, performance, and reliability of Internet data delivery services and applications running over transport layer protocols (e.g. TCP, UDP) over IP. It also develops and maintains methodologies and protocols for the measurement of these metrics. These metrics, protocols, and methodologies are designed such that they can be used by network operators, end users, or independent testing groups. Metrics developed by the IPPM WG are intended to provide unbiased quantitative performance measurements.
> 
> The IPPM WG works to foster commonality and comparability of metrics and measurements across IETF protocols at different layers. Its work is limited to metrics and methodologies which are applicable over transport-layer protocols over IP, and does not specify encapsulations required for measurements over non-IP layers.
> 
> The IPPM WG has produced documents that define specific metrics and procedures for accurately measuring and documenting these metrics. The working group will continue advancing the most useful of these metrics along the standards track, using the guidelines stated in RFC 6576. To the extent possible, these metrics will be used as the basis for future work on metrics in the WG.
> 
> The WG will seek to develop new metrics and models to more accurately characterize the network paths under test and/or the performance of transport and application layer protocols on these paths. The WG will balance the need for new metrics with the desire to minimize the introduction of new metrics, and will require that new metric definitions state how the definition improves on an existing metric definition, or assesses a property of network performance not previously covered by a defined metric. Metric definitions will follow the template given in RFC 6390.
> 
> Additional methods will be defined for the composition and calibration of IPPM-defined metrics, as well as active, passive and hybrid measurement methods for these metrics. In addition, the WG encourages work which describes the applicability of metrics and measurement methods, especially to improve understanding of the tradeoffs involved among active, passive, and hybrid methods.
> 
> The WG may update its core framework RFC 2330 as necessary to accommodate these activities.
> 
> The WG has produced protocols for communication among test equipment to enable the measurement of the one- and two-way metrics (OWAMP and TWAMP respectively). These protocols will be advanced along the standards track. The work of the WG will take into account the suitability of measurements for automation, in order to support large-scale measurement efforts. This may result in further developments in protocols such as OWAMP and TWAMP.
> 
> Agreement about the definitions of metrics and methods of measurement enables accurate, reproducible, and equivalent results across different implementations. To this end, the WG defines and maintains a registry of metric definitions.
> 
> The WG encourages work which assesses the comparability of measurements of IPPM metrics with metrics developed elsewhere. The WG also encourages work which improves the availability of information about the context in which measurements were taken, for example (but not limited to) measurement implementation information, estimates of confidence in these measurements, conditions on the network(s) on which measurements are taken, and/or information about the data-plane topology of these network(s).
> 
> In the interest of measurement comparability, the WG may define data formats and information models for the storage and exchange of the results of measurements defined within IPPM.
> 
> The IPPM WG seeks cooperation with other appropriate standards bodies and forums to promote consistent approaches and metrics. Within the IETF process, IPPM metric definitions and measurement protocols will be subject to as rigorous a scrutiny for usefulness, clarity, and accuracy as other protocol standards. The IPPM WG will interact with other areas of IETF activity whose scope intersects with the requirement of these specific metrics. The WG will, on request, provide input to other IETF working groups on the use and implementation of these metrics.
>