| CARVIEW |
Select Language
HTTP/2 200
date: Thu, 09 Oct 2025 13:43:57 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=kze47TkrG_g93K_Gag8OVAyPN77wa80WDO7xceipzzw-1760017437-1.0.1.1-9yuKwCdzuTudlC4U98zRBryvgNXVXSR9k33YBNslfID9ik_BONuP1aegJ47GfJFVlpojtZesDF2WUA3yRCpOPSxLa2gYG8y8nQr_mZu4X7c; path=/; expires=Thu, 09-Oct-25 14:13:57 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98be4f53c8948a2a-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 9537 » RFC Editor
Search RFCs
RFC 9537
Redacted Fields in the Registration Data Access Protocol (RDAP) Response, March 2024
- File formats:
- Also available: XML file for editing
- Status:
- PROPOSED STANDARD
- Authors:
- J. Gould
D. Smith
J. Kolker
R. Carney - Stream:
- IETF
- Source:
- regext (art)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC9537
Discuss this RFC: Send questions or comments to the mailing list regext@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 9537
Abstract
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.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us