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

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Tue, 20 September 2016 19:30 UTC

Return-Path: <spencerdawkins.ietf@gmail.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 EAA4A12B478 for <tsvwg@ietfa.amsl.com>; Tue, 20 Sep 2016 12:30:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 NfKk4R-y-VcM for <tsvwg@ietfa.amsl.com>; Tue, 20 Sep 2016 12:30:09 -0700 (PDT)
Received: from mail-yw0-x234.google.com (mail-yw0-x234.google.com [IPv6:2607:f8b0:4002:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB87612B48C for <tsvwg@ietf.org>; Tue, 20 Sep 2016 12:30:08 -0700 (PDT)
Received: by mail-yw0-x234.google.com with SMTP id g192so19230558ywh.1 for <tsvwg@ietf.org>; Tue, 20 Sep 2016 12:30:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=H4XHOIqWyA5dy/5V38tJyPaWNfgocvA/P6Zd2hj07Jw=; b=JBwuPMOvRmJ//bF9kSszzVJSpc1C1sQefA7eqDo4+dnf3gzhiAOXAttQcZOh/oPO6G zky7if/jGTLiJH+NZPRJtp8ZxpCy97aSvzjkyaJdpblZndxgX/l/YuTMxuwzR02k6+qo hZf+Sql6SALep5itLIGp9Q5CQjxyphhAzR+UfnhiA8rnSYDzAEWdDtkkDjh+zHNBGh0p pbNBXUgYXSTHUyGEgOhTHEM1uNiRQ5nvx6YW5EOh3LDixBDkfPiMaRt0HYLOx6JodQ4Q xYQNG576gJEWy9KpwAS3gvqDJ5oPAyWcQy2mntXZ5lOsIx+mLoCQKC8K/yGBzclLctDC fHrA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=H4XHOIqWyA5dy/5V38tJyPaWNfgocvA/P6Zd2hj07Jw=; b=EFbI7D5rv9D+7fexhULmQFwdIsZPZwxS3mRWxjuwo1xAl9qxkPqp693qVKjqC2I4sF 7oRkSgtpiRUsmcV2N6AjVRmT7QvCqefev8rBq0nrRqaA5vky9Vbw6PkxqwOF2+EABD4/ 0YHIgoYv7MxVFDst9QQlFvBY7yBmelEJUyeEirco046nST25CglQ83w+g9Y0o0mvYm7f +MuqDkNGNIDnMaZor1F/+bLQYEjoAMB/8l7I0yS7yNVnZJ7jj5Ri6BDecXXc/4MH1u5e czmp7eVi/9dMsxAU3hTJupVLHmJ/iOrPj6hYMtjZHfVE7b6HJUJ78w/d7ubsfvsIwPwD bJDw==
X-Gm-Message-State: AE9vXwMzFgutatK1BS5bsiO5Ho9rohcy8iOBJhs3Hf61HimFfSjEtFEMGf3ybyw62ENN4NXmofWi411XUvgSqg==
X-Received: by 10.129.161.86 with SMTP id y83mr24389085ywg.61.1474399808132; Tue, 20 Sep 2016 12:30:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.24.86 with HTTP; Tue, 20 Sep 2016 12:30:07 -0700 (PDT)
In-Reply-To: <7410465426646b090e413123cb768387.squirrel@erg.abdn.ac.uk>
References: <7410465426646b090e413123cb768387.squirrel@erg.abdn.ac.uk>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 20 Sep 2016 14:30:07 -0500
Message-ID: <CAKKJt-c67hAZiwK7kDpPiVJCg3xS162ppcHCnXz-T4mdvp2WPA@mail.gmail.com>
To: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>
Content-Type: multipart/alternative; boundary="001a114f8d26d21cdb053cf5749e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/OMIalnVUeMuCYSRjrE3o2nxIw6g>
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 19:30:12 -0000

Hi, Gorry,

On Wed, Sep 14, 2016 at 3:49 AM, <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.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
>