<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.15 (Ruby 3.3.1) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-delano-dult-threat-model-00" category="info" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.21.0 -->
  <front>
    <title>Draft DULT Threat Model</title>
    <seriesInfo name="Internet-Draft" value="draft-delano-dult-threat-model-00"/>
    <author fullname="Maggie Delano">
      <organization>Swarthmore College</organization>
      <address>
        <email>mdelano1@swarthmore.edu</email>
      </address>
    </author>
    <author fullname="Jessie Lowell">
      <organization>National Network to End Domestic Violence</organization>
      <address>
        <email>jlowell@nnedv.org</email>
      </address>
    </author>
    <date year="2024" month="June" day="14"/>
    <area>Security</area>
    <workgroup>Detecting Unwanted Location Trackers</workgroup>
    <keyword>next generation</keyword>
    <keyword>unicorn</keyword>
    <keyword>sparkling distributed ledger</keyword>
    <abstract>
      <?line 41?>

<t>Lightweight location tracking tags are in wide use to allow users to locate items. These tags function as a component of a crowdsourced tracking network in which devices belonging to other network users (e.g., phones) report which tags they see and their location, thus allowing the owner of the tag to determine where their tag was most recently seen. While there are many legitimate uses of these tags, they are also susceptible to misuse for the purpose of stalking and abuse. A protocol that allows others to detect unwanted location trackers must incorporate an understanding of the unwanted tracking landscape today. This document provides a threat analysis for this purpose, will define what is in and out of scope for the unwanted location tracking protocols, and will provide some design considerations for implementation of protocols to detect unwanted location tracking.</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        The latest revision of this draft can be found at <eref target="https://maggiedelano.github.io/draft-delano-dult-threat-model/draft-delano-dult-threat-model.html"/>.
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-delano-dult-threat-model/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        Detecting Unwanted Location Trackers Working Group mailing list (<eref target="mailto:unwanted-trackers@ietf.org"/>),
        which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/unwanted-trackers/"/>.
        Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/unwanted-trackers/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/maggiedelano/draft-delano-dult-threat-model"/>.</t>
    </note>
  </front>
  <middle>
    <?line 45?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>Location tracking tags are widely-used devices that allow users to locate items. These tags function as a component of a crowdsourced tracking network in which devices belonging to other network users (e.g., phones) report on the location of tags they have seen. At a high level, this works as follows:</t>
      <ul spacing="normal">
        <li>
          <t>Tags ("accessories") broadcast an advertisement payload containing accessory-specific information. The payload also indicates whether the accessory is separated from its owner and thus potentially lost.</t>
        </li>
        <li>
          <t>Devices belonging to other users ("non-owner devices") observe those payloads and if the payload is in a separated mode, reports its location to some central service.</t>
        </li>
        <li>
          <t>The owner queries the central service for the location of their accessory.</t>
        </li>
      </ul>
      <t>A naive implementation of this design exposes both a tag’s user and anyone who might be targeted for location tracking by a tag’s user, to considerable privacy risk. In particular:</t>
      <ul spacing="normal">
        <li>
          <t>If accessories simply have a fixed identifier that is reported back to the tracking network, then the central server is able to track any accessory without the user's assistance, which is clearly undesirable.</t>
        </li>
        <li>
          <t>Any attacker who can guess a tag ID can query the central server for its location.</t>
        </li>
        <li>
          <t>An attacker can surreptitiously plant an accessory on a target and thus track them by tracking their "own" accessory.</t>
        </li>
      </ul>
      <t>In order to minimize these privacy risks, it is necessary to analyze and be able to model different privacy threats. This document uses a flexible framework to provide analysis and modeling of different threat actors, as well as models of potential victims based on their threat context. It defines how these attacker and victim persona models can be combined into threat models. It is intended to work in concert with the requirements defined in <xref target="I-D.detecting-unwanted-location-trackers"/>, which facilitate detection of unwanted tracking tags.</t>
    </section>
    <section anchor="conventions-and-definitions">
      <name>Conventions and Definitions</name>
      <section anchor="conventions">
        <name>Conventions</name>
        <t>The key words "<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 "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
        <?line -18?>

