DNS Security with HTTP/2 ORIGIN
draft-bishop-httpbis-origin-fed-up-00
This document is an Internet-Draft (I-D).
Anyone may submit an I-D to the IETF.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Mike Bishop , Erik Nygren | ||
| Last updated | 2019-07-22 (Latest revision 2019-01-08) | ||
| 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
The definition of the HTTP/2 ORIGIN frame "relaxes" the requirement to check DNS for various reasons. However, experience has shown that such relaxation leads to security risks and is inadvisable. This document restores the original requirements.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)