source: wg_materials/ietf96/ietf-96-jfv.xhtml @ 2760

Last change on this file since 2760 was 2760, checked in by julian.reschke@…, 6 years ago

JFV slides for IETF 96

  • Property svn:executable set to *
  • Property svn:mime-type set to application/xhtml
File size: 2.6 KB
Line 
1<!DOCTYPE html
2  PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3<html xmlns="http://www.w3.org/1999/xhtml">
4  <head>
5    <title>IETF 96 - JSON Field Values</title>
6    <style type="text/css">
7body {
8  color: black;
9  font-family: cambria, helvetica, arial, sans-serif;
10  font-size: 18pt;
11}
12h1 {
13  font-size: 36pt;
14}
15pre {
16  font-family: consolas;
17}
18tt {
19  font-family: consolas;
20}
21li {
22  margin-top: 0.5em;
23}
24q {
25  font-style: italic; 
26}
27.break {
28  page-break-before: always;
29}
30@page {
31  size: a4 landscape;
32}
33@page {
34  @bottom-left {
35       content: "Julian Reschke, greenbytes";
36  }
37  @bottom-right {
38       content: counter(page);
39  }
40  @top-center {
41       content: "IETF 96 - JSON Field Values";
42  }
43}
44    </style>
45  </head>
46  <body>
47    <h1>IETF 96 - JSON Field Values</h1>
48    <p>
49      <a href="mailto:julian.reschke@greenbytes.de">Julian Reschke</a>, greenbytes
50    </p>
51    <h2 class="break">History</h2>
52    <ul>
53      <li>Started as a thought experiment in July 2014 (draft-reschke-http-jfv)</li>
54      <li>Adopted as WG document in June 2016 (draft-ietf-httpbis-jfv))</li>
55      <li>Motivation is captured in IETF 95 slides: <a href="https://svn.tools.ietf.org/svn/wg/httpbis/wg_materials/ietf95/ietf-95-httpbis-header-field-parsing.pdf">ietf-95-httpbis-header-field-parsing</a></li>
56    </ul>
57    <h2 class="break">Discussion</h2>
58    <p>
59      Current document driven by the goal to make it easier to define new header fields, to be used in both HTTP/1.1 and HTTP/2 -- avoiding predictable
60      problems such as I18N or list syntax.
61    </p>
62    <ul>
63      <li>Proposed format can be chatty. Several proposals for minimization.</li>
64      <li>Embrace list format (repeating header fields), as currently proposed, or try to get rid of it?</li>
65      <li>Opt-in per header field definition (current proposal), or applicable more widely? (header field naming convention?)</li>
66      <li>Is JSON the right format anyway? Concerns about data model (number formats) and potential interop issues (non-unique member names).</li>
67      <li>Is this just a step forwards to a common format that can be used in HTTP/1.1 and HTTP/2, or should we also start to discuss
68      headed formats in future versions of HTTP?</li>
69    </ul>
70    <h2 class="break">Links</h2>
71    <ul>
72      <li>Spec: <a href="https://greenbytes.de/tech/webdav/draft-ietf-httpbis-jfv-00.html">draft-ietf-httpbis-jfv-00</a></li>
73      <li>Issues: <a href="https://github.com/httpwg/http-extensions/issues?q=is%3Aissue+is%3Aopen+label%3Ajfv">Github</a></li>
74    </ul>
75  </body>
76</html>
Note: See TracBrowser for help on using the repository browser.