</section>
      <section anchor="definitions">
        <name>Definitions</name>
        <ul spacing="normal">
          <li>
            <t><strong>active scanning</strong>: a search for location trackers manually initiated by a user</t>
          </li>
          <li>
            <t><strong>passive scanning</strong>: a search for location trackers running in the background, often accompanied by notifications for the user</t>
          </li>
          <li>
            <t><strong>tracking tag</strong>: a small, concealable device that broadcasts location data to other devices</t>
          </li>
        </ul>
      </section>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>Incorporation of this threat analysis into the DULT protocol does not introduce any security risks not already inherent in the underlying Bluetooth tracking tag protocols. Existing attempts to prevent unwanted tracking by the owner of a tag have been criticized as potentially making it easier to engage in unwanted tracking of the owner of a tag. However, Beck et al. have <eref target="https://eprint.iacr.org/2023/1332.pdf">demonstrated</eref> a technological solution that employs secret sharing and error correction coding.</t>
      <section anchor="taxonomy-of-unwanted-tracking">
        <name>Taxonomy of unwanted tracking</name>
        <t>To create a taxonomy of threat actors, we can borrow from Dev et al.’s <eref target="https://dl.acm.org/doi/fullHtml/10.1145/3544548.3581484">Models of Applied Privacy (MAP) framework</eref>. This framework is intended for organizations and includes organizational threats and taxonomies of potential privacy harms. Therefore, it cannot be applied wholesale. However, its flexibility, general approach to personas, and other elements, are applicable or can be modified to fit the DULT context.</t>
        <t>The characteristics of threat actors may be described as follows. This is not intended to be a full and definitive taxonomy, but an example of how existing persona modeling concepts can be applied and modified.</t>
        <ul spacing="normal">
          <li>
            <t>Expertise level
            </t>
            <ul spacing="normal">
              <li>
                <t>Expert: The attacker works in or is actively studying computer science, networking, computer applications, IT, or another technical field.</t>
              </li>
              <li>
                <t>Non-expert: The attacker does not work or study in, or is a novice in, a technical field.</t>
              </li>
            </ul>
          </li>
          <li>
            <t>Proximity to victim
            </t>
            <ul spacing="normal">
              <li>
                <t>High: Lives with victim or has easy physical access to victim and/or victim’s possessions.</t>
              </li>
              <li>
                <t>Medium: Has some physical access to the person and possessions of someone who lives with victim, such as when the attacker and victim are co-parenting a child.</t>
              </li>
              <li>
                <t>Low: Does not live with or have physical access to victim and/or victim’s possessions.</t>
              </li>
            </ul>
          </li>
          <li>
            <t>Access to resources
            </t>
            <ul spacing="normal">
              <li>
                <t>High: The attacker has access to resources that may amplify the impact of other characteristics. These could include, but are not limited to, funds (or control over “shared” funds), persons assisting them in stalking behavior, or employment that provides privileged access to technology or individuals’ personal information.</t>
              </li>
              <li>
                <t>Low: The attacker has access to few or no such resources.</t>
              </li>
            </ul>
          </li>
        </ul>
        <t>In addition, the victim also has characteristics which influence the threat analysis. As with attacker characteristics, these are not intended as a definitive taxonomy.</t>
        <ul spacing="normal">
          <li>
            <t>Expertise level
            </t>
            <ul spacing="normal">
              <li>
                <t>Expert: The victim works in or is actively studying computer science, networking, computer applications, IT, or another technical field.</t>
              </li>
              <li>
                <t>Non-expert: The victim does not work or study in, or is a novice in, a technical field.</t>
              </li>
            </ul>
          </li>
          <li>
            <t>Access to resources
            </t>
            <ul spacing="normal">
              <li>
                <t>High: The victim is generally able to safely access practical and relevant resources. These might include funds to pay a car mechanic or private investigator, law enforcement or legal assistance, or other resources.</t>
              </li>
              <li>
                <t>Low: The victim is generally unable to safely access practical and relevant resources. These might include money to pay a car mechanic or private investigator, law enforcement or legal assistance, or other resources.</t>
              </li>
            </ul>
          </li>
          <li>
            <t>Access to technological safeguards
            </t>
            <ul spacing="normal">
              <li>
                <t>Normal: The victim is able to safely use, and has access to, technological safeguards such as active scanning apps.</t>
              </li>
              <li>
                <t>Impaired: The victim is able to safely use, and has access to, technological safeguards such as active scanning apps, but is unable to use their full capacity.</t>
              </li>
              <li>
                <t>Low: The victim is not able to use technological safeguards such as active scanning apps, due to reasons of safety or access.</t>
              </li>
            </ul>
          </li>
        </ul>
        <t>It is also appropriate to define who is using the tracking tags and incorporate this into a model. This is because if protocols overly deprioritize the privacy of tracking tags’ users, an attacker could use a victim’s own tag to track them. Beck et al. describe a <eref target="https://eprint.iacr.org/2023/1332.pdf">possible technological solution</eref> to the problem of user privacy vs privacy of other potential victims.</t>
        <ul spacing="normal">
          <li>
            <t>Tracking tag usage
            </t>
            <ul spacing="normal">
              <li>
                <t>Attacker only: The attacker controls one or more tracking tags, but the victim does not.</t>
              </li>
              <li>
                <t>Victim only: The victim controls one or more tracking tags, but the attacker does not.</t>
              </li>
              <li>
                <t>Attacker and victim: Both the attacker and victim control one or more tracking tags.</t>
              </li>
            </ul>
          </li>
        </ul>
        <section anchor="example-scenarios-with-analyses">
          <name>Example scenarios with analyses</name>
          <t>The following scenarios are composite cases based upon reports from the field. They are intended to illustrate different angles of the problem. They are not only technological, but meant to provide realistic insights into the constraints of people being targeted through these tags. There is no identifying information for any real person contained within them. In accordance with research on <eref target="https://dl.acm.org/doi/10.1145/2207676.2208573">how designers understand personas</eref>, the characters are given non-human names without attributes such as gender or race.
