<?xml version="1.0" encoding="UTF-8"?>
  <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
  <!-- generated by https://github.com/cabo/kramdown-rfc2629 version 1.2.12 --> encoding="utf-8"?>

<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
]>

<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc strict="no"?>
<?rfc compact="no"?>
<?rfc subcompact="no"?> "rfc2629-xhtml.ent">

<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902"
     docName="draft-ietf-core-senml-etch-07" category="std"> category="std" obsoletes=""
     updates="" submissionType="IETF" xml:lang="en" tocInclude="true"
     tocDepth="3" symRefs="true" sortRefs="true" consensus="true" version="3" number="8790">

  <!-- xml2rfc v2v3 conversion 2.41.0 -->
  <front>
    <title abbrev="FETCH &amp; and PATCH with SenML">FETCH &amp; and PATCH with Sensor Measurement Lists (SenML)</title>
    <seriesInfo name="RFC" value="8790"/>
    <author initials="A." surname="Keranen" surname="Keränen" fullname="Ari Keranen"> Keränen">
      <organization>Ericsson</organization>
      <address>
<postal>
<street/>
<city>Jorvas</city><code>02420</code>
<country>Finland</country>
</postal>
        <email>ari.keranen@ericsson.com</email>
      </address>
    </author>
    <author initials="M." surname="Mohajer" fullname="Mojan Mohajer">
      <organization></organization>
      <organization/>
      <address>
        <email>mojanm@hotmail.com</email>
      </address>
    </author>
    <date month="June" year="2020"/>

    <keyword>Internet-Draft</keyword>

<keyword>CoAP</keyword>
<keyword>IoT</keyword>
<keyword>data model</keyword>

    <abstract>
      <t>The Sensor Measurement Lists (SenML) media type and data model can be
      used to send collections of resources, such as batches of sensor data or
      configuration parameters. The CoAP Constrained Application Protocol (CoAP)
      FETCH, PATCH, and iPATCH methods enable accessing and updating parts of
      a resource or multiple resources with one request. This document defines
      new media types for the CoAP FETCH, PATCH, and iPATCH methods for
      resources represented with using the SenML data model.</t>
    </abstract>
  </front>
  <middle>
    <section anchor="intro" title="Introduction"> numbered="true" toc="default">
      <name>Introduction</name>
      <t>The Sensor Measurement Lists (SenML) media type <xref target="RFC8428"/> target="RFC8428" format="default"/> and data
model can be used to transmit collections of resources, such as
batches of sensor data or configuration parameters.</t>
      <t>An example of a SenML collection is shown below:</t>

<figure><artwork><![CDATA[

      <sourcecode name="" type="json"><![CDATA[
[
 {"bn":"2001:db8::2/3311/0/", "n":"5850", "vb":true},
 {"n":"5851", "v":42},
 {"n":"5750", "vs":"Ceiling light"}
]
]]></artwork></figure>

<t>Here
]]></sourcecode>
      <t>Here, three resources “3311/0/5850”, “3311/0/5851”, resources, "3311/0/5850", "3311/0/5851", and “3311/0/5750”, "3311/0/5750",
of an IPSO a dimmable light smart object <xref target="IPSO"/> target="IPSO" format="default"/> are represented using
a single SenML Pack with three SenML Records. All resources share the
same base name “2001:db8::2/3311/0/”, hence "2001:db8::2/3311/0/"; hence, full names for the resources
are “2001:db8::2/3311/0/5850”, "2001:db8::2/3311/0/5850", etc.</t>
      <t>The CoAP <xref target="RFC7252"/> target="RFC7252" format="default"/> FETCH, PATCH, and iPATCH methods <xref target="RFC8132"/> target="RFC8132" format="default"/>
enable accessing and updating parts of a resource or multiple resources
with one request.</t>
      <t>This document defines two new media types, one using the JavaScript
Object Notation (JSON) <xref target="RFC8259"/> target="RFC8259" format="default"/> and one using the Concise Binary
Object Representation (CBOR) <xref target="RFC7049"/>, target="RFC7049" format="default"/>, which can be used with the
CoAP FETCH, PATCH, and iPATCH methods for resources represented with using the
SenML data model (i.e., for both SenML and Sensor Streaming Measurement
Lists (SenSML) data). The rest of the document uses the term “(i)PATCH” "(i)PATCH" when
referring to both methods as the semantics of the new media types are the
same for the CoAP PATCH and iPATCH methods.</t>
    </section>
    <section anchor="terminology" title="Terminology">

<t>The numbered="true" toc="default">
      <name>Terminology</name>
        <t>
    The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”,
“SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “NOT RECOMMENDED”, “MAY”, "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>",
    "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
    NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>",
    "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
    "<bcp14>MAY</bcp14>", and
“OPTIONAL” "<bcp14>OPTIONAL</bcp14>" in this document are
    to be interpreted as described in
BCP 14 BCP&nbsp;14 <xref target="RFC2119"/>
    <xref target="RFC8174"/> when, and only when, they appear in all capitals,
    as shown here.</t> here.
        </t>
      <t>Readers should also be familiar with the terms and concepts discussed
in <xref target="RFC8132"/> target="RFC8132" format="default"/> and <xref target="RFC8428"/>. target="RFC8428" format="default"/>. The following additional terms are used in
this document:</t>

<t><list style="hanging">
  <t hangText='Fetch Record:'>
      <dl newline="false" spacing="normal">
        <dt>Fetch Record:</dt>
        <dd>
  One set of parameters that is used to match SenML Record(s).</t>
  <t hangText='Fetch Pack:'> Record(s).</dd>
        <dt>Fetch Pack:</dt>
        <dd>
  One or more Fetch Records in an array structure.</t>
  <t hangText='Patch Record:'> structure.</dd>
        <dt>Patch Record:</dt>
        <dd>
  One set of parameters similar to Fetch Record but also containing
instructions on how to change existing SenML Pack(s).</t>
  <t hangText='Patch Pack:'> Pack(s).</dd>
        <dt>Patch Pack:</dt>
        <dd>
  One or more Patch Records in an array structure.</t>
  <t hangText='Target Record:'> structure.</dd>
        <dt>Target Record:</dt>
        <dd>
  A Record in a SenML Pack that matches the selection criteria of
a Fetch or Patch Record and hence is a target for a Fetch or Patch
operation.</t>
  <t hangText='Target Pack:'>
