rfc9110-to-be-220217.xml		rfc9110-to-be-220217-2.xml
	skipping to change at line 12426 ¶		skipping to change at line 12426 ¶
	<title>Hypertext Transfer Protocol Version 3 (HTTP/3)</title>		<title>Hypertext Transfer Protocol Version 3 (HTTP/3)</title>
	<author initials='M' surname='Bishop' fullname='Mike Bishop' role="editor">		<author initials='M' surname='Bishop' fullname='Mike Bishop' role="editor">
	<organization />		<organization />
	</author>		</author>
	<date year='2022' month='February' />		<date year='2022' month='February' />
	</front>		</front>
	<seriesInfo name="RFC" value="9114"/>		<seriesInfo name="RFC" value="9114"/>
	<seriesInfo name="DOI" value="10.17487/RFC9114"/>		<seriesInfo name="DOI" value="10.17487/RFC9114"/>
	</reference>		</reference>
	<!-- [rfced] Section 8.3.1 and Informative References. The current		<referencegroup anchor="BCP13" target="https://www.rfc-editor.org/info/bcp13">
	reference entry in this document for [BCP13] includes only RFC		<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4289.xml"/>
	6838. However, BCP 13 also includes RFC 4289. Should the		<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6838.xml"/>
	reference include both RFCs? Or should [BCP13] be changed to		</referencegroup>
	[RFC6838]?
	Current:
	Media types ought to be registered with IANA according to the
	procedures defined in [BCP13].
	...
	[BCP13] Freed, N., Klensin, J., and T. Hansen, "Media Type
	Specifications and Registration Procedures", BCP 13,
	RFC 6838, January 2013,
	<https://www.rfc-editor.org/info/bcp13>.
	Perhaps:
	[BCP13] Freed, N., Klensin, J., and T. Hansen, "Media Type
	Specifications and Registration Procedures", BCP 13,
	RFC 6838, January 2013.
	Freed, N. and J. Klensin, "Multipurpose Internet Mail
	Extensions (MIME) Part Four: Registration Procedures",
	BCP 13, RFC 4289, December 2005.
	<https://www.rfc-editor.org/info/bcp13>
	Or perhaps:
	Media types ought to be registered with IANA according to the
	procedures defined in [RFC6838].
	-->
	<reference anchor="BCP13" target="https://www.rfc-editor.org/info/bcp13">
	<front>
	<title>Media Type Specifications and Registration Procedures</title>
	<author initials="N." surname="Freed" fullname="Ned Freed"/>
	<author initials="J." surname="Klensin" fullname="John C. Klensin"/>
	<author initials="T." surname="Hansen" fullname="Tony Hansen"/>
	<date year="2013" month="January"/>
	</front>
	<seriesInfo name="BCP" value="13"/>
	<seriesInfo name="RFC" value="6838"/>
	</reference>
	<referencegroup anchor="BCP35" target="https://www.rfc-editor.org/info/bcp35">		<referencegroup anchor="BCP35" target="https://www.rfc-editor.org/info/bcp35">
	<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7595.xml"/>		<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7595.xml"/>
	</referencegroup>		</referencegroup>
	<referencegroup anchor="BCP178" target="https://www.rfc-editor.org/info/bcp178">		<referencegroup anchor="BCP178" target="https://www.rfc-editor.org/info/bcp178">
	<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6648.xml"/>		<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6648.xml"/>
	</referencegroup>		</referencegroup>
	<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3864.xml"/>		<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3864.xml"/>
	skipping to change at line 12848 ¶		skipping to change at line 12808 ¶
	Current:		Current:
	Minimum URI lengths to be supported by implementations are now		Minimum URI lengths to be supported by implementations are now
	recommended (Section 3.1).		recommended (Section 3.1).
	-->		-->
	<t>		<t>
	Minimum URI lengths to be supported by implementations are now recommended.		Minimum URI lengths to be supported by implementations are now recommended.
	(<xref target="resources"/>)		(<xref target="resources"/>)
	</t>		</t>
	<t>		<t>
	The following have been clarified: CR and NUL in field values are to be rejected or		The following have been clarified: CR and NUL in field values are to be rejected or
	mapped to SP, and leading and trailing whitespace need to be		mapped to SP, and leading and trailing whitespace needs to be
	stripped from field values before they are consumed.		stripped from field values before they are consumed.
	(<xref target="fields.values"/>)		(<xref target="fields.values"/>)
	</t>		</t>
	<t>		<t>
	Parameters in media type, media range, and expectation can be empty via		Parameters in media type, media range, and expectation can be empty via
	one or more trailing semicolons.		one or more trailing semicolons.
	(<xref target="parameter"/>)		(<xref target="parameter"/>)
	</t>		</t>
	<t>		<t>
	An abstract data type for HTTP messages has been introduced to define the		An abstract data type for HTTP messages has been introduced to define the
End of changes. 2 change blocks.
	45 lines changed or deleted		5 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/