<?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.6.26 (Ruby 3.0.2) -->
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<?rfc rfcedstyle="yes"?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-mandyam-rats-proxlocclaim-00" category="info" tocDepth="4" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.16.0 -->
  <front>
    <title>The Proximate Location Claim</title>
    <seriesInfo name="Internet-Draft" value="draft-mandyam-rats-proxlocclaim-00"/>
    <author initials="G." surname="Mandyam" fullname="Giridhar Mandyam">
      <organization>Qualcomm Technologies Inc.</organization>
      <address>
        <postal>
          <street>5775 Morehouse Drive</street>
          <city>San Diego</city>
          <region>California</region>
          <country>USA</country>
        </postal>
        <phone>+1 858 651 7200</phone>
        <email>mandyam@qti.qualcomm.com</email>
      </address>
    </author>
    <date year="2023" month="March" day="13"/>
    <area>Internet</area>
    <workgroup>RATS Working Group</workgroup>
    <keyword>signing attestation cbor location</keyword>
    <abstract>
      <t>The Entity Attestation Token (EAT) is an extensible attestation version of a CBOR Web Token (CWT).
EAT defines a location claim, but does not define a proximate location claim.  This document proposes a claim
in which an attester can relay detected relative location of a target.</t>
    </abstract>
  </front>
  <middle>
    <section anchor="introduction">
      <name>Introduction</name>
      <t>The Entity Attestation Token i.e. EAT <xref target="EAT.Draft"/> provides a method for sending attesation-related
data in the form of a CBOR Web Token (CWT)  <xref target="RFC8392"/>.  Attested location is claim provided in the
EAT specification wherein an attester can provide location data in the form of a standard geodetic
coding system (WGS 84).</t>
      <t>Secure ranging involves the process of determining the relative location of a device (entity) with respect to
a receiver.  In this case, the receiver may actually attest to the location of the device in a similar manner to
how the Entity Attestation Token conveys location data.  However, there are majore differences between the EAT convveyance of location
and a secure ranging receiver:  (1) the EAT location is that of the entity to which the attester created the token, while the secure ranging
receiver is conveying the detected location of the entity, and (2) the receiver is providing the relative location of the entity.</t>
      <t>In this document, a new claim - the proximate location claim - is specified that will distinguish location determined via secure ranging
from location conveyed by as part of a entity's attestation evidence.  Although this claim could appear in a CWT for non-attestation scenarios,
it can be conveyed as part of a delegated attestation (i.e. the secure ranging receiver attests to the location on behalf of the target entity).  A sample
architecture is provided in <xref target="reader-attest"/>.  The secure ranging receiver in this case makes an angle-of-arrival (AoA) and distance determination based upon
a transmitted signal from a target device.  The receiver (assuming it can determine its own location) can project these measurements to a geodetic coordinate
system and attest to it.</t>
      <figure anchor="reader-attest">
        <name>Secure Ranging and Attestation</name>
        <artwork align="center"><![CDATA[
+-------------+
|             |
|    Target   |
|             |
+-------------+
       |
       |
       |
+-------------------------------+
|      |           Ranging Rcvr.|
|   +-----+                     |
|   | AoA/|                     |
|   |Dist.|                     |
|   +-----+                     |
|      |                        |
|   +-----+                     |
|   |Geod.|                     |
|   |Conv.|                     |
|   +-----+                     |
|      |                        |
|   +--------+                  |
|   |Attester|                  |
|   +--------+                  |
|        |                      |
+-------------------------------+
         |
    +--------+
    |Verifier|
    +--------+
]]></artwork>
      </figure>
    </section>
    <section anchor="proxloc">
      <name>The Proximate Location Claim (proxloc)</name>
      <t>The proximate location claim provides the location of a target entity based on what
a secure ranging receiver derives.  If the secure ranging receiver is capable
of determining its own location, then it can project the entity's location
to an appropriate geodetic coordinate system based on the relative location
of the entity.
It is partially derived derived from the EAT location claim <xref target="EAT.Draft"/>, but includes
the ueid claim to uniquely identify the entity.</t>
      <t>If the location cannot be derived as per the EAT specification, then the relative
