Registration Data Access Protocol Lookup Format
draft-ietf-weirds-rdap-query-03
Network Working Group A.L. Newton
Internet-Draft ARIN
Intended status: Standards Track S. Hollenbeck
Expires: September 15, 2013 Verisign Labs
March 14, 2013
Registration Data Access Protocol Lookup Format
draft-ietf-weirds-rdap-query-03
Abstract
This document describes uniform patterns to construct HTTP URLs that
may be used to retrieve registration information from registries
(including both Regional Internet Registries (RIRs) and Domain Name
Registries (DNRs)) using "RESTful" web access patterns.
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 http://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 September 15, 2013.
Copyright Notice
Copyright (c) 2013 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
(http://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 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.
Newton & Hollenbeck Expires September 15, 2013 [Page 1]
Internet-Draft RDAP Query Format March 2013
Table of Contents
1. Conventions Used in This Document . . . . . . . . . . . . . . 2
1.1. Acronyms and Abbreviations . . . . . . . . . . . . . . . 2
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Path Segment Specification . . . . . . . . . . . . . . . . . 4
3.1. IP Network Path Segment Specification . . . . . . . . . . 4
3.2. Autonomous System Path Segment Specification . . . . . . 5
3.3. Domain Path Segment Specification . . . . . . . . . . . . 6
3.4. Name Server Path Segment Specification . . . . . . . . . 6
3.5. Entity Path Segment Specification . . . . . . . . . . . . 7
4. Extensibility . . . . . . . . . . . . . . . . . . . . . . . . 7
5. Internationalization Considerations . . . . . . . . . . . . . 7
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
7. Security Considerations . . . . . . . . . . . . . . . . . . . 8
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
9.1. Normative References . . . . . . . . . . . . . . . . . . 8
9.2. Informative References . . . . . . . . . . . . . . . . . 10
Appendix A. Path Segment Specification for Search Queries . . . 10
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Conventions Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
1.1. Acronyms and Abbreviations
IDN: Internationalized Domain Name
IDNA: Internationalized Domain Names in Applications
DNR: Domain Name Registry
RDAP: Registration Data Access Protocol
REST: Representational State Transfer State Transfer. The term
was first described in a doctoral dissertation [REST].
RESTful: an adjective that describes a service using HTTP and the
principles of REST.
RIR: Regional Internet Registry
2. Introduction
This document describes a specification for querying registration
data using a RESTful web service and uniform query patterns. The
service is implemented using the Hypertext Transfer Protocol (HTTP)
[RFC2616].
Newton & Hollenbeck Expires September 15, 2013 [Page 2]
Internet-Draft RDAP Query Format March 2013
The protocol described in this specification is intended to address
Show full document text