[tsvwg] [Fwd: I-D Action: draft-ietf-tsvwg-rfc5405bis-17.txt] - new text
gorry@erg.abdn.ac.uk Wed, 14 September 2016 08:49 UTC
Return-Path: <gorry@erg.abdn.ac.uk>
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 7FE7D12B629 for <tsvwg@ietfa.amsl.com>; Wed, 14 Sep 2016 01:49:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.408
X-Spam-Level:
X-Spam-Status: No, score=-3.408 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.508] 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 xs_YKt_j7goG for <tsvwg@ietfa.amsl.com>; Wed, 14 Sep 2016 01:49:31 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:241:204::f0f0]) by ietfa.amsl.com (Postfix) with ESMTP id 5960F12B620 for <tsvwg@ietf.org>; Wed, 14 Sep 2016 01:49:31 -0700 (PDT)
Received: from erg.abdn.ac.uk (galactica.erg.abdn.ac.uk [139.133.210.32]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 13B4C1B001B1 for <tsvwg@ietf.org>; Wed, 14 Sep 2016 11:47:59 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Wed, 14 Sep 2016 09:49:29 +0100
Message-ID: <7410465426646b090e413123cb768387.squirrel@erg.abdn.ac.uk>
Date: Wed, 14 Sep 2016 09:49:29 +0100
From: gorry@erg.abdn.ac.uk
To: tsvwg@ietf.org
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/NstcPlX6LmD45MK49hPynZkpGY0>
Subject: [tsvwg] [Fwd: I-D Action: draft-ietf-tsvwg-rfc5405bis-17.txt] - new text
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: Wed, 14 Sep 2016 08:49:35 -0000
Lars and I just submitted a new revision of this ID. This is a result of discussion with Mark Alman on the topic of advice for using timers with UDP protocols/application and the pending issue presented at TSVWG in Berlin (Mark's work on TCP timer usage was discussed in TCPM at the last IETF meeting). After working through the points in draft-ietf-tsvwg-rfc5405bis, Mark volunteered improved text for section 3.1 - Thanks Mark for helping to get the wording correct. We hope this new text resolves the issue and we can now move forward. Gorry, Lars and Greg -------------------------------------------------------------------------- A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Transport Area Working Group of the IETF. Title : UDP Usage Guidelines Authors : Lars Eggert Godred Fairhurst Greg Shepherd Filename : draft-ietf-tsvwg-rfc5405bis-17.txt Pages : 58 Date : 2016-09-14 Abstract: 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 ECN, 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 RFC5405 and adds guidelines for multicast UDP usage. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc5405bis/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-tsvwg-rfc5405bis-17 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-rfc5405bis-17 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/
- [tsvwg] [Fwd: I-D Action: draft-ietf-tsvwg-rfc540… gorry
- Re: [tsvwg] [Fwd: I-D Action: draft-ietf-tsvwg-rf… Spencer Dawkins at IETF
- Re: [tsvwg] [Fwd: I-D Action: draft-ietf-tsvwg-rf… Spencer Dawkins at IETF
- Re: [tsvwg] [Fwd: I-D Action: draft-ietf-tsvwg-rf… Black, David