operation.</dd>
        <dt>Target Pack:</dt>
        <dd>
  A SenML Pack that is a target for a Fetch or Patch operation.</t>
  <t hangText='(i)PATCH:'> operation.</dd>
        <dt>(i)PATCH:</dt>
        <dd>
  A term that refers to both CoAP “PATCH” "PATCH" and “iPATCH” "iPATCH" methods when
there is no difference in this specification in as to which one is used.</t>
</list></t> used.</dd>
      </dl>
    </section>
    <section anchor="using-fetch-and-ipatch-with-senml" title="Using numbered="true" toc="default">
      <name>Using FETCH and (i)PATCH with SenML"> SenML</name>
      <t>The FETCH/(i)PATCH media types for SenML are modeled as extensions to the
SenML media type to enable re-use reuse of existing SenML parsers and
generators, in particular on constrained devices. Unless mentioned
otherwise, FETCH and PATCH Packs are constructed with the same rules and
constraints as SenML Packs.</t>
      <t>The key differences to from the SenML media type are allowing the use of a
“null”
"null" value for removing records Records with the (i)PATCH method and the lack of
value fields in Fetch Records. Also Also, the Fetch and Patch Records do not
have a default time or base version when the fields are omitted.</t>
      <section anchor="senml-fetch" title="SenML FETCH"> numbered="true" toc="default">
        <name>SenML FETCH</name>
        <t>The FETCH method can be used to select and return a subset of records, Records, in
sequence, of one or more SenML Packs. The SenML Records are selected by
giving a set of names that, when resolved, match resolved names in a
Target SenML Pack. The names for a Fetch Pack are given using the SenML
“name”
"name" and/or “base name” "base name" fields. The names are resolved by concatenating
the base name with the name field as defined in <xref target="RFC8428"/>.</t> target="RFC8428" format="default"/>.</t>
        <t>A Fetch Pack MUST <bcp14>MUST</bcp14> contain at least one Fetch Record. A Fetch Record MUST <bcp14>MUST</bcp14>
contain a name and/or a base name field.</t>
        <t>For example, to select the IPSO resources “5850” "5850" and “5851” "5851" from the
example in <xref target="intro"/>, target="intro" format="default"/>, the following Fetch Pack can be used:</t>

<figure><artwork><![CDATA[
        <sourcecode name="" type="json"><![CDATA[
[
 {"bn":"2001:db8::2/3311/0/", "n":"5850"},
 {"n":"5851"}
]
]]></artwork></figure>
]]></sourcecode>

        <t>The result to of a FETCH request with the example above would be:</t>

<figure><artwork><![CDATA[
        <sourcecode name="" type="json"><![CDATA[
[
 {"bn":"2001:db8::2/3311/0/", "n":"5850", "vb":true},
 {"n":"5851", "v":42},
]
]]></artwork></figure>
]]></sourcecode>
        <t>The SenML time and unit fields can be used in a Fetch Record to further
narrow the selection of matched SenML Records. When no time or unit is
given in a Fetch Record, all SenML Records with the given name are
matched (i.e., unlike with SenML Records, the lack of time field in a Fetch
Record does not imply a time value of zero).

When time is given in the Fetch
Record, a Target Record is matched only the SenML Records (if any) with equal when its resolved time value and name
are matched. equal to those of the Fetch Record. Similarly, when unit is given, a
Target Record is matched only the SenML
Records with equal when its resolved unit and name are matched. equal to
those of the Fetch Record. If both the time and unit are given in the Fetch
Record, a Target Record is matched only when both MUST are equal to match for those of the SenML
Record to match.
Fetch Record. Each Target Record MUST <bcp14>MUST</bcp14> be included in the response at
most once, even if multiple Fetch Records match with the same Target
Record.</t>
        <t>For example, if the IPSO resource “5850” would have "5850" had multiple sensor
	readings (SenML Records) with different time values, the following Fetch
Pack can be used to retrieve the Record with time “1.276020091e+09”:</t>

<figure><artwork><![CDATA[ "1.276020091e+09":</t>
        <sourcecode name="" type="json"><![CDATA[
[
 {"bn":"2001:db8::2/3311/0/", "n":"5850", "t":1.276020091e+09}
]
]]></artwork></figure>
]]></sourcecode>
        <t>The resolved form of records (Section 4.6 of <xref target="RFC8428"/>) Records (<xref target="RFC8428"
	sectionFormat="of" section="4.6"/>) is used when
comparing the names, times, and units of the Target and Fetch Records to
accommodate for differences in the use of the base values. In the resolved form form,
the SenML name in the example above becomes “2001:db8::2/3311/0/5850”. "2001:db8::2/3311/0/5850".
Since there is no base time in the Pack, the time in resolved form is
equal to the time in the example.</t>
        <t>If no SenML Records match, an empty SenML Pack (i.e., array with no
elements) is returned as a response.</t>
        <t>Fetch Records MUST NOT <bcp14>MUST NOT</bcp14> contain other fields than
	name, base name, time,
base time, unit, and base unit. Implementations MUST <bcp14>MUST</bcp14> reject and generate
an error for a Fetch Pack with other fields. <xref target="RFC8132"/> Section 2.2 target="RFC8132"
sectionFormat="comma" section="2.2"/> provides guidance for FETCH request error handling, e.g., using the 4.22
(Unprocessable Entity) CoAP error response code.</t>
      </section>
      <section anchor="senml-ipatch" title="SenML (i)PATCH"> numbered="true" toc="default">
        <name>SenML (i)PATCH</name>
        <t>The (i)PATCH method can be used to change the fields of SenML Records, to
add new Records, and to remove existing Records. The names, times, and
units of the Patch Records are given and matched in the same way as for the
Fetch Records, except each Patch Record MUST <bcp14>MUST</bcp14> match at most one Target
Record. A Patch Record matching more than one Target Record is considered
invalid (patching multiple Target Records with one Patch Record would
result in multiple copies of the same record). Record). Patch Packs can also
include new values and other SenML fields for the Records. Application of
Patch Packs is idempotent; hence hence, the PATCH and iPATCH methods for SenML Packs
are equivalent.</t>
        <t>When the name in a Patch Record matches with the name in an existing
Record, the resolved time values and units (if any) are compared. If the
time values and units either do not exist in both Records or are equal,
the Target Record is replaced with the contents of the Patch Record. All
Patch Records MUST <bcp14>MUST</bcp14> contain at least a SenML Value or Sum field.</t>
        <t>If a Patch Record contains a name, or the combination of a time value, unit,
