DRIP Entity Tag (DET) Differentiated Access using RDAP

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.¶

Table of Contents

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.¶

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 = (
    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

Extension Identifier: drip_version_0
Registry Operator: Any
Specification: This RFC
Contact: IETF DRIP WG <[email protected]>
Intended Usage: This extension identifies additional data elements for
                DRIP registrations in UAS RID.

Author's Address