Re: Giving the Framing Layer a real name

Roberto Peon <grmocg@gmail.com> Wed, 27 February 2013 22:15 UTC

Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A062121F87BA for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 27 Feb 2013 14:15:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.416
X-Spam-Level:
X-Spam-Status: No, score=-10.416 tagged_above=-999 required=5 tests=[AWL=0.182, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jbF+WdLIp-kO for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 27 Feb 2013 14:15:34 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id A973521F873D for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 27 Feb 2013 14:15:34 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UApH6-00055R-K2 for ietf-http-wg-dist@listhub.w3.org; Wed, 27 Feb 2013 22:14:56 +0000
Resent-Date: Wed, 27 Feb 2013 22:14:56 +0000
Resent-Message-Id: <E1UApH6-00055R-K2@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <grmocg@gmail.com>) id 1UApGw-00050f-N0 for ietf-http-wg@listhub.w3.org; Wed, 27 Feb 2013 22:14:46 +0000
Received: from mail-oa0-f54.google.com ([209.85.219.54]) by maggie.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <grmocg@gmail.com>) id 1UApGs-0003tI-HG for ietf-http-wg@w3.org; Wed, 27 Feb 2013 22:14:46 +0000
Received: by mail-oa0-f54.google.com with SMTP id n12so2325633oag.27 for <ietf-http-wg@w3.org>; Wed, 27 Feb 2013 14:14:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=iFBgiGCKkYUsI8uZrEwyd6t49oX7oFhaH/tyyWN/yIM=; b=IGzn+5p2fzYCmln7H+6gUBW0jSU5tw/pSQcPoeKgQnLiWsYREZ826mow31jDjjM9Jw qoIAsx/kkttkVHET9sOwpm4k/zsxHlZgU7qiUzI31np22bWEkE1BMOI/5naj3gtsoMS5 KNYr+7jZOKvO20Zg4h37VKmfqz6A9/UHNbCa43mFBrRJ8Wm7uAQY/pKh97Jy9RzgbFSd jnpaNjrGI+jJZ3hRL/QQeNcdfuoIcOWqisPKffbnkQkCSWWg5tjI/ZVNtqhE57e8PF+V l8e1dDnVSw1GG9bpBCEMwL5Uw+9qp06yWb2vS3+QU0R3/CoIml7djMyXwh1bnbhBOCjb gcbA==
MIME-Version: 1.0
X-Received: by 10.60.172.84 with SMTP id ba20mr3935110oec.10.1362003256353; Wed, 27 Feb 2013 14:14:16 -0800 (PST)
Received: by 10.76.109.72 with HTTP; Wed, 27 Feb 2013 14:14:16 -0800 (PST)
In-Reply-To: <CF77CF77-0C9A-4853-AFFF-89950FABE2FB@mnot.net>
References: <5479F0BA-C5E0-4DA0-BFA4-ECE174388C3F@mnot.net> <CABaLYCv9FdOoCooFZ4s0G4E0EHGQUEizJAGYB-BGoya7B90_9A@mail.gmail.com> <CABkgnnUWYR_scokR6DbBoFdD3ZqYF6gWqcis94tA9mHTD0o9cQ@mail.gmail.com> <CABP7Rbe5CyLFjRCRUtE8ZwO+4hdDF=2iuvaPNNqqWRCBzpT+PA@mail.gmail.com> <CAP+FsNcgQExR0mheLSE+D5Vo_B66oPBQfPhtszv3=icDuyGGYw@mail.gmail.com> <CABP7RbfU=GTOc2YunQM08q0V-cU5OzjtNOMVMRW41p8b36bnhA@mail.gmail.com> <C866B664-B753-4A6D-9E91-B521F1DED64C@mnot.net> <CABkgnnWOuq082RX26fK_XaZn+i5_fNq6rzObkXBARNfCh2RZUg@mail.gmail.com> <CF77CF77-0C9A-4853-AFFF-89950FABE2FB@mnot.net>
Date: Wed, 27 Feb 2013 14:14:16 -0800
Message-ID: <CAP+FsNeFWMYrtxRKRHrvgqNN1gCP2UMdbBoL6TyoN3uEVM7m1Q@mail.gmail.com>
From: Roberto Peon <grmocg@gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: Martin Thomson <martin.thomson@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="bcaec55408ac472f4304d6bc185d"
Received-SPF: pass client-ip=209.85.219.54; envelope-from=grmocg@gmail.com; helo=mail-oa0-f54.google.com
X-W3C-Hub-Spam-Status: No, score=-4.4
X-W3C-Hub-Spam-Report: AWL=-1.706, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001
X-W3C-Scan-Sig: maggie.w3.org 1UApGs-0003tI-HG 7a21c89801dad951814a3f45f630b46b
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Giving the Framing Layer a real name
Archived-At: <http://www.w3.org/mid/CAP+FsNeFWMYrtxRKRHrvgqNN1gCP2UMdbBoL6TyoN3uEVM7m1Q@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/16911
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

In my mind, we have a framing layer and a semantic layer.
-=R


On Wed, Feb 27, 2013 at 2:11 PM, Mark Nottingham <mnot@mnot.net> wrote:

>
> On 28/02/2013, at 9:06 AM, Martin Thomson <martin.thomson@gmail.com>
> wrote:
>
> > On 27 February 2013 13:59, Mark Nottingham <mnot@mnot.net> wrote:
> >> To me, a distinct name of a major, separable part of a protocol is only
> good spec hygiene; in HTTP we already have "representations" (nee
> "entities"), "resources" and so forth. They allow people to talk about
> different things that are happening with clarity; right now, people are
> using the term "HTTP/2.0" very, very sloppily, and that's a concern. "It
> means what I mean" is not a great basis for communication.
> >
> > I don't agree that it's separable in any real sense, which has been
> > the source of the contention.  However, I appreciate the value of a
> > handle by which we can identify important "things".  I always imagined
> > that in the few places it was necessary to refer to the concept,
> > "HTTP/2.0 framing" or "HTTP/2.0 framing layer" would suffice.
> >
> > That depends on the scope of what you are referring to, which is - I
> > believe - an important part of what we need to clarify.  Does this
> > include the creation and use of streams as well as the use of frames
> > to convey data?
>
>
> Yes, good point. We're already seeing the effect of this blurriness in
> terms of what people consider the "framing layer."
>
> To me, EVERYTHING about mapping HTTP-specific semantics is in the "HTTP"
> section; everything that's generic -- which includes streams and stream
> management -- is "below" on the framing "layer."
>
> I'm OK if we choose to use "HTTP/2.0 Framing" and stick with it -- it's
> just that it's used inconsistently now. However, this may not be the best
> name, because it has "HTTP/2.0" in it, and then we go and talk about using
> HTTP/2.0 *on* it. OTOH I'm not thrilled about introducing Yet Another
> Acronym...
>
> Cheers,
>
>
> --
> Mark Nottingham   http://www.mnot.net/
>
>
>
>
>