Test Plan and Results for Advancing RFC 2680 on the Standards Track (RFC7290)
Original Publication Date: 2014-Jul-01
Included in the Prior Art Database: 2014-Jul-23
Internet Society Requests For Comment (RFCs)
L. Ciavattone: AUTHOR [+3]
The IETF IP Performance Metrics (IPPM) working group has considered how to advance their metrics along the Standards Track since 2001.
Internet Engineering Task Force (IETF) L. Ciavattone Request for Comments: 7290 AT&T Labs Category: Informational R. Geib ISSN: 2070-1721 Deutsche Telekom A. Morton AT&T Labs M. Wieser Technical University Darmstadt July 2014
Test Plan and Results for Advancing RFC 2680 on the Standards Track
This memo provides the supporting test plan and results to advance RFC 2680, a performance metric RFC defining one-way packet loss metrics, along the Standards Track. Observing that the metric definitions themselves should be the primary focus rather than the implementations of metrics, this memo describes the test procedures to evaluate specific metric requirement clauses to determine if the requirement has been interpreted and implemented as intended. Two completely independent implementations have been tested against the key specifications of RFC 2680.
Status of This Memo
This document is not an Internet Standards Track specification; it is published for informational purposes.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7290.
al. Informational [Page 1]
RFC 7290 Standards Track Tests for RFC 2680 July 2014
Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents