[regext] BCP 221, RFC 8521 on Registration Data Access Protocol (RDAP) Object Tagging
rfc-editor@rfc-editor.org Mon, 19 November 2018 16:44 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 369DD130DDF; Mon, 19 Nov 2018 08:44:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 W56TZ-1OnkMv; Mon, 19 Nov 2018 08:44:41 -0800 (PST)
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 456E2130DDD; Mon, 19 Nov 2018 08:44:41 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id E3F7CB80BCE; Mon, 19 Nov 2018 08:44:13 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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: <20181119164413.E3F7CB80BCE@rfc-editor.org>
Date: Mon, 19 Nov 2018 08:44:13 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/NQmdCQHzsCu1V9XR2lkms2gAm3s>
Subject: [regext] BCP 221, RFC 8521 on Registration Data Access Protocol (RDAP) Object Tagging
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Nov 2018 16:44:43 -0000
A new Request for Comments is now available in online RFC libraries.
BCP 221
RFC 8521
Title: Registration Data Access Protocol (RDAP)
Object Tagging
Author: S. Hollenbeck,
A. Newton
Status: Best Current Practice
Stream: IETF
Date: November 2018
Mailbox: shollenbeck@verisign.com,
andy@arin.net
Pages: 13
Characters: 22381
Updates: RFC 7484
See Also: BCP 221
I-D Tag: draft-ietf-regext-rdap-object-tag-05.txt
URL: https://www.rfc-editor.org/info/rfc8521
DOI: 10.17487/RFC8521
The Registration Data Access Protocol (RDAP) includes a method that
can be used to identify the authoritative server for processing
domain name, IP address, and autonomous system number queries. The
method does not describe how to identify the authoritative server for
processing other RDAP query types, such as entity queries. This
limitation exists because the identifiers associated with these query
types are typically unstructured. This document updates RFC 7484 by
describing an operational practice that can be used to add structure
to RDAP identifiers and that makes it possible to identify the
authoritative server for additional RDAP queries.
This document is a product of the Registration Protocols Extensions Working Group of the IETF.
BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. 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