and a  name, that do does not exist in any existing Record in the Pack, the
given Record, with all the fields it contains, is added to the Pack.</t>
        <t>If a Patch Record has a value (“v”) ("v") field with value null, a null value, it MUST NOT <bcp14>MUST NOT</bcp14> be
added
added, but the matched Record (if any) is removed from the Target Pack.</t>
        <t>The Patch Records MUST <bcp14>MUST</bcp14> be applied in the same
	sequence as they are in the
Patch Pack. If multiple Patch Packs are being processed at the same time,
the result MUST <bcp14>MUST</bcp14> be equivalent to applying them in one sequence.</t>
        <t>Implementations MUST <bcp14>MUST</bcp14> reject and generate an error for Patch Packs with
invalid Records. If a Patch Pack is rejected, the state of the Target
Pack is not changed, i.e., either all or none of the Patch Records are
applied. <xref target="RFC8132"/> Section 3.4 target="RFC8132" sectionFormat="comma" section="3.4"/> provides guidance for error handling
with PATCH and iPATCH requests, e.g., using the 4.22 (Unprocessable
Entity) and 4.09 (Conflict) CoAP error response codes.</t>
        <t>For example, the following document could be given as an (i)PATCH payload
to change/set the values of two SenML Records for the example in
<xref target="intro"/>:</t>

<figure><artwork><![CDATA[ target="intro" format="default"/>:</t>
        <sourcecode name="" type="json"><![CDATA[
[
 {"bn":"2001:db8::2/3311/0/", "n":"5850", "vb":false},
 {"n":"5851", "v":10}
]
]]></artwork></figure>
]]></sourcecode>
        <t>If the request is successful, the resulting representation of the
example SenML Pack would be as follows:</t>

<figure><artwork><![CDATA[
        <sourcecode name="" type="json"><![CDATA[
[
 {"bn":"2001:db8::2/3311/0/", "n":"5850", "vb":false},
 {"n":"5851", "v":10},
 {"n":"5750", "vs":"Ceiling light"}
]
]]></artwork></figure>
]]></sourcecode>
        <t>As another example, the following document could be given as an (i)PATCH
payload to remove the two SenML Records:</t>

<figure><artwork><![CDATA[
        <sourcecode name="" type="json"><![CDATA[
[
 {"bn":"2001:db8::2/3311/0/", "n":"5850", "v":null},
 {"n":"5851", "v":null}
]
]]></artwork></figure>
]]></sourcecode>
      </section>
    </section>
    <section anchor="fragment-identification" title="Fragment Identification"> numbered="true" toc="default">
      <name>Fragment Identification</name>
      <t>Fragment identification for Records of Fetch and Patch Packs uses the
same mechanism as SenML JSON/CBOR fragment identification (see Section 9
of <xref target="RFC8428"/>),
target="RFC8428" sectionFormat="of" section="9"/>), i.e., “rec” the "rec" scheme followed by a comma-separated list of
Record positions or range(s) of Records. For example, to select the 3rd
and 5th Record of a Fetch or Patch Pack, a fragment identifier “rec=3,5” "rec=3,5"
can be used in the URI of the Fetch or Patch Pack resource.</t>
    </section>
    <section anchor="extensibility" title="Extensibility"> numbered="true" toc="default">
      <name>Extensibility</name>
      <t>The SenML mandatory to understand fields mandatory-to-understand field extensibility mechanism (see
section 4.4 in
<xref target="RFC8428"/>) target="RFC8428" sectionFormat="of" section="4.4"/>) does not apply to Patch Packs, i.e., unknown
fields MUST NOT <bcp14>MUST NOT</bcp14> generate an error error, but such fields are treated like any
other field (e.g., added to Patch target records Records where applicable).</t>
      <t>This specification allows only a small subset of SenML fields in Fetch
Records
Records, but future specifications may enable new fields for Fetch Records
and possibly also new fields for selecting targets for Patch Records.</t>
    </section>
    <section anchor="seccons" title="Security Considerations"> numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>The security and privacy considerations of SenML apply also with apply to the
FETCH and (i)PATCH methods. CoAP’s CoAP's security mechanisms are used to
provide security for the FETCH and (i)PATCH methods.</t>
      <t>In FETCH and (i)PATCH requests, the client can pass arbitrary names to
the target resource for manipulation. The resource implementer must take
care to only allow access to names that are actually part of (or
accessible through) the target resource. In particular particular, the receiver needs
to ensure that any input does not lead to uncontrolled special
interpretation by the system.</t>
      <t>If the client is not allowed to do a GET or PUT on the full target
resource (and thus all the names accessible through it), access
control rules must be evaluated for each record Record in the pack.</t> Pack.</t>
    </section>
    <section anchor="iana" title="IANA Considerations"> numbered="true" toc="default">
      <name>IANA Considerations</name>
      <t>This document registers two new media types and CoAP Content-Format IDs
for both media types.</t>

<t>Note to RFC Editor: Please replace all occurrences of “RFC-AAAA” with
the RFC number of this document.</t>
      <section anchor="coap-content-format-registration" title="CoAP numbered="true" toc="default">
        <name>CoAP Content-Format Registration"> Registration</name>
        <t>IANA is requested to assign has assigned CoAP Content-Format IDs for the SenML PATCH
and FETCH media types in the “CoAP Content-Formats” sub-registry, "CoAP Content-Formats" subregistry, within
the “CoRE Parameters” "Constrained RESTful Environments (CoRE) Parameters" registry <xref target="RFC7252"/>. target="RFC7252" format="default"/>. The assigned IDs are shown in
<xref target="tbl-coap-content-formats"/>.</t>

<texttable title="CoAP target="tbl-coap-content-formats" format="default"/>.</t>
        <table anchor="tbl-coap-content-formats" align="center">
          <name>CoAP Content-Format IDs" anchor="tbl-coap-content-formats">
      <ttcol align='left'>Media type</ttcol>
      <ttcol align='left'>Encoding</ttcol>
      <ttcol align='left'>ID</ttcol>
      <c>application/senml-etch+json</c>
      <c>-</c>
      <c>TBD-320</c>
      <c>application/senml-etch+cbor</c>
      <c>-</c>
      <c>TBD-322</c>
