[weirds] RFC 7483 on JSON Responses for the Registration Data Access Protocol (RDAP)

rfc-editor@rfc-editor.org Wed, 25 March 2015 20:53 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EBFD1B2BA9; Wed, 25 Mar 2015 13:53:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ddw772RX6A2f; Wed, 25 Mar 2015 13:53:48 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 07DDD1B2BCE; Wed, 25 Mar 2015 13:53:46 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 2E439180473; Wed, 25 Mar 2015 13:52:14 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150325205214.2E439180473@rfc-editor.org>
Date: Wed, 25 Mar 2015 13:52:14 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/weirds/NtwcYcgvAkJWJSgmzljaKYcWLtM>
Cc: drafts-update-ref@iana.org, weirds@ietf.org, rfc-editor@rfc-editor.org
Subject: [weirds] RFC 7483 on JSON Responses for the Registration Data Access Protocol (RDAP)
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds/>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Mar 2015 20:53:52 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7483

        Title:      JSON Responses for the Registration 
                    Data Access Protocol (RDAP) 
        Author:     A. Newton, S. Hollenbeck
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2015
        Mailbox:    andy@arin.net, 
                    shollenbeck@verisign.com
        Pages:      78
        Characters: 125362
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-weirds-json-response-14.txt

        URL:        https://www.rfc-editor.org/info/rfc7483

This document describes JSON data structures representing
registration information maintained by Regional Internet Registries
(RIRs) and Domain Name Registries (DNRs).  These data structures are
used to form Registration Data Access Protocol (RDAP) query
responses.

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

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC