<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.yasskin-http-origin-signed-responses" target="https://datatracker.ietf.org/doc/html/draft-yasskin-http-origin-signed-responses-09">
   <front>
      <title>Signed HTTP Exchanges</title>
      <author initials="J." surname="Yasskin" fullname="Jeffrey Yasskin">
         <organization>Google</organization>
      </author>
      <date month="July" day="27" year="2020" />
      <abstract>
	 <t>   This document specifies how a server can send an HTTP exchange--a
   request URL, content negotiation information, and a response--with
   signatures that vouch for that exchange&#x27;s authenticity.  These
   signatures can be verified against an origin&#x27;s certificate to
   establish that the exchange is authoritative for an origin even if it
   was transferred over a connection that isn&#x27;t.  The signatures can
   also be used in other ways described in the appendices.

   These signatures contain countermeasures against downgrade and
   protocol-confusion attacks.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-yasskin-http-origin-signed-responses-09" />
   
</reference>
