HTTP usage in the Registration Data Access Protocol (RDAP)
draft-ietf-weirds-using-http-09

The information below is for an old version of the document
Document Type Active Internet-Draft (weirds WG)
Last updated 2014-08-07
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
Document shepherd Olaf Kolkman
Shepherd write-up Show (last changed 2013-05-29)
IESG IESG state AD is watching
Consensus Boilerplate Yes
Telechat date
Responsible AD Pete Resnick
IESG note Document Shepherd: Olaf Kolkman (olaf@NLnetLabs.nl)
Send notices to weirds-chairs@tools.ietf.org, draft-ietf-weirds-using-http@tools.ietf.org
IANA IANA review state Version Changed - Review Needed
Network Working Group                                          A. Newton
Internet-Draft                                                      ARIN
Intended status: Standards Track                             B. Ellacott
Expires: February 8, 2015                                          APNIC
                                                                 N. Kong
                                                                   CNNIC
                                                          August 7, 2014

       HTTP usage in the Registration Data Access Protocol (RDAP)
                    draft-ietf-weirds-using-http-09

Abstract

   This document is one of a collection that together describe the
   Registration Data Access Protocol (RDAP).  It describes how RDAP is
   transported using the Hypertext Transfer Protocol (HTTP).

Normative Reference Note

   Normative references to RFC 7231 and draft-ietf-httpbis-http2 can be
   replaced with a reference to RFC 2616 if draft-ietf-httpbis-http2 is
   still a work in progress when this document is ready for publication.

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 February 8, 2015.

Copyright Notice

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

Newton, et al.          Expires February 8, 2015                [Page 1]
Internet-Draft               RDAP over HTTP                  August 2014

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Design Intents  . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Queries . . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  Accept Header . . . . . . . . . . . . . . . . . . . . . .   5
     4.2.  Query Parameters  . . . . . . . . . . . . . . . . . . . .   5
   5.  Types of HTTP Response  . . . . . . . . . . . . . . . . . . .   5
     5.1.  Positive Answers  . . . . . . . . . . . . . . . . . . . .   5
     5.2.  Redirects . . . . . . . . . . . . . . . . . . . . . . . .   5
     5.3.  Negative Answers  . . . . . . . . . . . . . . . . . . . .   6
     5.4.  Malformed Queries . . . . . . . . . . . . . . . . . . . .   6
     5.5.  Rate Limits . . . . . . . . . . . . . . . . . . . . . . .   6
     5.6.  Cross-Origin Resource Sharing . . . . . . . . . . . . . .   7
   6.  Extensibility . . . . . . . . . . . . . . . . . . . . . . . .   7
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
     8.1.  RDAP Extensions Registry  . . . . . . . . . . . . . . . .   8
   9.  Internationalization Considerations . . . . . . . . . . . . .   9
     9.1.  URIs and IRIs . . . . . . . . . . . . . . . . . . . . . .   9
     9.2.  Language Identifiers in Queries and Responses . . . . . .   9
     9.3.  Language Identifiers in HTTP Headers  . . . . . . . . . .   9
   10. Contributing Authors and Acknowledgements . . . . . . . . . .   9
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     11.2.  Informative References . . . . . . . . . . . . . . . . .  10
   Appendix A.  Protocol Example . . . . . . . . . . . . . . . . . .  11
   Appendix B.  Cache Busting  . . . . . . . . . . . . . . . . . . .  11
   Appendix C.  Changelog  . . . . . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   This document describes the usage of HTT[RFC7231]P for Registration
   Data Directory Services.  The goal of this document is to tie
   together usage patterns of HTTP into a common profile applicable to
Show full document text