Requirements For Internet Registry Services
draft-kucherawy-weirds-requirements-02

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-01-31 (latest revision 2011-08-09)
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                       M. Kucherawy
Internet-Draft                                                 Cloudmark
Intended status: Informational                          January 31, 2012
Expires: August 3, 2012

              Requirements For Internet Registry Services
                 draft-kucherawy-weirds-requirements-02

Abstract

   This document enumerates a base set of requirements that should be
   included in any system that provides registration information for
   Internet network entities, i.e., network assignments.  Some of these,
   in turn, will define requirements for registrars; this, however, is
   an issue outside of the scope of this document.

   It is hoped that this work will influnce the development of
   requirements and specifications for domain name registries at some
   point in the future.

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 August 3, 2012.

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

Kucherawy                Expires August 3, 2012                 [Page 1]
Internet-Draft             WHOIS Requirements               January 2012

   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  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Terminology and Definitions . . . . . . . . . . . . . . . . . . 3
     2.1.  Keywords  . . . . . . . . . . . . . . . . . . . . . . . . . 3
     2.2.  Incorporated Requirements . . . . . . . . . . . . . . . . . 3
   3.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . . . 3
     3.1.  Clients . . . . . . . . . . . . . . . . . . . . . . . . . . 3
     3.2.  Servers . . . . . . . . . . . . . . . . . . . . . . . . . . 4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 6
   6.  Informative References  . . . . . . . . . . . . . . . . . . . . 6
   Appendix A.  Public Discussion  . . . . . . . . . . . . . . . . . . 6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 6

Kucherawy                Expires August 3, 2012                 [Page 2]
Internet-Draft             WHOIS Requirements               January 2012

1.  Introduction

   The ubiquitous [WHOIS] service can be used today to query for domain
   name registration or network or subnetwork assignment information by
   the general public.  It is however a very simple protocol, whose
   output is free-form and thus not amenable to machine parsing.

   The CRISP working group created a workable and extensible standard
   for replacing WHOIS, called [IRIS].  Unfortunately, IRIS has seen
   little to no deployment for various reasons, mostly its complexity
   compared to WHOIS and some political and technical inertia.

   Thus, this effort confronts anew the need for a better service than
   WHOIS provides, by first laying down a framework of requirements that
   such a service needs to accommodate to become a viable alternative to
   WHOIS.

2.  Terminology and Definitions

   This section defines terms used in the rest of the document.

2.1.  Keywords

   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 [KEYWORDS].  In
   particular, since this is not a standards track document, these key
   words are meant to describe requirements for those proposals for a
   WHOIS replacement that seek standards track status.

2.2.  Incorporated Requirements

   Many of the requirements distilled from the input provided by various
   communities in [CRISP] will apply to this effort as well.  It is
Show full document text