Re: [hybi] Encourage disabling Nagle in the standard text?

Jacob Champion <champion.p@gmail.com> Wed, 19 April 2017 04:09 UTC

Return-Path: <champion.p@gmail.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 326A1126CF6 for <hybi@ietfa.amsl.com>; Tue, 18 Apr 2017 21:09:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 mSLXGEdfcIr9 for <hybi@ietfa.amsl.com>; Tue, 18 Apr 2017 21:09:37 -0700 (PDT)
Received: from mail-pf0-x229.google.com (mail-pf0-x229.google.com [IPv6:2607:f8b0:400e:c00::229]) (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 A9C8C131500 for <hybi@ietf.org>; Tue, 18 Apr 2017 21:09:37 -0700 (PDT)
Received: by mail-pf0-x229.google.com with SMTP id v14so2515327pfd.2 for <hybi@ietf.org>; Tue, 18 Apr 2017 21:09:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=eQnuSWF6tICgUNWnfl0PQxL3zp9Vi45vvBSuRZ9YPbI=; b=b4pRyTakJf637f0DkSviNygoQP/FRuTb6BxaEK8a89gh53+4spHB54BGocaDcI+OxC X9B3q5Kgn35kycxGXc4z45YWVGTygOhsfJ8Zxq67qwAgCo9XTwEU5oe7SB+WkiImjZld XH7ZpZHD3Ene9KjbuGCYAXZQs2d+2Ho24NZKWcQjEtt2aoRSg5PcEbQI/bFMmMMlxRgp 6xxVA4RYvluzoTLbvB7wu3bol7Arqsirb8M0QVsJhh4/bW0XHOtU7/IqQyVqqeIXhsFj NGHIt7QzgTiEDLjo5s/UcLjZ7WEM4UCISilkMPl9u74GIDmlr9uBknARiBV3C0ajd/Bl A2Ig==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=eQnuSWF6tICgUNWnfl0PQxL3zp9Vi45vvBSuRZ9YPbI=; b=lCGbRd0pwlaJ/viCcS6co6vJixTIYGiNC716nHaz60jch/aYZLChMGGFPa5wBtyvWm njAam882TnNhgS7JL2THAqkIuiTBSWiHpqU7RWdf7AXBQ7BFREN88wo/9Hwhb79JtJR5 vp5Crc6d5s3DGqgdkR2QRX2TjOIdGzvICEbhFqVNmFl3bleLWoOlsg5Kok5yjLeqXHyw E2lEZde2HaofCnSEYmgOgisLdOoNZGcwHdZKkQKLZsi+GqwTXuk1fsdmPqwXiKOa4ger fCxY0xJQaTydMCqCb7po3A68CcA0F5BR6cKNneeLmsk3tDK8M4BQp+z/Iz4NwdNHyhaV 1O9w==
X-Gm-Message-State: AN3rC/6Uf8xjb31ZhmmVtZ+HUcZIR4rn8iECKQHXbNDMtuKxU7WK9LVX D/KGbevwXSQisUe/6vw=
X-Received: by 10.99.216.85 with SMTP id k21mr934718pgj.10.1492574977109; Tue, 18 Apr 2017 21:09:37 -0700 (PDT)
Received: from [192.168.1.2] (50-39-112-180.bvtn.or.frontiernet.net. [50.39.112.180]) by smtp.gmail.com with ESMTPSA id z5sm1185975pfd.76.2017.04.18.21.09.36 for <hybi@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Apr 2017 21:09:36 -0700 (PDT)
To: hybi@ietf.org
References: <CAHixhFryAoF=no7_RkzxrkLFOSpSG3ACB1yBUtETp9A00sjsxw@mail.gmail.com> <B6D0F181-1482-4331-ADE1-FE92BE743208@warmcat.com>
From: Jacob Champion <champion.p@gmail.com>
Message-ID: <d44232f5-59cd-6e26-409e-7fd812245c5c@gmail.com>
Date: Tue, 18 Apr 2017 21:09:35 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <B6D0F181-1482-4331-ADE1-FE92BE743208@warmcat.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/hybi/vatYkgKkFPAsk5kdZ3CgE3mLUYY>
Subject: Re: [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 04:09:39 -0000

On 04/18/2017 07:57 PM, Andy Green wrote:
> libwebsockets always disables Nagle...

mod_websocket does too, simply because httpd disables it for all
connections.

> AFAIK there is no value to it for general ws use. But I dunno it
> needs the standard changing, if things have higher than expected
> latencies people will probably work it out for themselves.

Yeah. Seems like it would be subprotocol-specific... if I write a Telnet
clone over WebSocket, suddenly Nagle might make a lot of sense. But I'd
have to make sure to TCP_CORK my control frames so that they got flushed
through.

See also https://www.ietf.org/mail-archive/web/hybi/current/msg06895.html .

--Jacob