IETF Logo Mail Archive

Re: [#150] Making certain settings mandatory

Jeff Pinner <jpinner@twitter.com> Sun, 30 June 2013 19: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 B2E0B21F963F for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 30 Jun 2013 12:15:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.976
X-Spam-Level:
X-Spam-Status: No, score=-9.976 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 lOsJlOjqUPaT for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 30 Jun 2013 12:15:21 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 5764121F949F for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sun, 30 Jun 2013 12:15:21 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UtN4T-00077C-VP for ietf-http-wg-dist@listhub.w3.org; Sun, 30 Jun 2013 19:14:01 +0000
Resent-Date: Sun, 30 Jun 2013 19:14:01 +0000
Resent-Message-Id: <E1UtN4T-00077C-VP@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <jpinner@twitter.com>) id 1UtN4E-0006zK-Id for ietf-http-wg@listhub.w3.org; Sun, 30 Jun 2013 19:13:46 +0000
Received: from mail-ob0-f170.google.com ([209.85.214.170]) by maggie.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <jpinner@twitter.com>) id 1UtN4D-0002fT-3X for ietf-http-wg@w3.org; Sun, 30 Jun 2013 19:13:46 +0000
Received: by mail-ob0-f170.google.com with SMTP id ef5so3555879obb.1 for <ietf-http-wg@w3.org>; Sun, 30 Jun 2013 12:13:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=twitter.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=L5fR1VyfAUF6Prsxb71WWl8Vjvzv/bJepqWHqVkuItY=; b=Kld5nvRBedSwkNAQ+6Auk8/pcPW1VY5rGTXQRPYFhYasSNN80l46xhPCe0b8bMoAZW lIbxIFSZ0SCfIW+TAFr+sxX5yVP+C9IwVRz79XlRXUpTeM5JwyBfaoNYhQ+pwT292QDK MoIahUAsvwwpIK6lEOS97a7Rs6YzdvXpgV7zw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=L5fR1VyfAUF6Prsxb71WWl8Vjvzv/bJepqWHqVkuItY=; b=oxZeEkLv6Zlf+EHGD/DTynezwGmrBtkZ7dqtg1oWCmbCRWhAkgkG9i/0OZxpVM0HmV msem6u2C+RIPeFe5A5rBxcFfGQA/fpp+KD8whuNd1GNwtbuxMBhSgXIMUxMtOJFwFY6a PLyW6i3AfKLwNEoy8EgWn5al0u6ICiIZN6nP/RV5Ww9Ey69FnN4qMb6H1w5UmgLgDYPT PI31D3eYn5S0BHmajBNFh0YXv7wiU0nIUncWIpRhD5PtaCk1/QawurXcfHq0j6odKwUb 876m3u5abF50tBHeVXqRnwbfP8OYaI1Zuos52KPC+otoQXwnL+32AhS/KqawCJbmbm8u tO2w==
MIME-Version: 1.0
X-Received: by 10.182.95.71 with SMTP id di7mr9717825obb.12.1372619598840; Sun, 30 Jun 2013 12:13:18 -0700 (PDT)
Received: by 10.182.7.37 with HTTP; Sun, 30 Jun 2013 12:13:18 -0700 (PDT)
In-Reply-To: <51CF47FA.7050508@cisco.com>
References: <CABkgnnW2xi3pAKyg2Abi15Gb11ZCFi+D_QUQw1566BVXb65iHg@mail.gmail.com> <CABaLYCs8vb35CoL+A4mh7-PkbnKXxjz+jCJ_z-ivzYnYKF=VWQ@mail.gmail.com> <CA+pLO_gFrAow2==sZx8_57Hw81d24V4HaqJCEc63WhZSAoWdBA@mail.gmail.com> <CAP+FsNd9dVzRBv1iXS59XQEkk32rK9EtfQs=c1rp+yYHSbG5dQ@mail.gmail.com> <CA+pLO_ijfgbkYEKXn3xUq5-Kxw69k4oQhMc8+fL5tTtenN2x3A@mail.gmail.com> <CAP+FsNfO140h4UgS55P6Ouj2vEc7ZCZzGTBOWRD7+1DigRNUMw@mail.gmail.com> <CA+pLO_hpmFbDNyaPgi3JhtRSdKnTEGsv0_NXxL2BTJfUJ4xStw@mail.gmail.com> <CAP+FsNeq+xUKjVU3uLFGy-2uozErq5fbJ20bD85zNvz=PHJqSQ@mail.gmail.com> <CA+pLO_iEcHBxvXed+=wh5FpTLcu=c5Rr78Wo9WQvnEx6yJ40Jw@mail.gmail.com> <51CF47FA.7050508@cisco.com>
Date: Sun, 30 Jun 2013 12:13:18 -0700
Message-ID: <CA+pLO_jS3N7b8DNbr9h6TH_g7CCJg2gisE2QEgY-3_zWyAab1g@mail.gmail.com>
From: Jeff Pinner <jpinner@twitter.com>
To: Eliot Lear <lear@cisco.com>
Cc: Roberto Peon <grmocg@gmail.com>, Mike Belshe <mike@belshe.com>, Martin Thomson <martin.thomson@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="089e015381bc99d1ba04e063e767"
X-Gm-Message-State: ALoCoQnq5eIioCR21fH8DosxJLFF4W3yVEbwY4XZzACkjH8xt9s7n26B94sW2oyUXG/UrBAHgiI0
Received-SPF: pass client-ip=209.85.214.170; envelope-from=jpinner@twitter.com; helo=mail-ob0-f170.google.com
X-W3C-Hub-Spam-Status: No, score=-4.8
X-W3C-Hub-Spam-Report: AWL=-2.150, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001
X-W3C-Scan-Sig: maggie.w3.org 1UtN4D-0002fT-3X 6a904327cd3592af8583a4e38d470394
X-Original-To: ietf-http-wg@w3.org
Subject: Re: [#150] Making certain settings mandatory
Archived-At: <http://www.w3.org/mid/CA+pLO_jS3N7b8DNbr9h6TH_g7CCJg2gisE2QEgY-3_zWyAab1g@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/18432
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>

Here the initial values CAN be changed by a client sending the header
during the upgrade process.

The question is if sending certain settings should be mandatory.

Are you proposing we remove all default values and require that they all be
explicitly negotiated?


On Sat, Jun 29, 2013 at 1:47 PM, Eliot Lear <lear@cisco.com> wrote:

>
> On 6/29/13 9:47 PM, Jeff Pinner wrote:
>
> So devil's advocate -- why make the mandatory during Upgrade?
>
>  If the client is upgrading to HTTP/2.0 and doesn't send them, why can't
> we just assume that the client has accepted the default values?
>
>
> Because defaults can NEVER be changed.  Sometimes it's better to not ever
> have them.
>

v2.23.0 | Report a Bug | By Email