Registration Data Access Protocol (RDAP) Object Tagging
draft-ietf-regext-rdap-object-tag-05

Document Type Active Internet-Draft (regext WG)
Last updated 2018-09-18 (latest revision 2018-08-03)
Replaces draft-hollenbeck-regext-rdap-object-tag
Stream IETF
Intended RFC status Best Current Practice
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication (wg milestone: Jun 2018 - Submit for publicati... )
Document shepherd James Gould
Shepherd write-up Show (last changed 2018-05-25)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Adam Roach
Send notices to James Gould <jgould@verisign.com>
IANA IANA review state Version Changed - Review Needed
IANA action state In Progress
RFC Editor RFC Editor state IANA
Registration Protocols Extensions                          S. Hollenbeck
Internet-Draft                                             Verisign Labs
Updates: 7484 (if approved)                                    A. Newton
Intended status: Best Current Practice                              ARIN
Expires: February 4, 2019                                 August 3, 2018

        Registration Data Access Protocol (RDAP) Object Tagging
                  draft-ietf-regext-rdap-object-tag-05

Abstract

   The Registration Data Access Protocol (RDAP) includes a method that
   can be used to identify the authoritative server for processing
   domain name, IP address, and autonomous system number queries.  The
   method does not describe how to identify the authoritative server for
   processing other RDAP query types, such as entity queries.  This
   limitation exists because the identifiers associated with these query
   types are typically unstructured.  This document updates RFC 7484 by
   describing an operational practice that can be used to add structure
   to RDAP identifiers that makes it possible to identify the
   authoritative server for additional RDAP queries.

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 February 4, 2019.

Copyright Notice

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

Hollenbeck & Newton     Expires February 4, 2019                [Page 1]
Internet-Draft             RDAP Object Tagging               August 2018

   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 Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Object Naming Practice  . . . . . . . . . . . . . . . . . . .   3
   3.  Bootstrap Service Registry for Provider Object Tags . . . . .   8
     3.1.  Registration Procedure  . . . . . . . . . . . . . . . . .   9
   4.  RDAP Conformance  . . . . . . . . . . . . . . . . . . . . . .  10
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
     5.1.  Bootstrap Service Registry Structure  . . . . . . . . . .  10
     5.2.  RDAP Extensions Registry  . . . . . . . . . . . . . . . .  10
   6.  Implementation Status . . . . . . . . . . . . . . . . . . . .  11
     6.1.  Verisign Labs . . . . . . . . . . . . . . . . . . . . . .  11
     6.2.  OpenRDAP  . . . . . . . . . . . . . . . . . . . . . . . .  11
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  12
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  13
   Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   The Registration Data Access Protocol (RDAP) includes a method
   ([RFC7484]) that can be used to identify the authoritative server for
   processing domain name, IP address, and autonomous system number
   (ASN) queries.  This method works because each of these data elements
   is structured in a way that facilitates automated parsing of the
   element and association of the data element with a particular RDAP
   service provider.  For example, domain names include labels (such as
   "com", "net", and "org") that are associated with specific service
   providers.

   As noted in Section 9 of RFC 7484 [RFC7484], the method does not
   describe how to identify the authoritative server for processing
   entity queries, name server queries, help queries, or queries using
   certain search patterns.  This limitation exists because the
   identifiers bound to these queries are typically not structured in a
Show full document text