BCP 145, RFC 5405 on Unicast UDP Usage Guidelines for Application Designers

rfc-editor@rfc-editor.org Tue, 18 November 2008 17:09 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 [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E2EE928C23E; Tue, 18 Nov 2008 09:09:47 -0800 (PST)
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 20F7528C227; Tue, 18 Nov 2008 09:09:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.864
X-Spam-Level:
X-Spam-Status: No, score=-16.864 tagged_above=-999 required=5 tests=[AWL=0.735, BAYES_00=-2.599, 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 KapGTNsu-tQh; Tue, 18 Nov 2008 09:09:45 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 22E0C28C20E; Tue, 18 Nov 2008 09:09:45 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id AEA2317ADF5; Tue, 18 Nov 2008 09:09:44 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 145, RFC 5405 on Unicast UDP Usage Guidelines for Application Designers
From: rfc-editor@rfc-editor.org
Message-Id: <20081118170944.AEA2317ADF5@bosco.isi.edu>
Date: Tue, 18 Nov 2008 09:09:44 -0800
Cc: tsvwg@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/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.

        BCP 145        
        RFC 5405

        Title:      Unicast UDP Usage Guidelines for 
                    Application Designers 
        Author:     L. Eggert, G. Fairhurst
        Status:     Best Current Practice
        Date:       November 2008
        Mailbox:    lars.eggert@nokia.com, 
                    gorry@erg.abdn.ac.uk
        Pages:      27
        Characters: 69607
        See Also:   BCP0145

        I-D Tag:    draft-ietf-tsvwg-udp-guidelines-11.txt

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

The User Datagram Protocol (UDP) provides a minimal message-passing
transport that has no inherent congestion control mechanisms.
Because congestion control is critical to the stable operation of the
Internet, applications and upper-layer 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.  This document provides guidelines on the use of
UDP for the designers of unicast applications and upper-layer
protocols.  Congestion control guidelines are a primary focus, but
the document also provides guidance on other topics, including
message sizes, reliability, checksums, and middlebox traversal.  This 
document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.

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
  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


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce