W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2021

Distributed Origins and Alt-Svc

From: Mike Bishop <mbishop@evequefou.be>
Date: Thu, 7 Oct 2021 16:17:24 +0000
To: HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <BLAPR22MB225903A281193765CD11D74CDAB19@BLAPR22MB2259.namprd22.prod.outlook.com>
A problem I've been turning over in my head is dealing with "distributed origins," content libraries which are logically a single origin but are too large to actually be managed by a single host.  There are several obvious examples on the Internet at large.  An extension to Alt-Svc seems like a potential avenue to address it, but other properties of Alt-Svc would require other modifications to work smoothly.

This draft explores the problem and looks at one possible solution set.  I'm not totally happy with that solution, because it has too many moving parts, but I still see it as a useful starting point.  I'd be interested to have feedback from folks, and ideas for other ways to address the scenario.

-----Original Message-----
From: internet-drafts@ietf.org <internet-drafts@ietf.org> 
Sent: Monday, October 4, 2021 12:00 PM
To: Mike Bishop <mbishop@evequefou.be>
Subject: New Version Notification for draft-bishop-httpbis-distributed-origin-00.txt


A new version of I-D, draft-bishop-httpbis-distributed-origin-00.txt
has been successfully submitted by Mike Bishop and posted to the IETF repository.

Name:		draft-bishop-httpbis-distributed-origin
Revision:	00
Title:		Distributed HTTP Origins: Solution Space Exploration
Document date:	2021-10-04
Group:		Individual Submission
Pages:		9
URL:            https://www.ietf.org/archive/id/draft-bishop-httpbis-distributed-origin-00.txt

Status:         https://datatracker.ietf.org/doc/draft-bishop-httpbis-distributed-origin/

Html:           https://www.ietf.org/archive/id/draft-bishop-httpbis-distributed-origin-00.html

Htmlized:       https://datatracker.ietf.org/doc/html/draft-bishop-httpbis-distributed-origin



Abstract:
   Certain content libraries are logically a single origin, but too
   large to be practically served by a single origin server.  This
   document discusses existing solutions and explores possible
   directions for future protocol development.

                                                                                  


The IETF Secretariat


Received on Thursday, 7 October 2021 16:17:42 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 7 October 2021 16:17:45 UTC