draft-ietf-httpbis-header-structure-12.txt   draft-ietf-httpbis-header-structure-latest.txt 
HTTP Working Group M. Nottingham HTTP Working Group M. Nottingham
Internet-Draft Fastly Internet-Draft Fastly
Intended status: Standards Track P-H. Kamp Intended status: Standards Track P-H. Kamp
Expires: February 20, 2020 The Varnish Cache Project Expires: February 22, 2020 The Varnish Cache Project
August 19, 2019 August 21, 2019
Structured Headers for HTTP Structured Headers for HTTP
draft-ietf-httpbis-header-structure-12 draft-ietf-httpbis-header-structure-latest
Abstract Abstract
This document describes a set of data types and associated algorithms This document describes a set of data types and associated algorithms
that are intended to make it easier and safer to define and handle that are intended to make it easier and safer to define and handle
HTTP header fields. It is intended for use by specifications of new HTTP header fields. It is intended for use by specifications of new
HTTP header fields that wish to use a common syntax that is more HTTP header fields that wish to use a common syntax that is more
restrictive than traditional HTTP field values. restrictive than traditional HTTP field values.
Note to Readers Note to Readers
skipping to change at page 2, line 10 skipping to change at page 2, line 10
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 20, 2020. This Internet-Draft will expire on February 22, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 9 skipping to change at page 3, line 9
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 27 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 27
7.1. Normative References . . . . . . . . . . . . . . . . . . 27 7.1. Normative References . . . . . . . . . . . . . . . . . . 27
7.2. Informative References . . . . . . . . . . . . . . . . . 28 7.2. Informative References . . . . . . . . . . . . . . . . . 28
7.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 28 7.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 29 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 29
Appendix B. Frequently Asked Questions . . . . . . . . . . . . . 29 Appendix B. Frequently Asked Questions . . . . . . . . . . . . . 29
B.1. Why not JSON? . . . . . . . . . . . . . . . . . . . . . . 29 B.1. Why not JSON? . . . . . . . . . . . . . . . . . . . . . . 29
B.2. Structured Headers don't "fit" my data. . . . . . . . . . 30 B.2. Structured Headers don't "fit" my data. . . . . . . . . . 30
Appendix C. Implementation Notes . . . . . . . . . . . . . . . . 30 Appendix C. Implementation Notes . . . . . . . . . . . . . . . . 30
Appendix D. Changes . . . . . . . . . . . . . . . . . . . . . . 31 Appendix D. Changes . . . . . . . . . . . . . . . . . . . . . . 31
D.1. Since draft-ietf-httpbis-header-structure-11 . . . . . . 31 D.1. Since draft-ietf-httpbis-header-structure-12 . . . . . . 31
D.2. Since draft-ietf-httpbis-header-structure-10 . . . . . . 31 D.2. Since draft-ietf-httpbis-header-structure-11 . . . . . . 31
D.3. Since draft-ietf-httpbis-header-structure-09 . . . . . . 31 D.3. Since draft-ietf-httpbis-header-structure-10 . . . . . . 31
D.4. Since draft-ietf-httpbis-header-structure-08 . . . . . . 31 D.4. Since draft-ietf-httpbis-header-structure-09 . . . . . . 31
D.5. Since draft-ietf-httpbis-header-structure-07 . . . . . . 32 D.5. Since draft-ietf-httpbis-header-structure-08 . . . . . . 31
D.6. Since draft-ietf-httpbis-header-structure-06 . . . . . . 32 D.6. Since draft-ietf-httpbis-header-structure-07 . . . . . . 32
D.7. Since draft-ietf-httpbis-header-structure-05 . . . . . . 32 D.7. Since draft-ietf-httpbis-header-structure-06 . . . . . . 32
D.8. Since draft-ietf-httpbis-header-structure-04 . . . . . . 33 D.8. Since draft-ietf-httpbis-header-structure-05 . . . . . . 33
D.9. Since draft-ietf-httpbis-header-structure-03 . . . . . . 33 D.9. Since draft-ietf-httpbis-header-structure-04 . . . . . . 33
D.10. Since draft-ietf-httpbis-header-structure-02 . . . . . . 33 D.10. Since draft-ietf-httpbis-header-structure-03 . . . . . . 33
D.11. Since draft-ietf-httpbis-header-structure-01 . . . . . . 33 D.11. Since draft-ietf-httpbis-header-structure-02 . . . . . . 33
D.12. Since draft-ietf-httpbis-header-structure-00 . . . . . . 33 D.12. Since draft-ietf-httpbis-header-structure-01 . . . . . . 33
D.13. Since draft-ietf-httpbis-header-structure-00 . . . . . . 34
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 34 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 34
1. Introduction 1. Introduction
Specifying the syntax of new HTTP header fields is an onerous task; Specifying the syntax of new HTTP header fields is an onerous task;
even with the guidance in [RFC7231], Section 8.3.1, there are many even with the guidance in [RFC7231], Section 8.3.1, there are many
decisions - and pitfalls - for a prospective HTTP header field decisions - and pitfalls - for a prospective HTTP header field
author. author.
Once a header field is defined, bespoke parsers and serializers often Once a header field is defined, bespoke parsers and serializers often
skipping to change at page 7, line 36 skipping to change at page 7, line 36
header field whose value is defined as a list of lists of strings header field whose value is defined as a list of lists of strings
could look like: could look like:
Example-StrListListHeader: ("foo" "bar"), ("baz"), ("bat" "one"), () Example-StrListListHeader: ("foo" "bar"), ("baz"), ("bat" "one"), ()
Note that the last member in this example is an empty inner list. Note that the last member in this example is an empty inner list.
In textual HTTP headers, members' parameters are separated from the In textual HTTP headers, members' parameters are separated from the
member and each other by semicolons. For example: member and each other by semicolons. For example:
Example-ParamListHeader: abc_123;a=1;b=2; cdef_456, (ghi jkl);q="9";r="w" Example-ParamListHeader: abc;a=1;b=2; cde_456, (ghi jkl);q="9";r=w
In textual HTTP headers, an empty list is denoted by not serialising In textual HTTP headers, an empty list is denoted by not serialising
the header at all. the header at all.
Parsers MUST support lists containing at least 1024 members, support Parsers MUST support lists containing at least 1024 members, support
members with at least 256 parameters, support inner-lists containing members with at least 256 parameters, support inner-lists containing
at least 256 members, and support parameter keys with at least 64 at least 256 members, and support parameter keys with at least 64
characters. characters.
Header specifications can constrain the types of individual list Header specifications can constrain the types of individual list
skipping to change at page 13, line 26 skipping to change at page 13, line 26
2. Append value to output. 2. Append value to output.
3. If inner_list is not empty, append a single WS to output. 3. If inner_list is not empty, append a single WS to output.
3. Append ")" to output. 3. Append ")" to output.
4. Return output. 4. Return output.
4.1.1.2. Serializing Parameters 4.1.1.2. Serializing Parameters
Given an ordered dictionary parameters: Given an ordered dictionary parameters (each with a param-name and an
optional param-value):
1. Let output be an empty string. 1. Let output be an empty string.
2. For each parameter in parameters: 2. For each parameter in parameters:
3. Append ";" to output. 1. Append ";" to output.
4. Let name be the result of applying Serializing a Key 2. Let name be the result of applying Serializing a Key
(Section 4.1.1.3) to parameter's param-name. (Section 4.1.1.3) to parameter's param-name.
5. Append name to output. 3. Append name to output.
6. If parameter has a param-value: 4. If parameter has a param-value:
1. Let value be the result of applying Serializing an Item 1. Let value be the result of applying Serializing an Item
(Section 4.1.3) to parameter's param-value. (Section 4.1.3) to parameter's param-value.
2. Append "=" to output. 2. Append "=" to output.
3. Append value to output. 3. Append value to output.
7. Return output. 3. Return output.
4.1.1.3. Serializing a Key 4.1.1.3. Serializing a Key
Given a key as input_key: Given a key as input_key:
1. If input_key is not a sequence of characters, or contains 1. If input_key is not a sequence of characters, or contains
characters not allowed in the ABNF for key, fail serialisation. characters not allowed in the ABNF for key, fail serialisation.
2. Let output be an empty string. 2. Let output be an empty string.
skipping to change at page 18, line 30 skipping to change at page 18, line 30
2. Discard any leading OWS from input_string. 2. Discard any leading OWS from input_string.
3. If header_type is "list", let output be the result of Parsing a 3. If header_type is "list", let output be the result of Parsing a
List from Text (Section 4.2.1). List from Text (Section 4.2.1).
4. If header_type is "dictionary", let output be the result of 4. If header_type is "dictionary", let output be the result of
Parsing a Dictionary from Text (Section 4.2.2). Parsing a Dictionary from Text (Section 4.2.2).
5. If header_type is "item", let output be the result of Parsing an 5. If header_type is "item", let output be the result of Parsing an
Item from Text (Section 4.2.4). Item from Text (Section 4.2.3).
6. Discard any leading OWS from input_string. 6. Discard any leading OWS from input_string.
7. If input_string is not empty, fail parsing. 7. If input_string is not empty, fail parsing.
8. Otherwise, return output. 8. Otherwise, return output.
When generating input_bytes, parsers MUST combine all instances of When generating input_bytes, parsers MUST combine all instances of
the target header field into one comma-separated field-value, as per the target header field into one comma-separated field-value, as per
[RFC7230], Section 3.2.2; this assures that the header is processed [RFC7230], Section 3.2.2; this assures that the header is processed
skipping to change at page 19, line 45 skipping to change at page 19, line 45
6. Discard any leading OWS from input_string. 6. Discard any leading OWS from input_string.
7. If input_string is empty, there is a trailing comma; fail 7. If input_string is empty, there is a trailing comma; fail
parsing. parsing.
3. No structured data has been found; return members (which is 3. No structured data has been found; return members (which is
empty). empty).
4.2.1.1. Parsing a Parameterized Member from Text 4.2.1.1. Parsing a Parameterized Member from Text
Given an ASCII string input_string, return an token with an ordered Given an ASCII string input_string, return a member (either a list of
map of parameters. input_string is modified to remove the parsed items, or a single item) with an ordered map of parameters.
value. input_string is modified to remove the parsed value.
1. If the first character of input_string is "(", let member be the 1. If the first character of input_string is "(", let member be the
result of running Parsing an Inner List (Section 4.2.1.2) with result of running Parsing an Inner List (Section 4.2.1.2) with
input_string. input_string.
2. Else, let member be the result of running Parsing an Item 2. Else, let member be the result of running Parsing an Item
(Section 4.2.4) with input_string. (Section 4.2.3) with input_string.
3. Let parameters be an empty, ordered map. 3. Let parameters be an empty, ordered map.
4. In a loop: 4. In a loop:
1. Discard any leading OWS from input_string. 1. Discard any leading OWS from input_string.
2. If the first character of input_string is not ";", exit the 2. If the first character of input_string is not ";", exit the
loop. loop.
3. Consume a ";" character from the beginning of input_string. 3. Consume a ";" character from the beginning of input_string.
4. Discard any leading OWS from input_string. 4. Discard any leading OWS from input_string.
5. let param_name be the result of Parsing a key from Text 5. let param_name be the result of Parsing a key from Text
(Section 4.2.3) from input_string. (Section 4.2.1.3) from input_string.
6. If param_name is already present in parameters, there is a 6. If param_name is already present in parameters, there is a
duplicate; fail parsing. duplicate; fail parsing.
7. Let param_value be a null value. 7. Let param_value be a null value.
8. If the first character of input_string is "=": 8. If the first character of input_string is "=":
1. Consume the "=" character at the beginning of 1. Consume the "=" character at the beginning of
input_string. input_string.
2. Let param_value be the result of Parsing an Item from 2. Let param_value be the result of Parsing an Item from
Text (Section 4.2.4) from input_string. Text (Section 4.2.3) from input_string.
9. Append key param_name with value param_value to parameters. 9. Append key param_name with value param_value to parameters.
5. Return the tuple (member, parameters). 5. Return the tuple (member, parameters).
4.2.1.2. Parsing an Inner List 4.2.1.2. Parsing an Inner List
Given an ASCII string input_string, return an array of items. Given an ASCII string input_string, return an array of items.
input_string is modified to remove the parsed value. input_string is modified to remove the parsed value.
skipping to change at page 21, line 14 skipping to change at page 21, line 14
1. Discard any leading OWS from input_string. 1. Discard any leading OWS from input_string.
2. If the first character of input_string is ")": 2. If the first character of input_string is ")":
1. Consume the first character of input_string. 1. Consume the first character of input_string.
2. Return inner_list. 2. Return inner_list.
3. Let item be the result of running Parsing an Item from Text 3. Let item be the result of running Parsing an Item from Text
(Section 4.2.4) with input_string. (Section 4.2.3) with input_string.
4. Append item to inner_list. 4. Append item to inner_list.
5. If the first character of input_string is not SP or ")", fail 5. If the first character of input_string is not SP or ")", fail
parsing. parsing.
4. The end of the inner list was not found; fail parsing. 4. The end of the inner list was not found; fail parsing.
4.2.1.3. Parsing a Key from Text
Given an ASCII string input_string, return a key. input_string is
modified to remove the parsed value.
1. If the first character of input_string is not lcalpha, fail
parsing.
2. Let output_string be an empty string.
3. While input_string is not empty:
1. Let char be the result of removing the first character of
input_string.
2. If char is not one of lcalpha, DIGIT, "*", "_", or "-":
1. Prepend char to input_string.
2. Return output_string.
3. Append char to output_string.
4. Return output_string.
4.2.2. Parsing a Dictionary from Text 4.2.2. Parsing a Dictionary from Text
Given an ASCII string input_string, return an ordered map of (key, Given an ASCII string input_string, return an ordered map of (key,
item). input_string is modified to remove the parsed value. item). input_string is modified to remove the parsed value.
1. Let dictionary be an empty, ordered map. 1. Let dictionary be an empty, ordered map.
2. While input_string is not empty: 2. While input_string is not empty:
1. Let this_key be the result of running Parsing a Key from 1. Let this_key be the result of running Parsing a Key from
Text (Section 4.2.3) with input_string. Text (Section 4.2.1.3) with input_string.
2. If dictionary already contains the name this_key, there is a 2. If dictionary already contains the name this_key, there is a
duplicate; fail parsing. duplicate; fail parsing.
3. Consume the first character of input_string; if it is not 3. Consume the first character of input_string; if it is not
"=", fail parsing. "=", fail parsing.
4. Let member be the result of running Parsing a Parameterized 4. Let member be the result of running Parsing a Parameterized
Member from Text (Section 4.2.1.1) with input_string. Member from Text (Section 4.2.1.1) with input_string.
skipping to change at page 22, line 13 skipping to change at page 22, line 38
COMMA, fail parsing. COMMA, fail parsing.
9. Discard any leading OWS from input_string. 9. Discard any leading OWS from input_string.
10. If input_string is empty, there is a trailing comma; fail 10. If input_string is empty, there is a trailing comma; fail
parsing. parsing.
3. No structured data has been found; return dictionary (which is 3. No structured data has been found; return dictionary (which is
empty). empty).
4.2.3. Parsing a Key from Text 4.2.3. Parsing an Item from Text
Given an ASCII string input_string, return a key. input_string is
modified to remove the parsed value.
1. If the first character of input_string is not lcalpha, fail
parsing.
2. Let output_string be an empty string.
3. While input_string is not empty:
1. Let char be the result of removing the first character of
input_string.
2. If char is not one of lcalpha, DIGIT, "*", "_", or "-":
1. Prepend char to input_string.
2. Return output_string.
3. Append char to output_string.
4. Return output_string.
4.2.4. Parsing an Item from Text
Given an ASCII string input_string, return an item. input_string is Given an ASCII string input_string, return an item. input_string is
modified to remove the parsed value. modified to remove the parsed value.
1. If the first character of input_string is a "-" or a DIGIT, 1. If the first character of input_string is a "-" or a DIGIT,
process input_string as a number (Section 4.2.5) and return the process input_string as a number (Section 4.2.4) and return the
result. result.
2. If the first character of input_string is a DQUOTE, process 2. If the first character of input_string is a DQUOTE, process
input_string as a string (Section 4.2.6) and return the result. input_string as a string (Section 4.2.5) and return the result.
3. If the first character of input_string is "*", process 3. If the first character of input_string is "*", process
input_string as a byte sequence (Section 4.2.8) and return the input_string as a byte sequence (Section 4.2.7) and return the
result. result.
4. If the first character of input_string is "?", process 4. If the first character of input_string is "?", process
input_string as a Boolean (Section 4.2.9) and return the result. input_string as a Boolean (Section 4.2.8) and return the result.
5. If the first character of input_string is an ALPHA, process 5. If the first character of input_string is an ALPHA, process
input_string as a token (Section 4.2.7) and return the result. input_string as a token (Section 4.2.6) and return the result.
6. Otherwise, the item type is unrecognized; fail parsing. 6. Otherwise, the item type is unrecognized; fail parsing.
4.2.5. Parsing a Number from Text 4.2.4. Parsing a Number from Text
Given an ASCII string input_string, return a number. input_string is Given an ASCII string input_string, return a number. input_string is
modified to remove the parsed value. modified to remove the parsed value.
NOTE: This algorithm parses both Integers (Section 3.4) and Floats NOTE: This algorithm parses both Integers (Section 3.4) and Floats
(Section 3.5), and returns the corresponding structure. (Section 3.5), and returns the corresponding structure.
1. Let type be "integer". 1. Let type be "integer".
2. Let sign be 1. 2. Let sign be 1.
skipping to change at page 24, line 25 skipping to change at page 24, line 25
1. If the final character of input_number is ".", fail parsing. 1. If the final character of input_number is ".", fail parsing.
2. If the number of characters after "." in input_number is 2. If the number of characters after "." in input_number is
greater than six, fail parsing. greater than six, fail parsing.
3. Parse input_number as a float and let output_number be the 3. Parse input_number as a float and let output_number be the
product of the result and sign. product of the result and sign.
10. Return output_number. 10. Return output_number.
4.2.6. Parsing a String from Text 4.2.5. Parsing a String from Text
Given an ASCII string input_string, return an unquoted string. Given an ASCII string input_string, return an unquoted string.
input_string is modified to remove the parsed value. input_string is modified to remove the parsed value.
1. Let output_string be an empty string. 1. Let output_string be an empty string.
2. If the first character of input_string is not DQUOTE, fail 2. If the first character of input_string is not DQUOTE, fail
parsing. parsing.
3. Discard the first character of input_string. 3. Discard the first character of input_string.
skipping to change at page 25, line 17 skipping to change at page 25, line 17
3. Else, if char is DQUOTE, return output_string. 3. Else, if char is DQUOTE, return output_string.
4. Else, if char is in the range %x00-1f or %x7f (i.e., is not 4. Else, if char is in the range %x00-1f or %x7f (i.e., is not
in VCHAR or SP), fail parsing. in VCHAR or SP), fail parsing.
5. Else, append char to output_string. 5. Else, append char to output_string.
5. Reached the end of input_string without finding a closing DQUOTE; 5. Reached the end of input_string without finding a closing DQUOTE;
fail parsing. fail parsing.
4.2.7. Parsing a Token from Text 4.2.6. Parsing a Token from Text
Given an ASCII string input_string, return a token. input_string is Given an ASCII string input_string, return a token. input_string is
modified to remove the parsed value. modified to remove the parsed value.
1. If the first character of input_string is not ALPHA, fail 1. If the first character of input_string is not ALPHA, fail
parsing. parsing.
2. Let output_string be an empty string. 2. Let output_string be an empty string.
3. While input_string is not empty: 3. While input_string is not empty:
skipping to change at page 25, line 43 skipping to change at page 25, line 43
"*" or "/": "*" or "/":
1. Prepend char to input_string. 1. Prepend char to input_string.
2. Return output_string. 2. Return output_string.
3. Append char to output_string. 3. Append char to output_string.
4. Return output_string. 4. Return output_string.
4.2.8. Parsing a Byte Sequence from Text 4.2.7. Parsing a Byte Sequence from Text
Given an ASCII string input_string, return a byte sequence. Given an ASCII string input_string, return a byte sequence.
input_string is modified to remove the parsed value. input_string is modified to remove the parsed value.
1. If the first character of input_string is not "*", fail parsing. 1. If the first character of input_string is not "*", fail parsing.
2. Discard the first character of input_string. 2. Discard the first character of input_string.
3. If there is not a "*" character before the end of input_string, 3. If there is not a "*" character before the end of input_string,
fail parsing. fail parsing.
skipping to change at page 26, line 37 skipping to change at page 26, line 37
Because some implementations of base64 do not allow rejection of Because some implementations of base64 do not allow rejection of
encoded data that has non-zero pad bits (see [RFC4648], Section 3.5), encoded data that has non-zero pad bits (see [RFC4648], Section 3.5),
parsers SHOULD NOT fail when it is present, unless they cannot be parsers SHOULD NOT fail when it is present, unless they cannot be
configured to do so. configured to do so.
This specification does not relax the requirements in [RFC4648], This specification does not relax the requirements in [RFC4648],
Section 3.1 and 3.3; therefore, parsers MUST fail on characters Section 3.1 and 3.3; therefore, parsers MUST fail on characters
outside the base64 alphabet, and on line feeds in encoded data. outside the base64 alphabet, and on line feeds in encoded data.
4.2.9. Parsing a Boolean from Text 4.2.8. Parsing a Boolean from Text
Given an ASCII string input_string, return a Boolean. input_string is Given an ASCII string input_string, return a Boolean. input_string is
modified to remove the parsed value. modified to remove the parsed value.
1. If the first character of input_string is not "?", fail parsing. 1. If the first character of input_string is not "?", fail parsing.
2. Discard the first character of input_string. 2. Discard the first character of input_string.
3. If the first character of input_string matches "1", discard the 3. If the first character of input_string matches "1", discard the
first character, and return true. first character, and return true.
skipping to change at page 31, line 9 skipping to change at page 31, line 9
Likewise, implementations should note that it's important to preserve Likewise, implementations should note that it's important to preserve
the distinction between tokens and strings. While most programming the distinction between tokens and strings. While most programming
languages have native types that map to the other types well, it may languages have native types that map to the other types well, it may
be necessary to create a wrapper "token" object or use a parameter on be necessary to create a wrapper "token" object or use a parameter on
functions to assure that these types remain separate. functions to assure that these types remain separate.
Appendix D. Changes Appendix D. Changes
_RFC Editor: Please remove this section before publication._ _RFC Editor: Please remove this section before publication._
D.1. Since draft-ietf-httpbis-header-structure-11 D.1. Since draft-ietf-httpbis-header-structure-12
o Editorial improvements.
D.2. Since draft-ietf-httpbis-header-structure-11
o Allow * in key (#844). o Allow * in key (#844).
o Constrain floats to six digits of precision (#848). o Constrain floats to six digits of precision (#848).
o Allow dictionary members to have parameters (#842). o Allow dictionary members to have parameters (#842).
D.2. Since draft-ietf-httpbis-header-structure-10 D.3. Since draft-ietf-httpbis-header-structure-10
o Update abstract (#799). o Update abstract (#799).
o Input and output are now arrays of bytes (#662). o Input and output are now arrays of bytes (#662).
o Implementations need to preserve difference between token and o Implementations need to preserve difference between token and
string (#790). string (#790).
o Allow empty dictionaries and lists (#781). o Allow empty dictionaries and lists (#781).
o Change parameterized lists to have primary items (#797). o Change parameterized lists to have primary items (#797).
o Allow inner lists in both dictionaries and lists; removes lists of o Allow inner lists in both dictionaries and lists; removes lists of
lists (#816). lists (#816).
o Subsume Parameterised Lists into Lists (#839). o Subsume Parameterised Lists into Lists (#839).
D.3. Since draft-ietf-httpbis-header-structure-09 D.4. Since draft-ietf-httpbis-header-structure-09
o Changed Boolean from T/F to 1/0 (#784). o Changed Boolean from T/F to 1/0 (#784).
o Parameters are now ordered maps (#765). o Parameters are now ordered maps (#765).
o Clamp integers to 15 digits (#737). o Clamp integers to 15 digits (#737).
D.4. Since draft-ietf-httpbis-header-structure-08 D.5. Since draft-ietf-httpbis-header-structure-08
o Disallow whitespace before items properly (#703). o Disallow whitespace before items properly (#703).
o Created "key" for use in dictionaries and parameters, rather than o Created "key" for use in dictionaries and parameters, rather than
relying on identifier (#702). Identifiers have a separate minimum relying on identifier (#702). Identifiers have a separate minimum
supported size. supported size.
o Expanded the range of special characters allowed in identifier to o Expanded the range of special characters allowed in identifier to
include all of ALPHA, ".", ":", and "%" (#702). include all of ALPHA, ".", ":", and "%" (#702).
skipping to change at page 32, line 18 skipping to change at page 32, line 25
o Gave better names for referring specs to use in Parameterised o Gave better names for referring specs to use in Parameterised
Lists (#720). Lists (#720).
o Added Lists of Lists (#721). o Added Lists of Lists (#721).
o Rename Identifier to Token (#725). o Rename Identifier to Token (#725).
o Add implementation guidance (#727). o Add implementation guidance (#727).
D.5. Since draft-ietf-httpbis-header-structure-07 D.6. Since draft-ietf-httpbis-header-structure-07
o Make Dictionaries ordered mappings (#659). o Make Dictionaries ordered mappings (#659).
o Changed "binary content" to "byte sequence" to align with Infra o Changed "binary content" to "byte sequence" to align with Infra
specification (#671). specification (#671).
o Changed "mapping" to "map" for #671. o Changed "mapping" to "map" for #671.
o Don't fail if byte sequences aren't "=" padded (#658). o Don't fail if byte sequences aren't "=" padded (#658).
o Add Booleans (#683). o Add Booleans (#683).
o Allow identifiers in items again (#629). o Allow identifiers in items again (#629).
o Disallowed whitespace before items (#703). o Disallowed whitespace before items (#703).
o Explain the consequences of splitting a string across multiple o Explain the consequences of splitting a string across multiple
headers (#686). headers (#686).
D.6. Since draft-ietf-httpbis-header-structure-06 D.7. Since draft-ietf-httpbis-header-structure-06
o Add a FAQ. o Add a FAQ.
o Allow non-zero pad bits. o Allow non-zero pad bits.
o Explicitly check for integers that violate constraints. o Explicitly check for integers that violate constraints.
D.7. Since draft-ietf-httpbis-header-structure-05 D.8. Since draft-ietf-httpbis-header-structure-05
o Reorganise specification to separate parsing out. o Reorganise specification to separate parsing out.
o Allow referencing specs to use ABNF. o Allow referencing specs to use ABNF.
o Define serialisation algorithms. o Define serialisation algorithms.
o Refine relationship between ABNF, parsing and serialisation o Refine relationship between ABNF, parsing and serialisation
algorithms. algorithms.
D.8. Since draft-ietf-httpbis-header-structure-04 D.9. Since draft-ietf-httpbis-header-structure-04
o Remove identifiers from item. o Remove identifiers from item.
o Remove most limits on sizes. o Remove most limits on sizes.
o Refine number parsing. o Refine number parsing.
D.9. Since draft-ietf-httpbis-header-structure-03 D.10. Since draft-ietf-httpbis-header-structure-03
o Strengthen language around failure handling. o Strengthen language around failure handling.
D.10. Since draft-ietf-httpbis-header-structure-02 D.11. Since draft-ietf-httpbis-header-structure-02
o Split Numbers into Integers and Floats. o Split Numbers into Integers and Floats.
o Define number parsing. o Define number parsing.
o Tighten up binary parsing and give it an explicit end delimiter. o Tighten up binary parsing and give it an explicit end delimiter.
o Clarify that mappings are unordered. o Clarify that mappings are unordered.
o Allow zero-length strings. o Allow zero-length strings.
o Improve string parsing algorithm. o Improve string parsing algorithm.
o Improve limits in algorithms. o Improve limits in algorithms.
o Require parsers to combine header fields before processing. o Require parsers to combine header fields before processing.
o Throw an error on trailing garbage. o Throw an error on trailing garbage.
D.11. Since draft-ietf-httpbis-header-structure-01 D.12. Since draft-ietf-httpbis-header-structure-01
o Replaced with draft-nottingham-structured-headers. o Replaced with draft-nottingham-structured-headers.
D.12. Since draft-ietf-httpbis-header-structure-00 D.13. Since draft-ietf-httpbis-header-structure-00
o Added signed 64bit integer type. o Added signed 64bit integer type.
o Drop UTF8, and settle on BCP137 ::EmbeddedUnicodeChar for h1- o Drop UTF8, and settle on BCP137 ::EmbeddedUnicodeChar for h1-
unicode-string. unicode-string.
o Change h1_blob delimiter to ":" since "'" is valid t_char o Change h1_blob delimiter to ":" since "'" is valid t_char
Authors' Addresses Authors' Addresses
 End of changes. 45 change blocks. 
85 lines changed or deleted 91 lines changed or added

This html diff was produced by rfcdiff 1.44jr. The latest version is available from http://tools.ietf.org/tools/rfcdiff/