[tsvwg] BCP 145, RFC 8085 on UDP Usage Guidelines
rfc-editor@rfc-editor.org Tue, 07 March 2017 22:17 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15E83129607; Tue, 7 Mar 2017 14:17:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 JBW0iqGCf-nA; Tue, 7 Mar 2017 14:17:38 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A89281295FD; Tue, 7 Mar 2017 14:17:38 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 3DBA1B819A0; Tue, 7 Mar 2017 14:17:37 -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
Message-Id: <20170307221737.3DBA1B819A0@rfc-editor.org>
Date: Tue, 07 Mar 2017 14:17:37 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/tE7FLlnw7fTEadwxuyDMqviGgrQ>
Cc: drafts-update-ref@iana.org, tsvwg@ietf.org, rfc-editor@rfc-editor.org
Subject: [tsvwg] BCP 145, RFC 8085 on UDP Usage Guidelines
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Mar 2017 22:17:41 -0000
A new Request for Comments is now available in online RFC libraries.
BCP 145
RFC 8085
Title: UDP Usage Guidelines
Author: L. Eggert,
G. Fairhurst,
G. Shepherd
Status: Best Current Practice
Stream: IETF
Date: March 2017
Mailbox: lars@netapp.com,
gorry@erg.abdn.ac.uk,
gjshep@gmail.com
Pages: 55
Characters: 145359
Obsoletes: RFC 5405
See Also: BCP 145
I-D Tag: draft-ietf-tsvwg-rfc5405bis-19.txt
URL: https://www.rfc-editor.org/info/rfc8085
DOI: 10.17487/RFC8085
The User Datagram Protocol (UDP) provides a minimal message-passing
transport that has no inherent congestion control mechanisms. This
document provides guidelines on the use of UDP for the designers of
applications, tunnels, and other protocols that use UDP. Congestion
control guidelines are a primary focus, but the document also
provides guidance on other topics, including message sizes,
reliability, checksums, middlebox traversal, the use of Explicit
Congestion Notification (ECN), Differentiated Services Code Points
(DSCPs), and ports.
Because congestion control is critical to the stable operation of the
Internet, applications and other protocols that choose to use UDP as
an Internet transport must employ mechanisms to prevent congestion
collapse and to establish some degree of fairness with concurrent
traffic. They may also need to implement additional mechanisms,
depending on how they use UDP.
Some guidance is also applicable to the design of other protocols
(e.g., protocols layered directly on IP or via IP-based tunnels),
especially when these protocols do not themselves provide congestion
control.
This document obsoletes RFC 5405 and adds guidelines for multicast
UDP usage.
This document is a product of the Transport Area Working Group 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
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
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