[hybi] Encourage disabling Nagle in the standard text?

Adam Rice <ricea@chromium.org> Wed, 19 April 2017 02:34 UTC

Return-Path: <ricea@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 693A112EB30 for <hybi@ietfa.amsl.com>; Tue, 18 Apr 2017 19:34:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com header.b=TsDDNX20; dkim=pass (1024-bit key) header.d=chromium.org header.b=ccb3uFvR
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 egQ0WnBR1rW1 for <hybi@ietfa.amsl.com>; Tue, 18 Apr 2017 19:34:36 -0700 (PDT)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (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 0B350128D44 for <hybi@ietf.org>; Tue, 18 Apr 2017 19:34:36 -0700 (PDT)
Received: by mail-wm0-x230.google.com with SMTP id m123so264144wma.0 for <hybi@ietf.org>; Tue, 18 Apr 2017 19:34:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:sender:from:date:message-id:subject:to; bh=hyCtBCrHq+sAkdLp+ikQbYeOrEn1VKuHNMDKf17aAcc=; b=TsDDNX20POTvan54pg/l6Lolyfq1HSQq//j1ldMWQxDu0LHFTMk1dRewdTduJ6yS9R t9AzIxO9wUSnolmZFJvoYak/93WwX9W6bcCkheH9DmnRDg5iXwDNLXg38y0R1F+brlRh zt1zC5g86JhElgk9/Y/iFzmlg32D5tUGxYJA8aHhYHz5QKwLrs9tLHpaf7Q/nkGQ3S8r LA8oGRgYvPzgIWtNsUV+M1xD0kqZxMg9GsCfXf4gEVjCcALM0G/d+9pT34tZycMep7u5 R67w/1TBUvvoOUSKgDQI3Ga0nug2rOiqNEv7mkR9ytKnzswAkpKfQvw+Aq2AklC2+i2f fy1g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:sender:from:date:message-id:subject:to; bh=hyCtBCrHq+sAkdLp+ikQbYeOrEn1VKuHNMDKf17aAcc=; b=ccb3uFvRIMj0QYhH6xUobjfqqVhaBkRsy2I7nD/Mu9emo4sHPbp7xC+ItkW1nPYd/R EPRdBpi6ueED/OxHC/RBq/qLLHdUCQkQSFfsashNoYy9aSBqFuN2VhfBTqiVWFoNppCM ytqEWRmwru/X4Bl2xZmAWIANQuoT2jG48deeg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=hyCtBCrHq+sAkdLp+ikQbYeOrEn1VKuHNMDKf17aAcc=; b=Uh/AukoyWZO4Yx0YVn78/sHY90pCcxoBHoAdPAoFEBFtyNWL4tI9JRX2fEvFjt+kOJ OoevPQ2Dp5IgcYxHZqO3gPMgftMSAyh988cm9AMHxj+QKk/xNtvTVP3mONeH9gLHAYsP 6ZmfaYB7ULB8aMzAsbR7TR27AYIZJTIaJak6hTVeXPJC0h/Vh5VSvLt9nTsv5mjUcNMu piqcrfmju0ALHnqMA3GQy2LrdI9UOcBNYq7WWUpEx5/ravJGIvYQNIsrFDJovIpoTBeQ zAujIwNZP9hh8XJHOrRulQee6FnnSB+UlRtIjST/WEn4VDbYOun1s/bf4wdKx2IzGdwS 5aEw==
X-Gm-Message-State: AN3rC/7ka3DcmStVkzyLyaUSgFMvNKHcsGLRrn7BiWa0rfJb44kf8ZEg eUn9WQNgsuyNT+y+33nb/j5TN787pKFRrQQ34A==
X-Received: by 10.28.22.3 with SMTP id 3mr1627558wmw.86.1492569274226; Tue, 18 Apr 2017 19:34:34 -0700 (PDT)
MIME-Version: 1.0
Sender: ricea@google.com
Received: by 10.28.166.130 with HTTP; Tue, 18 Apr 2017 19:34:33 -0700 (PDT)
From: Adam Rice <ricea@chromium.org>
Date: Wed, 19 Apr 2017 11:34:33 +0900
X-Google-Sender-Auth: LQ8nka85Ndd7aP5rLBdcG023vQI
Message-ID: <CAHixhFryAoF=no7_RkzxrkLFOSpSG3ACB1yBUtETp9A00sjsxw@mail.gmail.com>
To: "hybi@ietf.org" <hybi@ietf.org>
Content-Type: multipart/alternative; boundary=001a1145bd3a64ec90054d7bdd9e
Archived-At: <https://mailarchive.ietf.org/arch/msg/hybi/FPxUYTCiZHgQa4-ZsecvBdlhsLU>
Subject: [hybi] Encourage disabling Nagle in the standard text?
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hybi/>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 02:34:37 -0000

Numerous developers have run into issues when using WebSocket servers that
have the Nagle algorithm enabled [Citation:
https://www.google.com/search?q=websocket+nagle]. My impression is that
this ends up with most WebSocket servers disabling Nagle.

I am wondering if it would be better if the standard had text to the effect
that implementations SHOULD disable Nagle (ie. set TCP_NODELAY on the
socket).

Does anyone have any use cases where Nagle is beneficial?

For reference, Chrome always disables Nagle. pywebsocket doesn't (but
probably should).