angle-of-arrival, angle-of-elevation, and ranging distance may be sent (the angular 
measurements in radians and the distance in meters).</t>
      <sourcecode type="CDDL"><![CDATA[
proxloc-label => proxloc-type

proxloc-type = {
    target-ueid => ueid, ; derived from EAT claim ueid
    ? target-location => location ; derived from EAT claim location if WGS-84 coordinate projection possible
    ? aoa => float ; angle-of-arrival optionally sent
    ? distance => float ; ranging distance optionally sent
    ? aoe =? float ; angle-of-elevation optionally sent
}
]]></sourcecode>
      <t>Note that this claim may be extended in the future for other coordinate systems.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>This document requests registration of the following claim in the "CBOR Web Token (CWT) Claims Registry" (http://www.iana.org/assignments/cwt).</t>
      <t> </t>
      <ul spacing="normal">
        <li>Claim Name: proxloc</li>
        <li>Claim Description: The Proximate Location Claim</li>
        <li>JWT Claim Name: "proxloc"</li>
        <li>CWT Claim Key: TBD</li>
        <li>Claim Value Type(s): map</li>
        <li>Change Controller: IESG</li>
        <li>Specification Document(s): <strong>this document</strong></li>
      </ul>
    </section>
  </middle>
  <back>
    <references>
      <name>Normative References</name>
      <reference anchor="RFC8392">
        <front>
          <title>CBOR Web Token (CWT)</title>
          <author fullname="M. Jones" initials="M." surname="Jones">
            <organization/>
          </author>
          <author fullname="E. Wahlstroem" initials="E." surname="Wahlstroem">
            <organization/>
          </author>
          <author fullname="S. Erdtman" initials="S." surname="Erdtman">
            <organization/>
          </author>
          <author fullname="H. Tschofenig" initials="H." surname="Tschofenig">
            <organization/>
          </author>
          <date month="May" year="2018"/>
          <abstract>
            <t>CBOR Web Token (CWT) is a compact means of representing claims to be transferred between two parties.  The claims in a CWT are encoded in the Concise Binary Object Representation (CBOR), and CBOR Object Signing and Encryption (COSE) is used for added application-layer security protection.  A claim is a piece of information asserted about a subject and is represented as a name/value pair consisting of a claim name and a claim value.  CWT is derived from JSON Web Token (JWT) but uses CBOR rather than JSON.</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="8392"/>
        <seriesInfo name="DOI" value="10.17487/RFC8392"/>
      </reference>
      <reference anchor="EAT.Draft">
        <front>
          <title>The Entity Attestation Token (EAT)</title>
          <author fullname="Laurence Lundblade" initials="L." surname="Lundblade">
            <organization>Security Theory LLC</organization>
          </author>
          <author fullname="Giridhar Mandyam" initials="G." surname="Mandyam">
            <organization>Qualcomm Technologies Inc.</organization>
          </author>
          <author fullname="Jeremy O'Donoghue" initials="J." surname="O'Donoghue">
            <organization>Qualcomm Technologies Inc.</organization>
          </author>
          <author fullname="Carl Wallace" initials="C." surname="Wallace">
            <organization>Red Hound Software, Inc.</organization>
          </author>
          <date day="19" month="December" year="2022"/>
          <abstract>
            <t>   An Entity Attestation Token (EAT) provides an attested claims set
   that describes state and characteristics of an entity, a device like
   a smartphone, IoT device, network equipment or such.  This claims set
   is used by a relying party, server or service to determine how much
   it wishes to trust the entity.

   An EAT is either a CBOR Web Token (CWT) or JSON Web Token (JWT) with
   attestation-oriented claims.

            </t>
          </abstract>
        </front>
        <seriesInfo name="Internet-Draft" value="draft-ietf-rats-eat-19"/>
      </reference>
    </references>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA71YUXPbuBF+54z+w44z00gXU7Gd5OIok159Vs7n9i5tbffy
6IFIUMKFJBQAtE5ju7+934IgRVqym+lD+WCLwGKx++3i2wXjOB5E1okyvRa5
LuWEnKnkIFJL439ad3Rw8O7gaBAlwk1IlZkeRIMo1UkpCkinRmQuLrB+LYrY
CGfjpdF/5DpJcqGK+OCAxVfzCV2cXF3SZ22+qHJOZ0ZXy0H0jBJdWlnayk7o
+Vra5zxmq1mhrFW6dOsl9jj/ePXTIFqqySAicjppRf1bKpdugaHXfsBq44zM
bEfGrosHI4kuliJxXZlqthkstR8zWSJT69a5bAWdcvx2tZD0D3ipCuEk/aIB
DYylU/Z4EAkjBYwunTSldIPoy2pCVs1L9ls4J4G2F09m2lAeFrPfKbRN6Ojg
8FV8CNhE5RbawOkYsMP8szH9WuPM1tXwnymj0oUw3RltgPY/K5HDo4KuZLIo
da7nSloYlYy9u8BIwtU3b9++oV+1kQtdWUlTo26kB0i59YQuRUlTJefaoyHn
MHNCpyJXmTalEjWSVekMZP91ecLvy4XPob0Xh3T85pi+f3NIb5FAezwnC6Hy
CYVc+ctXp8Zfg5Vj/OE8KbUBpDDCh7p+Ln46PX717qgz8vHkajzlvJsQncfT
sZIuq1NPCsdqzpGlOxW9e/Xq9YQlAGock5gBCMSc3zmmH0sEeE0nnSBd6S+y
pCG2HJGyBETkHw4Jq2a57EXzRhrOWNIZCTr98e8X9FnOmuWnn69GAB5aKJWZ
KhEK0Yae/EnZp1nlKNWYKrULYpBatnnWlx8T0hAW4SRWhSwdCy619ZqTOhFV
SauFShZsdW2qNJTgxchcrLGFk4mTqX9lrDY7eCecMHPpxhu4CpWmueS3Z5ze
RqdVUufuf4FPjeWYo0a3t23s7u/Z4huVeosLiVxPCWEj0EHaHhWvJfYGyhS0
I5zAYSCH3TjEj6NN2Ctkzv09sKqNgrOtj8DO49SYkQbFdZjsUiYqU0F2tZBG
YvohkGHpRuluAz2/CpPSXGqgrhKwqfZO2jV0FTT8fHZJx69HMJTBvJRJZSQZ
Uc5ZSJU3Or8BTqwVWybSWlbMATSF8sTCU4/EMZU3KpE0lD48I1opt4Ase+hA
oCAavCUSCw32P2fjGRth5X5QW0/i5K4JpwVnNl8HHLDey3R35PewJ0MG7itU
Lnh5WUIL77jQKy/2aMagLNzIte0DC+t+1isJU7xhQAhUC7W/g8AoVVmGoRLg
0Ey6lZR1FDiYrA3qBCbZwA3nIixsYB/uxl+wy/Bw1CrpJo5bCNe4WsPKQNSH
jcc2SYJawFnHg44922cpUAcP9PcdRC3QDL8HoIlse1Qf4lxvvk/syPBo1I8X
1NQJ+mSCbNSMa+6s49/wCnRTKVfhrMRNDu7kJExjZTg63mvAtFJ5juhYBysq
ZRedmIb8heSNehiGQZQZXXQ28IBAdIbcg2PCuDq9a9uf2x4bSz6WCDef/BzU
Us0XIa29nShbOSK/XErkpU9ScIZnnxJ001VkE1kKo7TdB586f+hncmNMz5JU
5nLuw93VMPTstx3vTZxqabt9lnivhcizJkw1IwePmSxOyIpiyZwsTLJQnCS8
Qxv4mtRub5GFqTTBMc+HV0/YozoUgOP1Rfq6B6lcxjqLhUGbIHIanuiTkc88
jq4/XE1Ea/tnWJ9StfQnDc2kKG2hHOPD7RA0+Ag3hSZwRrCtNWYorK0KT4M1
/G3WYAA0uCpbwEYNJ//umW0h2XwpLJzkTPYAi5aDEURtUrYV8AUe9nzQEpuq
i9+/8YCWX8Td58UguqPucxcGrmpnNgNdiS0dm6ldv/ri28/GiO5OFyGeF8mN
GQcrak0vaNcTRO4I8Xx596TIFIEePynyDRs9MPd/1HJ3hjg+bcvdKY7p/8/c
3YoaW0IDYnbo+nYtT1nzbfnSFafepvX73W/SMHmbHfN8EAbR7YSe9fgEVdit
cK+LcTOYlx/2wJjwc4/8ZenDXmhmmqzkI9ap93v3dT/51JWKhuFKOaLbZ+Hn
fdN0PlqL2u7yYX8i+jwaaMp3eXx9eLQfAPPw/chyk5Q9SeieO5dixsT8oE97
yFm+kykbbutw16aubdoV5q+SyxZafaPY5x1k1vSUrVs7K783rFf6z52vGwim
8g1e7W3a/vdkvdUM1Vj3+vr6JqPKJK8AP6zGmkqqNMjCiapUXyuJPbhIO5Wt
t5qQrB81YMOXoplsreHCy81ksKfXrgdMu35zq9cvX/ubgoayfRMWcnY24Wyr
Gve9M442bllD396hk+GOdhD1ygvqphGpQpnzenzj1ujAXMFpYEdtTTmdTn8Z
RCGf41zMZE4f/kzNAH/7iKLuG32gW38o6/yNPahYwf/36X0/Ur7v9YDztF/2
Q7OwxRWL29+Prt80vhnhnhIfv+5mW0hZnsf109+Lw2ZCC94gyzW6wPfb/YNe
8iqfawxtWNUi1lm6FZHdS4XGqh+2N2zju7XuviG1QfRJO1k3rJ0+MUTeX/k3
N0TKKt9mcb+o+SKyffrsOFyTTz6dEMqQRaYbb4Otiat7czcSp4EbQP7Gwl8k
uq15pvNcr9j72qRgwt7OS6+nS0sXtZ71Hg0Xzi0nL1+uVqsxElOMtZm/REcF
ovY5+zJZuToj/1TO7PJ9FH0XOPeT/74U0q8dnUqbGOVRfPozGFb8FS11V9de
ULbH2tq5v8k1NP04bbf4TeSVpCvk+9CO+HPRkqcWiKZkJJ0BIHw5O/94eYaZ
y95FfRow9Uuvr3s3mevrQfQfneNbM+8UAAA=

-->

</rfc>
