Protocol Action: 'Finding the Authoritative Registration Data (RDAP) Service' to Proposed Standard (draft-ietf-weirds-bootstrap-11.txt)

The IESG <> Thu, 01 January 2015 23:21 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id A2D671A8700; Thu, 1 Jan 2015 15:21:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id DlGuFdRgs2zI; Thu, 1 Jan 2015 15:21:23 -0800 (PST)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 68C741A8701; Thu, 1 Jan 2015 15:21:18 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Protocol Action: 'Finding the Authoritative Registration Data (RDAP) Service' to Proposed Standard (draft-ietf-weirds-bootstrap-11.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Thu, 01 Jan 2015 15:21:18 -0800
Cc: weirds chair <>, weirds mailing list <>, RFC Editor <>
X-Mailman-Version: 2.1.15
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 01 Jan 2015 23:21:26 -0000

The IESG has approved the following document:
- 'Finding the Authoritative Registration Data (RDAP) Service'
  (draft-ietf-weirds-bootstrap-11.txt) as Proposed Standard

This document is the product of the Web Extensible Internet Registration
Data Service Working Group.

The IESG contact persons are Pete Resnick and Barry Leiba.

A URL of this Internet Draft is:

Technical Summary

   This document specifies a method to find which Registration Data
   Access Protocol (RDAP) server is authoritative to answer queries for
   a requested scope, such as domain names, IP addresses or Autonomous
   System numbers.

Working Group Summary

   The WG spent a good deal of time working on the wording of the IANA
   section.  Attempts were made to clarify the specific data output
   requirements without providing instruction to IANA on update
   frequency, policy, etc., since this work has the unusual complication
   that the registry policies actually will mirror whatever rules ICANN
   puts in place for updating their name and number registries. IANA was
   consulted and (at last check) was satisfied with the proposed way

Document Quality

   The document appears to have the support of the WG, and there is at
   least one implementation in progress.


   The document shepherd is Michael Szucs. 
   Pete Resnick is the responsible Area Director.