We're expecting to follow roughly the same path that SPDY (eventually HTTP/2) took: iterate on some early versions in Chrome to get experience while the format

We're expecting to follow roughly the same path that SPDY (eventually HTTP/2) took: iterate on some early versions in Chrome to get experience while the format goes through the standardization process, and eventually remove those in favor of the standardized version. You can follow the IETF part of the process at https://tools.ietf.org/html/draft-yasskin-http-origin-signed-responses-01 https://tools.ietf.org/html/draft-yasskin-http-origin-signed....