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

<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<?rfc strict="yes"?>
<?rfc toc="yes"?>
<?rfc tocdepth="3"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc compact="yes"?>
<?rfc comments="yes"?>
<?rfc subcompact="no"?>
<?rfc iprnotified="no"?> [
 <!ENTITY nbsp    "&#160;">
 <!ENTITY zwsp   "&#8203;">
 <!ENTITY nbhy   "&#8209;">
 <!ENTITY wj     "&#8288;">
]>

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

  <!-- xml2rfc v2v3 conversion 2.47.0 -->
  <front>
    <title>CoRE
<title abbrev="CoRE Resource Directory">Constrained RESTful Environments (CoRE) Resource
Directory</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-core-resource-directory-28"/> name="RFC" value="9176"/>
    <author initials="C." surname="Amsüss" fullname="Christian Amsüss" role="editor">
      <organization/>
      <address>
        <postal>
          <street>Hollandstr. 12/4</street>
          <code>1020</code>
          <country>Austria</country>
        </postal>
        <phone>+43-664-9790639</phone>
        <email>christian@amsuess.com</email>
      </address>
    </author>
    <author initials="Z." surname="Shelby" fullname="Zach Shelby">
      <organization>ARM</organization>
      <organization>Edge Impulse</organization>
      <address>
        <postal>
          <street>150 Rose Orchard</street>
          <street>3031 Tisch Way</street>
          <city>San Jose</city>
          <code>95134</code>
          <country>USA</country>
          <code>95128</code>
          <country>United States of America</country>
        </postal>
        <phone>+1-408-203-9434</phone>
        <email>zach.shelby@arm.com</email>
        <email>zach@edgeimpulse.com</email>
      </address>
    </author>
    <author initials="M." surname="Koster" fullname="Michael Koster">
      <organization>SmartThings</organization>
      <organization>PassiveLogic</organization>
      <address>
        <postal>
          <street>665 Clyde Avenue</street>
          <city>Mountain View</city>
          <code>94043</code>
          <country>USA</country>
          <street>524 H Street</street>
          <city>Antioch</city>
	  <region>CA</region>
          <code>94509</code>
          <country>United States of America</country>
        </postal>
        <phone>+1-707-502-5136</phone>
        <email>Michael.Koster@smartthings.com</email>
        <email>michaeljohnkoster@gmail.com</email>
      </address>
    </author>
    <author initials="C." surname="Bormann" fullname="Carsten Bormann">
      <organization>Universitaet
      <organization>Universität Bremen TZI</organization>
      <address>
        <postal>
          <street>Postfach 330440</street>
          <city>Bremen</city>
          <code>D-28359</code>
          <country>Germany</country>
        </postal>
        <phone>+49-421-218-63921</phone>
        <email>cabo@tzi.org</email>
      </address>
    </author>
    <author initials="P." surname="van der Stok" fullname="Peter van der Stok">
      <organization abbrev="consultant">consultant</organization>
      <organization>vanderstok consultancy</organization>
      <address>
        <phone>+31-492474673 (Netherlands), +33-966015248 (France)</phone>
        <email>consultancy@vanderstok.org</email>
        <uri>www.vanderstok.org</uri>
        <email>stokcons@bbhmail.nl</email>
      </address>
    </author>
    <date year="2021" month="March" day="07"/> year="2022" month="April"/>
    <area>Internet</area>
    <workgroup>CoRE</workgroup>
    <keyword>CoRE, Web Linking, Resource Discovery, Resource
    <keyword>CoRE</keyword>
    <keyword>Web Linking</keyword>
    <keyword>Resource Discovery</keyword>
    <keyword>Resource Directory</keyword>
    <abstract>
      <t>In many IoT Internet of Things (IoT) applications, direct discovery of resources is not
      practical due to sleeping nodes, nodes or networks where multicast traffic
is inefficient. These problems can be solved by employing an entity called
a Resource Directory (RD), which contains information about resources held on
other servers, allowing lookups to be performed for those resources. The input to an RD is composed of links links, and the output is composed of links constructed from the information stored in the RD. This
document specifies the web interfaces that an RD supports for web servers to discover the RD and to register, maintain, lookup look up,
and remove information on resources. Furthermore, new target attributes useful
in conjunction with an RD are defined.</t>
    </abstract>
    <note>
      <name>Note to Readers</name>
      <t>Discussion of this document takes place on the
  CORE Working Group mailing list (core@ietf.org),
  which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/core/">https://mailarchive.ietf.org/arch/browse/core/</eref>.</t>
      <t>Source for this draft and an issue tracker can be found at
  <eref target="https://github.com/core-wg/resource-directory">https://github.com/core-wg/resource-directory</eref>.</t>
    </note>
  </front>
  <middle>
    <section anchor="introduction" numbered="true" toc="default">
      <name>Introduction</name>
      <t>In the work on Constrained RESTful Environments (CoRE), a REST Representational State Transfer (REST) architecture
suitable for constrained nodes (e.g. (e.g., with limited RAM and ROM <xref target="RFC7228" format="default"/>)
and networks (e.g. 6LoWPAN (e.g., IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) <xref target="RFC4944" format="default"/>)
has been established and is used in
Internet-of-Things
Internet of Things (IoT) or
machine-to-machine (M2M) applications applications, such as smart energy
and building automation.</t>
      <t>The discovery of resources offered by a constrained server is very important
in machine-to-machine applications where there are no humans in the loop and
static interfaces result in fragility. The discovery of resources provided by
an HTTP Web Server web server is typically called Web Linking web linking <xref target="RFC8288" format="default"/>. The use of
Web Linking
web linking for the description and discovery of resources hosted by
constrained web servers is specified by the CoRE Link Format
<xref target="RFC6690" format="default"/>. However, <xref target="RFC6690" format="default"/> only describes how to discover
resources from the web server that hosts them by querying
<tt>/.well-known/core</tt>. In many constrained scenarios, direct discovery of resources is
not practical due to sleeping nodes, nodes or networks where
multicast traffic is inefficient. These problems can be solved by employing
an entity called a Resource Directory (RD), which contains information about resources held on
other servers, allowing lookups to be performed for those resources.</t>
      <t>This document specifies the web interfaces that an RD supports for web servers to discover the RD and to register, maintain, lookup look up,
and remove information on resources. Furthermore, new target attributes useful in
conjunction with an RD are defined. Although the examples in
this document show the use of these interfaces with CoAP the Constrained Application Protocol (CoAP) <xref target="RFC7252" format="default"/>, they
can be applied in an equivalent manner to HTTP <xref target="RFC7230" format="default"/>.</t>
    </section>
    <section anchor="terminology" 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 <xref target="RFC2119" format="default"/> <xref target="RFC8174" format="default"/>
when, and only when, they appear in all capitals, as shown here.</t>
      <t>The term "byte" is used in its now customary sense as a synonym for "octet".</t>
      <t>This specification requires readers to be familiar with all the terms and
concepts that are discussed in <xref target="RFC3986" format="default"/>, <xref target="RFC8288" format="default"/> format="default"/>, and <xref target="RFC6690" format="default"/>. Readers should
also be familiar with the terms and concepts discussed in <xref target="RFC7252" format="default"/>.  To
describe the REST interfaces defined in this specification, the URI Template
format is used <xref target="RFC6570" format="default"/>.</t>
      <t>This specification makes use of the following additional terminology:</t>
      <dl newline="true">
        <dt>
resolve against  </dt>
        <dd>
          <t>The
	<dt>Resolve Against</dt>
        <dd>The expression "a URI-reference URI reference is <em>resolved against</em> a base URI" is used
	to describe the process of <xref target="RFC3986" format="default"/> Section 5.2. section="5.2" sectionFormat="comma"/>.
	      Noteworthy corner cases are
that include the following: (1) if the URI-reference URI reference is a (full) URI and resolved
      URI, resolving against any base URI, that URI gives the original
      full URI, URI and
that (2) resolving an empty URI reference gives the base
      URI without any fragment identifier.</t>
        </dd>
        <dt>
Resource identifier.</dd>
        <dt>Resource Directory (RD)  </dt> (RD)</dt>
        <dd>
          <t>A web entity that stores information about web resources and
          implements the REST interfaces defined in this specification for
          discovery, for the creation, maintenance maintenance, and removal of
          registrations, and for lookup of the registered resources.</t>
        </dd>
        <dt>
Sector  </dt>
        <dt>Sector</dt>
        <dd>
          <t>In the context of an RD, a sector is a logical grouping of endpoints.
</t> endpoints.</t>
          <t>The abbreviation "d=" is used for the sector in query parameters for
	  compatibility with deployed implementations.</t>
        </dd>
        <dt>
Endpoint  </dt>
        <dt>Endpoint (EP)</dt>
        <dd>
          <t>Endpoint (EP) is a term used to describe a web server or client
          in <xref target="RFC7252" format="default"/>.  In the context of
          this specification specification, an endpoint is used to describe a web server
          that registers resources to the RD. An endpoint is identified by its
          endpoint name, which is included during registration, and has a
          unique name within the associated sector of the registration.</t>
        </dd>
        <dt>
Registration
        <dt>Registration Base URI  </dt> URI</dt>
        <dd>
          <t>The Base base URI of a Registration registration is a URI that typically gives scheme and
	  authority information about an Endpoint. endpoint. The Registration Base registration base URI is provided at
	  registration time, time and is used by the RD to
	  resolve relative references of the registration into URIs.</t>
        </dd>
        <dt>
Target  </dt>
        <dt>Target</dt>
        <dd>
          <t>The target of a link is the destination address (URI) of the link. It is
	  sometimes identified with "href=", "href=" or displayed as <tt>&lt;target&gt;</tt>.
	  Relative targets need resolving with respect to the Base base URI (section 5.2 of <xref (<xref
	  target="RFC3986" format="default"/>).
</t> sectionFormat="of" section="5.2"/>).</t>
          <t>This use of the term Target "target" is consistent with the use in <xref target="RFC8288" format="default"/>'s use of the term.</t>
	  format="default"/>.</t>
        </dd>
        <dt>
Context  </dt>
        <dt>Context</dt>
        <dd>
          <t>The context of a link is the source address (URI) of the link, link
	  and describes which resource is linked to the target.
	  A link's context is made explicit in serialized links as the "anchor=" attribute.
</t> attribute.</t>
          <t>This use of the term Context "context" is consistent with the use in <xref target="RFC8288" format="default"/>'s use of the term.</t>
	  format="default"/>.</t>
        </dd>
        <dt>
Directory Resource  </dt>
        <dt>Directory Resource</dt>
        <dd>
          <t>A directory resource is a resource in the RD containing registration resources.</t>
        </dd>
        <dt>
Registration Resource  </dt>
        <dt>Registration Resource</dt>
        <dd>
          <t>A registration resource is a resource in the RD that contains information about an Endpoint
	  endpoint and its links.</t>
        </dd>
        <dt>
Commissioning
        <dt>Commissioning Tool  </dt> (CT)</dt>
        <dd>
          <t>Commissioning
          <t>A Commissioning Tool (CT) is a device that assists during installation events
	  by assigning values to parameters, naming endpoints and groups, or adapting
	  the installation to the needs of the applications.</t>
        </dd>
        <dt>
Registrant-ep  </dt>
        <dt>Registrant-EP</dt>
        <dd>
          <t>Registrant-ep
          <t>A registrant-EP is the endpoint that is registered into the RD. The registrant-ep registrant-EP can
	  register itself, or a CT registers the registrant-ep.</t> registrant-EP.</t>
        </dd>
        <dt>
RDAO  </dt>
        <dt>Resource Directory Address Option (RDAO)</dt>
        <dd>
          <t>Resource
          <t>A Resource Directory Address Option.
A Option (RDAO) is a new IPv6 Neighbor Discovery option defined
	  for announcing an RD's address.</t>
        </dd>
      </dl>
    </section>
    <section anchor="arch" numbered="true" toc="default">
      <name>Architecture and Use Cases</name>
      <section anchor="principles" numbered="true" toc="default">
        <name>Principles</name>
        <t>The RD is primarily a tool to make discovery operations more
efficient than querying /.well-known/core <tt>/.well-known/core</tt> on all connected devices, devices or across
boundaries that would limit those operations.</t>
        <t>It provides information about resources hosted by other devices that could otherwise only be obtained by
directly querying the /.well-known/core <tt>/.well-known/core</tt> resource on these other devices, either by a unicast request or a multicast request.</t>
        <t>Information SHOULD <bcp14>SHOULD</bcp14> only be stored in the RD
if it can be obtained by querying the described device's
/.well-known/core
<tt>/.well-known/core</tt> resource directly.</t>
        <t>Data in the RD can only be provided by the
device which that hosts those the data or a dedicated Commissioning Tool (CT).
These CTs act on behalf of endpoints too constrained, or generally
unable, to present that information themselves. No other client can modify data
in the RD. Changes to the information in the RD do not propagate automatically back to the web servers from where the information originated.</t>
      </section>
      <section anchor="architecture" numbered="true" toc="default">
        <name>Architecture</name>
        <t>The RD architecture is illustrated in <xref target="fig-arch" format="default"/>. An
RD is used as a repository of registrations
describing resources hosted on other web servers, also called endpoints
(EP).
(EPs).
An endpoint is a web server associated with a scheme, IP address address, and port. A physical node may host one or more endpoints. The
RD implements a set of REST interfaces for endpoints to register and maintain
RD registrations, registrations and for endpoints to
lookup
look up resources from the RD. An RD can be logically segmented by the use of Sectors.</t> sectors.</t>
        <t>A mechanism to discover an RD using CoRE Link Format <xref target="RFC6690" format="default"/> is defined.</t>
        <t>Registrations in the RD are soft state and need to be periodically refreshed.</t>
        <t>An endpoint uses specific interfaces to register, update update, and remove a registration. It is also possible for an RD to fetch Web Links web links
from endpoints and add their contents to its registrations.</t>
        <t>At the first registration of an endpoint, a "registration resource" is created,
the location of which is returned to the registering endpoint. The registering
endpoint uses this registration resource to manage the contents of registrations.</t>
        <t>A lookup interface for discovering any of the Web Links web links stored in the RD is
provided using the CoRE Link Format.</t>
        <figure anchor="fig-arch">
          <name>The RD architecture.</name> Architecture</name>
<artwork name="" type="" type="ascii-art" align="left" alt=""><![CDATA[
           Registration         Lookup
            Interface         Interface
+----+          |                 |
| EP |----      |                 |
+----+    ----  |                 |
              --|-    +------+    |
+----+          | ----|      |    |     +--------+
| EP | ---------|-----|  RD  |----|-----| Client |
+----+          | ----|      |    |     +--------+
              --|-    +------+    |
+----+    ----  |                 |
| CT |----      |                 |
+----+
]]></artwork>
        </figure>
        <t>A Registrant-EP MAY registrant-EP <bcp14>MAY</bcp14> keep concurrent registrations to more than one RD at the same time
if explicitly configured to do so,
but that is not expected to be supported by typical EP implementations.
Any such registrations are independent of each other.
The usual expectation when multiple discovery mechanisms or addresses are configured
is that they constitute a fall-back path for a single registration.</t>
      </section>
      <section anchor="ER-model" numbered="true" toc="default">
        <name>RD Content Model</name>
        <t>The Entity-Relationship (ER) models shown in Figures <xref target="fig-ER-WKC" format="default"/> format="counter"/> and <xref target="fig-ER-RD" format="default"/> format="counter"/> model the contents of /.well-known/core <tt>/.well-known/core</tt> and the RD respectively, with entity-relationship diagrams <xref target="ER" format="default"/>. Entities (rectangles) are used for concepts that exist independently. Attributes (ovals) are used for concepts that exist only in connection with a related entity. Relations (diamonds) give a semantic meaning to the relation between entities. Numbers specify the cardinality of the relations.</t>
        <t>Some of the attribute values are URIs. Those values are always full URIs and never relative references in the information model.
They can, however,
However, they can be expressed as relative references in serializations, and they often are.</t>
        <t>These models provide an abstract view of the information expressed in link-format documents and an RD. They cover the concepts, concepts but not necessarily all details of an RD's operation; they are meant to give an overview, overview and not be a template for implementations.</t>
        <figure anchor="fig-ER-WKC">
          <name>ER Model of the content Content of /.well-known/core</name> <tt>/.well-known/core</tt></name>
          <artwork name="" type="" type="ascii-art" align="left" alt=""><![CDATA[
           +----------------------+
           |   /.well-known/core  |
           +----------------------+
                      |
                      | 1
              ////////\\\\\\\
             <    contains   >
              \\\\\\\\///////
                      |
                      | 0+
            +--------------------+
            |      link          |
            +--------------------+
                      |
                      |  1   oooooooo
                      +-----o target o
                      |      oooooooo
 oooooooooooo   0+    |
o    target  o--------+
o  attribute o        | 0+   oooooo
 oooooooooooo         +-----o rel  o
                      |      oooooo
                      |
                      | 1    ooooooooo
                      +-----o context o
                             ooooooooo
]]></artwork>
        </figure>
        <t>The model shown in <xref
        <t><xref target="fig-ER-WKC" format="default"/> models the contents of /.well-known/core
	<tt>/.well-known/core</tt>, which contains:</t>
        <ul spacing="normal">
          <li>a contains a set of links belonging to the hosting web server</li>
        </ul> server.</t>
	<t>The web server is free to choose links it deems appropriate to be exposed in its <tt>/.well-known/core</tt>.
Typically, the links describe resources that are served by the host, but the set can also contain links to resources on other servers (see examples in <xref target="RFC6690" format="default"/> page 14). sectionFormat="of" section="5"/>).
The set does not necessarily contain links to all resources served by the host.</t>
        <t>A link has the following attributes (see <xref target="RFC8288" format="default"/>):</t>
        <ul spacing="normal">
          <li>
            <t>Zero sectionFormat="of" section="5"/>):</t>
        <ul>
          <li><t>Zero or more link relations:
	    They describe relations between the link context and the link target.  </t>
            <t>
In target.</t>
	    <t>In link-format serialization, they are expressed as space-separated values in the
	    "rel" attribute, attribute and default to "hosts".</t>
	  </li>
          <li>
            <t>A
	  <li><t>A link context URI: It defines the source of the relation, e.g. e.g., <em>who</em> "hosts" something.  </t>
            <t>
In something.</t>
	    <t>In link-format serialization, it is expressed in the "anchor" attribute and defaults
	    to the Origin of the target (practically: (practically, the target with its path and later components removed)</t>
	    removed).</t>
	  </li>
          <li>
            <t>A
	  <li><t>A link target URI: It defines the destination of the relation (e.g. (e.g., <em>what</em> is hosted), hosted) and is
	    the topic of all target attributes.  </t>
            <t>
In attributes.</t>
	    <t>In link-format serialization, it is expressed between angular brackets, brackets and
	    sometimes called the "href".</t>
	  </li>
          <li>Other target attributes (e.g. (e.g., resource type (rt), interface (if), or content format (ct)). (ct)): These provide additional information about the target URI.</li>
        </ul>
	        <figure anchor="fig-ER-RD">
          <name>ER Model of the content Content of the RD</name>
          <artwork name="" type="" type="ascii-art" align="left" alt=""><![CDATA[
                 +--------------+
                 +      RD      +
                 +--------------+
                        | 1
                        |
                        |
                        |
                        |
                   //////\\\\
                  < contains >
                   \\\\\/////
                        |
                     0+ |
 ooooooo     1  +---------------+
o  base o-------|  registration |
 ooooooo        +---------------+
                    |       | 1
                    |       +--------------+
       oooooooo   1 |                      |
      o  href  o----+                 /////\\\\
       oooooooo     |                < contains >
                    |                 \\\\\/////
       oooooooo   1 |                      |
      o   ep   o----+                      | 0+
       oooooooo     |             +------------------+
                    |             |      link        |
       oooooooo 0-1 |             +------------------+
      o    d   o----+                      |
       oooooooo     |                      |  1   oooooooo
                    |                      +-----o target o
       oooooooo   1 |                      |      oooooooo
      o   lt   o----+     ooooooooooo   0+ |
       oooooooo     |    o  target   o-----+
                    |    o attribute o     | 0+   oooooo
    ooooooooooo 0+  |     ooooooooooo      +-----o rel  o
   o  endpoint o----+                      |      oooooo
   o attribute o                           |
    ooooooooooo                            | 1   ooooooooo
                                           +----o context o
                                                 ooooooooo
]]></artwork>
        </figure>
        <t>The model shown in <xref
        <t><xref target="fig-ER-RD" format="default"/> models the contents of
	the RD RD, which contains contains, in addition to /.well-known/core:</t>
        <ul spacing="normal">
          <li>0 <tt>/.well-known/core</tt>, 0 to n Registrations registrations of endpoints,</li>
        </ul>
	endpoints.</t>
        <t>A registration is associated with one endpoint. A registration defines a set of links links,
	as defined for /.well-known/core. <tt>/.well-known/core</tt>. A Registration registration has six types of attributes:</t>
        <ul spacing="normal">
          <li>an endpoint name ("ep", a Unicode string) unique within a sector</li>
          <li>a Registration Base registration base URI ("base", a URI typically describing the scheme://authority part)</li>
          <li>a lifetime ("lt"),</li> ("lt")</li>
          <li>a registration resource location inside the RD ("href"),</li>
          <li>optionally ("href")</li>
          <li>optionally, a sector ("d", a Unicode string)</li>
          <li>optional additional endpoint attributes (from <xref target="iana-registry" format="default"/>)</li>
        </ul>
        <t>The cardinality of "base" is currently 1;
future documents are invited to extend the RD specification to support multiple values (e.g. (e.g., <xref target="I-D.silverajan-core-coap-protocol-negotiation" format="default"/>).
Its value is used as a Base base URI when resolving URIs in the links contained in the endpoint.</t>
        <t>Links are modelled modeled as they are in <xref target="fig-ER-WKC" format="default"/>.</t>
      </section>
      <section anchor="linklocal" numbered="true" toc="default">
        <name>Link-local addresses
        <name>Link-Local Addresses and zone identifiers</name> Zone Identifiers</name>
        <t>Registration Base base URIs can contain link-local IP addresses.
        To be usable across hosts, those cannot be serialized to
        contain zone identifiers (see <xref target="RFC6874" format="default"/> Section 1).</t>
        section="1" sectionFormat="comma"/>).</t>
        <t>Link-local addresses can only be used on a single link
(therefore
(therefore, RD servers cannot announce them when queried on a different link),
and lookup clients using them need to keep track of which interface they got them from.</t>
        <t>Therefore, it is advisable in many scenarios
to use addresses with larger scope scopes, if available.</t>
      </section>
      <section anchor="cellular" numbered="true" toc="default">
        <name>Use Case: Cellular M2M</name>
        <t>Over the last few years, mobile operators around the world
have focused on development of M2M solutions in order to
expand the business to the new type of users: machines. The
machines are connected directly to a mobile network using an appropriate
embedded wireless interface (GSM/GPRS, WCDMA, LTE) (GSM/General Packet Radio Service (GPRS), Wideband Code Division Multiple Access (W-CDMA), LTE, etc.) or via a gateway providing
short
short- and wide range wide-range wireless interfaces.
The ambition in such systems is to build them from reusable components.
These speed up development and deployment, deployment
and enable shared use of machines across different applications.
One crucial component of such systems
is the discovery of resources (and thus the endpoints they are hosted on) capable of providing required
information at a given time or acting on instructions from the end users.</t>
        <t>Imagine a scenario where endpoints installed on vehicles enable
tracking of the position of these vehicles for fleet management purposes and allow
monitoring of environment parameters. During the boot-up process process,
endpoints register with an RD, which is hosted by the
mobile operator or somewhere in the cloud. Periodically, these endpoints
update their registration and may modify resources they offer.</t>
        <t>When endpoints are not always connected, for example example, because they enter
a sleep mode, a remote server is usually used to provide proxy access to
the endpoints. Mobile apps or web applications for environment monitoring contact the RD, look up the endpoints capable of providing information about the environment using an appropriate set of link parameters, obtain information on how to contact them (URLs of the proxy server), and then initiate interaction to obtain information that is finally processed, displayed on the screen screen, and usually stored in a database. Similarly, fleet management systems provide
the appropriate link parameters to the RD to look up for EPs deployed on
the vehicles the application is responsible for.</t>
      </section>
      <section anchor="automation" numbered="true" toc="default">
        <name>Use Case: Home and Building Automation</name>
        <t>Home and commercial building automation systems can benefit from the use
of IoT web services.  The discovery requirements of these applications are
demanding. Home automation usually relies on run-time discovery to commission
the system, whereas whereas, in building automation automation, a combination of professional
commissioning and run-time discovery is used. Both home and building automation
involve peer-to-peer interactions between endpoints, endpoints and involve battery-powered
sleeping devices.
Both can use the common RD infrastructure to establish device interactions efficiently, efficiently
but can pick security policies suitable for their needs.</t>
        <t>Two phases can be discerned for a network servicing the system: (1) installation and (2) operation. During the operational phase, the network is connected to the Internet with a Border Router (e.g. border router (e.g., a 6LoWPAN Border Router (6LBR), see (6LBR) <xref target="RFC6775" format="default"/>) format="default"/>), and the nodes connected to the network can use the Internet services that are provided by the Internet Provider IP or the network administrator. During the installation phase, the network is completely stand-alone, no Border Router border router is connected, and the network only supports the IP communication between the connected nodes. The installation phase is usually followed by the operational phase.
As an RD's operations work without hard dependencies on names or addresses,
it can be used for discovery across both phases.</t>
      </section>
      <section anchor="usecase-catalogues" numbered="true" toc="default">
        <name>Use Case: Link Catalogues</name>
        <t>Resources may be shared through data brokers that have no knowledge beforehand
of who is going to consume the data. An RD can be used to hold
links about resources and services hosted anywhere to make them discoverable
by a general class of applications.</t>
        <t>For example, environmental and weather sensors that generate data for public
consumption may provide data to an intermediary server, server or broker. Sensor
data are published to the intermediary upon changes or at regular intervals.
Descriptions of the sensors that resolve to links to sensor data may be published
to an RD. Applications wishing to consume the data can use
RD Lookup lookup to discover and resolve links
to the desired resources and endpoints. The RD service need
not be coupled with the data intermediary service. Mapping of RDs
to data intermediaries may be many-to-many.</t>
        <t>Metadata in web link formats like formats, such as the one defined in <xref target="RFC6690" format="default"/> format="default"/>, which may be internally stored as  triples,  triples or relation/attribute
pairs providing metadata about resource links, need to be supported by RDs. External catalogues that are
represented in other formats may be converted to common web linking formats for
storage and access by RDs. Since it is common practice for these
to be encoded in URNs <xref target="RFC8141" format="default"/>, simple and lossless structural transforms should
generally be sufficient to store external metadata in RDs.</t>
        <t>The additional features of an RD allow sectors to be defined
to enable access to a particular set of resources from particular applications.
This provides isolation and protection of sensitive data when needed. Application groups with multicast addresses may be defined to support efficient data transport.</t>
      </section>
    </section>
    <section anchor="rd-discovery-and-other-interface-independent-components" numbered="true" toc="default">
      <name>RD discovery Discovery and other interface-independent components</name> Other Interface-Independent Components</name>
      <t>This and the following sections define the required set of REST interfaces between an RD,
endpoints
endpoints, and lookup clients. Although the examples throughout these sections assume the use of
CoAP <xref target="RFC7252" format="default"/>, these REST interfaces can also be realized using HTTP <xref target="RFC7230" format="default"/>.
The multicast discovery and simple registration operations are exceptions to that,
as they rely on mechanisms unavailable in HTTP.
In all definitions in these sections, both CoAP response codes (with dot notation) and HTTP response codes
(without dot notation) are shown. An RD implementing this specification MUST <bcp14>MUST</bcp14> support
the discovery, registration, update, lookup, and removal interfaces.</t>
      <t>All operations on the contents of the RD MUST <bcp14>MUST</bcp14> be atomic and idempotent.</t>

      <t>For several operations, interface templates are given in list form;
those describe the operation participants, request codes, URIs, content formats formats, and outcomes.
Sections of those templates contain normative content about
Interaction, Method, URI Template Template, and URI Template Variables Variables,
as well as the details of the Success condition.
The additional sections
on
for options like Content-Format (such as Content-Format) and on for Failure codes
give typical cases that an implementation of the RD should deal with.
Those serve to illustrate the typical responses
to readers who are not yet familiar with all the details of CoAP based CoAP-based interfaces;
they do not limit what how a server may respond under atypical circumstances.</t>
      <t>REST clients (registrant-EPs and CTs during registration and maintenance, lookup clients, and RD servers during simple registrations)
must be prepared to receive any unsuccessful code and act upon it
according to its definition, options options, and/or payload to the best of their capabilities,
falling back to failing the operation if recovery is not possible.
In particular, they SHOULD <bcp14>SHOULD</bcp14> retry the request upon 5.03 (Service Unavailable; 503 in HTTP)
according to the Max-Age (Retry-After in HTTP) option, option
and SHOULD <bcp14>SHOULD</bcp14> fall back to link-format link format when receiving 4.15 (Unsupported Content-Format; 415 in HTTP).</t>
      <t>An RD MAY <bcp14>MAY</bcp14> make the information submitted to it available to further
directories (subject to security policies on link confidentiality), confidentiality)
if it can ensure that a loop does not form.  The protocol used
between directories to ensure loop-free operation is outside the scope of
this document.</t>
      <section anchor="finding_an_rd" numbered="true" toc="default">
        <name>Finding a Resource Directory</name>
        <t>A (re-)starting (re)starting device may want to find one or more RDs
before it can discover their URIs. Dependent on the operational conditions, one or more of the techniques below apply.</t>
        <t>The device may be pre-configured preconfigured to exercise specific mechanisms for
finding the RD:</t>
        <ol spacing="normal" type="1">
          <li>It may be configured with a specific IP address for the RD.  That IP
address may also be an anycast address, allowing the network to
forward RD requests to an RD that is topologically close; each
target network environment in which some of these preconfigured
nodes are to be brought up is then configured with a route for this
anycast address that leads to an appropriate RD.  (Instead of using
an anycast address, a multicast address can also be preconfigured.
The RD servers then need to configure one of their
interfaces with this multicast address.)</li>
          <li>It may be configured with a DNS name for the RD and use DNS to return
the IP address of the RD; it can find a DNS server to perform the lookup using the usual mechanisms for finding DNS servers.</li>
          <li>It may be configured to use a service discovery mechanism mechanism, such as
DNS-SD,
DNS-based Service Discovery (DNS-SD), as outlined in <xref target="rd-using-dnssd" format="default"/>.</li>
        </ol>
        <t>For cases where the device is not specifically configured with a way
to find an RD, the network may want to provide a
suitable default.</t>
        <ol spacing="normal" type="1">
          <li>The IPv6 Neighbor Discovery option RDAO <xref (<xref target="rdao" format="default"/> format="default"/>) can do that.</li>
          <li>When DHCP is in use,
this could be provided via a DHCP option (no such option is defined
at the time of writing).</li>
        </ol>
        <t>Finally, if neither the device nor the network offers any specific
configuration, the device may want to employ heuristics to find a
suitable RD.</t>
        <t>The present specification does not fully define these heuristics, heuristics but
suggests a number of candidates:</t>
        <ol spacing="normal" type="1">
          <li>In a 6LoWPAN, just assume the Border Router (6LBR) 6LBR can act as an
RD (using the ABRO option Authoritative Border Router Option (ABRO) to find that <xref target="RFC6775" format="default"/>).
Confirmation can be obtained by sending a unicast to
<tt>coap://[6LBR]/.well-known/core?rt=core.rd*</tt>.</li>
<li>In a network that supports multicast well, discovering discover the RD using
a multicast query for /.well-known/core <tt>/.well-known/core</tt>, as specified in CoRE Link
Format <xref target="RFC6690" format="default"/>: Sending format="default"/>, and send a Multicast GET to
<tt>coap://[MCD1]/.well-known/core?rt=core.rd*</tt>.
<tt>coap://[ff0x::fe]/.well-known/core?rt=core.rd*</tt>.  RDs within the
multicast scope will answer the query.</li>
        </ol>

	<t>When answering a multicast request directed at a link-local group,
  the RD may want to respond from a routable address;
  this makes it easier for registrants to use one of their own routable addresses for registration.
When source addresses are selected using the mechanism described in <xref target="RFC6724" format="default"/> is used for source address selection, format="default"/>,
this can be achieved by applying the changes of its Section 10.4, <xref target="RFC6724" section="10.4" sectionFormat="bare"/>,
picking public addresses in Rule 7 of its Section 5 Rule 7, <xref target="RFC6724" section="5" sectionFormat="bare"/>,
and superseding rule Rule 8 with preferring the source address's precedence.</t>
        <t>As some of the RD addresses obtained by the methods listed here are
just (more or less educated) guesses, endpoints MUST <bcp14>MUST</bcp14> make use of any
error messages to very strictly rate-limit requests to candidate IP
addresses that don't work out.  For example, an ICMP Destination
Unreachable message (and, in particular, the port unreachable code for
this message) may indicate the lack of a CoAP server on the candidate
host, or a CoAP error response code code, such as 4.05 "Method (Method Not Allowed" Allowed),
may indicate unwillingness of a CoAP server to act as a directory
server.</t>
        <t>The following RD discovery mechanisms are recommended:</t>
        <ul spacing="normal">
          <li>In managed networks with border routers that need stand-alone operation, the RDAO option is recommended (e.g. (e.g., the operational phase described in <xref target="automation" format="default"/>).</li>
          <li>In managed networks without border router routers (no Internet services available), the use of a preconfigured anycast address is recommended (e.g. (e.g., the installation phase described in <xref target="automation" format="default"/>).</li>
          <li>In networks managed using DNS-SD, the use of DNS-SD for discovery discovery, as described in <xref target="rd-using-dnssd" format="default"/> format="default"/>, is recommended.</li>
        </ul>
        <t>The use of multicast discovery in mesh networks is NOT RECOMMENDED.</t> <bcp14>NOT RECOMMENDED</bcp14>.</t>
        <section anchor="rdao" numbered="true" toc="default">
          <name>Resource Directory Address Option (RDAO)</name>
          <t>The Resource Directory Address Option (RDAO) carries
information about the address of the RD in RAs (Router Advertisements) of IPv6 Neighbor Discovery (ND),
similar to how RDNSS Recursive DNS Server (RDNSS) options <xref target="RFC8106" format="default"/> are sent. This information is
needed when endpoints cannot discover the RD with a link-local
or realm-local scope multicast address, for instance instance, because the
endpoint and the RD are separated by a Border Router
(6LBR).
6LBR. In many circumstances circumstances, the availability of DHCP cannot be guaranteed either
during commissioning of the network. network either. The presence and the use of the RD is
essential during commissioning.</t>
          <t>It is possible to send multiple RDAO options RDAOs in one message,
indicating as many RD addresses.</t>
          <t>The RDAO format is:</t>
          <figure anchor="fig-rdao">
            <name>Resource Directory Address Option</name>
            <artwork name="" type="" type="ascii-art" align="left" alt=""><![CDATA[
0                   1                   2                   3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|     Type      |  Length = 3   |          Reserved             |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                        Valid Lifetime                         |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                                                               |
+                                                               +
|                                                               |
+                          RD Address                           +
|                                                               |
+                                                               +
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Fields:

Type:                   TBD38

Length:
]]></artwork>
	  </figure>

	  <t>Fields:</t>

	  <dl indent="18">
	    <dt>Type:</dt>
	    <dd>41</dd>

	    <dt>Length:</dt>
	    <dd> 8-bit unsigned integer.  The length of
            the option in units of 8 bytes.
            Always 3.

Reserved:               This 3.</dd>

	    <dt>Reserved:</dt>
	    <dd>This field is unused.  It MUST <bcp14>MUST</bcp14> be
            initialized to zero by the sender and
                        MUST
            <bcp14>MUST</bcp14> be ignored by the receiver.

Valid Lifetime:         32-bit receiver.</dd>

	    <dt>Valid Lifetime:</dt>
	    <dd>32-bit unsigned integer.  The length of
            time in seconds (relative to
            the time the packet is received) that
            this RD address is valid.
            A value of all zero bits (0x0) indicates
            that this RD address
            is not valid anymore.

RD Address: anymore.</dd>

	    <dt>RD Address:</dt>
	    <dd> IPv6 address of the RD.
]]></artwork>
          </figure> RD.</dd>
	  </dl>
        </section>
        <section anchor="rd-using-dnssd" numbered="true" toc="default">
          <name>Using DNS-SD to discover Discover a Resource Directory</name>
          <t>An RD can advertise its presence in DNS-SD <xref target="RFC6763" format="default"/>
	  using the service name names defined in this document: <tt>_core-rd._udp</tt> (for CoAP), <tt>_core-rd-dtls._udp</tt>
	  (for CoAP over DTLS), <tt>_core-rd._tcp</tt> (for CoAP over TCP) TCP), or
	  <tt>_core-rd-tls._tcp</tt> (for CoAP over TLS)
defined in this document. TLS).
	  (For the WebSocket transports of CoAP, no service is defined defined,
	  as DNS-SD is typically unavailable in environments where CoAP over WebSockets is used).</t>
	  used.)</t>
	  <t>The selection of the service indicates the protocol used, and
	  the SRV record points the client to a host name and port to use as a starting point for
	  the URI discovery "URI discovery" steps of <xref target="discovery" format="default"/>.</t>
          <t>This section is a simplified simplified, concrete application of the more generic mechanism
specified in <xref target="I-D.ietf-core-rd-dns-sd" format="default"/>.</t>
        </section>
      </section>
      <section anchor="payload-content-formats" numbered="true" toc="default">
        <name>Payload Content Formats</name>
        <t>RDs implementing this specification MUST <bcp14>MUST</bcp14> support the
application/link-format
<tt>application/link-format</tt> content format (ct=40).</t>
        <t>RDs implementing this specification MAY <bcp14>MAY</bcp14> support additional content formats.</t>
        <t>Any additional content format supported by an RD implementing this
specification SHOULD <bcp14>SHOULD</bcp14> be able to express all the information expressible in link-format. link format.
It MAY <bcp14>MAY</bcp14> be able to express information that is inexpressible in link-format, link format,
but those expressions SHOULD <bcp14>SHOULD</bcp14> be avoided where possible.</t>
      </section>
      <section anchor="discovery" numbered="true" toc="default">
        <name>URI Discovery</name>
        <t>Before an endpoint can make use of an RD, it must first know the RD's address
and port, port and the URI path information for its REST APIs. This section defines
discovery of the RD and its URIs using the well-known interface of the
CoRE Link Format <xref target="RFC6690" format="default"/> after having discovered a host host, as described in <xref target="finding_an_rd" format="default"/>.</t>
        <t>Discovery of the RD registration URI is performed by sending either a multicast or
unicast GET request to <tt>/.well-known/core</tt> and including a Resource Type resource type (rt)
parameter <xref target="RFC6690" format="default"/> with the value "core.rd" in the query string. Likewise, a
Resource Type
resource type parameter value of "core.rd-lookup*" is used to discover the
URIs for RD Lookup lookup operations, core.rd* and "core.rd*" is used to discover all URIs for RD operations.
Upon success, the response will contain a payload with
a link format entry for each RD function discovered, indicating the URI
of the RD function returned and the corresponding Resource Type. resource type. When performing
multicast discovery, the multicast IP address used will depend on the scope required
and the multicast capabilities of the network (see <xref target="mc-registration" format="default"/>).</t>
        <t>An RD MAY <bcp14>MAY</bcp14> provide hints about the content-formats content formats it supports in the links it exposes or registers, using the "ct" target attribute, as shown in the example below. Clients MAY <bcp14>MAY</bcp14> use these hints to select alternate content-formats content formats for interaction with the RD.</t>
        <t>HTTP does not support multicast and consequently multicast, and, consequently, only unicast discovery can be
	supported
at the using the HTTP <tt>/.well-known/core</tt> resource.</t>
        <t>RDs implementing this specification MUST <bcp14>MUST</bcp14> support query filtering for
the rt parameter parameter, as defined in <xref target="RFC6690" format="default"/>.</t>
        <t>While the link targets in this discovery step are often expressed in path-absolute form,
this is not a requirement.
Clients of the RD SHOULD <bcp14>SHOULD</bcp14> therefore accept URIs of all schemes they support,
both as URIs and relative references,
and not limit the set of discovered URIs to those hosted at the address used for URI discovery.</t>
        <t>With security policies where the client requires the RD to be authorized to act as an RD,
that authorization may be limited to resources on which the authorized RD advertises the adequate resource types.
Clients that have obtained links they can not cannot rely on yet
can repeat the URI discovery "URI discovery" step at the /.well-known/core <tt>/.well-known/core</tt> resource of the indicated host
to obtain the resource type information from an authorized source.</t>
        <t>The URI Discovery discovery operation can yield multiple URIs of a given resource type.
The client of the RD can use try out any of the discovered addresses initially.</t> addresses.</t>
        <t>The discovery request interface is specified as follows
(this is exactly the Well-Known Interface well-known interface of <xref target="RFC6690" format="default"/> Section 4, section="4" sectionFormat="comma"/>,
	with the additional requirement that the server MUST <bcp14>MUST</bcp14> support query filtering):</t>
<dl>
          <dt>
Interaction:  </dt>
  <dt>Interaction:</dt>
  <dd>
            <t>EP, CT EP, CT, or Client -&gt; RD</t>
          </dd>
          <dt>
Method:  </dt>
          <dd>
            <t>GET</t>
          </dd>
          <dt>
URI Template:  </dt>
          <dd>
            <t>/.well-known/core{?rt}</t> RD </dd>
          <dt>
URI
  <dt>Method:</dt>
  <dd>GET</dd>
  <dt>URI Template:</dt>
  <dd><tt>/.well-known/core{?rt}</tt></dd>
    <dt>URI Template Variables:  </dt> Variables:</dt>
    <dd>
      <t><br/></t>
      <dl>
              <dt>
rt
        <dt>rt := </dt>
              <dd>
                <t>Resource
        <dd>Resource Type. SHOULD <bcp14>SHOULD</bcp14> contain one of the values "core.rd",
        "core.rd-lookup*",
        "core.rd-lookup-res", "core.rd-lookup-ep", or "core.rd*"</t>
              </dd> "core.rd*"</dd>
      </dl>
    </dd>
          <dt>
Accept:  </dt>
          <dd>
            <t>absent, application/link-format
  <dt>Accept:</dt>
  <dd>absent, <tt>application/link-format</tt>, or any other media type representing web links</t>
          </dd> links</dd>
</dl>

<t>The following response is expected on this interface:</t>

<dl>
          <dt>
Success:  </dt>
          <dd>
            <t>2.05 "Content"
  <dt>Success:</dt>
  <dd>2.05 (Content) or 200 "OK" (OK) with an
application/link-format
  <tt>application/link-format</tt> or other web link payload containing one or more matching entries for the RD resource.</t>
          </dd> resource.</dd>
</dl>

<t>The following example shows an endpoint discovering an RD using this interface,
thus learning that the directory resource location, location in this example, example is /rd, /rd and that the
content-format
content format delivered by the server hosting the resource is application/link-format <tt>application/link-format</tt>
	(ct=40).  Note that it is up to the RD to choose its RD locations.</t>

<figure anchor="example-discovery">
          <name>Example discovery exchange</name>
          <artwork name="" type="" align="left" alt=""><![CDATA[ Discovery Exchange</name>
          <sourcecode type=""><![CDATA[
Req: GET coap://[MCD1]/.well-known/core?rt=core.rd* coap://[ff02::fe]/.well-known/core?rt=core.rd*

Res: 2.05 Content
Payload:
</rd>;rt=core.rd;ct=40,
</rd-lookup/ep>;rt=core.rd-lookup-ep;ct=40,
</rd-lookup/res>;rt=core.rd-lookup-res;ct=40
]]></artwork>
]]></sourcecode>
        </figure>
	<t>The following example shows the way of indicating that a client may request
	alternate content-formats. content formats. The Content-Format code attribute "ct" MAY <bcp14>MAY</bcp14>
	include a space-separated sequence of Content-Format codes codes, as specified in
Section 7.2.1 of <xref
	target="RFC7252" format="default"/>, section="7.2.1" sectionFormat="of"/>, indicating that multiple content-formats
	content formats are available. The example below shows the required Content-Format 40 (application/link-format)
indicated
	(<tt>application/link-format</tt>) indicated, as well as a CBOR Concise Binary Object Representation (CBOR)
	and JSON representation from representations in the style of <xref target="I-D.ietf-core-links-json" format="default"/>
(which have no numeric
	(for which the experimental values assigned yet, so they are shown as TBD64 65060 and TBD504 as 65050 are used in that draft). this example). The RD resource locations /rd, /rd
	and /rd-lookup are example values. The server in this example also indicates that
	it is capable of providing observation on resource lookups.</t>
        <figure anchor="example-discovery-ct">
          <name>Example discovery exchange indicating additional content-formats</name>
          <artwork name="" type="" align="left" alt=""><![CDATA[ Discovery Exchange Indicating Additional Content-Formats</name>
          <sourcecode type=""><![CDATA[
Req: GET coap://[MCD1]/.well-known/core?rt=core.rd* coap://[ff02::fe]/.well-known/core?rt=core.rd*

Res: 2.05 Content
Payload:
</rd>;rt=core.rd;ct="40 65225",
</rd>;rt=core.rd;ct=40,
</rd-lookup/res>;rt=core.rd-lookup-res;ct="40 TBD64 TBD504";obs, 65060 65050";obs,
</rd-lookup/ep>;rt=core.rd-lookup-ep;ct="40 TBD64 TBD504"
]]></artwork> 65060 65050"
]]></sourcecode>
        </figure>
        <t>For maintenance, management management, and debugging,
it can be useful to identify the components that constitute the RD server.
The identification can be used to find client-server incompatibilities,
supported features, required updates updates, and other aspects.
The Well-Known well-known interface described in Section 4 of <xref target="RFC6690" format="default"/> section="4" sectionFormat="of"/> can be used to find such data.</t>
<t>It would typically be stored in an implementation information link
(as described in <xref target="I-D.bormann-t2trg-rel-impl" format="default"/>):</t> format="default"/>).</t>
        <figure anchor="example-impl-discovery">
          <name>Example exchange Exchange of obtaining implementation information, using Obtaining Implementation Information Using the relation type currently proposed Relation Type Currently Proposed in the work-in-progress document</name>
          <artwork name="" type="" align="left" alt=""><![CDATA[ <xref target="I-D.bormann-t2trg-rel-impl" format="default"/></name>
          <sourcecode type=""><![CDATA[
Req: GET /.well-known/core?rel=impl-info

Res: 2.05 Content
Payload:
<http://software.example.com/shiny-resource-directory/1.0beta1>;
    rel=impl-info
]]></artwork>
]]></sourcecode>
        </figure>
        <t>Note that that, depending on the particular server's architecture,
such a link could be anchored at the RD server's root
(as in this example), example) or
at individual RD components.
The latter is to be expected when different applications
are run on the same server.</t>
      </section>
    </section>
    <section anchor="registration" numbered="true" toc="default">
      <name>Registration</name>
      <t>After discovering the location of an RD, a registrant-ep registrant-EP or CT MAY <bcp14>MAY</bcp14>
register the resources of the registrant-ep registrant-EP using the registration interface. This interface
accepts a POST from an endpoint containing the list of resources to be added
to the directory as the message payload in the CoRE Link Format <xref target="RFC6690" format="default"/> or other representations of web links, along with query
parameters indicating the name of the endpoint, and optionally endpoint and, optionally, the sector,
lifetime
lifetime, and base URI of the registration.
It is expected that other specifications will define further parameters (see
<xref target="iana-registry" format="default"/>). The RD then creates a new registration resource in the RD and returns its location. The receiving endpoint MUST <bcp14>MUST</bcp14> use that
location when refreshing registrations using this interface. Registration
resources in the RD are kept active for the period indicated by the lifetime
parameter. The creating endpoint is responsible for refreshing the registration resource within this
period
period, using either the registration or update interface. The registration
interface MUST <bcp14>MUST</bcp14> be implemented to be idempotent, so that registering twice
with the same endpoint parameters ep and d (sector) does not create multiple registration resources.</t>
      <t>The following rules apply for a registration request targeting a given (ep, d) value pair:</t>
      <ul spacing="normal">
        <li>When the (ep, d) value pair of the registration-request registration request is different from any existing registration,
a new registration is generated.</li>
        <li>When the (ep, d) value pair of the registration-request registration request is equal to an existing registration,
the content and parameters of the existing registration are replaced with the content of the registration request.
Like the later
As with changes to registration resources, security policies (<xref target="policies" format="default"/>) usually require such requests to come from the same device.</li>
      </ul>
      <t>The posted link-format document can (and typically does) contain relative references
both in its link targets and in its anchors, or anchors; it can also contain empty anchors.
The RD server needs to resolve these references in order to faithfully represent them in lookups.
They are resolved against the base URI of the registration,
which is provided either explicitly in the <tt>base</tt> parameter or constructed implicitly from the requester's URI URI, as constructed from its network address and scheme.</t>
      <t>For media types to which <xref target="limitedlinkformat" format="default"/> applies
(i.e.
(i.e., documents in application/link-format), <tt>application/link-format</tt>),
request bodies MUST <bcp14>MUST</bcp14> be expressed in Limited Link Format.</t>
      <t>The registration request interface is specified as follows:</t>

      <dl>
        <dt>
Interaction:  </dt>
        <dd>
          <t>EP
	<dt>Interaction:</dt>
        <dd>EP or CT -&gt; RD</t>
        </dd>
        <dt>
Method:  </dt>
        <dd>
          <t>POST</t>
        </dd>
        <dt>
URI Template:  </dt>
        <dd>
          <t>{+rd}{?ep,d,lt,base,extra-attrs*}</t>
        </dd>
        <dt>
URI RD</dd>
	<dt>Method:</dt>
        <dd>POST</dd>
	<dt>URI Template:</dt>
        <dd>{+rd}{?ep,d,lt,base,extra-attrs*}</dd>
	<dt>URI Template Variables:  </dt> Variables:</dt>
	<dd>
	  <t><br/></t>
	  <dl>
            <dt>
rd :=      </dt>
            <dd>
              <t>RD
	    <dt>rd :=</dt>
      	    <dd>RD registration URI
	    (mandatory). This is the location of
	    the RD, as obtained from discovery.</t>
            </dd>
            <dt>
ep :=      </dt>
            <dd>
              <t>Endpoint discovery.</dd>
	    <dt>ep :=</dt>

            <dd><t>Endpoint name (mostly mandatory). The endpoint name is an identifier
	    that MUST <bcp14>MUST</bcp14> be unique within a sector.
</t> sector.</t>

            <t>As the endpoint name is a Unicode string, it is
            encoded in UTF-8 (and possibly pct-encoded) percent encoded) during
            variable expansion (see <xref target="RFC6570" format="default"/> Section 3.2.1). section="3.2.1"
            sectionFormat="comma"/>).  The endpoint name MUST NOT <bcp14>MUST NOT</bcp14> contain any
	    character in the inclusive ranges 0-31 or 127-159.</t>

            <t>The maximum length of this parameter is 63 UTF-8 bytes encoded bytes.</t> in UTF-8.</t>
            <t>If the RD is configured to recognize the endpoint that is to be authorized to use
	    exactly
	    one endpoint name, the RD assigns that name. In that case, giving the endpoint name
	    becomes optional for the client; if the client gives any other endpoint name, it is
	    not authorized to perform the registration.</t>
            </dd>
            <dt>
d :=      </dt>
            <dd>
              <t>Sector

	    <dt>d :=</dt>
            <dd><t>Sector (optional). The This is the sector to which this endpoint belongs.
	    When this parameter is not present, the
	    RD MAY <bcp14>MAY</bcp14> associate the endpoint with a configured default sector
	    (possibly based on the endpoint's authorization)
	    or leave it empty.
</t> empty.</t>
	    <t>The sector is encoded like the ep parameter, parameter and is limited to 63 UTF-8 encoded bytes encoded in
	    UTF-8 as well.</t>
            </dd>
            <dt>
lt

	    <dt>lt := </dt>
            <dd>
              <t>Lifetime
	    <dd>Lifetime (optional). Lifetime This is the lifetime of the registration in seconds. Range seconds, with a
	    range of 1-4294967295.
	    If no lifetime is included in the initial registration, a default value of
	    90000 (25 hours) SHOULD <bcp14>SHOULD</bcp14> be assumed.</t>
            </dd>
            <dt>
base :=      </dt> assumed.</dd>
	    <dt>base :=</dt>
	    <dd>
	      <t>Base URI (optional). This parameter sets the base URI of the registration, under
	      which the relative links in the payload are to be interpreted. The specified URI
	      typically does not have a path component of its own, own and MUST <bcp14>MUST</bcp14> be
	      suitable as a base URI to resolve any relative references given in the registration.
	      The parameter is therefore usually of the shape "scheme://authority" for
	      HTTP and CoAP URIs.
	      The URI SHOULD NOT <bcp14>SHOULD NOT</bcp14> have a query or fragment component component,
	      as any non-empty relative part in a reference would remove those parts from the
	      resulting URI.</t>
            </dd>
            <dt/>
            <dd>
	      <t>In the absence of this parameter parameter, the scheme of the protocol, the source address address,
	      and the source port of the registration request are assumed.
	      The Base base URI is consecutively constructed by concatenating the used protocol's scheme
	      with the characters "://", the requester's source address as an address
literal literal,
	      and ":" followed by its port (if it was not the protocol's default
one) in analogy
	      one). This is analogous to the process described in <xref target="RFC7252" format="default"/> Section 6.5.</t>
            </dd>
            <dt/>
            <dd> section="6.5" sectionFormat="comma"/>.</t>
	      <t>This parameter is
	      mandatory when the directory is filled by a third party party, such as an a
	      commissioning tool.</t>
            </dd>
            <dt/>
            <dd>
              <t>If the registrant-ep registrant-EP uses an ephemeral port to register with, it MUST
	      <bcp14>MUST</bcp14> include the base
	      parameter in the registration to provide a valid network path.</t>
            </dd>
            <dt/>
            <dd>
              <t>A registrant that cannot be reached by potential lookup clients at the address it
	      registers from
 (e.g.
	      (e.g., because it is behind some form of Network Address Translation (NAT))
 MUST
	      <bcp14>MUST</bcp14> provide a reachable base address with its registration.</t>
            </dd>
            <dt/>
            <dd>
              <t>If the Base base URI contains a link-local IP literal, it MUST NOT <bcp14>MUST NOT</bcp14>
	      contain a Zone Identifier, Identifier
	      and MUST <bcp14>MUST</bcp14> be local to the link on which the registration request is
	      received.</t>
            </dd>
            <dt/>
            <dd>
              <t>Endpoints that register with a base that contains a path component
	      cannot efficiently express their registrations in Limited Link Format (<xref
	      target="limitedlinkformat" format="default"/>).
	      Those applications should use different representations of links to which <xref
	      target="limitedlinkformat" format="default"/> is not applicable
(e.g.
	      (e.g., <xref target="I-D.hartke-t2trg-coral" target="I-D.ietf-core-coral" format="default"/>).
<!-- or may just use unlimited link format if there is indication that the server is not strict about it --> </t>
	    </dd>
            <dt>
extra-attrs :=      </dt>
            <dd>
              <t>Additional

             <dt>extra-attrs :=</dt>
	      <dd>Additional registration attributes (optional). The endpoint can pass any
	      parameter registered at in <xref target="iana-registry" format="default"/> to the
	      directory. If the RD is
	      aware of the parameter's specified semantics, it processes it the parameter accordingly.
	      Otherwise, it MUST <bcp14>MUST</bcp14> store the unknown key and its value(s) as an
	      endpoint attribute for further lookup.</t>
            </dd> lookup.</dd>
	    </dl>
	  </dd>
        <dt>
Content-Format:  </dt>
        <dd>
          <t>application/link-format
	  <dt>Content-Format:</dt>
          <dd><tt>application/link-format</tt> or any other indicated media type representing web links</t>
        </dd> links</dd>
	</dl>
	<t>The following response is expected on this interface:</t>
	<dl>
        <dt>
Success:  </dt>
	  <dt>Success:</dt>
          <dd>
	    <t>2.01 "Created" (Created) or 201 "Created". (Created). The Location-Path option or Location header
	    field
MUST <bcp14>MUST</bcp14> be included in the response. This location MUST
	    <bcp14>MUST</bcp14> be a stable identifier generated by the RD RD, as it is used
	    for all subsequent operations on this registration resource. The registration
	    resource location thus returned is for the purpose of updating the lifetime
	    of the registration and for maintaining the content of the
	    registered links, including updating and deleting links.</t>
        </dd>
        <dt/>
        <dd>
	    <t>A registration with an already registered already-registered ep and d value pair
	    responds with the same success code and location as the original registration;
	    the set of links registered with the endpoint is replaced with the links
	    from the payload.</t>
        </dd>
        <dt/>
        <dd>
	    <t>The location MUST NOT <bcp14>MUST NOT</bcp14> have a query or fragment component,
	    as that could conflict with query parameters during the Registration Update registration update
	    operation. Therefore, the Location-Query option MUST NOT <bcp14>MUST NOT</bcp14> be
	    present in a successful response.</t>
              </dd>
	    </dl>

	    <t>If the registration fails, including request timeouts,
	    or if delays from Service Unavailable responses with Max-Age or Retry-After
	    accumulate to exceed the registrant's configured timeouts,
	    it SHOULD <bcp14>SHOULD</bcp14> pick another registration URI from the "URI Discovery" discovery" step
and of <xref target="discovery"/>,
	    and, if there is only one or the list is exhausted,
	    pick other choices from the "Finding "finding a Resource Directory" step.  resource directory" step of <xref target="finding_an_rd"/>.
	    Care has to be taken to consider the freshness of results obtained earlier,
e.g. of
	    e.g., the result of a <tt>/.well-known/core</tt> response,
	    the lifetime of an RDAO option RDAO, and
of DNS responses.
	    Any rate limits and persistent errors from the "Finding "finding a Resource Directory" resource directory" step
	    must be considered for the whole registration time,
	    not only for a single operation.</t>
	    <t>The following example shows a registrant-ep registrant-EP with the name "node1" registering
	    two resources to an RD using this interface. The location "/rd"
	    is an example RD location discovered in a request similar to <xref
	    target="example-discovery" format="default"/>.</t>
	    <figure anchor="example-payload">
        <name>Example registration payload</name>
        <artwork name="" type="" align="left" alt=""><![CDATA[ Registration Payload</name>
        <sourcecode type=""><![CDATA[
Req: POST coap://rd.example.com/rd?ep=node1
Content-Format: 40
Payload:
</sensors/temp>;rt=temperature-c;if=sensor,
<http://www.example.com/sensors/temp>;
  anchor="/sensors/temp";rel=describedby

Res: 2.01 Created
Location-Path: /rd/4521
]]></artwork>
]]></sourcecode>
      </figure>
      <t>An RD may optionally support HTTP. Here is an example of almost the same registration operation above, above when done using HTTP.</t>

      <figure anchor="example-payload-http">
        <name>Example registration payload Registration Payload as expressed using Expressed Using HTTP</name>
        <artwork name="" type="" align="left" alt=""><![CDATA[
        <sourcecode type=""><![CDATA[
Req:
POST /rd?ep=node1&base=http://[2001:db8:1::1] HTTP/1.1
Host: rd.example.com
Content-Type: application/link-format

</sensors/temp>;rt=temperature-c;if=sensor,
<http://www.example.com/sensors/temp>;
  anchor="/sensors/temp";rel=describedby

Res:
HTTP/1.1 201 Created
Location: /rd/4521
]]></artwork>
]]></sourcecode>
      </figure>
      <section anchor="simple" numbered="true" toc="default">
        <name>Simple Registration</name>
        <t>Not all endpoints hosting resources are expected to know how to upload links to an RD RD, as described in <xref target="registration" format="default"/>. Instead, simple endpoints can implement the Simple Registration simple registration approach described in this section. An RD implementing this specification MUST <bcp14>MUST</bcp14> implement Simple Registration. simple registration. However, there may
be security reasons why this form of directory discovery would be disabled.</t>
        <t>This approach requires that the registrant-ep registrant-EP makes available the hosted resources
that it wants to be discovered, discovered as links on its <tt>/.well-known/core</tt> interface interface, as
specified in <xref target="RFC6690" format="default"/>.
The links in that document are subject to the same limitations as the payload of a registration
(with respect to <xref target="limitedlinkformat" format="default"/>).</t>
        <ul spacing="normal">
          <li>The registrant-ep registrant-EP finds one or more addresses of the directory server server, as described in <xref target="finding_an_rd" format="default"/>.</li>
          <li>
            <t>The registrant-ep registrant-EP sends (and regularly refreshes with) a POST
	    request to the <tt>/.well-known/rd</tt> URI of the directory server of choice. The
	    body of the POST request is empty, empty and triggers the resource
	    directory server to perform GET requests (redone before lifetime expiry) at the requesting registrant-ep's /.well-known/core registrant-EP's
	    <tt>/.well-known/core</tt> to obtain the link-format payload to register.  </t>
            <t>
The registrant-ep
	    <t>The registrant-EP includes the same registration parameters in the POST request as
	    it would with a regular registration registration, per <xref target="registration"
	    format="default"/>. The registration base URI of the registration is taken from the registrant-ep's
	    registrant-EP's network address (as is default with regular registrations).  </t>
            <t>
Example
	    <t>The following is an example request from the registrant-EP to the RD (unanswered
	    until the next step):</t>
          </li>
        </ul>

        <figure anchor="example-simple1">
          <name>First half example exchange
          <name>First-Half Example Exchange of a simple registration</name>
          <artwork name="" type="" align="left" alt=""><![CDATA[ Simple Registration</name>
          <sourcecode type=""><![CDATA[
Req: POST /.well-known/rd?lt=6000&ep=node1
(No payload)
]]></artwork>
]]></sourcecode>
        </figure>
        <ul spacing="normal">
	  </li>
          <li>
            <t>The RD queries the registrant-ep's registrant-EP's discovery resource to determine the success of
	    the operation. It SHOULD <bcp14>SHOULD</bcp14> keep a cache of the discovery resource and not
	    query it again as long as it is fresh.  </t>
            <t>
Example
            <t>The following is an example request from the RD to the registrant-EP:</t>
          </li>
        </ul>
        <figure anchor="example-simple2">
          <name>Example exchange Exchange of the RD querying Querying the simple endpoint</name>
          <artwork name="" type="" align="left" alt=""><![CDATA[ Simple Endpoint</name>
          <sourcecode type=""><![CDATA[
Req: GET /.well-known/core
Accept: 40

Res: 2.05 Content
Content-Format: 40
Payload:
</sen/temp>
]]></artwork>
]]></sourcecode>
</figure>
          </li>
        </ul>

        <t>With this response, the RD would answer the previous step's request:</t>
        <figure anchor="example-simple3">
          <name>Second half example exchange
          <name>Second-Half Example Exchange of a simple registration</name>
          <artwork name="" type="" align="left" alt=""><![CDATA[ Simple Registration</name>
          <sourcecode type=""><![CDATA[
Res: 2.04 Changed
]]></artwork>
]]></sourcecode>
        </figure>
        <t>The sequence of fetching the registration content before sending a successful response
was chosen to make responses reliable,
and the point about caching was chosen to still allow very constrained registrants.
Registrants MUST <bcp14>MUST</bcp14> be able to serve a GET request to <tt>/.well-known/core</tt> after having requested registration.
Constrained devices MAY <bcp14>MAY</bcp14> regard the initial request as temporarily failed when they need RAM occupied by their own request to serve the RD's GET, GET
and retry later when the RD already has a cached representation of their discovery resources.
Then, the RD can reply immediately immediately, and the registrant can receive the response.</t>
        <t>The simple registration request interface is specified as follows:</t>
	<dl>
          <dt>
Interaction:  </dt>
          <dd>
            <t>EP
	  <dt>Interaction:</dt>
          <dd>EP -&gt; RD</t>
          </dd>
          <dt>
Method: RD</dd>
	  <dt>Method:  </dt>
          <dd>
            <t>POST</t>
          </dd>
          <dt>
URI
          <dd>POST</dd>
	  <dt>URI Template:  </dt>
          <dd>
            <t>/.well-known/rd{?ep,d,lt,extra-attrs*}</t>
          </dd>
             <dd><tt>/.well-known/rd{?ep,d,lt,extra-attrs*}</tt></dd>
        </dl>

        <t>URI Template Variables are the same as they are for registration in <xref target="registration" format="default"/>.
The base attribute is not accepted to keep the registration interface simple;
that rules out registration over CoAP-over-TCP or HTTP that would need to specify one.
For some time during this document's development, the URI template Template <tt>/.well-known/core{?ep,...}</tt> has been was in use instead.</t>
<t>The following response is expected on this interface:</t>

<dl>
          <dt>
Success:  </dt>
          <dd>
            <t>2.04 "Changed".</t>
          </dd>
  <dt>Success:</dt>
  <dd>2.04 (Changed)</dd>
</dl>
        <t>For the second interaction triggered by the above, the registrant-ep
        registrant-EP takes the role of server and the RD takes the role of
        client.  (Note that this is exactly the Well-Known Interface well-known interface
        of <xref target="RFC6690" format="default"/> Section 4):
<!-- the above paragraph could just as well be any other text;
what matters is that the tables above and below are clearly separated. --> section="4" sectionFormat="comma"/>):
        </t>
        <dl>
          <dt>
Interaction:  </dt>
          <dd>
            <t>RD
          <dt>Interaction:</dt>
          <dd>RD -&gt; EP</t>
          </dd>
          <dt>
Method:  </dt>
          <dd>
            <t>GET</t>
          </dd>
          <dt>
URI Template:  </dt>
          <dd>
            <t>/.well-known/core</t>
          </dd> EP</dd>
          <dt>Method:</dt>
          <dd>GET</dd>
          <dt>URI Template:</dt>
          <dd><tt>/.well-known/core</tt></dd>
        </dl>
        <t>The following response is expected on this interface:</t>
        <dl>
          <dt>
Success:  </dt>
          <dd>
            <t>2.05 "Content".</t>
          </dd>
          <dt>Success:</dt>
          <dd>2.05 (Content)</dd>
        </dl>
        <t>When the RD uses any authorization credentials to access the endpoint's discovery resource,
	resource or when it is deployed in a location where third parties might reach it but not
	the endpoint, it SHOULD <bcp14>SHOULD</bcp14> verify that the apparent registrant-ep registrant-EP intends to
	register with the given registration parameters
	before revealing the obtained discovery information to lookup clients.
	An easy way to do that is to verify the simple registration request's sender address using
	the Echo option option, as described in <xref target="I-D.ietf-core-echo-request-tag" format="default"/> Section 2.4.</t> target="RFC9175" section="2.4"
	sectionFormat="comma"/>.</t>
        <t>The RD MUST <bcp14>MUST</bcp14> delete registrations created by simple registration after the expiration of their lifetime. Additional operations on the registration resource cannot be executed because no registration location is returned.</t>
      </section>
      <section anchor="third-party-registration" numbered="true" toc="default">
        <name>Third-party registration</name>
        <name>Third-Party Registration</name>
        <t>For some applications, even Simple Registration simple registration may be too taxing
for some very constrained devices, in particular particular, if the security requirements
become too onerous.</t>
        <t>In a controlled environment (e.g. (e.g., building control), the RD
can be filled by a third party third-party device, called a Commissioning Tool (CT). The commissioning
tool CT can fill the RD from a database or other means. For
that purpose scheme, the IP address and port of the URI of the registered device is
 the value of the "base" parameter of the registration described in <xref target="registration" format="default"/>.</t>
        <t>It should be noted that the value of the "base" parameter applies to all the links of the registration and has consequences for the anchor value of the individual links links, as exemplified in <xref target="weblink" format="default"/>. An eventual  A potential (currently non-existing) nonexistent) "base" attribute of the link is not affected by the value of "base" parameter in the registration.</t>
      </section>
      <section anchor="operations-on-the-registration-resource" numbered="true" toc="default">
        <name>Operations on the Registration Resource</name>
        <t>This section describes how the registering endpoint can maintain the registrations that it created. The registering endpoint can be the registrant-ep registrant-EP or the CT. The registrations are resources of the RD.</t>
        <t>An endpoint should not use this interface for registrations that it did not create.
	This is usually enforced by security policies,
which
	which, in general general, require equivalent credentials for creation of and operations on a
	registration.</t>
        <t>After the initial registration, the registering endpoint retains the returned location of the registration resource for further operations, including refreshing the registration in order to extend the lifetime and "keep-alive" the registration. When the lifetime of the registration has expired, the RD SHOULD NOT <bcp14>SHOULD NOT</bcp14> respond to discovery queries concerning this endpoint. The RD SHOULD <bcp14>SHOULD</bcp14> continue to provide access to the registration resource after a registration time-out timeout occurs in order to enable the registering endpoint to eventually refresh the registration. The RD MAY <bcp14>MAY</bcp14> eventually remove the registration resource for the purpose of garbage collection. If the registration resource is removed, the corresponding endpoint will need to be re-registered.</t> reregistered.</t>
        <t>The registration resource may also be used to cancel the registration using DELETE, DELETE and to perform further operations beyond the scope of this specification.</t>
        <t>Operations on the registration resource are sensitive to reordering;
<xref target="freshness" format="default"/> describes how order is restored.</t>
        <t>The operations on the registration resource are described below.</t>
        <section anchor="update" numbered="true" toc="default">
          <name>Registration Update</name>
          <t>The update interface is used by the registering endpoint to refresh or update its
registration with an RD. To use the interface, the registering endpoint sends a POST request to the registration resource returned by the initial registration operation.</t>
          <t>An update MAY <bcp14>MAY</bcp14> update registration parameters like parameters, such as lifetime, base URI URI, or others.
Parameters that are not being changed should not
be included in an update. Adding parameters that have not changed increases
the size of the message but does not have any other implications.
Parameters are included as query parameters in an update operation operation, as
in <xref target="registration" format="default"/>.</t>
          <t>A registration update resets the timeout of the registration to the (possibly
updated) lifetime of the registration, independent of whether a an <tt>lt</tt> parameter
was given.</t>
          <t>If the base URI of the registration is changed in an update,
relative references submitted in the original registration or later updates are resolved anew against the new base.</t>
          <t>The registration update operation only describes the use of POST with an empty payload.
Future standards might describe the semantics of using content formats and payloads
with the POST method to update the links of a registration (see <xref target="link-up" format="default"/>).</t>
          <t>The update registration request interface is specified as follows:</t>
          <dl>
            <dt>
Interaction:  </dt>
            <dd>
              <t>EP
            <dt>Interaction:</dt>
            <dd>EP or CT -&gt; RD</t>
            </dd>
            <dt>
Method:  </dt>
            <dd>
              <t>POST</t>
            </dd>
            <dt>
URI Template:  </dt>
            <dd>
              <t>{+location}{?lt,base,extra-attrs*}</t>
            </dd>
            <dt>
URI RD</dd>
            <dt>Method:</dt>
            <dd>POST</dd>
            <dt>URI Template:</dt>
            <dd>{+location}{?lt,base,extra-attrs*}</dd>
	    <dt>URI Template Variables:  </dt> Variables:</dt>
	    <dd>
	      <t><br/></t>
              <dl>
                <dt>
location :=      </dt>
                <dd>
                  <t>This
                <dt>location :=</dt>
                <dd>This is the Location location returned by the RD as a result of a successful
		earlier registration.</t>
                </dd>
                <dt>
lt :=      </dt>
                <dd>
                  <t>Lifetime registration.</dd>
                <dt>lt :=</dt>
                <dd>Lifetime (optional). Lifetime This is the lifetime of the registration in seconds. Range seconds,
		with a range of 1-4294967295. If no lifetime is included, the previous last
		lifetime set on a previous update or the original registration
		(falling back to 90000) SHOULD <bcp14>SHOULD</bcp14> be used.</t>
                </dd>
                <dt>
base :=      </dt> used.</dd>
                <dt>base :=</dt>
                <dd>
                  <t>Base URI (optional). This parameter updates the Base base URI established in the
		  original registration to a new value, value and is subject to
		  the same restrictions as in the registration.
</t> registration.</t>
                  <t>If the parameter is set in an update, it is stored by the RD as the new
Base
		  base URI under which to interpret the relative links present in the payload of
		  the original registration.</t>
                  <t>If the parameter is not set in the request but was set before, the previous
Base
		  base URI value is kept unmodified.</t>
                  <t>If the parameter is not set in the request and was not set before either, the
		  source address and source port of the update request are stored as the
Base
		  base URI.</t>
                </dd>
                <dt>
extra-attrs :=      </dt>
                <dt>extra-attrs :=</dt>
                <dd>
                  <t>Additional registration attributes (optional). As with the registration,
		  the RD processes them if it knows their semantics. Otherwise, unknown
		  attributes are stored as endpoint attributes, overriding any previously
		  stored endpoint attributes of the same key.</t>
                </dd>
                <dt/>
                <dd>
		  <t>Note that this default behavior does not allow removing an endpoint attribute
		  in an update. For attributes whose functionality depends on the endpoints'
		  ability to remove them in an update,
		  it can make sense to define a value whose presence is equivalent to the absence
		  of a value. As an alternative, an extension can define different updating rules
		  for their attributes. That necessitates either discovery of discovering whether the RD is
		  aware of that extension, extension or tolerating the default behavior.</t>
                </dd> behavior.</t></dd>
              </dl>
	    </dd>
            <dt>
Content-Format:  </dt>
            <dd>
              <t>none
            <dt>Content-Format:</dt>
            <dd>none (no payload)</t>
            </dd> payload)</dd>
          </dl>
          <t>The following responses are expected on this interface:</t>
          <dl>
            <dt>
Success:  </dt>
            <dd>
              <t>2.04 "Changed"
            <dt>Success:</dt>
            <dd>2.04 (Changed) or 204 "No Content" (No Content) if the update was successfully processed.</t>
            </dd>
            <dt>
Failure:  </dt>
            <dd>
              <t>4.04 "Not Found" processed.</dd>
            <dt>Failure:</dt>
            <dd>4.04 (Not Found) or 404 "Not Found". (Not Found). Registration does not exist (e.g. (e.g., may have
	    been removed).</t>
            </dd> removed).</dd>
          </dl>

          <t>If the registration update fails in any way, including "Not Found" and request timeouts,
or if the time indicated in a Service Unavailable Max-Age/Retry-After exceeds the remaining lifetime,
the registering endpoint SHOULD <bcp14>SHOULD</bcp14> attempt registration again.</t>
          <t>The following example shows how the registering endpoint resets the timeout on its registration resource at
an RD using this interface with the example location value: /rd/4521.</t> value /rd/4521:</t>
          <figure anchor="example-update">
            <name>Example update Update of a registration</name>
            <artwork name="" type="" align="left" alt=""><![CDATA[ Registration</name>
<sourcecode type=""><![CDATA[
Req: POST /rd/4521

Res: 2.04 Changed
]]></artwork>
]]></sourcecode>
          </figure>
          <t>The following example shows the registering endpoint updating its registration resource at
an RD using this interface with the example location value: value /rd/4521. The initial registration by the registering endpoint set the following values:</t>
          <ul spacing="normal">
            <li>endpoint name (ep)=endpoint1</li>
            <li>lifetime (lt)=500</li>
            <li>Base
            <li>base URI (base)=coap://local-proxy-old.example.com</li>
            <li>payload of <xref target="example-payload" format="default"/></li>
          </ul>
          <t>The initial state of the RD is reflected in the following request:</t>
          <figure anchor="example-update-base-lookup-pre">
            <name>Example lookup before Lookup Before a change Change to the base address</name>
            <artwork name="" type="" align="left" alt=""><![CDATA[ Base Address</name>
            <sourcecode type=""><![CDATA[
Req: GET /rd-lookup/res?ep=endpoint1

Res: 2.05 Content
Payload:
<coap://local-proxy-old.example.com/sensors/temp>;
    rt=temperature-c;if=sensor,
<http://www.example.com/sensors/temp>;
    anchor="coap://local-proxy-old.example.com/sensors/temp";
    rel=describedby
]]></artwork>
]]></sourcecode>
          </figure>
          <t>The following example shows the registering endpoint changing the Base base URI to <tt>coaps://new.example.com:5684</tt>:</t>
          <figure anchor="example-update-base">
            <name>Example registration update Registration Update that changes Changes the base address</name>
            <artwork name="" type="" align="left" alt=""><![CDATA[ Base Address</name>
            <sourcecode type=""><![CDATA[
Req: POST /rd/4521?base=coaps://new.example.com

Res: 2.04 Changed
]]></artwork>
]]></sourcecode>
          </figure>
          <t>The consecutive query returns:</t>
          <figure anchor="example-update-base-lookup-post">
            <name>Example lookup after Lookup After a change Change to the base address</name>
            <artwork name="" type="" align="left" alt=""><![CDATA[ Base Address</name>
            <sourcecode type=""><![CDATA[
Req: GET /rd-lookup/res?ep=endpoint1

Res: 2.05 Content
Payload:
<coaps://new.example.com/sensors/temp>;
    rt=temperature-c;if=sensor,
<http://www.example.com/sensors/temp>;
    anchor="coaps://new.example.com/sensors/temp";
    rel=describedby
]]></artwork>
]]></sourcecode>
          </figure>
        </section>
        <section anchor="removal" numbered="true" toc="default">
          <name>Registration Removal</name>
          <t>Although RD registrations have soft state and will eventually timeout time out after their
lifetime, the registering endpoint SHOULD <bcp14>SHOULD</bcp14> explicitly remove an entry from the RD if it
knows it will no longer be available (for example example, on shut-down). shutdown). This is
accomplished using a removal interface on the RD by performing a DELETE on
the endpoint resource.</t>
          <t>The removal request interface is specified as follows:</t>
          <dl>
            <dt>
Interaction:  </dt>
            <dd>
              <t>EP
            <dt>Interaction:</dt>
            <dd>EP or CT -&gt; RD</t>
            </dd>
            <dt>
Method:  </dt>
            <dd>
              <t>DELETE</t>
            </dd>
            <dt>
URI Template:  </dt>
            <dd>
              <t>{+location}</t>
            </dd>
            <dt>
URI RD</dd>
            <dt>Method:</dt>
            <dd>DELETE</dd>
            <dt>URI Template:</dt>
            <dd>{+location}</dd>
            <dt>URI Template Variables:  </dt> Variables:</dt>
            <dd>
	      <t><br/></t>
              <dl>
                <dt>
location :=      </dt>
                <dd>
                  <t>This
                <dt>location :=</dt>
                <dd>This is the Location location returned by the RD as a result of a successful
		earlier registration.</t>
                </dd> registration.</dd>
              </dl>
            </dd>
	  </dl>
          <t>The

         <t> The following responses are expected on this interface:</t>
          <dl>
            <dt>
Success:  </dt>
            <dd>
              <t>2.02 "Deleted"
            <dt>Success:</dt>
            <dd>2.02 (Deleted) or 204 "No Content" (No Content) upon successful deletion</t>
            </dd>
            <dt>
Failure:  </dt>
            <dd>
              <t>4.04 "Not Found" deletion.</dd>
            <dt>Failure:</dt>
            <dd>4.04 (Not Found) or 404 "Not Found". (Not Found). Registration does not exist (e.g. (e.g., may
	    already have been removed).</t>
            </dd> removed).</dd>
          </dl>

          <t>The following examples example shows successful removal of the endpoint from the RD
	  with example location value /rd/4521.</t> /rd/4521:</t>
          <figure anchor="example-removal">
            <name>Example of a registration removal</name>
            <artwork name="" type="" align="left" alt=""><![CDATA[ Registration Removal</name>
            <sourcecode type=""><![CDATA[
Req: DELETE /rd/4521

Res: 2.02 Deleted
]]></artwork>
]]></sourcecode>
          </figure>
        </section>
        <section anchor="link-up" numbered="true" toc="default">
          <name>Further operations</name> Operations</name>
          <t>Additional operations on the registration can be specified in future documents, for
	  example:</t>
          <ul spacing="normal">
            <li>Send iPATCH (or PATCH) updates (<xref <xref target="RFC8132" format="default"/>) format="default"/> to add, remove
	    remove, or change the links of a registration.</li>
            <li>Use GET to read the currently stored set of links in a registration resource.</li>
          </ul>
          <t>Those operations are out of scope of this document, document and will require media types suitable for modifying sets of links.</t>
        </section>
        <section anchor="freshness" numbered="true" toc="default">
          <name>Request freshness</name> Freshness</name>
          <t>Some security mechanisms usable with an RD allow out of order out-of-order request processing, processing
or do not even mandate replay protection at all.
The RD needs to ensure that operations on the registration resource
are executed in an order that does not distort the client's intentions.</t>
          <t>This ordering of operations is expressed in terms of freshness freshness, as defined in <xref target="I-D.ietf-core-echo-request-tag" target="RFC9175" format="default"/>.
Requests that alter a resource's state need to be fresh relative to the latest request
that altered that state in a conflicting way.</t>
          <t>An RD SHOULD <bcp14>SHOULD</bcp14> determine a request's freshness, freshness
and MUST <bcp14>MUST</bcp14> use the Echo option if it requires request freshness and can not cannot determine the it in any other way.
An endpoint MUST <bcp14>MUST</bcp14> support the use of the Echo option.
(One reason why an RD would not require freshness is when no relevant registration properties are covered by is its security policies.)</t>
          <section anchor="efficient-use-of-echo-by-an-rd" numbered="true" toc="default">
            <name>Efficient use Use of Echo by an RD</name>
            <t>To keep latency and traffic added by the freshness requirements to a minimum,
RDs should avoid naive (sufficient but inefficient) freshness criteria.</t>
            <t>Some simple mechanisms the RD can employ are:</t>
            <ul spacing="normal">
              <li>
		<t>State counter. The RD can keep a monotonous counter that increments
		whenever a registration changes. For every registration resource, it stores
		the post-increment value of that resource's last change. Requests altering
		them need to have at least that value encoded in their Echo option, option
		and are otherwise rejected with a 4.01 Unauthorized (Unauthorized) and the current
		counter value as the Echo value. If other applications on the same server
		use Echo as well, that encoding may include a prefix indicating that it
		pertains to the RD's counter.  </t>
                <t>
The counter.</t>
                <t>The value associated with a resource needs to be kept across the removal
		of registrations if the same registration resource is to be reused.  </t>
                <t>
The reused.</t>
                <t>The counter can be reset (and the values of removed resources forgotten)
		when all previous security associations are reset.
<!-- It can *also* be reset more frequently in an epoch based scheme, but that description is too large to fit in the margin. -->  </t>
                <t>
This reset.</t>
                <t>This is the "Persistent Counter" method of <xref target="I-D.ietf-core-echo-request-tag" format="default"/> Appendix A.</t> target="RFC9175"
		section="A" sectionFormat="comma"/>.</t>
              </li>
              <li>
                <t>Preemptive Echo values. The current state counter can be sent in an Echo
		option not only when requests are rejected with 4.01 Unauthorized, (Unauthorized) but
		also with successful responses. Thus, clients can be provided with Echo
		values sufficient for their next request on a regular basis. This is also described in <xref target="RFC9175" section="2.3" sectionFormat="of"/> </t>
                <t> While endpoints may discard received Echo values at leisure between
		requests, they are encouraged to retain these values for the next request
		to avoid additional round trips.</t>
              </li>
              <li>If the RD can ensure that only one security association has modifying access to any registration at any given time, time
and that security association provides order on the requests,
that order is sufficient to show request freshness.</li>
            </ul>
          </section>
          <section anchor="examples-of-echo-usage" numbered="true" toc="default">
            <name>Examples of Echo usage</name> Usage</name>
            <t><xref target="example-freshness" format="default"/> shows the interactions of an endpoint
that has forgotten the server's latest Echo value
and temporarily reduces its registration lifetime:</t>
            <figure anchor="example-freshness">
              <name>Example update Update of a registration</name>
              <artwork name="" type="" align="left" alt=""><![CDATA[ Registration</name>
              <sourcecode type=""><![CDATA[
Req: POST /rd/4521?lt=7200

Res: 4.01 Unauthorized
Echo: 0x0123

(EP tries again immediately) immediately.)

Req: POST /rd/4521?lt=7200
Echo: 0x0123

Res: 2.04 Changed
Echo: 0x0124

(Later

(Later, the EP regains its confidence in its long-term reachability) reachability.)

Req: POST /rd/4521?lt=90000
Echo: 0x0124

Res: 2.04 Changed
Echo: 0x0247
]]></artwork>
]]></sourcecode>
            </figure>

	    <t>The other examples do not show Echo options for simplicity, two reasons: (1) for simplicity
and (2) because they lack the context for any example values to have meaning.</t>
          </section>
        </section>
      </section>
    </section>

    <section anchor="lookup" numbered="true" toc="default">
      <name>RD Lookup</name>
      <t>To discover the resources registered with the RD,
a lookup interface must be provided. This lookup interface
is defined as a default, and it is assumed that RDs may also support lookups
to return resource descriptions in alternative formats (e.g. (e.g., JSON or CBOR link format <xref target="I-D.ietf-core-links-json" format="default"/>)
or using use more advanced interfaces (e.g. (e.g., supporting context context- or semantic
based semantic-based lookup) on different resources that are discovered independently.</t>
      <t>RD Lookup lookup allows lookups for endpoints and resources
using attributes defined in this document and for use with the CoRE
Link Format. The result of a lookup request is the list of links (if any)
corresponding to the type of lookup.  Thus, an endpoint lookup MUST <bcp14>MUST</bcp14> return a list of endpoints endpoints, and a resource lookup MUST <bcp14>MUST</bcp14> return a list of links to resources.</t>
      <t>The lookup type is selected implemented by a URI endpoint, which lookup resource is indicated by a Resource Type resource type, as per <xref target="lookup-types" format="default"/> below:</t> format="default"/>:</t>
      <table anchor="lookup-types" align="center">
        <name>Lookup Types</name>
        <thead>
          <tr>
            <th align="left">Lookup Type</th>
            <th align="left">Resource Type</th>
            <th align="left">Mandatory</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">Resource</td>
            <td align="left">core.rd-lookup-res</td>
            <td align="left">Mandatory</td>
          </tr>
          <tr>
            <td align="left">Endpoint</td>
            <td align="left">core.rd-lookup-ep</td>
            <td align="left">Mandatory</td>
          </tr>
        </tbody>
      </table>
      <section anchor="resource-lookup" numbered="true" toc="default">
        <name>Resource lookup</name> Lookup</name>
        <t>Resource lookup results in links that are semantically equivalent to the links submitted to the RD by the registrant.
The links and link parameters returned by the lookup are equal to the originally submitted ones,
except that the target reference is fully resolved, resolved
and that the anchor reference is fully resolved if it is present in the lookup result at all.</t>
        <t>Links that did not have an anchor attribute in the registration are returned without an anchor attribute.
Links of which href or anchor was submitted as a (full) URI are returned with the respective attribute unmodified.</t>
        <t>The above rules allow the client to interpret the response as links without any further knowledge of the storage conventions of the RD.
The RD MAY <bcp14>MAY</bcp14> replace the registration base URIs with a configured intermediate proxy, e.g. e.g., in the case of an HTTP lookup interface for CoAP endpoints.</t>
        <t>If the base URI of a registration contains a link-local address,
the RD MUST NOT <bcp14>MUST NOT</bcp14> show its links unless the lookup was made from the
link on which the registered endpoint can be reached.
The RD MUST NOT <bcp14>MUST NOT</bcp14> include zone identifiers in the resolved URIs.</t>
      </section>
      <section anchor="lookup-filtering" numbered="true" toc="default">
        <name>Lookup filtering</name> Filtering</name>
        <t>Using the Accept Option, option, the requester can control whether the returned list is returned in CoRE Link Format (<tt>application/link-format</tt>, default) or in alternate content-formats (e.g. content formats (e.g., from <xref target="I-D.ietf-core-links-json" format="default"/>).</t>
        <t>Multiple search criteria MAY <bcp14>MAY</bcp14> be included in a lookup. All included criteria MUST <bcp14>MUST</bcp14> match for a link to be returned. The RD MUST <bcp14>MUST</bcp14> support matching with multiple search criteria.</t>

	<t>A link matches a search criterion if it has an attribute of
        the same name and the same value, allowing for a trailing "*"
        wildcard operator operator, as in Section 4.1 of <xref target="RFC6690" format="default"/>. section="4.1"
        sectionFormat="of"/>.  Attributes that are defined as
        <tt>relation-types</tt> (in the link-format ABNF) match if the
        search value matches any of their values (see Section 4.1 of <xref target="RFC6690" format="default"/>; e.g. section="4.1" sectionFormat="of"/>;
        for example, <tt>?if=tag:example.net,2020:sensor</tt> matches
        <tt>;if="example.regname tag:example.net,2020:sensor";</tt>). tag:example.net,2020:sensor";</tt>.
        A resource link also matches a search criterion if its
        endpoint would match the criterion, and vice versa, an
        endpoint link matches a search criterion if any of its
        resource links matches it.</t>
        <t>Note that <tt>href</tt> is a valid search criterion and matches target references. Like all search criteria, on a resource lookup lookup, it can match the target reference of the resource link itself, itself but also the registration resource of the endpoint that registered it.
Queries for resource link targets MUST <bcp14>MUST</bcp14> be in URI form (i.e. (i.e., not relative references) and are matched against a resolved link target. Queries for endpoints SHOULD <bcp14>SHOULD</bcp14> be expressed in path-absolute form if possible and MUST <bcp14>MUST</bcp14> be expressed in URI form otherwise; the RD SHOULD <bcp14>SHOULD</bcp14> recognize either.
The <tt>anchor</tt> attribute is usable for resource lookups, lookups and, if queried, MUST <bcp14>MUST</bcp14> be in URI form as well.</t>
        <t>Additional query parameters "page" and "count" are used to obtain lookup results in specified increments using pagination, where count specifies how many links to return and page specifies which subset of links organized in sequential pages, each containing 'count' links, starting with link zero and page zero. Thus, specifying a count of 10 and page of 0 will return the first 10 links in the result set (links 0-9). Count = Specifying a count of 10 and page = of 1 will return the next 'page' containing links 10-19, and so on.
Unlike block-wise transfer of a compelte complete result set,
these parameters ensure that each chunk of results can be interpreted on its own.
This simplifies the processing, processing
but can result in duplicate or missed items when coinciding with changes from the registration interface.</t>
        <t>Endpoints that are interested in a lookup result repeatedly or continuously can use
mechanisms like such as ETag caching, resource observation (<xref <xref target="RFC7641" format="default"/>), format="default"/>,
or any future mechanism that might allow more efficient observations of collections.
These are advertised, detected detected, and used according to their own specifications
and can be used with the lookup interface as with any other resource.</t>
        <t>When resource observation is used,
every time the set of matching links changes, changes or the content of a matching link changes, the RD sends a notification with the matching link set.
The notification contains the successful current response to the given request,
especially with respect to representing zero matching links
(see "Success" item below).</t>
        <t>The lookup interface is specified as follows:</t>
        <dl>
          <dt>
Interaction:  </dt>
          <dd>
            <t>Client
          <dt>Interaction:</dt>
          <dd>Client -&gt; RD</t>
          </dd>
          <dt>
Method:  </dt>
          <dd>
            <t>GET</t>
          </dd>
          <dt>
URI Template:  </dt>
          <dd>
            <t>{+type-lookup-location}{?page,count,search*}</t>
          </dd>
          <dt>
URI RD</dd>
          <dt>Method:</dt>
          <dd>GET</dd>
          <dt>URI Template:</dt>
          <dd>{+type-lookup-location}{?page,count,search*}</dd>
          <dt>URI Template Variables:  </dt> Variables:</dt>
	  <dd>
	    <t><br/></t>
            <dl>
              <dt>
type-lookup-location :=      </dt>
              <dd>
                <t>RD Lookup
              <dt>type-lookup-location :=</dt>
              <dd>RD lookup URI for a given lookup type (mandatory). The address is
	      discovered as described in <xref target="discovery" format="default"/>.</t>
              </dd>
              <dt>
search format="default"/>.</dd>
              <dt>search := </dt>
              <dd>
                <t>Search
		<t> Search criteria for limiting the number of results (optional).</t>
              </dd>
              <dt/>
              <dd>
                <t>The (optional). The search
		criteria are an associative array, expressed in a form-style query query,
	       as per the URI template Template (see <xref target="RFC6570" format="default"/> format="default"/>, Sections 2.4.2
	       <xref target="RFC6570" section="2.4.2" sectionFormat="bare"/> and 3.2.8)</t> <xref
	       target="RFC6570" section=" 3.2.8" sectionFormat="bare"/>).</t>
              </dd>
              <dt>
page :=      </dt>
              <dd>
                <t>Page
              <dt>page :=</dt>
              <dd>Page (optional). Parameter This parameter cannot be used without the count
	      parameter. Results are returned from result set in pages that contain
	      'count' links starting from index (page * count). Page numbering starts
	      with zero.</t>
              </dd>
              <dt>
count zero.</dd>
              <dt>count := </dt>
              <dd>
                <t>Count
              <dd>Count (optional). Number The number of results is limited to this parameter value. If
	      the page parameter is also present, the response MUST <bcp14>MUST</bcp14> only include
	      'count' links starting with the (page * count) link in the result set from the
	      query. If the count parameter is not present, then the response MUST <bcp14>MUST</bcp14>
	      return all matching links in the result set. Link numbering starts with zero.</t> zero. </dd>
            </dl>
	  </dd>
          <dt>
Accept:  </dt>
          <dd>
            <t>absent, application/link-format

          <dt>Accept:</dt>
          <dd>absent, <tt>application/link-format</tt>, or any other indicated media type representing web links</t>
          </dd>
	  links</dd>
        </dl>
        <t>The

       <t> The following responses codes are defined for this interface:</t>
        <dl>
          <dt>
Success:  </dt>
          <dt>Success:</dt>
          <dd>
            <t>2.05 "Content" (Content) or 200 "OK" (OK) with an <tt>application/link-format</tt> or other
	    web link payload containing matching entries for the lookup.
</t> lookup.</t>
            <t>The payload can contain zero links (which is an empty payload in the link format described in <xref
	    target="RFC6690" format="default"/> link format, but could also be <tt>[]</tt>
	    in JSON based JSON-based formats), indicating that no entities matched the request.</t>
          </dd>
        </dl>

      </section>
      <section anchor="resource-lookup-examples" numbered="true" toc="default">
        <name>Resource lookup examples</name> Lookup Examples</name>
        <t>The examples in this section assume the existence of CoAP hosts with a default CoAP port 61616. HTTP hosts are possible and do not change the nature of the examples.</t>
        <t>The following example shows a client performing a resource lookup with the example resource look-up lookup locations discovered in <xref target="example-discovery" format="default"/>:</t>
        <figure anchor="example-lookup-res">
          <name>Example of a resource lookup</name>
          <artwork name="" type="" align="left" alt=""><![CDATA[ Resource Lookup</name>
          <sourcecode type=""><![CDATA[
Req: GET /rd-lookup/res?rt=tag:example.org,2020:temperature

Res: 2.05 Content
Payload:
<coap://[2001:db8:3::123]:61616/temp>;
    rt="tag:example.org,2020:temperature"
]]></artwork>
]]></sourcecode>
        </figure>
        <t>A client that wants to be notified of new resources as they show up can use
	this observation:</t>
        <figure anchor="example-lookup-obs">
          <name>Example of an observing resource lookup</name>
          <artwork name="" type="" align="left" alt=""><![CDATA[ Observing Resource Lookup</name>
         <sourcecode type=""><![CDATA[
Req: GET /rd-lookup/res?rt=tag:example.org,2020:light
Observe: 0

Res: 2.05 Content
Observe: 23
Payload: empty

(at a later point in time)

Res: 2.05 Content
Observe: 24
Payload:
<coap://[2001:db8:3::124]/west>;rt="tag:example.org,2020:light",
<coap://[2001:db8:3::124]/south>;rt="tag:example.org,2020:light",
<coap://[2001:db8:3::124]/east>;rt="tag:example.org,2020:light"
]]></artwork>
]]></sourcecode>
        </figure>
        <t>The following example shows a client performing a paginated resource lookup</t> lookup:</t>
        <figure anchor="example-lookup-page">
          <name>Examples
          <name>Example of paginated resource lookup</name>
          <artwork name="" type="" align="left" alt=""><![CDATA[ Paginated Resource Lookup</name>
         <sourcecode type=""><![CDATA[
Req: GET /rd-lookup/res?page=0&count=5

Res: 2.05 Content
Payload:
<coap://[2001:db8:3::123]:61616/res/0>;ct=60,
<coap://[2001:db8:3::123]:61616/res/1>;ct=60,
<coap://[2001:db8:3::123]:61616/res/2>;ct=60,
<coap://[2001:db8:3::123]:61616/res/3>;ct=60,
<coap://[2001:db8:3::123]:61616/res/4>;ct=60

Req: GET /rd-lookup/res?page=1&count=5

Res: 2.05 Content
Payload:
<coap://[2001:db8:3::123]:61616/res/5>;ct=60,
<coap://[2001:db8:3::123]:61616/res/6>;ct=60,
<coap://[2001:db8:3::123]:61616/res/7>;ct=60,
<coap://[2001:db8:3::123]:61616/res/8>;ct=60,
<coap://[2001:db8:3::123]:61616/res/9>;ct=60
]]></artwork>
]]></sourcecode>
        </figure>
        <t>The following example shows a client performing a lookup of all resources
of all endpoints of a given endpoint type. It assumes that two endpoints (with endpoint
names <tt>sensor1</tt> and <tt>sensor2</tt>) have previously registered with their respective
addresses <tt>coap://sensor1.example.com</tt> (<tt>coap://sensor1.example.com</tt> and <tt>coap://sensor2.example.com</tt>, <tt>coap://sensor2.example.com</tt>) and
posted the very payload of the 6th response of section 5 of <xref target="RFC6690" format="default"/>.</t> sectionFormat="of" section="5"/>.</t>
        <t>It demonstrates how absolute link targets stay unmodified, while relative ones
are resolved:</t>
        <figure anchor="example-lookup-multiple">
          <name>Example of resource lookup a Resource Lookup from multiple endpoints</name>
          <artwork name="" type="" align="left" alt=""><![CDATA[ Multiple Endpoints</name>
         <sourcecode type=""><![CDATA[
Req: GET /rd-lookup/res?et=tag:example.com,2020:platform

Res: 2.05 Content
Payload:
<coap://sensor1.example.com/sensors>;ct=40;title="Sensor Index",
<coap://sensor1.example.com/sensors/temp>;rt=temperature-c;if=sensor,
<coap://sensor1.example.com/sensors/light>;rt=light-lux;if=sensor,
<http://www.example.com/sensors/t123>;rel=describedby;
    anchor="coap://sensor1.example.com/sensors/temp",
<coap://sensor1.example.com/t>;rel=alternate;
    anchor="coap://sensor1.example.com/sensors/temp",
<coap://sensor2.example.com/sensors>;ct=40;title="Sensor Index",
<coap://sensor2.example.com/sensors/temp>;rt=temperature-c;if=sensor,
<coap://sensor2.example.com/sensors/light>;rt=light-lux;if=sensor,
<http://www.example.com/sensors/t123>;rel=describedby;
    anchor="coap://sensor2.example.com/sensors/temp",
<coap://sensor2.example.com/t>;rel=alternate;
    anchor="coap://sensor2.example.com/sensors/temp"
]]></artwork>
]]></sourcecode>
        </figure>
      </section>
      <section anchor="ep-lookup" numbered="true" toc="default">
        <name>Endpoint lookup</name> Lookup</name>
        <t>The endpoint lookup returns links to and information about registration resources,
	which themselves can only be manipulated by the registering endpoint.</t>
        <t>Endpoint registration resources are annotated with their endpoint names (ep), sectors
	(d, if present) present), and registration base URI (base; reports the registrant-ep's registrant-EP's address if
	no explicit base was given) given), as well as a constant resource type (rt="core.rd-ep"); the
	lifetime (lt) is not reported.
	Additional endpoint attributes are added as target attributes to their endpoint link
	unless their specification says otherwise.</t>
        <t>Links to endpoints SHOULD <bcp14>SHOULD</bcp14> be presented in path-absolute form or, if
	required, as (full) URIs. (This ensures that the output conforms to Limited Link Format Format,
	as described in <xref target="limitedlinkformat" format="default"/>.)</t>
        <t>Base addresses that contain link-local addresses MUST NOT <bcp14>MUST NOT</bcp14> include zone
	identifiers, and such registrations <!-- or "' base attributes" --> MUST NOT  <bcp14>MUST
	NOT</bcp14> be shown unless the lookup was made from the same link from which the
	registration was made.</t>

	<t>While Endpoint Lookup the endpoint lookup does expose the registration resources,
	the RD does not need to make them accessible to clients.
	Clients SHOULD NOT <bcp14>SHOULD NOT</bcp14> attempt to dereference or manipulate them.</t>
        <t>An
        <t>  An RD can report registrations in lookup whose URI scheme and
   authority differ from that of the lookup resource's. resource.
	Lookup clients MUST <bcp14>MUST</bcp14> be prepared to see arbitrary URIs as registration
	resources in the results and treat them as opaque identifiers;
	the precise semantics of such links are left to future specifications.</t>
	<t>The following example shows a client performing an endpoint lookup that is limited to
	endpoints of endpoint type <tt>tag:example.com,2020:platform</tt>:</t>
        <figure anchor="example-lookup-ep">
          <name>Examples
          <name>Example of endpoint lookup</name>
          <artwork name="" type="" align="left" alt=""><![CDATA[ Endpoint Lookup</name>
         <sourcecode type=""><![CDATA[
Req: GET /rd-lookup/ep?et=tag:example.com,2020:platform

Res: 2.05 Content
Payload:
</rd/1234>;base="coap://[2001:db8:3::127]:61616";ep=node5;
    et="tag:example.com,2020:platform";ct=40;rt=core.rd-ep,
</rd/4521>;base="coap://[2001:db8:3::129]:61616";ep=node7;
    et="tag:example.com,2020:platform";ct=40;d=floor-3;
    rt=core.rd-ep
]]></artwork>
]]></sourcecode>
        </figure>
      </section>
    </section>
    <section anchor="policies" numbered="true" toc="default">
      <name>Security policies</name> Policies</name>
      <t>The security policies that are applicable to an RD strongly depend on the application, application
and are not set out normatively here.</t>
      <t>This section provides a list of aspects that applications should consider when describing their use of the RD,
without claiming to cover all cases.
It is using uses terminology of <xref target="I-D.ietf-ace-oauth-authz" format="default"/>,
in which the RD acts as the Resource Server (RS), and both registrant-eps registrant-EPs and lookup clients act as Clients (C) with support from an Authorization Server (AS),
without the intention of ruling out other (e.g. certificate / public-key infrastructure (PKI) based) schemes.</t> schemes (e.g., those based on certificates/Public Key Infrastructures (PKIs)).</t>
      <t>Any, all all, or none of the below can apply to an application.
Which are relevant depends on its protection objectives.</t>
      <t>Security policies are set by configuration of the RD, RD or by choice of the implementation.
Lookup clients (and, where relevant, endpoints) can only trust an RD to uphold them if it is authenticated, authenticated
and authorized to serve as an RD according to the application's requirements.</t>
      <section anchor="secure-ep" numbered="true" toc="default">
        <name>Endpoint name</name> Name</name>
        <t>Whenever an RD needs to provide trustworthy results to clients doing endpoint lookup, lookup
or resource lookup with filtering on the endpoint name,
the RD must ensure that the registrant is authorized to use the given endpoint name.
This applies both to registration and later to operations on the registration resource.
It is immaterial whether the client is the registrant-ep registrant-EP itself or a CT is doing the registration: registration.
The RD cannot tell the difference, and CTs may use authorization credentials authorizing only operations on that particular endpoint name, name or a wider range of endpoint names.</t>
        <t>It is up to the concrete security policy to describe
how the endpoint name and sector are transported when certificates are used.
For example, it may describe how SubjectAltName dNSName entries are mapped to endpoint and domain names.</t>
        <section anchor="arbitrary-ep" numbered="true" toc="default">
          <name>Random endpoint names</name> Endpoint Names</name>
          <t>Conversely, in applications where the RD does not check the endpoint name,
the authorized registering endpoint can generate a random number (or string) that identifies the endpoint.
The RD should then remember unique properties of the registrant,
associate them with the registration for as long as its registration resource is active (which may be longer than the registration's lifetime),
and require the same properties for operations on the registration resource.</t>

<t>Registrants that are prepared to pick a different identifier when their initial attempt
(or attempts, in the unlikely case of two subsequent collisions)
at registration is unauthorized should pick an identifier at least twice as long as would be needed to enumerate the expected number of registrants;
registrants without any such a recovery options should pick significantly longer endpoint names (e.g. (e.g., using UUID Universally Unique Identifier (UUID) URNs <xref target="RFC4122" format="default"/>).</t>
        </section>
      </section>
      <section anchor="entered-resources" anchor="entered-links" numbered="true" toc="default">
        <name>Entered resources</name> Links</name>
        <t>When lookup clients expect that certain types of links can only originate from certain endpoints,
then the RD needs to apply filtering to the links an endpoint may register.</t>
        <t>For example, if clients use an RD to find a server that provides firmware updates,
then any registrant that wants to register (or update) links to firmware sources will need to provide suitable credentials to do so, independently of its endpoint name.</t>
        <t>Note that the impact of having undesirable links in the RD depends on the application:
if application.
If the client requires the firmware server to present credentials as a firmware server,
a fraudulent link's impact is limited to the client revealing its intention to obtain updates and slowing down the client until it finds a legitimate firmware server;
if the client accepts any credentials from the server as long as they fit the provided URI, the impact is larger.</t>

<t>An RD may also require that links are only registered if the registrant is authorized to publish information about the anchor (or even target) of the link.
One way to do this is to demand that the registrant present the same credentials in its role as a registering client that they'd it would need to present if contacted in its role as a server when contacted at the resources' URI, which URI. These credentials may include using the address and port that are part of the URI.
Such a restriction places severe practical limitations on the links that can be registered.</t>
        <t>As above, the impact of undesirable links depends on the extent to which the lookup client relies on the RD.
To avoid the limitations, RD applications should consider <!-- can we pull in RFC6919 to make this normative? --> prescribing that lookup clients only use the discovered information as hints, hints
and describe which pieces of information need to be verified because they impact the application's security.
A straightforward way to verify such information is to request it again from an authorized server, typically the one that hosts the target resource.
That is similar to what happens in <xref target="discovery" format="default"/> when the URI discovery "URI discovery" step is repeated.</t>
      </section>
      <section anchor="link-confidentiality" numbered="true" toc="default">
        <name>Link confidentiality</name> Confidentiality</name>
        <t>When registrants publish information in the RD that is not available to any client that would query the registrant's /.well-known/core <tt>/.well-known/core</tt> interface,
or when lookups to that interface are subject so to stricter firewalling than lookups to the RD,
the RD may need to limit which lookup clients may access the information.</t>
        <t>In this case, the endpoint (and not the lookup clients) needs to be careful to check the RD's authorization.
The RD needs to check any lookup client's authorization
before revealing information directly (in resource lookup)
or indirectly (when using it to satisfy a resource lookup search criterion).</t>
      </section>
      <section anchor="segmentation" numbered="true" toc="default">
        <name>Segmentation</name>
        <t>Within a single RD, different security policies can apply.</t>
        <t>One example of this are multi-tenant deployments separated by the sector (d) parameter.
Some sectors might apply limitations on the endpoint names available,
while others use a random identifier approach to endpoint names and place limits on the entered links based on their attributes instead.</t>
        <t>Care must be taken in such setups to determine the applicable access control measures to each operation.
One easy way to do that is to mandate the use of the sector parameter on all operations,
as no credentials are suitable for operations across sector borders anyway.</t>
      </section>
      <section anchor="first-come-first-remembered-a-default-policy" numbered="true" toc="default">
        <name>First-Come-First-Remembered:
        <name>"First Come First Remembered": A default policy</name> Default Policy</name>
        <t>The First-Come-First-Remembered "First Come First Remembered" policy is provided both as a reference example for a
	security policy definition, definition and as a policy that implementations may choose to use as
	default policy in the absence of any other configuration. It is designed to enable efficient
	discovery operations even in ad-hoc ad hoc settings.</t>
	<t>Under this policy, the RD accepts registrations for any endpoint name that is not assigned to an active registration resource, resource
and only accepts registration updates from the same endpoint.
The policy is minimal in that towards lookup clients it does not make any of promises to lookup clients about the claims of Sections <xref target="entered-resources" format="default"/> target="entered-links" format="counter"/> and <xref target="link-confidentiality" format="default"/>, format="counter"/>,
and its promises about the claims on in <xref target="secure-ep" format="default"/> are limited to the lifetime of that endpoint's registration.
It does, however, guarantee towards any does however promise the endpoint that that, for the duration of its registration, its links will be discoverable on the RD.</t>
        <t>When a registration or operation is attempted, the RD MUST <bcp14>MUST</bcp14> determine the client's subject name or public key:</t>
        <ul spacing="normal">
          <li>If the client's credentials indicate any subject name that is certified by any authority which that the RD recognizes (which may be the system's trust anchor store), all such subject names are stored.
With credentials based on CWT or JWT based credentials (as common with ACE), Authentication and Authorization for Constrained Environments (ACE)), the Subject (sub) claim is stored as a single name, if it exists.
With X.509 certificates, the Common Name (CN) and the complete list of SubjectAltName entries are stored.
In both cases, the authority that certified the claim is stored along with the subject, as the latter may only be locally unique.</li>
          <li>Otherwise, if the client proves possession of a private key, the matching public key is stored.
This applies both to raw public keys and to the public keys indicated in certificates that failed the above authority check.</li>
          <li>If neither is present, a reference to the security session itself is stored.
With (D)TLS, that is the connection itself, itself or the session resumption information information, if available.
With OSCORE, that is the security context.</li>
        </ul>
        <t>As part of the registration operation, that information is stored along with the registration resource.</t>
        <t>The RD MUST <bcp14>MUST</bcp14> accept all registrations whose registration resource is not already active,
as long as they are made using a security layer supported by the RD.</t>
        <t>Any operation on a registration resource,
including registrations that lead to an existing registration resource,
MUST
<bcp14>MUST</bcp14> be rejected by the RD unless all the stored information is found in the new request's credentials.</t>

<t>Note that that, even though subject names are compared in this policy,
they are never directly compared to endpoint names,
and an endpoint can not cannot expect to "own" any particular endpoint name outside of an active registration --
even if a certificate says so.
It is an accepted shortcoming of this approach that the endpoint has no indication of whether the RD remembers it by its subject name or public key;
recognition by subject happens on a best-effort base basis (given the RD may not recognize any authority).
Clients MUST <bcp14>MUST</bcp14> be prepared to pick a different endpoint name when rejected by the RD initially or after a change in their credentials;
picking an endpoint name name, as per <xref target="arbitrary-ep" format="default"/> format="default"/>, is an easy option for that.</t>
        <t>For this policy to be usable without configuration, clients should not set a sector name in their registrations.
An RD can set a default sector name for registrations accepted under this policy,
which is useful especially useful in a segmented setup where different policies apply to different sectors.
The configuration of such a behavior, as well as any other configuration applicable to such an RD
(i.e.
(i.e., the set of recognized authorities) authorities),
is out of scope for this document.</t>
      </section>
    </section>
    <section anchor="security-considerations" numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>The security considerations as described in Section 5 of <xref target="RFC8288" format="default"/> section="5" sectionFormat="of"/> and
Section 6 of <xref target="RFC6690" format="default"/> section="6" sectionFormat="of"/> apply. The <tt>/.well-known/core</tt> resource may be
protected e.g.
protected, e.g., using DTLS when hosted on a CoAP server server, as described in
<xref target="RFC7252" format="default"/>.</t>
      <t>Access that is limited or affects sensitive data SHOULD <bcp14>SHOULD</bcp14> be protected,
e.g.
e.g., using (D)TLS or OSCORE (<xref <xref target="RFC8613" format="default"/>;
which aspects of the RD this affects depends on the security policies of the application (see <xref target="policies" format="default"/>).</t>
      <section anchor="seccons-discovery" numbered="true" toc="default">
        <name>Discovery</name>
        <t>Most steps in discovery of the RD, and possibly its resources, are not covered by CoAP's security mechanisms.
This will not endanger the security properties of the registrations and lookup itself
(where the client requires authorization of the RD if it expects any security properties of the operation), operation)
but may leak the client's intention to third parties, parties
and allow them to slow down the process.</t>
        <t>To mitigate that, clients can retain the RD's address,
use secure discovery options like (such as configured addresses, addresses),
and send queries for RDs in a very general form (<tt>?rt=core.rd*</tt> (e.g., <tt>?rt=core.rd*</tt> rather than <tt>?rt=core.rd-lookup-ep</tt>).</t>
      </section>
      <section anchor="endpoint_identification" numbered="true" toc="default">
        <name>Endpoint Identification and Authentication</name>
        <t>An Endpoint endpoint (name, sector) pair is unique within the set of endpoints registered by the RD. An Endpoint MUST NOT endpoint <bcp14>MUST NOT</bcp14> be identified by its protocol, port port, or IP
address
address, as these may change over the lifetime of an Endpoint.</t> endpoint.</t>
        <t>Every operation performed by an Endpoint endpoint on an RD
SHOULD
<bcp14>SHOULD</bcp14> be mutually authenticated using Pre-Shared Key, Raw Public Key a pre-shared key, a raw public key, or
Certificate based
certificate-based security.</t>
        <t>Consider the following threat: two devices devices, A and B B, are registered at a single server. Both devices have unique, per-device credentials for use with DTLS to make sure that only parties with authorization to access A or B can do so.</t>
        <t>Now, imagine that a malicious device A wants to sabotage the device B. It uses its credentials during the DTLS exchange. Then, it specifies the
endpoint name of device B as the name of its own endpoint in device A. If the server does not check
whether the identifier provided in the DTLS handshake matches the
identifier used at the CoAP layer layer, then it may be inclined to use the
endpoint name for looking up what information to provision to the malicious device.</t>

<t>Endpoint authorization needs to be checked on registration and registration resource operations
independently of whether there are configured requirements on the credentials for a given endpoint name (and sector; <xref and sector (<xref target="secure-ep" format="default"/>)
or whether arbitrary names are accepted (<xref target="arbitrary-ep" format="default"/>).</t>
        <t>Simple registration could be used to circumvent address-based access control: control.
An attacker would send a simple registration request with the victim's address as the source address, address
and later look up the victim's /.well-known/core <tt>/.well-known/core</tt> content in the RD.
Mitigation for this is recommended in <xref target="simple" format="default"/>.</t>
        <t>The registration resource path is visible to any client that is allowed endpoint lookup, lookup
and can be extracted by resource lookup clients as well.
The same goes for registration attributes that are shown as target attributes or lookup attributes.
The RD needs to consider this in the choice of registration resource paths,
and
as do administrators or endpoint endpoints in their choice of attributes.</t>
      </section>
      <section anchor="access-control" numbered="true" toc="default">
        <name>Access Control</name>
        <t>Access control SHOULD <bcp14>SHOULD</bcp14> be performed separately for the RD registration and Lookup lookup
API paths, as different endpoints may be authorized to register
with an RD from those authorized to lookup look up endpoints from the RD. Such access
control SHOULD <bcp14>SHOULD</bcp14> be performed in as fine-grained a level as possible. For example example,
access control for lookups could be performed either at the sector, endpoint endpoint,
or resource level.</t>
        <t>The precise access controls necessary (and the consequences of failure to enforce them)
depend on the protection objectives of the application and the security policies (<xref target="policies" format="default"/>) derived from them.</t>
      </section>
      <section anchor="denial-of-service-attacks" numbered="true" toc="default">
        <name>Denial of Service
        <name>Denial-of-Service Attacks</name>
        <t>Services that run over UDP unprotected are vulnerable to unknowingly
amplify and distribute a DoS attack attack, as UDP does not require a return
routability check.
Since RD lookup responses can be significantly
larger than requests, RDs are prone to this.</t>
        <t><xref target="RFC7252" format="default"/> describes this at length in its Section 11.3, <xref target="RFC7252" section="11.3" sectionFormat="bare"/>,
including some mitigation by using small block sizes in responses.
The upcoming
<xref target="I-D.ietf-core-echo-request-tag" target="RFC9175" format="default"/> updates that
by describing a source address verification mechanism using the Echo option.</t>
        <t>[ If this document is published together with or after I-D.ietf-core-echo-request-tag,
the above paragraph is replaced with the following:</t>
        <t><xref target="RFC7252" format="default"/> describes this at length in its Section 11.3,
and <xref target="I-D.ietf-core-echo-request-tag" format="default"/> (which updates the former)
recommends using the Echo option to verify the request's source address.</t>
        <t>]</t>
      </section>
      <section anchor="skipping-freshness-checks" numbered="true" toc="default">
        <name>Skipping freshness checks</name> Freshness Checks</name>
        <t>When RD based RD-based applications are built in which request freshness checks are not performed,
these concerns need to be balanced:</t>
        <ul spacing="normal">
          <li>
            <t>When alterations to registration attributes are reordered,
an attacker may create any combination of attributes ever set,
with the attack difficulty determined by the security layer's replay properties.  </t>
            <t>
For example, if <xref target="example-freshness" format="default"/> were conducted without freshness assurances,
an attacker could later reset the lifetime back to 7200.
<!-- That is, with DTLS without replay protection, or DTLS when causing a retransmission and swallowing one message,
or with OSCORE when swallowing all of an update's retransmission but the ep later tries again. -->
Thus, the device is made unreachable to lookup clients.</t>
          </li>
          <li>
            <t>When registration updates without query parameters
	    (which just serve to restart the lifetime) can be reordered,
	    an attacker can use intercepted messages to give the appearance of the device being
	    alive to the RD.  </t>
            <t>
This
	    <t>This is unacceptable when when the RD's security policy promises reachability of
	    endpoints
(e.g. (e.g., when disappearing devices would trigger further investigation), investigation)
	    but may be acceptable with other policies.</t>
          </li>
        </ul>
      </section>
    </section>

    <section anchor="iana-considerations" numbered="true" toc="default">
      <name>IANA Considerations</name>
      <section anchor="iana-rt" numbered="true" toc="default">
        <name>Resource Types</name>
        <t>IANA is asked to enter has added the following values into to the Resource "Resource Type (rt=) Link Target Attribute Values sub-registry Values"
	subregistry of the Constrained Restful "Constrained RESTful Environments (CoRE) Parameters Parameters"
	registry defined in <xref target="RFC6690" format="default"/>:</t>

<table align="center">
  <name>Additions to Resource Type (rt=) Link Target Attribute Values Subregistry</name>
          <thead>
            <tr>
              <th align="left">Value</th>
              <th align="left">Description</th>
              <th align="left">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">core.rd</td>
              <td align="left">Directory resource of an RD</td>
              <td align="left">RFCTHIS align="left">RFC 9176, <xref target="discovery" format="default"/></td>
            </tr>
            <tr>
              <td align="left">core.rd-lookup-res</td>
              <td align="left">Resource lookup of an RD</td>
              <td align="left">RFCTHIS align="left">RFC 9176, <xref target="discovery" format="default"/></td>
            </tr>
            <tr>
              <td align="left">core.rd-lookup-ep</td>
              <td align="left">Endpoint lookup of an RD</td>
              <td align="left">RFCTHIS align="left">RFC 9176, <xref target="discovery" format="default"/></td>
            </tr>
            <tr>
              <td align="left">core.rd-ep</td>
              <td align="left">Endpoint resource of an RD</td>
              <td align="left">RFCTHIS align="left">RFC 9176, <xref target="lookup" format="default"/></td>
            </tr>
          </tbody>
        </table>
      </section>
      <section anchor="ipv6-nd-resource-directory-address-option" numbered="true" toc="default">
        <name>IPv6 ND Resource Directory Address Option</name>
        <t>This document registers
        <t>IANA has registered one new ND option type under in the sub-registry "IPv6 Neighbor
        Discovery Option Formats" subregistry of the "Internet Control Message
        Protocol version 6 (ICMPv6) Parameters" registry:</t>
        <ul spacing="normal">
          <li>Resource

<table>
  <name>Addition to IPv6 Neighbor Discovery Option Formats Subregistry</name>
  <thead>
    <tr>
      <th>Type</th>
      <th>Description</th>
      <th>Reference</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>41</td>
      <td>Resource Directory Address Option (TBD38)</li>
        </ul>
        <t>[ The RFC editor is asked to replace TBD38
with the assigned number in the document;
the value 38 is suggested. ]</t> Option</td>
      <td>RFC 9176</td>
    </tr>
  </tbody>
</table>

      </section>

      <section anchor="iana-registry" numbered="true" toc="default">
        <name>RD Parameter Parameters Registry</name>
        <t>This specification defines a new sub-registry subregistry for registration and
        lookup parameters called "RD Parameters" under "CoRE Parameters". within the "Constrained
        RESTful Environments (CoRE) Parameters" registry. Although this
        specification defines a basic set of parameters, it is expected that
        other standards that make use of this interface will define new
        ones.</t>
        <t>Each entry in the registry must include</t> include:</t>
        <ul spacing="normal">
          <li>the human readable human-readable name of the parameter,</li>
          <li>the short name name, as used in query parameters or target attributes,</li>
          <li>syntax and validity requirements (if any),</li>
          <li>indication of whether it can be passed as a query parameter at registration of
	  endpoints, passed as a query parameter in lookups, or be expressed as a target
	  attribute,</li>
          <li>syntax and validity requirements if any,</li>
          <li>a description,</li>
          <li>and a description, and</li>
          <li>a link to reference documentation.</li>
        </ul>
        <t>The query parameter MUST <bcp14>MUST</bcp14> be both a valid URI query key <xref target="RFC3986" format="default"/> and a token as used in <xref target="RFC8288" format="default"/>.</t>
        <t>The description reference documentation must give details on whether the parameter can be updated, updated and how it is to be processed in lookups.</t>
        <t>The mechanisms around new RD parameters should be designed in such a way that they tolerate RD implementations that are unaware of the parameter and expose any parameter passed at registration or updates on in endpoint lookups. (For example, if a parameter used at registration were to be confidential, the registering endpoint should be instructed to only set that parameter if the RD advertises support for keeping it confidential at the discovery step.)</t>
        <t>Initial entries in this sub-registry subregistry are as follows:</t>
        <table anchor="tab-registry" align="center">
          <name>RD Parameters</name>
          <name>New RD Parameters Registry</name>
          <thead>
            <tr>
              <th align="left">Full name</th> align="left">Name</th>
              <th align="left">Short</th>
              <th align="left">Validity</th>
              <th align="left">Use</th>
              <th align="left">Description</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Endpoint Name</td>
              <td align="left">ep</td>
              <td align="left">Unicode*</td>
              <td align="left">RLA</td>
              <td align="left">Name of the endpoint</td>
            </tr>
            <tr>
              <td align="left">Lifetime</td>
              <td align="left">lt</td>
              <td align="left">1-4294967295</td>
              <td align="left">R</td>
              <td align="left">Lifetime of the registration in seconds</td>
            </tr>
            <tr>
              <td align="left">Sector</td>
              <td align="left">d</td>
              <td align="left">Unicode*</td>
              <td align="left">RLA</td>
              <td align="left">Sector to which this endpoint belongs</td>
            </tr>
            <tr>
              <td align="left">Registration Base URI</td>
              <td align="left">base</td>
              <td align="left">URI</td>
              <td align="left">RLA</td>
              <td align="left">The scheme, address and port address, port, and path at which this server is
	      available</td>
            </tr>
            <tr>
              <td align="left">Page</td>
              <td align="left">page</td>
              <td align="left">Integer</td>
              <td align="left">L</td>
              <td align="left">Used for pagination</td>
            </tr>
            <tr>
              <td align="left">Count</td>
              <td align="left">count</td>
              <td align="left">Integer</td>
              <td align="left">L</td>
              <td align="left">Used for pagination</td>
            </tr>
            <tr>
              <td align="left">Endpoint Type</td>
              <td align="left">et</td>
              <td align="left">
                RFC 9176, <xref target="et-description" format="default"/></td>
              <td align="left">RLA</td>
              <td align="left">Semantic type of the endpoint (see RFC 9176, <xref target="et-registry" format="default"/>)</td>
            </tr>
          </tbody>
        </table>
        <t>(Short: Short
        <t>Where:</t>
	<dl newline="false" spacing="normal">
	  <dt>Short:</dt>
	  <dd>Short name used in query parameters or target attributes. Validity: Unicode* attributes</dd>

	  <dt>Validity:</dt>
	  <dd>
	    <t><br/></t>
	    <dl spacing="normal">
	      <dt>Unicode* = </dt>
	      <dd>up to 63 Bytes bytes of UTF-8 encoded UTF-8-encoded Unicode, with no control characters as per
          <xref target="registration" format="default"/>. Use: R = used format="default"/></dd>
	  </dl>
	  </dd>

	  <dt>Use:</dt>
	  <dd>
	    <t><br/></t>
	    <dl spacing="compact">
              <dt>R =</dt>
	      <dd>used at registration, L = used registration</dd>
	      <dt>L =</dt>
	      <dd>used at lookup, A = expressed lookup</dd>
	      <dt>A =</dt>
	      <dd>expressed in the target attribute.)</t> attribute</dd>

	  </dl>
	  </dd>
	</dl>

        <t>The descriptions for the options defined in this document are only summarized here.
To which registrations they apply and when they are to be shown is are described in the respective sections of this document.
All their reference documentation entries point to this document.</t>
        <t>The IANA policy for future additions to the sub-registry subregistry is "Expert Review" Expert Review,
as described in <xref target="RFC8126" format="default"/>. The evaluation should consider
formal criteria,
duplication of functionality (Is (i.e., is the new entry redundant with an existing one?),
topical suitability (E.g. (e.g., is the described property actually a property of the endpoint and not a property of a particular resource, in which case it should go into the payload of the registration and need not be registered?),
and the potential for conflict with commonly used target attributes (For example, (e.g., <tt>if</tt> could be used as a parameter for conditional registration if it were not to be used in lookup or attributes, attributes but would make a bad parameter for lookup, lookup because a resource lookup with an <tt>if</tt> query parameter could ambiguously filter by the registered endpoint property or the target attribute <xref target="RFC6690" format="default"/> target attribute).</t> format="default"/>).</t>
        <section anchor="et-description" numbered="true" toc="default">
          <name>Full description Description of the "Endpoint Type" RD Parameter</name>
          <t>An endpoint registering at an RD can describe itself with
          endpoint types, similar to how resources are described with Resource Types resource
          types in <xref target="RFC6690" format="default"/>.  An endpoint
          type is expressed as a string, which can be either a URI or one of
          the values defined in the Endpoint "Endpoint Type sub-registry. (et=) RD Parameter Values"
          subregistry.  Endpoint types can be passed in the <tt>et</tt> query
          parameter as part of extra-attrs at the Registration step, "registration" step of <xref target="registration"/>, are shown
          on endpoint lookups using the <tt>et</tt> target attribute, and can
          be filtered for using <tt>et</tt> as a search criterion in resource
          and endpoint lookup.  Multiple endpoint types are given as separate
          query parameters or link attributes.</t>
          <t>Note that Endpoint Type the endpoint type differs from Resource Type the resource type in that it uses multiple
attributes rather than space separated space-separated values.
As a result, RDs implementing this specification automatically support correct
filtering in the lookup interfaces from the rules for unknown endpoint
attributes.</t>
        </section>
      </section>
      <section anchor="et-registry" numbered="true" toc="default">
        <name>"Endpoint Type"
        <name>Endpoint Type (et=) RD Parameter values</name> Values</name>
        <t>This specification establishes a new sub-registry under "CoRE Parameters" subregistry called '"Endpoint Type" "Endpoint
        Type (et=) RD Parameter values'. Values" within the "Constrained RESTful
        Environments (CoRE) Parameters" registry.
	The registry properties (required policy, requirements, and template) are
	identical to those of the Resource "Resource Type parameters (rt=) Link Target Attribute
	Values" subregistry defined in <xref target="RFC6690" format="default"/>, format="default"/>;
	in short:</t>
        <t>The short, the review policy is IETF Review for
        values starting with "core", "core" and Specification Required for others.</t>
        <t>The requirements to be enforced are:</t>
        <ul spacing="normal">
          <li>The values MUST <bcp14>MUST</bcp14> be related to the purpose described in <xref target="et-description" format="default"/>.</li>
          <li>The registered values MUST <bcp14>MUST</bcp14> conform to the ABNF reg-rel-type definition of
<xref target="RFC6690" format="default"/> and MUST NOT <bcp14>MUST NOT</bcp14> be a URI.</li>
          <li>It is recommended to use the period "." character for segmentation.</li>
        </ul>
        <t>The initial contents of the registry initially contains one value:</t>
        <ul spacing="normal">
          <li>"core.rd-group": An are as follows:</t>

<table>
  <name>New Endpoint Type (et=) RD Parameter Values Registry</name>
  <thead>
    <tr>
      <th>Value</th>
      <th>Description</th>
      <th>Reference</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>core.rd-group</td>
      <td>An application group group, as described in RFC 9176, <xref target="groups" format="default"/>.</li>
        </ul> format="default"/>.</td>
      <td>RFC 9176</td>
    </tr>
  </tbody>
</table>

      </section>
      <section anchor="mc-registration" numbered="true" toc="default">
        <name>Multicast Address Registration</name>
        <t><!--
        <t>
   IANA has assigned -->
   IANA is asked to assign
	the following multicast addresses for use by CoAP nodes:</t>
        <t>IPv4  -- "all
	<dl newline="false" spacing="normal">
          <dt>IPv4</dt>
	  <dd>-- "All CoRE Resource Directories" address MCD2 (suggestion: 224.0.1.189), from 224.0.1.190, in the
	  "Internetwork Control Block (224.0.1.0 - 224.0.1.255 (224.0.1/24))"
	  subregistry within the "IPv4 Multicast Address Space Registry".  As
	  the address is used for discovery that may span beyond a single
	  network, it has come from the Internetwork Control Block (224.0.1.x)
	  <xref target="RFC5771" format="default"/>.</t>
        <t>IPv6  -- "all format="default"/>.</dd>
      <dt>IPv6</dt>
      <dd>-- "All CoRE Resource Directories" address MCD1 (suggestions FF0X::FE), from the "IPv6 Multicast
      Address Space Registry", ff0x::fe, in
      the "Variable Scope Multicast Addresses" space (RFC 3307). subregistry within the "IPv6
      Multicast Address Space Registry" <xref target="RFC3307"
      format="default"/>.  Note that there is a distinct multicast address for
      each scope that interested CoAP nodes should
listen to; CoAP needs the Link-Local
      link-local and Site-Local site-local scopes only.</t>
        <t>[ The RFC editor is asked to replace MCD1 and MCD2
with the assigned addresses throughout the document. ]</t> only.</dd>
    </dl>
      </section>

      <section anchor="well-known-uris" numbered="true" toc="default">
        <name>Well-Known URIs</name>
        <t>IANA is asked to permanently register
<!-- IANA has permanently registered --> the URI suffix "rd" in the "Well-Known URIs" registry.
The change controller is the IETF,
this document is the reference.</t>
        registry as follows: </t>

<table>
  <name>Addition to Well-Known URIs Registry</name>
  <thead>
    <tr>
      <th>URI Suffix</th>
      <th>Change Controller</th>
      <th>Reference</th>
      <th>Status</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>rd</td>
      <td>IETF</td>
      <td>RFC 9176</td>
      <td>permanent</td>
    </tr>
  </tbody>
</table>

      </section>
      <section anchor="service-names-and-transport-protocol-port-number-registry" numbered="true" toc="default">
        <name>Service Names Name and Transport Protocol Port Number Registry</name>
        <t>IANA is asked to enter has added four new items into to the "Service Name and Transport Protocol Port Number Registry" as follows:</t>

<table>
  <name>Additions to Service Names Name and Transport Protocol Port Number Registry:</t>
        <ul spacing="normal">
          <li>Service name: "core-rd",  Protocol: "udp", Description: "Resource Registry</name>
  <thead>
    <tr>
      <th>Service Name</th>
      <th>Transport Protocol</th>
      <th>Description</th>
      <th>Reference</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>core-rd</td>
      <td>udp</td>
      <td>Resource Directory accessed using CoAP"</li>
          <li>Service name "core-rd-dtls", Protocol: "udp", Description: "Resource CoAP</td>
      <td>RFC 9176</td>
    </tr>
    <tr>
      <td>core-rd-dtls</td>
      <td>udp</td>
      <td>Resource Directory accessed using CoAP over DTLS"</li>
          <li>Service name: "core-rd",  Protocol: "tcp", Description: "Resource DTLS</td>
      <td>RFC 9176</td>
    </tr>
    <tr>
      <td>core-rd</td>
      <td>tcp</td>
      <td>Resource Directory accessed using CoAP over TCP"</li>
          <li>Service name "core-rd-tls", Protocol: "tcp", Description: "Resource TCP</td>
      <td>RFC 9176</td>
    </tr>
    <tr>
      <td>core-rd-tls</td>
      <td>tcp</td>
      <td>Resource Directory accessed using CoAP over TLS"</li>
        </ul>
        <t>All in common have this document as their reference.</t> TLS</td>
      <td>RFC 9176</td>
    </tr>
  </tbody>
</table>

      </section>
    </section>
    <section anchor="examples" numbered="true" toc="default">
      <name>Examples</name>
      <t>Two examples are presented: a Lighting Installation lighting installation example in <xref target="lt-ex" format="default"/> and a LwM2M Lightweight M2M (LwM2M) example in <xref target="lwm2m-ex" format="default"/>.</t>
      <section anchor="lt-ex" numbered="true" toc="default">
        <name>Lighting Installation</name>
        <t>This example shows a simplified lighting installation which that makes use of
the RD with a CoAP interface to facilitate the installation and start-up startup of
the application code in the lights and sensors. In particular, the example
leads to the definition of a group and the enabling of the corresponding
multicast address address, as described in <xref target="groups" format="default"/>. No conclusions must be drawn on the realization of actual
installation or naming procedures, because the example only "emphasizes" emphasizes some of the issues
that may influence the use of the RD and does not pretend to be normative.</t>
        <section anchor="lt-in-ch" numbered="true" toc="default">
          <name>Installation Characteristics</name>
          <t>The example assumes that the installation is managed. That means that a Commissioning
Tool (CT) is used to authorize the addition of nodes, name them, and name
their services. The CT can be connected to the installation in many ways:
the CT can be part of the installation network, connected by WiFi Wi-Fi to the
installation network, or connected via GPRS link, or other connected by another method.</t>
          <t>It is assumed that there are two naming authorities for the installation:
(1) the network manager that is responsible for the correct operation of
the network and the connected interfaces, interfaces and (2) the lighting manager that
is responsible for the correct functioning of networked lights and sensors.
The result is the existence of two naming schemes coming from the two managing
entities.</t>
          <t>The example installation consists of one presence sensor, sensor and two luminaries,
luminary1 and luminary2, each with their own wireless interface. Each luminary
contains three lamps: left, right right, and middle. Each luminary is accessible
through one endpoint. For each lamp lamp, a resource exists to modify the settings
of a lamp in a luminary. The purpose of the installation is that the presence
sensor notifies the presence of persons to a group of lamps. The group of
lamps consists of: of the middle and left lamps of luminary1 and the right lamp of luminary2.</t>
          <t>Before commissioning by the lighting manager, the network is installed installed, and
access to the interfaces is proven to work by the network manager.</t>
          <t>At the moment of installation, the network under installation is not necessarily
connected to the DNS infrastructure. Therefore, SLAAC Stateless Address Autoconfiguration (SLAAC) IPv6 addresses are
assigned to CT, RD, luminaries luminaries, and the sensor.
The addresses shown in <xref target="interface-S" format="default"/> below stand in for these in the following examples.</t>
          <table anchor="interface-S" align="center">
            <name>Addresses used Used in the examples</name> Examples</name>
            <thead>
              <tr>
                <th align="left">Name</th>
                <th align="left">IPv6 address</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">luminary1</td>
                <td align="left">2001:db8:4::1</td>
              </tr>
              <tr>
                <td align="left">luminary2</td>
                <td align="left">2001:db8:4::2</td>
              </tr>
              <tr>
                <td align="left">Presence sensor</td>
                <td align="left">2001:db8:4::3</td>
              </tr>
              <tr>
                <td align="left">RD</td>
                <td align="left">2001:db8:4::ff</td>
              </tr>
            </tbody>
          </table>
          <t>In <xref target="rd-en" format="default"/> format="default"/>, the use of RD during installation is
presented.</t>
        </section>
        <section anchor="rd-en" numbered="true" toc="default">
          <name>RD entries</name> Entries</name>
          <t>It is assumed that access to the DNS infrastructure is not always possible
during installation. Therefore, the SLAAC addresses are used in this section.</t>
          <t>For discovery, the resource types (rt) of the devices are important. The
lamps in the luminaries have rt=tag:example.com,2020:light, and the presence sensor has rt=tag:example.com,2020:p-sensor.
The endpoints have names which that are relevant to the light installation manager.
In this case case, luminary1, luminary2, and the presence sensor are located in
room 2-4-015, where luminary1 is located at the window and luminary2 and
the presence sensor are located at the door. The endpoint names reflect
this physical location. The middle, left left, and right lamps are accessed via
path /light/middle, /light/left, and /light/right /light/right, respectively. The identifiers
relevant to the RD are shown in <xref target="endpoint" format="default"/> below:</t> format="default"/>.</t>
          <table anchor="endpoint" align="center">
            <name>RD identifiers</name> Identifiers</name>
            <thead>
              <tr>
                <th align="left">Name</th>
                <th align="left">endpoint</th> align="left">Endpoint</th>
                <th align="left">resource path</th> align="left">Resource Path</th>
                <th align="left">resource type</th> align="left">Resource Type</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">luminary1</td>
                <td align="left">lm_R2-4-015_wndw</td>
                <td align="left">/light/left</td>
                <td align="left">tag:example.com,2020:light</td>
              </tr>
              <tr>
                <td align="left">luminary1</td>
                <td align="left">lm_R2-4-015_wndw</td>
                <td align="left">/light/middle</td>
                <td align="left">tag:example.com,2020:light</td>
              </tr>
              <tr>
                <td align="left">luminary1</td>
                <td align="left">lm_R2-4-015_wndw</td>
                <td align="left">/light/right</td>
                <td align="left">tag:example.com,2020:light</td>
              </tr>
              <tr>
                <td align="left">luminary2</td>
                <td align="left">lm_R2-4-015_door</td>
                <td align="left">/light/left</td>
                <td align="left">tag:example.com,2020:light</td>
              </tr>
              <tr>
                <td align="left">luminary2</td>
                <td align="left">lm_R2-4-015_door</td>
                <td align="left">/light/middle</td>
                <td align="left">tag:example.com,2020:light</td>
              </tr>
              <tr>
                <td align="left">luminary2</td>
                <td align="left">lm_R2-4-015_door</td>
                <td align="left">/light/right</td>
                <td align="left">tag:example.com,2020:light</td>
              </tr>
              <tr>
                <td align="left">Presence sensor</td>
                <td align="left">ps_R2-4-015_door</td>
                <td align="left">/ps</td>
                <td align="left">tag:example.com,2020:p-sensor</td>
              </tr>
            </tbody>
          </table>
          <t>It is assumed that the CT has performed RD discovery and has received a response like the one in the example in <xref target="discovery" format="default"/> example.</t> format="default"/>.</t>
          <t>The CT inserts the endpoints of the luminaries and the sensor in the RD
using the registration base URI parameter (base) to specify the interface address:</t>
          <figure anchor="example-lighting-1">
            <name>Example of registrations Registrations a CT enters Enters into an RD</name>
            <artwork name="" type="" align="left" alt=""><![CDATA[
           <sourcecode type=""><![CDATA[
Req: POST coap://[2001:db8:4::ff]/rd
  ?ep=lm_R2-4-015_wndw&base=coap://[2001:db8:4::1]&d=R2-4-015
Payload:
</light/left>;rt="tag:example.com,2020:light",
</light/middle>;rt="tag:example.com,2020:light",
</light/right>;rt="tag:example.com,2020:light"

Res: 2.01 Created
Location-Path: /rd/4521

Req: POST coap://[2001:db8:4::ff]/rd
  ?ep=lm_R2-4-015_door&base=coap://[2001:db8:4::2]&d=R2-4-015
Payload:
</light/left>;rt="tag:example.com,2020:light",
</light/middle>;rt="tag:example.com,2020:light",
</light/right>;rt="tag:example.com,2020:light"

Res: 2.01 Created
Location-Path: /rd/4522

Req: POST coap://[2001:db8:4::ff]/rd
  ?ep=ps_R2-4-015_door&base=coap://[2001:db8:4::3]&d=R2-4-015
Payload:
</ps>;rt="tag:example.com,2020:p-sensor"

Res: 2.01 Created
Location-Path: /rd/4523
]]></artwork>
]]></sourcecode>
          </figure>
          <t>The sector name d=R2-4-015 has been added for an efficient lookup because
filtering on the "ep" name is more awkward. The same sector name is communicated to
the two luminaries and the presence sensor by the CT.</t>
          <t>The group is specified in the RD. The base parameter is set to the site-local
multicast address allocated to the group.
In the POST in the example below, the resources supported by all group members are published.</t>
          <figure anchor="example-lighting-2">
            <name>Example of a multicast group Multicast Group a CT enters Enters into an RD</name>
            <artwork name="" type="" align="left" alt=""><![CDATA[
           <sourcecode type=""><![CDATA[
Req: POST coap://[2001:db8:4::ff]/rd
  ?ep=grp_R2-4-015&et=core.rd-group&base=coap://[ff05::1]
Payload:
</light/left>;rt="tag:example.com,2020:light",
</light/middle>;rt="tag:example.com,2020:light",
</light/right>;rt="tag:example.com,2020:light"

Res: 2.01 Created
Location-Path: /rd/501
]]></artwork>
]]></sourcecode>
          </figure>
          <t>After the filling of the RD by the CT, the application in the luminaries
can learn to which groups they belong, belong and enable their interface for the
multicast address.</t>
          <t>The luminary, knowing its sector and being configured to join any group
containing lights, searches for candidate groups and joins them:</t>
          <figure anchor="example-lighting-3">
            <name>Example of a lookup exchange Lookup Exchange to find suitable multicast addresses</name>
            <artwork name="" type="" align="left" alt=""><![CDATA[ Find Suitable Multicast Addresses</name>
           <sourcecode type=""><![CDATA[
Req: GET coap://[2001:db8:4::ff]/rd-lookup/ep
  ?d=R2-4-015&et=core.rd-group&rt=light

Res: 2.05 Content
Payload:
</rd/501>;ep=grp_R2-4-015;et=core.rd-group;
          base="coap://[ff05::1]";rt=core.rd-ep
]]></artwork>
]]></sourcecode>
          </figure>
          <t>From the returned base parameter value, the luminary learns the multicast address
of the multicast group.</t>
          <t>The presence sensor can learn the presence of groups that support resources with rt=tag:example.com,2020:light in its own sector by sending the same request, as used by the luminary. The presence sensor learns the multicast address to use for sending messages to the luminaries.</t>
        </section>
      </section>
      <section anchor="lwm2m-ex" numbered="true" toc="default">
        <name>OMA Lightweight M2M (LwM2M)</name>
        <t>OMA LwM2M is a profile for device services based on CoAP, providing interfaces and operations for device management and device service enablement.</t>
        <t>An LwM2M server is an instance of an LwM2M middleware service layer, containing an RD (<xref target="LwM2M" format="default"/> format="default"/>, starting at page 36f).</t> 36).</t>
        <t>That RD only implements the registration interface, and no lookup is implemented.
Instead, the LwM2M server provides access to the registered resources, resources in a similar way to a reverse proxy.</t>
        <t>The location of the LwM2M Server server and RD URI path is provided by the LwM2M Bootstrap bootstrap process, so no dynamic discovery of the RD is used. LwM2M Servers servers and endpoints are not required to implement the /.well-known/core <tt>/.well-known/core</tt> resource.</t>
      </section>
    </section>
    <section anchor="acknowledgments" numbered="true" toc="default">
      <name>Acknowledgments</name>
      <t>Oscar Novo, Srdjan Krco, Szymon Sasin, Kerry Lynn, Esko Dijk, Anders
Brandt, Matthieu Vial, Jim Schaad, Mohit Sethi, Hauke Petersen, Hannes Tschofenig, Sampo Ukkola, Linyi
Tian, Jan Newmarch, Matthias Kovatsch, Jaime Jimenez and Ted Lemon have provided helpful comments, discussions and ideas to improve and
shape this document. Zach would also like to thank his colleagues from the
EU FP7 SENSEI project, where many of the RD concepts were
originally developed.</t>
    </section>
    <section anchor="changelog" numbered="true" toc="default">
      <name>Changelog</name>
      <t>changes from -27 to -28</t>
      <ul spacing="normal">
        <li>Security policies / link confidentiality: Point out the RD's obligations that follow from such a policy.</li>
        <li>Simple registration: clarify term "regular registration" by introducing it along with the reference to <xref target="registration" format="default"/></li>
        <li>Wording fix in first-come-first-remembered</li>
        <li>Wording fixes in RD definition</li>
        <li>Capitalization: Consistently using "registration resource"</li>
      </ul>
      <t>changes from -26 to -27</t>
      <ul spacing="normal">
        <li>In general, this addresses the points that were pointed out in
https://mailarchive.ietf.org/arch/msg/core/xWLomwwhovkU-CPGNxnvs40BhaM/ as
having "evolved from the review comments being discussed in the interim
meetings", and the review comments from Esko Dijk that were largely entangled
in these points.</li>
        <li>
          <t>Relaxation of the serialization rules for link-format  </t>
          <t>
The interpretation of RFC6690 used in <xref target="resolution-rules" format="default"/> was shown to be faulty.
Along with a correction, the common implementations of link-format were surveyed again
and it was found that the only one that employed the faulty interpretation can still safely be upgraded.
These were removed from the set considered for Limited Link Format,
making the set of valid Limited Link Format documents larger.  </t>
          <t>
As a consequence, the prescribed serialization of RD output can be roughly halved in bytes.  </t>
          <t>
There might be additional usage patterns that are possible with the new set of constraints,
but there is insufficient implementation and deployment experience with them to warrant a change changes on that front at this point.
The specification can later be extended compatibly to allow these cases and drop the requirement of Limited Link Format.</t>
        </li>
        <li>
          <t>Add Request freshness subsection  </t>
          <t>
It is now recommended (with security considerations on consequences of not doing it) to require ordering of RD operations.  </t>
          <t>
The Echo mechanism (previously suggested in various places but never exclusively) is the one prescribed way of getting this ordering,
making the echo-request-tag reference normative.</t>
        </li>
        <li>
          <t>Improved expression about when an RD needs to verify simple registration.  </t>
          <t>
The simple wording missed the authorization part, and did not emphasize that this is a per-deployment property.</t>
        </li>
        <li>Point out the non-atomic properties of paginated access.</li>
        <li>Clarification around impl-info reference.</li>
        <li>Inconsistencies and extraneous quotings removed from examples.</li>
      </ul>
      <t>changes from -25 to -26</t>
      <ul spacing="normal">
        <li>
          <t>Security policies:
          </t>
          <ul spacing="normal">
            <li>The First-Come-First-Remembered policy is added as an example and a potential default behavior.</li>
            <li>Clarify that the mapping between endpoint names and subject fields is up to a policy that defines reliance on names, and give an example.</li>
            <li>Random EP names: Point that multiple collisions are possible but unlikely.</li>
            <li>
              <t>Add pointers to policies:
              </t>
              <ul spacing="normal">
                <li>RD replication: Point out that policies may limit that.</li>
                <li>Registration: Reword (ep, d) mapping to a previous registration's resource that could have been read as another endpoint taking over an existing registration.</li>
              </ul>
            </li>
            <li>Clarify that the security policy is a property of the RD the any client may need to verify by checking the RD's authorization.</li>
            <li>Clarify how information from an untrusted RD can be verified</li>
            <li>Remove speculation about how in detail ACE scopes are obtained.</li>
          </ul>
        </li>
        <li>
          <t>Security considerations:
          </t>
          <ul spacing="normal">
            <li>Generalize to all current options for security layers usable with CoAP (OSCORE was
missing as the text predated RFC8613)</li>
            <li>Relax the previous SHOULD on secure access to SHOULD where protection is indicated by security policies
(bringing the text in line with the -25 changes)</li>
            <li>Point out that failure to follow the security considerations has implications depending on the protection objective described with the security policies</li>
            <li>Shorten amplification mitigation</li>
            <li>Add note about information in Registration Resource path.</li>
            <li>Acknowledge that most host discovery operations are not secured; mention consequences and mitigation.</li>
          </ul>
        </li>
        <li>Abstract, introduction: removed "or disperse networks"</li>
        <li>
          <t>RD discovery:
          </t>
          <ul spacing="normal">
            <li>Drop the previously stated assumption that RDAO and any DHCP options would only be used together with SLAAC and DHCP for address configuration, respectivly.</li>
            <li>Give concrete guidance for address selection based on RFC6724 when responding to multicasts</li>
            <li>
              <t>RDAO:
              </t>
              <ul spacing="normal">
                <li>Clarify that it is an option for RAs and not other ND messages.</li>
                <li>Change Lifetime from 16-bit minutes to 32-bit seconds and swap it with Reserved (aligning it with RDNSS which it shares other properties as well).</li>
              </ul>
            </li>
            <li>Point out that clients may need to check RD authorization already in last discovery step</li>
          </ul>
        </li>
        <li>
          <t>Registration:
          </t>
          <ul spacing="normal">
            <li>Wording around "mostly mandatory" has been improved, conflicts clarified and sector default selection adjusted.</li>
          </ul>
        </li>
        <li>Simple registration: Rather than coopting POSTs to /.well-known/core, a new resource /.well-known/rd is registered.
A historical note in the text documents the change.</li>
        <li>
          <t>Examples:
          </t>
          <ul spacing="normal">
            <li>Use example URIs rather than unclear reg names (unless it's RFC6690 examples, which were kept for continuity)</li>
            <li>The LwM2M example was reduced from an outdated explanation of the complete LwM2M model to a summary of how RD is used in there, with a reference to the current specification.</li>
            <li>Luminary example: Explain example addresses</li>
            <li>Luminary example: Drop reference to coap-group mechanism that's becoming obsolete, and thus also to RFC7390</li>
            <li>Multicast addresses in the examples were changed from ff35:30:2001:db8::x to ff35:30:2001:db8:f1::8000:x; the 8000 is to follow RFC 3307, and the f1 is for consistency with all the other example addresses where 2001:db8::/32 is subnetted to 2001:db8:x::/48 by groups of internally consistent examples.</li>
          </ul>
        </li>
        <li>
          <t>Use case text enhancements
          </t>
          <ul spacing="normal">
            <li>Home and building automation: Tie in with RD</li>
            <li>M2M: Move system design paragraph towards the topic of reusability.</li>
          </ul>
        </li>
        <li>Various editorial fixes in response to Gen-ART and IESG reviews.</li>
        <li>Rename 'Full description of the "Endpoint Type" Registration Parameter' section to '... RD Parameter'</li>
        <li>Error handling: Place a SHOULD around the likely cases, and make the previous "MUST to the best of their capabilities" a "must".</li>
        <li>impl-info: Add note about the type being WIP</li>
        <li>Interaction tables: list CTs as possible initiators where applicable</li>
        <li>Registration update: Relax requirement to not send parameters needlessly</li>
        <li>Terminology: Clarify that the CTs' installation events can occur multiple times.</li>
        <li>Promote RFCs 7252, 7230 and 8288 to normative references</li>
        <li>Moved Christian Amsuess to first author</li>
      </ul>
      <t>changes from -24 to -25</t>
      <ul spacing="normal">
        <li>
          <t>Large rework of section 7 (Security policies)  </t>
          <t>
Rather than prescribing which data in the RD <em>is</em> authenticated (and how),
it now describes what applications built on an RD <em>can</em> choose to authenticate,
show possibilities on how to do it and outline what it means for clients.  </t>
          <t>
This addresses Russ' Genart review points on details in the text in a rather broad fashion.
That is because the discussion on the topic inside the WG showed that that text on security has been driven more review-by-review than by an architectural plan of the authors and WG.</t>
        </li>
        <li>Add concrete suggestions (twice as long as registrant number with retries, or UUIDs without) for random endpoint names</li>
        <li>Point out that simple registration can have faked origins,
RECOMMEND mitigation when applicable
and suggest the Echo mechanism to implement it.</li>
        <li>Reference existing and upcoming specifications for DDOS mitigation in CoAP.</li>
        <li>Explain the provenance of the example's multicast address.</li>
        <li>Make "SHOULD" of not manipulating foreign registrations a "should" and explain how it is enforced</li>
        <li>Clarify application of RFC6570 to search parameters</li>
        <li>Syntactic fixes in examples</li>
        <li>
          <t>IANA:
          </t>
          <ul spacing="normal">
            <li>Don't announce expected number of registrations (goes to write-up)</li>
            <li>Include syntax as part of a field's validity in entry requirements</li>
          </ul>
        </li>
        <li>
          <t>Editorial changes
          </t>
          <ul spacing="normal">
            <li>Align wording between abstract and introduction</li>
            <li>Abbreviation normalization: "ER model", "RD"</li>
            <li>RFC8174 boilerplate update</li>
            <li>Minor clarity fixes</li>
            <li>Markup and layouting</li>
          </ul>
        </li>
      </ul>
      <t>changes from -23 to -24</t>
      <ul spacing="normal">
        <li>Discovery using DNS-SD added again</li>
        <li>Minimum lifetime (lt) reduced from 60 to 1</li>
        <li>References added</li>
        <li>
          <t>IANA considerations
          </t>
          <ul spacing="normal">
            <li>added about .well-known/core resource</li>
            <li>added DNS-SD service names</li>
            <li>made RDAO option number a suggestion</li>
            <li>added "reference" field to endpoint type registry</li>
          </ul>
        </li>
        <li>Lookup: mention that anchor is a legitimate lookup attribute</li>
        <li>Terminology and example fixes</li>
        <li>Layout fixes, esp. the use of non-ASCII characters in figures</li>
      </ul>
      <t>changes from -22 to -23</t>
      <ul spacing="normal">
        <li>Explain that updates can not remove attributes</li>
        <li>Typo fixes</li>
      </ul>
      <t>changes from -21 to -22</t>
      <ul spacing="normal">
        <li>Request a dedicated IPv4 address from IANA (rather than sharing with All CoAP nodes)</li>
        <li>Fix erroneous examples</li>
        <li>
          <t>Editorial changes
          </t>
          <ul spacing="normal">
            <li>Add figure numbers to examples</li>
            <li>Update RD parameters table to reflect changes of earlier versions in the text</li>
            <li>Typos and minor wording</li>
          </ul>
        </li>
      </ul>
      <t>changes from -20 to -21</t>
      <t>(Processing comments during WGLC)</t>
      <ul spacing="normal">
        <li>Defer outdated description of using DNS-SD to find an RD to the defining document</li>
        <li>Describe operational conditions in automation example</li>
        <li>Recommend particular discovery mechanisms for some managed network scenarios</li>
      </ul>
      <t>changes from -19 to -20</t>
      <t>(Processing comments from the WG chair review)</t>
      <ul spacing="normal">
        <li>Define the permissible characters in endpoint and sector names</li>
        <li>Express requirements on NAT situations in more abstract terms</li>
        <li>Shifted heading levels to have the interfaces on the same level</li>
        <li>Group instructions for error handling into general section</li>
        <li>Simple Registration: process reflowed into items list</li>
        <li>Updated introduction to reflect state of CoRE in general, reference RFC7228
(defining "constrained") and use "IoT" term in addition to "M2M"</li>
        <li>Update acknowledgements</li>
        <li>
          <t>Assorted editorial changes
          </t>
          <ul spacing="normal">
            <li>Unify examples style</li>
            <li>Terminology: RDAO defined and not only expanded</li>
            <li>Add CT to <xref target="fig-arch" format="default"/></li>
            <li>Consistency in the use of the term "Content Format"</li>
          </ul>
        </li>
      </ul>
      <t>changes from -18 to -19</t>
      <ul spacing="normal">
        <li>link-local addresses: allow but prescribe split-horizon fashion when used,
disallow zone identifiers</li>
        <li>Remove informative references to documents not mentioned any more</li>
      </ul>
      <t>changes from -17 to -18</t>
      <ul spacing="normal">
        <li>Rather than re-specifying link format (Modernized Link Format), describe a
Limited Link Format that's the uncontested subset of Link Format</li>
        <li>Acknowledging the -17 version as part of the draft</li>
        <li>Move "Read endpoint links" operation to future specification like PATCH</li>
        <li>Demote links-json to an informative reference, and removed them from exchange
examples</li>
        <li>Add note on unusability of link-local IP addresses, and describe mitigation.</li>
        <li>Reshuffling of sections: Move additional operations and endpoint lookup back
from appendix, and groups into one</li>
        <li>Lookup interface tightened to not imply applicability for non link-format
lookups (as those can have vastly different views on link cardinality)</li>
        <li>Simple registration: Change sequence of GET and POST-response, ensuring
unsuccessful registrations are reported as such, and suggest how devices that
would have required the inverse behavior can still cope with it.</li>
        <li>Abstract and introduction reworded to avoid the impression that resources are
stored in full in the RD</li>
        <li>Simplify the rules governing when a registration resource can or must be
changed.</li>
        <li>Drop a figure that has become useless due to the changes of and -13 and -17</li>
        <li>Wording consistency fixes: Use "Registrations" and "target attributes"</li>
        <li>Fix incorrect use of content negotiation in discovery interface description
(Content-Format -&gt; Accept)</li>
        <li>State that the base attribute value is part of endpoint lookup even when
implicit in the registration</li>
        <li>Update references from RFC5988 to its update RFC8288</li>
        <li>Remove appendix on protocol-negotiation (which had a note to be removed
before publication)</li>
      </ul>
      <t>changes from -16 to -17</t>
      <t>(Note that -17 is published as a direct follow-up to -16, containing a single change to be discussed at IETF103)</t>
      <ul spacing="normal">
        <li>Removed groups that are enumerations of registrations and have dedicated mechanism</li>
        <li>Add groups that are enumerations of shared resources and are a special case of endpoint registrations</li>
      </ul>
      <t>changes from -15 to -16</t>
      <ul spacing="normal">
        <li>Recommend a common set of resources for members of a group</li>
        <li>Clarified use of multicast group in lighting example</li>
        <li>Add note on concurrent registrations from one EP being possible but not expected</li>
        <li>Refresh web examples appendix to reflect current use of Modernized Link Format</li>
        <li>Add examples of URIs where Modernized Link Format matters</li>
        <li>Editorial changes</li>
      </ul>
      <t>changes from -14 to -15</t>
      <ul spacing="normal">
        <li>Rewrite of section "Security policies"</li>
        <li>Clarify that the "base" parameter text applies both to relative references
both in anchor and href</li>
        <li>Renamed "Registree-EP" to  Registrant-EP"</li>
        <li>Talk of "relative references" and "URIs" rather than "relative" and
"absolute" URIs. (The concept of "absolute URIs" of <xref target="RFC3986" format="default"/> is not needed in RD).</li>
        <li>Fixed examples</li>
        <li>Editorial changes</li>
      </ul>
      <t>changes from -13 to -14</t>
      <ul spacing="normal">
        <li>Rename "registration context" to "registration base URI" (and "con" to
"base") and "domain" to "sector" (where the abbreviation "d" stays for
compatibility reasons)</li>
        <li>Introduced resource types core.rd-ep and core.rd-gp</li>
        <li>Registration management moved to appendix A, including endpoint and group lookup</li>
        <li>
          <t>Minor editorial changes
          </t>
          <ul spacing="normal">
            <li>PATCH/iPATCH is clearly deferred to another document</li>
            <li>Recommend against query / fragment identifier in con=</li>
            <li>Interface description lists are described as illustrative</li>
            <li>Rewording of Simple Registration</li>
          </ul>
        </li>
        <li>Simple registration carries no error information and succeeds immediately (previously, sequence was unspecified)</li>
        <li>Lookup: href are matched against resolved values (previously, this was unspecified)</li>
        <li>Lookup: lt are not exposed any more</li>
        <li>con/base: Paths are allowed</li>
        <li>Registration resource locations can not have query or fragment parts</li>
        <li>Default life time extended to 25 hours</li>
        <li>clarified registration update rules</li>
        <li>lt-value semantics for lookup clarified.</li>
        <li>added template for simple registration</li>
      </ul>
      <t>changes from -12 to -13</t>
      <ul spacing="normal">
        <li>Added "all resource directory" nodes MC address</li>
        <li>Clarified observation behavior</li>
        <li>version identification</li>
        <li>example rt= and et= values</li>
        <li>domain from figure 2</li>
        <li>more explanatory text</li>
        <li>endpoints of a groups hosted by different RD</li>
        <li>
          <t>resolve RFC6690-vs-8288 resolution ambiguities:
          </t>
          <ul spacing="normal">
            <li>require registered links not to be relative when using anchor</li>
            <li>return absolute URIs in resource lookup</li>
          </ul>
        </li>
      </ul>
      <t>changes from -11 to -12</t>
      <ul spacing="normal">
        <li>added Content Model section, including ER diagram</li>
        <li>removed domain lookup interface; domains are now plain attributes of groups and endpoints</li>
        <li>updated chapter "Finding a Resource Directory"; now distinguishes configuration-provided, network-provided and heuristic sources</li>
        <li>improved text on: atomicity, idempotency, lookup with multiple parameters, endpoint removal, simple registration</li>
        <li>updated LWM2M description</li>
        <li>clarified where relative references are resolved, and how context and anchor interact</li>
        <li>new appendix on the interaction with RFCs 6690, 5988 and 3986</li>
        <li>lookup interface: group and endpoint lookup return group and registration resources as link targets</li>
        <li>lookup interface: search parameters work the same across all entities</li>
        <li>removed all methods that modify links in an existing registration (POST with payload, PATCH and iPATCH)</li>
        <li>removed plurality definition (was only needed for link modification)</li>
        <li>enhanced IANA registry text</li>
        <li>state that lookup resources can be observable</li>
        <li>More examples and improved text</li>
      </ul>
      <t>changes from -09 to -10</t>
      <ul spacing="normal">
        <li>removed "ins" and "exp" link-format extensions.</li>
        <li>removed all text concerning DNS-SD.</li>
        <li>removed inconsistency in RDAO text.</li>
        <li>suggestions taken over from various sources</li>
        <li>replaced "Function Set" with "REST API", "base URI", "base path"</li>
        <li>moved simple registration to registration section</li>
      </ul>
      <t>changes from -08 to -09</t>
      <ul spacing="normal">
        <li>clarified the "example use" of the base RD resource values /rd, /rd-lookup, and /rd-group.</li>
        <li>changed "ins" ABNF notation.</li>
        <li>various editorial improvements, including in examples</li>
        <li>clarifications for RDAO</li>
      </ul>
      <t>changes from -07 to -08</t>
      <ul spacing="normal">
        <li>removed link target value returned from domain and group lookup types</li>
        <li>Maximum length of domain parameter 63 bytes for consistency with group</li>
        <li>removed option for simple POST of link data, don't require a .well-known/core resource to accept POST data and handle it in a special way; we already have /rd for that</li>
        <li>add IPv6 ND Option for discovery of an RD</li>
        <li>clarify group configuration section 6.1 that endpoints must be registered before including them in a group</li>
        <li>removed all superfluous client-server diagrams</li>
        <li>simplified lighting example</li>
        <li>introduced Commissioning Tool</li>
        <li>RD-Look-up text is extended.</li>
      </ul>
      <t>changes from -06 to -07</t>
      <ul spacing="normal">
        <li>added text in the discovery section to allow content format hints to be exposed in the discovery link attributes</li>
        <li>editorial updates to section 9</li>
        <li>update author information</li>
        <li>minor text corrections</li>
      </ul>
      <t>Changes from -05 to -06</t>
      <ul spacing="normal">
        <li>added note that the PATCH section is contingent on the progress of
the PATCH method</li>
      </ul>
      <t>changes from -04 to -05</t>
      <ul spacing="normal">
        <li>added Update Endpoint Links using PATCH</li>
        <li>http access made explicit in interface specification</li>
        <li>Added http examples</li>
      </ul>
      <t>Changes from -03 to -04:</t>
      <ul spacing="normal">
        <li>Added http response codes</li>
        <li>Clarified endpoint name usage</li>
        <li>Add application/link-format+cbor content-format</li>
      </ul>
      <t>Changes from -02 to -03:</t>
      <ul spacing="normal">
        <li>Added an example for lighting and DNS integration</li>
        <li>Added an example for RD use in OMA LWM2M</li>
        <li>Added Read Links operation for link inspection by endpoints</li>
        <li>Expanded DNS-SD section</li>
        <li>Added draft authors Peter van der Stok and Michael Koster</li>
      </ul>
      <t>Changes from -01 to -02:</t>
      <ul spacing="normal">
        <li>Added a catalogue use case.</li>
        <li>Changed the registration update to a POST with optional link format payload. Removed the endpoint type update from the update.</li>
        <li>Additional examples section added for more complex use cases.</li>
        <li>New DNS-SD mapping section.</li>
        <li>Added text on endpoint identification and authentication.</li>
        <li>Error code 4.04 added to Registration Update and Delete requests.</li>
        <li>Made 63 bytes a SHOULD rather than a MUST for endpoint name and resource type parameters.</li>
      </ul>
      <t>Changes from -00 to -01:</t>
      <ul spacing="normal">
        <li>Removed the ETag validation feature.</li>
        <li>Place holder for the DNS-SD mapping section.</li>
        <li>Explicitly disabled GET or POST on returned Location.</li>
        <li>New registry for RD parameters.</li>
        <li>Added support for the JSON Link Format.</li>
        <li>Added reference to the Groupcomm WG draft.</li>
      </ul>
      <t>Changes from -05 to WG Document -00:</t>
      <ul spacing="normal">
        <li>Updated the version and date.</li>
      </ul>
      <t>Changes from -04 to -05:</t>
      <ul spacing="normal">
        <li>Restricted Update to parameter updates.</li>
        <li>Added pagination support for the Lookup interface.</li>
        <li>Minor editing, bug fixes and reference updates.</li>
        <li>Added group support.</li>
        <li>Changed rt to et for the registration and update interface.</li>
      </ul>
      <t>Changes from -03 to -04:</t>
      <ul spacing="normal">
        <li>Added the ins= parameter back for the DNS-SD mapping.</li>
        <li>Integrated the Simple Directory Discovery from Carsten.</li>
        <li>Editorial improvements.</li>
        <li>Fixed the use of ETags.</li>
        <li>Fixed tickets 383 and 372</li>
      </ul>
      <t>Changes from -02 to -03:</t>
      <ul spacing="normal">
        <li>Changed the endpoint name back to a single registration parameter ep= and removed the h= and ins= parameters.</li>
        <li>Updated REST interface descriptions to use RFC6570 URI Template format.</li>
        <li>Introduced an improved RD Lookup design as its own function set.</li>
        <li>Improved the security considerations section.</li>
        <li>Made the POST registration interface idempotent by requiring the ep= parameter to be present.</li>
      </ul>
      <t>Changes from -01 to -02:</t>
      <ul spacing="normal">
        <li>Added a terminology section.</li>
        <li>Changed the inclusion of an ETag in registration or update to a MAY.</li>
        <li>Added the concept of an RD Domain and a registration parameter for it.</li>
        <li>Recommended the Location returned from a registration to be stable, allowing for endpoint and Domain information to be changed during updates.</li>
        <li>Changed the lookup interface to accept endpoint and Domain as query string parameters to control the scope of a lookup.</li>
      </ul>
    </section>
  </middle>
  <back>

<displayreference target="I-D.silverajan-core-coap-protocol-negotiation" to="COAP-PROT-NEG"/>
<displayreference target="I-D.ietf-ace-oauth-authz" to="ACE-OAUTH-AUTHZ"/>
<displayreference target="I-D.ietf-core-links-json" to="CORE-LINKS-JSON"/>
<displayreference target="I-D.ietf-core-rd-dns-sd" to="CORE-RD-DNS-SD"/>
<displayreference target="I-D.bormann-t2trg-rel-impl" to="T2TRG-REL-IMPL"/>
<displayreference target="I-D.ietf-core-coral" to="CORE-CORAL"/>

    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
        <reference anchor="RFC6690" target="https://www.rfc-editor.org/info/rfc6690">
          <front>
            <title>Constrained RESTful Environments (CoRE) Link Format</title>
            <seriesInfo name="DOI" value="10.17487/RFC6690"/>
            <seriesInfo name="RFC" value="6690"/>
            <author fullname="Z. Shelby" initials="Z." surname="Shelby">
              <organization/>
            </author>
            <date month="August" year="2012"/>
            <abstract>
              <t>This specification defines Web Linking using a link format for use by constrained web servers to describe hosted resources, their attributes, and other relationships between links.  Based on the HTTP Link Header field defined in RFC 5988, the Constrained RESTful Environments (CoRE) Link Format is carried as a payload and is assigned an Internet media type.  "RESTful" refers to the Representational State Transfer (REST) architecture.  A well-known URI is defined as a default entry point for requesting the links hosted by a server.  [STANDARDS-TRACK]</t>
            </abstract>
          </front>
        </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>
            <seriesInfo name="DOI" value="10.17487/RFC2119"/>
            <seriesInfo name="RFC" value="2119"/>
            <seriesInfo name="BCP" value="14"/>
            <author fullname="S. Bradner" initials="S." surname="Bradner">
              <organization/>
            </author>
            <date month="March" year="1997"/>
            <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>
        </reference>
        <reference anchor="RFC3986" target="https://www.rfc-editor.org/info/rfc3986">
          <front>
            <title>Uniform Resource Identifier (URI): Generic Syntax</title>
            <seriesInfo name="DOI" value="10.17487/RFC3986"/>
            <seriesInfo name="RFC" value="3986"/>
            <seriesInfo name="STD" value="66"/>
            <author fullname="T. Berners-Lee" initials="T." surname="Berners-Lee">
              <organization/>
            </author>
            <author fullname="R. Fielding" initials="R." surname="Fielding">
              <organization/>
            </author>
            <author fullname="L. Masinter" initials="L." surname="Masinter">
              <organization/>
            </author>
            <date month="January" year="2005"/>
            <abstract>
              <t>A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource.  This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet.  The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier.  This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme.  [STANDARDS-TRACK]</t>
            </abstract>
          </front>
        </reference>
        <reference anchor="RFC8126" target="https://www.rfc-editor.org/info/rfc8126">
          <front>
            <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
            <seriesInfo name="DOI" value="10.17487/RFC8126"/>
            <seriesInfo name="RFC" value="8126"/>
            <seriesInfo name="BCP" value="26"/>
            <author fullname="M. Cotton" initials="M." surname="Cotton">
              <organization/>
            </author>
            <author fullname="B. Leiba" initials="B." surname="Leiba">
              <organization/>
            </author>
            <author fullname="T. Narten" initials="T." surname="Narten">
              <organization/>
            </author>
            <date month="June" year="2017"/>
            <abstract>
              <t>Many protocols make use of points of extensibility that use constants to identify various protocol parameters.  To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper.  For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA).</t>
              <t>To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed.  This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry.</t>
              <t>This is the third edition of this document; it obsoletes RFC 5226.</t>
            </abstract>
          </front>
        </reference>
        <reference anchor="RFC6570" target="https://www.rfc-editor.org/info/rfc6570">
          <front>
            <title>URI Template</title>
            <seriesInfo name="DOI" value="10.17487/RFC6570"/>
            <seriesInfo name="RFC" value="6570"/>
            <author fullname="J. Gregorio" initials="J." surname="Gregorio">
              <organization/>
            </author>
            <author fullname="R. Fielding" initials="R." surname="Fielding">
              <organization/>
            </author>
            <author fullname="M. Hadley" initials="M." surname="Hadley">
              <organization/>
            </author>
            <author fullname="M. Nottingham" initials="M." surname="Nottingham">
              <organization/>
            </author>
            <author fullname="D. Orchard" initials="D." surname="Orchard">
              <organization/>
            </author>
            <date month="March" year="2012"/>
            <abstract>
              <t>A URI Template is a compact sequence of characters for describing a range of Uniform Resource Identifiers through variable expansion. This specification defines the URI Template syntax and the process for expanding a URI Template into a URI reference, along with guidelines for the use of URI Templates on the Internet.   [STANDARDS-TRACK]</t>
            </abstract>
          </front>
        </reference>
        <reference anchor="RFC6763" target="https://www.rfc-editor.org/info/rfc6763">
          <front>
            <title>DNS-Based Service Discovery</title>
            <seriesInfo name="DOI" value="10.17487/RFC6763"/>
            <seriesInfo name="RFC" value="6763"/>
            <author fullname="S. Cheshire" initials="S." surname="Cheshire">
              <organization/>
            </author>
            <author fullname="M. Krochmal" initials="M." surname="Krochmal">
              <organization/>
            </author>
            <date month="February" year="2013"/>
            <abstract>
              <t>This document specifies how DNS resource records are named and structured to facilitate service discovery.  Given a type of service that a client is looking for, and a domain in which the client is looking for that service, this mechanism allows clients to discover a list of named instances of that desired service, using standard DNS queries. This mechanism is referred to as DNS-based Service Discovery, or DNS-SD.</t>
            </abstract>
          </front>
        </reference>
        <reference anchor="RFC7230" target="https://www.rfc-editor.org/info/rfc7230">
          <front>
            <title>Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</title>
            <seriesInfo name="DOI" value="10.17487/RFC7230"/>
            <seriesInfo name="RFC" value="7230"/>
            <author fullname="R. Fielding" initials="R." role="editor" surname="Fielding">
              <organization/>
            </author>
            <author fullname="J. Reschke" initials="J." role="editor" surname="Reschke">
              <organization/>
            </author>
            <date month="June" year="2014"/>
            <abstract>
              <t>The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems.  This document provides an overview of HTTP architecture and its associated terminology, defines the "http" and "https" Uniform Resource Identifier (URI) schemes, defines the HTTP/1.1 message syntax and parsing requirements, and describes related security concerns for implementations.</t>
            </abstract>
          </front>
        </reference>
        <reference anchor="RFC7252" target="https://www.rfc-editor.org/info/rfc7252">
          <front>
            <title>The Constrained Application Protocol (CoAP)</title>
            <seriesInfo name="DOI" value="10.17487/RFC7252"/>
            <seriesInfo name="RFC" value="7252"/>
            <author fullname="Z. Shelby" initials="Z." surname="Shelby">
              <organization/>
            </author>
            <author fullname="K. Hartke" initials="K." surname="Hartke">
              <organization/>
            </author>
            <author fullname="C. Bormann" initials="C." surname="Bormann">
              <organization/>
            </author>
            <date month="June" year="2014"/>
            <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>
        </reference>
        <reference anchor="RFC8288" target="https://www.rfc-editor.org/info/rfc8288">
          <front>
            <title>Web Linking</title>
            <seriesInfo name="DOI" value="10.17487/RFC8288"/>
            <seriesInfo name="RFC" value="8288"/>
            <author fullname="M. Nottingham" initials="M." surname="Nottingham">
              <organization/>
            </author>
            <date month="October" year="2017"/>
            <abstract>
              <t>This specification defines a model for the relationships between resources on the Web ("links") and the type of those relationships ("link relation types").</t>
              <t>It also defines the serialisation of such links in HTTP headers with the Link header field.</t>
            </abstract>
          </front>
        </reference>
        <reference anchor="I-D.ietf-core-echo-request-tag" target="https://www.ietf.org/archive/id/draft-ietf-core-echo-request-tag-12.txt">
          <front>
            <title>CoAP: Echo, Request-Tag, and Token Processing</title>
            <seriesInfo name="Internet-Draft" value="draft-ietf-core-echo-request-tag-12"/>
            <author fullname="Christian Amsüss">
	 </author>
            <author fullname="John Preuß Mattsson">
              <organization>Ericsson AB</organization>
            </author>
            <author fullname="Göran Selander">
              <organization>Ericsson AB</organization>
            </author>
            <date day="1" month="February" year="2021"/>
            <abstract>
              <t>   This document specifies enhancements to the Constrained Application
   Protocol (CoAP) that mitigate security issues in particular use
   cases.  The Echo option enables a CoAP server to verify the freshness
   of a request or to force a client to demonstrate reachability at its
   claimed network address.  The Request-Tag option allows the CoAP
   server to match block-wise message fragments belonging to the same
   request.  This document updates RFC7252 with respect to the client
   Token processing requirements, forbidding non-secure reuse of Tokens
   to ensure binding of response to request when CoAP is used with a
   security protocol, and with respect to amplification mitigation,
   where the use of Echo is now recommended.

              </t>
            </abstract>
          </front>
        </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>
            <seriesInfo name="DOI" value="10.17487/RFC8174"/>
            <seriesInfo name="RFC" value="8174"/>
            <seriesInfo name="BCP" value="14"/>
            <author fullname="B. Leiba" initials="B." surname="Leiba">
              <organization/>
            </author>
            <date month="May" year="2017"/>
            <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>
        </reference>

<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6690.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.3986.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6570.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6763.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7230.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.8288.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.9175.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>

      </references>
      <references>
        <name>Informative References</name>
        <reference anchor="RFC6775" target="https://www.rfc-editor.org/info/rfc6775">
          <front>
            <title>Neighbor Discovery Optimization for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)</title>
            <seriesInfo name="DOI" value="10.17487/RFC6775"/>
            <seriesInfo name="RFC" value="6775"/>
            <author fullname="Z. Shelby" initials="Z." role="editor" surname="Shelby">
              <organization/>
            </author>
            <author fullname="S. Chakrabarti" initials="S." surname="Chakrabarti">
              <organization/>
            </author>
            <author fullname="E. Nordmark" initials="E." surname="Nordmark">
              <organization/>
            </author>
            <author fullname="C. Bormann" initials="C." surname="Bormann">
              <organization/>
            </author>
            <date month="November" year="2012"/>
            <abstract>
              <t>The IETF work in IPv6 over Low-power Wireless Personal Area Network (6LoWPAN) defines 6LoWPANs such as IEEE 802.15.4.  This and other similar link technologies have limited or no usage of multicast signaling due to energy conservation.  In addition, the wireless network may not strictly follow the traditional concept of IP subnets and IP links.  IPv6 Neighbor Discovery was not designed for non- transitive wireless links, as its reliance on the traditional IPv6 link concept and its heavy use of multicast make it inefficient and sometimes impractical in a low-power and lossy network.  This document describes simple optimizations to IPv6 Neighbor Discovery, its addressing mechanisms, and duplicate address detection for Low- power Wireless Personal Area Networks and similar networks.  The document thus updates RFC 4944 to specify the use of the optimizations defined here.  [STANDARDS-TRACK]</t>
            </abstract>
          </front>
        </reference>
        <reference anchor="RFC6874" target="https://www.rfc-editor.org/info/rfc6874">
          <front>
            <title>Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers</title>
            <seriesInfo name="DOI" value="10.17487/RFC6874"/>
            <seriesInfo name="RFC" value="6874"/>
            <author fullname="B. Carpenter" initials="B." surname="Carpenter">
              <organization/>
            </author>
            <author fullname="S. Cheshire" initials="S." surname="Cheshire">
              <organization/>
            </author>
            <author fullname="R. Hinden" initials="R." surname="Hinden">
              <organization/>
            </author>
            <date month="February" year="2013"/>
            <abstract>
              <t>This document describes how the zone identifier of an IPv6 scoped address, defined as &lt;zone_id&gt; in the IPv6 Scoped Address Architecture (RFC 4007), can be represented in a literal IPv6 address and in a Uniform Resource Identifier that includes such a literal address.  It updates the URI Generic Syntax specification (RFC 3986) accordingly.</t>
            </abstract>
          </front>
        </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>
            <seriesInfo name="DOI" value="10.17487/RFC8132"/>
            <seriesInfo name="RFC" value="8132"/>
            <author fullname="P. van der Stok" initials="P." surname="van der Stok">
              <organization/>
            </author>
            <author fullname="C. Bormann" initials="C." surname="Bormann">
              <organization/>
            </author>
            <author fullname="A. Sehgal" initials="A." surname="Sehgal">
              <organization/>
            </author>
            <date month="April" year="2017"/>
            <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>
        </reference>
        <reference anchor="RFC7641" target="https://www.rfc-editor.org/info/rfc7641">
          <front>
            <title>Observing Resources in the Constrained Application Protocol (CoAP)</title>
            <seriesInfo name="DOI" value="10.17487/RFC7641"/>
            <seriesInfo name="RFC" value="7641"/>
            <author fullname="K. Hartke" initials="K." surname="Hartke">
              <organization/>
            </author>
            <date month="September" year="2015"/>
            <abstract>
              <t>The Constrained Application Protocol (CoAP) is a RESTful application protocol for constrained nodes and networks.  The state of a resource on a CoAP server can change over time.  This document specifies a simple protocol extension for CoAP that enables CoAP clients to "observe" resources, i.e., to retrieve a representation of a resource and keep this representation updated by the server over a period of time.  The protocol follows a best-effort approach for sending new representations to clients and provides eventual consistency between the state observed by each client and the actual resource state at the server.</t>
            </abstract>
          </front>
        </reference>

<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6775.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6874.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.7641.xml"/>

        <reference anchor="ER">
          <front>
            <title>The entity-relationship model--toward a unified view of data</title>
            <seriesInfo name="DOI" value="10.1145/320434.320440"/>
            <seriesInfo name="ACM Transactions on Database Systems" value="Vol. 1, pp. 9-36"/>
	    <author fullname="Peter Pin-Shan Chen" initials="P." surname="Chen">
              <organization/>
            </author>
	    <date month="March" year="1976"/>
	  </front>
        </reference>
        <reference anchor="I-D.silverajan-core-coap-protocol-negotiation" target="https://www.ietf.org/archive/id/draft-silverajan-core-coap-protocol-negotiation-09.txt">
          <front>
            <title>CoAP Protocol Negotiation</title>
            <seriesInfo name="Internet-Draft" value="draft-silverajan-core-coap-protocol-negotiation-09"/>
            <author fullname="Bilhanan Silverajan">
              <organization>TUT</organization>
            </author>
            <author fullname="Mert Ocak">
              <organization>Ericsson</organization>
            </author>
            <date day="2" month="July" year="2018"/>
            <abstract>
              <t>   CoAP has been standardised as an application-level REST-based
   protocol.  When multiple transport protocols exist for exchanging
   CoAP resource representations, this document introduces a way forward
   for CoAP endpoints as well as intermediaries to agree upon alternate
   transport and protocol configurations as well as URIs for CoAP
   messaging.  Several mechanisms are proposed: Extending the CoRE
   Resource Directory with new parameter types, introducing a new CoAP
   Option with which clients can interact directly with servers without
   needing the Resource Directory, and finally a new CoRE Link Attribute
   allowing exposing alternate locations name="DOI" value="10.1145/320434.320440"/>
            <refcontent>ACM Transactions on a per-resource basis.

              </t>
            </abstract>
          </front> Database Systems, Vol. 1, pp. 9-36</refcontent>
        </reference>

<xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.silverajan-core-coap-protocol-negotiation.xml"/>

<reference anchor="I-D.ietf-ace-oauth-authz" target="https://www.ietf.org/archive/id/draft-ietf-ace-oauth-authz-37.txt"> anchor='I-D.ietf-ace-oauth-authz'>
<front>
<title>Authentication and Authorization for Constrained Environments (ACE) using Using the OAuth 2.0 Framework (ACE-OAuth)</title>
            <seriesInfo name="Internet-Draft" value="draft-ietf-ace-oauth-authz-37"/>
<author fullname="Ludwig Seitz">
              <organization>Combitech</organization> initials='L' surname='Seitz' fullname='Ludwig Seitz'>
    <organization />
</author>
<author fullname="Goeran Selander">
              <organization>Ericsson</organization> initials='G' surname='Selander' fullname='Göran Selander'>
    <organization />
</author>
<author fullname="Erik Wahlstroem"> initials='E' surname='Wahlstroem' fullname='Erik Wahlstroem'>
    <organization />
</author>
<author fullname="Samuel Erdtman">
              <organization>Spotify AB</organization> initials='S' surname='Erdtman' fullname='Samuel Erdtman'>
    <organization />
</author>
<author fullname="Hannes Tschofenig">
              <organization>Arm Ltd.</organization> initials='H' surname='Tschofenig' fullname='Hannes Tschofenig'>
    <organization />
</author>
<date day="4" month="February" year="2021"/>
            <abstract>
              <t>   This specification defines a framework for authentication and
   authorization in Internet of Things (IoT) environments called ACE-
   OAuth.  The framework is based on a set of building blocks including
   OAuth 2.0 and the Constrained Application Protocol (CoAP), thus
   transforming a well-known and widely used authorization solution into
   a form suitable for IoT devices.  Existing specifications are used
   where possible, but extensions are added and profiles are defined to
   better serve the IoT use cases.

              </t>
            </abstract> month='November' day='8' year='2021'/>
</front>
<seriesInfo name='Internet-Draft' value='draft-ietf-ace-oauth-authz-46' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-ietf-ace-oauth-authz-46.txt' />
</reference>

<reference anchor="I-D.ietf-core-links-json" target="https://www.ietf.org/archive/id/draft-ietf-core-links-json-10.txt"> anchor='I-D.ietf-core-links-json'>
<front>
<title>Representing Constrained RESTful Environments (CoRE) Link Format in JSON and CBOR</title>
            <seriesInfo name="Internet-Draft" value="draft-ietf-core-links-json-10"/>
<author fullname="Kepeng LI">
              <organization>Alibaba Group</organization> initials='K' surname='Li' fullname='Kepeng Li'>
    <organization />
</author>
<author fullname="Akbar Rahman">
              <organization>InterDigital</organization> initials='A' surname='Rahman' fullname='Akbar Rahman'>
    <organization />
</author>
<author fullname="Carsten Bormann">
              <organization>Universitaet Bremen TZI</organization> initials='C' surname='Bormann' fullname='Carsten Bormann' role="editor">
    <organization />
</author>
<date day="26" month="February" year="2018"/>
            <abstract>
              <t>   JavaScript Object Notation, JSON (RFC 8259) is a text-based data
   format which is popular for Web based data exchange.  Concise Binary
   Object Representation, CBOR (RFC7049) is a binary data format which
   has been optimized for data exchange for the Internet of Things
   (IoT).  For many IoT scenarios, CBOR formats will be preferred since
   it can help decrease transmission payload sizes as well as
   implementation code sizes compared to other data formats.

   Web Linking (RFC 8288) provides a way to represent links between Web
   resources as well as the relations expressed by them and attributes
   of such a link.  In constrained networks, a collection of Web links
   can be exchanged in the CoRE link format (RFC 6690).  Outside of
   constrained environments, it may be useful to represent these
   collections of Web links in JSON, and similarly, inside constrained
   environments, in CBOR.  This specification defines a common format
   for this.

              </t>
            </abstract> month='February' day='26' year='2018' />
</front>
<seriesInfo name='Internet-Draft' value='draft-ietf-core-links-json-10' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-ietf-core-links-json-10.txt' />
</reference>

<reference anchor="I-D.ietf-core-rd-dns-sd" target="https://www.ietf.org/archive/id/draft-ietf-core-rd-dns-sd-05.txt"> anchor='I-D.ietf-core-rd-dns-sd'>
<front>
<title>CoRE Resource Directory: DNS-SD mapping</title>
            <seriesInfo name="Internet-Draft" value="draft-ietf-core-rd-dns-sd-05"/>
<author fullname="Peter initials='P' surname='van der Stok' fullname='Peter van der Stok">
              <organization>Consultant</organization> Stok'>
    <organization />
</author>
<author fullname="Michael Koster">
              <organization>SmartThings</organization> initials='M' surname='Koster' fullname='Michael Koster'>
    <organization />
</author>
<author fullname="Christian Amsüss">
              <organization>Energy Harvesting Solutions</organization> initials='C' surname='Amsuess' fullname='Christian Amsuess'>
    <organization />
</author>
<date day="7" month="July" year="2019"/>
            <abstract>
              <t>   Resource and service discovery are complementary.  Resource discovery
   provides fine-grained detail about the content of a web server, while
   service discovery can provide a scalable method to locate servers in
   large networks.  This document defines a method for mapping between
   CoRE Link Format attributes and DNS-Based Service Discovery records
   to facilitate the use of either method to locate RESTful service
   interfaces (APIs) in heterogeneous HTTP/CoAP environments.

              </t>
            </abstract> month='July' day='7' year='2019' />
</front>
<seriesInfo name='Internet-Draft' value='draft-ietf-core-rd-dns-sd-05' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-ietf-core-rd-dns-sd-05.txt' />
</reference>

        <reference anchor="LwM2M" target="https://openmobilealliance.org/RELEASE/LightweightM2M/V1_1-20180612-C/OMA-TS-LightweightM2M_Transport-V1_1-20180612-C.pdf">
          <front>
            <title>Lightweight Machine to Machine Technical Specification: Transport Bindings (Candidate Version 1.1)</title>
            <author>
              <organization>Open Mobile Alliance</organization>
            </author>
            <date year="2018" month="June" day="12"/>
          </front>
        </reference>
        <reference anchor="RFC7228" target="https://www.rfc-editor.org/info/rfc7228">
          <front>
            <title>Terminology for Constrained-Node Networks</title>
            <seriesInfo name="DOI" value="10.17487/RFC7228"/>
            <seriesInfo name="RFC" value="7228"/>
            <author fullname="C. Bormann" initials="C." surname="Bormann">
              <organization/>
            </author>
            <author fullname="M. Ersue" initials="M." surname="Ersue">
              <organization/>
            </author>
            <author fullname="A. Keranen" initials="A." surname="Keranen">
              <organization/>
            </author>
            <date month="May" year="2014"/>
            <abstract>
              <t>The Internet Protocol Suite is increasingly used on small devices with severe constraints on power, memory, and processing resources, creating constrained-node networks.  This document provides a number of basic terms that have been useful in the standardization work for constrained-node networks.</t>
            </abstract>
          </front>
        </reference>
        <reference anchor="RFC4944" target="https://www.rfc-editor.org/info/rfc4944">
          <front>
            <title>Transmission of IPv6 Packets over IEEE 802.15.4 Networks</title>
            <seriesInfo name="DOI" value="10.17487/RFC4944"/>
            <seriesInfo name="RFC" value="4944"/>
            <author fullname="G. Montenegro" initials="G." surname="Montenegro">
              <organization/>
            </author>
            <author fullname="N. Kushalnagar" initials="N." surname="Kushalnagar">
              <organization/>
            </author>
            <author fullname="J. Hui" initials="J." surname="Hui">
              <organization/>
            </author>
            <author fullname="D. Culler" initials="D." surname="Culler">
              <organization/>
            </author>
            <date month="September" year="2007"/>
            <abstract>
              <t>This document describes the frame format for transmission of IPv6 packets and the method of forming IPv6 link-local addresses and statelessly autoconfigured addresses on IEEE 802.15.4 networks. Additional specifications include a simple header compression scheme using shared context and provisions for packet delivery in IEEE 802.15.4 meshes.  [STANDARDS-TRACK]</t>
            </abstract>
          </front>
        </reference>
        <reference anchor="RFC8141" target="https://www.rfc-editor.org/info/rfc8141">
          <front>
            <title>Uniform Resource Names (URNs)</title>
            <seriesInfo name="DOI" value="10.17487/RFC8141"/>
            <seriesInfo name="RFC" value="8141"/>
            <author fullname="P. Saint-Andre" initials="P." surname="Saint-Andre">
              <organization/>
            </author>
            <author fullname="J. Klensin" initials="J." surname="Klensin">
              <organization/>
            </author>
            <date month="April" year="2017"/>
            <abstract>
              <t>A Uniform Resource Name (URN) is a Uniform Resource Identifier (URI) that is assigned under the "urn" URI scheme and a particular URN namespace, with the intent that the URN will be a persistent, location-independent resource identifier.  With regard to URN syntax, this document defines the canonical syntax for URNs (in a way that is consistent with URI syntax), specifies methods for determining URN-equivalence, and discusses URI conformance.  With regard to URN namespaces, this document specifies a method for defining a URN namespace and associating it with a namespace identifier, and it describes procedures for registering namespace identifiers with the Internet Assigned Numbers Authority (IANA).  This document obsoletes both RFCs 2141 and 3406.</t>
            </abstract>
          </front>
        </reference>
        <reference anchor="RFC6724" target="https://www.rfc-editor.org/info/rfc6724">
          <front>
            <title>Default Address Selection for Internet Protocol Version 6 (IPv6)</title>
            <seriesInfo name="DOI" value="10.17487/RFC6724"/>
            <seriesInfo name="RFC" value="6724"/>
            <author fullname="D. Thaler" initials="D." role="editor" surname="Thaler">
              <organization/>
            </author>
            <author fullname="R. Draves" initials="R." surname="Draves">
              <organization/>
            </author>
            <author fullname="A. Matsumoto" initials="A." surname="Matsumoto">
              <organization/>
            </author>
            <author fullname="T. Chown" initials="T." surname="Chown">
              <organization/>
            </author>
            <date month="September" year="2012"/>
            <abstract>
              <t>This document describes two algorithms, one for source address selection and one for destination address selection.  The algorithms specify default behavior for all Internet Protocol version 6 (IPv6) implementations.  They do not override choices made by applications or upper-layer protocols, nor do they preclude the development of more advanced mechanisms for address selection.  The two algorithms share a common context, including an optional mechanism for allowing administrators to provide policy that can override the default behavior.  In dual-stack implementations, the destination address selection algorithm can consider both IPv4 and IPv6 addresses -- depending on the available source addresses, the algorithm might prefer IPv6 addresses over IPv4 addresses, or vice versa.</t>
              <t>Default address selection as defined in this specification applies to all IPv6 nodes, including both hosts and routers.  This document obsoletes RFC 3484.  [STANDARDS-TRACK]</t>
            </abstract>
          </front>
        </reference>
        <reference anchor="RFC8106" target="https://www.rfc-editor.org/info/rfc8106">
          <front>
            <title>IPv6 Router Advertisement Options for DNS Configuration</title>
            <seriesInfo name="DOI" value="10.17487/RFC8106"/>
            <seriesInfo name="RFC" value="8106"/>
            <author fullname="J. Jeong" initials="J." surname="Jeong">
              <organization/>
            </author>
            <author fullname="S. Park" initials="S." surname="Park">
              <organization/>
            </author>
            <author fullname="L. Beloeil" initials="L." surname="Beloeil">
              <organization/>
            </author>
            <author fullname="S. Madanapalli" initials="S." surname="Madanapalli">
              <organization/>
            </author>
            <date month="March" year="2017"/>
            <abstract>
              <t>This document specifies IPv6 Router Advertisement (RA) options (called "DNS RA options") to allow IPv6 routers to advertise a list of DNS Recursive Server Addresses and a DNS Search List to IPv6 hosts.</t>
              <t>This document, which obsoletes RFC 6106, defines a higher default value of the lifetime of the DNS RA options to reduce the likelihood of expiry of the options on links with a relatively high rate of packet loss.</t>
            </abstract>
          </front>
        </reference>
        <reference anchor="I-D.bormann-t2trg-rel-impl" target="https://www.ietf.org/archive/id/draft-bormann-t2trg-rel-impl-02.txt">
          <front>
            <title>impl-info: A link relation type for disclosing implementation information</title>
            <seriesInfo name="Internet-Draft" value="draft-bormann-t2trg-rel-impl-02"/>
            <author fullname="Carsten Bormann">
              <organization>Universität Bremen TZI</organization>
            </author>
            <date day="27" month="September" year="2020"/>
            <abstract>
              <t>   For debugging, it is often helpful to have information about the
   implementation of a peer.  The present specification defines a link
   relation type, "impl-info", that can be used to convey such
   information via self-description, such as in the "/.well-known/core"
   resource.

              </t>
            </abstract>
          </front>
        </reference>
        <reference anchor="I-D.hartke-t2trg-coral" target="https://www.ietf.org/archive/id/draft-hartke-t2trg-coral-09.txt">
          <front>
            <title>The Constrained RESTful Application Language (CoRAL)</title>
            <seriesInfo name="Internet-Draft" value="draft-hartke-t2trg-coral-09"/>
            <author fullname="Klaus Hartke">
              <organization>Ericsson</organization>
            </author>
            <date day="8" month="July" year="2019"/>
            <abstract>
              <t>   The Constrained RESTful Application Language (CoRAL) defines a data
   model and interaction model as well as two specialized serialization
   formats for the description of typed connections between resources on
   the Web ("links"), possible operations on such resources ("forms"),
   as well as simple resource metadata.

              </t>
            </abstract>
          </front>
        </reference>
        <reference anchor="RFC4122" target="https://www.rfc-editor.org/info/rfc4122">
          <front>
            <title>A Universally Unique IDentifier (UUID) URN Namespace</title>
            <seriesInfo name="DOI" value="10.17487/RFC4122"/>
            <seriesInfo name="RFC" value="4122"/>
            <author fullname="P. Leach" initials="P." surname="Leach">
              <organization/>
            </author>
            <author fullname="M. Mealling" initials="M." surname="Mealling">
              <organization/>
            </author>
            <author fullname="R. Salz" initials="R." surname="Salz">
              <organization/>
            </author>
            <date month="July" year="2005"/>
            <abstract>
              <t>This specification defines a Uniform Resource Name namespace for UUIDs (Universally Unique IDentifier), also known as GUIDs (Globally Unique IDentifier).  A UUID is 128 bits long, and can guarantee uniqueness across space and time.  UUIDs were originally used in the Apollo Network Computing System and later in the Open Software Foundation\'s (OSF) Distributed Computing Environment (DCE), and then in Microsoft Windows platforms.</t>
              <t>This specification is derived from the DCE specification with the kind permission of the OSF (now known as The Open Group).  Information from earlier versions of the DCE specification have been incorporated into this document.  [STANDARDS-TRACK]</t>
            </abstract>
          </front>
        </reference>
        <reference anchor="RFC8613" target="https://www.rfc-editor.org/info/rfc8613">
          <front>
            <title>Object Security for Constrained RESTful Environments (OSCORE)</title>
            <seriesInfo name="DOI" value="10.17487/RFC8613"/>
            <seriesInfo name="RFC" value="8613"/>
            <author fullname="G. Selander" initials="G." surname="Selander">
              <organization/>
            </author>
            <author fullname="J. Mattsson" initials="J." surname="Mattsson">
              <organization/>
            </author>
            <author fullname="F. Palombini" initials="F." surname="Palombini">
              <organization/>
            </author>
            <author fullname="L. Seitz" initials="L." surname="Seitz">
              <organization/>
            </author>
            <date month="July" year="2019"/>
            <abstract>
              <t>This document defines Object Security for Constrained RESTful Environments (OSCORE), a method for application-layer protection of the Constrained Application Protocol (CoAP), using CBOR Object Signing and Encryption (COSE).  OSCORE provides end-to-end protection between endpoints communicating using CoAP or CoAP-mappable HTTP. OSCORE is designed for constrained nodes and networks supporting a range of proxy operations, including translation between different transport protocols.</t>
              <t>Although an optional functionality of CoAP, OSCORE alters CoAP options processing and IANA registration.  Therefore, this document updates RFC 7252.</t>
            </abstract>
          </front>
        </reference>
        <reference anchor="RFC5771" target="https://www.rfc-editor.org/info/rfc5771">
          <front>
            <title>IANA Guidelines for IPv4 Multicast Address Assignments</title>
            <seriesInfo name="DOI" value="10.17487/RFC5771"/>
            <seriesInfo name="RFC" value="5771"/>
            <seriesInfo name="BCP" value="51"/>
            <author fullname="M. Cotton" initials="M." surname="Cotton">
              <organization/>
            </author>
            <author fullname="L. Vegoda" initials="L." surname="Vegoda">
              <organization/>
            </author>
            <author fullname="D. Meyer" initials="D." surname="Meyer">
              <organization/>
            </author>
            <date month="March" year="2010"/>
            <abstract>
              <t>This document provides guidance for the Internet Assigned Numbers Authority (IANA) in assigning IPv4 multicast addresses.  It obsoletes RFC 3171 and RFC 3138 and updates RFC 2780.  This memo documents an  Internet Best Current Practice.</t>
            </abstract>
          </front>
        </reference>
        <reference anchor="RFC3849" target="https://www.rfc-editor.org/info/rfc3849">
          <front>
            <title>IPv6 Address Prefix Reserved for Documentation</title>
            <seriesInfo name="DOI" value="10.17487/RFC3849"/>
            <seriesInfo name="RFC" value="3849"/>
            <author fullname="G. Huston" initials="G." surname="Huston">
              <organization/>
            </author>
            <author fullname="A. Lord" initials="A." surname="Lord">
              <organization/>
            </author>
            <author fullname="P. Smith" initials="P." surname="Smith">
              <organization/>
            </author>
            <date month="July" year="2004"/>
            <abstract>
              <t>To reduce the likelihood of conflict and confusion when relating documented examples to deployed systems, an IPv6 unicast address prefix is reserved for use in examples in RFCs, books, documentation, and the like.  Since site-local and link-local unicast addresses have special meaning in IPv6, these addresses cannot be used in many example situations.  The document describes the use of the IPv6 address prefix 2001:DB8::/32 as a reserved prefix for use in documentation.  This memo provides information for the Internet community.</t>
            </abstract>
          </front>
        </reference>
        <reference anchor="RFC3306" target="https://www.rfc-editor.org/info/rfc3306">
          <front>
            <title>Unicast-Prefix-based IPv6 Multicast Addresses</title>
            <seriesInfo name="DOI" value="10.17487/RFC3306"/>
            <seriesInfo name="RFC" value="3306"/>
            <author fullname="B. Haberman" initials="B." surname="Haberman">
              <organization/>
            </author>
            <author fullname="D. Thaler" initials="D." surname="Thaler">
              <organization/>
            </author>
            <date month="August" year="2002"/> month="June"/>
          </front>
        </reference>

<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7228.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4944.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8141.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6724.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8106.xml"/>

<xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.bormann-t2trg-rel-impl.xml"/>

<xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.ietf-core-coral.xml"/>

<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4122.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8613.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5771.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3849.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3306.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3307.xml"/>

      </references>
    </references>
    <section anchor="groups" numbered="true" toc="default">
      <name>Groups Registration and Lookup</name>
      <t>The RD-Groups RD-Group's usage pattern allows announcing application groups inside an RD.</t>
      <t>Groups are represented by endpoint registrations.
      Their base address is a multicast address,
      and they SHOULD <bcp14>SHOULD</bcp14> be entered with the endpoint type <tt>core.rd-group</tt>.
      The endpoint name can also be referred to as a group name in this context.</t>
      <t>The registration is inserted into the RD by a Commissioning Tool,
      which might also be known as a group manager here.
      It performs third party third-party registration and registration updates.</t>
      <t>The links it registers SHOULD <bcp14>SHOULD</bcp14> be available on all members that join the group.
Depending on the application, members that lack some resource
MAY resources
<bcp14>MAY</bcp14> be permissible if requests to them fail gracefully.</t>
      <t>The following example shows a CT registering a group with the name "lights" "lights", which provides two resources.
The directory resource path /rd
is an example RD location discovered in a request similar to <xref target="example-discovery" format="default"/>.
The group address in the example is constructed from <xref target="RFC3849" format="default"/>'s the reserved 2001:db8:: prefix in <xref target="RFC3849" format="default"/> as a unicast-prefix based unicast-prefix-based site-local address (see <xref target="RFC3306" format="default"/>.</t> format="default"/>).</t>
      <figure anchor="example-group-registration">
        <name>Example registration Registration of a group</name>
        <artwork name="" type="" align="left" alt=""><![CDATA[ Group</name>
       <sourcecode type=""><![CDATA[
Req: POST coap://rd.example.com/rd?ep=lights&et=core.rd-group
                           &base=coap://[ff35:30:2001:db8:f1::8000:1]
Content-Format: 40
Payload:
</light>;rt="tag:example.com,2020:light";
     if="tag:example.net,2020:actuator",
</color-temperature>;if="tag:example.net,2020:parameter";u=K

Res: 2.01 Created
Location-Path: /rd/12
]]></artwork>
]]></sourcecode>
      </figure>
      <t>In this example, the group manager can easily permit devices that have no
writable color-temperature to join, as they would still respond to brightness
changing brightness-changing commands. Had the group instead contained a single resource that sets
brightness and color temperature color-temperature atomically, endpoints would need to support
both properties.</t>
      <t>The resources of a group can be looked up like any other resource,
and the group registrations (along with any additional registration parameters)
can be looked up using the endpoint lookup interface.</t>
      <t>The following example shows a client performing an endpoint lookup for all groups.</t> groups:</t>
      <figure anchor="example-group-lookup">
        <name>Example lookup Lookup of groups</name>
        <artwork name="" type="" align="left" alt=""><![CDATA[ Groups</name>
       <sourcecode type=""><![CDATA[
Req: GET /rd-lookup/ep?et=core.rd-group

Res: 2.05 Content
Payload:
</rd/12>;ep=lights&et=core.rd-group;
         base="coap://[ff35:30:2001:f1:db8::8000:1]";rt=core.rd-ep
]]></artwork>
]]></sourcecode>
      </figure>
      <t>The following example shows a client performing a lookup of all resources of all endpoints (groups) with et=core.rd-group.</t> et=core.rd-group:</t>
      <figure anchor="example-group-lookup-res">
        <name>Example lookup Lookup of resources inside groups</name>
        <artwork name="" type="" align="left" alt=""><![CDATA[ Resources Inside Groups</name>
       <sourcecode type=""><![CDATA[
Req: GET /rd-lookup/res?et=core.rd-group

Res: 2.05 Content
Payload:
<coap://[ff35:30:2001:db8:f1::8000:1]/light>;
     rt="tag:example.com,2020:light";
     if="tag:example.net,2020:actuator",
<coap://[ff35:30:2001:db8:f1::8000:1]/color-temperature>;
     if="tag:example.net,2020:parameter";u=K,
]]></artwork>
]]></sourcecode>
      </figure>
    </section>
    <section anchor="weblink" numbered="true" toc="default">
      <name>Web links Links and the Resource Directory</name>
      <t>Understanding the semantics of a link-format document and its URI references is
a journey through different documents (<xref target="RFC3986" format="default"/> defining URIs, <xref target="RFC6690" format="default"/>
defining link-format documents based on <xref target="RFC8288" format="default"/> format="default"/>, which defines Link header fields,
and <xref target="RFC7252" format="default"/> providing the transport). This appendix summarizes
the mechanisms and semantics at play from an entry in <tt>/.well-known/core</tt> to a
resource lookup.</t>
      <t>This text is primarily aimed at people entering the field of Constrained
Restful Environments from applications that previously did not use web
mechanisms.</t>
      <section anchor="a-simple-example" numbered="true" toc="default">
        <name>A simple example</name> Simple Example</name>
        <t>Let's start this example with a very simple host, <tt>2001:db8:f0::1</tt>. A client
that follows classical CoAP Discovery discovery (<xref target="RFC7252" format="default"/> Section 7), section="7" sectionFormat="comma"/>) sends the
following multicast request to learn about neighbours neighbors supporting resources with
resource-type "temperature".</t>
        <t>The client sends a link-local multicast:</t>
        <figure anchor="example-weblink-wkc">
          <name>Example of direct resource discovery</name>
          <artwork name="" type="" align="left" alt=""><![CDATA[ Direct Resource Discovery</name>
         <sourcecode type=""><![CDATA[
Req: GET coap://[ff02::fd]:5683/.well-known/core?rt=temperature

Res: 2.05 Content
Payload:
</sensors/temp>;rt=temperature;ct=0
]]></artwork>
]]></sourcecode>
        </figure>
        <t>where the response is sent by the server, <tt>[2001:db8:f0::1]:5683</tt>.</t>
        <t>While the client -- on the a practical or implementation client side -- can implementation might just go
ahead and create a new request to <tt>[2001:db8:f0::1]:5683</tt> with Uri-Path: Uri-Path
<tt>sensors</tt> and <tt>temp</tt>, the full resolution steps for insertion into and retrieval from the RD without any shortcuts are:</t> are as follows.</t>
        <section anchor="resolveURI" numbered="true" toc="default">
          <name>Resolving the URIs</name>
          <t>The client parses the single returned record. The link's link. Its target (sometimes
called "href") is "<tt>/sensors/temp</tt>", <tt>/sensors/temp</tt>, which is a relative URI that needs resolving.
The base
URI &lt;coap://[ff02::fd]:5683/.well-known/core&gt; <tt>coap://[ff02::fd]:5683/.well-known/core</tt> is used to resolve the
reference /sensors/temp against.</t> against <tt>/sensors/temp</tt>.</t>
          <t>The Base base URI of the requested resource can be composed from the options of the CoAP GET request by following the steps of
<xref target="RFC7252" format="default"/> section 6.5 sectionFormat="comma" section="6.5"/> (with an addition at the end of 8.2) Section <xref target="RFC7252" sectionFormat="bare" section="8.2"/>) into
"<tt>coap://[2001:db8:f0::1]/.well-known/core</tt>".</t>
<tt>coap://[2001:db8:f0::1]/.well-known/core</tt>.</t>
          <t>Because "<tt>/sensors/temp</tt>" <tt>/sensors/temp</tt> starts with a single slash,
the record's link's target is resolved by replacing the path "<tt>/.well-known/core</tt>" <tt>/.well-known/core</tt>
from the Base base URI (section 5.2 <xref (<xref target="RFC3986" format="default"/>) sectionFormat="comma" section="5.2"/>) with the relative target URI "<tt>/sensors/temp</tt>" <tt>/sensors/temp</tt> into
"<tt>coap://[2001:db8:f0::1]/sensors/temp</tt>".</t>
<tt>coap://[2001:db8:f0::1]/sensors/temp</tt>.</t>
        </section>
        <section anchor="interpreting-attributes-and-relations" numbered="true" toc="default">
          <name>Interpreting attributes Attributes and relations</name> Relations</name>
	  <t>Some more information but about the record's link's target can be obtained from the payload:
the resource type of the target is "temperature", and its content format is
text/plain (ct=0).</t>
          <t>A relation in a web link is a three-part statement that specifies a named relation between the so-called "context resource"
and the target resource, like "<em>This page</em> has <em>its table
of contents</em> at <em>/toc.html</em>". In link format link-format documents,
there is an implicit "host relation" specified with default parameter: parameter rel="hosts".</t>
          <t>In our example, the context resource of the link is implied to be "coap:://[2001:db8:f0::1]" <tt>coap:://[2001:db8:f0::1]</tt>
by the default value of the anchor (see <xref target="resolution-rules" format="default"/>).
A full English expression of the "host relation" is:</t>
          <t>'<tt>coap://[2001:db8:f0::1]</tt>
          <t indent="3"><tt>coap://[2001:db8:f0::1]</tt> is hosting the resource
<tt>coap://[2001:db8:f0::1]/sensors/temp</tt>, which is of the resource type "temperature" and
can be accessed using read in the text/plain content format.'</t> format.</t>
        </section>
      </section>
      <section anchor="a-slightly-more-complex-example" numbered="true" toc="default">
        <name>A slightly more complex example</name> Slightly More Complex Example</name>
        <t>Omitting the <tt>rt=temperature</tt> filter, the discovery query would
have given some more records links in the payload:</t>
        <figure anchor="example-weblink-wkc-extended">
          <name>Extended example Example of direct resource discovery</name>
          <artwork name="" type="" align="left" alt=""><![CDATA[ Direct Resource Discovery</name>
         <sourcecode type=""><![CDATA[
Req: GET coap://[ff02::fd]:5683/.well-known/core

Res: 2.05 Content
Payload:
</sensors/temp>;rt=temperature;ct=0,
</sensors/light>;rt=light-lux;ct=0,
</t>;anchor="/sensors/temp";rel=alternate,
<http://www.example.com/sensors/t123>;anchor="/sensors/temp";
    rel=describedby
]]></artwork>
]]></sourcecode>
        </figure>
        <t>Parsing the third record, link, the client encounters the "anchor" parameter. It is
a URI relative to the Base base URI of the request and is thus resolved to
"<tt>coap://[2001:db8:f0::1]/sensors/temp</tt>".
<tt>coap://[2001:db8:f0::1]/sensors/temp</tt>.
That is the context resource of the link, so the "rel" statement is not about
the target and the Base base URI any more, more but about the target and the resolved
URI. Thus, the third record link could be read as
"<tt>coap://[2001:db8:f0::1]/sensors/temp</tt> as:</t>
<t indent="3"><tt>coap://[2001:db8:f0::1]/sensors/temp</tt> has an alternate representation at
<tt>coap://[2001:db8:f0::1]/t</tt>".</t>
<tt>coap://[2001:db8:f0::1]/t</tt>.</t>
        <t>Following the same resolution steps, the fourth record link can be read as "<tt>coap://[2001:db8:f0::1]/sensors/temp</tt> <tt>coap://[2001:db8:f0::1]/sensors/temp</tt> is
described by <tt>http://www.example.com/sensors/t123</tt>".</t> <tt>http://www.example.com/sensors/t123</tt>.</t>
      </section>
      <section anchor="enter-the-resource-directory" numbered="true" toc="default">
        <name>Enter the Resource Directory</name>
        <t>The RD tries to carry the semantics obtainable by classical
	CoAP discovery over to the resource lookup interface as faithfully as possible.</t>
	<t>For the following queries, we will assume that the simple host has used Simple
Registration simple
	registration to register at the RD that was announced to it,
	sending this request from its UDP port <tt>[2001:db8:f0::1]:6553</tt>:</t>
        <figure anchor="example-weblink-simple">
          <name>Example of a simple registration</name>
          <artwork name="" type="" align="left" alt=""><![CDATA[ Simple Registration</name>
         <sourcecode type=""><![CDATA[
Req: POST coap://[2001:db8:f01::ff]/.well-known/rd?ep=simple-host1 coap://[2001:db8:f0::ff]/.well-known/rd?ep=simple-host1

Res: 2.04 Changed
]]></artwork>
]]></sourcecode>
        </figure>
        <t>The RD would have accepted the registration, registration and queried the
simple host's <tt>/.well-known/core</tt> by itself. As a result, the host is registered
as an endpoint in the RD with the name "simple-host1". The registration is
active for 90000 seconds, and the endpoint registration Base base URI is
"<tt>coap://[2001:db8:f0::1]</tt>"
<tt>coap://[2001:db8:f0::1]</tt>, following the resolution steps described in <xref target="resolveURI" format="default"/>. It should be remarked that the Base base URI constructed that way always yields a URI of the form: form scheme://authority without path suffix.</t>
        <t>If the client now queries the RD as it would previously have issued a multicast
request, it would go through the RD discovery steps by fetching
<tt>coap://[2001:db8:f0::ff]/.well-known/core?rt=core.rd-lookup-res</tt>, obtain
<tt>coap://[2001:db8:f0::ff]/rd-lookup/res</tt> as the resource lookup endpoint, and
ask it for all temperature resources:</t>
        <figure anchor="example-weblink-lookup-result">
          <name>Example exchange performing resource lookup</name>
          <artwork name="" type="" align="left" alt=""><![CDATA[ Exchange Performing Resource Lookup</name>
         <sourcecode type=""><![CDATA[
Req: GET coap://[2001:db8:f0::ff]/rd-lookup/res?rt=temperature

Res: 2.05 Content
Payload:
<coap://[2001:db8:f0::1]/sensors/temp>;rt=temperature;ct=0
]]></artwork>
]]></sourcecode>
        </figure>
        <t>This is not <em>literally</em> the same response that it would have received from a
multicast request, but it contains the equivalent statement:</t>
        <t>'<tt>coap://[2001:db8:f0::1]</tt>
        <t indent="3"><tt>coap://[2001:db8:f0::1]</tt> is hosting the resource
<tt>coap://[2001:db8:f0::1]/sensors/temp</tt>, which is of the resource type "temperature" and
can be accessed using the text/plain content format.'</t> format.</t>
        <t>To complete the examples, the client could also query all resources hosted at
the endpoint with the known endpoint name "simple-host1":</t>
        <figure anchor="example-weblink-lookup-result-extended">
          <name>Extended example exchange performing resource lookup</name>
          <artwork name="" type="" align="left" alt=""><![CDATA[ Example Exchange Performing Resource Lookup</name>
         <sourcecode type=""><![CDATA[
Req: GET coap://[2001:db8:f0::ff]/rd-lookup/res?ep=simple-host1

Res: 2.05 Content
Payload:
<coap://[2001:db8:f0::1]/sensors/temp>;rt=temperature;ct=0,
<coap://[2001:db8:f0::1]/sensors/light>;rt=light-lux;ct=0,
<coap://[2001:db8:f0::1]/t>;
    anchor="coap://[2001:db8:f0::1]/sensors/temp";rel=alternate,
<http://www.example.com/sensors/t123>;
    anchor="coap://[2001:db8:f0::1]/sensors/temp";rel=describedby
]]></artwork>
]]></sourcecode>
        </figure>
        <t>All the target and anchor references are already in absolute form there, which
don't need to be resolved any further.</t>
        <t>Had the simple host done an equivalent full registration with a base= parameter (e.g.
<tt>?ep=simple-host1&amp;base=coap+tcp://simple-host1.example.com</tt>), (e.g.,
<tt>?ep=simple-host1&amp;base=coap+tcp://sh1.example.com</tt>), that context would
have been used to resolve the relative anchor values instead, giving</t> giving the following and analogous links:</t>
        <figure anchor="example-weblink-lookup-result-base">
          <name>Example payload Payload of a response Response to a resource lookup Resource Lookup with a dedicated base Dedicated Base URI</name>
          <artwork name="" type="" align="left" alt=""><![CDATA[
<coap+tcp://simple-host1.example.com/sensors/temp>;rt=temperature;ct=0
]]></artwork>
         <sourcecode type=""><![CDATA[
<coap+tcp://sh1.example.com/sensors/temp>;rt=temperature;ct=0
]]></sourcecode>
        </figure>
        <t>and analogous records.</t>

      </section>
      <section anchor="resolution-rules" numbered="true" toc="default">
        <name>A note Note on differences Differences between link-format Link-Format and Link header fields</name> Header Fields</name>
        <t>While link-format and Link header fields look very similar and are based on the same
model of typed links, there are some differences between <xref target="RFC6690" format="default"/> and
<xref target="RFC8288" format="default"/>.
When implementing an RD or interacting with an RD,
care must be taken to follow the behavior described in <xref target="RFC6690" format="default"/> behavior
whenever application/link-format <tt>application/link-format</tt> representations are used.</t>
        <ul spacing="normal">
          <li>
            <t>"Default value of anchor":
Both under
Under both <xref target="RFC6690" format="default"/> and <xref target="RFC8288" format="default"/>,
relative references in the term inside the angle brackets (the target)
and the anchor attribute are resolved against the relevant base URI
(which usually is the URI used to retrieve the entity), entity)
and independent of each other.  </t>
            <t>
When, in an a Link header <xref target="RFC8288" format="default"/> Link header, format="default"/>, the anchor attribute is absent,
the link's context is the URI of the selected representation
(and usually equal to the base URI).  </t>
            <t>
In links per <xref target="RFC6690" format="default"/> links, format="default"/>, if the anchor attribute is absent,
the default value is the Origin of
(for all relevant cases: cases, the URI reference <tt>/</tt> resolved against)
the link's target.</t>
          </li>
          <li>
            <t>There is no percent encoding in link-format documents.  </t>
            <t>
A
            <t>A link-format document is a UTF-8 encoded UTF-8-encoded string of Unicode characters and
	    does not have percent encoding, while Link header fields are practically ASCII
	    strings that use percent encoding for non-ASCII characters, stating the
	    encoding explicitly when required.  </t>
            <t>
For
	    <t>For example, while a Link header field in a page about a Swedish city might read  </t>
            <artwork
	    read:</t>

            <sourcecode name="" type="" align="left" alt=""><![CDATA[ type="http-message"><![CDATA[
Link: </temperature/Malm%C3%B6>;rel=live-environment-data
]]></artwork>
]]></sourcecode>
            <t>
a link-format document from the same source might describe the link as as:  </t>
            <artwork
            <sourcecode name="" type="" align="left" alt=""><![CDATA[ type=""><![CDATA[
</temperature/Malmö>;rel=live-environment-data
]]></artwork>
]]></sourcecode>
          </li>
        </ul>
      </section>
    </section>
    <section anchor="limitedlinkformat" numbered="true" toc="default">
      <name>Limited Link Format</name>
      <t>The CoRE Link Format Format, as described in <xref target="RFC6690" format="default"/> format="default"/>,
has been interpreted differently by implementers,
and a strict implementation
rules out some use cases of an RD
(e.g.
(e.g., base values with path components in combination with absent anchors).</t>
      <t>This appendix describes
a subset of link format documents called the Limited Link Format.
The one rule herein is not very limiting in practice --
all examples in RFC6690, <xref target="RFC6690" format="default"/> and all deployments the authors are aware of already stick to them --
but ease eases the implementation of RD servers.</t>
      <t>It is applicable to representations in the application/link-format <tt>application/link-format</tt> media type, type
and any other media types that inherit <xref target="RFC6690" format="default"/> Section 2.1.</t> section="2.1" sectionFormat="comma"/>. </t>
      <t>A link format representation is in the Limited Link format Format if,
for each link in it,
the following applies:</t>
      <t>All URI references either follow the URI or the path-absolute ABNF rule of
  RFC3986 (i.e.
  <xref target="RFC3986" format="default"/> (i.e., the target and anchor each either start with a scheme or with a
  single slash).</t>
      <!--  LocalWords:  lookups multicast lookup RESTful CoRE LoWPAN CoAP
 -->
<!--  LocalWords:  microcontrollers URI DNS EP IP EPs discoverable
 -->
<!--  LocalWords:  Metadata metadata lossless anycast ABRO RDNSS ICMP
 -->
<!--  LocalWords:  DHCPv RD's DHCP RDs unicast JSON CBOR wildcard TLS
 -->
<!--  LocalWords:  subdomain substring prepending subtype DTLS UDP
 -->
<!--  LocalWords:  routability NTP TCP WiFi GPRS FQDN SLAAC IPv SDOs
 -->
<!--  LocalWords:  OMA LWM IETF OMNA API SMS MSISDN
 -->
    </section>
        <section anchor="acknowledgments" numbered="false" toc="default">
      <name>Acknowledgments</name>
     <t> <contact fullname="Oscar Novo"/>, <contact fullname="Srdjan Krco"/>, <contact fullname="Szymon Sasin"/>, <contact fullname="Kerry Lynn"/>, <contact fullname="Esko Dijk"/>, <contact fullname="Anders
Brandt"/>, <contact fullname="Matthieu Vial"/>, <contact fullname="Jim Schaad"/>, <contact fullname="Mohit Sethi"/>, <contact fullname="Hauke Petersen"/>, <contact fullname="Hannes Tschofenig"/>, <contact fullname="Sampo Ukkola"/>, <contact fullname="Linyi Tian"/>, <contact fullname="Jan Newmarch"/>, <contact fullname="Matthias Kovatsch"/>, <contact fullname="Jaime Jimenez"/>, and <contact fullname="Ted Lemon"/> have provided helpful comments, discussions, and ideas to improve and shape this document. Zach would also like to thank his colleagues from the EU FP7 SENSEI project, where many of the RD concepts were originally developed.</t>
	</section>
      </back>
  <!-- ##markdown-source:
H4sIAFoPRWAAA9y963bb2JUu+h9PgS2P0RYrJK2bb3I71SrZ1XHHLrtlVXK6
k4wYIiEJMQkwAGhZcfm80nmB82+/2Jn3NRcASnZVdfcex713SqLAhXWda16+
+c3JZJK0RbvID9Pj6uR5epI31bqe5emzos5nbVVfJ/NqVmZLeGBeZ+ftpMjb
88msqvNJLc9O5vrsZO9R0rRZOf9rtqhK+Epbr/OkWNX0U9Pu7ew83tlLZll7
mDbtPFkVh0kKP9XFDD65e503d+H3tppFv8zzVXsJn+zj7831ss7Pm/BAU9Vt
/MmsWq4y3yB8sMzLFh6BD/Ar67PwTFnhI9DHsmqL8yKfy2e3zEpW59lh+qJs
87rM2+Tqgh9N3l/xD+P0j/lZ+rIo3xflxdi30MyqD3l9PR5sdd1eVvVhMkmL
Erp7PE2Pls3//n8b7DUvwvFlXTRtkZXuLzCBeQ5j+V21WMDkw6/TdHfv3gEN
fQ5furu7s7fDM7Eu2/r6MD1a46xn8NHqklZq6zcH+5MHDw4mjx8+3nmw/3gL
/pQvs2JxmM70lf+SLZt13jRTmD34c13hBOXzArquPf7Pafr2Ml+cXVuH/zOb
XYbPqhom6ujklev17v2d9KRq8vR1PbvM6jl2s2ihj29hkP8GfwjDeHx/d/8g
GsePb4/8GHYnBzuPJns7+5PHB/sHbgz/gF5MG+rFv2T1kkYgXX41TX9fNbCO
1uVXBXQkX4SPqddvl1ndnl7Ccvo5f/Dgfnq8uJ7n6dGHvFzn1vtX2MWsKNM/
FPmVG8LBzsH+zUN4uPNwcn9nbwKDfeCGIL2acq/+pcHutNQdPxrYMt9V9TIr
y7Blshq+UbrPaTw/lgXsw6Zos7xNv6tzOCLp6X++cGN7A286x+Xb3985ONix
ofHDNqZncOz37z/2Y/rXHF91HW2vx5ODvd3J3u6jCWyvvV2/wbKz6l/afxRT
6JeO4800/QDrP8/r9G1bvbfBvMlh8N0/0XhmVdmsFyB9WvgkOzur8w+dD60v
+7BPHu8dPDx48HA/3f4hby/zmk7OaJz+Zh82z4MHO7v39w4epdvf11k5y0e+
t9rk7PpfoB/QjQZ6QX1P03VdHKZXV1fTzl9KnPsWJhwF3sn3xw8ePN6RH/d2
dx/Lj/uPHz2QHx/t7sGPd/jh/f37h+mKBN2FfP/+Q/3+g4cP9kE4l00zl+cf
7j/WZh7u7e/Yj/f3tPG9R4/wxxeTZ9Mgz/PZZQVC/e9wxNtJm10cJkV53u33
w4f39cdHDw+ss/t72tn9B3uPD9N1e/5IPri/+/jRYVp+aCfuw93dPej0ZYVb
7e/62c7+AQ1kVzr84GAXX/D8BPbY6xfT3Z3p7u7B/Xv7e3CEDqb4H9qUOIqm
WMBmzv6WlTyWWZWtJqu6guujWkzK/AKEO4yjKqNhZ3B5VShzJ/g//+hPyQLk
dzP5W9P5Hl9/8wn0ddLM8U8vr17tvcIf8J9K8dT+0QZ9vYIT9qo6KxYgLBaL
AjeWPDPPWtiYeztwOHYeTHb35GO5g7ZeFheX7VWO/5u+ggNZlDlcjPbjKaxc
WcyyRfp2lc/gEpvxUNNT2LwN7pv0u6Kco6hIt49hYxb4vvQPePqrMt2d7tL+
pjdm9QUe/cu2XTWH9+5V0OcldTmTHuN2vnfy/OXzo7fP77mOwfjv/WH3r3DC
YRQ7D3b3Jsf3Xr86mpy+ncRP/dV6Nek8P13Nz5NkMpnA8YWNAfdzkrwoU5Qk
6YvqNM1Wq4WMrRmnrHXAf+RCTavzVFWSJi2aFC70dIWt4NQk8zXNWbPI8xXM
BPx1nkMrVZ3C/X1V1e+b9ArEQJ4u4XDDN5oWdJbsHCYzgbZgmvHHAtSIaXp6
mcN1BbvrbJEvGxBfZXqWgyICW3Cenl2DoFgtqmt8CfwFvgFCEx5aLPJ5kg3c
+un2yTMQPFeXIOBRuuCtgW+UswcrBPJx3brBwT02T6syqVBwpU1eoyAfp/CK
6gpfu6iq9+tVg+OFjq3yGpuCvsF/Utia0Hlri0YDL1vBC+Bx6PDJM5w8VJDg
wTnOKp0C+NMcvpyn0BV8ePAZlI2g6c1afFldLekLfiQgEGv4G1yL+JeTZ/j6
okEdc40qWtrwBoYx4t+vQIUqUMWCW4g+ylrpYbNe4Q5qaEj4mEwCjkF3hLyC
O17BkC8KvDnHsKEKmuSxTFSCT8CdBl+KOgv/z83T9+sap3sJAxjDnrmSs5Jm
LWhSZ+sWOrhu8vP1AsQmTsTf1uWMmrkq2kvpNmiNcG+dw26aT3mnL4v5fJEn
IAJBl6yr+Zq/8+lO4X79TOeAZgQ2KvbrmCY6w4bSk+dvT+G16fPyQ1FXJam6
cM5BCYVdldGf4cUgKlrYb+s6T5o1XPqwd2nyZq4lOhPpdj69mHKvF8WywLU8
OXpF03jy+lX66dO3dJvsPfr8eURTZweIv/ngZfXHN0c/yIMHjw8O8MHLrIHN
CBIQbhd4eQHK2JzaLGjecE8kqk5PqvMJa1rpNhz8EZzSZMnCbtJWE/kx3QZp
MoqkAuwLOEPwJtKO4Ozl9cU19fFsXSzmdCTXbcXrCyuAe3+DAKnOz/Oaz3MW
TRLvNOw2falY4kZEBaNAUdXrZNQ9ljAt/S/uhbJKL9cg3xo9EbAhVzgraEaB
FPK7H7oGkgkfPK+zi2IBUoUP74YBgHz6UMxpBDAD6e9OT9+QTfLW+t9er1A0
LlQ6eZMFVk8Uhc+f+TWwSPCCxD/D8gS3dDOrixXLKpjsDT3C65774+fTn17o
lEoAmnlsnCwwfGP6PZ3MhHqGChT27HfVVf4BD7X7FA4IjIk7dUbvvfJyIQk9
MhkVOsFSBrtKMmiJ3QCVqEZ5nry7N73KF4vJ+7K6Ku+hGvBumuoVFW2SWV5m
dVF9wT2VRPdU+qX3VNK7p9KffU8l3Xsq/T/vnsLDCgP8/9VNgTLvC24K0BZh
NtYXl9TP/GMG64Zbp0zaeEpoo9tRxR+b3E8LtX9cHb3h04IWwefPY3wOjiTv
DhJXfEPjpvj7uviQLbBxNB1xpiqWJNLAPh7CBK+vUxhwUVaL6uIabq82/PaZ
xez7/Bpvr3mTbr368e3p1pj/m/7wmn4+ef7vP744ef4Mf377u6OXL+0HfiKB
X17/+FL+jj+Fbx6/fvXq+Q/P+Mvwadr56NXRf8B/cOm2Xr85ffH6h6OXWwkJ
XK964IzzRqQZW9U5Ciu4S1SQ0KR8d/wm3T3g4aPlBtLm06f/RTbQQ7jnEjib
Jb+LhBD/ihOMM5tnNU3sYgHnbAWX8AJPQ0MLV6Z4quVOwulLt86u23zL3Y9p
0aJWe5XO1g1eYnAkm7yEJYYmsrS5Lqvyekn7fKsCFazd0kPTeLMgRRMPzjTe
KNlcTgKM+jxbwqUCPeRdCH1spSek++FGneWrVg9XzRfPupG+0YygAYs7yl0e
NBeRyD6R18Ko1wtQiRfNwPujd6f27v4reRNP0/S0SnSl+Dyj3uM2v5ymVBY+
nhRao/THkxewj+F0gXmU8Om26echgNlNG35gWpfZez7YcvRgIVTOZfN5gc+A
eHcH4zBJPh2mH5oVdO/p3Z27n+liAuGcZhcoWtvkECyyUzrysBsbMta2Muwl
mOmoncCkYP++ke/N9YvfwHY4yxoakG2gBAWenyC4GGBeUNPxiwf6AQuj+9O9
afpD1eZwattLvN5qFABw48AwYfkT2gfFuc5c3Kcs3QYBtxjRnLLUlD5qJ1O8
M7WXY95VF8UHEehVXVwUOGHYCj+Bm5Ce4qbUvlqu4NrCt4T3h2a0fdpUeDnh
S1F/oiMP6lFJTt8alnTDhUeLcEQ3h1yR1AcyZIZuP3ww3ICk4KK4Zq0cupR8
1b6k0zwPPmPVuGZwdnnf0hUFygaO224nmDfSMvAeq9Vgxr/i9+Uqk12ql10+
jy7btzQFNHgxPfDGzz+22DBdUWhbNPQUrXcCW5oUmIu6WpPmAg/m5XxVQf+w
xVQ2M7vm2BuTbs2fBgmng9NWS1a80lVWZ0v0+9ElnpDvvi3OSAVmaTHPUZPJ
3VzzoOG1z6ULNBT9Jd1+/mbE25RELb3en4/Ma4RoJS0K2jCx0En6UzOwhKRc
yXt1qNG7kq72qWvSuJ0E31CT+Sg0SL4J3cWk1OEdYa9Dn6lqbKQdzhZrNAnm
6xpXyG+QMek2l3SVrMsCZp6+TfMrxknWNNUMFo6MIFqiaA/ValWduF/T7+QE
mjDTD2gjpdGztCD4J5qFYJ7weW5moI7TJpc4CS5//wDCdOsys+Ey2B18l1lI
NuXyUFvgtHnjVGwRUMzaysR0nS/INxokTzM0I3jYK3wnKbGkCtpkiGZIU4Eu
FDLL2KJqQfzxsOZzlP7pNjQx0hfgw2B60I5qKjgd0OVoK9C52LqErj3dIvMB
pAhcbNes07z7Z37zb9/hfSzD4I9AxcjzuROy1BL8ukIzRrahTeN2E66Lzk0y
skNfRPcinTieB/YilQ3udtiu9CanO9ztfQ+aPObDZlPo5VI0hyLON07fmHpH
9qqZinxU9NRhS/gkH9jW1mtK3zyiv91trAfw9BJUG7yuweQvSFzAsS6yRfEP
aELcaNy5LRDYsIVB+plVcNN0HYdXfO18hetMbzicuiM3SHXGqVHXFQ3RxRCd
pltbpIN8g63oDiuft5ZnvKGFXi4L0nqwQ6dVtUgwttr9MN0+PhVZPod7ZZaL
gtrgLDUq6lDjAFnC784/4G2coGsHnrqgpuDOXLOYDdfNGEUg/tHuMeok3XBs
k2fzbNWiBc2OTvcO2TB4lkwqeF+Qm8qyneQr2s9p9JFuZBPnrHE1/s4m2RJ8
qUHycAto1enTOLn54pz7nR6fumum7X4Re/fs6DV0akAtOpIT9XrFAh/XHs3c
F28+PEh/QD//GbziWXB4sGdIFR285sGYrMDqFR3u5BnsXDmnaE2COXnkHJY0
6T/Cxj4m3fPTHfRmgll55076BhZ3VqA5zIYTO69XdQHWUbFA112LWwTmCNVz
74RZ5aIYpWinJ+Y2wUkuzeOT9hw+aOuTAVeBPUyObt51sh9mddXAzoLBzaEH
6oq4QkuHvani2AjvhwG/aPUuusWfog60lD0q8mY9ZfgO+sNVgW9A+xPUi+qs
ZZ/U2XXCvqhF8GjRyvfHaCe5KsWLEL1wnOYF/U7O0XXJbigJHfL2Ct4p+RiH
6YYmNrx2shsXSMCugLkSp4QbQtzzYJpzz+42yQ2D0dGjUMzazAu+rLSuOL8p
6esiVPhmUL8gLuEc26DBwtN4rOE7G8TTNGFf3PEp7HO4RSsc1mW2OI+UZNyr
3otIO+oCndioBSXrEp32YxJRMKbcBIKbVvRYwiH/gG6oHypZNVFecZDLal6c
X1PXExeEOYY9fxGUTN9imKR5JSG1agUmXJubK52VtLNs9l4b8H428rGa4zt2
m7GR11I05E586O08+9AFKbGLxZouIHUCnBcXE5IIn1E1TlgEkNZGymydr6qm
IMHVtYnUYcAXXueUYf9o+txg0HfZVOoktYVL0JyYJkexoh/ZEE53Zv+KqLNj
kJqmoqCcQ2cljCNdXV43ZE+hAxik1zX1C3qFtjHJLGddoeSngQdTE40zUoq6
9iaKX7/lwv2Ar1ePJ7a2wX70X07YmHSzZy51sVTkdJ1hbONCtkqTk/0d9GrR
WtjoRIl4lC7zGWzKollGjlp2jq4bXLFuYCAKARSNC7SdRIsedjQ6sZrqHK15
2s8Uy2Jlj/3RRTWXLoMeDWO8pOb8Oq/xRlJ7L3JBez/yejXXF4j3OIuNJtHk
aXfBdm0KDc/xgKGx87wF+aPRlyaheY71EthGOLKiZo1UlhdVqmglcQQte6iK
uumYPmzda7to428NqoJktZMXAuRUwqGrmTVhFmedw7Etg/6sU+KVKq+30F+S
eHbJpB7sBN/rZXaRBzMcR90957ShZKfaEkWuFVZErlVRs2nuXUwYsLEbgvfh
UJAK3vh/wz8HAXHKHY1B/71kb0z0IOMKqZO9T+DJ30zg32/C0z+l3X8/Jfjp
8zfpT/joTU+FtvjJ4afif5PJT9QmfVe+/dNgv/CDn9zr+Wf5Hjxr3Uz1o8lP
E/kSzDV3Xz855mvsZ7/pawdx04T8hPrzF06ubIVPh+kdvaoY2fP07sAVN70L
UgBskqdbi/y83QI1F/auMwtgtl4d/Uf6Pkftvipn67rGWYn2O52Lii5cUmz4
JXzmG3TqoLcAVSy1VBcUvYTerWtxTlUgGMfJ2ToYHXj3w/Os87KElNiayHF2
1+By9rxwR3C0KDQfdxPlb1HO8xUceBwEKkOIN6R7l3QmOGJraJPfywcHQyqs
XsJLnEZvF0bDhhldqeyqdoNLClGXKSZDylbRrlE2p+cg6CekxawyuKFJ+qZ4
whc9DxcqKzClxyxw0ldwRS/ALnl+MlnijxLyek7+4gn7V+BNl8Uq3X5+Mkrp
IQ37mA4D3/7j748tYiIfnTyDT+gLPRnXV3UVo0OXNzlsig/54nrMOgf7rye1
78+8yC7A3G3SPz0/+cuf/jLlTqPhso3Kcoajb0Y0ieajjSNB+UeYGb+MoGCn
RyHUuY3u6C9pghRwxs6UuQ+IsqONFK6WUA82o+k29H9ZIXKTnISk9cCNgNCJ
ZZ6REm43jxjmZ3l7RTgUGSgoyuvlGQWk6BpnjWSW1XOMP6CP0Xx6C7tO3lZL
87OYA0d9CDhScvfBxYaGgvs4W1xl140FNRrROVC1GfImyrXjdWbaCnQ2MFhf
jhHdwAiIMwsUseq7oUH1SHm1DnQgmJFM44/QZ9mictWhTqCYvPRDAba+jN33
LLwc3oJOnImE0DTEKlpKqb4KPH8afdcNAcMAmYOyBvYAtCZmPEzXPAe9dNFY
/OFuE4zoJxJiRfgeLDu5KXk/gPiDV2CXeaTYMvn3W4nz0Xbshw36t7f8sysl
/te/YPRa6J/SgSv1q1vu3DQ3P5Dubnrknvz7M//b8Ng/4/+YFy9Nf7upOWnm
z9Lqr9DznQ3DH5ysDc/K5Uy+4dve/TXtftVA0l34TyX/bnuce1FZeOALmk+H
m6/cP/h1x/Qc/Tv+j7wmrQYGDA8EAVeFF1JLt70uHg0IpPQrx/Jr7P2oX186
8xZVuO0Lqe8uviDp6Ht8ravG9/xEtAURoHKfD17nPU0QlQpWBTapDiK2b9cU
YhTXYZJ8EzwGHKg4yxdVeeFuUPQ/UDzIvBrcI+flKND+z8kum11WePdxWwVc
Ajli0LIVuo9qdISIDgm3RuXgLUMIu+RUI4FjC94EWI6PkSoyhbpj3gXsON8r
HF1mVxh7cngCpEmy2Q0Aqv4fdWRtN3mEvor8DSs0QncP2NNH75hXedO7yHrv
w5stvLPfbzZdUXJdSuTIwUqckoV9c5GgEa3of+Z1Zd4iasR0mEO+gN0kqkql
+pHOtB0FVS7pQw2EJYQP8Ld9pF+Mw8Uc6SYEepk0OcZaULMTFUn0nS3ojQuM
jSVId54hABYmbYvcsAhv+kaicNZJUKoO0ZnCzp8oENhR48YpoZW/ubqsvtEW
OZSKyOMvGFlBZlGk9bjInuu/7775WF+T79NidSyBtw0Hurg+9H8gRRjPB5km
2B7qLjVD8Es65uxYmo/cpMiXh+bEB5g7EyMwbpiYrP0Gh8gO0ZFFxKlfFRxJ
0sUQKNbFN0oo8+vmTzce2BzrRVanZzAX7/NWVNQQ5BbvK801xrd5H7yms9pH
WvJggsfoepWDadPCaIInaLs4H5GzXaWxdHh71o5GGN86VSQtK8MBztWP1rhF
g3mfJptUyd/cqmKIfwP9IPTrz2lD/t2gAd5whf5qfwk65sBf/zloloN6ZVAo
v7Y7oKLAX7w2sttX8H6TwJ8IJqbaDyggkbex00Y61MZgr+y/w5Ovf9+0ik6P
2h1wMEUjh4fwKIgK95vec70FiJS0XuO3rclAd/rL9JX9T/NVurH/8tKdocnp
9mZAhb95gaLfvJXwU+9tO5PuUG54G3VuftugvmxFrI+3mhEbvrrJpPiiVYof
dcOD+zgaXs/auGF4VTA85OzdsExVzwrpmyD+5fi3nwa6lA6ZI/AHCzncvAFd
i8lgrzZ8sde/mx6O1vhLDZAwtK83Xty/8NquEYNhqFttGHY+fpXhEhycfbtF
fJm9lBO7glGb6lkMpPvu4J/KKObSRNH2MWrWMU6v6YVp0Xce4lSd51Wf6hhO
WRNBXXrdw3aiUBBq9k3xkXQT9m+Z+sKGWRkjOtPtrXyFGQ2Yw485+EShUV6M
FLgpmE3F55JtN4yC3N7Cq4/bQtylQS5dZJxUaApWH967F5CXoLq3I2p6UZyT
agatLdqt0Zg+HA7YWZAQ1hFVKVngbVbk6KuMFqJOGMB4e2s+NF73tFfKbLK8
Gkjx0k+fiqzMJtK3a8xLpL3Z8fbypFCEk8Mr0JfdJ8n5mjAIzp1J8YsPhURE
4MjlwQEfg4AxpYujJSF2IUYPa6ifPn1VHjvBK19AH6iRGPFgq0uhkgDkJIdz
UTobWo5UMF5srycJxz/JpYqHc8GtmznX8z0whAO/NcFVXvgQDMzKP/AoBcA9
wriwD/To5w2YYc5Z8zazNB0wE2hrnJIjYd1QTisjsBioMxakzgzhZuT3dXDM
Nlj/vb4FcxpZDlxSxO5IZqY3Rg8hoqWoyhA+wq4n22ih5Odoi+P2EK+C9E0A
cXQilrxwiHQqtKF5QfmosKmxrRGjtSWkzfieJoSjlwZjoDAhuu3fu7C82T20
mLCl+Dt4Qtj/z71UCy2bfyh4bgvJdLTsRswpQexGmAZOG8ZrvYbHKjC2CpBn
H7JigS3wHlEo32F6DPuKbL1Xe69gQ8zkV9gPrzUwsEAM2Xl+lV7nGQJwmI1A
XP9VjTsUwXYMO6rqxTy5zD6gl2SmqzDPP+SLarWUKwpfBSdizTcCmuD1nBLb
EjBF1cdxhnOJkByDcV6x6QgNQLt1c6i5vgK+0d803KjYQAXcoatH+y6JnLJe
6IoKXrEkX57l8zndP6CgYBecnfqvb1/d+9c3J2/H6R+Pn706GqcvT59jdnT6
ocigfURlXWXXYqgikgKu25o9N1cobmuEeQ203LDbKlueFQr6onBtcw2W/5Ly
ctFbhznUYa+AZJEzF7wQCnQD4Yf4iFU0+ewGwUwN/JW3cE6gNlALspoAFTTD
YTL5MIfNHyNoX5eYCbOGC3sR+oAN+M4nCqkfTsDd5iVfx1BbJ+gMDjbCpD3q
LTRgU6zpdPMk8gW0uBzFh5yTCRgaSt5TvvuIJIE2oOGl8OqgrYVIyWV2Qcnj
dtQEQRf6J2Bj3uIfcjjZ6JXk6UzoxEsODrZNCLjg6sGYpH4DVZTzRZ63gqSh
lVqta/TKSsAO/Y3JsioRRGeJPcY14PDS0/QZo63pCFVVO4EdIGlmSei6Ac5C
vqtLUgkgV0Rfdo47TiR6gng25NKaLar1fJq+cXitsQwzQPQEgsX4qEg5Ydjb
tWIjvTs5v2YeAFiSP17mpcdbUfZ+qwFdO/GcoiVeYrgLZhnuaWoJEW91knFq
N12qY9KTllWbOwc6IR5AYmiekHqd4L8fYUfOZiyWkmi7TpVYBg4I4R/QKR9R
DzByL6yaW0+6BmetKC6c64xnNz4Qg5t/2P/l3zMk5Ly+HMHtGejbTa2W/H3X
zSVmc7w0E4GnhqdQ3JQtLlcBQ6T3kaDLZqqJDbxGUS7nBauesmtxQUPiDANs
4UzW7Kec22IFmFhG4FpUIKfp22IJ916N27F3xFS0yvLScvop6sxNyP/Cn3SF
cFGfv2lC/ltVUkN2uts464Ahec0KU0gEYSholnAn/67iJKv0O6XMODLKDMTe
2y9wS9uzRLFXkyAeYNqwwTIStATrqA2CDzY6JiMiw4+GkgrKo++wW4igXTrj
sOnwa2Ba6hwBINiBqQwldENXC66/giM89bqckIAOr6Gdpihumk3u/ZhFcEY6
w9AgkSYELtDgVIfFPOe03WyRzCJkOCFB++8WNR453FoEm8vsDrwNbpsPlIQG
F22NfCP4X7/PGwd0UYuXHfjyxTOwjuCdk1V1hZkkiTFOCMh/mlAncMlEhNG8
VMwQVJ7XGd9ia86bN1oXzcKJ+mLpFXAWCFWGzYKt+R4tvDXbkxVC0TAI5ulp
WF5TFg3qplcgDy8z1bfPeO7y2tJKTLfiXWTmK63gYbq9O4qzdHBCtvdGAUkS
XWH2KWxreu1YlEF+R+Hkvp5PpbBR6NJ3rF2egGiE/7CplxlFTuevD15+dwLy
KxgfDx/eB0PPIm/Mz9N7p/bHL5X1Q49TCI52EhzCo2/4D3TJ+naz+RIkKd2X
IC/8BEVzuWmG8CZscxKSMJAJUYOOkfomHn0R3aI2ZGmJTCvj8qBuv6H9SNkn
EbBLnEgyRzRnynLV7a2/bzmuGqalt/jT5KjpQ48a5mTS/HJksEwVCjcTKYNO
mxiVOE5CdouB4oIcEL33DA8g7/eemCaw8TFcNYvqYk1ZUdAOJudPZvbh55DV
3pCKc2aadntZE6MIJbGc1dV7TgND6hs0n2B10GEF6uUFajFoDl5i4i0ZkRVO
20Ul0ADiQ1zyrsPWOqh/VWMuKzDNxEHWSWui8J5uU1H/wMyUnBFJ3aJbX2eI
lFxKPpL0GNABM6Yy6OTYfR+0sbHXS9B2R6sozyTGXzaVzgC32UqGD67Mag2i
bZbwUFdC93Btqhk9x+xpJPWW+bxgdo6akHlVLVMMKgG9KKFv0GFcKxeW5d64
BtZwU6czSc7B/UNAX7KY6TlEVk6TZ4F+yVSiaECasIyagwIP+AHuumwN60ui
THCwlhF9Ffx1w6qr8MG8EYa0d/I2jAGCu5DIcOFwFhH3QMpWoc9sUXcJ3ip4
EyTizJlV69VCPbXWkd4KwNdAPYZ9IbbLyTN6e/fhIpwRdHIwh1eJyWKv8jaT
p0lDIdWMVUfMVn2fR0gQNmSkJWq/9Coi6A9pW1PKIm0MjbrfM2dlssqKunFK
9lLfHx8cnsixT1mJANkwzmn6/CN3IA1SwW6CpM4lkYxVV4a76MBkBLDQsICt
OsxIAdBJEA4wehyZGXCIiIMhq5ENFe3H24KIQZQ3EFsRrIPd87B5BBJUopOX
uvTjyQ+NEMk92j3YRW6ZhsCajIEAIUmODNVEkGAF2SWxU0YwYxl0PEMh0bPi
NSG/Lc3R0i009pqdw86zfA7iYl3nAYTKxrG4qZVJR7z/OBpxb5jVBhIL/ebF
jM6wmEGd5Cn3QCzMKDM8JIrCaQpKDPqIxUeJ/g843AVhf2k45E7EbUJkUs4c
4ExmPkAhYzN482QPaDjDObFDviwLP+X0RA8fJQuGu6yUrNTgbpp40H9wHgmt
jl79AegkHAMaVxG0CrtdNqW5BTQJ2rRJnCkVO043EWzJHSlWbZOHfsBdo8JP
aPEGWbWaPguRIc8IcyWuaLaR+7xaFDazZYmnVI5BnLwVlBJGXCGkWhNC8NSP
E3Xh16iQ4TUWsibWpflp8QBgd4jhhMHX52RMV0ZV6KZjzIoKTYFYlzlxQzfp
NtOzVATppq6xNktjjZ9NtlWH6jyOeD6MGqpiYWBt1kJ7fCtEKyb7NIk8f+OY
8UTS8pTcbRzx53jfaHIEU+Amt3K0L3Gkkt6N+HKw04oZ21tgkK4qfFDUkQbh
+plv0GORFJfOS8guRAp+NAxLepJI9rGncrKmRHgUq4zsPU3JnjGJIIZUxh2Q
Ex8ImHY4hzjWt7rHaVD4ptAjjZcYm7W1RTcT83eyyTdO4da8rObjiFSLM/n9
B3+Aixd3XIM7EwOlSpDh4P7469s1i1B4IUvjaVc2625M6CDwGOhyliydiWSJ
Mjdb+j20vq5171GygGYwMcWVcgjGuQFurfl6gY7CV3DrYo+qRlx5lHlpmcqM
CpPmdduTFqIcbKhVq0/xGiTaMBubmxQ6behmmrutipsDUZ2cqc18A1c0DnUw
okTnDoDYQYpy2Ko67KKerZdopAnTB4oujS1t1z4FjTcNZrMPMAmFPGKmpRp3
xO3Yh7/k+wPSrBklS5g+TslHoGgu5IyznDM7QD0GHZS2BXIpUmCYNY+WFeei
TeDireq56KyInwyCbGy7BL50D5X87HpRZaaInxGXwbl4IMj7iYxTBRpvmCqG
jWrO+zmsSs9pgJEv6K15dih5XnJ7SbCGi15gskKKUOdtfW2XHHaDhnN/urOf
br8VRfjHIK2fpPfhLyKyR/GYsZVX2cfJEahl2yfY8OTonMxteVxmgaMx0gEc
no3NIzgloIwrgO0fTHfvp9s/lkHtjM/ak/QAHtA3ceY0Csmj/zCbLmaHXp/B
jhVdE7ZuuI9wjplVM9FqI5SjBt/4m9AS9R1JVWnY4HOO7lKEfzR27BKgKK1r
pYxh+l0DbmPHxAupIXhm0lPdwneFlD1qCxuZEAzebYUGRaxBHjgyCmpDRODJ
0dHvmap9mIL1051z/vNfs/Kv9fwzYljgaE5GcGzrNnjv6JxfSSYUfiUiDkAL
iI16nQbPhAq7nbPXnoXEzLLnEjFBjGaMa9vIh5CTHncvJRJckSp7rZTLoY98
uidx9mn+EX3JHEbkxHqnpqChIZMgkvgwSXYpgz6YLNqYci1oO45sQdnm0MqF
NYb1f/EG8VL6d2xMNTVU2sprrxw7FlvvpmoJcgVNX6EfiNIw6QQ3gVxdIw1t
taoCJcIMbBk4yJj+ii0IME6b9QEVNELJxGxCDiKBk3OX5QpNsLMwsJqekTKL
skQw3OXARNXoi5OpKRqajnjc3P0F3Fo6JB+0oLncflE2LTzAsXKMQlMzAzPY
tzki/TgaEnFuOWeA0BaVZv7ao7wdRXDjt7oMuHToeq+ejpK9m3fRsx/eMv4q
bB0JAuX0N7qdkO+AVpBdlDouUxue6JGjU8mNKvdfpRzIjHzgWzOQDHAudHwU
Uj0KoR24u/c3DEThGuZOGUifVg51HAQ0Onn7jDhqYWMsFCn06VM9n1C/JlR3
hMA/qNqy5hTIXjQUwPLU1PRFnG8u03uVXScqrSQo7I+Wl2iGxA9c9pJfAR3Z
Z6fRLWxUSG9FA8mqz59ZBrKNNE0OpilFe5/97vgN0ybirI15Vcl/gXqfpwpi
+AU9L81vlxVPpPwe+EjoNEieQMEn+AruLcSz4Sxy/HGMykMpLEtuJsuOa56i
0w0pQzq7ic5sSMAZuhSY/Du9zNdU3WnW2E3hJhXOM0tsJRyKLa1wU64ZM6jW
Oeyx0DClXkGbFxckCLO0pHxrHPhMi5Eg0PE+UalbcGSc/g3VP2dqD0VLWGDM
WkK+0cFDOGE4M0ffnbzWNdABkgjzARaSLcc4baqJDBBPwfjlXlbCKxb27xCj
d3jv3p+wP3/poT2/rdunhPqs59+8g9l8IKO0G4PYZDWwEaQSNjOO+ElE4gSR
6p5motRBuCmnWympflEGrhJspE+dc4g+ahnpK3vBvz4/7Y731fGz3dvGi8vR
OA5RbCD0mtWgqwKtvrK5kq1OY8EMIjqE/AfuTo9UTDQwpvDMPEKQPFt4ZGXW
/NZX+4e8bXznsZeOZfWTRM45MzqDuM6zpmDPqGPJa1Sa+usmRXRzt0FB2cQc
EjQ49mw+eLh3wJRFFgrqcFc2+YKt2zFrjErWPrssckkYJP1Kt4mFDM7J6DH0
4s70YJxg2BUf5KCG66SkYBoBdHqyhkE8ZNMAtihImpwhT/j5I5bbK2IXsA0a
d/xuQ5d4jrEwBP8dNV5rofvT3u7PGv5xSf6Dhjwf8KnWzEhIKmyzrlmn5P7N
52uiXxul6N9uiKDO/H3kkiFzQ9BlWJgMeowKK+ZlCu8Z3Q1cihARAtDchO1n
r8GZvEJdMXSdzvC8Ku+2UqBl3U7paIXQEyzYi+NXb0Cntry75MeyRn2Ptop0
heBo6A7qGofECwaSJ3yD7F1Uhnmv8vdHtNFRJZip22Eh4M+MXQbKaSwuLB1Q
wkmyTA2Jz/EMRS46q65yMN25n26xgwcpwrGcFYZOt5Lo7esSjzbsjFI0oLgL
qD6K4DZL6jrhP8q1E1zAkUvZqUAZEfxxhUe4iQ8x8fAbKckB8+GK09BuPeMr
hNRcjY6RAuli08HMGcsuPXrtrnH3Nonn9yLFccmAT58cZoYvm809RP9n1EnS
JPrRfDONR2Pnhsbwgleae9r7YP8H4uJfNADruI6Er11VGl23+KNukLvpvqar
VXa6K5tCQaIDjnEEKOfNZegZNNApCMGB9Du385oi+/vR6xGY3KQjCh/hl35r
ltXoFkiGAXI9q4AiTiAdt0W5OZpj0A1MYEI7EW3xJn12+4dno3HSMNSMI+1X
0OIPb9+ag0sDaDvI78/58Uy7VsR8o1iMhqJE7Ojx2D8CqXfrpYjiHq7dhERG
tljKLcwXfM/UYpAkbTuMCjqUZKB+c1RG3GNNFaewf6QKJqwKuko83pPJE87H
pdAMD1LVQ1rAxTrDKx0FAevcifglY9SWLJfsrmkaNONZ4F5yDMxMF4d3BPme
0qFGmf4VA3tK+8fB+XnIE3ECiAHrpd0X40SkLSlIDQ/fX6tT5dGEJqyixaEk
Je8MJIDtDny2N/DZPnx7F/6ynx6ApvAgfQgKweP0Kz5LfjP5hf+XcD7eKeLy
6R/8/jIvL2BTPoX3RamQcHCZW8H/++lX68PAvz9ki2IOerbkRm3691/ahy/8
B334hS38F/cBdrSK2f+xPnzRv1+lD794PyTfF/lijsccz8bhwFtOv3u2/yhJ
+LT0H3g0OStQ20RydAkwXSB6iSTego9Ydb4xu5R9xZpJAuYyx0gfpVjRqJlu
/N4Rg+n3uRoLnddu3+jOOsfhkb1UMlwWvV0Set3YOIPBLffrH8iNIqYGilsG
KW38tgZ2YUKqOhgpEo1CfTU+76Hf+3u/cDJRehBvG7rcKRKn9Ro25/ead4lM
B+LREGUKuwuGEmq+N3wbng23CNU6xNHdsHKShyiEIDy5uOzbOx93RmYSNDe8
knxi0Xs3LyV7nahPqOKiMUiM9Sol4l1DmlNP5ZrGGc6o5GmC861aXi/B+Q5h
M4P2G4PfhiM5HW1Xo2Pk0FL1jzlfVMWAXSDNi/fqwf7nz0lwdhlIDp3U7/4q
ZYqnf13PV+/SbdS50P4Ci8H+Npm3i6b7AFHmpc9OX74FxdI10876T50ev6EE
tNAiNTj4KLSXdKsdhdjX9vfi2/xjfva2oh1rqCKLeBNuWIfpfKqg+sjMRHUt
O5CW3FdIZS916J69tlFPzEiUJ/O+BHCldEC3NR8zHyPUclV5+vbkD2TE1Mjt
rallyslOiDAi9qY1UwJwc9RTcrmG9lgx1uADwiiC5dO0+UpKedmHrlKZ9J9Y
ySnWzt5AZF3EOndRjogMkjwshJ3z8bckciVy0vJATWxNB34jMXVlSmV3Y4Nn
tfkqIA8ZB66X93xYuk/b8/RgZzT9wrcc/Ye9xMFJOigZCl5fb34ghl5mw0Cl
JH6zRNvRkSd6v5AhGd5jgF6zkL3sxo+J4DSMgZaGcpzgxGxsSzl/EcgSys41
vq8fqkJMxDp3gAbGp8OmDKbppzthLybJdxxx9mwGVJIgcs1R2KfAJHnEOxE/
OfqWRWaHMiGJHpWQKoDvJnosP2YyNOHMEZjl6A2TsroTIRwOSZQd6mJ7+F3K
RA9SNji8HWyLv5XcyEmfEfDiMiPshL4QnTQsAfr+kDjW/5mK+fS7GWFvtLSV
1VJ1kQsJJ3k/elUnGs1AD7+61WEDDRDxSfoQ1hDrABROlVUrsYy1GBOtCG3W
ErYkQLClGZwcvmBWhynM3/scS5jA0ibxK0Lrpm5oWxMOl/75m1BPrlPhNaF1
xA0RMOoegycN/fmbwQYyZeyVBnwBlx9XBF4hKNJY9ELxm1JwQ3FzmWGMcEKS
zCPJMT1UQjjEgQ2vONe6sGGvjFNn78umT8JWsG8Y774eDhichD3Im+pnVaKd
smUwuDTgWuNhhT+40DZNFY2TQb0hTRKdP5YerT0JbXhMVce3ogwMy9nEb28u
KhZQRBoHvmRkr/nXRDZPFOJYuBBbRIBRtEJA2aQWoaFM1HDct2btVo9XzpVt
VeYMS/ldVFdTIatvqJfi22q0n+TgQZUCNhUhz9t+j9lBFrJW7QRRSJbgsxZ9
jYhF2M/GNVMbPM7EXkLpU3rSg6zTktB6dyUSmA6jpzcNyQIFrX/pLevvcolW
FgupBMFRDNgrLpnc0+jEXJuUjI25zrqMVrjOlMpILSL/ITNcR2SNeFdMsjPi
gqBIylKia2JeZD7jdJroiobTJndia7QeCPNftSwmxBJi4hwBXcv44Y5FvHTW
BArwAa5uDrsFHCcrngRJdHcHtUA4P7yxNXkq9jJbVDFSGXEacVP1cXMBvyFa
qlUMloEzoEiogMSethg8we0ZTycPZJYwhVVgcDAK5XRcq4xpom6HdskWFFNI
HLlz6AsemIjRsQnLE3LYLKAoOU/CmE5TqvD367xNuEbaKpdZ6+vVOp831clS
OnQtBIUrkYRUc7kTHAdlpKRQILr0I7fDdSpd8gAWRRViz6/JF2K+Ytt7Ah2P
XsqYaVnUsI81b9QVQPHaiYsPkwclwPii1OycqgCoPlR40EHWSCSvQRIcPmEg
L5kYhSw+mNbfk0b1wmtUXoXQqPTBODFZ6LRxd1TVl2CkCjfJHiTKdbD1w+Qw
fQ5W5vEp3gdScWTyW6xIlnC8E58AVSlJPIwdP+ztjk/f1u3n+LkAd8dvQG8O
nyZpeti9j0WwqNoQAAZKGWUK1HhA/0HUQ+dTuESb/rMTYhHDcuGm+mzB7UpC
DPsHsjGnGkAbzC4qT6S16CiJjre2pZUpWzRn/HUiuqYiMQkswzgqkeC2kWB5
BPqPPdqjwLMYk1vYgb2dnXTr9e+3lEsExn5Dd0NBL6FXYG3M1b30UFb40uyS
KxW1hPF1uD93/cXDUj0AlYMmMnbiWkOhjlU8YJSd6wYRljWXr9DNbCHyPpva
2G4+wxvAz/dqy6PmJpJYyYDrdVHwGTc/KJ0XJfqOhFbRbJrYRO3tlMqFi5nJ
tY5XMW+FkIKTQfbMum/1Fk7yv9PhSr8cYkSeYtkYsi8ScTocJv8MU/DbJ+Hp
J9TRMX0uZ+BevvJPhJMx9CxMxtDD8DE/HTyKsg4TRytBrsWt57I9wh/yj4zW
2Uo/37yXyPbMSERHRgBBn0Soc3oHCeNko3LJgctOWgynTxibJWm9qLxKzWhE
BXY4u1m7ZEk90FjTBZ5palH6cLo33TX5rvly3THZldZVjamOSmAUO+0q3266
LEmw07+DnXR7w24eJeESdylJWXr83esTOk7/9vb1D0HGuRu86w0jsTf5W4N2
S7ItBSQlu75cL8mxprVhGokOgEIyhsuftRVLfcMenH737MEBdQB+ur9zkGai
8OJJrrPzVrjnnXAKJywIg7CdJUeQZ477oez1zEUUyxSGZXuXpx3zQWqg6gzb
MRIf1yd8+X/rmd+C9X5wf2/v/tbXnGf8Fk86T/jWExjSlwuP3tdvkA4TTGG5
TUD4E9L3Q+rxIDGCrvQoA8sRDzEL29n6Ams7dHgoMI8KU2+YClEqIQWKea3m
rDWzWg/H572jLIqzCEer3hSC37KomtguwxfA0yG7KrhSNd96HE4y52w2Lq04
o0JXsnedKhmU0citZopkV8Mc6ish3ojVAmEaCdfxDfGFqHJtP1fQ6/hMAdn3
8X2LMuMMHyvLSbvX1hdYoGuCLXEZh/iUDByMfPEUn57g224+Gpdti0cMS15e
YbEn2YdTWIF7yOyAtcH4lE5M27i3O905y9ts97dPKB4Xv663pelPG28928ow
9WwZEYnYxlnzfhgrT0A6ZiBmxeyTytVfQPcRdA5ZUy/I/NUQE52MoKGws0oo
+ThM6hLzcW+it9lV5sONOVO8U0gC4HIPweq2AwFfr6uqpUXvyFKqNpBQ7d55
AfIS8zqo/nrEo4g1HoQZx2qlsJpM8KxhVsSEEJHr0rxwGFcyUCUm53t38ac7
kXsNtH/yUXdh5762p/joA8MvVxpHc+kUNYbE6P28/mh+k/hbfnk9E7MeXQOp
afVLdrHgffzmNVh1ajmHiEJQ5dk91HQoFsR3gRSbxkFimrXkHisYV+0D2Vk3
OvfNuog1Axq32UCYNVahUYTGClmiiaN467h2KSIos+YKsqLcCxTJrLZj78eJ
8TATZ5iSAHfmndHnL9rI7KIDIdVuvNuuUb8uJXZIBqZnpUM3bdJnVTbalpbS
zKhMLGV+5FcbiKFdUV5yh6H7uiFDQfeelonV5FNbcjLv2ccKxohtVclVpbK9
3RTlZtD0mkZnIwl7Jq4Y/B59fBmVVjSLkGsFO/+PWFS6JGGZeRg0JdEo+sx8
vvO9E2ITZ7kVWJiWe8Fjc8lDMUlEreWIo1MWP5WEy9OQLyqljW0mMBuIyppp
HVKRHFcFnFjz1pAksvG6TYQeNlRKcDfhTh4F1zZvnWALDM5B0zPCMUGB7dVr
4YXrfFHCXOQ35lgWu8u289U4nY8kvIREPMTATgESHEP/70Pna2L+MM9dK7Lq
mstddrckem0GDggybQkd1Xz6y3qCjtOFJG1u7IKLnjAaISyTiqKhrwoOf7WA
HeMImTqVAYYWATFFGPDj48JFjUI1+uH1Hg84rbc/fdKfkTIvUD2S3qjVZ10q
B+ahGAcl7U3OktOMN3alD9WxJE2ReYMDX36FZVLVYzfgzmefv6TYRFELjqrS
56xLNFaLCNuCM9Ze61/MxBPtmYgR1ZdOFF8UZ4orfirBNdIUtJecq2e3FH5j
SSAAtctO1fSUNkGzucC6C6ze3HSvjBNj8bXUSBFDrtKwSNN32NI7F/DhMTOV
E6pzS/uGLZMsIOlW2Iesib5Cz+E8BuZCjoBQAhNFYiRRNXgrafa4258+SXAC
l4fXHKP2qFwhPU0xBUEZyP+LcpNDbDRO9NidVXPcnCpDo/jTS4mExGXDu5L4
y33rQ55sUcvEg+1c2Kg9JX0n9qff1PPPn74F2TIfL9oxLtE4/whdmaBrqPnz
N5+TGz3ac/No93EJZD5sIzkr8khej1S3a7oqZqIIxhNJPdZADq2vD2BR0SB5
4/O4RMYSzi9snfh17v6hp4htyjH/JwZF1BUbrqgh9c2OYtLw0GanUAWlDmu9
M0dudvr95BELEoHRgDybgV7Mj4w0X+CDTHFKBPUNZZkEjtD7D314ZB99a5zQ
OjBeGhUmxBgiAbMlLjPcM+rxydnl15D4YkG8M9nfxZ20u/dwsnv/sYwem19m
H4vlehlgrKxShUMNvzzYl5Hq0AUFzCXiXKZEJ1MdQXMXZfGPPJ7koeDjmtBK
HFDyJVto1GNT3sjJpllfGQoD6oI40WZEX3rB2mV/Xc9yYkgKFUdU92N/BlvH
xbmPm6JO0bgYSadbhdVVj0fjSQA6hcexnpTs97dSGkX7IxtcKqaYUGOzU1/M
RT0Fgi26RHe9iKeGLweaOnpWABdWHyeeIEkEcuun1RqlAg0dfdvkTFtUxSVH
0Nr2AeMR10zCFE/0mSJSA29Ct/lkqO5QLVSRALFgY7K6hS70PLwn1eFL71hY
dM5yOPxc24dDuk2Aa4NNoQ6P3cnB3uODxw8e7j2+P9XNX1ahfA7ZIuRtn4ej
SCHXDm9ZZtOrMChq7vEO/Eu39+6nl6AngTriQHuURT+ngdENLkMLhYCibRRt
iSYXzOqNV7+wSdGmMwFuepCgbdTRwmZ14Cahu22FSNS57GK73zplidQwID96
xni/qPQD5RpclbzoKsWN0IA8+TYOpzfhIR0qmG4EbL3DyNlf/uC0BgRR7VPx
wpfZKk+3+kWUtgj6grNFOBsi1UJAMvHv2D7HrspSouyWoXMgGxlA6uxiGTEp
0jczljwlGAGsQtrw0NFF6ksYaMqeTa4hKmASfKzxuleDVhjXEaKNdMiiM+dA
saIgor1Do6dhO65+QkmPO6ni3OdSkQ8Mg77BbuAwkG5rnSrbz3yboJmAQ2a+
EdMTz+hXNNTL4G4hv6/2DoQRd5taDvaMXpVNugXruKVgv6CVdhL3GRHjh7go
WmL/w6FuHW5FtNME9sdxbzNB1VXGm93P291GDz/LxzIfsfMZ2V2Jvd5F1Uwt
eDC9L0t22pX31IypSew2ib1ilHFDpUYo9xKWuCbDsL22jHCm3uikS7ZVtdCN
Muz8yzlCvsKZxklR7HtUIYQuSjrJGotUYUTvdGPpn9KILEYSRtQ4QNkh3Tty
PVNlQHNDKeOex87ODpTHncpLHcBVEfwgfIA4k4WzrTXblW//s/yykOq2BEHD
Lf+DdFBzTk4xDUJr8/5wdDriq5HnJIwuUAOQgNPOWOngniphy2KnxkrsRVwa
L97org1LESmR6X+i0vXC1OixHWYVwNyQ+FvJ+o0gX8MGT8hXku4+d9V5nK9J
1Q8atsaodBzxDcG7lNfW1SQwuHzbKw/TbDDV0OEwYC6a6l11a1MIXSQuffAJ
DTiLjaH7JqNU9UZ+AbKhhw0mMSUQVe37XEJKswpWz3r3z/9rMiGUS3bNJDvY
qXWp+pFHJbNCW4tyMrdydh2IlTI8EX+GAHFhq0wmvyUjLViQqngceeiW9yO5
kn0dzTbKGlhlZNZfd0SAbgkOx/Qc02nX4z+NDBDetldZoLGzlu96m7vBEiNM
bVS0ViqGzr2RLyJKDpujutSMZtezw6zTdOeUnEfwPr+2bANS6bZBe8si+BD3
zfAZRP0l/ngWRnBGYpQDQbi+BLoVvNb/XSCu3XTrmDy7cwFxuQ94sV+KO2Dy
Bs+vJJPCo/p5eknEqZwKmrj8zI4CrR0Urda8DEbUmzasGUZOAHO5qh+frEcF
NSmclvC96zNBWcPXuhTBRdOVbAIa6/nb+5CNlGBghuMvAvpMinMRvR468kOs
S2IN6aDehPvrXHEBLkQW+2iT1J8hCVqFnA97IaMIFuw9p8dg/x12K6Rqga9s
gTy3175pc/oHBza9m3IUmjSOGjTG/jtX5neZJYnYgTZ9UXSFyRPxZ0fVWV0X
7B1xEKbrxOaNnwZNWOwXGvCpd13ZzXi7ik7ufkNU4MWAxvMCpWcIDnrv+zxU
XYkiuD9yLCcUsElIE9YSjq0/S/++dgR41tmzQO/GLq7AqWunJ0leDGwppL2N
tocFVmAbIt/pGAlB4AqBnYKJ3TSDAwS29h5ZdyWsxUybQFmLsd/1ck1eR8pw
mxHzY6RW3o2dSNYNOLliQVHRoazUWG0ndcrWeCvCXG8RDpwA+f5CpKwKQYy2
Gm0mSXgJKh7WsSGyLRGzs8uqMJJ/esdNVK/8ymlyTDUIMw1ct9n7vNQCHFSs
B1uiOKGyLLGh5tymeVYvSCtjtiJdSHyKoeIb8jtoScaJly0GAAiUSFIWBvkn
bRmnlCxZcx2zZSFBDiQQw7MHG43Ypb5uKowNWkcuUhi/fnVZdYOD2NsxVQqh
VeIooJRjdYflFvhux2IxmUAewS2kWN3d8jHPBDT3GGywGek7jYXH1r16vpWw
R1p74UCyHpIvtjufNcf88+lTD1lG6TIBQkSgCUHa1fMIAFTPv81XT2lIXUUi
PdjxADupLXMPieEJ/4Y/4Iyukcn3SXH+lJ8YG+Lo6uoqBhtFLaAopPDW063o
L1tPEGxkeKmz64Bu2k1FXUgiReEQ4Y33Du7v7faRSUbvHUOSok0jzxBSiLPM
UEV2cAvNIqDiCOnvRA64FaO0H4w9hMtruEQDKskf8rFAeVCIhCoQfskSWjK/
Ov+Eds5Tmdk/7e3s7B7Ozx4d7h4e7v6Fvn5vd7qb/A76gAEZP++2rkwLsgnP
/T+/xIkOg1TD7lJ/wSpPsFdfstR4CYeoXFgC2gJ37mAJRzqIMWiK6eoZTkZq
YKDKUvB8EAIMs1WkDRfW0pqW6xV1wmw+KSrTZ0aLkiCR6Yoolq0aTkTVFaAa
tAmHhkCkzZhmGr2ndZnRX1VtI7xw4GVYh/Eqp0JYfHPCmUqoFrfE8LGoImGN
Lq/5DeoICS6ogCi8UtzdnItSz5XjwIbkstXESI2FONN6Om75S0ucs0VLFN18
pUyfZ3mUhps1smgVR+6HrtAQsc2aLm+Cy2Y8vYz84x5oQADwQHFvIoUuVbE0
RAPW/UwXegTl4RoseDdLM5scF8k3kV3Cs4Uw2CZKi3GUnZospssk3oAvyWQf
ehcmqktFZilzRkgF0m5ENxwJ8i9xqeqEJojmv56/84GKXgeRepi0Mb6Dz6q5
+epJ3HrUDPrOJY8GjIwL4R23rZL0GncRPJdTb05C+d0jaGj0oLr2EwzjDEJv
wbtqFap/kJesP6tiEjcbbqQIgNifAjZ7+dQpSbyUoIuboZT/rpzq2bk3xZAo
hkL6rQs6xDPUBXYQttY84qns9H73mhFNTrgJeHBSxtxVNsH5JAbpkomH8VIA
2cd0HGX+sSVdNMZl8w0d779vF+3TBzs7O/9kOtX2D5Uu2qh/b7Ec39Ur63ti
vrjMFuemWXjsdDZUMIWurG8UeYkGZJE3g7PoEzc1PbTC4jI55v9LiQoxuWWd
nMr8wmyp91jIGkv/zS7zcNZ6bWseM9u06CS7ILcxumOYtpAdK3TON6+T+GHk
wEerdjtMXtMaUZUdwMjfqvCyHrNp3fZuArq3YUGMoLlzbdPSpekfrTqBWV/6
bT6AjiUbVJYPRbVuaD8i1JynKswED/EgPaaOzDd1fV+7/pYC1j9nz3EsPiSD
gak4G0atqq9Jio8ESvUBn0OC0a8Z+tFLKwIa/ARYwhlv77HxSghtKLmecUeS
3zJqAoQuJnNRxT6mP6CYIBvJjth7mpyEX4Kn0Lg5a3LufAlfiid80SjhPJqS
KW4964SUXiaoBTyFNURiFIDJZNyOVZ3VBdq2oMloUkCL4D1iND45epVWs9l6
VZgbU/nJQ6+lVtWlkOvAmHhCuQQRwzEtIkjlDtmRd0mB9BlHxjq5cMaF3hcF
jC40XuVUUu8RFLgk3zPVCdYVdTE5fpArP0VuXdl9A8Xwfhlu7osRcx25H7Bz
XdjcMGpOwti8bvhzlyl+UP+nQXOUzyICGhIiOSeWBsrn/i1rE8LT9oSVXcZM
c4FRb7CiSoOghAn+NDk9JkwhwRXoayyYtAgLzy85xaZc7A4Dm1zlXB2YjvWN
gtkf8kW1WiraiIEZOk/9U0UTPJ1OP7+jTXiWMzyDIqpsFPXR4D8vSHGQbons
3EI/kdLTMbAnImcRxTCEC8S279seLdke9HnF3gJVmQPdsf8rB5inqDxo3tIv
JlAA5YUCgNZRUgEv6mx1Ka5oKbzBya9nuQsVtbCrnyRUUm5JyUmC39SCJrKn
qVXKQuHaT1hnDzPa0YOi+cNTjg52jh6MH47e8zdJj2/hdsKFnjPvl1MM4ML/
0ck/gSxcd7hNZnUu9cXYipdyr5cRuq0vDsk9TuKVFaB5jjVZ1MHnM1koXqiw
C6pUXGAtJwr545eRtE2RIpYr5LzemMtF+ZyKVFhhQb2yTbumQksmWBeCQd9R
QpFB20HriYFWglVNtRaeuqA9RbsjpKu6lVjR65ZnzTUluqNOKmklhdZo0KzU
GyQ+hmqF0NUIcLRDz0EbMMd1z0qN07dzeFbzJyZtduHO0N70wIi1WUGgWFin
gKFkrzAH20B/WT2gJfu4KurO7aku96mPlfeLkA5HEQN8Jf+IGCjshOBOyk5W
hW2zIoQbhc3vFLfchJE+0Xc+3WnDn2KGriSIfQ9/GKc57p4hX5QQA7UVrHX2
EZ3o59pCT0sTBalTIUNht86jZGwwuDMp1wPbh2upBp0Zw1kl41VbkLSoPPkK
a4LTWReLOdO101Mj1VoSSRTehIniPo5TRCwSu99xhIo6rapFun18KqiGCDKV
IGRKqoMJBSSyunGdGkxDpjvfUg2XORgEUwSk8BWukWGGro09SZsxi4pB0jPB
89qml5AQ+Bcj2aMQDb57y+drDFjwN7stiepecDBnVOs0D+wkt7xN0jBIvMrU
iANuQ6z7UpJDxDAJ8XN2RMevc3m43Cq5hXMjSqXRXOVn+Ef0a6CYgv3c4he2
Qy4ygS0lP2qkYwgqmryM8DWqrp2f5zMHNAi8ht0JGMKg0il93ZMJ0fHSeFqH
ClZXqmFXtNsHUVoiM3QyYqD3/kACIZLOO3wGGjrLoyYscRg/PD7te4saS0OK
UoiJAu/IJf3KlsL55DxQf733NOrQ63kxd1mGUmCdEB4M383xrpopiWYn48yS
nUqBixgJFWbaFbCQFPB3mgF2hBM/NZN63hHoWXd5j+yKGEaCb1y3OmcAHD8g
IBKfxr357vDQorhGdQjzb05M9flmoCzmotdGuclbaJhMMmQf2upv6pDjuLgJ
Y3/JkZuC3PEiKR1KWpAknsPz2pxiiP7NlV/J5UdY3rJj4CrKdR7BSEW5q26Y
Qr7ZO1mnOJIJ2ldolddxZl5eWihicDnxEZE3wSU+MHWqkhz9R/y8wLpvWnLy
oQRo0UVWn2EO/AzvR4kIDWFAPEEUv0eWI2YcdakiIL3VXCR47SRcQMP5b/IC
X5CVMFgz5DZZ9LskZYiev3x++lw898El39/Z0N51JdtUC/MORLqgb31Ju2H5
2bfVFELTD3+hlYZuPUk+fTK0BmiUsRjm/cD+P+IVkQn5UrUPXxyuYKYi1XJH
fczQpzucCC4uvG5WuGHdrNbB8MbU3egSy0HrGsSBYX3Y00oJUR3p2eYXcEwo
i4MSNx4+E3fS7yHJGUFA4CqRjhNbK/+4KUZCKUYqmMYuniFKGSiXb8LTzM4l
dd3PclIn2afgLq2kg1vMtD+s+iPze6dFYZFqrbECedwzqilPxtE/TGYqlwVa
iJ3smQAAXQZFPeo+9tx6BvK2h0rzvfXYBix8NaT/dfCBNteWYySQrUGJL6tu
eWQJf30+uvGiIGaxUMn6HM3plnmw3y1al4BMDmcycgPc7bZwVZj/MA+Y/dtP
JAq1zUWRGoQsUr4beV2N5yhKxEZ+AJ+Njb9jH4cEZ29VCAgVBA5+X3jX6XDp
IeVsIQM5fr9G0AcXyMvquboetB0xvAQQbTWfu/z5QiZAbTaBE4JezJUeGQ4x
t7KFqtx3blHJfKVQ6HrFcWsnvX5FF3CUOt31A/cTp1W5+vzp25+ROW2qmeDj
fWq0YZ67ko2hIjhBAcsXIimEGBfsX1ev/B9ObxzHIaxF1iB82p4kwG7JxQz5
Cd3L9eajAw1sn2dUbxKOxAxrsXNGpM+DpHJByc/JgtTziO+353MCjxfNpR1r
SVodOtpU6wMPLNl4IUemaBzGw1InJVDPGRUK9Bi2AV0edZSPiNMYCSZxMwpl
WbSJRJhQWzY8l9JJtHCapSmdiHI7HYSYO2JwlI0rdkPXKZkkb8OAhU5hzUlx
+Kczh3DWfRJ3n21paI0Ye9blsprTwf/69+IyaTJeeLdwW4Qk6W7y33A2o0mq
kMcoK8LrEA1i+uvkzxw5RH10OTquBZfI0hInCOUgontd86JMzE99WoskscQJ
Kk1nXKGuoz0xpthSzWyRqIzoKi44q0e+PPBNy6vFM/I+v5b0sE6MREEhZzlG
YLH0qKo/HAIma0XIePsviRUx6hA6Nl0nrijHS0suZFRakhWNppvb3txNtfgk
Kcxqji07ioPQRFhZFDQiBJtBDFyZ7Gl+dagL1XiXg6hJLilXvjZV0grKyGBy
2OIDFycmU52oJfDl8rqQp2Z5HxwlFHux8POhiW9UURf3ESLU4FkhgIkKrKgK
JhsP0Xsh6wprYWhvxkoC0FYLUmPE5dBd28HkpxJRa1g+12A3G+JDHYzmV4UG
OX8JPvihUjTJlvqj5aSTxLJrmSkL6aChJPo+KxagX2HDB1NuB8skgeilpg/i
j2KKsrCjyekojmu0k0nBp9io2OSjDSkc0kXK5EiFEOQqu/beHt8jxgYMJ3mo
+u7yySiONZTwIRke91x6hyR0qMtqKSlKZmolG01Eud4xHgmqa0ceorJ8G8z/
Rg/okHFS9hJqnQ3eJpsx/y7nSHpgih8d0QBt7sP2DfT8JeAe1aRjWJKqUV2t
+ou4pwdnxwTDf/2EkHNr0Ji/yUHRiLoSRsZUx8TrFjO8bOer0VP9aBf+bArp
9qIdPb2/swOfBV0RNcjRU0mmoARn5Bz9eD2pFjHq/huvDYUcDfnws0y9jqxp
s9bjxsgbdL5g0SR6iRdhHdiXAuAilmPMHQgDu5Ej9vbx9KH9afqrZAiEHIGv
7MRWoKb1qQQbDsUEF065mld175BISFp0vExsfL1WfW79zz821KZeZralEEaG
Q29g7KCM+/Ee3n/w6ODdAOxUTse3lBSy4ctfITEmnER/Q+KE2ehZG5j6Nk2M
4+AQ55FQe/66G3ZgzP9Nu/S2N/+SrUlZRIN7U+MLt2zNnuP3BJUBkDFI+0s/
YZ7Tor2s1heXXcq2hpUIJIsWmURWELrvXWhBr0TDMhR1Eryjt13ZjhVQlGLS
xakQmoP8kiWSsCVSaAihIvQwvPTMlQPgmqOWjFXCOVy3kzmYJ4FuDvNIK/R4
ktnOl1KWyoS4m6ky1A9Sf1h1NHiWQwvwQOKVfLvxzBnHLf6XeKG4Czf6of4P
cjf9Smr3Xrr1jHA2G9TutavDh1BiTlCHZfov0rIDGnZA2x68Fxq5GCK8M2+T
DtNzdABISRpWkLzC6ESqbNG+zriXyhT2ZZD2pCNz+j5YeZBkDAmZ7/tBtU93
1EULIuaLAUxakM4nS52zA9qYN8epO+Okxr3FKHPx5uj0+HfpNvyNfhqZy26b
YJCPdvf3kBkW3XDz+VgFTlWbFN3sdUbm3R9BuOJFRQZ8JlUVDfkhzoqIaqDo
BvRjCUGB1jAdZP9y5COOQurAx0EAK9DA05gaxxmRPKCri7INyHjRLlkwUNMq
NG38050QlIRTVy0dmMpq/2I4kN4QwnniSpF+c/hS5Z1YucR/Sd4XPkMIA2O6
KWEMJnu4FVhKRt4Zo7k1flu4Ute1aB1fGA1NWLoI/I0dLRJw5yQ7OdXzAhdP
CkcSDvEuC6FSAmKMC9EILg009KDw+aOonuf1kiY8TG63kuFtMEPMP1CiYoof
LhRNwANDgCNdyC6MziFYVxqetzPu/1ZXJAmtKe6K2ykEDEf8E5w3cW11NuWq
DtlBlnp+twmD5LQBR8UeYy3Zl2iZmXVvA1LFSinOFyciFa36JaR6F/bNo3+6
ZaI1qNXpwzTZfl0SnVdDmFqt0nxl2CE9VaFXRcPwXMJMLvIPWdlxL2DxiZwR
uQRyrqyeFkOtYsjQdETn7076XKmntK/UTy0cDRtOsPu4fuVMMiLqDL/FpQv0
Sg5d9ZBHDjXADCI365jqc0q0mYo3g7X7v/8f2CTbzdr6gZ51mHH9feRaBqUV
1TcsgcKCgTGcTizILTXj4OGiokwGlswt159al5SfmCpABR+V7LFlBXMP/3/d
6HO8NSmkbaXay/xDH1Ej5ge2i77ZXMDVA7KAQh8koyVbFnTrib3BYwGz1p+z
BdWppdfgW+xcZlq6lJy4eg45rN4iY2kjPHLcsiP9Zbep25fEBFMyG2alXnXo
w9+k1AfnXB4g58GPpSOKtcq+fAfZ5PEbJaRD7zHn74tzLZnjicmqXqEQ2pX0
VUkCYGZ4KlIMA8Fxo/pjpcHQE31efEy7JbyQHAtOBwPRtA7c3SbsB9kQ2mXh
lnWJpuJCsmvgzMov1FVjrkLVnyLzJTE23n7OqwctKQxJQoOpoHJ5MkUfIR+g
UL5fWhVGeiPpe9YgucYvqhaOLZL0kfBAuGrI1lOZoKP1MMec2PApOeMFRwG+
QcDTN6ELlIB9XltdX77V8lU1uxRWXcX+chn3TAP1K0UsIAx6gczzXOPIQl1L
+Kwop0rZ5g2CrTeBuOWYJ2ZLg/bk0boVN3+0olo7H9Mjyvx+U+foqcWLKmzQ
RsWDbujGyw7TDJWmqIzuF+N5kaofekzr7knqnSPc2jhXhCyjRwZyEaVva6wS
LpSP0h/juaevutGkTriGcAllEOvtp4BPgrDD6hVMis3FjQOjAx41jJ5gNqAS
IkZvIolTkH50lrdXuZsBKenAqWV4eNd1dqH02orpbWxHKw4w6iZeJnRt+HKr
aCdh3hMVcvvGsejRJeCVNeVIGtr5BOIMumqAVjIdbxTXpM84B4XjAWkobjnY
tiyNaG5BVfQzQ1R4grlzC4aZbJcUIuzoKVO9wNWc07t7jSCrJAneXQ/yC85A
lzXWCJeSEfwJssuJEMHWSDEpUebCynPqq0sEBdVjTTUfur549cjc4D9ctE8f
7u1ocnTvmCT42sN05+PO7t5+kmxjpjxBaTmX26VvjpKbmo+b6bsl3d8P4DUv
M8U/wwsxI7aQqkDE8jXn6KfU1KjKiwkqjqkQoVK8dWNvCBrSed0N3dk7eNg3
mIOO9LVxFuGD110kthHtOSfW+EA2WgnjmpVsTeShc70gpMul0Ph9ZFnDRWZ8
YUfTTjBlBI7alCqBPUtfsj8RjHX64TOpnhqqlfOiN5vLE3HV6KFP6pUMDi6l
6lLpaOyL8XNJESwj8ixJWFcY2wmsIhTPfFZRkzUYsKr8UrgkYZm2rt317u4+
NsdD1NuAaezOoaKe6GvDKp+eAPWmop4jtGvZgSjMKB8QkjwPI9Tmpa8GjPtI
FJyKp0j46uaBjNKqjBhijUxMsaQRE5hBG6ksd1hSMsx1ynkjhSuFw7jKdSMu
0IBscNZq5IEwDkncfrYHsCxa4ouYSB5HcBLKujtWFfa1NM5ZgpTXsG9HSYwb
F7WRKEnxWaY61cvYIzfkJWQNyj7I7B3x0J1meeO3jJbJ5a8zXQ9/iwu5o1K3
sCSejIFhVq/NKuJEtcEczR1yceHuZwIV8f2TSwduDoJwg9T+SZeVnv6p8+2f
0lfG3/1T4v76U9ovbdp72gqn9J4G+yx+GIWf76HIvbuuc81dJs46iWeYhGs0
5UpTWJQ6z7q/9VhwDk4P2MJPBzxtqDAdxYExv8iTKxFtKFf9Nvhy18PtC+Nq
tSwPXyMGOH0vKDWgRSBqYeVqznNVpzQw6yOxiZRcYhSvUlZoKi6no93wBfGe
FD2QXTST5jqjsyjTqRlOAvjWl0Uop54DjbVmmRk85hTg6X95Km8iQA8VN4ZB
MLUwPci4F50uEvDbOLIR127qvkWvGwwHFB88tUEE3Tu91LR1qfJGHsjgvBtC
KkoauJF2hUFdW0IIhpcW+TxwtqC7gDNgyg/iC/QZaOLJYKoO4oztz6TCx5uB
CinUR9GaUopxj1O6K2RJZlmjdJvEttC7ZFEQU7UIE27DuPWu02SQ413Choyy
0aRmzKMinURrljXIEq6p7dIhXOVlNg/F1JJN/O55BOcz05pIRKZRNjW+WL0L
/0DjIbAzOxCsnA4ulkFCR+TQeSHumST50VK/mQAofb3ymXNSuIE6I3m+ETgt
pM4VykivhMxlvx7o9rsNlIrvxqrajPB8OE2kX96cFYZbC4pjiOmVlkVscixU
a5462pTdpBK7O48Wi/CX8BWcd+gANMNcqVyjTpwjkhae+kVS/Yu+VGhV0+WG
PlHyB7VJz1M50PgRcxNfStWMbt4s+XEIqaOOGPqE4dQsB7Ab3H3MGCcs+Naf
v9nCqMmcDGj23Fe1oKmNFMMVpFdevqOgEAXVK2ir77QgMV+F70CD6bO0HX33
w/cjmVZLUqdBs8/L5qJUArqiVpWdMh02d/AJS4t33xbnT9vs4lARCGXejvd2
9nYOGYbwzt7xDuEOW/oYHEmayhu+uvXkHeyyI6cs4fKR7n3bGjrAL/vXeQpI
rumTrOUTNBCU2SbrqHO3bxWZNLZ2XRcb+16BFfUCLPgdXlDvuEIb1wLpNYtd
0m93r/JmypUqifc93t1jdebEOo5heXXwPe0gsDG7KYYR5YvzcfBLbYxx9aLG
UWEMPPkwA/8uWa+cCO1fpCUoA3s+s2BjoiTXO+S4SC+daWQua56sUCMyC4LZ
vWKa+k4EbTxkZkRBNCzaMcnOoB2pdUBodMn7yqPKItH3rPPmSH+iuqG8KRSV
Y1wy3zvvWGN5F9MpSbQznja2p2jvjrFTnFIMPw/NYagn5kLgvSS6rRWoGYyt
3SJ35xbNrBaiFwLIvtrso+QWK2FjDlosSkl/Y/oYati+wpjXJZ4gZ+Sw+UOJ
Whe5e5Yvcip14Oyiqr7ISgpFUD4QuaQRwIhfRr4PpKZx5bjvUg/uak2Bps3Y
HqZbg7bKP/K6Cq/H36Zi5wmtFJvPa07j290Jz8KvOxoZp0FQbIw4FOGxqPiY
KMvkz+c/7Ewej6bs2E6fRs3Cb71WyTV6F/9814+Om9rdmew+HkviR4oxxx9L
Shg9Ay3r/YQiO2iYNOfMn5FRQYB80fp+kQ7W5H6HeIcqz+vlGnWsQPYu2pQr
pKYo5eqqFGYDdiSdKyukj8+frZVjjXoBczVfsybDvK8Fn7A2X0pEdAbnd8ap
G7SAigTsMXdKwphynidJp4gPp5iisGraWFPRzoB2TeQSi2sti1uUa0oToS7D
MUlcLJKm+/lpdqEkgGMnLM/QmSp5hFwm68HBLuhSBFBgY4CwJtYe95EzHtnQ
IEePxUl9k2QdhHR55rprOCk7m3/AMHGDggLD2+QtwG1Ch9yKxoi9KTx9cSn2
REPkmv4eClR0LYNM7Q0LmjvgyR85QjIwJZLvDTYtBVIJ+cwaCx040/N4r8uK
jzUpz9URyeJnw6MiizWnGy6XQCRtw4m/S0ExlNHRw2bEUP9CwEZjR2byiQGv
3FWk78MAaWrJnu+SI0d1b0gixeNOSC3bEmDaFp0JdtOMYufQz4D7HbMB2wP7
Ef9ZH+mHeqe6alz2KcqmMYnJMWspt+WeDrXj6viKUSWXmpVK9z6w7W6ZXauE
xil5zmPZZ92KaxWkqlpZmdPYtMEuEH212nXlennG0lRloUt805p3fROJTmUZ
AkbocKhrzHyJNAp64XLStNcLRTCLrw7fHXEVbqrJ2xBd2B4ddyzP+2iEvaIL
Rsb4Bn/26XqWgu+IvOzMV2vBKuESx/WvELjIcxB5V4Tm2C4+0rAu1K6Rs0Qt
RZd0uKO5sHY5zz+m29TxP3/Dr6e+XugiEN4Mv9OEsol0jeOA+eKWEfNt64f8
Q28Z44qtncKSjGlIX4Ri0dSvKJmTVGdfyTaIBVLWKDSpbgYZudRojEZvkqkz
dlHWe3qF3YG0X6JO8iTcWG63HOipqmagiqg0ch3t9WDKXonuokQLInzIWCPs
jN/969cK24j7RTRMExnUHHn+UlpGRv/upFuvf79laMSNzpdAmKZ9s4Qcp8GZ
mEf8eeGC4VZeLZWSr/LVzK4hvickjmEO/y6VQhoT//soE5t6TL6pFDfv/vQX
LCHAkSkOEImLaISx6y7WpkSMZFswOaTYZM7HJQ6yrlveQpC8VhaQ7BSDkCgc
m5ofCQrCtif5H7F4gnk4NTOT/kL+oQe78H9TdmLyo7jwkTEn8U8HxC0pRcPM
W+nXJli1lesRF3CE1u8a5b2Ms+iBCTyhl2DTKbozWF/ntkwWTDpxPhawmtjH
4jJRvigjK1R62T883N3b/8shTWwnv2Xrtndt9cPYLjbUiWP3Jo8r45innQiA
XYUM1tFyggUh00EIXirFMbmTkfBTNHenf/7ciVygdp68pobyw3SQ393+urdv
M8unM0m20QoR1hUpA8cQk9HNLR3cukYHf7l3BWePCugMLwz1fWt8QwMwge3l
L2oBwYi3NrBxV8AC9XZFKWaDr3PjN8jXn1HxVzgkncUNb9wTeCE/3fknulaf
3v9F5wiau7fz2yczrNuwcTqjp3e/6um9r3p6/6uePpCnk5snavdXm6j7X9W9
B1/19MOvevrRVz39WCdq03YnDS/e72TXb9ygP3PDy11E5cIWDoshHwQPKZnT
bHEFJy8oXVOEiPK1rATcV5X7Hlf9MXAZ+vqb9B079nff0a0rv+29G3F8OPBv
DGF9qC6yBmeTUATonUy7NO0zIeU10QN70QPkK0tWXH2JoLXsG43IYx6IhU76
MFGms1JyvxeyQX7Zeb5kwuBWvJzmR45c3qASX7vAMgE1Fo7VBqP7iSffujVj
Nb6eYHQsX9E4xHX/ojM3MImaTko792DniZXrwE/TF2iUOfF/QwNfUsztC1qh
+4KaoZ8mi/XHr8qjhRP5227Vt8Hs79uGcsuoW36LBVp/nXfs/dKlGWzgq5dm
uJX/5qXZPJRbRv0VS3PDOzbKcAtB9xMZu7YAmer2vElPrf73vAMu+3QnX00C
VNIH3sxnTentvqLfPOK85wI1g8E8oxQGobdschA67NcnP8UZOkbLYkX1b2/k
5HQ+9g3vEecXaOsh24IlfESI0RAjxpjkLVZr3eaIl9j6I0ERDsBdmBvjCfoF
qrodrkFlHkIiidNEcG7CiBhHVoWC682gYM8cKFK8j6jbKnQtX22Nnkgc3rF3
qKeFu4R4ExeRG6KYYq+98F5K2Nb92Rz1ccA6wGOQLisqlNhgBWSLSwaYVjUY
DpVJ3hgOhfOMUydZX1yQMICrmmm6fcrExhg4chU6YPOtyNVAW5Je/1KcbB7J
0vfSDpQMxHS27xznQMehOAAvypvb8T0Mj2vWVMnR0xFQXgzI1a27ndI3cFwn
k9/6gtYJql7ll4CVtJ4iumLwIzuAHQJb+R7FT1BPsBMm3nHKJoVdXDU38CwH
eJUln2rqGNF94bmXJIhCqk1ZYYxjyTtxFNdKeET8YA5SUDtJQW1aLqfUW0Kv
TDy3Ib7M1GJ4iDmTiAP9nAeABGcETA7TF0J1kjI3TV5GJT0sLg47GmuOcJmg
HL3tZwW8H9Q9AshlG+iDOu5NDoO1yKIu0wWHapX9fR3toScJBzjh/DUddlLa
WIIIhSO+yM9pAiXwF4fcfo67qY9Idk7sSK2P1Pn03Y3K47ubtM989QuVT8yL
gLsfrEhikdkaNqQeiiG19URqGt7nezvveBZ6L98S9QjEdJDSY34tpmPc/NrH
3dc+/MrXzp+ew0TVk31zkoVebNQh8m714HjJnO2X3MFAT5zoC4qC/mj18bqP
WPRb3NZy4DkpGY5BVV4slFBQk5ech5vFpFJLU4iWagCRnvEBy6gh7GPaqfpg
OVEB5J6RTaf98YmhkjNslea5VDVfCxJ9K2qfbY3ZIBqhmi2yYikhbc4mQbsW
Qa0NlZAsrCwP5XpXi+riupNNmM3ySYWiZ4L/84/Pn8fIKh1QpUg/gD2XXFdz
bb/lJNbtk7cjxmKcVe1lrIAIHDyWVNAYtqWSdvt4pAmBDHTkOixlehTVftK3
HcHbEh+fMwoBUjzXBEYkogQKRTDMc4aogHPGWdxLV+szmP3J+5zKJNUZdHc9
I7m0/eb3L0YcBRiJYG5Iql8T8BFlPrEdykJw2S2U9rig17Kv3OJO8RqDaWQD
VzLbHXklAkccK0NF9LSwrfCl/d3OoP0WlVIFOGc6cNkX2EP8M1XdtaorWjZa
+tS5ObYJY8XwJe3kOMjQUVCOYZ6IpVXqg65Xl9VizveDYedxD+WUVtAqBt9l
U4fCjo0yW3RAGX767sb59tPYWCBc5ac7dORz2GyfGXTBGexlRGuhRSVoAFew
yS6vLf4Zbn9QFyL2JN63BFoZDG4Y/rnLQ0pdMyWEsrQ8tCjW03XSwgwps0PH
HYWNTq0IN1XpoRPXdipN0ZHjhL7qS0k8VFYUy2VGgfsYny0XcDFgYwiKksKX
SKFU6DR233Wo0HOJtbe51BfSJKxZzmLk+JSzz3AaNtd/07/w9CNoqTNSKt5s
pavipeHeXpG4rZVZOzbK2MuF4nOlOxPLmSDmq3PLcAU1UeMTdIXFfIekZ5Nt
RyeYgGlsHQnGKwinxhCJXNZRbkuiVaD8ZGWDx7e8ZTbro0X7A75m/sNb+q/G
VRk1ulrFKpHEAZH208ZJXDXwOYjdjmH66Y6pj3zAjjFJo4YFJ+rS+B7T+nmx
5g1CVFInB06H2/cbqxlx1Z+WomTcSYGiIAUR8nZjDSjmQVDNNK4JaDkPctG2
jMxa5tTKuixQq3UMIx0qdqzwZ5wJLOwGOZ4ZteOLLW9i6izoDkTvp0SxpTSb
EK3BWPonFROTxdAeae1YplEx68oNAbvyxSc/KsNr6pK3I1YFLGHmsiWDDWBl
a4vaqDXFYEq2OYsJf+ZSctiJNSE1CVQoGs1VxZhXQrYSsq9ATuJmlGQdzwqe
Rs/NIQvK3St9rwI7yFXBSD1dFo5ICxeaBzXZHDxJ3C8GBSKDJiNgM9MrryLt
jfrQFBclnWQijZDl7Pl6UCFhnezHH188A7PsBzhon749+f74YHdvj1NO6J7j
wECw0D7dyfmziX0md15XxeIBipuAqUGEvspgxXapS9JdK8a6Pm73P51U4+iz
K5U1nnAFRlmD3jzDza2He5p0xNq5dZmkvWoW5wWljwpNCstyVanPi3pJLNbC
Oyb981QGvZi5vp9kBn9vFHyH1qJOdFQ8SXUHI/7qVCGdw/atouonC8uX6Nzd
iadOJ70MdWF4VmpXYyGApqjpLRHmCAVqTHnuJO9hIikvcksb/ZOgs2VsMpcG
1YpvUzRVOs9iyjlox+v5mtJCsUPI2MWd7qLG3Nu1MmnROn4vh7C3kit4L4rF
j9SRvpU1fGmBtx7uBDKjYAVB+NE2jbv5pDN8rszMuT5RWThzRUkp4EgmXBNJ
i+C1mWrkx5MXY79OOGR0UNbm57Ec+SCLs9Z5Peh8+SyR7s3S1/3INmkuB3zZ
tOqc8bnNLEylOExHvuLhNEH6LV/XVRhmUEdZRimxrh+6J+wy6W0Oj0XB+bo7
dydE0mXP2Sc5szxUnWpLEOUDdpfnNlx+6qQMFWR7BTXDxZRF5TWnCF8TFiMt
4pFSniia44gpgv7hdTujopPLoo0vRZcUbamSrk7aUeOrTIcT2z+q3ZoEH1vJ
kg2WdCSl0dYidUOP+BRJIZgChjtmfR2ToXSTz4Ccttj/K6wuR5mHKQZsH+8+
dm5Pcs6L5+Jbcubi0gU/Q9Z2LxLawWqPRCgttz2b9JIvCtItVUXlYa+KXEpK
+q84Rj0qNlzkHb4Nmei+PaiqNybMUbnai0v0Ql1h0qFseilfTBe2f2khV4Gw
I7TCqaLuBq9XsPzDK1PS48mnX8oBZ3Rd6/PMVJeiugwNrBzaHLT2RDaDvExN
D4ZtuhP5gUPlBth8K06C5YwM1gcobqB8LHgw0QAR+s/Ox58t/SDoMUOCJdwu
Wv2ZynYYy68wBEUwNNp3jNCOZQgsTq9UuCs9ZzW4lSqj1ZrTIZ8CZbqU6EHi
ETrO6AUH0XolJYdIOY6aYH+Y2tqwBXRz0QGSbdjZ1iS4Q/VwNydcs5iOCiqo
49hyIWoyLQAetzmK2NNmMBZMlEDnghlARMoWWbR9Ak5+mhLGfPPdL/brgPt1
ncOEUdF6zJXtuC6ITAVRrfoILQoL3oIpmaCR5vx6ANLZTeMUTfVtfmHeJdh5
oDAToh+bXLBXKlgOfQetuc+w8mMZ4KLKy0p2LIaOJyBQxX+2qK45Dc/K3Guk
Vgzt7fnIwfWNaZXiq5JmRPrrwIXQ0dftNFDUeCGcQqKvqkXqLY8VKBAZV3Lq
NoV3GTEY0GvdG1k94HuEMciVGlUuGIqJnznWikuOeVKY/acF4c7FwlDiNXkr
RyPm93Tub9n5moi/BEOJo5cVZ725oo20IBsLxSu/LNl1wT8ta+BKWDOm3lW5
TajKU6xl1HlMrutJe5mHUBo+Iy4x0vCYQRWpkTELcXIM6zzhH0/EwM/nh+mR
waXZYcOxghu+oo4d4gIRdZB8bULMrTFA3aucsNN1CxHovnBRBPyyuoxoFiPH
LIslUPAqTqhaM5VG3HXyuoSSQ+zkjrzB6spD/eSiVO8PzWrIp3NlgsIsk0qJ
7c8nl9UMdxLi3tFD9GPJfL44H9QNyzFTbTuOcxo7VuQIiy6ZJvQOBcBMMp+H
SEVp8kgTGXqb2RNxrDn2/oT1JLpWIqAXXba6onKLnRuicMzFpD0F6gCOuTRS
ZaRnkX+mcy6lE7sX82ceDFGrSSuoFAQf9mcOl8amVVx3k/hBeXB346mgpcdu
j9FBmJMOc7HO8HbOcxtptDDUnKZgzF1Aoeu+Gjt2ErKPz4JCSJvL6bGsfXQI
UfyJJruHPUOurDSFsGOpZbef6gW0kVC4UAwHq5IdOmJEe9wLFs2loYFH7eiG
FA+scEbBUyEQH4XBLKu96XjuaNddg3Rewrs1SkKmGpHhjjh6xPLZdcBXb0Pq
S7w60+M/nuIA/w3+w1eBH8t2hnJ7udREzqPj5yOeP/EGI9vw2Yg3lytCyNYY
X8jsAeeADWWZNPbu/2t6f+dx5JDmxo/5leRf3j7+YRRYcbHCQ94GlrGOU9o7
o8M4QcMiaUphSn5DmHFzWvGK2IHzoyHD3bywMqVjde8tcGvVtDaK6SJ4DJoy
5O1FnnlXWS/2H6DAzxtKnEGACJ8G5N4tPuAmgh3HPbZEprAVQxenyu3ai9Rk
V+4LrBPIKfcfR7W9ogABH1jQSWRumKMpTB8pkFM+EqUUhQuUVuPo+pIX272l
A5aQTjQa2h/bz0anL9+Ogw7AUZFS4pdKqCHiRJvDSNtSmHG99XEelCt7w+u3
x69PnsdvsP4Jpx+b5d4PMFxzWluJbcDhPbS5fkAQTXz7CJLcX3cM5tno7Oda
iFzDgi860n8i7xNHa8wF4pSJRXYNSyjBcV8lhAPTUeHhTYUQMKKvdebirrPR
T4UWKi5QCH/sPubaUZiR0f2GoiUCA8skrCfz3Jn9c2K0LZTkwbhfY5kduUrZ
08XFc/rSEyVQVjsWRVFQEptWjgibwWNf6CnooqWVcfyJK5Jo3voWmLZbXEZz
Q3ARwQfolBFSsSHNZjJJWNciagqHTSDwYlOpCkdfxz3HsY66hb5LaYRWhIvY
GurSs55csoKt6YssxTr1IDUGRtoOcum3N92zGBah648xqOEqVfcGbb8zZKMG
PRNddgQf3BYuYWefEz5U+WGi63YUAHhDeLZeHCqeeCGl7m1MiUsxsUWnppNR
xbvd9yTBF3VhZhzLVQLJKC76WfNQ0VISqmzWqbJWQh5ua4qLwBX5qAQqajp8
4L8O5esJ+pGpDUS9sc5HZ3rqUIj8HTUh/HeZbseLAttq6562n1i2LRgl6Ndw
zA5s67MLgHxnLcEb89oXNg0YFgXKRC4BtMunWsksBrZI3E0rkI4jqLLlS8df
i6Fe3AJVfGCyJb5TWg77yT4M4Evo5QgZc6MiMZY3rRyt0wiQdix+WKEQiaFo
s+iPPcyvUo+FNJtHe48esRmR6B8fdHJwxGNCmdLvem63d+H6YQU1EZAREgOG
8OMzuMv50FxyZhCdYMooDjES39eEyVz27u9RFtCRetCyKB5Eh+ycwG6YSFCQ
/AMTLYtw19KfceI6xOoFNsBqALLHYFz00YPd/c+fn8guVCRdqN3IwlDe2fHD
9x1O8j3nV1ZOCQMTagz2mZnJhDPClXQ5yUnyCmvHobuWnLtR7V1xTEoAg5DG
1xGHGpJbCazQ1TPB2Xdublf+Q6A/UpWNZF8meAE/yo04Btl9AY/H2lqyHXAb
3QBijL5xtTLFduB1ILNq8/tNPxkx/xHuSFA43scGWxQohPWs53zB2q2s9KNL
OtL4i8UMhWFpSqzaSFlyoZUT4zoCgYpfXLFKxrluZAbzyDHCM0ZMR45Q1DD2
gqBH3OjfHesakmeTTKRWGL2yEK63d98GWOw3cEozuY6RVsH9KaBj3406oLcX
4mmcBazXUUDc4UeIEuCH/1pED3+msKW1tM12IEtf9JYWNQMsCA9zxV5cJyoD
qNpFNIMymvq2XY5A8I3OVcfAw1/NqsVY6rXX6Ys3iQX8SCFucnGGMThLWdK9
IyQL78NUnNiZpVhxNelD12jS8C4Iwmi5liqLEXZRZNKbOp+8vSQN5Pdo+p2A
AfeGlSL4HTqfHDsFToqDWJAq0ZuBuh8Q7u0lQusPCfwyz5GcsUmPaDW/E7Co
TTGlzYvpzmJ5mn6H1qR+j5JKednGOO4J/yEOfns2cZL7GhXslJCQQyc0E9H5
RwOBJf4Rrtl3XMK8In0V1PUrMKSXmL4rzSE7FYpTLMciPToKiAxQfqo2ExYK
+fN3lGy7bqS0gu//fK1lgLj3+UepFoQ3YMllh4xHD55KOir5ub1DnQT6uXC3
BT0PBbl0d6p+JbkOY1Bb4tVpFwEwj7GcH+ow9HbeXOKEG+0l9NJ9ixnKWnG3
wBXMdh9uSEX/CdVsUUYw0c5QibgJxAfhSVYcgPQ2mCJaGpO1eW+hfGpbvAei
GBdOAmsNPfzpBhZN8zUnPbiMm8w6F8vOZG5UdUsu9u727qVvc7HpgL58Ejta
RxKRpLeGLJlgWZo+vN1V91Eovy36NXuZWeYscErOihrUxQ8ES2H5NmEJEYdg
DlEwZ22bwXzWEmKleyXTKmCd+eQQtjkvPiDsYemy/ZARXKqC6x0XUMG4OwjV
6r/ZD90q0VwR/Lqv+G4N5g1DS1CJXi5xMSWJjTtNOuLpJt8KZdvht3Erbgg2
F0I77vmsFZTtaPryj22dqc3XjVla1oFyhJ5qhOCiMrLWqAJOn46Y09wGExTl
tCGbvX04ENUNt0BhoK4A0t88Qar9zDFsQY9gBNNxuzoD1przPUHlQfT0Y95s
prdr/M9p5XZpalwVIX6Vcxh0jjlnEiRHb15Ib8li6JnnjYqvGOukl1ziCl1K
EKdqug8rkZI16Qq3TlPGANG4kpvGVdAyIhfW5KLOmGMatNEPOdmTSpY0TR1K
MemES89tyZtw4MMbxOUqkpwlT8imiHMJ8L1yRjSJLn4Z3DYIn2lQMG0Hn3vJ
YFkB1pxz0V32Z0EvmCF/OUripKbBPJMhY8hYv3uW03ZkImE2JBXJ0pVYitGU
lwUXisOcHbpISbQ1mNNSs87C/MnrklW7H5+9AQUm2Kh45j6sF6VElvCuK1Ey
oRJ0nWREr8rVGrGoqDAJZ+mz6q1IUVxMbNQubAXocd54UoNxL5WL1GH+tkCP
OOzAkGqpLGpSEs2DexNGArLqbrWuSPdn8DSBhRh9N0283WwGdSNmK7pfywuU
hZwPpCb/7u503/ttG8QwLIMEPrsWDbVZosuVqG+hk//gVM46lFTD7bVeievw
C6rIaTwV1yg5u/apaFnnWhH0lmycQOcacHxRZdDkz39ijcoXuykMm0QH/YIv
ZBIJ5q67uc+SS0CBEBRbcLJXlwKgQriF43A1DfzwlywKB3hvnUiJEYb55KTy
vB4ldmU2w3PlcGxsw6uTPJ5/nNK/MAbnfbFaMYekFRTFjd1IMBbLtrDm4WGE
uFfP1gVTEXNv+zVjuR1zVpioUwJlTIvJkYzBofrOsgWVaKLgLEeDESiuQYdu
xlLMB1DnBPDgooGZ04zIJETDid3GMIVnQr8dX3tUopQ5ntOw9iIa8HpCvz1m
WWus2cOHXNTlrmwh79YggsIuiH24Ht0VE4KX87UVRkSnoq9YDNYXzlPTHSlf
LKyv1VSSMjJ/z6gcWZVirTerZXn6/3X3bctxI0mW7/gKbJbNiNRkpnjRrahW
t1GkVKVuUeKKrKm9WNsQZIIkWskEN5Epiq2S2XzI7m/s077Nn8yXbJzj7nEB
kBKrum3NduqhJGUmgEBcPDzcj58jLtMwOuTZIzsC0MzRhfgfkJfG4sf6JDBR
217Q3HjNB1i1K+xHFxQGrHWdarSOt4p+TcwPD+qyBNidye1PFdesGrzzWOxO
NDJNgio6JlbKLbCcqQKdbBGpvzf2E68XK2Id0yaJd8/TVfsXJPGlVlGUqcDt
mYwClEc9ZHjFjFX+PQE56nFCO5DL4IIq0rIBlwXngm3J+ranpXRlJDfN1F/Q
Dl3O5KQi6QS88k0o2IhjiZp+cLPA9T+V5oKAXxLhQS8wLCulyFUjrSNQX4MO
ckhxw3WBbdDEfaqZ8ylsh1o3zU9z/qJW0rrzEi/ajID66923u51geqxyRemr
/PN3VTErRvPFlyzjJRSw+2A5vUUn3KJSH+7dtAcTXS8Qm6wTX5sdi4PvNUny
fzaV0dORTiQf3d0T/iuaD3fDBfIiL2cfK7f386CarUG5Zj2wDHtAzW0qVO6j
+lQg4xPz9L9fnFMV5GVX/wdNMkvup19kXnWsfWPmRet5dHKSNet2jOTGr/aO
f3x91EIwR/eN+S1j6bSIgq110193X2cj8Ps2V9Bvvy9v6H8fcfms7obkvkpQ
9EX6l/P09eHHx/nb/fDyoXd31WMSYSTlC/BOkB2FGppY5MXdXcwVwBy1nFyZ
TsWBPLGsLi5PYdF99FoeozwzzSDTOTsgFfqsXNhpMD8Qa5QfalCWIjGSclp7
vXfgbh/P4IGfwtzZv/me+drxi/1tUHE714+n4ld7eTmpkIaMF61Je/HXWdiy
DSWohXp6crZuE/4RkfjZfiriss4eIZc1ztUxcuMXaL7fW7+ZBdF/fzH+hoRK
SBYpGfTdgCT93g0b+LxKFglKAHTkWj+IG+H6UAZzQGGr6HNoRinOAV5otqo1
0DA+s7B8eNpQK/B9daNEdWFlM/A5TYj+E6UFBCI9Yjemg5b8kjyLrw2CPsQD
ATMAmuu2pWV3KzhkreDBpMCXl8srHoyKCe29BVt5DrUGD/W3RDb49PpSGeE7
8i0IQ7TDL7hFP8Sh8uU81wVJ5omAa900bxeYxpvgsP8ST+EjkgyJNA4vaDcS
bWxuZ4vikwgxQRAJG24S0xSZJfy0iNVU+QHjgCYTFsBbtgisbAGrq91YA1EI
dlnFmFBsIj8EZI3bz/b3Tx8rcNW9QA08eTQUUVJanxOLnXP46cdMkF+bNqJJ
F0Lj1zHLPqOjdMImkhsV3bugEK/JPHmy9rQ+NZIfKUQZGxPUra1olihe4rQM
+GdDxhcCYrcCNve8qRSWI6PZQmL70J9zrlhr2J68bLsSUSkaSL+w+daeWnPv
fErlTSuiCS6x9rGiiG677LspTxgajY+QxsNogbYq6kP/oJpgLicT1GYi+SPn
jCJhzvdJX6+t0gSmFtfeD2V5rbUjcRMsAJZWNYHK7LVWiRs01HOgx/aV8fdY
wuOX/BXK2mgl0g35iOaDfpMsrPjLn5ryzs7Tt/9LZFzfxk35JRdvwj1xVoF2
/37qNLzZdf9/G1lBPyC/sRlv7CiYfpNPF/Ln5ujh1vcPv3/8ZOv7R6EZ/P+b
BE3ekRDCeaFGYOIuzTgSRFH7m3ySf7M39NKoQLKKCqZBrTO7+HYjclXijV7h
hdEj/iIINDTD/avTRmkG0wFk+hl2i05Fogq2cxG3UtOBVVQdxGZQo6PbQNHM
cH/C+cJxKfkyf6MTVdQZgqTYHd69vzdE9aPbDFHF+H/WDL9SeMgKTyp1in7+
XC5G0U4C99zPDaGS84LUyZJRtI672vtvX9ZXNAOcY+7MGSyLSiknHtk9EIyt
0ZDsqD2hoflVvsjYW6CdMO2f54+38xe3C4m0/3T8avTUvQe+m9iPNF4zq32G
we1yzGfNm4A3jBep24YxUDtuPT/v3ReGbjDDN5oxy3fdZ4noTvsVYJ1bu3uQ
5zA4zGrRcit4b5ZXV4XkbYQb7bj2scUUegyALvGAWGcWtBDjL5uaJN6qFmJO
jJYXMG5M/6duhZbH2a5gkav5Kr/J70JaDVN3UH7oEMYYNHqC/lAWw0KpTX0h
arKFudsMXn5C1NCZp49VeTPIunSfcKw2tx5jRPGgEmcZaVirwjtjBn8alDAz
U45Tv/V8OWM3SF3w2mtFOZQ36rXPy8kSiLGFF3LxUG/n4v9hfZgtalY7axGe
RIXWXlIqudGIlLVdw6GEsyt0JnzWXq5WM5v+pIgB1B5fHuLQpIepvMNyUYfo
TYu3vHMOYxxa5ZwCkOYP66YIjnKwhbop56J1d+66UntGymuk7H3Sk/FNvbST
6vyklfeXMj/vQekTPAtuut0SSUc3jmXFtb9LoAqNtcAbkbAxsVfUpblNbtJ6
nK14K6lfIc4C1Bma3z41qEDO1Wl1oQKAQvPSZkOO0/JhaMVcxFjVdh+uK+cU
Pbr4KGFBimTnGKRH+M/ftXYNotrKEL0JTm9hXHUEKhkvgRa3JLz9Qo4zzKLK
fZxLUibnMP15bSsmmUbyxkmjuIvJyTw+KQp51dBPeAEzaP5YZMXnudANhkBH
ywKXrW02NkHjgOIR8p/0RKzXn5SL7hQoQn0N0RUjDF6TqVOfuFvw64dZgEnU
3aNNlOPi07pH5AjNIXNN3RC5kBcV/frEEWACgOnWo8dBvDsda46oAIaKUEbe
u9Pj6J0lmIpQm5J2viAfFJqQxpit3LRSgJuRoUc3TuCgzTWCMaG8XcZ+TD6S
XKgLJd3sT67Sw50gVrFc1IB+Sf2bndzO6jkCdlngbzJV7ZaqYiw1upwqYEay
8WGcszbipL2C10pE2JN1rJOZy/nrYTikXiQ/3BuKWxFMyzT2du/Obbk3jtFK
CZR5zQjAfflzHL0ZenHCddFZnQiIdJpxw6oj5tZkTkTTLLUe3AYZFtsxBBUc
iKiK+fXL41fqVnBEtDdTLT2StQ9E++Mo6dL39jrnptnWeKxWFJWS7UhBJYRl
MOp7HGxRKAcTvnxfyjhnZKTl7bT9/bHdLdpR4hsrfbrdFSrv+Kkb+ynV4KMK
e9jIPK2QMPVqxSEXwhaEyshFG7UWkW5ew65M8sF4EPxwdlMTsVykwLbbqMLI
K6bCbvNdXJfl93NPnH8xr5fXgx3ApWPQDT/u4YPn5w27CguL1uwMxHYWZ09s
8efvrs5GyVEBiUJJD9OJRVmYD6pLfjXvZNDkB/gqzaJd+YcHnnkDFmvpQg7m
aMRrcN/Djw9z95B8gEQw12cnX1CBVd6O3Qd7+1uoX2YI3zV+J9/aejjeGG+O
N59+vz4MlghZj4eZHPG6PXJE02mh/sE4z3fFfw1qqeJiubbrTUKUSsPjtzDA
2I5ua4VhSul0CfbYD4y0X0opttDm6X3wFMuw4Ic+y/KC6Jw1e59P68r49+jJ
k03VY5Xk0a/sr824v5r81auN/7Kz8+plu7Meh27Slq7oLE/TODDp2vyIBVAr
rkdzZKtaQ2Zne3vjybrr8ITnbi6Ml8RqVe6QonfozCbRrEeeQWquAjuQaFaH
+aWHAr3RlEKJbuI+058I6tK9BFK6ozeijOCG8cg5DfpPPkHorcZ3zU2xu2lV
3DztyVHF8gxzZHGMtc2fJi0n9TOgtn/iFgpS/p4ktrNCV8VMwNEeJpku476f
6KLGQyktsDw/rz7lg/lkkNm4tp4dEnpafycVFxqKmEqUi9Pa7ThA/LSgW3Ie
0LO10QEJ6u+tJ705NsrbkGU8xL9UjNZm38pk/rlbBNz4RRndHwR/85O4jdnV
CPXsiIEeuZ4a5v5a9+lycu0+iQLI7rOerKfANn3RCObhoPUI/4TRZDFt3E3/
Lk8RACWQPO3nrXylxdnf9rDjva+8W+fV/uan4c0YyAETgvBQsOKlFX0yNZhk
MuZeVeCzKQ9QKQASbvaNkt2KDMyOs1NvwA+FRryGDM50ql6oUv2ISstiVH7y
CbM3NwdbB60f3FxtXfE3Rt7Wd8/P38mN1O1ty14QRi+VU1O7voqvNw6SD2Wj
2VzjQVOVWHZjyO2C67Q4Q2THWJuS2xHsBQ9yRFxF1gYGI1rpzwlokHJ4ilrU
GLQeIaajzGmKoQbDgA+TJV4b6jbE99HYDLmKfJV7KUcVgFmBgs26u8ZXfCa3
DxGdOF2SUNgzZk3mhRxUxXoV06jEUSJaWdIxUjNNrg9kJydgywrRleg9JQA6
cKcBZ6EBxR0IbNeI+JvG+baZ9zGq2fl0KUwclwmDFtJt5OkuvXD1opwZuNJz
OGocJZlTe+a0Yrc9a2SOVbPR2eWXRHy4JWrYngsE2c2KCyApCCy8KgufFyUf
jED4MCbHtTOza3vH696zghNp6H1zvfyAcwsfGgNPeSV5YPwzkyXcKEpcYqJ7
xxYZUKaRcMxIWzxDi8lU5hzQRXJlzBWSXOQdunBv58n+XL2q9BlZ/88lpqdX
fKyK/IfD90eMFAyDDLY7213WE08kLx0+if0iRrqdMdLZFZWg+7h7/PydbG1z
XeO64l/KGClFMg81hH1XxqHmFxBYSwNRiKxtu0lUWKBvFI7/MjhrW+th1YuK
d3hu9o3nWmRa17Q+1YxaakP0WEWF9crIuiMh7KizVJ4jV2C793fxEzYPU7NU
re5xOveTQWWIvZGCcpzaZDNg9IWCftI/7q7TpXtSMWdNsv79VjxC+9fWUBzY
SOoNjtZNBV2NJoLZjHMCauy6zB8bURgKBqOr62aHqknDfC58he4xV9VkMm1f
K3TyJmaVqe/JN/EcaAJY5lXuznE8WAigWA0KiU5DQQvzG2VS5RJWNNsjZWHa
Ib9vXVWRXbH+zKQ/Tb26Sb4klKmcN5pNsU0BdOXoC3mifZbxs3jgdrRvZDQg
NiU/wfXJSEln8pWi77bc/HghjJpnsWmziHd73g+TRVg19vI4BcwmVjHkrZSP
pSmfIE8rOa/VB7TWM8gVpPOuaro35M8N/Zs+XyJg7f4X2TOpHqqmnGKp9dx/
e9TSv2Evz9kPw/zoze7unhxKw8nGGawspu7bOx6S5SAsjah8CKMtKzrcQDN6
2KZ9v4yOnCslWjrEqeFrNSKNdzg66mBY04qp+CVpJpPPYdR/yb3Q1cOdnc3k
263Wt1uSxk8NQOs324I42G99fH6u2ebotSzZ7A/LPrUT+QzNvS/knP38GZhU
ZMEjZwDE78t5x/Grmsy7rBIZItDRkpmfv5Nb9e486eTsToLAWIWd1NfEZT3t
SOYLD2ScM8l0iV45CGQpKY4PuxhgKZKbRNA1MJsb7Jzh1Ssc8AqYNfd4tQXm
loZ5yEPCfIVgGxf00M/Vlsnn+XrVpdejeGaHekQ+T6qHb7qiT57JEeYnGUu/
5GPe4TB/h/Hmsqq95IysjTAum9duL9waPRxtbD4yZaewIEDVor9VC+2W1QQK
zvFORkP2rWcZyKt23ZHH3aEd4ebGFGkG4RK6vG2Ehb0+C9NHDfdQrHZqokMd
No+Gzs/KiMYRBd4HdqX+U3ZL3EE/kBsFpIAR5kQKhll7gOB5+1SWBK31lcxG
7URmx7/uL6265l/SydwxSdOrf3mvA/QvN7PJDfAw0WsQkLN64ua/5n66Mf4d
7zjXK+5+w63WDTFh/pZX/sb9fsMrf+OOd3/l7uZx3fTc9rpZfTezMIZfCplL
j12KpvC9fjOvByCNFGpxMrYTH+om+pZ6oGcl63gLXzUqpDe4BVVjZ5rSjysp
rNXiWEP4y11nKsSJAGfLLqf+QaAXyEKSuF/tOGSnqXu8ThoRprVuUz/LNiC3
UiM1z8N3zCi1tC+5c//5wRzB5D+U18/b0/4fqZnZd9nmn/9x8tx+G6t8hjlN
jfB+9Uz+CPrdyZT9FRfMvQj5134fBEk38z1WTk6yN2p+R4fOUu3kJg+a/dZu
wpxe3U1b/7G6aetXdVN76a/upu1V3XTdfKX1Zil+xQts92ix6ulmtNkr5Z7Q
h2GlMyivYXgCbCjQenzpmd8Z2gmvQytzWgJqQaVvYQeP2MgVdKABtSzRVRyU
1wNlO2zcaQj+wM0HEFnLXk4mj4QTUQiSlzNlcVrUmUUFeoxQ27nR49jesdo1
OXEGSELw3sE6gV/QPEV4+UZQ9AoIRMaJ3MN9gcupuVH6az5M/cBSZlh6VBAH
JHWWm5QaFqlDabRxezK+bQX2419vES/m134S/2MZOMr4lHRCn59vPIJh/P98
mT/a2PzKItnqWSRFlM3UaPbqhbJ77gtUq2kc6UaNvs0/ZcWOou+dE06G4Oa0
LOazAKKX0Dd+eKsQevGIVQBgoTp9tlHqKbs7OXX6m3c0zJV+QzhiVcwSkr+s
To6YmlxL/lJXIsfGxlhoC7+TgN9QUVwa5HRvMakoI6GNx31xD77GVUeRe/WE
DULdmLrB/nRnrZsnbMu39brdXPj9s9YqeNa+37MsQM5TjW1bEYNn39LDtum1
3Tu9jP1Gac+8Rp4XzOjBZnCyvfLoLTKfwEikBosYlWE8tW5lUokn17mvVZK2
JnygsUnsaTRFW8E+P1MhmKSotGDTGED96uHdmDlwTjNdkFuyZpkXya1B6SyG
vp7NInppKLPV7K91gIGFBBMkj4tL+tNFKum/dwe7kgK8Kdl25AvXmDZcR4LG
koVZxh8ynUjIxPW8Pq80pK58AJYcCToxSPINlXVOIjQ+3kjhjCDwEd1Gog6S
OqVqV3xzNReKgN+daZOispeZxDBmvkxafiF224vz4VYk0hjmkRUQTO7a58+8
xh0lWB6z/fh8nZPIzQf3NRNpHtvYdI8FQVlKAeYeuhhhIrHhvRbVHJniyYsE
lfYkJBaBKSKuVpU0EnywquHgwEQ5XNzq060ZzTqg8sMzVb8cbX2/r+cZIUAL
CjO30e9f1PUCL3ttFZFDaGK515zcIgFy1sc2a/m3cfLMRncAO5IZkYvHNLo3
8T3GO3XJ4CJG/AyEYvhqWk4uhOgge9ecuV55W3+sh/nRfPIXN8R/mp/hH3+9
RcL+qHBnu2H+p3Lumvvmdub+/rL5UOf71V8+DPNdxK+b7AXElNxKPSgWi8uq
XOb/zFLGP1ZX+ZEzexjCg/qyWrjXct8P8x+LpTukHhJACQ7IH4sZ6qOPm7PL
+rycVW7rO3KWo85/+vChnhZDwIFuq+y4KtyP/+ia+La8ucJGZI90JuJP9cdi
0eCjPxYokXMPL2flXwVb4rrqTenxB37YLsvpNbgfBE6I/Q1Ds2wk58x49qQs
Gu3mOeUaZpOsuSyuWyiGcf7fmD0S/D2EJeUcTtGl2Yec0UGgcoqLZYTMzV7+
lL86fJIfvXx79PI1GiZyGBL4u4qUa4CFB1sPNHRQdJCp+CuQixOwkTljIQFl
5JHdRjOtL7JM9hx93mjrCRo02noqGJo2R9gDKVVuCd84Z1PYVxUSRWKS2jml
F3HBrcT45TlasiuQV8I2exgXdyANIixJ5fwqH7jvtJ4k/GZA2lnAmSbLM61U
7Yg/RIoY7VorEsmoRD3QVEhOUC4K4L+R/HXulaNav5bCAMq3GuYBv9grrt2+
bbCDHaE8QZZzMTVWr0EvKeCgMxqPZTSeENhqatmsAK6aBJJW5rr+RcePwpj4
AJvIEtupc2IuF4vrxvktV6hqdCsDGANQXI3r+cUDfPDgqrmgRXjw6ec39dXN
zWX98cNPo73DH95+mn1sHm68uCwOHrjNFjcTUdtB+bGexjRxhma29aJOpC6a
cMKiha8ArbwqS+YjByEC3r4Hb+5tSvSOJGqbQvHIbVcXzma5+8kDGuuRsVBZ
TItPid1uUGfloSEB/U5hJyFUFRoebSpAGv4GikOOaugxhNMljxq8FwiiCkuI
CbCDLP23IHTaDRO0sES6z/spCqpds67Szto0eftm6XaAW8T2QKlEcqIJK44K
k+LwwUIRgzb2XgDa69tSOlva1X5L6gssQBfRFOel6Owsry/mxcT0b9DFbIZb
H3UyBXBGttI2jQi8Ufp46lwKbwkIhK6KD96hE8YLYTHo+bm3o5FQL8G/RcyZ
OPSuqGKG0nGWpJtbEdfLoAiLjLp7wcuCE7kC+d5CqcCOxcjSrTsNQJdiCoGH
C6YDFuU8phSwjFqwP6xpkJc7M1KhRWP0SQuD0DqXa+ljJunoqxNnwojkAHHu
5+wsPIUweueaUe/X61+YNam1PsWNEL5e5Cr/QHZtmeRpVQY9e3J2narYLfZC
iqssyHUP/8hI28ESVzTqkE7m9bWuYV9rgFfvGVGuzN3JhAULKSsdJePPxKDm
CumfsWYrwPrX+O6rhBgU+hFTacItmtSySaybWix4I0nvpUd1TA/vU9scEPK+
wIC4dg0LJdVznpQGM+ej26/AtKwSxRhgEahxZzvg1JCmWjfsi8FRrO6s4E5+
IfAMGSJrWWuttOkIoz0uho+5PUNckokVp3EyUXD6RmTVEyJb09btbsW+I/S7
G90EAaZQM5JSSQOTNVQSTynX9LA5M0rCb1Yoqbmf3FZryPanfsXMWddiUcM/
TpUItJ69NOplXrtH58FXSgmnCJo/AmN2AiXF5npmu/SZhRBZGzcrMZ7/Y1lz
j0ptXYRVaO3bj2TfftzrRe24vpTKmLuJVEpctRARGsP3EZsaKl1NBMaUVMZ8
xp75T7YNXBXCI3lausNqm05bwVoq/HNeldOJlFNcy3EoFrc0viLIXMtBcaYy
S7wJGWNCc6U170VO9eWh/NK8RgFMWiEfPOBKnevYnGIpLWfwmKe3cjtYDvFx
5py9cffycfsE9+sESH3UIhKtoWQF1YRF0UevThzR9yVmfL5WXjv/f913o3SL
2oJkwdxrohwxNe/o9vNswWA52JNkTAVOGNKAssxrOU/2S3atGN02F6BFGZLK
bSqqlDEbdyyrrCbgVJlzzeD0iRvHTSDPT8RDb7Lbyxn1EiU5qfutaYLLnOB6
4u6zNKAy7ZPcUVmHoIRoVR1kIjhdkJlvnKyvdAeQVfaDeMw0O9yycvdj0lfX
EQVCSgzaxOpNgrJeMxJM+r457V7lBd5y6NZhHpD5KFdNm3V9Qed5mlMi80Sp
q+uZyZKECIV+JWe7iNO5ikUDT2/zDnszW7V2ir3CxoyNQqE5yL68NwLbpMZK
GthaFhHftB7YkpnV2mWR+yGO3ThnhZVaszvy1l1i6naxdXfuyhvdF7oObFSC
lTcqYs+T7A3BDDVJMnNaGuhJCd37GMehZsSHO3SlXkH2B5pJ/Tq6FmCRsZs8
y69U2iZxNwTQac0UT+e0IZP90J9XxbbYljIQzNQ1Q06K/msGPL1EiX2Z1vvm
ZcWOyEJ2wMbrMS4k3Lb7TrYLt+L3f9w79DNfIhEmoqnQ7pihWQFf7lpex8ye
hklbgmYehmPG+QcMM6IRwLbnF8tqwl0ivkVTTnVi+GAnzlVPth6a1pvVBRDA
apFamRh4KzP0iR2sTFsvUmp7v9t4ngqxtm/3fVTXDL6ERAJ/Ek3Y5uPRKfQ5
qploBtT59hY/MRolpdC95rFLiQMQl3N7hbM6FzMNSchX+2+PjjSVQ+6LAmya
SpQa/BnVMlgf9y3PWOPebLaoygPblLhgJkoJE1AksxlF/XIqjvY4Ps2CG+ot
DbAW3PQQKfB6fjsI2V6Ndk2GnmGj0XhNJUBZC9wHfTob72LyF24KqwM/76Ni
+bMaQwmxnndHxxyDTgRzqKXjfstNfuE27irWNeIRHOE2lFwCskbjoXEJWs1w
1OSJXMRo0FirOJLeAv+YOWQot0tq/JezMyQa8Fz1rtZUQ7MC1beFEMyHNKII
nqg/QIlUqUXcqy8hnuidxrQg6YYYH2dMzCnF1F8uZCdyXv+0CBzaGl4QTV+N
6deTcip+jDD70E/A5hsCzto1cyMz6hGZtU01OUXKBH5jeSdt8Y7rRNeqKvJl
LY614vc0dskjkYAbWSLcDmVYH/cwOU1H87Sp8aYWVlo2EnV114Mafvv7DT7v
oKfuuYXhVa5vTgPt5fPz7Uc72xs7Pk+584lbZvvj882dnacbGxs7n57xlvi7
0iHq9mqVtSH6db4pWqrzPJxJbrXrVX5VfcZ2B6rjEBr1YHtLiFNP3YaiYAT/
7Sf3/cOncCc0XUccOuIZVuyuYcv4oCOznihWLpVydgnLLqkC9OePKIli9nhZ
TSda+FJf6cI+rrjS1B7KAGwd7OQH9AIpsq3cjhHZv2mbc32Cx0igK/DSSGTE
Zv2zHr2lxpfsPxah9cA39/bOIRztvj9mC1+/PPpBY40WJiTK5N6duWti38Iz
TtwzIDSed288Hid8FPdoR+ZzApFnE0AE3NmENcheQ1HNr2CKceIxMW26FYWi
97xDOSATgi5FaLRqe6EbU1xLJ0ltubPozvIO+LL+KLzT9qDYzwC2Suz259eH
ckQGx7++GPxj1LBAGHzvuIn1VZQvgVo2Mh+DYmd711HWzB11k+OY0aJWN2s2
ibk0sOnBik5vSS9Bhv96Wl/c7nTPQ65h91I4NoR5VS+wPnNGK5w7sefLJDh0
6xt94RZmk0NBYuj+v73BvgdPqrRMoyzBLjW49oCe3N4l6/PcQ3avmn/7P+La
M5egW3TWCRg8lIDBowx3eYP4prsz6z+gUqrT6Um+1gkmrCMyE2+XFlEiUQi3
FKpzemBTfr9q7rfE8NaUq5Wk7s41QagtiGZQZSxRlhBVidoCSPddf96HRFEt
ayy+Oe6IKLhOD52KuBYfQiq2Zs5mxkSFnFXUj5OiRNpBT/tvwuve4r1fNm6Q
3aouCDFQJpVKpcSMtDbe3Jnr1Z36dA6qsfOiudT9SmUWkvLPkPCzQ40YoYpH
IX7w8w98yQDPxf/wMDvkYci86zSZk5roSnKvaPLo9HakjecgiqwhkzQ4PS0h
Momt3Cv6cBqJ+/nzDz6Q6h3umDZibXGDVH2kSW6+FuI+UjoviIySBSascfzp
p9f7XkhhXRixJXyThozaQTrgPfq00wrNq54XFJVjYpIx8Pcv994dHLyEQx7U
byQ4GaxGrpEpvhQ7oBWQTZLc1UKNuXkMPoaCu3ixnMRXkXm2v//uKG5HJfgL
df3Ea9FDrRvAWM9Bd8h7TRdSwqsPYLQHYt4HFox2bnV1zbAH8oluNmDba0My
B0KHMTBOYjYi8Cobf08WzkExrkyTVY+ebBBQLQRbkSKG87/BXn0GOk6/X9p2
D6O/+3ZXj5z17B7W6cxtTexT5SHXGdQBk65RgQ1ZCdB5jZbX4sG+FipxT5od
qMgKCTm6LvQs2tXM8xsG4iKMhd/j1YzKSR4HLh+athBnocduSY5FJ2+55vQU
604LgMnC6PO2g5fvxT8eDEHyPpCDJzgdnzzMT+tqWs7JC6WbmDgzbjeayzlo
cSs9Kp8X8w9aBj8tbt1aQf1qexPYlk3gISZMIPtXOee3R6OjfYsFM9/Hp1VX
y6sgHbM2dYs1OQ485sBvxutBI8o6uq2QDlurT6EzsBItEv1SG9dEpBFyI0q5
MAKhx3GdLUVkoaL7DPxuOpDJICwhMdGeEZpgmyQkaMcHYCQHN3OWQWBM+dT9
1nULhqgt45f6Drq2xJuWQcMufEtBH/xzCE100RbX2j3kInaP9l6/jgldiR4A
VLLpjO2WjO12akpcg403HCZSgDuMiAbSNTT19rrWdrXvuyn33RKLJ3k0sMxb
sJA8TZ6DB9dw0NcSOrpLkX/hLrBLeiIj41l3t31VfcrLOUTP6F8H47BiGbqN
SHpBR5tWwF/GgzPfuUXuvjCtH60rC9nL89zZrSl0VFW+ItnQ5WDsesiibliB
agU63bUh3bWZZWuHgrwSiKsCDbQM8ucf3uytcxViPobzdOtIkKxMA22KS5SQ
YQD/oBEF3lO5Kn1QER1oHKIiL+1PTJ5jA6Oruc+YWzUEdSL+fIa0KSgnJA++
lrg5g59U1Z1ptPm99MvGin7xqX3n6LgrycQCb8U6SXSBya/G0DhGMl0XCWFs
BOlvZD1weraFYN/uHgNkvyx8x0iJgFl0wIK4hV1W5wtitQqafkovctYpl0xS
pq0+HAGk/KW7ww9SCaCk+d4fKJNjmkC9TfPb8tM+gpVmjBTXx8lMx5AXC8UR
Tk2ZrYJ0U4rnPwO6mGdkC6si+E8IhlDkbuspNJ38XBt4mEE5GayL09OAKqw+
HgiUqpoFzg73wIE7gg98g/IiRMRtw91tGilCKHuW/Ahk1+e3IVzSLG7ptI3S
8xn3AeM39fFYhJ+dM1Egp89rYD/2jgWs5ezICC7Lly/8ai+Kh6gFiHhVBCWm
SG/FGHQgVZs8v7kJj5lLRM1UKMTsRLGjwAYkHH123jmL7uAyYnQVQWU5MIif
ihAZPFkoafHKv7KsLipD9Wkun5pIDo5yCrKIIx1D2dFKCdpj0ndeQ3B6m8Tp
xce/eTnSsjnB5M8+5AoZWjtwBn0+I3V3hMJYHwb23MK9Rh/0RkNr7O8ZpYOZ
0yNKQ9Ed/sdZnFKxXBTaa9JDkctHEzkvzhd6dAZ5VBHLAbvbNoOI2wRGVui5
U7wKkZSHu8d7P9Ie8fzOi0d/aeQygpp7el9iKpaDIZJGc/vS4a5Hoh3PB0oQ
upj5AJRHZ8lcen0YppOCIKyH45wQFZYul+fnViZiXOcaDovQRnH+adbRS6Zi
oGuoxH+vmYH7pIl4iezR+LgJ5b2mmDcK6KZSKR8w+2DO/ClCX/Cc1B6zBB6X
ewbgNeZBawYG9aD3sWDmIMgFM8qW6y3c77A/Ez26vioJoBkZS6qhh1AigtdC
KmBkYT0I8DbcuF2Tlu6vTKcCtNs6S9F51WoqgPOWgALHJ8tLxj2CiC0EJkPe
PkCquaEINtwAFxFgjvyG9KVwEg2Jv84JREI8SlFafKwrvfWVx+qIkm5MVI1w
irPAEpU/XwpzmkR2rB+9rihBjRdwD2YSDSoZ+ujVo2ZIbG4kWhA/lHA3XoAB
+MKcOrZJYhlkyFw2Qn8zWYZ0QPDc8M6jzW3980kEoI2D2/RtdxhaHsT7aCPH
3kGHqH2gfmk1MyIi3QhM2HxWXtSLyh/jg58UJn7kzWH/1I1jpDZv9HtKa18v
OD+VU00Di6yy8Y1RjbIqYtVurU+EHdn9CK8xXV556fV4OMIeHO0Owjf9au/R
9xJ7RF3MUh1oUW4KG4wtfqyza6XpG8VdofqXlwCfiCUTcKoaQIAShSmHRYVi
Xdc7m4/Akt1oZmuBDBQ2PpH7LYQXVGiimOwYCZTI3SCtGTEG1lD/dFpGkGF3
cxBUbm5sr2f+XSdJkRHWdumOGwH/1ylunekyDmcj7zKrZf/WDZmxncTrcSZy
1oVsR/CKCpmGLcp6L3fZ6shH2h1Z4t8XBgLW3TU8EGbYSj8Du14Au5UTWwft
kkUCQZTnKJwp4v0MwUNN46U9x7bCp3l5qBmBBJVFcJ9GgyTMABhnflOeRjSM
Ni/j450+TBvc751oG/2NoLOCTKskFvqvcceehQa3uifU9ghI4H3zkYwAY1Vx
yH3QCbgPsh7k1QAWYRAV3jH4yy0UMFAItPHNp52kQS7fsqiSkQvOU/cDn46a
eJNYlqOXhwPcyR82nL16ScLO42LKXMGg5yFqRJURNnIW/Y/5C9eWQXFKHLv7
AL8e52vHl6VVlfD29gPll63PE405z0xVTmSHer+/PhZTXU6+HjpoD4wEwzYf
Rnm5tGqClv7Tgv2RfmOkEgNJbOA8hF/h/ThOciYaTNwZu5rJ9XIiHcA+UnUN
MfY4NDiYDHAeu22UV9qg0OIdzcsC3GbrkiXj/h7ZCdNnCMqkFESwGtPrdk4s
qt5Tr7QOC2gX8CFTjU8O1bLOVabSIpF957X74ik/qPgHa+qBVGCVkJsyWjRm
wEQfuRA0m7dRCEE2prH8wI1acSHRd3/wEU7X2XON+/ZsuzwJt/U3ACmbTpfS
HR9Lfa6Fdd2E6zlv97uQ8DJJCDCr9SgfY8PE8XNbPNDPlXuriRtr5FojdPcw
eJ8AWjjn0pgC1qMAJJYrX8Ld+eyyDJ3DqhCMoPLeJ3cmAvord50uPNZMpAij
0+B9dOwDTOadHKXtyqU0ZaihPZ8ieRhLdliwkRuiDCGUj2wM4cc0EtkhdAfx
ZWZIQy0AgASPnMO8pJ0NwJ8eQW5xRHHcXozEVWpUAayJBG3CPWAwJB5sygsS
0eoOcMdoSJR1c1sTYrCdgEz4HpgYJfFAucYPPKFZsonWp4hlqzVRD9/9wI6w
NsfPbPJZ7Hi+eC4HNPenjLn7UuyM4kbEh95yHzOWZQgdsCQzmHk/pdcpzCkB
IFGwn+FIRZdf55gBikYfmxGz1KEiScV+mHgVzNzIlz5E5bA8L0dCRX4j0SiH
JNCwR/l7oOg8T3aEvErmG21Re5AkZL3JkLWMs8VsDohGaqwcKhi6l+/dawMN
csU3FrOo/doWNXmmXxhU8yaXaHukxRIq1JPiWXdvVS+FtbzGPj54VQkEseiR
Qx48k0y5ZBeXImKSICNHVkc6tBis/0Q2+nIpVL65eniCy5CaDU0g7+RS8+A2
miFm3hVR/5ApieWePJAhlgyOvFDXZYgc9i2i8NZvfgYmLD4XxUtbtsYe/0JP
1mLrgvCrbtAKPpW0jGJI3H2B14uPKz5KqxATgQgBg4FpPcx5/MGt4GrAmLSG
fSdimm6fv3Smhh/0noGJYhEpXh43m96ndHKoQvXpQ8rF2bwW/pfc+GmjOYuP
hTnYxJqFmFUWH73Afsh/vkZCF/aKSqQNZR+XsAL/uh496XoK1AC8k4iRew37
DUOu6qJZyaO0wx/47huuayLpoiCwKDaqCedh38XWiQrzVxN6ynPGgdg6Ow1I
IU6Y5W0TsSHpiM2NLHqhQeXDAc5qDpJySG5LjZRspZ3NGUgHVoIgkq2Jf1XN
ztKwMuPUuA6/ipEUiwLayazMYDut2iusXVWTcE18pbzIqGcfqGLP+5duBHcP
XyOf7H1U+zsQ6QNuC2hUH4iCJ4hYm8sq5FqdJxHuDUa4w+rlMcX2qSVOKxqA
5dNZLKP2TZ2VB3M3wwLxipIvGisKUQ0GiZShoYKP2z8C5P1jB5Onw66l9MHA
x6iD0OwYm4FR6byqRME3nsbzJFrBGpnx7Ci8SreNtsssXrpgNT5JVr2cXbhh
c92kl4Tj3eNtKRLtR2nKoTxqUoRF14HlYtaoMQFaQ/cQACxsYy5WJ97pnTM0
JbchvkvCGzMwI1aKcbKYxE1x+8wdxz0gnE4fUNFCEIRCZ27EwrP7dj9/F5qb
8FAwtRmGR3Gj6Y7nT86Px5tabOz9GWPoj5wOjTaFicAIPJvf6UUs52YJvsMp
lAsVFTZSvg/1DziCfdoKFvTADhvOaAnXfQ6u+yyTkosR/HAGrAgaa7zrO+6g
9zYkHrbxJHg0hjQz/JgC7wMuVFJFFq1UM3ZZRcJc6vN3bsIpE8EDYKz9+jI0
AcE+8jDaAfXEBTcWH4PwpaTM1VJaNbq7cbaXvqZEqzYeh9ecxVJAuh01oWZJ
4OsXLLfyyKkL5nqp6BUukj2x27MSntl4FB6pAVKPxH3DnVPcU8kAuZ+C6sDK
qohBgZ9tUdcQAU6SSOHMwKuDOWp3g0QmNh7utK7wMGNIaTRRCWo5SVFzUjxu
oL0IrvUg2tP+6exUCwAwyY2RoNUUOe9sbEdNiYpEZXPX+c8yHvJBL8qLeeuN
Wxe53WAp5NykLIJXGH7LFJ30ekjMeT+imkklUE0QY3CtJc3PLG+AC52lrWAq
0GMbD5XBCijOeX60qEXL4KByU8SdEv5UUzap3SNyuNjYYo/Y2zmfZFFM64ul
5IsRpOX+pCmmSScQb+uFhRHB8RI7DpLjKK+q3tjYx6WJB0xAS3o3j6KQf4+t
iZblCwl0XyhjPtqVste7rz/5dxBoIZhurEutMDUwcftOMDiqb1l6iBUvPQB3
/dUCVac6zMPxxkOzb3UaYzDoACZZyfoSLU/XNh5gEfpd0wPd42BkIYJ+xF0k
q0Uc9phwOTjf4+7yFIjPxqbMgHhQXh4XFwIu1ElbFiTG5w8Fgn9ZTycqCYgr
vtatL9WkMMvJgtEJ85PuUtndZ8HxMB7CMGDeo9b1lrySHzTjTrP2/PHo3dsO
hYL+tlOUQ1AL4nVA7XBt9fQWbbr7ft+0llwHSs8ZPAW38rl75LJl6rZvZJba
uh36twSI/uSXUvCfdJuKmx9p0rffup2y1inlA5zU2T1dGiePzBfrjJ5Hidui
T0kNwZzRjzI8u6M/rWs5bsxXNwhbfjzeNs+jTkDWfsVMk0a9VlOtl2uEM8hq
BYwoH7xXzOGF6uzsdbnlO4nGR+gZLAz5Tr+qzj6482++/VQSt9tPtr6+9SSG
NF29fEspMJMkX9KjoTfK6+dtKEZ++Vxz5nG/6UvY9OShqjep68n8DAENXrbj
KKToF1AUtC9CZSOWpU49LUlCaFpZCU33Bjk6vYk/0X6lYDqxIDSK9IFgL/oJ
8ELEZ4ENVY4HngfkOp5P4jeqdETPtOzfGhcRDDZpXTyklcls6TGAlrRKweow
fPG2ebD7X8etBRAlkgQmuR/OYsWqiYEVopD+kH/QG5pdbR3xis7BGRAuAkyH
4nkr4j7NoGhr4iSBXGrnXIWHJiYl7qZ2tCg6qfU9qGg09i5a4QkYtjaVRplO
xJREZKHu2aPRSIA/IHT7QcKZ79vWSufv5+9UNk1IDN3pRi9IaIykaxoD+dNr
bKvYNlb2wgF0zdAbKbjGdEti5y9NJ1NZo5orhiKIthbdyglRDl+A7lb9BQoW
y8nRMwekrtZJwt16kup4iEVCgIqVoKcaxLSMV+OViYRs2iQ7JI6ZygIXdsYR
ZnwDeGqNFep3es6Ww0xF/UT0SdsgctvR001/C/HWMej/leMfIcNqLvjf2+7O
1OPAeqpfCS8u/NG7iXq0+AhCuFMK3GmAUmHbONiR8BevpWGf/TbDQzRFhuml
U5h+ApF9zYAzCjRSEU64Ove+onouV2ShcA90SwgQJxR48jU6MkFeTXHv2L+a
ROulJwMJFwb03//1fwpJ8b//6//S2jjPEgoKcR/DlFnjk0XB+xSBkvkkqxI2
HjfinhfUDupydC/s3Ty7KHGtRgwcaS6MI0pyvyxSgnCZi4JRNlMnSsPbTx9+
/+WLkM4I/UCoAcaOAGpDTjAypzeLkX4mzAuByNw/ea0pS7v39sZjKl32c4vP
J+OIw9f9kwoC7OYONXOWr/6vTTa+qpB6889ZitTayR9udDjJv8kWrqzO1Xn6
q1m5kF9RKRKQANCQn7ntcT5CNhIbuTsy/P7Zygu9ER88Wz7/0x1JyTe3uqTR
7LFRupGl5NHp7uuThQORnFpEqqPDsIK9dYEZLIumcucXLsdFAn1UxaM6AySG
xqHTCZjKsA5DpcG5VbCkoCCVvoM7KAncQewm4R0rLXBGqxnnPxaTqHWVEPoa
PKycxI5jTKjUIEET7qyYiikDWaGJkjpDPfswCkRKO40/Qw8CGYE4gYjD23tL
bERypprjwF4MyNW1AJDJxcoDrV3kdzC9rlUiFzGV4toI8NvvCzXrWefJQVil
nfVKjihfN5/KBKX7jPI4t+9H8hZTIGjGber2hKP9D52l/00y9s0tcrGvMB0R
C3ubhD2yFOdq89RSfJOYXdaYJQDS1aWf+lzx4Mtv6MXoLjEQobEPwpxck6es
y3Rov/7Xetvd9Fd2912srNlR6fe/ozW908N7LO43HpHa3eHXxxrY8dXjHUZJ
fd0wASDvfqrulC3tHsHrz9/dlNA5/uAu+YkE2JA+DFSnBn8Rjz5KZAbJa1K5
NjyzRpn2qskKZ3Rx1gH8UNRAAyIklJGsxbA8XxoEiMZQEHvIqn/5kvmv+loR
8dDzGgBLwGwrtAJKAchwFEqvcFYjaaBYPV4B/gSQwHv+ehbqmI77+ljL+Q0H
IBw00FamrktU0yZlY9ZvCLtOi1vPeCNVws5dOulwA53Qtc9aoJSxqnJbcud6
Xl1RSTMHMzghx9dljWnB84a1XIpSWZLlS6yw0haoNng5+1jN61lUMZeQJgjr
YODrMmLMJXl0T7PwsiIrsGu5Qp+5elOiCoci3snubrQ8kmOSi4AXGuYnYXFt
7OxsnozdXcVKZREnN4mbGpHvY+lnCCytxaN4ZDwU60PycnDXz4I9DAc4c3pd
14tAhNQSzyCQcArMmG26AnOIhSH8SI14nhtENmCgW7LaWWlCEVfe+BasFBY5
P9/Y2tk5n/x559Hjp9ud2fIHyFKEJ35j11Jh4we4gh5ndOmzs8Xzja4VUrsw
uvlw1qMFomj5CK+mAwHbE6CpPtNEQSKJDIlhQSrUDft/T8ddXtYdhrOfLytR
irFOHI1Cao40AKg2mrcJiGkF3U/hfYC7K7+os+KSFJZwu+jYeg4uP/QrmiHT
9ad5JQ5wdqLdeMKbnaAPT8RhZX1LBGQDcZnk3OXUrZGyWo+/oK/4COIfy7O4
c5lSWNC/asAmeLYUxOmOCqsStmTrmxC2z98plsn960sy49weY3Tr3ifVuBOY
iU22CgOMcjnBIKzhBEx6mexMVIQHAIwOyAM8OEkm0cnAeMAYEfFYK+wCXLDC
1Tu3RsuhEUY6w09+d8dZ/vtYy90AhFjLIWyeNMsArbr+XphonyJIdMhjyLMX
db+SLLYfEiMf1EtpbrA+bdqc3kYOFjuaY16fZ7ElCiCDR8oDXUQlrZqOBkzZ
PebpeGudsyQbnHTkhWRedjeNATWjhQOmM0ZighszuzoVGmdDL4eZdAgmQ5gC
lQ2ZBMYEJWQvyJjCoGfjGmS+13yPr9mbPxpvxcj79VjvQCeNPhyXdV/hGx2S
/nosa+W1UcTTtQ1wSll9U6txOWLpucA6QiRVyc47fePhYnrc8+98bXZ2cRmf
/W6vQ8Gv791klxh656kFr3DOE/b7B4IHXYOBhirNrm+8RGxu1MOTNUjN9hEr
u4h6Ux2VwpPdMZ8phRr+PkY+wglcj2zdGyIyCD6YD6mv4s+NcqAc3KeTAgmd
+yy5u4+34nE8C7VuoHNa5PcfLOqz8eXianp/MIZYRJyj9g4d56cQzkumQ1AR
A/KdWvMHkSAep5VROHofG6yl0+e8qsHseA3SwXkabWi/rFcL1a7lw8UEufGX
81zPVBxkurlZIwTTZURIgivVcFVXhcGN765sIy/dIq2ay5gJ3VjdWi9fQVv0
3qqlcYK244qgZ6qxzbstpsjAe/MZz+1kKrMsR1eIV0oOJ/5oNqdTfXzPXEie
z6a3KYDAe5TvrqqFf5GT1IE5yUWqcdjCH0nKgiGUjEGiC7JZNX7Vywr30Uu/
jn+bR/a3umDD6EchNMi/jabLT/437nOZTM8HyU0HzzDViyl5EcFn9juAfVzD
b25uksinv2hza3vlvXiIxQ19vcvp7VedxFGouDBvUf9d3tFtPHROi58wzB/I
AA1jN9Dt+fVSqdSxJKT5UUXbWFQY3OlTTqS2x9Tp/pR6BGKIcctltAP+qo3H
CNm+ZVEooMWmu7YNIlNtgvc4gGSRqTXL65tuxTVDblURE2L6e3sNOFxw95bN
sNO1yvbO/BJp3u/6wjTyTE/pdAs5Nc3zLFabmQU36lep91Ro9iX2oNW5dn1I
1jdpsYqhKC39XdvrZkSo3HKG+uQOi0P9CWeRTSqzG0GxPGVOSjqmQwvIi7XC
J3QaGJ0GY70dYjN6lRF09aNkxxNj28nVQjSncLsdM04xoSU7VTU9fefCCpIs
7wbHb7e/iD53AENG53COKt1tgXBk73th3eDFMgEtuc9N4ZOxslFWi2EWVBCr
xi80ek2MF+0f5gTPdA9fjx892j7Z+bZG7Ln7k6KbKYky8jryUiO81GYwzA8t
Cb7akmlv9Klf9kDdBz5PHfMvSCa9B60nDp+MCL/Nos53nmZfUAiyYYumnJ6P
RUPIzQvnXMjK4JgllNGZqm947Jxn00wzjIO4gwZyGmwljLNCOPBxiv1+A3TA
yiUeCIB7E+fBUFVfMSfOs0+PT53Tc1iuQbhKjrpfaOOFblA5AYr5hzJSkfJN
iNOQOlOhTnyDAtlbEQ4p4v0AXslO3pxdOpvsWq1E5YtbfzznIYgCSJ/gTp7H
exNqrHS5Wa8TiKNzIwqpcZpUbiEybeSDQZnXCfUXXdQ+eqq3TOnRGx5Ey8XZ
JWhF+nu7vUQsfmSB+BBqdk6fmKqv3CmJ55+YskTbXNnU4GRxs/IDXskSM3Hi
ywfVvi2x29uCXxUIu8te8SvjY6Hz4PO37IZXyo1SLa2eEhMiGkPY/+9PK9SW
OdN+P9kYlRhaKWcTtpezsvJSP0XWCW6Kn1AtLFUpAwZ8ljuhMD5pPsh/iOPE
cR244yNQQpO4kWdB3FKOCWnSS4tYC3HEvJnzNlSQMClaJzWpv3U2r9y7/q7T
efjta79yBFnp12nuy44Ud2nebzy1/Mbn3Okwk6zobx9r7rDGcyzyXaXEj9x0
DQq0ClQjPQxfsowb5wvVNsA6yqQKy6ABp8Hf5/ngHC4zpQcNtRC7eROQpMBN
CDZAI9jRNq5BQyaxI5TjWjm+GGcn7YkaUDH/tDjDaMRfxgN5sj7MVWhKDknR
AZ2k0z3h3nCM0x7Tyr/KRJXdyZ4kmhzT392hFX83iz8iPLBl9jWSIG5jTOpf
dGaG9nLg+vH1lm7KyBxBQYjIdjFcYUk3o8OxpCp1/DScF+dIia7spD4teRAH
oSzrcoer0XqfxiNczCiGfCLWNq9MpDtg9J2d1/L9oUxmXsGATN9bROlfbghR
anfsmlpG4qNB0Tsq3q4CZsV9M3QbCqgvtLZPamRT9aj4gZ5NAawClEZcUf/U
OvnKGqb+NWC3g/12NFAjFiA4eAEgzxJp9/a7xmlscDb2FbN7alkSZXqKd+rL
5qeuAwiNXws2Z135yaN4ZOAGi0vjPS+Irr3yIyjYbWaCg0z28mWzpAKHhj3g
R4fVyySXbsGoL78lab/A5EV9SxU3S6hN12qu8hwDO9QK8ziZH83CYf8rIFZ8
ioEYasme5rfM0kTN9OK6UyEHT8cQbyhspPJ+zk4WU69bod2wzta+TqepTu7q
/I4tTGPF2sB3ZJ2XysM185n9MLCgase/SciEnTw46YzgetoTMg84MY8tvD6r
sXOdWXDNqpx7YRYiZdsPBGES4qfjV6Onch/gNRemVvrTrGJlVsS1K0ROk7ps
AsNLuyHc7KZlnwWi6KJlgt0YkeOapINzCmAKZ3XTvadRRHZYsYd0hNXHBJ2m
XVCGAioV/BJ+RfYGIi4+nSCtLbrtlYQN8iMasCvyoxtn85vLHHwZCrTGvo97
cuvJeZed/HcPoq3pwUExvfqHve1/ePH49/Rops4ojMoA6BihyNpugfXWP1hB
Ahmuq25J0ghPAepzIEUTNarbnH/733dpyne9hK2fv5vKp3iQNFJDKuQSjn9a
dEICARwUxL4s84ciCEMbTakT6fcKDLVsrbnUfrVABJnwUWKUGuWNVN1gX1pO
J0gsgboiynfh/sdU8ozYGp5Prk6tXEz2Iq5/NQ3NuuF7PLLIy5lkRcRb25sj
yzVd1ytZjD6Em4eXIUC/mtkRU6uzr1iQhkbqOgJyIiPYz+o7q5nR9UjQp6Dc
kEngirXyEh/Yzm+oennufVhQxnzwaHl3exxFy0IFS1rgDVE1FmwITI3IKQd5
DdlX0s226mD7k72ZZFl0PHTIPfI1fKO2opq5j90pOTbnBiTaGm8y/xoPQyvg
zQqLdCgsm3s+zFjCg31Oa48ZIE0DtUrCtyMnhRacrqzY6MhX4S4294n5kT8q
kN2Co84NRDPv+Vo1Lsc9hw+2Sm8viC1DCzAIhmfIB7CtEYAAMzf73X8ajXIW
N03Bluq2JU+1G8IQ6umi/g3oM1nY9c+Hu2+JqsjctPh9352uqrN5rcVFU+wY
eGVUhr88BHPxy8PGx8JEfGXFfQ7KRUHqiSv7y7RumqlgsW/ZxN0X79+p7OHr
vYPVTYK85EcRmaXS5Pv9xioVpOR178W79wizT8AbnB+/OVp5K7e2la0Dq1zr
qua+ZsV9yLDIvrsHYuUr7zN3dsrIj98eH+bHrlk/V6+q/IfD90f5q/+8/1bl
MV+7lh/tv2tW3klL6Elh6v7xdhcUMPnRwVF+cPT6aP+tXPh/AVs3rbtFPgIA

-->
    </rfc>