</texttable> IDs</name>
          <thead>
            <tr>
              <th align="left">Media Type</th>
              <th align="left">Encoding</th>
              <th align="left">ID</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">application/senml-etch+json</td>
              <td align="left">-</td>
              <td align="left">320</td>
            </tr>
            <tr>
              <td align="left">application/senml-etch+cbor</td>
              <td align="left">-</td>
              <td align="left">322</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section anchor="senml-etchjson-media-type" title="senml-etch+json numbered="true"
	       toc="default">
        <name>senml-etch+json Media Type">

<t>Type name: application</t>

<t>Subtype name: senml-etch+json</t>

<t>Required parameters: N/A</t>

<t>Optional parameters: N/A</t>

<t>Encoding considerations: binary</t>

<t>Security considerations: See <xref target="seccons"/> of RFC-AAAA.</t>

<t>Interoperability considerations: N/A</t>

<t>Published specification: RFC-AAAA</t>

<t>Applications Type</name>
<dl newline="false">
<dt>Type name:</dt><dd>application</dd>
<dt>Subtype name:</dt><dd>senml-etch+json</dd>
<dt>Required parameters:</dt><dd>N/A</dd>
<dt>Optional parameters:</dt><dd>N/A</dd>
<dt>Encoding considerations:</dt><dd>binary</dd>
<dt>Security considerations:</dt><dd>See <xref target="seccons" format="default"/> of RFC 8790.</dd>
<dt>Interoperability considerations:</dt><dd>N/A</dd>
<dt>Published specification:</dt><dd>RFC 8790</dd>
<dt>Applications that use this media type: Applications type:</dt><dd>Applications that use the
SenML media type for resource representation.</t>

<t>Fragment representation.</dd>
<dt>Fragment identifier considerations: Fragment considerations:</dt><dd>Fragment identification for
application/senml-etch+json is supported by using fragment identifiers as
specified by <xref target="fragment-identification"/> of RFC AAAA.</t>

<t>Additional information:</t>

<t>Deprecated 8790.</dd>
<dt>Additional information:</dt>
<dd><t><br/></t>
<dl>
  <dt>Deprecated alias names for this type: N/A</t>

<t>Magic number(s): N/A</t>

<t>File extension(s): senml-etchj</t>

<t>Windows type:</dt><dd>N/A</dd>
  <dt>Magic number(s):</dt><dd>N/A</dd>
  <dt>File extension(s):</dt><dd>senml-etchj</dd>
  <dt>Windows Clipboard Name: “SenML Name:</dt><dd>"SenML FETCH/PATCH format”</t>

<t>Macintosh format"</dd>
  <dt>Macintosh file type code(s): N/A</t>

<t>Macintosh code(s):</dt><dd>N/A</dd>
  <dt>Macintosh Universal Type Identifier code: org.ietf.senml-etch-json code:</dt><dd><t><br/>org.ietf.senml-etch-json
  conforms to public.text</t>

<t>Person public.text</t></dd>
</dl>
</dd>
<dt>Person &amp; email address to contact for further information:
Ari Keranen ari.keranen@ericsson.com</t>

<t>Intended usage: COMMON</t>

<t>Restrictions
information:</dt><dd><t><br/><contact fullname="Ari Keränen"/> &lt;ari.keranen@ericsson.com&gt;</t></dd>
<dt>Intended usage:</dt><dd>COMMON</dd>
<dt>Restrictions on usage: N/A</t>

<t>Author: Ari Keranen ari.keranen@ericsson.com</t>

<t>Change controller: IESG</t> usage:</dt><dd>N/A</dd>
<dt>Author:</dt><dd><t><contact fullname="Ari Keränen"/> &lt;ari.keranen@ericsson.com&gt;</t></dd>
<dt>Change controller:</dt><dd>IESG</dd>
</dl>
      </section>
      <section anchor="senml-etchcbor-media-type" title="senml-etch+cbor numbered="true"
	       toc="default">
        <name>senml-etch+cbor Media Type">

<t>Type name: application</t>

<t>Subtype name: senml-etch+cbor</t>

<t>Required parameters: N/A</t>

<t>Optional parameters: N/A</t>

<t>Encoding considerations: binary</t>

<t>Security considerations: See <xref target="seccons"/> of RFC-AAAA.</t>

<t>Interoperability considerations: N/A</t>

<t>Published specification: RFC-AAAA</t>

<t>Applications Type</name>
<dl newline="false">
<dt>Type name:</dt><dd>application</dd>
<dt>Subtype name:</dt><dd>senml-etch+cbor</dd>
<dt>Required parameters:</dt><dd>N/A</dd>
<dt>Optional parameters:</dt><dd>N/A</dd>
<dt>Encoding considerations:</dt><dd>binary</dd>
<dt>Security considerations:</dt><dd>See <xref target="seccons" format="default"/> of RFC 8790.</dd>
<dt>Interoperability considerations:</dt><dd>N/A</dd>
<dt>Published specification:</dt><dd>RFC 8790</dd>
<dt>Applications that use this media type: Applications type:</dt><dd>Applications that use the
SenML media type for resource representation.</t>

<t>Fragment representation.</dd>
<dt>Fragment identifier considerations: Fragment considerations:</dt><dd>Fragment identification for
application/senml-etch+cbor is supported by using fragment identifiers as
specified by <xref target="fragment-identification"/> of RFC AAAA.</t>

<t>Additional information:</t>

<t>Deprecated 8790.</dd>
<dt>Additional information:</dt>
<dd><t><br/></t>
    <dl newline="false">
      <dt>Deprecated alias names for this type: N/A</t>

<t>Magic number(s): N/A</t>

<t>File extension(s): senml-etchc</t>

<t>Macintosh type:</dt><dd>N/A</dd>
      <dt>Magic number(s):</dt><dd>N/A</dd>
      <dt>File extension(s):</dt><dd>senml-etchc</dd>
      <dt>Macintosh file type code(s): N/A</t>

<t>Macintosh code(s):</dt><dd>N/A</dd>
      <dt>Macintosh Universal Type Identifier code: org.ietf.senml-etch-cbor code:</dt>
      <dd><t><br/>org.ietf.senml-etch-cbor conforms to public.data</t>

<t>Person public.data</t></dd>
    </dl>
 </dd>
<dt>Person &amp; email address to contact for further information:
Ari Keranen ari.keranen@ericsson.com</t>

<t>Intended usage: COMMON</t>

