Re: [tsvwg] [Fwd: I-D Action: draft-ietf-tsvwg-rfc5405bis-17.txt] - new text

"Black, David" <David.Black@dell.com> Tue, 20 September 2016 20:02 UTC

Return-Path: <David.Black@dell.com>
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 2127712B503 for <tsvwg@ietfa.amsl.com>; Tue, 20 Sep 2016 13:02:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level:
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=fail (1024-bit key) reason="fail (message has been altered)" header.from=David.Black@dell.com header.d=dell.com; dkim=pass (1024-bit key) header.d=dell.com header.b=yqvvD1gk; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=emc.com header.b=aIBj54yk
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 XWGWe3F1Y88F for <tsvwg@ietfa.amsl.com>; Tue, 20 Sep 2016 13:02:35 -0700 (PDT)
Received: from esa3.dell-outbound.iphmx.com (esa3.dell-outbound.iphmx.com [68.232.153.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C09A512B4F0 for <tsvwg@ietf.org>; Tue, 20 Sep 2016 12:59:36 -0700 (PDT)
DomainKey-Signature: s=smtpout; d=dell.com; c=simple; q=dns; h=Received:From:Cc:Received:Received:X-DKIM:DKIM-Signature: X-DKIM:Received:Received:Received:To:Subject:Thread-Topic: Thread-Index:Date:Message-ID:References:In-Reply-To: Accept-Language:Content-Language:X-MS-Has-Attach: X-MS-TNEF-Correlator:x-originating-ip:Content-Type: MIME-Version:X-Sentrion-Hostname:X-RSA-Classifications; b=aBL+JifarINe0tIbZQqbQyAt8JX3cJf5ncjGIdbDFwgqaJEmCwXMZbOI hazvaFQ2a245GO3MXQXTkLc42/mDe4wltsksXIhbpoR3XtOvFNnvAZKaC qm9kt9BcrN95mxHjlSKQ8CPKc7s/CSAckhb0g2SBORDuWwBBJw5gOICy7 0=;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dell.com; i=@dell.com; q=dns/txt; s=smtpout; t=1474401576; x=1505937576; h=from:cc:to:subject:date:message-id:references: in-reply-to:mime-version; bh=rrsgHvMTg94H5OKUqwsT83wBBWY5hvAhD+Qh0o3kXzM=; b=yqvvD1gkFf53AEpZj9KxTXhM5HnfoqCSjUPIzBCPlz3MsD68GUyAtFqX fpLPMRDulCftezH60Bk3nlx9vfHA6GgBAT4IIsUwoBT1DlAAawg20Vzxb TqA1jzboIjZJxC0Y/b2IMaszw+P7KaZdvTih4F02pH4bo0RzbV8TZ+Mz6 Y=;
Received: from esa1.dell-outbound2.iphmx.com ([68.232.153.201]) by esa3.dell-outbound.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Sep 2016 14:59:36 -0500
From: "Black, David" <David.Black@dell.com>
Received: from mailuogwdur.emc.com ([128.221.224.79]) by esa1.dell-outbound2.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Sep 2016 01:59:35 +0600
Received: from maildlpprd53.lss.emc.com (maildlpprd53.lss.emc.com [10.106.48.157]) by mailuogwprd54.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id u8KJxWjj007320 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 20 Sep 2016 15:59:33 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd54.lss.emc.com u8KJxWjj007320
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1474401575; bh=YMPp9ffWFmbkJggu0SJZTBqKNgQ=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:MIME-Version; b=aIBj54ykAJMDKrFuczDJNoZlOLZ4FO/u8am4OTkSHoVAgn/zi4vt7rLPGcMhA27Ka USUo5va15gLtsshUz+YnVdoYvZLKwGbErPANhE6cF8b/Zu43eIaFv/5SIk8h/KIXXm omwmTIgYNAZI0Vf+kc1h8IcPCCH1cSGE3p7/x7cI=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd54.lss.emc.com u8KJxWjj007320
Received: from mailusrhubprd52.lss.emc.com (mailusrhubprd52.lss.emc.com [10.106.48.25]) by maildlpprd53.lss.emc.com (RSA Interceptor); Tue, 20 Sep 2016 15:58:43 -0400
Received: from MXHUB316.corp.emc.com (MXHUB316.corp.emc.com [10.146.3.94]) by mailusrhubprd52.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id u8KJxG6m005942 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Tue, 20 Sep 2016 15:59:16 -0400
Received: from MX307CL04.corp.emc.com ([fe80::849f:5da2:11b:4385]) by MXHUB316.corp.emc.com ([10.146.3.94]) with mapi id 14.03.0266.001; Tue, 20 Sep 2016 15:59:15 -0400
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>
Thread-Topic: [tsvwg] [Fwd: I-D Action: draft-ietf-tsvwg-rfc5405bis-17.txt] - new text
Thread-Index: AQHSDmTvMmqAs41HAkSOSp7Pe5IY9qCDEQ2A//+/XCA=
Date: Tue, 20 Sep 2016 19:59:15 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949362F69BFC1@MX307CL04.corp.emc.com>
References: <7410465426646b090e413123cb768387.squirrel@erg.abdn.ac.uk> <CAKKJt-c67hAZiwK7kDpPiVJCg3xS162ppcHCnXz-T4mdvp2WPA@mail.gmail.com>
In-Reply-To: <CAKKJt-c67hAZiwK7kDpPiVJCg3xS162ppcHCnXz-T4mdvp2WPA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.97.22.247]
Content-Type: multipart/alternative; boundary="_000_CE03DB3D7B45C245BCA0D243277949362F69BFC1MX307CL04corpem_"
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd52.lss.emc.com
X-RSA-Classifications: public
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/vKZRAOFEg79hVTXP2MTE9ZdDp54>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [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: Tue, 20 Sep 2016 20:02:37 -0000

Hi Spencer,

> I'm not seeing any responses to this on the TSVWG mailing list. Is this ready to go?

As draft shepherd, I believe that the timer-related issues were the only technical item needing resolution after Berlin.
With the rewritten text in 3.1.1 having resolved those issues, I t think this draft is ready to go.

Thanks, --David

From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of Spencer Dawkins at IETF
Sent: Tuesday, September 20, 2016 3:30 PM
To: gorry@erg.abdn.ac.uk
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] [Fwd: I-D Action: draft-ietf-tsvwg-rfc5405bis-17.txt] - new text

Hi, Gorry,

On Wed, Sep 14, 2016 at 3:49 AM, <gorry@erg.abdn.ac.uk<mailto:gorry@erg.abdn.ac.uk>> wrote:

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.

I hope so, too, of course!

I'm not seeing any responses to this on the TSVWG mailing list. Is this ready to go?

I'm assuming we're close, so getting ready to put this on a telechat agenda. I've been copied on (most of?) the discussion since IETF Last Call, so I'm not surprised at the changes in https://tools.ietf.org/rfcdiff?url1=draft-ietf-tsvwg-rfc5405bis-13.txt&url2=draft-ietf-tsvwg-rfc5405bis-17.txt. Thanks for that.

It's in previous versions, too, but

   required when operating over the general.

should be

   required when operating over the general Internet.

The authors can fix that (quickly) if they agree, or I can put it in my Yes ballot when we start IESG Evaluation (but reviewers who are assigned to re-review at telechat time may also notice it and complain). Please let me know which you prefer.

Spencer

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<http://tools.ietf.org>.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/