Security Services for the Registration Data Access Protocol
draft-ietf-weirds-rdap-sec-01

The information below is for an old version of the document
Document Type Active Internet-Draft (weirds WG)
Last updated 2012-11-26
Replaces draft-hollenbeck-weirds-rdap-sec
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document (wg milestone: Sep 2014 - draft-ietf-weirds-rd... )
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                            S. Hollenbeck
Internet-Draft                                             Verisign Labs
Intended status: Standards Track                                 N. Kong
Expires: May 30, 2013                                              CNNIC
                                                       November 26, 2012

      Security Services for the Registration Data Access Protocol
                     draft-ietf-weirds-rdap-sec-01

Abstract

   The Registration Data Access Protocol (RDAP) provides "RESTful" web
   services to retrieve registration metadata from domain name and
   regional internet registries.  This document describes information
   security services, specific requirements for RDAP, and approaches to
   provide RDAP security services.

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 May 30, 2013.

Copyright Notice

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

Hollenbeck & Kong         Expires May 30, 2013                  [Page 1]
Internet-Draft           RDAP Security Services            November 2012

   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Conventions Used in This Document . . . . . . . . . . . . . . . 3
     2.1.  Acronyms and Abbreviations  . . . . . . . . . . . . . . . . 3
   3.  Information Security Services and RDAP  . . . . . . . . . . . . 3
     3.1.  Authentication  . . . . . . . . . . . . . . . . . . . . . . 3
       3.1.1.  Federated Authentication  . . . . . . . . . . . . . . . 4
     3.2.  Authorization . . . . . . . . . . . . . . . . . . . . . . . 5
     3.3.  Availability  . . . . . . . . . . . . . . . . . . . . . . . 6
     3.4.  Data Confidentiality  . . . . . . . . . . . . . . . . . . . 6
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 6
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 7
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 7
     7.1.  Normative References  . . . . . . . . . . . . . . . . . . . 7
     7.2.  Informative References  . . . . . . . . . . . . . . . . . . 8
   Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . . . 8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 8

Hollenbeck & Kong         Expires May 30, 2013                  [Page 2]
Internet-Draft           RDAP Security Services            November 2012

1.  Introduction

   The Registration Data Access Protocol (RDAP) core is specified in two
   documents: "Unified Registration Data Access Protocol Query Format"
   [I-D.ietf-weirds-rdap-query] and "JSON Responses for the Registry
   Data Access Protocol" [I-D.ietf-weirds-json-response].  One goal of
   RDAP is to provide security services that do not exist in the WHOIS
   [RFC3912] protocol, including authentication, authorization,
   availability, and data confidentiality.

   This document describes each of these security services from the
   perspective of RDAP requirements and applicability.  Where
   applicable, informational references to requirements for a WHOIS
   replacement service [RFC3707] are noted.

2.  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].

2.1.  Acronyms and Abbreviations

      DNR: Domain Name Registry

      RDAP: Registration Data Access Protocol

      RIR: Regional Internet Registry

3.  Information Security Services and RDAP

   RDAP itself does not include native security services.  Instead, RDAP
Show full document text