[regext] RFC 9537 on Redacted Fields in the Registration Data Access Protocol (RDAP) Response
rfc-editor@rfc-editor.org Fri, 29 March 2024 16:54 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
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 C137BC14F616; Fri, 29 Mar 2024 09:54:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.949
X-Spam-Level:
X-Spam-Status: No, score=-3.949 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PtXIbEvqgJaF; Fri, 29 Mar 2024 09:54:27 -0700 (PDT)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C294C14F60B; Fri, 29 Mar 2024 09:54:27 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 6F32A18FF745; Fri, 29 Mar 2024 09:54:27 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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: <20240329165427.6F32A18FF745@rfcpa.amsl.com>
Date: Fri, 29 Mar 2024 09:54:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/XhZezidJ6YB9TL73E_9S5rGkWis>
Subject: [regext] RFC 9537 on Redacted Fields in the Registration Data Access Protocol (RDAP) Response
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 29 Mar 2024 16:54:31 -0000
A new Request for Comments is now available in online RFC libraries. RFC 9537 Title: Redacted Fields in the Registration Data Access Protocol (RDAP) Response Author: J. Gould, D. Smith, J. Kolker, R. Carney Status: Standards Track Stream: IETF Date: March 2024 Mailbox: jgould@verisign.com, dsmith@verisign.com, jkolker@godaddy.com, rcarney@godaddy.com Pages: 31 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-regext-rdap-redacted-16.txt URL: https://www.rfc-editor.org/info/rfc9537 DOI: 10.17487/RFC9537 This document describes a Registration Data Access Protocol (RDAP) extension for specifying methods of redaction of RDAP responses and explicitly identifying redacted RDAP response fields, using JSONPath as the default expression language. This document is a product of the Registration Protocols Extensions 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/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