IETF Logo Mail Archive

Re: [hybi] Multiple connections serialization and proxies

"Thomson, Martin" <Martin.Thomson@andrew.com> Fri, 23 April 2010 00:57 UTC

Return-Path: <Martin.Thomson@andrew.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 6A9FE3A686D for <hybi@core3.amsl.com>; Thu, 22 Apr 2010 17:57:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.958
X-Spam-Level:
X-Spam-Status: No, score=-1.958 tagged_above=-999 required=5 tests=[AWL=0.641, BAYES_00=-2.599]
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 UDBeShpFxIsm for <hybi@core3.amsl.com>; Thu, 22 Apr 2010 17:57:21 -0700 (PDT)
Received: from csmailgw1.commscope.com (csmailgw1.commscope.com [198.135.207.244]) by core3.amsl.com (Postfix) with ESMTP id 9BF493A67BD for <hybi@ietf.org>; Thu, 22 Apr 2010 17:57:21 -0700 (PDT)
Received: from [10.86.20.103] ([10.86.20.103]:59489 "EHLO ACDCE7HC2.commscope.com") by csmailgw1.commscope.com with ESMTP id S18882545Ab0DWA5L (ORCPT <rfc822; hybi@ietf.org>); Thu, 22 Apr 2010 19:57:11 -0500
Received: from SISPE7HC1.commscope.com (10.97.4.12) by ACDCE7HC2.commscope.com (10.86.20.103) with Microsoft SMTP Server (TLS) id 8.1.436.0; Thu, 22 Apr 2010 19:57:11 -0500
Received: from SISPE7MB1.commscope.com ([fe80::9d82:a492:85e3:a293]) by SISPE7HC1.commscope.com ([fe80::8a9:4724:f6bb:3cdf%10]) with mapi; Fri, 23 Apr 2010 08:57:05 +0800
From: "Thomson, Martin" <Martin.Thomson@andrew.com>
To: Jamie Lokier <jamie@shareable.org>
Date: Fri, 23 Apr 2010 08:58:34 +0800
Thread-Topic: [hybi] Multiple connections serialization and proxies
Thread-Index: AcriepO3/NKkEzkdR6CozetS8FsuGAAAO+Tw
Message-ID: <8B0A9FCBB9832F43971E38010638454F03E7D06E28@SISPE7MB1.commscope.com>
References: <4BCF4932.8040303@gmail.com> <4BD09A2C.6060506@gmail.com> <x2n557ae281004221224i2a9a46c0k6f6f684c94de255c@mail.gmail.com> <8B0A9FCBB9832F43971E38010638454F03E7D06DF7@SISPE7MB1.commscope.com> <20100422225448.GG13951@shareable.org> <8B0A9FCBB9832F43971E38010638454F03E7D06E00@SISPE7MB1.commscope.com> <20100422230957.GI13951@shareable.org> <8B0A9FCBB9832F43971E38010638454F03E7D06E06@SISPE7MB1.commscope.com> <20100423001858.GA22326@shareable.org>
In-Reply-To: <20100423001858.GA22326@shareable.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-BCN: Meridius 1000 Version 3.4 on csmailgw1.commscope.com
X-BCN-Sender: Martin.Thomson@andrew.com
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] Multiple connections serialization and proxies
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: Fri, 23 Apr 2010 00:57:22 -0000

> Correct, there is no mechanism, but also no need for one since reuse
> and multiplexing don't occur.  If they're added, a virtual connection
> mechanism will be at the same time.

I think that I misread the referenced section.

Just re-read it.

So, the only protection against multi-connection-DOS from the one client is to request that the client not have more than one connection attempt in progress at a time.

This only works if the client doesn't get rejected straight away, otherwise, the round trip time is the only limiting factor, which isn't that great.

Some (security considerations) advice on what a server might do to take advantage of the client-side requirement would be good.

--Martin

v2.23.0 | Report a Bug | By Email