%% You should probably cite draft-yasskin-http-origin-signed-responses-09 instead of this revision. @techreport{yasskin-http-origin-signed-responses-00, number = {draft-yasskin-http-origin-signed-responses-00}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-yasskin-http-origin-signed-responses/00/}, author = {Jeffrey Yasskin}, title = {{Origin-signed HTTP Responses}}, pagetotal = 11, year = ** No value found for 'doc.pub_date.year' **, month = ** No value found for 'doc.pub_date' **, day = ** No value found for 'doc.pub_date.day' **, abstract = {This document explores how a server can send particular responses that are authoritative for an origin, when the server itself is not authoritative for that origin. For now, it focuses on the constraints covering any such mechanism. Note to Readers Discussion of this draft takes place on the HTTP working group mailing list (ietf-http-wg@w3.org), which is archived at https://lists.w3.org/Archives/Public/ietf-http-wg/. The source code and issues list for this draft can be found in https://github.com/WICG/webpackage.}, }