IETF Logo Mail Archive

Frame changes landing soon

Martin Thomson <martin.thomson@gmail.com> Tue, 30 October 2018 01:07 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 835831288BD for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 18:07:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 q7Mf1zqz3ePF for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 18:07:57 -0700 (PDT)
Received: from mail-oi1-x22b.google.com (mail-oi1-x22b.google.com [IPv6:2607:f8b0:4864:20::22b]) (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 B16CB127332 for <quic@ietf.org>; Mon, 29 Oct 2018 18:07:57 -0700 (PDT)
Received: by mail-oi1-x22b.google.com with SMTP id f21-v6so5781433oig.1 for <quic@ietf.org>; Mon, 29 Oct 2018 18:07:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=1+RJCGw92Aftm002JD+AXtKxCsT+3v199DDD055Fwec=; b=QPNXJ1c4dn0yFn84NDrAAfIq4AgQRiDAKlzJJR2TZWj5l8GbHMBYZhsZXiCA0qMxZ8 WKMQID/8e6sSi894L1CAQUWeze1FteGl49wzXZSuUn/TX/npbyq4SDDESq52Z3gHcpQ0 REkGA3RyP/89BCL5wYEh9dQoiSzEXCKSpug6lCknxyHjAlSOFB3546UHbOxT27FCpvtY gCvwT63vg9EXYO8qxSebBA7vTt8Pz3n3+M4uV1nSFCBS85DC4m6Mv95wvUjl9cqqjGl8 g331VlFuA8FDOIDATBib+uikoiN70i2ZKbsfZU4VrBinmo0FXySpItI+7ngFbCxjafB8 PXWA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=1+RJCGw92Aftm002JD+AXtKxCsT+3v199DDD055Fwec=; b=SSz58xL2Iy5rfDoXrhLdzM1keSzr/PhsOkqI6sziNy8iD1F5ZIgG0Brr+54oafJ8oM bwZVvv6zIrX+owIiPA7Qr9hfVaV4mST0W5MxBjhTvXBU5o0tosZM33+V1+N+vv+KyLUj 7HHoVWFvYr6YHbLFpJZnhD0SNqxbYpYIPHipUkwr2VvO2MMvlEzFDdk6yg22VGRBxw8S NCYZRvAM7d4rzhP5wh0JFzhM2CT1SyK4oHrNrGAOtt6iRIqH8V5/o8arg15H4m4gFUMj HCvoU6PAlmxw8358fUz7I5kU1Q84o4KPx+g0ArWQl7LHrsx+R1PBHVQQd6SjpCjCR8dX vSgg==
X-Gm-Message-State: AGRZ1gJxgogzQRMd4Y4Ii0LMtGjgLLx9PdZNJ2mXfUHjrD1iOFUNovYP AVi9/MGMs/kHZfCwuansi+sGMhKvrcjmj0p4muA/ADwmSLI=
X-Google-Smtp-Source: AJdET5fZLLsnCBJXxSGdfb2jY3piM6uBJXT+7+1PUJMCv+HVJM+R0OFA2gmKxYPQDb03+NSv+d9stIB6lsOorx9DipQ=
X-Received: by 2002:aca:3554:: with SMTP id c81-v6mr9315955oia.308.1540861675954; Mon, 29 Oct 2018 18:07:55 -0700 (PDT)
MIME-Version: 1.0
From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 30 Oct 2018 12:07:46 +1100
Message-ID: <CABkgnnXwmvCGcukYnQHU4sfAZFR24RT31O+BVqqnkZwB3Cp_Kw@mail.gmail.com>
Subject: Frame changes landing soon
To: QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/2PEv3DUJ4m3hJdRR-NgifjxLdFk>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Oct 2018 01:07:59 -0000

I have some changes outstanding to frames for -17.  I would like to
resolve these so that I can do some cleanup.

https://github.com/quicwg/base-drafts/pull/1906 contains real changes
to the way that stream limits are signaled.

The discussion on https://github.com/quicwg/base-drafts/pull/1900
seems to be coming to a close (no pun intended, but appreciated
nonetheless).  That consolidates the description of APPLICATION_CLOSE
with CONNECTION_CLOSE (no wire format changes).

My current plan is to merge both of these in the next 24 hours.  That
will allow me to renumber frame types so that they start to make more
sense..  If you are interested in what that will look like, see
https://docs.google.com/spreadsheets/d/1G73qp-GBhXGyKEsZBudzWJY85FSa5txT4MxtVC5ajiE/edit?usp=sharing

v2.23.0 | Report a Bug | By Email