<t>Restrictions information:</dt>
<dd><t><br/><contact fullname="Ari Keränen"/> &lt;ari.keranen@ericsson.com&gt;</t></dd>
<dt>Intended usage:</dt><dd>COMMON</dd>
<dt>Restrictions on usage: N/A</t>

<t>Author: Ari Keranen ari.keranen@ericsson.com</t>

<t>Change controller: IESG</t> usage:</dt><dd>N/A</dd>
<dt>Author:</dt><dd><t><contact fullname="Ari Keränen"/> &lt;ari.keranen@ericsson.com&gt;</t></dd>
<dt>Change controller:</dt><dd>IESG</dd>
</dl>
      </section>
    </section>
  </middle>
  <back>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8428.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.8132.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8259.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7049.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
      </references>
      <references>
        <name>Informative References</name>

        <reference anchor="IPSO" target="http://www.openmobilealliance.org/tech/profiles/lwm2m/3311.xml">
          <front>
            <title>IPSO Light Control Smart Object</title>
            <author>
              <organization>IPSO</organization>
            </author>
            <date year="2019"/>
          </front>
        </reference>
      </references>
    </references>
    <section anchor="acks" title="Acknowledgements"> numbered="false" toc="default">
      <name>Acknowledgements</name>
      <t>The use of the FETCH and (i)PATCH methods with SenML was first
      introduced by the OMA SpecWorks LwM2M Lightweight Machine to Machine (LwM2M)
      v1.1 specification. This document generalizes the use to any SenML
      representation. The authors would like to thank Carsten
Bormann, Christian Amsuess, Jaime Jimenez, Klaus Hartke, Michael
Richardson, <contact
      fullname="Carsten Bormann"/>, <contact fullname="Christian Amsüss"/>,
      <contact fullname="Jaime Jiménez"/>, <contact fullname="Klaus Hartke"/>,
      <contact fullname="Michael Richardson"/>, and other participants from
      the IETF CoRE and OMA SpecWorks DMSE working groups who have contributed
      ideas and reviews.</t>
    </section>

  </middle>

  <back>

    <references title='Normative References'>

<reference  anchor="RFC8428" target='https://www.rfc-editor.org/info/rfc8428'>
<front>
<title>Sensor Measurement Lists (SenML)</title>
<author initials='C.' surname='Jennings' fullname='C. Jennings'><organization /></author>
<author initials='Z.' surname='Shelby' fullname='Z. Shelby'><organization /></author>
<author initials='J.' surname='Arkko' fullname='J. Arkko'><organization /></author>
<author initials='A.' surname='Keranen' fullname='A. Keranen'><organization /></author>
<author initials='C.' surname='Bormann' fullname='C. Bormann'><organization /></author>
<date year='2018' month='August' />
<abstract><t>This specification defines a format for representing simple sensor measurements and device parameters in Sensor Measurement Lists (SenML).  Representations are defined in JavaScript Object Notation (JSON), Concise Binary Object Representation (CBOR), Extensible Markup Language (XML), and Efficient XML Interchange (EXI), which share the common SenML data model.  A simple sensor, such as a temperature sensor, could use one of these media types in protocols such as HTTP or the Constrained Application Protocol (CoAP) to transport the measurements of the sensor or to be configured.</t></abstract>
</front>
<seriesInfo name='RFC' value='8428'/>
<seriesInfo name='DOI' value='10.17487/RFC8428'/>
</reference>

<reference  anchor="RFC7252" target='https://www.rfc-editor.org/info/rfc7252'>
<front>
<title>The Constrained Application Protocol (CoAP)</title>
<author initials='Z.' surname='Shelby' fullname='Z. Shelby'><organization /></author>
<author initials='K.' surname='Hartke' fullname='K. Hartke'><organization /></author>
<author initials='C.' surname='Bormann' fullname='C. Bormann'><organization /></author>
<date year='2014' month='June' />
<abstract><t>The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained (e.g., low-power, lossy) networks.  The nodes often have 8-bit microcontrollers with small amounts of ROM and RAM, while constrained networks such as IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) often have high packet error rates and a typical throughput of 10s of kbit/s.  The protocol is designed for machine- to-machine (M2M) applications such as smart energy and building automation.</t><t>CoAP provides a request/response interaction model between application endpoints, supports built-in discovery of services and resources, and includes key concepts of the Web such as URIs and Internet media types.  CoAP is designed to easily interface with HTTP for integration with the Web while meeting specialized requirements such as multicast support, very low overhead, and simplicity for constrained environments.</t></abstract>
</front>
<seriesInfo name='RFC' value='7252'/>
<seriesInfo name='DOI' value='10.17487/RFC7252'/>
</reference>

<reference  anchor="RFC8132" target='https://www.rfc-editor.org/info/rfc8132'>
<front>
<title>PATCH and FETCH Methods for the Constrained Application Protocol (CoAP)</title>
<author initials='P.' surname='van der Stok' fullname='P. van der Stok'><organization /></author>
<author initials='C.' surname='Bormann' fullname='C. Bormann'><organization /></author>
<author initials='A.' surname='Sehgal' fullname='A. Sehgal'><organization /></author>
<date year='2017' month='April' />
<abstract><t>The methods defined in RFC 7252 for the Constrained Application Protocol (CoAP) only allow access to a complete resource, not to parts of a resource.  In case of resources with larger or complex data, or in situations where resource continuity is required, replacing or requesting the whole resource is undesirable.  Several applications using CoAP need to access parts of the resources.</t><t>This specification defines the new CoAP methods, FETCH, PATCH, and iPATCH, which are used to access and update parts of a resource.</t></abstract>
</front>
<seriesInfo name='RFC' value='8132'/>
<seriesInfo name='DOI' value='10.17487/RFC8132'/>
</reference>

<reference  anchor="RFC8259" target='https://www.rfc-editor.org/info/rfc8259'>
<front>
<title>The JavaScript Object Notation (JSON) Data Interchange Format</title>
<author initials='T.' surname='Bray' fullname='T. Bray' role='editor'><organization /></author>
<date year='2017' month='December' />
<abstract><t>JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format.  It was derived from the ECMAScript Programming Language Standard.  JSON defines a small set of formatting rules for the portable representation of structured data.</t><t>This document removes inconsistencies with other specifications of JSON, repairs specification errors, and offers experience-based interoperability guidance.</t></abstract>
</front>
<seriesInfo name='STD' value='90'/>
<seriesInfo name='RFC' value='8259'/>
<seriesInfo name='DOI' value='10.17487/RFC8259'/>
</reference>

