IETF Logo Mail Archive

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

Mike Belshe <mike@belshe.com> Mon, 26 July 2010 04:23 UTC

Return-Path: <mike@belshe.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 793ED3A69B7 for <hybi@core3.amsl.com>; Sun, 25 Jul 2010 21:23:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.718
X-Spam-Level:
X-Spam-Status: No, score=-1.718 tagged_above=-999 required=5 tests=[AWL=0.258, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 vZe018lEqyRn for <hybi@core3.amsl.com>; Sun, 25 Jul 2010 21:23:33 -0700 (PDT)
Received: from mail-px0-f172.google.com (mail-px0-f172.google.com [209.85.212.172]) by core3.amsl.com (Postfix) with ESMTP id 91FE13A6809 for <hybi@ietf.org>; Sun, 25 Jul 2010 21:23:33 -0700 (PDT)
Received: by pxi20 with SMTP id 20so6099569pxi.31 for <hybi@ietf.org>; Sun, 25 Jul 2010 21:23:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.231.12 with SMTP id d12mr8337441wfh.242.1280118233693; Sun, 25 Jul 2010 21:23:53 -0700 (PDT)
Received: by 10.142.74.7 with HTTP; Sun, 25 Jul 2010 21:23:53 -0700 (PDT)
In-Reply-To: <AANLkTi=Z-Zw3gJAdwQMAqG5UUVnV_kgsGm3M_qQ2Bwt7@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> <AANLkTi=Z-Zw3gJAdwQMAqG5UUVnV_kgsGm3M_qQ2Bwt7@mail.gmail.com>
Date: Sun, 25 Jul 2010 21:23:53 -0700
Message-ID: <AANLkTimCwMM-bGkYBoV_DA4EXmE5M0oV_Fqes6EVDyka@mail.gmail.com>
From: Mike Belshe <mike@belshe.com>
To: John Tamplin <jat@google.com>
Content-Type: multipart/alternative; boundary="000e0cd29ca696ff3b048c42c05b"
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:23:34 -0000

On Sun, Jul 25, 2010 at 9:22 PM, John Tamplin <jat@google.com> wrote:

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

Sounds like what you've said is that Android devices are too wimpy to do
encryption?  I bet the iPhone can handle it.  :-)

Mike



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

v2.23.0 | Report a Bug | By Email