STD 95, RFC 9083 on JSON Responses for the Registration Data Access Protocol (RDAP)
rfc-editor@rfc-editor.org Wed, 16 June 2021 18:19 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0798B3A21BF; Wed, 16 Jun 2021 11:19:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 jRmmZ9vRCIPs; Wed, 16 Jun 2021 11:19:23 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 192EF3A220A; Wed, 16 Jun 2021 11:19:23 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 85DB2F407AE; Wed, 16 Jun 2021 11:18:41 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: STD 95, RFC 9083 on JSON Responses for the Registration Data Access Protocol (RDAP)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, regext@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210616181841.85DB2F407AE@rfc-editor.org>
Date: Wed, 16 Jun 2021 11:18:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/n3aCklisU0WlRhlZ5qHDRu1MKqM>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Jun 2021 18:19:37 -0000
A new Request for Comments is now available in online RFC libraries. STD 95 RFC 9083 Title: JSON Responses for the Registration Data Access Protocol (RDAP) Author: S. Hollenbeck, A. Newton Status: Standards Track Stream: IETF Date: June 2021 Mailbox: shollenbeck@verisign.com, andy@hxr.us Pages: 81 Obsoletes: RFC 7483 See Also: STD 95 I-D Tag: draft-ietf-regext-rfc7483bis-05.txt URL: https://www.rfc-editor.org/info/rfc9083 DOI: 10.17487/RFC9083 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 obsoletes RFC 7483. This document is a product of the Registration Protocols Extensions Working Group of the IETF. This is now an Internet 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/retrieve/bulk 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