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

Maciej Stachowiak <mjs@apple.com> Sun, 31 January 2010 00:47 UTC

Return-Path: <mjs@apple.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 D93813A67B3 for <hybi@core3.amsl.com>; Sat, 30 Jan 2010 16:47:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.577
X-Spam-Level:
X-Spam-Status: No, score=-106.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 RmxRGQeKViC5 for <hybi@core3.amsl.com>; Sat, 30 Jan 2010 16:47:54 -0800 (PST)
Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id BFF383A67A8 for <hybi@ietf.org>; Sat, 30 Jan 2010 16:47:53 -0800 (PST)
Received: from relay16.apple.com (relay16.apple.com [17.128.113.55]) by mail-out4.apple.com (Postfix) with ESMTP id EBC608965739 for <hybi@ietf.org>; Sat, 30 Jan 2010 16:48:21 -0800 (PST)
X-AuditID: 11807137-b7bd4ae000000f0d-99-4b64d355c4ee
Received: from et.apple.com (et.apple.com [17.151.62.12]) by relay16.apple.com (Apple SCV relay) with SMTP id 3F.06.03853.553D46B4; Sat, 30 Jan 2010 16:48:21 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: text/plain; charset="us-ascii"
Received: from [10.0.1.5] (c-69-181-42-237.hsd1.ca.comcast.net [69.181.42.237]) by et.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0KX300G2L68KAM70@et.apple.com> for hybi@ietf.org; Sat, 30 Jan 2010 16:48:21 -0800 (PST)
From: Maciej Stachowiak <mjs@apple.com>
In-reply-to: <5c902b9e1001301600g205fe7cfoc8f314e742ec50c6@mail.gmail.com>
Date: Sat, 30 Jan 2010 16:48:20 -0800
Message-id: <D8121C48-82F3-4C87-9A0D-51DC1CBA1593@apple.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> <5c902b9e1001301600g205fe7cfoc8f314e742ec50c6@mail.gmail.com>
To: Justin Erenkrantz <justin@erenkrantz.com>
X-Mailer: Apple Mail (2.1077)
X-Brightmail-Tracker: AAAAAQAAAZE=
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:47:54 -0000

On Jan 30, 2010, at 4:00 PM, Justin Erenkrantz wrote:

> 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.

Surely HTTP headers in the handshake are an appropriate place for protocol metadata?

> 
> 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.  --

This doesn't help you with detecting unaware intermediaries, or with letting intermediaries participate if you are going over SSL.

Regards,
Maciej