RFC 5236 on Improved Packet Reordering Metrics

rfc-editor@rfc-editor.org Tue, 03 June 2008 22:23 UTC

Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietf-announce-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from [] (localhost []) by core3.amsl.com (Postfix) with ESMTP id 337543A683D; Tue, 3 Jun 2008 15:23:54 -0700 (PDT)
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 109883A6C31 for <ietf-announce@core3.amsl.com>; Tue, 3 Jun 2008 15:23:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.928
X-Spam-Status: No, score=-16.928 tagged_above=-999 required=5 tests=[AWL=0.671, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id XJliBoo2wN3c for <ietf-announce@core3.amsl.com>; Tue, 3 Jun 2008 15:23:51 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu []) by core3.amsl.com (Postfix) with ESMTP id 137973A6A74 for <ietf-announce@ietf.org>; Tue, 3 Jun 2008 15:23:50 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 6F96F135106; Tue, 3 Jun 2008 15:23:53 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5236 on Improved Packet Reordering Metrics
From: rfc-editor@rfc-editor.org
Message-Id: <20080603222353.6F96F135106@bosco.isi.edu>
Date: Tue, 03 Jun 2008 15:23:53 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Announcements <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

A new Request for Comments is now available in online RFC libraries.

        RFC 5236

        Title:      Improved Packet Reordering Metrics 
        Author:     A. Jayasumana, N. Piratla,
                    T. Banka, A. Bare,
                    R. Whitner
        Status:     Informational
        Date:       June 2008
        Mailbox:    Anura.Jayasumana@colostate.edu, 
        Pages:      26
        Characters: 57805
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-jayasumana-reorder-density-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5236.txt

This document presents two improved metrics for packet reordering,
namely, Reorder Density (RD) and Reorder Buffer-occupancy Density
(RBD).  A threshold is used to clearly define when a packet is
considered lost, to bound computational complexity at O(N), and to
keep the memory requirement for evaluation independent of N, where N
is the length of the packet sequence.  RD is a comprehensive metric
that captures the characteristics of reordering, while RBD evaluates
the sequences from the point of view of recovery from reordering.

These metrics are simple to compute yet comprehensive in their
characterization of packet reordering.  The measures are robust and
orthogonal to packet loss and duplication.  This memo provides 
information for the Internet community.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
USC/Information Sciences Institute

IETF-Announce mailing list