Document Action: 'Rate Measurement Test Protocol Problem Statement and Requirements' to Informational RFC (draft-ietf-ippm-rate-problem-10.txt)
The IESG <iesg-secretary@ietf.org> Thu, 12 February 2015 19:37 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3FCE1A1DFA; Thu, 12 Feb 2015 11:37:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
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 Pl_xHtvyjW_1; Thu, 12 Feb 2015 11:37:19 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E6CBF1A1EB7; Thu, 12 Feb 2015 11:37:13 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Document Action: 'Rate Measurement Test Protocol Problem Statement and Requirements' to Informational RFC (draft-ietf-ippm-rate-problem-10.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150212193713.325.7204.idtracker@ietfa.amsl.com>
Date: Thu, 12 Feb 2015 11:37:13 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/aMIOiJIwYbl-Zmb2ju5P8tjUkjo>
Cc: ippm mailing list <ippm@ietf.org>, ippm chair <ippm-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Feb 2015 19:37:21 -0000
The IESG has approved the following document: - 'Rate Measurement Test Protocol Problem Statement and Requirements' (draft-ietf-ippm-rate-problem-10.txt) as Informational RFC This document is the product of the IP Performance Metrics Working Group. The IESG contact persons are Spencer Dawkins and Martin Stiemerling. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-ippm-rate-problem/ Technical Summary This memo presents an access rate-measurement problem statement for test protocols to measure IP Performance Metrics. The rate measurement scenario has wide-spread attention of Internet access subscribers and seemingly all industry players, including regulators. Key test protocol aspects require the ability to control packet size on the tested path and enable asymmetrical packet size testing in a controller-responder architecture. Working Group Summary A controversial topic regards the level of requirement for the capability to control asymmetric packet sizes in two-way testing architectures. A few participants felt that the document should not require asymmetric packet sizes, even though there are a number of cases where it would appear asymmetric packets sizes would be essential to measure the path capacity accurately. As a compromise, the author updated the document to require asymmetric packet rate generation, and both symmetric and asymmetric packet sizes are recommended. The many circumstances where asymmetric packet size testing is needed are documented, and many of these circumstances would be unknown prior to comparative tests using symmetric and asymmetric packet sizes. Document Quality The draft was reviewed by many members of WG. There are already standards track protocol extension proposals that respond to the requirements in this draft. At least one protocol solution has been implemented and deployed. Personnel The document shepherd is Bill Cerveny. The responsible area director is Spencer Dawkins.