The analysis of each scenario provides an example usage of the modeling framework described above. It includes a tracking tag usage element for illustrative purposes. However, as discussed previously, this element becomes more or less relevant depending on protocol evolution.
Note that once a given attacker persona has been modeled, it could be recombined with a different victim persona, or vice versa, to model a different scenario. For example, a non-expert victim persona could be combined with both non-expert and expert attacker personas.</t>
          <section anchor="scenario-1">
            <name>Scenario 1</name>
            <section anchor="narrative">
              <name>Narrative</name>
              <t>Mango and Avocado have two young children. Mango, Avocado, and the children all use smartphones, but have no specialized technical knowledge. Mango left because Avocado was abusive. They were homeless for a month, and the children have been living with Avocado. They now have an apartment two towns away. They do not want Avocado to know where it is, but they do want to see the children. They and Avocado meet at a public playground. They get there early so that Avocado will not see which bus route they arrived on and keep playing with the children on the playground until after Avocado leaves, so that Avocado will not see which bus route they get on. Two days later, Avocado shows up at Mango’s door, pounding on the door and shouting.</t>
            </section>
            <section anchor="analysis">
              <name>Analysis</name>
              <t>In this case, the attacker has planted a tag on a child. Co-parenting after separation is common in cases of intimate partner violence where the former partners have a child together. Child visits can be an opportunity to introduce technology for purposes of stalking the victim.</t>
              <table>
                <thead>
                  <tr>
                    <th align="left">Attacker Profile</th>
                    <th align="left">Avocado</th>
                  </tr>
                </thead>
                <tbody>
                  <tr>
                    <td align="left">Expertise Level</td>
                    <td align="left">Non-Expert</td>
                  </tr>
                  <tr>
                    <td align="left">Proximity to Victim</td>
                    <td align="left">Medium</td>
                  </tr>
                  <tr>
                    <td align="left">Access to Resources</td>
                    <td align="left">Unknown, but can be presumed higher than Mango’s due to Mango’s recent homelessness</td>
                  </tr>
                </tbody>
              </table>
              <table>
                <thead>
                  <tr>
                    <th align="left">Victim Profile</th>
                    <th align="left">Mango</th>
                  </tr>
                </thead>
                <tbody>
                  <tr>
                    <td align="left">Expertise Level</td>
                    <td align="left">Non-Expert</td>
                  </tr>
                  <tr>
                    <td align="left">Access to Resources</td>
                    <td align="left">Low</td>
                  </tr>
                  <tr>
                    <td align="left">Access to Technological Safeguards</td>
                    <td align="left">Normal</td>
                  </tr>
                </tbody>
              </table>
              <table>
                <thead>
                  <tr>
                    <th align="left">Other Characteristics</th>
                    <th align="left">Avocado and Mango</th>
                  </tr>
                </thead>
                <tbody>
                  <tr>
                    <td align="left">Accessory Usage</td>
                    <td align="left">Attacker Only</td>
                  </tr>
                </tbody>
              </table>
            </section>
          </section>
          <section anchor="scenario-2">
            <name>Scenario 2</name>
            <section anchor="narrative-1">
              <name>Narrative</name>
              <t>Strawberry and Elderberry live together. Neither has any specialized technological knowledge. Strawberry has noticed that Elderberry has become excessively jealous – every time they go to visit a friend by themselves, Elderberry accuses them of infidelity. To their alarm, over the last week, on multiple occasions, Elderberry has somehow known which friend they visited at any given time and has started to harass the friends. Strawberry eventually gets a notification that a tracker is traveling with them, and thinks it may be in their car, but they cannot find it. They live in a car-dependent area and cannot visit friends without the car, and Elderberry controls all of the “family” money, so their cannot take the car to the mechanic without Elderberry knowing.</t>
            </section>
            <section anchor="analysis-1">
              <name>Analysis</name>
              <t>Here, the attacker and the victim are still cohabiting, and the attacker is monitoring the victim’s independent activities. This would allow the attacker to know if, for instance, the victim went to a police station or a domestic violence agency. The victim has reason to think that they are being tracked, but they cannot find the device. This can happen if the sound emitted by the device is insufficiently loud, and is particularly a risk in a car, where seat cushions or other typical features of a car may provide sound insulation for a hidden tag. The victim could benefit from having a mechanism to increase the volume of the sound emitted by the tag. Another notable feature of this scenario is that because of the cohabitation, the tag will spend most of the time in “near-owner state” as defined by the proposed industry consortium specification <xref target="I-D.detecting-unwanted-location-trackers"/>. In near-owner state it would not provide alerts under that specification.</t>
              <table>
                <thead>
                  <tr>
                    <th align="left">Attacker Profile</th>
                    <th align="left">Elderberry</th>
                  </tr>
                </thead>
                <tbody>
                  <tr>
                    <td align="left">Expertise Level</td>
                    <td align="left">Non-Expert</td>
                  </tr>
                  <tr>
                    <td align="left">Proximity to Victim</td>
                    <td align="left">High</td>
                  </tr>
                  <tr>
                    <td align="left">Access to Resources</td>
                    <td align="left">High</td>
                  </tr>
                </tbody>
              </table>
              <table>
                <thead>
                  <tr>
                    <th align="left">Victim Profile</th>
                    <th align="left">Strawberry</th>
                  </tr>
                </thead>
                <tbody>
                  <tr>
                    <td align="left">Expertise Level</td>
                    <td align="left">Non-Expert</td>
                  </tr>
                  <tr>
                    <td align="left">Access to Resources</td>
                    <td align="left">Low</td>
                  </tr>
                  <tr>
                    <td align="left">Access to Technological Safeguards</td>
                    <td align="left">Impaired (cannot hear alert sound)</td>
                  </tr>
                </tbody>
              </table>
              <table>
                <thead>
                  <tr>
                    <th align="left">Other Characteristics</th>
                    <th align="left">Elderberry and Strawberry</th>
                  </tr>
                </thead>
                <tbody>
                  <tr>
                    <td align="left">Accessory Usage</td>
                    <td align="left">Attacker Only</td>
                  </tr>
                </tbody>
              </table>
            </section>
          </section>
          <section anchor="scenario-3">
            <name>Scenario 3</name>
            <section anchor="narrative-2">
              <name>Narrative</name>
              <t>Lime and Lemon have been dating for two years. Lemon works for a tech company and often emphasizes how much more they know about technology than Lime, who works at a restaurant. Lemon insists on having access to Lime’s computer and Android phone so that they can “make sure they are working well and that there are no dangerous apps.” Lemon hits Lime when angry and has threatened to out Lime as gay to their conservative parents and report them to Immigration &amp; Customs Enforcement if Lime “talks back.” Lime met with an advocate at a local domestic violence program to talk about going to their shelter once a bed was available. The advocate did some safety planning with Lime, and mentioned that there is an app for Android that can scan for location trackers, but Lime did not feel safe installing this app because Lemon would see it. The next time Lime went to see the advocate, they chose a time when they knew Lemon had to be at work until late to make sure that Lemon did not follow them, but when Lemon got home from work they knew where Lime had been.</t>
            </section>
            <section anchor="analysis-2">
              <name>Analysis</name>
              <t>This is a case involving a high-skill attacker, with a large skill difference between attacker and victim. This situation often arises in regions with a high concentration of technology industry workers. It also may be more common in ethnic-cultural communities with high representation in the technology industry. In this case the victim is also subject to a very high level of control from the attacker due to their imbalances in technological skills and societal status, and is heavily constrained in their options as a result. It is unsafe for the victim to engage in active scanning, or to receive alerts on their phone. The victim might benefit from being able to log into an account on another phone or a computer and view logs of any recent alerts collected through passive scanning.</t>
              <table>
                <thead>
                  <tr>
                    <th align="left">Attacker Profile</th>
                    <th align="left">Lemon</th>
                  </tr>
                </thead>
                <tbody>
                  <tr>
                    <td align="left">Expertise Level</td>
                    <td align="left">Expert</td>
                  </tr>
                  <tr>
                    <td align="left">Proximity to Victim</td>
                    <td align="left">High</td>
                  </tr>
                  <tr>
                    <td align="left">Access to Resources</td>
                    <td align="left">High</td>
                  </tr>
                </tbody>
              </table>
              <table>
                <thead>
                  <tr>
                    <th align="left">Victim Profile</th>
                    <th align="left">Lime</th>
                  </tr>
                </thead>
                <tbody>
                  <tr>
                    <td align="left">Expertise Level</td>
                    <td align="left">Non-Expert</td>
                  </tr>
                  <tr>
                    <td align="left">Access to Resources</td>
                    <td align="left">Low</td>
                  </tr>
                  <tr>
                    <td align="left">Access to Technological Safeguards</td>
                    <td align="left">Low</td>
                  </tr>
                </tbody>
              </table>
              <table>
                <thead>
                  <tr>
                    <th align="left">Other Characteristics</th>
                    <th align="left">Lemon and Lime</th>
                  </tr>
                </thead>
                <tbody>
                  <tr>
                    <td align="left">Accessory Usage</td>
                    <td align="left">Attacker Only</td>
                  </tr>
                </tbody>
              </table>
            </section>
          </section>
        </section>
        <section anchor="bluetooth-vs-other-technologies">
          <name>Bluetooth vs. other technologies</name>
          <t>The above taxonomy and threat analysis focus on location tracking tags. They are protocol-independent; if a tag were designed using a technology other than Bluetooth, they would still apply. The key attributes are the functionalities and physical properties of the accessory from the user’s perspective. The accessory must be small enough to be easily concealed, and able to broadcast its location to other consumer devices.</t>
        </section>
      </section>
      <section anchor="what-is-in-scope">
        <name>What is in scope</name>
        <section anchor="technologies">
          <name>Technologies</name>
          <t>The scope of this threat analysis includes any easily-concealable accessory that is able to broadcast its location to other consumer devices.</t>
        </section>
        <section anchor="attacker-profiles">
          <name>Attacker Profiles</name>
          <t>An attacker who attempts to track a victim using a tracking tag and applications readily available for end-users (e.g. native tracking application) is in scope. Additonally, an attacker who physically modifies a tracking tag (e.g. to disable a speaker) is in scope. An atacker who makes non-nation-state level alterations to the firmware of an existing tracking tag or creates a custom device that leverages the crowdsourced tracking network is in scope.</t>
        </section>
        <section anchor="victim-profiles">
          <name>Victim Profiles</name>
          <t>All victims profiles are in scope regardless of their expertise, access to resources, or access to technological safeguards. For example, protocols should account for a victim's lack of access to a smartphone, and scenarios in which victims cannot install separate software.</t>
        </section>
      </section>
      <section anchor="what-is-out-of-scope">
        <name>What is out of scope</name>
        <section anchor="technologies-1">
          <name>Technologies</name>
          <t>There are many types of technology that can be used for location tracking. In many cases, the threat analysis would be similar, as the contexts in which potential attackers and victims exist and use the technology are similar. However, it would be infeasible to attempt to describe a threat analysis for each possible technology in this document. We have therefore limited its scope to location-tracking accessories that are small enough to be easily concealed, and able to broadcast their locations to other devices. The following are out of scope for this document:</t>
          <ul spacing="normal">
            <li>
              <t>App-based technologies such as parental monitoring apps.</t>
            </li>
            <li>
              <t>Other Internet of Things (IoT) devices.</t>
            </li>
            <li>
              <t>Connected cars.</t>
            </li>
            <li>
              <t>User accounts for cloud services or social media.</t>
            </li>
          </ul>
        </section>
        <section anchor="attack-profiles">
          <name>Attack Profiles</name>
          <t>Attackers with nation-state level expertise and resources who deploy custom or altered tracking tags to bypass protocol safeguards or jailbreak a victim end-device (e.g. smartphone) are considered out of scope.</t>
        </section>
        <section anchor="victim-profiles-1">
          <name>Victim Profiles</name>
          <t>N/A</t>
        </section>
      </section>
    </section>
    <section anchor="design-considerations">
      <name>Design Considerations</name>
      <t>As discussed in <xref target="security-considerations"/>, unwanted location tracking can involve a variety of attacker, victim, and tracking tag profiles. A successful implementation to preventing unwanted location tracking would:</t>
      <ul spacing="normal">
        <li>
          <t>Include a variety of approaches to address different scenarios, including active and passive scanning and notifications or sounds</t>
        </li>
        <li>
          <t>Account for scenarios in which the attacker has high expertise, proximity, and/or access to resources within the scope defined in <xref target="what-is-in-scope"/> and <xref target="what-is-out-of-scope"/></t>
        </li>
        <li>
          <t>Account for scenarios in which the victim has low expertise, access to resources, and/or access to technological safeguards within the scope defined in <xref target="what-is-in-scope"/> and <xref target="what-is-out-of-scope"/></t>
        </li>
        <li>
          <t>Avoid privacy compromises for the tag owner when protecting against unwanted location tracking using tracking tags</t>
        </li>
      </ul>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>This document has no IANA actions.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-normative-references">
      <name>Normative References</name>
      <reference anchor="I-D.detecting-unwanted-location-trackers">
        <front>
          <title>Detecting Unwanted Location Trackers</title>
          <author fullname="Brent Ledvina" initials="B." surname="Ledvina">
            <organization>Apple</organization>
          </author>
          <author fullname="Zachary Eddinger" initials="Z." surname="Eddinger">
            <organization>Google</organization>
          </author>
          <author fullname="Ben Detwiler" initials="B." surname="Detwiler">
            <organization>Apple</organization>
          </author>
          <author fullname="Siddika Parlak Polatkan" initials="S. P." surname="Polatkan">
            <organization>Google</organization>
          </author>
          <date day="20" month="December" year="2023"/>
          <abstract>
            <t>   This document lists a set of best practices and protocols for
   accessory manufacturers whose products have built-in location-
   tracking capabilities.  By following these requirements and
   recommendations, a location-tracking accessory will be compatible
   with unwanted tracking detection and alerts on mobile platforms.
   This is an important capability for improving the privacy and safety
   of individuals in the circumstance that those accessories are used to
   track their location without their knowledge or consent.

            </t>
          </abstract>
        </front>
        <seriesInfo name="Internet-Draft" value="draft-detecting-unwanted-location-trackers-01"/>
      </reference>
      <reference anchor="RFC2119">
        <front>
          <title>Key words for use in RFCs to Indicate Requirement Levels</title>
          <author fullname="S. Bradner" initials="S." surname="Bradner"/>
          <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>
        <seriesInfo name="BCP" value="14"/>
        <seriesInfo name="RFC" value="2119"/>
        <seriesInfo name="DOI" value="10.17487/RFC2119"/>
      </reference>
      <reference anchor="RFC8174">
        <front>
          <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
          <author fullname="B. Leiba" initials="B." surname="Leiba"/>
          <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>
        <seriesInfo name="BCP" value="14"/>
        <seriesInfo name="RFC" value="8174"/>
        <seriesInfo name="DOI" value="10.17487/RFC8174"/>
      </reference>
    </references>
    <?line 268?>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>TODO acknowledge.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA9Vc65Ibx3X+j6forKpiUQWA4kWWsnEcr7hUuCleFHFplUvl
