[tcpm] BCP 233, RFC 8961 on Requirements for Time-Based Loss Detection

rfc-editor@rfc-editor.org Tue, 24 November 2020 01:24 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 5C7A03A09D8; Mon, 23 Nov 2020 17:24:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id a4R-UF7n4lLw; Mon, 23 Nov 2020 17:24:50 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B3033A09D4; Mon, 23 Nov 2020 17:24:50 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id DC4AEF40780; Mon, 23 Nov 2020 17:24:47 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, tcpm@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20201124012447.DC4AEF40780@rfc-editor.org>
Date: Mon, 23 Nov 2020 17:24:47 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/eOv7K_1SKQN06s7SQlAttX036YE>
Subject: [tcpm] BCP 233, RFC 8961 on Requirements for Time-Based Loss Detection
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Nov 2020 01:24:54 -0000

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

        BCP 233        
        RFC 8961

        Title:      Requirements for Time-Based Loss Detection 
        Author:     M. Allman
        Status:     Best Current Practice
        Stream:     IETF
        Date:       November 2020
        Mailbox:    mallman@icir.org
        Pages:      12
        See Also:   BCP 233

        I-D Tag:    draft-ietf-tcpm-rto-consider-17.txt

        URL:        https://www.rfc-editor.org/info/rfc8961

        DOI:        10.17487/RFC8961

Many protocols must detect packet loss for various reasons (e.g., to
ensure reliability using retransmissions or to understand the level
of congestion along a network path).  While many mechanisms have been
designed to detect loss, ultimately, protocols can only count on the
passage of time without delivery confirmation to declare a packet
"lost". Each implementation of a time-based loss detection mechanism
represents a balance between correctness and timeliness; therefore,
no implementation suits all situations.  This document provides
high-level requirements for time-based loss detectors appropriate for
general use in unicast communication across the Internet.  Within the
requirements, implementations have latitude to define particulars
that best address each situation.

This document is a product of the TCP Maintenance and Minor Extensions Working Group of the IETF.

BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. 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 https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

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
Association Management Solutions, LLC