Profiles for Initial Server Settings
draft-montenegro-httpbis-http2-server-profiles-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Roberto Peon , Gabriel Montenegro | ||
Last updated | 2014-03-10 (Latest revision 2013-09-06) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
In HTTP/2.0, if running over TLS, the client is the first to transmit HTTP/2.0 frames on the new session. With its first transmission to the server, the client can already overrun some of the server settings and preferences, leading to failure conditions and unnecessary complexity. This document proposes a solution to this problem based on a very small set of server profiles for initial settings sent within the TLS handshake.
Authors
Roberto Peon
Gabriel Montenegro
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)