RFC 5560 on A One-Way Packet Duplication Metric

rfc-editor@rfc-editor.org Fri, 29 May 2009 22:38 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1E5E23A6AE4; Fri, 29 May 2009 15:38:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.949
X-Spam-Level:
X-Spam-Status: No, score=-16.949 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9HxVtZiAx-Vn; Fri, 29 May 2009 15:38:04 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 5CAA33A7013; Fri, 29 May 2009 15:37:37 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id F026B2BBC25; Fri, 29 May 2009 15:38:11 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5560 on A One-Way Packet Duplication Metric
From: rfc-editor@rfc-editor.org
Message-Id: <20090529223811.F026B2BBC25@bosco.isi.edu>
Date: Fri, 29 May 2009 15:38:11 -0700
Cc: ippm@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <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/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: Fri, 29 May 2009 22:38:05 -0000

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

        
        RFC 5560

        Title:      A One-Way Packet Duplication Metric 
        Author:     H. Uijterwaal
        Status:     Standards Track
        Date:       May 2009
        Mailbox:    henk@ripe.net
        Pages:      14
        Characters: 25304
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ippm-duplicate-08.txt

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

When a packet is sent from one host to the other, one normally
expects that exactly one copy of the packet that was sent arrives at
the destination.  It is, however, possible that a packet is either
lost or that multiple copies arrive.

In earlier work, a metric for packet loss was defined.  This metric
quantifies the case where a packet that is sent does not arrive at
its destination within a reasonable time.  In this memo, a metric for
another case is defined: a packet is sent, but multiple copies
arrive.  The document also discusses streams and methods to summarize
the results of streams.  [STANDARDS TRACK]

This document is a product of the IP Performance Metrics Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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