<reference  anchor="RFC7049" target='https://www.rfc-editor.org/info/rfc7049'>
<front>
<title>Concise Binary Object Representation (CBOR)</title>
<author initials='C.' surname='Bormann' fullname='C. Bormann'><organization /></author>
<author initials='P.' surname='Hoffman' fullname='P. Hoffman'><organization /></author>
<date year='2013' month='October' />
<abstract><t>The Concise Binary Object Representation (CBOR) is a data format whose design goals include the possibility of extremely small code size, fairly small message size, and extensibility without the need for version negotiation.  These design goals make it different from earlier binary serializations such as ASN.1 and MessagePack.</t></abstract>
</front>
<seriesInfo name='RFC' value='7049'/>
<seriesInfo name='DOI' value='10.17487/RFC7049'/>
</reference>

<reference  anchor="RFC2119" target='https://www.rfc-editor.org/info/rfc2119'>
<front>
<title>Key words for use in RFCs to Indicate Requirement Levels</title>
<author initials='S.' surname='Bradner' fullname='S. Bradner'><organization /></author>
<date year='1997' month='March' />
<abstract><t>In many standards track documents several words are used to signify the requirements in the specification.  These words are often capitalized. This document defines these words as they should be interpreted in IETF documents.  This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t></abstract>
</front>
<seriesInfo name='BCP' value='14'/>
<seriesInfo name='RFC' value='2119'/>
<seriesInfo name='DOI' value='10.17487/RFC2119'/>
</reference>

<reference  anchor="RFC8174" target='https://www.rfc-editor.org/info/rfc8174'>
<front>
<title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
<author initials='B.' surname='Leiba' fullname='B. Leiba'><organization /></author>
<date year='2017' month='May' />
<abstract><t>RFC 2119 specifies common key words that may be used in protocol  specifications.  This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the  defined special meanings.</t></abstract>
</front>
<seriesInfo name='BCP' value='14'/>
<seriesInfo name='RFC' value='8174'/>
<seriesInfo name='DOI' value='10.17487/RFC8174'/>
</reference>

    </references>

    <references title='Informative References'>

<reference anchor="IPSO" target="http://www.openmobilealliance.org/tech/profiles/lwm2m/3311.xml">
  <front>
    <title>IPSO Light Control Smart Object</title>
    <author >
      <organization>IPSO</organization>
    </author>
    <date year="2018"/>
  </front>
</reference>

    </references>
  </back>

