Re: Alt-Svc across a domain?
Patrick McManus <mcmanus@ducksong.com> Fri, 08 April 2016 18:07 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 6D5CB12D1B9 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 8 Apr 2016 11:07:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.93
X-Spam-Level:
X-Spam-Status: No, score=-6.93 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-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 (1024-bit key) header.d=sendgrid.me
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 hN2gmNiRU-eI for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 8 Apr 2016 11:07:08 -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 0AE8012D0E4 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 8 Apr 2016 11:07:06 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1aoajh-0003sb-PD for ietf-http-wg-dist@listhub.w3.org; Fri, 08 Apr 2016 18:02:25 +0000
Resent-Date: Fri, 08 Apr 2016 18:02:25 +0000
Resent-Message-Id: <E1aoajh-0003sb-PD@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 <bounces+1568871-208f-ietf-http-wg=w3.org@sendgrid.net>) id 1aoajc-0003r7-7D for ietf-http-wg@listhub.w3.org; Fri, 08 Apr 2016 18:02:20 +0000
Received: from o1678912x138.outbound-mail.sendgrid.net ([167.89.12.138]) by lisa.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA256:128) (Exim 4.80) (envelope-from <bounces+1568871-208f-ietf-http-wg=w3.org@sendgrid.net>) id 1aoajZ-0002TM-GJ for ietf-http-wg@w3.org; Fri, 08 Apr 2016 18:02:18 +0000
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.me; h=mime-version:in-reply-to:references:subject:from:to:cc:content-type; s=smtpapi; bh=3aBE91rpCt+eQ6KSeleT/mu6auY=; b=Tm/+1wCJhqZO0mHAg3 yjN9lxJOsP7KPh1KdAbCmhHSBUfnRrneYeE2P64NlXaM0A5akAAAUmq7Z/R1+zVq zB115Cd/7eO4R+h8NHjH/RqgzC55yWr1nFYPT3J72umsYpDY1nQcweCYZiPJvViQ YbNYaxwZRuPiKvdNwzGmNgSgg=
Received: by filter0691p1mdw1.sendgrid.net with SMTP id filter0691p1mdw1.3274.5707F2082D 2016-04-08 18:01:44.529024401 +0000 UTC
Received: from mail-vk0-f50.google.com (mail-vk0-f50.google.com [209.85.213.50]) by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id FF_8DLP8R7K_dcsirsz7mw for <ietf-http-wg@w3.org>; Fri, 08 Apr 2016 18:01:44.623 +0000 (UTC)
Received: by mail-vk0-f50.google.com with SMTP id t129so61012130vkg.2 for <ietf-http-wg@w3.org>; Fri, 08 Apr 2016 11:01:44 -0700 (PDT)
X-Gm-Message-State: AD7BkJINiRpKvZ4ApbBaIVaZfWbeiNluLBcGll6AJ65Wf3KOO5GpK/OjuAvj3sFlEt5WhM1ctz3EXBMf5ff9lw==
MIME-Version: 1.0
X-Received: by 10.31.6.130 with SMTP id 124mr4405949vkg.106.1460138504388; Fri, 08 Apr 2016 11:01:44 -0700 (PDT)
Received: by 10.159.37.3 with HTTP; Fri, 8 Apr 2016 11:01:44 -0700 (PDT)
In-Reply-To: <CAJ_4DfS3qxB+pePU_0sD3XD_7jc8MntRZ9f2mH8eabH30WzyqA@mail.gmail.com>
References: <CAJ_4DfS3qxB+pePU_0sD3XD_7jc8MntRZ9f2mH8eabH30WzyqA@mail.gmail.com>
Date: Fri, 08 Apr 2016 15:01:44 -0300
X-Gmail-Original-Message-ID: <CAOdDvNoLxn4uwL4ZZRJQmjX_0332WQObVdmUti7ifcrUd=jscQ@mail.gmail.com>
Message-ID: <CAOdDvNoLxn4uwL4ZZRJQmjX_0332WQObVdmUti7ifcrUd=jscQ@mail.gmail.com>
From: Patrick McManus <mcmanus@ducksong.com>
To: Ryan Hamilton <rch@google.com>
Cc: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="001a1143d392e0aefb052ffcfca8"
X-SG-EID: YLWet4rakcOTMHWvPPwWbcsiUJbN1FCn0PHYd/Uujh4hLTbrKGf3ivgmKiPiPxBQEFJg5WaIHYnnyP YSikq+N92SmDUIy1Sbbia+sion7LgihmkUYfiW7bdid6EEnvFYLF5Kb/wKZpNfzMMH2U0DzGcOYSjT L6KcXEZu/TPiaaQR75iW52My1hqjcaSBzd3d67/b2wzQ8RcUkC0bTnloY+lTTUhsTlMEm9FvUT72G8 M=
Received-SPF: pass client-ip=167.89.12.138; envelope-from=bounces+1568871-208f-ietf-http-wg=w3.org@sendgrid.net; helo=o1678912x138.outbound-mail.sendgrid.net
X-W3C-Hub-Spam-Status: No, score=-4.5
X-W3C-Hub-Spam-Report: AWL=-1.769, BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001, URIBL_GREY=0.424, W3C_AA=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: lisa.w3.org 1aoajZ-0002TM-GJ 0f79421cf6f332e50eb8072f1ebbc678
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Alt-Svc across a domain?
Archived-At: <http://www.w3.org/mid/CAOdDvNoLxn4uwL4ZZRJQmjX_0332WQObVdmUti7ifcrUd=jscQ@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/31398
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 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 :) -P > 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