DRIP Information Agent (DIA) RDAP Interface

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

Copyright Notice

Copyright (c) 2022 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

The DIA is one of the required components in a DIME for it to fulfill the role of lookup of additional information around DRIP Entity Tags (DETs). A standardized interface is needed for this to avoid interoperability issues between vendors supporting DRIP and the various logical components of the DIME.¶

Per [drip-detim] the DIA MUST use:¶

• Registration Data Access Protocol (RDAP) ([RFC7480], [RFC9082] and [RFC9083]) as the selected protocol to provide policy driven differentiated access for queries of information.¶

This document is the definition of this interface and its behavior; specifically between the DIA and client looking up information using the DET as a key. A snapshot of the OpenAPI specification is in Appendix A at the time of this documents publishing; with a URI to access an updated specification.¶

2. Terminology

Appendix A. OpenAPI Specification

TODO¶

Authors' Addresses