DRIP Entity Tag (DET) Differentiated Access using RDAP
draft-wiethuechter-drip-det-diff-access-rdap-00

drip Working Group                                       A. Wiethuechter
Internet-Draft                                        AX Enterprize, LLC
Intended status: Standards Track                       27 September 2024
Expires: 31 March 2025

         DRIP Entity Tag (DET) Differentiated Access using RDAP
            draft-wiethuechter-drip-det-diff-access-rdap-00

Abstract

   This document defines an RDAP profile and extension data model for
   UAS registration.  It also gives recommendations for AAA mechanisms.

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 31 March 2025.

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.

Wiethuechter              Expires 31 March 2025                 [Page 1]
Internet-Draft            det-rdap-diff-access            September 2024

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  URI Specification . . . . . . . . . . . . . . . . . . . . . .   2
   4.  Conformance Literal . . . . . . . . . . . . . . . . . . . . .   2
   5.  Extension Model . . . . . . . . . . . . . . . . . . . . . . .   3
   6.  Access Control Mechanisms . . . . . . . . . . . . . . . . . .   4
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
     7.1.  RDAP Extensions Registry  . . . . . . . . . . . . . . . .   4
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   For DRIP private information is accessed via the lookup of the DRIP
   Entity Tag (DET) [RFC9374] in DNS [DET-DNS] and following a URI.
   This URI per [RFC9153] REG-2 MUST have the data behind it access
   controlled.

   It should be noted that full compliance with RDAP is not required but
   RECOMMENDED.  Where possible DRIP reuses RDAP query methods and
   reuses or extends response models.

   This document only specifies the minimum data models for response of
   UAS information associated to a DET.  Other elements that MAY be
   required by policy are out of scope for this document.

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

3.  URI Specification

   The URIs to Private Information resources SHOULD follow those defined
   in [RFC9082].  For DRIP the /domain query format MUST be support for
   DETs.

4.  Conformance Literal

   The string literal drip_version_0 MUST be used in the rdapConformance
   section to signal conformance with this specification.

Wiethuechter              Expires 31 March 2025                 [Page 2]
Internet-Draft            det-rdap-diff-access            September 2024

5.  Extension Model

   The data model for responses SHOULD follow the RDAP specification for
   results in [RFC9083].  For DRIP the additional data member is used to
   hold non-DNS based registration information.  The following CDDL is
   the response model under the RDAP key of drip.

drip = {
  serial_number: tstr .size(5..20),
  csr: bstr,
  x509: [+ bstr / #6.TBD],
  ? caa_assigned_id: tstr,
  ? f3411: {
    ? uas_type: nibble-field,
    ? uas_ids: uas-id-map,
    ? auths: [* auth-grp],
    ? self-grp,
    ? area-grp,
    ? classification-grp,
    ? operator-grp,
  }
  ? utm: {
      operational_intent: #6.37(bstr),
      uss_uri: #6.32(tstr) / tstr
  },
  * tstr => any
}
uas-id-map = {
    &uas-id-types: [+ uas-id]
}
uas-id-types = (none: 0, serial: 1, caa_id: 2, utm_id: 3, session_id: 4)
uas-id: tstr .size(1..20) / bstr .size(1..20)
auth-grp = (
    a_type: nibble-field,
    a_data: bstr .size(1..362)
)
area-grp = (
    area_count: 1..255,
    area_radius: float,
    area_floor: float,
    area_ceiling: float
)
classification-grp = (
    ua_class: 0..8,
    eu_class: nibble-field,
    eu_category: nibble-field
)
self-grp = (

Wiethuechter              Expires 31 March 2025                 [Page 3]
Internet-Draft            det-rdap-diff-access            September 2024

    desc_type: nibble-field,
    description: tstr .size(23)
)
operator-grp = (
    operator_id_type: nibble-field,
    operator_id: bstr .size(20)
)
nibble-field = 0..15

6.  Access Control Mechanisms

   TBD

7.  IANA Considerations

7.1.  RDAP Extensions Registry

   This specification registers drip_version_0 extension.

  Extension Identifier: drip_version_0
  Registry Operator: Any
  Specification: This RFC
  Contact: IETF DRIP WG <tm-rid@ietf.org>
  Intended Usage: This extension identifies additional data elements for
                  DRIP registrations in UAS RID.

8.  References

8.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <https://www.rfc-editor.org/info/rfc2119>.

   [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
              2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
              May 2017, <https://www.rfc-editor.org/info/rfc8174>.

   [RFC9082]  Hollenbeck, S. and A. Newton, "Registration Data Access
              Protocol (RDAP) Query Format", STD 95, RFC 9082,
              DOI 10.17487/RFC9082, June 2021,
              <https://www.rfc-editor.org/info/rfc9082>.

   [RFC9083]  Hollenbeck, S. and A. Newton, "JSON Responses for the
              Registration Data Access Protocol (RDAP)", STD 95,
              RFC 9083, DOI 10.17487/RFC9083, June 2021,
              <https://www.rfc-editor.org/info/rfc9083>.

Wiethuechter              Expires 31 March 2025                 [Page 4]
Internet-Draft            det-rdap-diff-access            September 2024

8.2.  Informative References

   [DET-DNS]  Wiethuechter, A. and J. Reid, "DRIP Entity Tags (DET) in
              the Domain Name System (DNS)", Work in Progress, Internet-
              Draft, draft-ietf-drip-registries-18, 27 September 2024,
              <https://datatracker.ietf.org/doc/html/draft-ietf-drip-
              registries-18>.

   [RFC8126]  Cotton, M., Leiba, B., and T. Narten, "Guidelines for
              Writing an IANA Considerations Section in RFCs", BCP 26,
              RFC 8126, DOI 10.17487/RFC8126, June 2017,
              <https://www.rfc-editor.org/info/rfc8126>.

   [RFC9153]  Card, S., Ed., Wiethuechter, A., Moskowitz, R., and A.
              Gurtov, "Drone Remote Identification Protocol (DRIP)
              Requirements and Terminology", RFC 9153,
              DOI 10.17487/RFC9153, February 2022,
              <https://www.rfc-editor.org/info/rfc9153>.

   [RFC9374]  Moskowitz, R., Card, S., Wiethuechter, A., and A. Gurtov,
              "DRIP Entity Tag (DET) for Unmanned Aircraft System Remote
              ID (UAS RID)", RFC 9374, DOI 10.17487/RFC9374, March 2023,
              <https://www.rfc-editor.org/info/rfc9374>.

   [RFC9434]  Card, S., Wiethuechter, A., Moskowitz, R., Zhao, S., Ed.,
              and A. Gurtov, "Drone Remote Identification Protocol
              (DRIP) Architecture", RFC 9434, DOI 10.17487/RFC9434, July
              2023, <https://www.rfc-editor.org/info/rfc9434>.

   [RFC9575]  Wiethuechter, A., Ed., Card, S., and R. Moskowitz, "DRIP
              Entity Tag (DET) Authentication Formats and Protocols for
              Broadcast Remote Identification (RID)", RFC 9575,
              DOI 10.17487/RFC9575, June 2024,
              <https://www.rfc-editor.org/info/rfc9575>.

Author's Address

   Adam Wiethuechter
   AX Enterprize, LLC
   4947 Commercial Drive
   Yorkville, NY 13495
   United States of America
   Email: adam.wiethuechter@axenterprize.com

Wiethuechter              Expires 31 March 2025                 [Page 5]