IETF Logo Mail Archive

[#150] Making certain settings mandatory

Martin Thomson <martin.thomson@gmail.com> Thu, 27 June 2013 17:29 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 425B721F9EB2 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 27 Jun 2013 10:29:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AObFgt1ytXK2 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 27 Jun 2013 10:29:44 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 2394F21F9EB3 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 27 Jun 2013 10:29:39 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UsFzS-0003JL-Jp for ietf-http-wg-dist@listhub.w3.org; Thu, 27 Jun 2013 17:28:14 +0000
Resent-Date: Thu, 27 Jun 2013 17:28:14 +0000
Resent-Message-Id: <E1UsFzS-0003JL-Jp@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <martin.thomson@gmail.com>) id 1UsFz7-0003Gh-Au for ietf-http-wg@listhub.w3.org; Thu, 27 Jun 2013 17:27:53 +0000
Received: from mail-we0-f181.google.com ([74.125.82.181]) by maggie.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <martin.thomson@gmail.com>) id 1UsFz6-0000cR-LI for ietf-http-wg@w3.org; Thu, 27 Jun 2013 17:27:53 +0000
Received: by mail-we0-f181.google.com with SMTP id p58so767169wes.26 for <ietf-http-wg@w3.org>; Thu, 27 Jun 2013 10:27:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=gj9gYFSovccSGqlXouIlgMeBcNhurThvLNKieoNpuIo=; b=SJdu5Kbcdbj5KzBM5ng0VAt7YaURzbyXDqmFDagbUdlH0kQgt7JgMR0+cFJf8yp1th fTh9PakYxOfLKwZgH5IbxUAHIH04I9eMoNW8Uxv6xh3N0OXF3tk2CNKhXxQg9ZfnxU0o mfQ2OrasHEyULRfLbyzGpZI41ciuYa+Iqoi1dQ1NG7phV11t8ushCw2IWPej0FYkVeIk a9o984C3NCfaWczYVxJha87yC9QEr/0joIigcMd/ex6/40XTfHpE7pMUl24/0v6W1S/R 7tTvuK9gFiT410unKxrDDZJAlE6hotftXPpXEaGy4OS2m+AS4dx1bHL1vATtZXBk6Y2w dsMQ==
MIME-Version: 1.0
X-Received: by 10.180.36.12 with SMTP id m12mr6754789wij.10.1372354046185; Thu, 27 Jun 2013 10:27:26 -0700 (PDT)
Received: by 10.194.60.46 with HTTP; Thu, 27 Jun 2013 10:27:26 -0700 (PDT)
Date: Thu, 27 Jun 2013 10:27:26 -0700
Message-ID: <CABkgnnW2xi3pAKyg2Abi15Gb11ZCFi+D_QUQw1566BVXb65iHg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"
Received-SPF: pass client-ip=74.125.82.181; envelope-from=martin.thomson@gmail.com; helo=mail-we0-f181.google.com
X-W3C-Hub-Spam-Status: No, score=-3.5
X-W3C-Hub-Spam-Report: AWL=-2.682, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001
X-W3C-Scan-Sig: maggie.w3.org 1UsFz6-0000cR-LI 5d7b320bf367ff194d36d4d45c9e3619
X-Original-To: ietf-http-wg@w3.org
Subject: [#150] Making certain settings mandatory
Archived-At: <http://www.w3.org/mid/CABkgnnW2xi3pAKyg2Abi15Gb11ZCFi+D_QUQw1566BVXb65iHg@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/18395
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>

This pull request proposes to make two settings mandatory in every
SETTINGS frame: SETTINGS_MAX_CONCURRENT_STREAMS and
SETTINGS_INITIAL_WINDOW_SIZE.

https://github.com/http2/http2-spec/pull/150

Gabriel's proposal for an HTTP/1.1 header for carrying settings in the
Upgrade made these mandatory only at that point, which didn't cover
the TLS handshake, or just starting from prior knowledge.

Two questions:
 - Do we want to make any settings mandatory, or are defaults acceptable?
 - Is this the right trade-off? Or are the 16 bytes on subsequent
SETTINGS frames completely intolerable.

Note that if we make these settings mandatory, there might be other
settings in the future that will also be mandatory; e.g., the
compression context size.

v2.23.0 | Report a Bug | By Email