Skip to main content

One-way/Two-way Active Measurement Protocol Extensions for Performance Measurement on LAG
draft-ietf-ippm-otwamp-on-lag-08

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-ippm-otwamp-on-lag@ietf.org, ippm-chairs@ietf.org, ippm@ietf.org, marcus.ihlar@ericsson.com, martin.h.duke@gmail.com, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'One-way/Two-way Active Measurement Protocol Extensions for Performance Measurement on LAG' to Proposed Standard (draft-ietf-ippm-otwamp-on-lag-08.txt)

The IESG has approved the following document:
- 'One-way/Two-way Active Measurement Protocol Extensions for Performance
   Measurement on LAG'
  (draft-ietf-ippm-otwamp-on-lag-08.txt) as Proposed Standard

This document is the product of the IP Performance Measurement Working Group.

The IESG contact persons are Zaheduzzaman Sarker and Martin Duke.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-ippm-otwamp-on-lag/


Ballot Text

Technical Summary

   This document defines extensions to One-way Active Measurement
   Protocol (OWAMP), and Two-way Active Measurement Protocol (TWAMP) to
   implement performance measurement on every member link of a Link
   Aggregation Group (LAG).  Knowing the measured metrics of each member
   link of a LAG enables operators to enforce the performance based
   traffic steering policy across the member links.

Working Group Summary

The one point of controversy was around the applicability or rather the wording of
this draft. Micro-sessions could be useful in more cases than measuring LAG groups
and to be able to measure LAG groups you need a very specific deployment.  There
were suggestions to remove all mentions of LAG from the document and generalize
the concept. 

Document Quality

The protocol defined in the document has been implemented by Huawei, ZTE
and New H3C. China Mobile has wide field deployment.

Personnel

   The Document Shepherd for this document is Marcus Ihlar. The Responsible
   Area Director is Martin Duke.

RFC Editor Note