H42ZBjDiXODpmV3CIqv0DvmVKqcqz5JH0ZPk+87p7pnBghRlyy5HP8TFoKf7
9Olz+c6lsVgsZl3Rle7UnJy3dt2Z8xePL83ltnW2M0+a3JUns8x2btO0+1NT
1OtmNsubrLYVXsn5xgJjbN0s8r7sFp28uKj44uLjj2e+X1WF90VTd/sd3rh4
ePmFMR8YW/oGSxZ17nYO/6u7k7k5cXnRNW1hS364OPsc/zQt/vrq8ouTWd1X
K9eeznJQczrLmtq72vf+1HRt72ZXp+bezGJxzPrcZX1bdPuT2XXTvty0Tb/j
9lznsq6oN+ZFfW3rzuXmcYOtgTZz2drspWv9yeyl2+Ol/HRmFqZ2rzqzcbVr
ZRQf9XWRNa386Xe2fVlyvrzwXVusek5Zunzj2tmVq3tQacxPW90YZdPJ1yCc
g/+Nr/N5ZYsSz/vw8qIL7/ymcN162bQbDrJttsWgbdft/Ont23yHj4ort4zD
bvPB7VXbXHt3+8ZstznLpui2/QrzVHazKZwe7+13nzXfK3EwvpusP7y/1FmX
xY/N9CNfL7ddhdVmtu+2TctjwsrGrPuyVJk8eSKrmnOZ4ES+xb5tXfxRuH1q
nl/btttWTevMg6Ys3cbJIBdYXOnSd37j07ily3useXOtf3eQbYeTvHZleWyt
p/KvLc1T11EYTdeYh3VuzpsKvCoy89uiKV2dTUj4tpT5flPXLr/ioc1mddNW
mOoKMjWjEg6fZovFwtiV5xF2s9njYrPtrh3/b8ooYHK8FKfObjykxEGRzXWR
O9N7R5JsiSX5ofX8KC9iUOcqv4QxcBzFV9d9ncmMFtOYrKl2TQ3dNc2aHyFU
uW/6NoNwpyXrsHGuuC2yrcndVZE5b1aubOqNUNWYptu6No1VQj50y81ybnZb
rOFvmdbtmrYLkwg1eGdvvHPGgqP4ULRpy3N87r3uS5bYOtNcQ5NJKj9gAq6b
Qy3bqqgd5nXgi87CL6+xxarxHdbNsMVSVqqX5uttUco4jCYnK1vvofUQ76Ii
00C7D4sErs2VUA6m2TMwWpnbdcWqFN7DPvIUcKZC2K5vdw0+Ywrf2VJ4yP3Z
FUYtzZnZtU3XZE2J0TDRskOv/PNxR1lnomofCAEHVT12VdSwY2AoSbY1huf4
qsNCXC/wKM2RDhOKkfvM7kh4bveUjcIb+IO+ohiAtCtIFWVDdRZT23LvMUa3
hz/C/uaQv7IEtWtlPsbiSwgJ99r0IlI+a3YDY96yI5IVWQJW83WZOdBiPDQN
y/hiUxs6DTxTc640FdWudCRep8SqabIf5ybWXqoCVkWel242+8Bc1F3b5L2o
CdTx7SpI/Sv3C5xqnnRiONL/H8rIjeFoElcoOEkzt/bKBaU5w67MFkYJmnLl
yrmKAqf3pH7diBTDmhk41kvO8OGJzUCYBxxw/uSWgceyeWY9RcrY/Mq1XeGd
Sp3dl/iSp9vZohaFCe/uF37nsmINQ5usZlMLF9NropMAIgXZ7GkHZPvcV5qG
sukdHL6lEKzbpsJ5+GBR1PrA2uyaDvQAvsBYlDAdS9nO+dtZHFh7Ujf1QucK
54ENNyt8eUVLQ2sQiPWyWKHqGTcQ9GZEID3lPJyRF0oHuW1UI2jTWvglLoIV
ldTLZCX/0DsyXtY5GJoUcnLqYjcTv6AVZ6a28FBHFEzOPmike0VjAOaAIbQa
dvPD9//lhTFq9ep9I/aBdpI+bUXhbzdOzqFpjxiD1f5gojk3nVSfVnfXFlc2
25u28C+X0FiwEuKU9UBLQQYv1mYkf8ZzF0GirVkXr7B6QdQK0RJZUfOlHMd3
K9DCVcXTHCifuIP6BmcxDWawwSnIS9z9SAavgaBoGcUY4pVfUHdgW2G1M9pT
UWjMkZXOtqCWNt0XsmM93jNO13XiBoSlGXRp02N65Zi5OJdHPPz9MQLFYI6k
KU47zMrXfd+29G8Y0XvQsYPXULVNW6HRCuc4qI/uGctWPMPBYIponUAuTyYC
hmMDUCf3KRt1URV/dMHrjs8XPqGQw6kd37XcWaN+6Y+KHCBSke0CMYHn12u4
d3FoOpF6M3/o78TXQx5K90q8+boFLIwwLzqg5AK5liwQXOywTHSWGaIf+jBY
IeA/IwgE4wVPJONioITAGtAZS9ehJpigRSehFUTcArHugnf1Zgt/opxJB0Vi
dCKzgxECRo1r8QjBEviTFV6GnNciyDK5DpG5xep0jN1y7ja6FSyfOcI0CKuI
UOv+0BetWAAfCOKc5rvv/uFicb7MY1y0SMFIlK4Ulbx5E6V7bbOiLDr6w/Ci
mpSbSIVuaEl//KCpr8g4Onxu+pwkFPIZX0++n9H+IQDkZmBqT568eH7JSJT/
mqfP5O+vHv7Hi4uvHp7z7+ePzh4/Tn/Mwojnj569eHw+/DW8+eDZkycPn57r
y3hqJo9mJ0/OfneiCObk2ZeXF8+enj0+Iau6idARO4DhKyf8b3et2ELrZ9D2
DGGosvfzB1/+7//cuU82f/XFg7t37vzTmzfhw2d3Pr2PD3B0ta7W1NBS/UjH
PbO7HSyIOBVIIeAeOF6qXHqIUm0IfsHcj74hZ35/an61ynZ37v86POCGJw8j
zyYPhWc3n9x4WZl45NGRZRI3J88POD2l9+x3k8+R76OHv/rXkhB1ceezf/31
TERmIkIL89FHUFy6OiDjmvDjo49OxR0z1D7ipASD27oXnCATidMWv0W7LlPu
aNp/2pxtLyNVYpz4IGYf6nwOFYGm0noCJCI61dXqhu4rG4Hh6FmEgrEqhdUr
kDxXFbel2EzFK+oAE0QbwY3cdnbAOwHdUC1jjob6N8LkNOsxMBnDhcNwIhgl
p+mqFBLlDawd9sXvBYU78aE+LiYOQQbYEhPm5P9WbXDgmgRC5Z77/rzsXdcQ
mIxZMcQHS/PwFbyv4M0O6HzXebX77kqcww2btNpP41B1ugIqVoDJwOyQhQxu
jOo8QZOVlQngyJz1hfo8V2/sRiL5myuFAG660tI8aq5BGwDR5w6elr63XOr6
3+SuAvs7wY+//zBmcBwcYN0tC5u1kjy6+/Hde7fv3Lt3d7nL17c4rcu2dVM2
G8gRYEJT9iqTlAdwpGz2BM4ZbBRMh21jMOvaFuKGg26DDc+aXIMpqNelfdXU
TbU/athns0vgFgqDk10NQw+c6LVTT4Y14P0EsgOJh00LNvzmSXKuZ7tdSa34
Mvj7D5+cfXlrcOcDQ/JyabNKeJE3xW2mgh51VXn7zsfLO3fuf3L73if3739y
/7PlvU8+u3P/s/u3AmIYgMHYbVLlxumigO7rrOwZRI+/smXEIIqXdN+FO4AG
Ea+A1SFYbB1WcYKBaEkaQdA2bBcYsHTeAh8OokF8p4CGnnY/DwnQki9BwZl7
aSJkCPG2KrdTmM9nbVgiExvRtBFTAD4QMAtgWBfdoMARtMzEBWcgH8eICIQp
Mn/jcKEOe043OLwhhgwML5IZSAhlJdC9J66qc0UihZjtKERzs+oFp7pXlkEL
1yVyclHLJ0CJD8QSUu3D/iJfA9KTvS41oHj4aqchq0bAku6LT08l8BqQuYTF
BeGthATiXJh/6vp8r8tWux7sgXMonGD/EFrgy/nwbTgCkay5ubiUZLqt9bRE
cUVpQWSZLwNBTwG73DGikmUVKcZEQg2onEcy8a34Aj6yx+ZfQL2aV8DpnUBw
RZ9h3UcI7k7NY2zUK3QM2BRzb3G4sHqII7Yw/ZxRo4BhDvL7NkbqJ9FtRJXe
Sd3Bx609cXnRV6fmEWEMQ+Aj80lYLacsZziaRfJReCtGo+UhqXPEPVAOKxkE
9SXHwDZ1I2sWCDipsjSHEPdiOIDHzfWpOY/M5iq6iDDi6ijR78sERGrpndZp
bshP+D85cfLd3nxBbTs1kEpSrNWnIT6GnJJJKl4HKhzzVlnTl8nCBX0DQ3Sr
EAzR1DkzW8DfH4qLoCMvTcPw84fv/0Qn4vIfvv9vHXNrHo4rhsIhYKyoPil9
unJgXdG0IqrqlSoNu+woZ0nbWbAakI8FIvq3vYh5nWNMDuTmweBoD8pJbml8
ju/g59pdc8a6UbFJ7NXA1uZ5EdPYLh0wE1Wc5dA+hsi/XgOw1ILG3CFgWpqz
IK1DqD6dZR4jxHAeyXRKdvGIuXxvwxbI/3sya4Gkn8WovY9ShfUwY/Cm2HfM
OXi7JhuCaOx4JqrgMBotnOoVsyeDfARN0mxY0KSgMHTM1Eu4o9ZUoBXwIeNO
BBYwh4xQF4e9sR2VobTwbZTcTPOoDCrchiuPskqEKMLZkYQeSPixzfX1z7k9
QFO3/xtub3yoBwgXu9n0ts19kiwofnnIiIPN96x3cMMTGzB/69zJlRwElpT9
xP8LmNwCxvBvubaabCwynK9UECUBJdgqs3AE8PDvkBIJv8Zv/3mU5L1TpbM+
+me82omh1n3Slgq1YjkFv0JUKClS2QmVp0b242OV8KBQo4A8lcokGJXgM8DA
AW+uXGa5nWJcQqLfwiHkDKQahneao0xAndB2vCDdilQF5pIwTbZa/CZnt2MH
z1xMKGQOydPlJLqLGBkvfkM8oFXHo1Hbe4d9ESi1DSarJExjvj7u6cqPt6fq
dSN7GbzH5Tiy7r0NtXgoYNw6k1MHnjSAAuy/luhCSvkTNqqcdjctfRTL3wZ4
mSYP437K1Dew8fKQ9gH3nZrPm5AQPYYKE8x526oSGX8At6qRic9cjWi6iT5d
vDwTK9yKRkJ8cximsLOCBABkQUml5iL5434HsBtLRRImk0j1b+TMPvQLDIFU
UZa9ZgpGKWxbb8pU+I6iMZqASi95xonsKTMrRx8wSplDp0tBJVjX0xOMEj6Z
pikKppMZ+7qGDFk55VSoDAH9NP1mOyrCh2BY7U+s3ew1XZbAm0TkTBiRgBgI
hLIiw2XwWtNElVSNmE9rczoSPQb4EM3P4a1vGDlqkYu5uaG+nmLntyYVYi7h
7t2PP/3lp79c4t/PPvn03i0Fgwm26aFuYBlrwwLitq9gMtiY4lOpCLKmjUmD
Md3wHJl3MJjGLUViUloNDHUM8aPgjCr6Q1gsahpPOsXCQ4pjFJavYP+0WhCT
GnaaTNO5QupA60tRumjyQ7OAH+UnsIW88FnvKbzMtWmVKZSU40wwxuywUU0S
z+/9ADe06UwSZfWQPHRXwRAuZ0+bLiQ1GeGDaGVzUt2YCaBPldSdsMHlmmcR
Y72iGKciiqrpSF+mtRcBIgI0sUdv50MtavxOPJWl+YKBjB7HXEBqhLeHNZ1E
y5QSKbeO3pKcXPjzYI/B9HxgnkeZuKMPPjBPbavnNJs9gf43Ms3ZVZPZvNFo
FfDd7Jue4J5BbsteABk6j+PmsXknjZCiA12dr2zbacOB2gmZkhETa/qwEEyU
DpD8Zd1cS/ddWAJnvu6SV45ksa2HrTTsiVPrdE2zsIW0iIyIBSDg7LZHSBty
tYjMKT/CzTB3mA9khEIxtsLCssaa4EQHf43Vr7VxBkNBj0QflMlIIE6eOwn9
SFK6TC5H3rgOxpKNT2PiorEdnUHliALYe7HrVwiaWIrda00gjGYBVnuZtGbs
GxX7xC620pBGrqZxJphnMIUoiBh3+HqtQ3Lpl87tZJnEnQkDQ8PIQAcsY1dA
zNcM7eKqpQP/sO2fTg33Iw0eYHdu916aEtskbVK/gjXekSsiJYKj8oYBw470
BKNAIvlU9uRpS2N6moJ/FuylxOpid+hR51P3TtsgpW8aQjF2UvXWbI95MMkB
ye5D/wb9EGdsqop/1cFbw97C52mPGaWKmf2r0Dw4NK9Rfisqr47wsWVBVoXU
bKS5BcvL56vCF6PsJY5nRxzQ1yFFN1RRRnkQaki0y5MutQFugVGvBxT0Zdus
2TP3Op3Ca3y9GP9nbnzGiCGz8JiZBYNBjOP1sZEhk4RiwHQYpqk+HTJEcl+l
FBb/e21e1FS0WrUr8AAOxfcVTozNStrZUY8FRWOO4YE2BybzUXMpLDt7HYgZ
9q426Wfb+dFtvWa4dfj95QTsPx/Cq8AGjWD5lgn/zV4/E9D+4CDPNBwgteKn
bOgsdX68EIdvRuLxjKiQPJt6mbtHvMxz4ILrlWtbNXMPSyAZ/SiJ0kG8n7pC
diAxLwuAhx4j8WPkNUaz8z2WR6V5jhZotJT6fMILuExuS9NY3wIyAomYH77/
T0OkApEsqmiVGs3TQttYg2gLV+ehGlh5V4qtG60AXCmdJZLIFL1fs1eQUbW5
bGKvVWnbaq6JUenGYm/ctXMv57QzVV92hdQwMpgPTZUd7IHZbIJUUYLYX6Gk
CdFCLm1XJyxUBCR7itkEaH6rKVsWnKzXdjGdw0/4KRVRLXjjiDSvNhSfQ9tj
rGTT+uHPK8WV0YdU0R0XNdOIXSwCFbH/JbPtyFGGYhdifATwXfB2IiXSK4fB
i3T1gEDayuzhLT2psJFJ35UsciB7KWYkcAmw+Ifv/7S2VVHumaqW9FXwZkqp
rNLZly5OGmPqlNaKi47W4UEd90KPXHvofSJ0GZUdoMRM0DRbuyo6yanGQemt
goi5lksYE4Mutm50WUNTMpjFxYLbtQBNbV2dTBnxTLGeK76vY+5tRN61U0wD
oNKUhME+tgsSjeWxWT75O9iQOlMUFaegQGouSHkJMVG56mIIGmJEEbL8LaIi
fl+6FMK+6Be2bIipY9ulF9ji4HVC18bwjlZ3fb+GZBfaNA6bkCuj2fuc2gyZ
EZVuhCSO8+DEvTRx9X6rVaeYn+z2O0084+u+Vc8bMqHQg6HZuZeElccaQ0AL
Z5bnrtYegEmyQ4OD2q1F3Bty8UqLUkEQfaU4gBV3TfQZRklViv+OckMWOgsp
efwj2b5AeWrpSDFmEWpKEaqHmYOg2qEOIm35lGFPMdTu/NjOT7sEVkLvaiDZ
0E1LKXLUQDu0ngUSmQtsvPRK5Yw3RY3hoToCh9g0rDz87rv3b1STvMAhBbRW
qh+Us9QXWDqmXCQzoAyYLPs2DDUyCH9tGMX6xY+BqDjmCOIZ2f+/Q9gT0+fm
w6D/W/a8yaGoUN96P0g09tsQyp+86T8DGt07Ao0eR8f8mI08o0A1txJiSHsX
o3HsEjZbR2lJTm0EYZHR/jDdifaMuWoHywrgpF2kFbNImp6k6RTLblfiHYcI
QUAzCZpLej20+dPDw3B1tm+hPpEEJvjYMaY0D737PEJOIZ5nqP0xuK3ztily
vYqQQsRoyWkBKjpW37dusP2hjBj6aus8vdTGiicYVW9cSwgnVRaajcBLxkjC
X6nsY1g4a7ocrbO6WmEQGaEn4c3G7oNXLyRlzR7qkNWSwM+HEphcpBCoh9EX
VVVsQhD4j+YBLFNTefNwVMaCF5IVsE8GXl76/JRaPq5cF3PCvCahd0eE97RW
5RFfCnuEFWV1ThiOc9OEmwpKv9+6spNsvKTDmNyTTMoVrxiywVwz9HHBHOcj
PRahJMM4uE5oTkVDmmS089ZNzkNapXkIIpnxuGWAtJfzf0c7INWnCxtIgDh1
57SkpLijLBXXFHLIyeNEbaCJZmohAEa9ACquRY/fTTMvcbvhglcmNzWsvhCb
QKgj7jppZepECjVnzX6UoSY1FlyM0JfSVpoIrirdqCyhYzaNxqDqxLUDPa2t
uEJ2QAJoFY5gyFjGspJvYC21KQMWYCy88C/peSOsm8eMZsmUu9EvY6Yyo+np
rt04YzoUOwKwAsLuY4+nNKfCpDrpD2jdRrBPWEGuDUmnVd2NukIHc5M8OPft
Wm1Pl5JfCBHEXg35FMSIQNgL4DDgEVvKN0x5FLGhR1aEYjKfH++thPbQI8uK
y09JoDGqjZVH36++5S0yAbgSGg5XobiXWP1J1ZehsqT5BtXBoloh6Ksz5dJB
DY8HoBbFN8CeHZ+B9N4n8An/doWAZCigaKO4zt3sQgOiVysN3sQu/74W/Yn9
wWFvkwbUgwKtZLOlNJs5Pg9IJ91UEMs9QaLxbs8IiSpaj3Vi7DOUXbXs0ted
ZhxDeXEbKmd26iuuCsg/3lW4LIUdydcEijJe/83GBaPDtuu3oTBVuz8b1vz1
wZeo+98h7Aqv/DiuUg4Lonn/rbwvmBr1dl/BXox6h4T0WEmV+tXQZKy44fBe
K2I1iuLxy9ajCmisMy1GcfQ/051rcljKEKFgmId+BDvpP+tSQjJRHzxP8FwS
37M9KkTGvMoyqgDamCIO90ZtqTZPipKxrZBxEaVhqOUOt7aSfWK5XzsMYW53
TrQ/IIA0WG4Zr5xeGoCt0HqsOD/2sKsh4j0CF+LjqOrDTc/Di4uhtRB2qq+G
2wTaNP71cINYrg3rMV/eOFK9U/z2awWxTAlboWQuxtcdhu3FK39/EdUf3DAt
oHJ8nY7weXy3IFwLjGYzScm4pCq8HPXIMSuSk98JrIkthwAuRld7Ta3YNE01
muLWmLEI7NmcSPFh1dUeUBsFiZcWtAP6Rs1X12MLTuGVq4x8AX3aw4U49zA1
0ZGXqmWtYbcG1+pGLeFp2HDIpa2Ltrq2mnGQ8nXsDx0Twx5TQfCCfARvTy61
cPYWpiRchX33reoR8Xq8U7PMwy2H+3u78DT+IIOKJtAP7KXUItO9Whct9PxY
R+586Hh6V8PaQdV46FFieavMk1vVcFCJ/AULaJC4Zj1awI4qs6q6Q59Julge
NxmC64C+0x1loJR1x8OZau/44v9bNHj8swv8sRR/gAZTnLASO/WWW8IC2mQO
qa7Nj/XMBrNKGwb/XFptPgg9KLyuMNru0N8UtcGPIK9X4ZMnoV9uTLIkZ3WJ
yUWMgYCiXtMaBVsTLIJ2saX2rmO/uCDNHDfbvvY3bhUuzdculOzjnZHUkU2D
prIZf40g5bzGd+2L9PsF7V9k9bvJD3n4G7fH1NEMTU6i4Td/MGK0uXCn+2y3
W2jP09jTp8YYjcpxgqMMeOy3XBiFKRe8cVk7WQxRTM0fKrhoLm8NVp1jHzR1
rbAyY7JFnr2QG+2qYno2GVPD8VK9ZHqJ3Lm+yws78Q9jA5LES0KVI5YwGYuQ
X4h4jSYUwKNs9tHOUdFpNg/vzcp57AmFh+aYUVsmXvsWnmQFcRv5IvqTYDjV
wA9G4lZoP9OLfm76+x5vs5RPb5/xtqU51x8KOLwmeDZuA5LrxPGS32L6Kx+8
PPyOnw6hpdBYV3orYcWkhXQ9inTj/Q6Bfwc3AYVY/ioLpIhqsO7Lw188GK4E
8r13kCLafsobpReh73lKULh/5dQI53lLe3yzO4gX3uV9VU7x6gLxDkIbeTi9
AyoyyFbymXRAJ3dwxL7faHWQkHbkqHYxrJnHmynHLpMMLXVBeSc3xPmzMIvC
AzEv5Ns3b4To4QsI0qJZxy/fj+pRvaiU213v9q03iH9ru/LPvpcrSXOGVlrG
tcDfkiSJsbgAGKkzSC6Iyhp+ZMxuLF3uu8QttDyPFV9+v+bs6dkNbZv+7IFW
x3WklVDCh5/BYS6Sk5xlsa4uVwJn353qr7e5/F9O1rb07uQNJn12/gzvDxX4
2f8BzviQkY5OAAA=

-->

</rfc>
