IETF Logo Mail Archive

Re: [hybi] Intermediaries and idle connections (was Re: Technical feedback.)

Justin Erenkrantz <justin@erenkrantz.com> Sun, 31 January 2010 00:04 UTC

Return-Path: <justin.erenkrantz@gmail.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E4F9C3A6828 for <hybi@core3.amsl.com>; Sat, 30 Jan 2010 16:04:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level:
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[AWL=-0.034, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8FHO6UCWHgPz for <hybi@core3.amsl.com>; Sat, 30 Jan 2010 16:04:55 -0800 (PST)
Received: from mail-yx0-f194.google.com (mail-yx0-f194.google.com [209.85.210.194]) by core3.amsl.com (Postfix) with ESMTP id 21EC13A6782 for <hybi@ietf.org>; Sat, 30 Jan 2010 16:04:55 -0800 (PST)
Received: by yxe32 with SMTP id 32so21600yxe.5 for <hybi@ietf.org>; Sat, 30 Jan 2010 16:05:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=V0U59354QydK96rQTNqeNb3McV/jnMwojmkVe5G/ruA=; b=YoRH4TSsAx/lNGLaEfuN43iLm2gdvcMgVtj7NXwt4fQXagsV+IlXFgqL9qG1gCuz9p ky3Z7bhdRglLj7HCQwNBOcMODJkSF8SJ6TAUu6VfcR2olQj01Ru/gDfAKWgaodjfOEej ntO4T0TCcdZ9LVDMwC+y0++2w/9VJXW/ThTMM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=sXcw9O0OJwhXJ1cQfsR17xI917/f1bugFpP2yrCDG7HfcHQ/5Ag/RsdzB3rG6C/7Yu dqXSDehba4w0rDS8WRUP+HdKvCVJ521JUQ3RRzE7K4pxxEWnMtUqxyQ5ui0UkgnP6VGA RJT7rkl6fUAZBoAleR2Kek8klfRNNO78b9cOA=
MIME-Version: 1.0
Sender: justin.erenkrantz@gmail.com
Received: by 10.91.97.14 with SMTP id z14mr2458259agl.0.1264896013198; Sat, 30 Jan 2010 16:00:13 -0800 (PST)
In-Reply-To: <4B64B179.9050502@webtide.com>
References: <de17d48e1001280012i2657b587i83cda30f50013e6b@mail.gmail.com> <4B62C5FE.8090904@it.aoyama.ac.jp> <Pine.LNX.4.64.1001291134350.22020@ps20323.dreamhostps.com> <4B62E516.2010003@webtide.com> <5c902b9e1001290756r3f585204h32cacd6e64fbebaa@mail.gmail.com> <4B636757.3040307@webtide.com> <E379EA13-D58A-4BFB-A62D-2B931A54E276@apple.com> <4B63DD6B.5030803@webtide.com> <E765982E-06B5-48BC-B75D-02E3F9555018@apple.com> <4B64B179.9050502@webtide.com>
Date: Sat, 30 Jan 2010 16:00:13 -0800
X-Google-Sender-Auth: 279b55acf5d09363
Message-ID: <5c902b9e1001301600g205fe7cfoc8f314e742ec50c6@mail.gmail.com>
From: Justin Erenkrantz <justin@erenkrantz.com>
To: Greg Wilkins <gregw@webtide.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: Hybi <hybi@ietf.org>
Subject: Re: [hybi] Intermediaries and idle connections (was Re: Technical feedback.)
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 31 Jan 2010 00:04:56 -0000

On Sat, Jan 30, 2010 at 2:23 PM, Greg Wilkins <gregw@webtide.com> wrote:
>> this. Do they respect the fixed list of hop-by-hop headers? Do they treat headers listed in the Connection header field as hop-by-hop?
>
> I think a hop-by-hop header is exactly what is needed, so that any non transparent
> proxy would have to explicitly copy the timeout value from input to output.

While I grok the rationale for hop-by-hop headers, I'd really like to
come to some way to cleanly separate content meta-data from protocol
meta-data.  IMO, it makes stuff like caching and intermediaries way
too hard to implement.

Spitballing an idea: if we have some way to multiplex over a single
connection (channels, etc.), then we can have a "protocol"
meta-channel or similar for exchanging hop-by-hop capabilities.  --
justin

v2.23.0 | Report a Bug | By Email