IETF Logo Mail Archive

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

Justin Erenkrantz <justin@erenkrantz.com> Sun, 31 January 2010 00:30 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 6400F3A683F for <hybi@core3.amsl.com>; Sat, 30 Jan 2010 16:30:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.007
X-Spam-Level:
X-Spam-Status: No, score=-2.007 tagged_above=-999 required=5 tests=[AWL=-0.030, 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 3VKN6mI8-JNy for <hybi@core3.amsl.com>; Sat, 30 Jan 2010 16:30:14 -0800 (PST)
Received: from mail-gx0-f226.google.com (mail-gx0-f226.google.com [209.85.217.226]) by core3.amsl.com (Postfix) with ESMTP id 7521A3A6829 for <hybi@ietf.org>; Sat, 30 Jan 2010 16:30:14 -0800 (PST)
Received: by gxk26 with SMTP id 26so1381253gxk.8 for <hybi@ietf.org>; Sat, 30 Jan 2010 16:30:39 -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:content-transfer-encoding; bh=V0jnRuja7JtWU/cZC3nbpZxq11hI67EG5i2RDt8efIM=; b=mpMn7HmHFt5VMnmNc/DeTjMyDcIi6qLCakZ3y1oLI20uyJImG/y26QCMjekZtd9TL0 c/pDn1Hz8R5MnwDNJ8+fHX7wghUsJm5hZkK5rG9g1ujHNF8qgKgNoeqDj8fu4AY744zw +5NHi20ZqEDBHhgr8s2zRnpwRXmf3Rrl1Ee6I=
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 :content-transfer-encoding; b=C65MsJrSU1Fnfymv+03w4b+FHx9FzcROGaPc0JUCQVhXbf1ZZIytIJ2CoJNkWI2kz6 jWryLNpR7OZ1bAPeLeCjdcODQDLFp1kltMEO+cOVJN51UhDtbP32uWIRJnUXhkOZOj3S ewSg7cG5QygNcEKaIfubbSXYYeJ8qhlLIj84A=
MIME-Version: 1.0
Sender: justin.erenkrantz@gmail.com
Received: by 10.91.18.5 with SMTP id v5mr2432745agi.62.1264897839742; Sat, 30 Jan 2010 16:30:39 -0800 (PST)
In-Reply-To: <4B64CD92.206@webtide.com>
References: <de17d48e1001280012i2657b587i83cda30f50013e6b@mail.gmail.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> <4B64CD92.206@webtide.com>
Date: Sat, 30 Jan 2010 16:30:39 -0800
X-Google-Sender-Auth: 92b75ec967194535
Message-ID: <5c902b9e1001301630t6c4d70aeg88876c85963b1bf5@mail.gmail.com>
From: Justin Erenkrantz <justin@erenkrantz.com>
To: Greg Wilkins <gregw@webtide.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
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:30:15 -0000

On Sat, Jan 30, 2010 at 4:23 PM, Greg Wilkins <gregw@webtide.com> wrote:
> Justin,  in this case, the hop-by-hop header is only applicable
> to the initial upgrade HTTP request and not to the actual data channel
> once established.

Ah, yes, if it's confined to the original Upgrade HTTP request, yah,
you can't run away from hop-by-hop headers there.

> I also think there is a need for out-of-band meta data to be
> exchanged once the channel is established, but I think that should
> be considered separately.

Fair 'nuf.  -- justin

v2.23.0 | Report a Bug | By Email