<!-- ##markdown-source:
H4sIAPOiZl4AA+1ba28bOZb9zl/BVYCJjZFkW3EmiRYNjOI40+6J7YztTGOx
WCyoKspiXK8tVlmtzqR/+94HyWKV5STdgwZ2F9sfOq4qPi7v49xzSWoymQjb
qCL9T5WVhZ7Lpm61MFVNf9lmdnj46nAm0jIpVA6f01qtmonRzWqSlLWeWF3k
2UQ3yXpy+ELc6e2mrNO5PCsaXRe6mbzB9iJRzVzaJhWVmQspmzKZy6dbbZ/y
Q5lXKml6r1JdNWt488w9myLVRdTEbvNar2z0oqyb/hsYNoc+0RtTZAbXGPo0
taF5i9J1cHLws22X/VeNaTLo/vb05uR7+Qf5foH/bkyzlte6AAHkuVa2rTVO
K98Z21i5B1/O3+0LtVzW+v6xvufvRKoaGHp2ODsUqm3WZT0XExAYpF9M5V91
rQpdgExshUVtondlfTuXp7AUa0t81rky2Vyq2kzvuNGftfs6hQX5cc+n8rxc
q4+6DuOelx9VEb11I+X4Ov/zumzwmcYoyjpXjbnXaM+rtycvj2cv58IUq/j9
2fvrS/wXLKjqWw1qXDdNNT842Gw207IC1ymXJtMqy4wqEj2FhRw0OlkfVHW5
gg/2INvks/zg2bOjo+lPecZDsRGe4uCg5Nt1I0/KoqnLTF7nqm7k5fKjTpqn
1NirEv+esKKwHz17jR+9FEJMJhOpluAQYG0hbtb6qyaVuU6Nks220hLiB4dT
oKlUZzIBJS61aK1OwXclxEgKzpVlIJYpCyvLlay1Lds60XYMbpaspbJyqSCK
NH21PDcNWdYiKYuVuW1rhd1lpWowFsSXnUoU9KRcvGe/GrNbjUkewy4GLddl
aoUu1DIDSROY05riltq0FUyBDzBmQzOrIBlMLPM2a0wF3YK4glwWkAJe/Ver
bYMyGCsBIFrSUapXEGNWFnoTachKcAzZOGnF16Sl1mFO+KuCBxgd9EnzN2wf
Dhun9SkbMTdpmmmw6BMEobpMW1K6/PTE4OPnX2/cT5+cf3/+HAwtYkNLb2jw
nsLmpvm6scWjxpaPGluIRSH1TypHg5CpSNZoMgmGsOtyg0Jl5WYuxC+//CL+
XchPo2Uxmo8AzI/m6fLlfD6jmDo4PBiN5Qg/PX/5/BD/vl+O5pgCPo+xl/ty
RF9G8+NZ9PqF62Dh4USbDN0ow3AcfRb/QROL73WtwVa1jhxIjtzMfsbuEadB
BYdXNIXApRYUtjI1eU5uTBNJS/FeUryDmbAJ2qjWPY9p0d2FkvhP5vxGvlfJ
nfcllI/fXmlIainE1SLLIpHtWtFCtLBgDAhUqwkw5SMaXWtAM7lqYRBsNnBn
gYPt6uk0Asl0yl5Kkf3p07+A/72YPZ/B2r4aONz65dEzaP37xTyKtyvom005
DPwxdSQbUNj+oO7VdVKbqhEM1PKibNjX9364vrzY90uYPX/lAq4/AIB9YsAA
r02h6q0f5Mob3A118vryyg/14vAYhhrLzdpA8MUx68FEfBOGfgMqCfajKBfs
mamejqnrsvTZngZ3GHQNtEXluLoIjUSHRtcIRzjgPsM9zNmg1VAXwQCwGtC+
rnM52jP7JPUI1gv0ADiRrmtSXskS+NVAysExLCT5ogF64AcdInfP92MYdyTm
oaKmiL43II0pyqy83bI3AzmUyA4BAs4/XN9g7OO/8uKS/r46/duHs6vTN/j3
9feLd+/CH9xCwMPlh3fuO/7V9Ty5PD8/vXjDneGtHLw6X/wbY4sYXb6/Obu8
WLwbAQmClcReTAst0TkM0lewLpoW1JRqCx67hAdTiNcn7+XRsXOt2dEReqmP
uhfH8IBqHzvHzbbuEXS2laqqtKpxEKA84IiVaVQGEaI8bK8BMEF5V1qlgPj4
ss1AgsySVCtwE2BKdZcD0eKWpoKskQBlBlmNTVoLzg1kzKUuAgNqFaUydqYV
5I5yQ9CQpgZDR2V+1NoFCYjb0xOklbdI+B1azsVcXhboR+SWXcICCVWDKcmn
xxxzXg9p9+z+1I+GiOzHQhiC6kLG81g0GMSuqmu1ReoOib0ldb1X3yKNNaA9
UB4IEg8rl23DGgYVNsoUmCyAH9P4nMDBLuUG+yVrVdxqyMEQnKizLpXwQliQ
XQuJRXx8ITfEkqOVLLyQ2CPOXKTa3HEIjmLPAcBTYb0QveUKkh4vFcSIJSBf
4CQF5lGOnVNsD3sIoOlMRTr5/AIXDyT62mgyHs0DFQ9F4EWDEGLZAFeENCMH
aUQPjHvwQEY412DsoABFCTGwgiF4fS7IbaUTszIJpwd4y8kAU4vzUAKtD5Rm
uEjDubyMcaVGYEZNDsLnIdN1KA8SURZgGNE/NQD55FNIFkO2iLgmvHdJG2pr
kAp9eOBu4NIW9YNodqsL1GdZA4gYIosA5C16OTpCiV4MHg2zp/reQM6ayg8F
lFVWYhyDIIASJSpuAwl1HC2bF4V2ZRzgocBPYwJO+aBuM82yhOkaSi2da9hp
h/+dZbwO5AMd4ITKwxK2cHpQYlQApRrJe5W12iXjvLzHZrWLrCBcZBl0ElpV
hn4KUeH6G51xLPZQBrmfZcn4PemjF74pkJyyEWt1r5H5KCBMUJXmFO3EDe/B
Puhm6Jg0kpsLV1ZCfdCwtz1xaye9R27lZR5UFxziJA9kprZGSLDt0iGd0wD6
gbBI00DHY/xQRjAUG0XerAe0l+TjWWDG5VbcGlKu8mjKZBaDdMxrQzKU3et0
7LDdP7uWiFoeNLqpeeaOGHuQIBhBEWBaGLtjfBx2I+xBCHAAnUaBhI+cduNh
uQRwsiy3lB2h2i+I+CJURBw+uAw90Vic81cUOSGLctaEIiwWlwiMSxwSsCsD
CteQymOnAp/q5xzsJkI3ntktTEWikTCYIOG9K/zGkSeg0FQWRcUV1RAMk1RR
yVVd5oQ1vnKkBXEt/HnM3hlIQLSyyPl+dR05KB5DPejoK8VLiXYnb3dFRWcI
L6lalhBhG+JAS/37VLORZOyhFMhUJxVQyLvAjSORLNazJqxl1daIowJKkhq5
Qi8jQ+Rwqk6HZeaPGESQsDx60JzGCo6ABzONERcHMRu0xn3YlWot/Iyu/miL
zNzpKI35AcYeFlkI9v9uZuHWmJa4p1OCdGCaLbdlHP1Z1+W+Wwq9hnwa5A8w
KvwKiBM3D6Bnz2CVv91nCcEjVNZFcDebQMv4NXqtTuU1c7ts63DJ6ZHlGM4p
eqobTEU9d09ytmJC4j1EcNsAWPFyg8GoB6FEIMC+hIqFCV+n8lRBmx4T5P5U
liRZm7IPNhxLFWRdkKYReUnAg6CvSZpVV8n3aTRL0U/jPJ8TZog4ZvUQajzS
cHRSKgzT8YYWVJ4qBVDxe2p+fmdizwSayLp2Jx6JIR6hsiAD1gYWSh2cmnhJ
ONroaDp78adDPLw40n88fDX6LeDRjOaDYYZAxi6DW95RBsblctwfT/+E76P0
sR/KIeKsdLpQ+zRHqWtMC7DjAEGhLHcuge/79mxKoRI87ChxR5vcK6ZZpvAE
KuQ9VjZ4dNFfhejiktzfuVkfj5cwLebYR3ewpuLaIPWOGTlNy+jAY6JN2dr+
bV+fAIIcmY4lxn2dPOCmEJIweB9JyL0hCPKq2cYFigNCrrrIVYpSAEbTGREZ
hlkVc3UVgmvaL3et9JsWIe8ThfapAtgRo/C4S+Rs1LEIWhiTadnI9BIfwR64
rNxvYrmZav3R0z5H9xEFpYZEUz/kT7xVFwk07W0CeNecTWeiqoE7p2DJ29ak
inYsYbR+TuZZYEkp7u+CVqe3mEwCNTuezmZi70MBY+EeI1Uup1BaNIDkVLjx
AAGoEqiGYurraTqH1JC0D2Leld8RoQanHiQzDIY0pT2s8A5VR5CRo/+Gcipk
4ZtdwSd6wdcvADrMx6F9pgVPICzdgH+pcODRdx7Q4E+4TyO1IosNOKHDZqzt
S8cj+8gMRLLXidrjYojek+91ncLmgaUCDmxd07YQhL8BYlCFvh64e91cfsTh
elMS4gtH42DNoXdSVkYHjXF1SF2AHXQ7I0ymcMNFuHRGxmJI4l0z8l62q7Oz
T5ldjVZVmS/moaKLh4fVwkrzqgS+3/yr2+Z4bKcyKtapN+3Ng+8bkAe6g6v+
6Gs4j4hqhwW0HZQRvMPjXS2QnybOG1Hei9A+ECGuuzFBOPKBzrS7jzakMq5L
eVaUgLiHNyYCBa9NZWMRJZTOSWpdAReMS3xEOITHXWFAhySiHxi7yyG/c/V3
4ouo8DYPtc3ZaqhR19+6wmjMh2L50hTe3rjJFBThsJSYoe9B+0hDdYBWh8H/
IBs55u3tRYpAzh1hDh3vsYRj2vBKU3f65wbauag15RRmzHtQfew7pk0z8Gvc
3Bjj8CHBLLXg0XGPEof3UOMGDb5CxkN0S0O9J6PNOrcBs8NWgK4KQ6njlBS3
fgPBbVvXPvVGgUYuGWI/DkBsvtR0wsRZATNq0w3OubDpakEvSRd3VB6CXFuX
Z3Kcvyw6wVDH35gsZS9ZxoKi7gMcBmiJbEcZlXT7kfZEOIBtg6P2WJnwLdHh
OE1BYyYcLjjRi2D+grZjHkkqwtlid85+Nj2Wu3N2P0vzcd0DxHMp3e5O4rKf
xIVP4jjA8fTwldw7KYsVYG7zeGK3D7YqemQ+nLMkrqL3ORShrMv9ldpmpUpF
SPgHuPvkMA81txkyPp8duh0OEXY4fuuuwQoy1O5tg6PDUAYwKAeyhNvMLZ21
rtosgD2GCO1Q9g4o2QXCpkx8KO21QxwClWd/l0X8qpP8BdqIE/M/ZV3hrBvx
MWL3Q5v+phWP5gihO9dLH/xinsi3tbolYc/wVlk4FwD39R9M7wO5WMikqwc7
w4wnfAjrT0pzje5rbN7thuP59gGeTANK755nz9JdBA74V2JQPXpIGQGvGkkL
qSD3JuB9TkWX3tTEajz4wl3czNBpsd9mqEpr3KkWBC9G1x7UPjBNgL8v7DU+
q1PKss8DreBcPDjj4WSqHq4RnAcl/+7Z+PlIDLbUcPwPV2ceGncMGbYe6KDm
lM9SluCtzTbev8tBQjwR2aLwbYHnqHi90WdvHfeLbISKFzYU7seDfd/9bgOM
8hIOHpneG6Yt7opyUwg3WUjkD3MRZnS6CxQdDeBFALbZHbbciqiOk3uM2oFt
8OzurC0cf1DJrZgcA4zv+5sa/eMvOl2xvC2m8BYN5KbuJKHHvP3xSNg0Q8FX
LR5Y9gfFwnvrD6+Q0UfUvVcCkQuBH4IRcHo8bBk0dzunmJ1oeTbK3N5P0Qcg
TtoazXjiqhsnyKcnYEiseNxlL+vb0cw1cIxkGyoiFW5puTM7Mi+JFS517DgP
9DcdKBk+td0cwaWiE3QoSl3i7tr5pPWFsSHBFLu+d5mcODowBoRdhed/Fmdd
mqZWEADuuKYkrhU8xe3f4fwQK6ZqMz6Q9ZdL+LPx7ErjjSDAkEbdaQhaviLB
noNe5C4X4cvudIiP8JIGSg1oV9ElrZXcK2vhriKhjzTrumxv1/tyh3S0NRWd
ZnIqTTRkFKBQWoMX0UkpXpdxMwK5N0XVNl2gQvGRMggkfD8Uj2HJZ1Umwg0P
jogl7w/brW10Pg2Z3enWETvlgBbGTPH44i+nNwRRH27wuJXSIV754rWIoMo9
2n9YtzZUEu6Q6oEugPwDxvN74YR2J6xkA+TISIQIJYj4KTp0i0uZivn+E3m2
uFg8jAyjCvV5eH2r1reQJujQ/eEFLvI9onwnXA1O3tIdX3n2xopwrSnqALNf
QPGNagL8lKepATiey/dYDGpfZDIfTiAY3DYlOMgImk8W8N+IqTlV/DBC0eZL
sDulhkhs3kfaJdkVrad2OZ0UQSyewoYNCJFibovH1tXfo2cuTbjlz2c77Ti1
j3aMZEeIqhPWbr3lcpJu01D7q1PANH89ZSR9M047fN+Pg5JlBblRMjqjpctC
RHObZTZJSlVNXKk+4QvYlo4q/yHPu2P1h//9Q55CaOAePfx59sa9hF6q2105
6C74//GjBTeHppNugJvXbybPZodf6pUsQZe7es2g16e5fPLYEvBiq/1ulMls
xJe+v9ulZFQK8FTyhaGsvPobWD14POqAb7lHggpx3S6b7tNgBLyKBUVpDbrv
bhLN5cXBQojLyl2XevAlaLWfY+ZyyVcWRUhcwwbXGq8b++z1mYiZiwnKBjAJ
3aBx9GXYnWZ/3y6B9K091vn8PA8jAZvvFOAAG08IKLg6157Lx5rtuLcS34wc
lDrTHaxa1w9k/wLzFl/yRyq6qqqs+c6CK2t3cE+8lSKcSrgpYotT7aK7/RZ+
wwA6E+INriUhwFWZASbf3VsgfbGmSPHn6tYkDqyAVbu3b02mu5s/9L5bwkch
fjRFimTsJDPVslQA5BfkiaPobsgB532Wa4QzJZC/SovsEbMHWgAL8G7WrsWH
ApOmhYVRBJzFFkhhnrK+neLPeabRL3nI9fEeeokXAQEtK/SpZNrAOsDBYDhQ
/B/41yHISGvHAGhfLOGrX+5EvK/O6Hcrj/88hfy8SOnmtroFEfEq5+UFxiL/
YMffynOfacEL/qGH/LYZTvgkIfAC6Hh2ev2XIYgQdP1TIIIj/D+I/E8GEbLx
/2oQSX5/QCA33gEI9FOY/9uAIBcJ1vRQO9zyUTGQaCz5XW3pjtYfr+LiKzcb
3NIzNR1H8E+T+J4dEsLL84W8Bsf6sazvrHy3OZ+dy/uj6VE/AIe/tuKNhcz8
7HaeKLZKqoZ4ykEYMZ8k1Vi300i7DXR8oYo7eaJAPF2I12ijohjLk3WNRyZQ
XS5yC/wZqs4fFB6+/AD/K/TPY/nXTEFt8z1Ua3d6LM8N1L86E1f4L1Tqpb8L
T8bnms5UChUZjirOTm/eSiLE2LKnCfHm/PoUfzZwhxF5C2VShdscJV85IXuZ
ZYuRBUGqrLsdeW/0BusQ+kXYEswl/htdm7HZ6DoAAA==

-->

</rfc>