Re: ORIGIN - suggested changes

Frederik Deweerdt <fdeweerdt@fastly.com> Wed, 01 February 2017 16:49 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@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 508CD1294D8 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 1 Feb 2017 08:49:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.719
X-Spam-Level:
X-Spam-Status: No, score=-9.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-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=fastly.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 jXsiruRC2ivv for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 1 Feb 2017 08:49:28 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E25012947D for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 1 Feb 2017 08:49:28 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1cYy3q-0006fV-Sq for ietf-http-wg-dist@listhub.w3.org; Wed, 01 Feb 2017 16:47:10 +0000
Resent-Date: Wed, 01 Feb 2017 16:47:10 +0000
Resent-Message-Id: <E1cYy3q-0006fV-Sq@frink.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by frink.w3.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <fdeweerdt@fastly.com>) id 1cYy3m-0006cj-N0 for ietf-http-wg@listhub.w3.org; Wed, 01 Feb 2017 16:47:06 +0000
Received: from mail-yw0-f181.google.com ([209.85.161.181]) by mimas.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <fdeweerdt@fastly.com>) id 1cYy3g-0006GD-Kk for ietf-http-wg@w3.org; Wed, 01 Feb 2017 16:47:01 +0000
Received: by mail-yw0-f181.google.com with SMTP id l19so241422980ywc.2 for <ietf-http-wg@w3.org>; Wed, 01 Feb 2017 08:46:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastly.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=mmS/mMlFORBaOMqd36dXE0TjdUEPkojGH2vy9moDvVk=; b=UsWZCkagdiso3GzzJfoOO/qLQFxcNHNWGXbCnxZbdfZMIB1cv+p2UAJY7/COCmNu0c GgXYGpHk4rr1AASPX5QshNsEhZ86BJpT8D8szvgpLtWelSDJwkSVwquulYRyF0N5pEbb FQiDy8ZEoQfC+viSh1xz5JmI1TLHu/etA1uwE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=mmS/mMlFORBaOMqd36dXE0TjdUEPkojGH2vy9moDvVk=; b=VzyqBjWq869sKMadtQ+i0yvZp5xIeZstdMNPZmUZq3QL0v5SvRT2rGkU0OREYw7HLY /z3m6K3FJpFxFCphWvtWsC/adiPwzpqovm65vtWUkwz7z83blyzA3hYcjHosrA4YGLxF dLdDIP/08mnsLEHQ/sLAQ/SAvuhw3FLGfZrRuupzKxJiUfHGnvIZYPxQbZIRjqvA+i+K YFTdjSroJnshTj2IlHsbXm6lV9U9QQ5ePWR3qPFrVK7tH8kShcePhAb/7UMVjBy1cIFh vxXmILGeppKuGNODzDHWZOmfiyCNYSroHPITemsj5iCZHS5Z9NfTtLMVqc3LaowG87m4 oGjA==
X-Gm-Message-State: AIkVDXIQBabtlneCcQDInq0D2neFhXRBLWP2T/ELr5ReN3+MV7PoCVNmrGmbYMBernjIB4K6sC8dLeu7CuiKHLg/
X-Received: by 10.129.83.215 with SMTP id h206mr2354375ywb.187.1485967593038; Wed, 01 Feb 2017 08:46:33 -0800 (PST)
MIME-Version: 1.0
Received: by 10.129.160.87 with HTTP; Wed, 1 Feb 2017 08:46:32 -0800 (PST)
In-Reply-To: <CABkgnnWaN6Kaq28=a+At_YQcZmG_o0-VRMAWBABzdLz-RBxxPA@mail.gmail.com>
References: <C3CCA267-F5B5-4827-AC27-9853BDADACDE@mnot.net> <CABkgnnWaN6Kaq28=a+At_YQcZmG_o0-VRMAWBABzdLz-RBxxPA@mail.gmail.com>
From: Frederik Deweerdt <fdeweerdt@fastly.com>
Date: Wed, 1 Feb 2017 08:46:32 -0800
Message-ID: <CAM8YLWn6Q7UhwfVoG7LT+-hyf5dBEOpnQds17BiXwq3NXYb0uw@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary=001a114d723488199305477acaa2
Received-SPF: pass client-ip=209.85.161.181; envelope-from=fdeweerdt@fastly.com; helo=mail-yw0-f181.google.com
X-W3C-Hub-Spam-Status: No, score=-3.5
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1cYy3g-0006GD-Kk ba0389db5d839b6a755ddc74ca31c5b5
X-Original-To: ietf-http-wg@w3.org
Subject: Re: ORIGIN - suggested changes
Archived-At: <http://www.w3.org/mid/CAM8YLWn6Q7UhwfVoG7LT+-hyf5dBEOpnQds17BiXwq3NXYb0uw@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/33410
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>

Hello,

On Wed, Feb 1, 2017 at 2:11 AM, Martin Thomson <martin.thomson@gmail.com>
wrote:
[...]
> >   - Redefines the initial Origin Set as whatever SNI included (if
anything).
>
> If you do support this feature, the second change leads to having no
> valid origins initially if you don't use SNI.  It also could be read
> to prohibit coalescing as we do today.  Presumably the set is whatever
> we have today until you see an ORIGIN frame.  You should probably say
> something about that.
>

I'm confused by the "if you don't use SNI part", how can that happen with
RFC 7540, 9.2. stating:
+    The TLS implementation MUST support the Server Name Indication (SNI)
+    [TLS-EXT] extension to TLS.  HTTP/2 clients MUST indicate the target

I've seen HTTP/2 servers reject the connection if the client doesn't send
an SNI.

Frederik