Using the Registration Data Access Protocol (RDAP) with HTTP
draft-ietf-weirds-using-http-03
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (weirds WG)
|
|
Last updated |
|
2013-03-27
|
|
Replaces |
|
draft-designteam-weirds-using-http
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
pdf
htmlized
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
Waiting for WG Chair Go-Ahead
Revised I-D Needed - Issue raised by WGLC, Doc Shepherd Follow-up Underway
|
|
Document shepherd |
|
Olaf Kolkman
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group A.L. Newton
Internet-Draft ARIN
Intended status: Standards Track B.J. Ellacott
Expires: September 28, 2013 APNIC
N. Kong
CNNIC
March 27, 2013
Using the Registration Data Access Protocol (RDAP) with HTTP
draft-ietf-weirds-using-http-03
Abstract
This document describes the usage of the Registration Data Access
Protocol (RDAP) using HTTP.
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 28, 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, et al. Expires September 28, 2013 [Page 1]
Internet-Draft RDAP over HTTP March 2013
1. Introduction
This document describes the usage of HTTP for Registration Data
Directory Services running on RESTful web servers. The goal of this
document is to tie together the usage patterns of HTTP into a common
profile applicable to the various types of Directory Services serving
Registration Data using RESTful styling. By giving the various
Directory Services common behavior, a single client is better able to
retrieve data from Directory Services adhering to this behavior.
In designing these common usage patterns, this draft endeavours to
satisfy requirements for a Registration Data Access Protocol (RDAP).
This draft also introduces an additional design consideration to
define a simple use of HTTP. Where complexity may reside, it is the
goal of this specification to place it upon the server and to keep
the client as simple as possible. A client implementation should be
possible using common operating system scripting tools.
This is the basic usage pattern for this protocol:
1. A client issues an HTTP query using GET. As an example, a query
for the network registration 192.0.2.0 might be http://
example.com/ip/192.0.2.0.
2. If the receiving server has the information for the query, it
examines the Accept header field of the query and returns a 200
response with a response entity appropriate for the requested
format.
3. If the receiving server does not have the information for the
query but does have knowledge of where the information can be
found, it will return a redirection response (3xx) with the
Location: header containing an HTTP URL pointing to the
information or another server known to have knowledge of the
location of the information. The client is expected to re-query
using that HTTP URL.
4. If the receiving server does not have the information being
requested and does not have knowledge of where the information
can be found, it should return a 404 response.
It is important to note that it is not the intent of this document to
redefine the meaning and semantics of HTTP. The purpose of this
document is to clarify the use of standard HTTP mechanisms for this
application.
2. Terminology
Newton, et al. Expires September 28, 2013 [Page 2]
Internet-Draft RDAP over HTTP March 2013
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].
Show full document text