Re: [quicwg/base-drafts] We have two things called "frame" (#128)

Patrick McManus <notifications@github.com> Fri, 28 April 2017 13:26 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0ACC2126B6D for <quic-issues@ietfa.amsl.com>; Fri, 28 Apr 2017 06:26:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.801
X-Spam-Level:
X-Spam-Status: No, score=-4.801 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PG8jokXtaFrZ for <quic-issues@ietfa.amsl.com>; Fri, 28 Apr 2017 06:26:32 -0700 (PDT)
Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E219A12E6A3 for <quic-issues@ietf.org>; Fri, 28 Apr 2017 06:23:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=7P4wGULgrGU7gc5wjiNDgwPXsYc=; b=VRIuP3TNhpdw/BzV jylsaqS24c86R1ak1R3c94RZYXwCKsZ6M2MwA5tQGAuZxkAEOwPivTpXljf3Y+dk Hi3huJki+zBqaCv47a8xuJFuVNgpxnBSGpQcOv/SPG2COal9Or7GQfAxpfgqnEJb QWgoP4gI0xTZzK88s8r9+rOqbTk=
Received: by filter1080p1mdw1.sendgrid.net with SMTP id filter1080p1mdw1-15251-59034244-33 2017-04-28 13:23:16.422297451 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id n-abaXgrQGW8hirQ0GJ3Jw for <quic-issues@ietf.org>; Fri, 28 Apr 2017 13:23:16.252 +0000 (UTC)
Date: Fri, 28 Apr 2017 06:23:16 -0700
From: Patrick McManus <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abcb608f1a98d3d218d1b3b140647e7ed4a33207c592cf00000001151b044492a169ce0bde5924@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/128/297996392@github.com>
In-Reply-To: <quicwg/base-drafts/issues/128@github.com>
References: <quicwg/base-drafts/issues/128@github.com>
Subject: Re: [quicwg/base-drafts] We have two things called "frame" (#128)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_590342441b0e0_1ca43f80bcde7c3c632c5"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mcmanus
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3+yD0p/yXy1trG5oIylskVytHx5yb6aTAre/ PGGjEx5r6D3XT9CINirgZcu0X+He/0TzD/q/hbiBpkKYy4csuHwo+FBUDdznqBGOdSWKdQBvrYbNl2 Sl01nkmdMv9dbezoxeHSuhdZr5cwCon8ln+6OgN9eqgAb3qBhfVrKpGgdM/XdeYpuAK4Ew/5+fuYhH o=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/eMqbHUIPQlfmTztJPJv1wR0D6xc>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 13:26:34 -0000

I don't like quic-segments because
1] it implies an ordering (and seqno) and the quic-frames aren't really
ordered unless they are streams
2] the term doesn't line up well with tcp segments (which are 1:1 with
unfragmented IP).. and quic and tcp are at the same 'layer' - so confusion.

The best (but still imperfect) solution I have is to change http frame to
http record. It overlaps with TLS of course (which isn't all that
desirable), but it uses the term pretty much the same way - to provide
delimiters within a QUIC stream.

The other idea I had was "http-control-segments".. I think segment is a
better fit here as compared against renaming all quic frames to quic
segments (again ordering and offset are present) and it emphasizes the
native integration between hq and quic for data but not control.

I'm not especially concerned that we would be changing the h2-frame
language.. HQ doesn't need framing in many of the same places that H2 did
so a change in nomenclature is ok to avoid confusion with the transport.


On Fri, Apr 28, 2017 at 12:48 AM, Mark Nottingham <notifications@github.com>
wrote:

> H2 already has frames; maybe the new thing should have the new name. E.g.,
> 'QUIC segments".
>
> YMMV.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/issues/128#issuecomment-297906141>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAP5s58K4M7rtBP3eMwmWWZ3xo2n5V4Nks5r0W-RgaJpZM4LcZBd>
> .
>


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/128#issuecomment-297996392