rfc8941v13.xml		rfc8941.xml
	skipping to change at line 27 ¶		skipping to change at line 27 ¶
	<email>mnot@mnot.net</email>		<email>mnot@mnot.net</email>
	<uri>https://www.mnot.net/</uri>		<uri>https://www.mnot.net/</uri>
	</address>		</address>
	</author>		</author>
	<author initials="P-H." surname="Kamp" fullname="Poul-Henning Kamp">		<author initials="P-H." surname="Kamp" fullname="Poul-Henning Kamp">
	<organization>The Varnish Cache Project</organization>		<organization>The Varnish Cache Project</organization>
	<address>		<address>
	<email>phk@varnish-cache.org</email>		<email>phk@varnish-cache.org</email>
	</address>		</address>
	</author>		</author>
	<date month="January" year="2021"/>		<date month="February" year="2021"/>
	<area>Applications and Real-Time</area>		<area>Applications and Real-Time</area>
	<workgroup>HTTP</workgroup>		<workgroup>HTTP</workgroup>
	<abstract>		<abstract>
	<t>This document describes a set of data types and associated algorithms		<t>This document describes a set of data types and associated algorithms
	that are intended to make it easier and safer to define and handle HTTP		that are intended to make it easier and safer to define and handle HTTP
	header and trailer fields, known as "Structured Fields", "Structured		header and trailer fields, known as "Structured Fields", "Structured
	Headers", or "Structured Trailers". It is intended for use by		Headers", or "Structured Trailers". It is intended for use by
	specifications of new HTTP fields that wish to use a common syntax that		specifications of new HTTP fields that wish to use a common syntax that
	is more restrictive than traditional HTTP field values.</t>		is more restrictive than traditional HTTP field values.</t>
	</abstract>		</abstract>
	skipping to change at line 196 ¶		skipping to change at line 196 ¶
	specification are not intended to be used in field definitions.</t>		specification are not intended to be used in field definitions.</t>
	<t>For example, a fictitious Foo-Example header field might be specified		<t>For example, a fictitious Foo-Example header field might be specified
	as:</t>		as:</t>
	<blockquote>		<blockquote>
	<t>42. Foo-Example Header</t>		<t>42. Foo-Example Header</t>
	<t>The Foo-Example HTTP header field conveys information about how		<t>The Foo-Example HTTP header field conveys information about how
	much Foo the message has.</t>		much Foo the message has.</t>
	<t>Foo-Example is an Item Structured Header [RFC8941]. Its value <bcp14>MUST</bc p14> be		<t>Foo-Example is an Item Structured Header [RFC8941]. Its value MUST be
	an Integer (Section 3.3.1 of [RFC8941]). Its ABNF is:</t>		an Integer (Section 3.3.1 of [RFC8941]). Its ABNF is:</t>
	<artwork>		<artwork>
	Foo-Example = sf-integer		Foo-Example = sf-integer
	</artwork>		</artwork>
	<t>Its value indicates the amount of Foo in the message, and it <bcp14>MUST</bcp		<t>Its value indicates the amount of Foo in the message, and it MUST
	14>		be between 0 and 10, inclusive; other values MUST cause
	be between 0 and 10, inclusive; other values <bcp14>MUST</bcp14> cause
	the entire header field to be ignored.</t>		the entire header field to be ignored.</t>
	<t>The following parameter is defined:</t>		<t>The following parameter is defined:</t>
	<ul>		<ul>
	<li>A parameter whose key is "foourl", and whose value is a String		<li>A parameter whose key is "foourl", and whose value is a String
	(Section 3.3.3 of [RFC8941]), conveying the Foo URL		(Section 3.3.3 of [RFC8941]), conveying the Foo URL
	for the message. See below for processing requirements.</li>		for the message. See below for processing requirements.</li>
	</ul>		</ul>
	<t>"foourl" contains a URI-reference (Section 4.1 of [RFC3986]). If		<t>"foourl" contains a URI-reference (Section 4.1 of [RFC3986]). If
	its value is not a valid URI-reference, the entire header field		its value is not a valid URI-reference, the entire header field
	<bcp14>MUST</bcp14> be ignored. If its value is a relative reference (Section 4.		MUST be ignored. If its value is a relative reference (Section 4.2
	2		of [RFC3986]), it MUST be resolved (Section 5 of [RFC3986]) before
	of [RFC3986]), it <bcp14>MUST</bcp14> be resolved (Section 5 of [RFC3986]) befor
	e
	being used.</t>		being used.</t>
	<t>For example:</t>		<t>For example:</t>
	<artwork>		<artwork>
	Foo-Example: 2; foourl="https://foo.example.com/"		Foo-Example: 2; foourl="https://foo.example.com/"
	</artwork>		</artwork>
	</blockquote>		</blockquote>
	</section>		</section>
End of changes. 4 change blocks.
	9 lines changed or deleted		6 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/