Re: [hybi] how do we move forward on agreeing on framing?

Roberto Peon <fenix@google.com> Fri, 20 August 2010 18:39 UTC

Return-Path: <fenix@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 EA51D3A69E8 for <hybi@core3.amsl.com>; Fri, 20 Aug 2010 11:39:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.949
X-Spam-Level:
X-Spam-Status: No, score=-103.949 tagged_above=-999 required=5 tests=[AWL=2.027, 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 vWw9Wv5Ytaw6 for <hybi@core3.amsl.com>; Fri, 20 Aug 2010 11:39:37 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id 5FE033A6B01 for <hybi@ietf.org>; Fri, 20 Aug 2010 11:39:37 -0700 (PDT)
Received: from hpaq3.eem.corp.google.com (hpaq3.eem.corp.google.com [172.25.149.3]) by smtp-out.google.com with ESMTP id o7KIeBhE001181 for <hybi@ietf.org>; Fri, 20 Aug 2010 11:40:11 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1282329611; bh=pn/iAe0gP2pZJR41teEtZmCvI5I=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=jM1Ot0C7FHd9WoXf2YNhLY8wa8gJHSe70S/CRdsC4ebRa+xmy6udnj1KmN4etZ/h/ S0tug2yt3RjxbpV+i6cSw==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:x-system-of-record; b=ZyyeDOOrR7eoqRvCGAsIfOMMCGqeRKtOWX41Bx40RcAFJwvBZQCWRALgM0w21yd8L WpALNZsggyHe6P+n7QsEg==
Received: from yxh35 (yxh35.prod.google.com [10.190.2.227]) by hpaq3.eem.corp.google.com with ESMTP id o7KIe936015327 for <hybi@ietf.org>; Fri, 20 Aug 2010 11:40:09 -0700
Received: by yxh35 with SMTP id 35so1998848yxh.40 for <hybi@ietf.org>; Fri, 20 Aug 2010 11:40:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.215.17 with SMTP id n17mr2431602ybg.44.1282329608538; Fri, 20 Aug 2010 11:40:08 -0700 (PDT)
Received: by 10.150.95.11 with HTTP; Fri, 20 Aug 2010 11:40:08 -0700 (PDT)
In-Reply-To: <1282329287.8341.152.camel@vulcan.aspl.local>
References: <AANLkTineuhvGsC_vca6AiAX8OmHdkE-7s7rA1DQtjtMm@mail.gmail.com> <1282231803.22142.649.camel@vulcan.aspl.local> <AANLkTim44=x0BRpF3BYMqS9GNzHA+icG818JgfRRaFPT@mail.gmail.com> <1282238100.22142.732.camel@vulcan.aspl.local> <AANLkTinst1+-iTjJXfBypoOjwc+QNdVt85QopdM9w4nZ@mail.gmail.com> <1282245566.10518.11.camel@tot.local> <1282314477.2266.10.camel@tng> <1282329287.8341.152.camel@vulcan.aspl.local>
Date: Fri, 20 Aug 2010 11:40:08 -0700
Message-ID: <AANLkTi=RPzHiwmYox_dhQMvX_3B0--ApaCcEWNsT-crs@mail.gmail.com>
From: Roberto Peon <fenix@google.com>
To: Francis Brosnan Blazquez <francis@aspl.es>
Content-Type: multipart/alternative; boundary="000e0cd2e6accd4a23048e45a051"
X-System-Of-Record: true
Cc: Hybi <hybi@ietf.org>
Subject: Re: [hybi] how do we move forward on agreeing on framing?
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, 20 Aug 2010 18:39:39 -0000

On Fri, Aug 20, 2010 at 11:34 AM, Francis Brosnan Blazquez
<francis@aspl.es>wrote:

> > I don't agree with such a broad brushed statement like that at all.
> > Layers are a convenient way to think about things, but truly layered
> > implementations are almost always inferior.
> >
> > See varghese's _network algorithmics_ for an amazing treatment of the
> > topic.
> > (
> http://www.amazon.com/Network-Algorithmics-Interdisciplinary-Designing-Networking/dp/0120884771/ref=sr_1_1?ie=UTF8&s=books&qid=1282314428&sr=8-1)
> >
> > Protocol designers might use layers as a useful way to articulate the
> > protocol, but it is incumbent on us to consider all the various
> > requirements of different implementation scenarios. That often means
> > layering violations in practice. And that's ok.
>
> Obviously we can't take any rule as inviolable, and obviously perfect
> layer separation is not possible nor desirable...however, what we have
> here is a flagrant attempt to design a complex protocol that was
> expected to only provide transport.
>


Yes, but what does it mean to only transport? Do you want it reliably?
Scalably?
There have been flagrant attempts to do both of these things :)
There have also been attempts to ensure that we have a modicum of security.
These all add complexity and are potentially compelling end results.


>
> It is clear in our particular case, websocket, that it will provide far
> more better benefits if the protocol, as long as possible, keeps its
> features at the transport level, letting other specialized application
> protocols on top of it to provide what the user is looking for.
>
> Without considering the websocket final design, inevitably people will
> layer its favorite protocol on top of it. Assuming that, WG should focus
> on providing features that won't be provided by upper level apps, AND,
> as long as possible do to include features that are already available on
> them.
>


And, hopefully, to reduce overall system complexity by putting complexity in
the appropriate places.
-=R


> --
> Francis Brosnan Blazquez <francis@aspl.es>
> ASPL
>
>