Re: Alt-Svc across a domain?
Ryan Hamilton <rch@google.com> Sat, 09 April 2016 13:42 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 2C3FC12D63D for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 9 Apr 2016 06:42:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.03
X-Spam-Level:
X-Spam-Status: No, score=-7.03 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, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 NdorGwCkFUza for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 9 Apr 2016 06:42:21 -0700 (PDT)
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 1BB3D12D56A for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sat, 9 Apr 2016 06:42:20 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1aot4a-0002R8-VD for ietf-http-wg-dist@listhub.w3.org; Sat, 09 Apr 2016 13:37:12 +0000
Resent-Date: Sat, 09 Apr 2016 13:37:12 +0000
Resent-Message-Id: <E1aot4a-0002R8-VD@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <rch@google.com>) id 1aot4W-0002Ll-UB for ietf-http-wg@listhub.w3.org; Sat, 09 Apr 2016 13:37:08 +0000
Received: from mail-wm0-f50.google.com ([74.125.82.50]) by lisa.w3.org with esmtps (TLS1.2:RSA_ARCFOUR_SHA1:128) (Exim 4.80) (envelope-from <rch@google.com>) id 1aot4V-0004TP-6I for ietf-http-wg@w3.org; Sat, 09 Apr 2016 13:37:08 +0000
Received: by mail-wm0-f50.google.com with SMTP id f198so93839979wme.0 for <ietf-http-wg@w3.org>; Sat, 09 Apr 2016 06:36:46 -0700 (PDT)
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; bh=bRDBS0HTs1vf0Xqc0Kf9zZdIqAwpIxR8FHPJXdzV3AM=; b=ZlDm8BKOxjYvdpfvWxX2entv5kFERbjf6B6KMhEu2b4GZUDHvL6b/OEF7KLkojkjra HI6pzv9qcU2CZq4Vv7w3nK9RRumtBaNBZt583xT1rpQekxN1MBY+VFDLQTcvhKZhA+15 tf9i0lrhnqyoIDYCx6By86PEjLivghg8QUSG0U3js6xcZyEwDGHfhWXxsEfCATqOQErQ oGrAdI4Vbp+bfbDs3NpuT9ANLIbwIUtdazI/zu36KIsA5IGpS1nLsVSYMPumkY8IySIP w6A/Ecl2pfYfLi+WvBzCKH1ApqZFOL/Wml3OsDCZtw2hn8gCBYgJJynEMUj+AwNjDkdw U6+Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=bRDBS0HTs1vf0Xqc0Kf9zZdIqAwpIxR8FHPJXdzV3AM=; b=kuJC6Mre9dbQOFQRAZRKmhwHh/qic3ntYBRSVYQPQcUF6MQK47hQRtk0kUcKRRs5uW Xxfc3MSwhwhkYbwLawzHTdoDY8LBlhdUhOL1oWm4EQHd0AmV9ERje1UI4Mg+PBLQhl0d /nvggUe9Mr6t6acGqAV/utELThV2KShUJxtZxx4qHqpM4kZ9EopWUSZgbEPCqcPNWvWw 7mdW5fube7RVU0bfOC5Sk+FerZK8b1RlDHva7DFgtxBZfNQtgkqjile/xVbLALPCVrvG v8QiF5SzBRX2vd4s+1mpX4SmlA7f0F6f+GRVt5W4e9FBsIMp+UmhnTmrbDkJNHQyRmcr ZISg==
X-Gm-Message-State: AD7BkJJBZX/3qWERFFzFSAXyHmZ++V6hfVXwaDWioiEUvFObDYusL8iP5DmmAZcm7cfe9Lig+3nGaU7uR69YRTer
MIME-Version: 1.0
X-Received: by 10.194.178.233 with SMTP id db9mr14736716wjc.11.1460209000093; Sat, 09 Apr 2016 06:36:40 -0700 (PDT)
Received: by 10.28.31.201 with HTTP; Sat, 9 Apr 2016 06:36:39 -0700 (PDT)
In-Reply-To: <CAOdDvNoLxn4uwL4ZZRJQmjX_0332WQObVdmUti7ifcrUd=jscQ@mail.gmail.com>
References: <CAJ_4DfS3qxB+pePU_0sD3XD_7jc8MntRZ9f2mH8eabH30WzyqA@mail.gmail.com> <CAOdDvNoLxn4uwL4ZZRJQmjX_0332WQObVdmUti7ifcrUd=jscQ@mail.gmail.com>
Date: Sat, 09 Apr 2016 06:36:39 -0700
Message-ID: <CAJ_4DfRTQmXkJs=_K4B2=y4b4774B5fdOqMUWwnYP+zWB6fhaw@mail.gmail.com>
From: Ryan Hamilton <rch@google.com>
To: Patrick McManus <mcmanus@ducksong.com>
Cc: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="089e013d1a08bfe0ea05300d6645"
Received-SPF: pass client-ip=74.125.82.50; envelope-from=rch@google.com; helo=mail-wm0-f50.google.com
X-W3C-Hub-Spam-Status: No, score=-5.7
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_LOW=-0.7, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: lisa.w3.org 1aot4V-0004TP-6I c8b68f0e53bace6cad3908604f47323d
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Alt-Svc across a domain?
Archived-At: <http://www.w3.org/mid/CAJ_4DfRTQmXkJs=_K4B2=y4b4774B5fdOqMUWwnYP+zWB6fhaw@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/31401
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>
On Fri, Apr 8, 2016 at 11:01 AM, Patrick McManus <mcmanus@ducksong.com> wrote: > On Fri, Apr 8, 2016 at 2:31 PM, Ryan Hamilton <rch@google.com> wrote: > >> Howdy, >> >> It is common for web sites to serve content from a variety of different >> origins within the same domain. For example, www.example.com, >> accounts.example.com, images.example.com. A single page view may require >> loading resources from several such origins. (Tricks like domain sharing >> can exacerbate this proliferation of origins.) It would be great if the >> service had some way to tell the client, "All of my domains can use this >> alternative service". What would folks thinks of an include-subdomains >> parameter in the Alt-Svc value? If such a parameter were present in an >> Alt-Svc advertisement, a client could use this advertisement to apply to >> any sub-domain of the origin that the client does not already have an >> alternative for. This would avoid the need to discover the alternatives >> individually. >> >> > the server can send, unsolicited, on stream 0 an altsvc frame for each > origin it wants to provide alt-svc info for (the connection needs to be > authoritative for those origins, of course). > > yesterday's discussion of adding certificates to an established connection > would make that more powerful. > > I would encourage h1 servers to update to h2 to get this feature :) > Hm. This seems plausible for the simple case where the number of extra origins is small. But in some cases, the number of extra origins can be ... enormous. In the case of YouTube which I'm quite familiar with, there are literally thousands of hostnames and they all have the same Alt-Svc. We can't practically push an origin frame for each server. And even if we could, I suspect that browsers will limit the number of servers for which they are tracking Alt-Svc information. Cheers, Ryan
- Alt-Svc across a domain? Ryan Hamilton
- Re: Alt-Svc across a domain? Martin Thomson
- Re: Alt-Svc across a domain? Patrick McManus
- Re: Alt-Svc across a domain? Erik Nygren
- Re: Alt-Svc across a domain? Ryan Hamilton