A JSON Encoding for HTTP Header Field Values
draft-ietf-httpbis-jfv-02
| Document | Type |
Replaced Internet-Draft
(httpbis WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Julian Reschke | ||
| Last updated | 2016-12-16 (Latest revision 2016-10-24) | ||
| Replaced by | draft-ietf-httpbis-header-structure | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Dead WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-httpbis-header-structure | |
| Consensus boilerplate | Unknown | ||
| 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
This document establishes a convention for use of JSON-encoded field values in HTTP header fields. Editorial Note (To be removed by RFC Editor before publication) Discussion of this draft takes place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived at <https://lists.w3.org/Archives/Public/ietf-http-wg/>. Working Group information can be found at <http://httpwg.github.io/>; source code and issues list for this draft can be found at <https://github.com/httpwg/http-extensions>. The changes in this draft are summarized in Appendix A.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)