Re: [hybi] Insight you need to know: Browsers are at fault when servers crash

John Tamplin <jat@google.com> Mon, 26 July 2010 04:22 UTC

Return-Path: <jat@google.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 29A073A6912 for <hybi@core3.amsl.com>; Sun, 25 Jul 2010 21:22:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.976
X-Spam-Level:
X-Spam-Status: No, score=-105.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 Nabo713xkI5t for <hybi@core3.amsl.com>; Sun, 25 Jul 2010 21:22:12 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 1B8E53A6809 for <hybi@ietf.org>; Sun, 25 Jul 2010 21:22:12 -0700 (PDT)
Received: from wpaz37.hot.corp.google.com (wpaz37.hot.corp.google.com [172.24.198.101]) by smtp-out.google.com with ESMTP id o6Q4MW6Z011541 for <hybi@ietf.org>; Sun, 25 Jul 2010 21:22:32 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1280118152; bh=aBpN8iXAOnol62zaykWxo5EHR+Q=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=wzJYiyB7mv7iwVXN/bG4f9xrTPLM+cbxDsPdtTbJVr64KMnmX6IPYSnjl+0ZPbZWc k/WHQGl0hD3U5xFwvo8WA==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:from:date:message-id: subject:to:cc:content-type:x-system-of-record; b=P4QMr3S3ujI4vtdFAO7KlVhlgXvAtWG7HXaroFFwWVxHNA7xpiN7R8ieubsfvyAsY NhbR0i55golajiqvFd3Ig==
Received: from gxk6 (gxk6.prod.google.com [10.202.11.6]) by wpaz37.hot.corp.google.com with ESMTP id o6Q4MV7o027050 for <hybi@ietf.org>; Sun, 25 Jul 2010 21:22:31 -0700
Received: by gxk6 with SMTP id 6so1103860gxk.2 for <hybi@ietf.org>; Sun, 25 Jul 2010 21:22:31 -0700 (PDT)
Received: by 10.150.176.3 with SMTP id y3mr8326312ybe.431.1280118151072; Sun, 25 Jul 2010 21:22:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.151.60.3 with HTTP; Sun, 25 Jul 2010 21:22:11 -0700 (PDT)
In-Reply-To: <AANLkTi=Q-PVrdaWuOu3H=wUiphe6JB4C+LauSOXKozoY@mail.gmail.com>
References: <AANLkTilfxps1wWjFrwrH_3Js6Q9E331AMKFRNHfeHcdL@mail.gmail.com> <AANLkTi=vPAnnK0=gE=YN10vt9b-f6sWXXcwK+La5SriO@mail.gmail.com> <623C6D70-B4AF-49EC-BA07-6F90BD0FFFBF@apple.com> <AANLkTi=Q-PVrdaWuOu3H=wUiphe6JB4C+LauSOXKozoY@mail.gmail.com>
From: John Tamplin <jat@google.com>
Date: Mon, 26 Jul 2010 00:22:11 -0400
Message-ID: <AANLkTi=Z-Zw3gJAdwQMAqG5UUVnV_kgsGm3M_qQ2Bwt7@mail.gmail.com>
To: Mike Belshe <mike@belshe.com>
Content-Type: multipart/alternative; boundary="000e0cd7620aaa4de3048c42bb12"
X-System-Of-Record: true
Cc: hybi@ietf.org
Subject: Re: [hybi] Insight you need to know: Browsers are at fault when servers crash
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: Mon, 26 Jul 2010 04:22:13 -0000

On Mon, Jul 26, 2010 at 12:00 AM, Mike Belshe <mike@belshe.com> wrote:

> Adam has also suggested encrypting the channel.  Even without TLS, this
> would go a long way toward preventing attackers from sending particular byte
> patterns over the wire, and could probably be done without adding
> round-trips.
>

Would it be worth having a requirement saying something about a target
platform?  I worry about requiring encryption if we are including embedded
devices as target platforms - any encryption worth doing may be an
unacceptable burden for such platforms.

-- 
John A. Tamplin
Software Engineer (GWT), Google