The Proximate Location Claim
draft-mandyam-rats-proxlocclaim-01
| Document | Type | Active Internet-Draft (individual) | |
|---|---|---|---|
| Author | Giridhar Mandyam | ||
| Last updated | 2024-01-17 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-mandyam-rats-proxlocclaim-01
RATS Working Group G. Mandyam
Internet-Draft 17 January 2024
Intended status: Informational
Expires: 20 July 2024
The Proximate Location Claim
draft-mandyam-rats-proxlocclaim-01
Abstract
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.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 20 July 2024.
Copyright Notice
Copyright (c) 2024 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components
extracted from this document must include Revised BSD License text as
described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Revised BSD License.
Mandyam Expires 20 July 2024 [Page 1]
Internet-Draft The Proximate Location Claim January 2024
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. The Proximate Location Claim (proxloc) . . . . . . . . . . . 3
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
4. Normative References . . . . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction
The Entity Attestation Token i.e. EAT [EAT.Draft] provides a method
for sending attesation-related data in the form of a CBOR Web Token
(CWT) [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).
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.
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 Figure 1. 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.
Mandyam Expires 20 July 2024 [Page 2]
Internet-Draft The Proximate Location Claim January 2024
+-------------+
| |
| Target |
| |
+-------------+
|
|
|
+-------------------------------+
| | Ranging Rcvr.|
| +-----+ |
| | AoA/| |
| |Dist.| |
| +-----+ |
| | |
| +-----+ |
| |Geod.| |
| |Conv.| |
| +-----+ |
| | |
| +--------+ |
| |Attester| |
| +--------+ |
| | |
+-------------------------------+
|
+--------+
|Verifier|
+--------+
Figure 1: Secure Ranging and Attestation
2. The Proximate Location Claim (proxloc)
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 [EAT.Draft],
but includes the ueid claim to uniquely identify the entity.
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).
Mandyam Expires 20 July 2024 [Page 3]
Internet-Draft The Proximate Location Claim January 2024
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
}
Note that this claim may be extended in the future for other
coordinate systems.
3. IANA Considerations
This document requests registration of the following claim in the
"CBOR Web Token (CWT) Claims Registry"
(http://www.iana.org/assignments/cwt).
* Claim Name: proxloc
* Claim Description: The Proximate Location Claim
* JWT Claim Name: "proxloc"
* CWT Claim Key: TBD
* Claim Value Type(s): map
* Change Controller: IESG
* Specification Document(s): *this document*
4. Normative References
[EAT.Draft]
Lundblade, L., Mandyam, G., O'Donoghue, J., and C.
Wallace, "The Entity Attestation Token (EAT)", Work in
Progress, Internet-Draft, draft-ietf-rats-eat-25, 15
January 2024, <https://datatracker.ietf.org/doc/html/
draft-ietf-rats-eat-25>.
[RFC8392] Jones, M., Wahlstroem, E., Erdtman, S., and H. Tschofenig,
"CBOR Web Token (CWT)", RFC 8392, DOI 10.17487/RFC8392,
May 2018, <https://www.rfc-editor.org/rfc/rfc8392>.
Mandyam Expires 20 July 2024 [Page 4]
Internet-Draft The Proximate Location Claim January 2024
Author's Address
Giridhar Mandyam
Email: giridhar.mandyam@gmail.com
Mandyam Expires 20 July 2024 [Page 5]