Diff: rfc9193v3.xml - rfc9193.xml

	rfc9193v3.xml	rfc9193.xml

	skipping to change at line 90 ¶	skipping to change at line 90 ¶
	field based on the context, e.g., the name of the data source and out-of-band	field based on the context, e.g., the name of the data source and out-of-band
	knowledge of the application. However, this context may not always be	knowledge of the application. However, this context may not always be
	easily available to entities processing the SenML Pack, especially if	easily available to entities processing the SenML Pack, especially if
	the Pack is propagated over time and via multiple entities. To facilitate	the Pack is propagated over time and via multiple entities. To facilitate
	automatic interpretation, it is useful to be able to indicate an Internet	automatic interpretation, it is useful to be able to indicate an Internet
	media type and, optionally, content codings right in the SenML Record.</t>	media type and, optionally, content codings right in the SenML Record.</t>
	<t>The Constrained Application Protocol (CoAP)	<t>The Constrained Application Protocol (CoAP)
	Content-Format (<xref section="12.3" sectionFormat="of" target="RFC7252" format= "default"/>) provides this	Content-Format (<xref section="12.3" sectionFormat="of" target="RFC7252" format= "default"/>) provides this
	information in the form of a single unsigned integer. For instance, <xref target ="RFC8949" format="default"/> defines the Content-Format number 60 for	information in the form of a single unsigned integer. For instance, <xref target ="RFC8949" format="default"/> defines the Content-Format number 60 for
	Content-Type application/cbor. Enclosing this Content-Format number in the Recor d is illustrated in <xref target="ex-2" format="default"/>. All registered CoAP Content-Format numbers are listed	Content-Type application/cbor. Enclosing this Content-Format number in the Recor d is illustrated in <xref target="ex-2" format="default"/>. All registered CoAP Content-Format numbers are listed

	in the "<xref section="CoAP Content-Formats" relative="#content-formats" section Format="bare" target="IANA.core-parameters" format="default"/>" registry <xref t arget="IANA.core-parameters" format="default"/>, as specified by	in the "CoAP Content-Formats" registry <xref target="IANA.core-parameters" forma t="default"/>, as specified by
	<xref section="12.3" sectionFormat="of" target="RFC7252" format="default"/>.	<xref section="12.3" sectionFormat="of" target="RFC7252" format="default"/>.
	Note that, at the time of writing, the structure of this registry only	Note that, at the time of writing, the structure of this registry only
	provides for zero or one content coding; nothing in the present	provides for zero or one content coding; nothing in the present
	document needs to change if the registry is extended to allow	document needs to change if the registry is extended to allow
	sequences of content codings.</t>	sequences of content codings.</t>
	<figure anchor="ex-2">	<figure anchor="ex-2">
	<name>SenML Record with Binary Data Identified as CBOR</name>	<name>SenML Record with Binary Data Identified as CBOR</name>
	<sourcecode type="json"><![CDATA[	<sourcecode type="json"><![CDATA[
	{"n":"nfc-reader", "vd":"gmNmb28YKg", "ct":"60"}	{"n":"nfc-reader", "vd":"gmNmb28YKg", "ct":"60"}
	]]></sourcecode>	]]></sourcecode>

	skipping to change at line 161 ¶	skipping to change at line 161 ¶
	<dt>Media-Type-Name: </dt>	<dt>Media-Type-Name: </dt>
	<dd>A combination of a type-name and a subtype-name registered in	<dd>A combination of a type-name and a subtype-name registered in
	<xref target="IANA.media-types" format="default"/>, as per <xref target="RFC6838 " format="default"/>, conventionally	<xref target="IANA.media-types" format="default"/>, as per <xref target="RFC6838 " format="default"/>, conventionally
	identified by the two names separated by a slash.</dd>	identified by the two names separated by a slash.</dd>
	<dt>Content-Type: </dt>	<dt>Content-Type: </dt>
	<dd>A Media-Type-Name, optionally associated with parameters	<dd>A Media-Type-Name, optionally associated with parameters
	(<xref section="5" sectionFormat="of" target="RFC2045" format="default"/>, separ ated from	(<xref section="5" sectionFormat="of" target="RFC2045" format="default"/>, separ ated from
	the Media-Type-Name and from each other by a semicolon).	the Media-Type-Name and from each other by a semicolon).
	In HTTP and many other protocols, it is used in a <tt>Content-Type</tt> header f ield.</dd>	In HTTP and many other protocols, it is used in a <tt>Content-Type</tt> header f ield.</dd>
	<dt>Content coding: </dt>	<dt>Content coding: </dt>

	<dd>A name registered in the "<xref section="HTTP Content Coding Registr	<dd>A name registered in the "HTTP Content Coding Registry"
	y" relative="#content-coding" sectionFormat="bare" target="IANA.http-parameters"	<xref target="IANA.http-parameters" format="default"/>, as specified by
	format="default"/>" <xref target="IANA.http-parameters" format="default"/>, as
	specified by
	Sections <xref target="RFC9110" section="16.6.1" sectionFormat="bare" format="de fault"/> and <xref target="RFC9110" section="18.6" sectionFormat="bare" format=" default"/> of <xref target="RFC9110" format="default"/>, indicating an encoding	Sections <xref target="RFC9110" section="16.6.1" sectionFormat="bare" format="de fault"/> and <xref target="RFC9110" section="18.6" sectionFormat="bare" format=" default"/> of <xref target="RFC9110" format="default"/>, indicating an encoding
	transformation with semantics further specified in <xref section="8.4.1" section Format="of" target="RFC9110" format="default"/>.	transformation with semantics further specified in <xref section="8.4.1" section Format="of" target="RFC9110" format="default"/>.
	Confusingly, in HTTP, content coding values are found in a header field	Confusingly, in HTTP, content coding values are found in a header field
	called "Content-Encoding"; however, "content coding" is the correct	called "Content-Encoding"; however, "content coding" is the correct
	term for the process and the registered values.</dd>	term for the process and the registered values.</dd>
	<dt>Content format: </dt>	<dt>Content format: </dt>
	<dd>The combination of a Content-Type and zero or more content codings, identified	<dd>The combination of a Content-Type and zero or more content codings, identified

	by (1) a numeric identifier defined in the "<xref section="CoAP Content-Formats" relative="#content-formats" sectionFormat="bare" target="IANA.core-parameters" format="default"/>" registry <xref target="IANA.core-parameters" format="default "/>,	by (1) a numeric identifier defined in the "CoAP Content-Formats" registry <xref target="IANA.core-parameters" format="default"/>,
	as per <xref section="12.3" sectionFormat="of" target="RFC7252" format="default" /> (referred to as Content-Format	as per <xref section="12.3" sectionFormat="of" target="RFC7252" format="default" /> (referred to as Content-Format
	number), or (2) a Content-Format-String.</dd>	number), or (2) a Content-Format-String.</dd>
	<dt>Content-Format-String:</dt>	<dt>Content-Format-String:</dt>
	<dd>The string representation of the combination of a Content-Type and	<dd>The string representation of the combination of a Content-Type and
	zero or more content codings.</dd>	zero or more content codings.</dd>
	<dt>Content-Format-Spec:</dt>	<dt>Content-Format-Spec:</dt>
	<dd>The string representation of a content format; either a	<dd>The string representation of a content format; either a
	Content-Format-String or the (decimal) string representation of a	Content-Format-String or the (decimal) string representation of a
	Content-Format number.</dd>	Content-Format number.</dd>
	</dl>	</dl>

	skipping to change at line 343 ¶	skipping to change at line 344 ¶
	<t>The indication of a media type in the data does not exempt a consuming	<t>The indication of a media type in the data does not exempt a consuming
	application from properly checking its inputs.	application from properly checking its inputs.
	Also, the ability for an attacker to supply crafted SenML data that	Also, the ability for an attacker to supply crafted SenML data that
	specifies media types chosen by the attacker may expose vulnerabilities	specifies media types chosen by the attacker may expose vulnerabilities
	of handlers for these media types to the attacker.	of handlers for these media types to the attacker.
	This includes "decompression bombs", compressed data that is crafted	This includes "decompression bombs", compressed data that is crafted
	to decompress to extremely large data items.</t>	to decompress to extremely large data items.</t>
	</section>	</section>
	<section anchor="iana" numbered="true" toc="default">	<section anchor="iana" numbered="true" toc="default">
	<name>IANA Considerations</name>	<name>IANA Considerations</name>

	<t>IANA has assigned the following new labels in the	<t>IANA has assigned the following new labels in the "SenML Labels" subreg
	"<xref section="SenML Labels" sectionFormat="bare" target="IANA.senml" relative=	istry
	"#senml-labels" format="default"/>" subregistry
	of the "Sensor Measurement Lists (SenML)" registry <xref target="IANA.senml" for mat="default"/> (as defined in <xref section="12.2" sectionFormat="of" target="R FC8428" format="default"/>) for the	of the "Sensor Measurement Lists (SenML)" registry <xref target="IANA.senml" for mat="default"/> (as defined in <xref section="12.2" sectionFormat="of" target="R FC8428" format="default"/>) for the
	Content-Format indication, as per <xref target="tbl-senml-reg" format="default"/ >:</t>	Content-Format indication, as per <xref target="tbl-senml-reg" format="default"/ >:</t>
	<table anchor="tbl-senml-reg" align="center">	<table anchor="tbl-senml-reg" align="center">
	<name>IANA Registration for New SenML Labels</name>	<name>IANA Registration for New SenML Labels</name>
	<thead>	<thead>
	<tr>	<tr>
	<th align="right">Name</th>	<th align="right">Name</th>
	<th align="left">Label</th>	<th align="left">Label</th>
	<th align="left">JSON Type</th>	<th align="left">JSON Type</th>
	<th align="left">XML Type</th>	<th align="left">XML Type</th>

	skipping to change at line 403 ¶	skipping to change at line 403 ¶
	</author>	</author>
	</front>	</front>
	</reference>	</reference>

	<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7252. xml"/>	<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7252. xml"/>
	<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5234. xml"/>	<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5234. xml"/>

	<reference anchor='RFC9110'>	<reference anchor='RFC9110'>
	<front>	<front>
	<title>HTTP Semantics</title>	<title>HTTP Semantics</title>

	<author initials='R' surname='Fielding' fullname='Roy Fielding'>	<author initials='R' surname='Fielding' fullname='Roy Fielding' role="editor">
	<organization />	<organization />
	</author>	</author>

	<author initials='M' surname='Nottingham' fullname='Mark Nottingham'>	<author initials='M' surname='Nottingham' fullname='Mark Nottingham' role="edito r">
	<organization />	<organization />
	</author>	</author>

	<author initials='J' surname='Reschke' fullname='Julian Reschke'>	<author initials='J' surname='Reschke' fullname='Julian Reschke' role="editor">
	<organization />	<organization />
	</author>	</author>

	<date year='2022' month='February' />	<date year='2022' month='June' />
	</front>	</front>
	<seriesInfo name="RFC" value="9110"/>	<seriesInfo name="RFC" value="9110"/>
	<seriesInfo name="STD" value="97"/>	<seriesInfo name="STD" value="97"/>
	<seriesInfo name="DOI" value="10.17487/RFC9110"/>	<seriesInfo name="DOI" value="10.17487/RFC9110"/>
	</reference>	</reference>

	<reference anchor="IANA.media-types" target="https://www.iana.org/assign ments/media-types">	<reference anchor="IANA.media-types" target="https://www.iana.org/assign ments/media-types">
	<front>	<front>
	<title>Media Types</title>	<title>Media Types</title>
	<author>	<author>

End of changes. 8 change blocks.
	13 lines changed or deleted	10 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/