<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="std" consensus="true" docName="draft-ietf-regext-rdap-redacted-16" number="9537" ipr="trust200902" obsoletes="" updates="" submissionType="IETF" xml:lang="en" tocInclude="true" tocDepth="4" sortRefs="true" symRefs="true" prepTime="2024-03-29T09:24:24" indexInclude="true" scripts="Common,Latin">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-redacted-16" rel="prev"/>
  <link href="https://dx.doi.org/10.17487/rfc9537" rel="alternate"/>
  <link href="urn:issn:2070-1721" rel="alternate"/>
  <front>
    <title abbrev="Redacted Fields in RDAP">Redacted Fields in the Registration Data Access Protocol (RDAP) Response</title>
    <seriesInfo name="RFC" value="9537" stream="IETF"/>
    <author fullname="James Gould" initials="J." surname="Gould">
      <organization showOnFrontPage="true">VeriSign, Inc.</organization>
      <address>
        <postal>
          <street>12061 Bluemont Way</street>
          <city>Reston</city>
          <region>VA</region>
          <code>20190</code>
          <country>United States of America</country>
        </postal>
        <email>jgould@verisign.com</email>
        <uri>http://www.verisign.com</uri>
      </address>
    </author>
    <author fullname="David Smith" initials="D." surname="Smith">
      <organization showOnFrontPage="true">VeriSign, Inc.</organization>
      <address>
        <postal>
          <street>12061 Bluemont Way</street>
          <city>Reston</city>
          <region>VA</region>
          <code>20190</code>
          <country>United States of America</country>
        </postal>
        <email>dsmith@verisign.com</email>
        <uri>http://www.verisign.com</uri>
      </address>
    </author>
    <author fullname="Jody Kolker" initials="J." surname="Kolker">
      <organization showOnFrontPage="true">GoDaddy Inc.</organization>
      <address>
        <postal>
          <street>14455 N. Hayden Rd., #219</street>
          <city>Scottsdale</city>
          <region>AZ</region>
          <code>85260</code>
          <country>United States of America</country>
        </postal>
        <email>jkolker@godaddy.com</email>
        <uri>http://www.godaddy.com</uri>
      </address>
    </author>
    <author fullname="Roger Carney" initials="R." surname="Carney">
      <organization showOnFrontPage="true">GoDaddy Inc.</organization>
      <address>
        <postal>
          <street>14455 N. Hayden Rd., #219</street>
          <city>Scottsdale</city>
          <region>AZ</region>
          <code>85260</code>
          <country>United States of America</country>
        </postal>
        <email>rcarney@godaddy.com</email>
        <uri>http://www.godaddy.com</uri>
      </address>
    </author>
    <date month="03" year="2024"/>
    <area>art</area>
    <workgroup>regext</workgroup>
    <keyword>Redacted</keyword>
    <keyword>Redaction</keyword>
    <keyword>Redacting</keyword>
    <keyword>JSONPath</keyword>
    <abstract pn="section-abstract">
      <t indent="0" pn="section-abstract-1">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.</t>
    </abstract>
    <boilerplate>
      <section anchor="status-of-memo" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.1">
        <name slugifiedName="name-status-of-this-memo">Status of This Memo</name>
        <t indent="0" pn="section-boilerplate.1-1">
            This is an Internet Standards Track document.
        </t>
        <t indent="0" pn="section-boilerplate.1-2">
            This document is a product of the Internet Engineering Task Force
            (IETF).  It represents the consensus of the IETF community.  It has
            received public review and has been approved for publication by
            the Internet Engineering Steering Group (IESG).  Further
            information on Internet Standards is available in Section 2 of 
            RFC 7841.
        </t>
        <t indent="0" pn="section-boilerplate.1-3">
            Information about the current status of this document, any
            errata, and how to provide feedback on it may be obtained at
            <eref target="https://www.rfc-editor.org/info/rfc9537" brackets="none"/>.
        </t>
      </section>
      <section anchor="copyright" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.2">
        <name slugifiedName="name-copyright-notice">Copyright Notice</name>
        <t indent="0" pn="section-boilerplate.2-1">
            Copyright (c) 2024 IETF Trust and the persons identified as the
            document authors. All rights reserved.
        </t>
        <t indent="0" pn="section-boilerplate.2-2">
            This document is subject to BCP 78 and the IETF Trust's Legal
            Provisions Relating to IETF Documents
            (<eref target="https://trustee.ietf.org/license-info" brackets="none"/>) in effect on the date of
            publication of this document. Please review these documents
            carefully, as they describe your rights and restrictions with
            respect to this document. Code Components extracted from this
            document must include Revised BSD License text as described in
            Section 4.e of the Trust Legal Provisions and are provided without
            warranty as described in the Revised BSD License.
        </t>
      </section>
    </boilerplate>
    <toc>
      <section anchor="toc" numbered="false" removeInRFC="false" toc="exclude" pn="section-toc.1">
        <name slugifiedName="name-table-of-contents">Table of Contents</name>
        <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1">
          <li pn="section-toc.1-1.1">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.1"><xref derivedContent="1" format="counter" sectionFormat="of" target="section-1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-introduction">Introduction</xref></t>
          </li>
          <li pn="section-toc.1-1.2">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.2.1"><xref derivedContent="2" format="counter" sectionFormat="of" target="section-2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-conventions-used-in-this-do">Conventions Used in This Document</xref></t>
          </li>
          <li pn="section-toc.1-1.3">
            <t indent="0" pn="section-toc.1-1.3.1"><xref derivedContent="3" format="counter" sectionFormat="of" target="section-3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-redaction-methods">Redaction Methods</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.3.2">
              <li pn="section-toc.1-1.3.2.1">
                <t indent="0" keepWithNext="true" pn="section-toc.1-1.3.2.1.1"><xref derivedContent="3.1" format="counter" sectionFormat="of" target="section-3.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-redaction-by-removal-method">Redaction by Removal Method</xref></t>
              </li>
              <li pn="section-toc.1-1.3.2.2">
                <t indent="0" pn="section-toc.1-1.3.2.2.1"><xref derivedContent="3.2" format="counter" sectionFormat="of" target="section-3.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-redaction-by-empty-value-me">Redaction by Empty Value Method</xref></t>
              </li>
              <li pn="section-toc.1-1.3.2.3">
                <t indent="0" pn="section-toc.1-1.3.2.3.1"><xref derivedContent="3.3" format="counter" sectionFormat="of" target="section-3.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-redaction-by-partial-value-">Redaction by Partial Value Method</xref></t>
              </li>
              <li pn="section-toc.1-1.3.2.4">
                <t indent="0" pn="section-toc.1-1.3.2.4.1"><xref derivedContent="3.4" format="counter" sectionFormat="of" target="section-3.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-redaction-by-replacement-va">Redaction by Replacement Value Method</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.4">
            <t indent="0" pn="section-toc.1-1.4.1"><xref derivedContent="4" format="counter" sectionFormat="of" target="section-4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-redacted-rdap-response">Redacted RDAP Response</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.4.2">
              <li pn="section-toc.1-1.4.2.1">
                <t indent="0" pn="section-toc.1-1.4.2.1.1"><xref derivedContent="4.1" format="counter" sectionFormat="of" target="section-4.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-rdap-conformance">RDAP Conformance</xref></t>
              </li>
              <li pn="section-toc.1-1.4.2.2">
                <t indent="0" pn="section-toc.1-1.4.2.2.1"><xref derivedContent="4.2" format="counter" sectionFormat="of" target="section-4.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-redacted-member">"redacted" Member</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.5">
            <t indent="0" pn="section-toc.1-1.5.1"><xref derivedContent="5" format="counter" sectionFormat="of" target="section-5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-jsonpath-considerations">JSONPath Considerations</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.5.2">
              <li pn="section-toc.1-1.5.2.1">
                <t indent="0" pn="section-toc.1-1.5.2.1.1"><xref derivedContent="5.1" format="counter" sectionFormat="of" target="section-5.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-jsonpath-client-considerati">JSONPath Client Considerations</xref></t>
              </li>
              <li pn="section-toc.1-1.5.2.2">
                <t indent="0" pn="section-toc.1-1.5.2.2.1"><xref derivedContent="5.2" format="counter" sectionFormat="of" target="section-5.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-jsonpath-server-considerati">JSONPath Server Considerations</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.6">
            <t indent="0" pn="section-toc.1-1.6.1"><xref derivedContent="6" format="counter" sectionFormat="of" target="section-6"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-iana-considerations">IANA Considerations</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.6.2">
              <li pn="section-toc.1-1.6.2.1">
                <t indent="0" pn="section-toc.1-1.6.2.1.1"><xref derivedContent="6.1" format="counter" sectionFormat="of" target="section-6.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-rdap-extensions-registry">RDAP Extensions Registry</xref></t>
              </li>
              <li pn="section-toc.1-1.6.2.2">
                <t indent="0" pn="section-toc.1-1.6.2.2.1"><xref derivedContent="6.2" format="counter" sectionFormat="of" target="section-6.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-rdap-json-values-registry">RDAP JSON Values Registry</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.7">
            <t indent="0" pn="section-toc.1-1.7.1"><xref derivedContent="7" format="counter" sectionFormat="of" target="section-7"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-security-considerations">Security Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.8">
            <t indent="0" pn="section-toc.1-1.8.1"><xref derivedContent="8" format="counter" sectionFormat="of" target="section-8"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-references">References</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.8.2">
              <li pn="section-toc.1-1.8.2.1">
                <t indent="0" pn="section-toc.1-1.8.2.1.1"><xref derivedContent="8.1" format="counter" sectionFormat="of" target="section-8.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">Normative References</xref></t>
              </li>
              <li pn="section-toc.1-1.8.2.2">
                <t indent="0" pn="section-toc.1-1.8.2.2.1"><xref derivedContent="8.2" format="counter" sectionFormat="of" target="section-8.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-informative-references">Informative References</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.9">
            <t indent="0" pn="section-toc.1-1.9.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.a"/><xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgements">Acknowledgements</xref></t>
          </li>
          <li pn="section-toc.1-1.10">
            <t indent="0" pn="section-toc.1-1.10.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.b"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-addresses">Authors' Addresses</xref></t>
          </li>
        </ul>
      </section>
    </toc>
  </front>
  <middle>
    <section numbered="true" removeInRFC="false" toc="include" pn="section-1">
      <name slugifiedName="name-introduction">Introduction</name>
      <t indent="0" pn="section-1-1">This document describes an RDAP extension for specifying methods of
      redaction of RDAP responses and explicitly identifying redacted RDAP
      response fields, using JSONPath as the default expression language.  A redacted RDAP field is one that has data
        removed or replaced in the RDAP response due to server policy, such as the lack of client privilege to
        receive the field. This extension can be used to identify
      redacted RDAP fields in any RDAP object class, as defined in <xref target="RFC9083" format="default" sectionFormat="of" derivedContent="RFC9083"/>, or
      RDAP fields defined in RDAP extensions.  Because an RDAP response may exclude a field due to either the lack of data
      or the lack of RDAP client privileges,
      this extension is used to explicitly specify which RDAP fields are not included in the RDAP response due
      to redaction.  It thereby provides a capability for disambiguation
      between redaction and other possible reasons for data or field absence.</t>
      <t indent="0" pn="section-1-2">In <xref target="RFC9082" format="default" sectionFormat="of" derivedContent="RFC9082"/>, RDAP supports both lookup and search queries, where a lookup query responds
        with a single object and a search query responds with a list of objects.
        This document applies to redaction of a single object of a lookup response and in each of the objects of a search response.</t>
      <t indent="0" pn="section-1-3">JSONPath, as defined in <xref target="RFC9535" format="default" sectionFormat="of" derivedContent="RFC9535"/>, is used
      as the default expression language to reference RDAP fields that have been redacted.
      The redacted JSON fields will be removed, have empty values, have partial values, or be replaced in the RDAP response.
      JSON is defined by <xref target="RFC8259" format="default" sectionFormat="of" derivedContent="RFC8259"/>.</t>
    </section>
    <section numbered="true" removeInRFC="false" toc="include" pn="section-2">
      <name slugifiedName="name-conventions-used-in-this-do">Conventions Used in This Document</name>
      <t indent="0" pn="section-2-1">
    The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
    "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
    described in BCP 14 <xref target="RFC2119" format="default" sectionFormat="of" derivedContent="RFC2119"/> <xref target="RFC8174" format="default" sectionFormat="of" derivedContent="RFC8174"/> 
    when, and only when, they appear in all capitals, as shown here.
      </t>
      <t indent="0" pn="section-2-2">The JSON examples include extra line breaks and empty space.  For
        instance, the JSONPath expressions are broken out into multiple
      lines when required for illustration.</t>
      <t indent="0" pn="section-2-3">The JSONPath expressions in the examples are for illustration
   purposes with single-role entities, and the exact expressions to be used
   by the server are out of scope.</t>
    </section>
    <section anchor="redaction-methods" numbered="true" removeInRFC="false" toc="include" pn="section-3">
      <name slugifiedName="name-redaction-methods">Redaction Methods</name>
      <t indent="0" pn="section-3-1">Redaction in RDAP can be handled in multiple ways. The resulting redacted RDAP response <bcp14>MUST</bcp14> comply with the format defined in the RDAP RFCs, such as <xref target="RFC9083" format="default" sectionFormat="of" derivedContent="RFC9083"/> and updates.
      The use of placeholder text for the values of the RDAP fields, such as "XXXX", 
      <bcp14>MUST NOT</bcp14> be used for redaction, since the placeholder text value may not match the format requirements of each of the RDAP fields, which could provide an inconsistent and unreliable redaction signal.  
      This section covers the redaction
        methods that can be used with the redaction signaling defined in <xref target="redacted-member" format="default" sectionFormat="of" derivedContent="Section 4.2"/>.</t>
      <t indent="0" pn="section-3-2">RDAP responses, as defined in <xref target="RFC9083" format="default" sectionFormat="of" derivedContent="RFC9083"/>, include
      a mix of JSON objects and JSON arrays, where JSON arrays are heavily used for entity objects with <xref target="RFC7095" format="default" sectionFormat="of" derivedContent="RFC7095">jCard</xref>.
      jCard is a JSON representation of <xref target="RFC6350" format="default" sectionFormat="of" derivedContent="RFC6350">vCard</xref> that
      inherits its dependency on arrays.
      An example is the vCard "ADR" property <xref target="RFC6350" format="default" sectionFormat="of" derivedContent="RFC6350"/>, or the jCard
    "adr" property <xref target="RFC7095" format="default" sectionFormat="of" derivedContent="RFC7095"/>, which defines a sequence of
    address components. According to <xref target="RFC6350" format="default" sectionFormat="of" derivedContent="RFC6350"/>, when an "ADR" property component value is missing,
      the associated component separator <bcp14>MUST</bcp14> still be specified.
      jCard extends the use of arrays with
      each individual vCard property being represented by an array of three fixed elements, followed by one or more additional elements.
      The mix of JSON objects and JSON arrays impacts the methods used for redaction in RDAP.</t>
      <t indent="0" pn="section-3-3">The redaction of RDAP fields fall into the four categories defined in the following subsections.</t>
      <section anchor="redaction-removal" numbered="true" removeInRFC="false" toc="include" pn="section-3.1">
        <name slugifiedName="name-redaction-by-removal-method">Redaction by Removal Method</name>
        <t indent="0" pn="section-3.1-1">The Redaction by Removal Method is when the RDAP field is removed from the RDAP response, which is the default method.
        The Redaction by Removal Method can be done for all RDAP response fields except for response fields using the position in an array to signal the redacted field (e.g., the JSON arrays used with jCard).
        RDAP extensions, such as the one described in <xref target="I-D.ietf-regext-rdap-jscontact" format="default" sectionFormat="of" derivedContent="RDAP-JSCONTACT">"Using JSContact in Registration Data Access Protocol (RDAP) JSON Responses"</xref>, do not have a dependency on the use of positional JSON arrays and
        are therefore suited for the Redaction by Removal Method.</t>
        <t indent="0" pn="section-3.1-2">When an RDAP object is redacted
        by removal, all of the RDAP object's child fields are also removed.  Only the redacted RDAP object needs to be referenced in the list of redacted fields,
        as defined in <xref target="redacted-member" format="default" sectionFormat="of" derivedContent="Section 4.2"/>.</t>
        <t indent="0" pn="section-3.1-3">An example of redacting an RDAP object is removing the administrative contact
        from the RDAP response and including the following "redacted" member:</t>
        <figure anchor="redacted-admin-contact" align="left" suppress-title="false" pn="figure-1">
          <name slugifiedName="name-redacted-administrative-con">Redacted Administrative Contact</name>
          <sourcecode type="json" markers="false" pn="section-3.1-4.1">
"redacted": [
  {
    "name": {
      "description": "Administrative Contact"
    },
    "prePath": "$.entities[?(@.roles[0]=='administrative')]",
    "method": "removal"
  }
]
</sourcecode>
        </figure>
        <t indent="0" pn="section-3.1-5">The Redaction by Removal Method <bcp14>MUST NOT</bcp14> be used to remove an element of an array where the position of the element in the array determines semantic meaning.
          For example, removal of an individual data field in jCard will result in a non-conformant jCard array definition.</t>
      </section>
      <section anchor="redaction-empty-value" numbered="true" removeInRFC="false" toc="include" pn="section-3.2">
        <name slugifiedName="name-redaction-by-empty-value-me">Redaction by Empty Value Method</name>
        <t indent="0" pn="section-3.2-1">The Redaction by Empty Value Method is when a redacted field is not removed but its value is set to an empty value, such as "" for a jCard
        text ("text") property or null for a non-text property.  The empty jCard values ("" or null) are referenced in the "redacted"
        member in place of the jCard property name in an array, such as referencing the "fn" jCard property value at position 3 instead of referencing the "fn"
        jCard property name at position 0.
        The Redaction by Empty Value Method <bcp14>MUST</bcp14> be used only when redacting JSON response fields that use the position in an
        array to signal the redacted field (e.g., jCard arrays).
        Optional jCard properties <bcp14>MUST</bcp14>
        use the <xref target="redaction-removal" format="default" sectionFormat="of" derivedContent="Section 3.1">Redaction by Removal Method</xref> to redact the entire property.
        The required jCard "fn" property, defined in <xref target="RFC6350" section="6.2.1" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc6350#section-6.2.1" derivedContent="RFC6350">vCard</xref>, <bcp14>MUST</bcp14> use the Redaction by Empty Value Method to redact the property value.
        Removing the "fn" property would violate <xref target="RFC6350" format="default" sectionFormat="of" derivedContent="RFC6350">vCard</xref>, and removing the property value
        would violate the fixed array positions defined in jCard.</t>
        <figure anchor="redacted-fn-empty-value" align="left" suppress-title="false" pn="figure-2">
          <name slugifiedName="name-redacted-fn-jcard-property-">Redacted "fn" jCard Property Using the Redaction by Empty Value Method</name>
          <sourcecode type="json" markers="false" pn="section-3.2-2.1">
[
  "fn",
  {},
  "text",
  ""
]
</sourcecode>
        </figure>
        <t indent="0" pn="section-3.2-3">An example of the "redacted" member for the redacted "fn" jCard property value, which is array position 3:</t>
        <figure anchor="redacted-fn-array-pos" align="left" suppress-title="false" pn="figure-3">
          <name slugifiedName="name-redacted-registrant-name-us">Redacted Registrant Name Using an Array Position</name>
          <sourcecode type="json" markers="false" pn="section-3.2-4.1">
"redacted": [
  {
    "name": {
      "description": "Registrant Name"
    },
    "postPath": "$.entities[?(@.roles[0]=='registrant')].
      vcardArray[1][?(@[0]=='fn')][3]",
    "pathLang": "jsonpath",
    "method": "emptyValue",
    "reason": {
      "description": "Server policy"
    }
  }
]
</sourcecode>
        </figure>
      </section>
      <section anchor="redaction-partial-value" numbered="true" removeInRFC="false" toc="include" pn="section-3.3">
        <name slugifiedName="name-redaction-by-partial-value-">Redaction by Partial Value Method</name>
        <t indent="0" pn="section-3.3-1">The Redaction by Partial Value Method is when a redacted field is not removed but its value has a portion of the data removed, such as for the "label" or "fn" jCard
        properties.  The partial values are referenced in the "redacted"
        member in place of the property name in an array, such as referencing the "fn" jCard property value at position 3 instead of referencing the "fn"
        jCard property name at position 0.
        The Redaction by Partial Value Method <bcp14>SHOULD</bcp14> be used only when redacting JSON response fields that use a formatted value, where a portion of the value is removed.  
        </t>
        <t indent="0" pn="section-3.3-2">An example of the "label" jCard property in <xref target="RFC7095" sectionFormat="of" section="3.3.1.3" format="default" derivedLink="https://rfc-editor.org/rfc/rfc7095#section-3.3.1.3" derivedContent="RFC7095"/> that redacts "123 Maple Ave\nSuite 901\n":</t>
        <figure anchor="redacted-home-address-label-value" align="left" suppress-title="false" pn="figure-4">
          <name slugifiedName="name-redacted-label-jcard-proper">Redacted "label" jCard Property</name>
          <sourcecode type="json" markers="false" pn="section-3.3-3.1">
["adr",
  {
    "type":"home",
    "label":"Vancouver\nBC\n1239\n"
  },
  "text",
  [
    "", "", "", "", "", "", ""
  ]
]
</sourcecode>
        </figure>
        <t indent="0" pn="section-3.3-4">An example of the "redacted" member for the redacted "label" jCard property value, based on <xref target="RFC7095" sectionFormat="of" section="3.3.1.3" format="default" derivedLink="https://rfc-editor.org/rfc/rfc7095#section-3.3.1.3" derivedContent="RFC7095"/>:</t>
        <figure anchor="redacted-home-address-label" align="left" suppress-title="false" pn="figure-5">
          <name slugifiedName="name-redacted-label-using-the-re">Redacted Label Using the Redaction by Partial Value Method</name>
          <sourcecode type="json" markers="false" pn="section-3.3-5.1">
"redacted": [
  {
    "name": {
      "description": "Home Address Label"
    },
    "postPath": "$.vcardArray[1][?(@[0]=='adr')][1].label",
    "pathLang": "jsonpath",
    "method": "partialValue",
    "reason": {
      "description": "Server policy"
    }
  }
]
</sourcecode>
        </figure>
      </section>
      <section anchor="redaction-replacement-value" numbered="true" removeInRFC="false" toc="include" pn="section-3.4">
        <name slugifiedName="name-redaction-by-replacement-va">Redaction by Replacement Value Method</name>
        <t indent="0" pn="section-3.4-1">The Redaction by Replacement Value Method is when a redacted field is not removed but its value is replaced with a different value, such as protecting the "email" jCard
        property value with an anonymized email "text" value or the use of an alternative "uri" value to a web form.  Replacing a property value is a form of redaction, since it protects the
        true property value for privacy reasons.</t>
        <figure anchor="redacted-email-anonymized-value" align="left" suppress-title="false" pn="figure-6">
          <name slugifiedName="name-redacted-email-jcard-proper">Redacted "email" jCard Property Using the Redaction by Replacement Value Method with an Anonymized Email</name>
          <sourcecode type="json" markers="false" pn="section-3.4-2.1">
[
  "email",
  {},
  "text",
  "anonymized123@example.com"
]
</sourcecode>
        </figure>
        <figure anchor="redacted-email-replacement-anonymized" align="left" suppress-title="false" pn="figure-7">
          <name slugifiedName="name-redacted-email-using-a-repl">Redacted Email Using a Replacement Value with an Anonymized "text" Value</name>
          <sourcecode type="json" markers="false" pn="section-3.4-3.1">
"redacted": [
  {
    "name": {
      "description": "Registrant Email"
    },
    "postPath": "$.entities[?(@.roles[0]=='registrant')].
               vcardArray[1][?(@[0]=='email')][3]",
    "pathLang": "jsonpath",
    "method": "replacementValue",
  }
]
</sourcecode>
        </figure>
        <figure anchor="redacted-email-links-related" align="left" suppress-title="false" pn="figure-8">
          <name slugifiedName="name-redacted-email-jcard-propert">Redacted "email" jCard Property Using the Redaction by Replacement Value Method with a "contact-uri" jCard Property to a Web Form</name>
          <sourcecode type="json" markers="false" pn="section-3.4-4.1">
[
  "contact-uri",
  {},
  "uri",
  "https://email.example.com/123"
]
</sourcecode>
        </figure>
        <figure anchor="redacted-email-replacement-links-related" align="left" suppress-title="false" pn="figure-9">
          <name slugifiedName="name-redacted-email-using-a-repla">Redacted Email Using a Replacement Value with a "contact-uri" jCard Property to a Web Form</name>
          <sourcecode type="json" markers="false" pn="section-3.4-5.1">
"redacted": [
  {
    "name": {
      "description": "Registrant Email"
    },
    "prePath": "$.entities[?(@.roles[0]=='registrant')].
               vcardArray[1][?(@[0]=='email')]",
    "replacementPath": "$.entities[?(@.roles[0]=='registrant')].
               vcardArray[1][?(@[0]=='contact-uri')]",
    "pathLang": "jsonpath",
    "method": "replacementValue",
  }
]
</sourcecode>
        </figure>
      </section>
    </section>
    <section anchor="redacted-rdap-response" numbered="true" removeInRFC="false" toc="include" pn="section-4">
      <name slugifiedName="name-redacted-rdap-response">Redacted RDAP Response</name>
      <section anchor="rdap-conformance" numbered="true" removeInRFC="false" toc="include" pn="section-4.1">
        <name slugifiedName="name-rdap-conformance">RDAP Conformance</name>
        <t indent="0" pn="section-4.1-1">RDAP responses that contain values described in this document <bcp14>MUST</bcp14>
           indicate conformance with this specification by including an
           "rdapConformance" <xref target="RFC9083" format="default" sectionFormat="of" derivedContent="RFC9083"/> value of "redacted".	   
           The "redacted" extension identifier is described in <xref target="rdap-extensions-registry" format="default" sectionFormat="of" derivedContent="Section 6.1"/>.</t>
        <figure anchor="rdapConformance-with-redacted" align="left" suppress-title="false" pn="figure-10">
          <name slugifiedName="name-rdapconformance-with-redact">"rdapConformance" with Redacted Extension</name>
          <sourcecode type="json" markers="false" pn="section-4.1-2.1">
"rdapConformance": [
  "rdap_level_0",
  "redacted"
]
</sourcecode>
        </figure>
      </section>
      <section anchor="redacted-member" numbered="true" removeInRFC="false" toc="include" pn="section-4.2">
        <name slugifiedName="name-redacted-member">"redacted" Member</name>
        <t indent="0" pn="section-4.2-1">The "redacted" member <bcp14>MUST</bcp14> be added to the RDAP response when
        there is one or more redacted fields.  The "redacted" member is included as a member of the object instance in a lookup response, such as the object classes defined in <xref target="RFC9083" format="default" sectionFormat="of" derivedContent="RFC9083"/>, and
        as a member of the object instances in a search response.</t>
        <t indent="0" pn="section-4.2-2">The server, including a redacted signal, provides an unauthorized client additional 
        information related to the existence of data and <bcp14>MAY</bcp14> exclude the redacted members 
        for RDAP fields that are considered a privacy issue in providing a data existence signal.
        The server <bcp14>MAY</bcp14> choose to publish a redaction policy describing how this extension is implemented for their constituency. 
        The contents of such a policy are outside the scope of this specification.</t>
        <t indent="0" pn="section-4.2-3">The "redacted" member contains an array
        of objects with the following child members:</t>
        <dl indent="4" newline="false" spacing="normal" pn="section-4.2-4">
          <dt pn="section-4.2-4.1">"name":</dt>
          <dd pn="section-4.2-4.2">
            <bcp14>REQUIRED</bcp14> logical name for the redacted field.  The logical name used
          for the redacted field is up to server policy.
          The logical name
          is defined using an object with a "type" field denoting a registered redacted
          name (see <xref target="json-values-registry" format="default" sectionFormat="of" derivedContent="Section 6.2"/>) or a "description" field denoting an unregistered redacted name.
          The registered redacted names and the chosen unregistered names
          can meet the needs of different RDAP services or industries.</dd>
          <dt pn="section-4.2-4.3">"prePath":</dt>
          <dd pn="section-4.2-4.4">
            <bcp14>OPTIONAL</bcp14> JSON path expression referencing a redacted JSON field in the pre-redacted response, using the expression language defined by the "pathLang" member.  
          The "prePath" member <bcp14>MAY</bcp14> be set when the redacted field does not exist in the redacted response for the <xref target="redaction-removal" format="default" sectionFormat="of" derivedContent="Section 3.1">Redaction by Removal Method</xref> and the <xref target="redaction-replacement-value" format="default" sectionFormat="of" derivedContent="Section 3.4">Redaction by Replacement Value Method</xref>.  
          The "prePath" member <bcp14>MUST NOT</bcp14> be set when the "postPath" member is set. 
          </dd>
          <dt pn="section-4.2-4.5">"postPath":</dt>
          <dd pn="section-4.2-4.6">
            <bcp14>OPTIONAL</bcp14> JSON path expression referencing a redacted JSON field in the redacted (post-redacted) response, using the expression language defined by the "pathLang" member.
          The "postPath" member <bcp14>MUST</bcp14> be set when the redacted field does exist in the redacted response for the <xref target="redaction-empty-value" format="default" sectionFormat="of" derivedContent="Section 3.2">Redaction by Empty Value Method</xref>, the <xref target="redaction-partial-value" format="default" sectionFormat="of" derivedContent="Section 3.3">Redaction by Partial Value Method</xref>, and the <xref target="redaction-replacement-value" format="default" sectionFormat="of" derivedContent="Section 3.4">Redaction by Replacement Value Method</xref>.  
          The "postPath" member <bcp14>MUST NOT</bcp14> be set when the "prePath" member is set. 
          </dd>
          <dt pn="section-4.2-4.7">"replacementPath":</dt>
          <dd pn="section-4.2-4.8">
            <bcp14>OPTIONAL</bcp14> JSON path expression of the replacement field of the redacted field with the
            <xref target="redaction-replacement-value" format="default" sectionFormat="of" derivedContent="Section 3.4">Redaction by Replacement Value Method</xref>, using the expression language defined by the "pathLang" member.
          </dd>
          <dt pn="section-4.2-4.9">"pathLang":</dt>
          <dd pn="section-4.2-4.10">
            <bcp14>OPTIONAL</bcp14> JSON path expression language used, with the default value of "jsonpath" for JSONPath <xref target="RFC9535" format="default" sectionFormat="of" derivedContent="RFC9535"/>.
           Other JSON path expression languages registered with the "redacted expression language" Type in the "RDAP JSON Values" registry <bcp14>MAY</bcp14> be used based on server policy.</dd>
          <dt pn="section-4.2-4.11">"method":</dt>
          <dd pn="section-4.2-4.12">
            <t indent="0" pn="section-4.2-4.12.1"><bcp14>OPTIONAL</bcp14> redaction method used, with one of the following values:</t>
            <ul bare="false" empty="false" indent="3" spacing="normal" pn="section-4.2-4.12.2">
              <li pn="section-4.2-4.12.2.1">"removal" indicating the <xref target="redaction-removal" format="default" sectionFormat="of" derivedContent="Section 3.1">Redaction by Removal Method</xref>,</li>
              <li pn="section-4.2-4.12.2.2">"emptyValue" indicating the <xref target="redaction-empty-value" format="default" sectionFormat="of" derivedContent="Section 3.2">Redaction by Empty Value Method</xref>,</li>
              <li pn="section-4.2-4.12.2.3">"partialValue" indicating the <xref target="redaction-partial-value" format="default" sectionFormat="of" derivedContent="Section 3.3">Redaction by Partial Value Method</xref>, or</li>
              <li pn="section-4.2-4.12.2.4">"replacementValue" indicating the <xref target="redaction-replacement-value" format="default" sectionFormat="of" derivedContent="Section 3.4">Redaction by Replacement Value Method</xref>.</li>
            </ul>
            <t indent="0" pn="section-4.2-4.12.3">The default value is "removal" when not provided.</t>
          </dd>
          <dt pn="section-4.2-4.13">"reason":</dt>
          <dd pn="section-4.2-4.14">
            <bcp14>OPTIONAL</bcp14> human-readable reason(s) for the redacted field in
          the language defined by the "lang" <xref target="RFC9083" format="default" sectionFormat="of" derivedContent="RFC9083"/> member.
          The default language is "en" if the "lang" <xref target="RFC9083" format="default" sectionFormat="of" derivedContent="RFC9083"/> member is not specified.
       The reason is defined using an object with an <bcp14>OPTIONAL</bcp14> "type" field denoting a registered redacted reason
          (see <xref target="json-values-registry" format="default" sectionFormat="of" derivedContent="Section 6.2"/>) and an <bcp14>OPTIONAL</bcp14> "description" field denoting an unregistered redacted reason.
          The "description" field <bcp14>MUST NOT</bcp14> be a client processing dependency.</dd>
        </dl>
        <t indent="0" pn="section-4.2-5">Example of the unredacted version of an RDAP lookup response:</t>
        <figure anchor="unredacted-lookup-response" align="left" suppress-title="false" pn="figure-11">
          <name slugifiedName="name-unredacted-rdap-lookup-resp">Unredacted RDAP Lookup Response</name>
          <sourcecode type="json" markers="false" pn="section-4.2-6.1">
    {
      "rdapConformance": [
        "rdap_level_0"
      ],
      "objectClassName": "domain",
      "handle": "ABC123",
      "ldhName": "example.com",
      "secureDNS": {
        "delegationSigned": false
      },
      "notices": [
        {
          "title": "Terms of Use",
          "description": [
            "Service subject to Terms of Use."
          ],
          "links": [
            {
              "rel": "self",
              "href": "https://www.example.com/terms-of-use",
              "type": "text/html",
              "value": "https://www.example.com/terms-of-use"
            }
          ]
        }
      ],
      "nameservers": [
        {
          "objectClassName": "nameserver",
          "ldhName": "ns1.example.com"
        },
        {
          "objectClassName": "nameserver",
          "ldhName": "ns2.example.com"
        }
      ],
      "entities": [
        {
          "objectClassName": "entity",
          "handle": "123",
          "roles": [
            "registrar"
          ],
          "publicIds": [
            {
              "type": "IANA Registrar ID",
              "identifier": "1"
            }
          ],
          "vcardArray": [
            "vcard",
            [
              [
                "version",
                {},
                "text",
                "4.0"
              ],
              [
                "fn",
                {},
                "text",
                "Example Registrar Inc."
              ],
              [
                "adr",
                {},
                "text",
                [
                  "",
                  "Suite 100",
                  "123 Example Dr.",
                  "Dulles",
                  "VA",
                  "20166-6503",
                  "US"
                ]
              ],
              [
                "email",
                {},
                "text",
                "contact@organization.example"
              ],
              [
                "tel",
                {
                  "type": "voice"
                },
                "uri",
                "tel:+1.7035555555;ext=1234"
              ],
              [
                "tel",
                {
                  "type": "fax"
                },
                "uri",
                "tel:+1.7035555556"
              ]
            ]
          ],
          "entities": [
            {
              "objectClassName": "entity",
              "roles": [
                "abuse"
              ],
              "vcardArray": [
                "vcard",
                [
                  [
                    "version",
                    {},
                    "text",
                    "4.0"
                  ],
                  [
                    "fn",
                    {},
                    "text",
                    "Abuse Contact"
                  ],
                  [
                    "email",
                    {},
                    "text",
                    "abuse@organization.example"
                  ],
                  [
                    "tel",
                    {
                      "type": "voice"
                    },
                    "uri",
                    "tel:+1.7035555555;ext=1234"
                  ]
                ]
              ]
            }
          ]
        },
        {
          "objectClassName": "entity",
          "handle": "XXXX",
          "roles": [
            "registrant"
          ],
          "vcardArray": [
            "vcard",
            [
              [
                "version",
                {},
                "text",
                "4.0"
              ],
              [
                "fn",
                {},
                "text",
                "Registrant User"
              ],
              [
                "org",
                {},
                "text",
                "Example Inc."
              ],
              [
                "adr",
                {},
                "text",
                [
                  "",
                  "Suite 1235",
                  "4321 Rue Somewhere",
                  "Quebec",
                  "QC",
                  "G1V 2M2",
                  "Canada"
                ]
              ],
              [
                "email",
                {},
                "text",
                "registrant.user@example.com"
              ],
              [
                "tel",
                {
                  "type": "voice"
                },
                "uri",
                "tel:+1-555-555-1235;ext=123"
              ],
              [
                "tel",
                {
                  "type": "fax"
                },
                "uri",
                "tel:+1-555-555-5321"
              ]
            ]
          ]
        },
        {
          "objectClassName": "entity",
          "handle": "YYYY",
          "roles": [
            "technical"
          ],
          "vcardArray": [
            "vcard",
            [
              [
                "version",
                {},
                "text",
                "4.0"
              ],
              [
                "fn",
                {},
                "text",
                "Technical User"
              ],
              [
                "org",
                {},
                "text",
                "Example Inc."
              ],
              [
                "adr",
                {},
                "text",
                [
                  "",
                  "Suite 1234",
                  "4321 Rue Somewhere",
                  "Quebec",
                  "QC",
                  "G1V 2M2",
                  "Canada"
                ]
              ],
              [
                "email",
                {},
                "text",
                "technical.user@example.com"
              ],
              [
                "tel",
                {
                  "type": "voice"
                },
                "uri",
                "tel:+1-555-555-1234;ext=321"
              ],
              [
                "tel",
                {
                  "type": "fax"
                },
                "uri",
                "tel:+1-555-555-4321"
              ]
            ]
          ]
        },
        {
          "objectClassName": "entity",
          "handle": "ZZZZ",
          "roles": [
            "administrative"
          ],
          "vcardArray": [
            "vcard",
            [
              [
                "version",
                {},
                "text",
                "4.0"
              ],
              [
                "fn",
                {},
                "text",
                "Administrative User"
              ],
              [
                "org",
                {},
                "text",
                "Example Inc."
              ],
              [
                "adr",
                {},
                "text",
                [
                  "",
                  "Suite 1236",
                  "4321 Rue Somewhere",
                  "Quebec",
                  "QC",
                  "G1V 2M2",
                  "Canada"
                ]
              ],
              [
                "email",
                {},
                "text",
                "administrative.user@example.com"
              ],
              [
                "tel",
                {
                  "type": "voice"
                },
                "uri",
                "tel:+1-555-555-1236;ext=789"
              ],
              [
                "tel",
                {
                  "type": "fax"
                },
                "uri",
                "tel:+1-555-555-6321"
              ]
            ]
          ]
        },
        {
          "objectClassName": "entity",
          "handle": "WWWW",
          "roles": [
            "billing"
          ],
          "vcardArray": [
            "vcard",
            [
              [
                "version",
                {},
                "text",
                "4.0"
              ],
              [
                "fn",
                {},
                "text",
                "Billing User"
              ],
              [
                "email",
                {},
                "text",
                "billing.user@example.com"
              ]
            ]
          ]
        }
      ],
      "events": [
        {
          "eventAction": "registration",
          "eventDate": "1997-06-03T00:00:00Z"
        },
        {
          "eventAction": "last changed",
          "eventDate": "2020-05-28T01:35:00Z"
        },
        {
          "eventAction": "expiration",
          "eventDate": "2021-06-03T04:00:00Z"
        }
      ],
      "status": [
        "server delete prohibited",
        "server update prohibited",
        "server transfer prohibited",
        "client transfer prohibited"
      ]
    }
</sourcecode>
        </figure>
        <t indent="0" pn="section-4.2-7">Example of the redacted version of an RDAP lookup response:</t>
        <figure anchor="redacted-lookup-response" align="left" suppress-title="false" pn="figure-12">
          <name slugifiedName="name-redacted-rdap-lookup-respon">Redacted RDAP Lookup Response</name>
          <sourcecode type="json" markers="false" pn="section-4.2-8.1">
    {
      "rdapConformance": [
        "rdap_level_0",
        "redacted"
      ],
      "objectClassName": "domain",
      "ldhName": "example.com",
      "secureDNS": {
        "delegationSigned": false
      },
      "notices": [
        {
          "title": "Terms of Use",
          "description": [
            "Service subject to Terms of Use."
          ],
          "links": [
            {
              "rel": "self",
              "href": "https://www.example.com/terms-of-use",
              "type": "text/html",
              "value": "https://www.example.com/terms-of-use"
            }
          ]
        }
      ],
      "nameservers": [
        {
          "objectClassName": "nameserver",
          "ldhName": "ns1.example.com"
        },
        {
          "objectClassName": "nameserver",
          "ldhName": "ns2.example.com"
        }
      ],
      "entities": [
        {
          "objectClassName": "entity",
          "handle": "123",
          "roles": [
            "registrar"
          ],
          "publicIds": [
            {
              "type": "IANA Registrar ID",
              "identifier": "1"
            }
          ],
          "vcardArray": [
            "vcard",
            [
              [
                "version",
                {},
                "text",
                "4.0"
              ],
              [
                "fn",
                {},
                "text",
                "Example Registrar Inc."
              ],
              [
                "adr",
                {},
                "text",
                [
                  "",
                  "Suite 100",
                  "123 Example Dr.",
                  "Dulles",
                  "VA",
                  "20166-6503",
                  "US"
                ]
              ],
              [
                "email",
                {},
                "text",
                "contact@organization.example"
              ],
              [
                "tel",
                {
                  "type": "voice"
                },
                "uri",
                "tel:+1.7035555555"
              ],
              [
                "tel",
                {
                  "type": "fax"
                },
                "uri",
                "tel:+1.7035555556"
              ]
            ]
          ],
          "entities": [
            {
              "objectClassName": "entity",
              "roles": [
                "abuse"
              ],
              "vcardArray": [
                "vcard",
                [
                  [
                    "version",
                    {},
                    "text",
                    "4.0"
                  ],
                  [
                    "fn",
                    {},
                    "text",
                    "Abuse Contact"
                  ],
                  [
                    "email",
                    {},
                    "text",
                    "abuse@organization.example"
                  ],
                  [
                    "tel",
                    {
                      "type": "voice"
                    },
                    "uri",
                    "tel:+1.7035555555"
                  ]
                ]
              ]
            }
          ]
        },
        {
          "objectClassName": "entity",
          "handle": "XXXX",
          "roles": [
            "registrant"
          ],
          "vcardArray": [
            "vcard",
            [
              [
                "version",
                {},
                "text",
                "4.0"
              ],
              [
                "fn",
                {},
                "text",
                ""
              ],
              [
                "adr",
                {},
                "text",
                [
                  "",
                  "",
                  "",
                  "",
                  "QC",
                  "",
                  "Canada"
                ]
              ]
            ]
          ]
        },
        {
          "objectClassName": "entity",
          "handle": "YYYY",
          "roles": [
            "technical"
          ],
          "vcardArray": [
            "vcard",
            [
              [
                "version",
                {},
                "text",
                "4.0"
              ],
              [
                "fn",
                {},
                "text",
                ""
              ],
              [
                "org",
                {},
                "text",
                "Example Inc."
              ],
              [
                "adr",
                {},
                "text",
                [
                  "",
                  "Suite 1234",
                  "4321 Rue Somewhere",
                  "Quebec",
                  "QC",
                  "G1V 2M2",
                  "Canada"
                ]
              ]
            ]
          ]
        }
      ],
      "events": [
        {
          "eventAction": "registration",
          "eventDate": "1997-06-03T00:00:00Z"
        },
        {
          "eventAction": "last changed",
          "eventDate": "2020-05-28T01:35:00Z"
        },
        {
          "eventAction": "expiration",
          "eventDate": "2021-06-03T04:00:00Z"
        }
      ],
      "status": [
        "server delete prohibited",
        "server update prohibited",
        "server transfer prohibited",
        "client transfer prohibited"
      ],
      "redacted": [
        {
          "name": {
            "description": "Registry Domain ID"
          },
          "prePath": "$.handle",
          "pathLang": "jsonpath",
          "method": "removal",
          "reason": {
            "description": "Server policy"
          }
        },
        {
          "name": {
            "description": "Registrant Name"
          },
          "postPath": "$.entities[?(@.roles[0]=='registrant')].
            vcardArray[1][?(@[0]=='fn')][3]",
          "pathLang": "jsonpath",
          "method": "emptyValue",
          "reason": {
            "description": "Server policy"
          }
        },
        {
          "name": {
            "description": "Registrant Organization"
          },
          "prePath": "$.entities[?(@.roles[0]=='registrant')].
            vcardArray[1][?(@[0]=='org')]",
          "pathLang": "jsonpath",
          "method": "removal",
          "reason": {
            "description": "Server policy"
          }
        },
        {
          "name": {
            "description": "Registrant Street"
          },
          "postPath": "$.entities[?(@.roles[0]=='registrant')].
            vcardArray[1][?(@[0]=='adr')][3][:3]",
          "pathLang": "jsonpath",
          "method": "emptyValue",
          "reason": {
            "description": "Server policy"
          }
        },
        {
          "name": {
            "description": "Registrant City"
          },
          "postPath": "$.entities[?(@.roles[0]=='registrant')].
            vcardArray[1][?(@[0]=='adr')][3][3]",
          "pathLang": "jsonpath",
          "method": "emptyValue",
          "reason": {
            "description": "Server policy"
          }
        },
        {
          "name": {
            "description": "Registrant Postal Code"
          },
          "postPath": "$.entities[?(@.roles[0]=='registrant')].
            vcardArray[1][?(@[0]=='adr')][3][5]",
          "pathLang": "jsonpath",
          "method": "emptyValue",
          "reason": {
            "description": "Server policy"
          }
        },
        {
          "name": {
            "description": "Registrant Email"
          },
          "prePath": "$.entities[?(@.roles[0]=='registrant')].
            vcardArray[1][?(@[0]=='email')]",
          "method": "removal",
          "reason": {
            "description": "Server policy"
          }
        },
        {
          "name": {
            "description": "Registrant Phone"
          },
          "prePath": "$.entities[?(@.roles[0]=='registrant')].
            vcardArray[1][?(@[1].type=='voice')]",
          "method": "removal",
          "reason": {
            "description": "Server policy"
          }
        },
        {
          "name": {
            "description": "Technical Name"
          },
          "postPath": "$.entities[?(@.roles[0]=='technical')].
            vcardArray[1][?(@[0]=='fn')][3]",
          "method": "emptyValue",
          "reason": {
            "description": "Server policy"
          }
        },
        {
          "name": {
            "description": "Technical Email"
          },
          "prePath": "$.entities[?(@.roles[0]=='technical')].
            vcardArray[1][?(@[0]=='email')]",
          "method": "removal",
          "reason": {
            "description": "Server policy"
          }
        },
        {
          "name": {
            "description": "Technical Phone"
          },
          "prePath": "$.entities[?(@.roles[0]=='technical')].
            vcardArray[1][?(@[1].type=='voice')]",
          "method": "removal",
          "reason": {
            "description": "Server policy"
          }
        },
        {
          "name": {
            "description": "Technical Fax"
          },
          "prePath": "$.entities[?(@.roles[0]=='technical')].
            vcardArray[1][?(@[1].type=='fax')]",
          "reason": {
            "description": "Client request"
          }
        },
        {
          "name": {
            "description": "Administrative Contact"
          },
          "prePath": "$.entities[?(@.roles[0]=='administrative')]",
          "method": "removal",
          "reason": {
            "description": "Refer to the technical contact"
          }
        },
        {
          "name": {
            "description": "Billing Contact"
          },
          "prePath": "$.entities[?(@.roles[0]=='billing')]",
          "method": "removal",
          "reason": {
            "description": "Refer to the registrant contact"
          }
        }
      ]
    }
</sourcecode>
        </figure>
        <t indent="0" pn="section-4.2-9">Example of the unredacted version of an RDAP search response:</t>
        <figure anchor="unredacted-search-response" align="left" suppress-title="false" pn="figure-13">
          <name slugifiedName="name-unredacted-rdap-search-resp">Unredacted RDAP Search Response</name>
          <sourcecode type="json" markers="false" pn="section-4.2-10.1">
  {
    "rdapConformance": [
      "rdap_level_0"
    ],
    "domainSearchResults":[
      {
        "objectClassName": "domain",
        "handle": "ABC121",
        "ldhName": "example1.com",
        "links":[
          {
            "value":"https://example.com/rdap/domain/example1.com",
            "rel":"self",
            "href":"https://example.com/rdap/domain/example1.com",
            "type":"application/rdap+json"
          },
          {
            "value":"https://example.com/rdap/domain/example1.com",
            "rel":"related",
            "href":"https://example.com/rdap/domain/example1.com",
            "type":"application/rdap+json"
          }
        ]
      },
      {
        "objectClassName": "domain",
        "handle": "ABC122",
        "ldhName": "example2.com",
        "links":[
          {
            "value":"https://example.com/rdap/domain/example2.com",
            "rel":"self",
            "href":"https://example.com/rdap/domain/example2.com",
            "type":"application/rdap+json"
          },
          {
            "value":"https://example.com/rdap/domain/example2.com",
            "rel":"related",
            "href":"https://example.com/rdap/domain/example2.com",
            "type":"application/rdap+json"
          }
        ]
      }
    ]
  }
</sourcecode>
        </figure>
        <t indent="0" pn="section-4.2-11">Example of the redacted version of an RDAP search response:</t>
        <figure anchor="redacted-search-response" align="left" suppress-title="false" pn="figure-14">
          <name slugifiedName="name-redacted-rdap-search-respon">Redacted RDAP Search Response</name>
          <sourcecode type="json" markers="false" pn="section-4.2-12.1">
  {
    "rdapConformance": [
      "rdap_level_0",
      "redacted"
    ],
    "domainSearchResults":[
      {
        "objectClassName": "domain",
        "ldhName": "example1.com",
        "links":[
          {
            "value":"https://example.com/rdap/domain/example1.com",
            "rel":"self",
            "href":"https://example.com/rdap/domain/example1.com",
            "type":"application/rdap+json"
          },
          {
            "value":"https://example.com/rdap/domain/example1.com",
            "rel":"related",
            "href":"https://example.com/rdap/domain/example1.com",
            "type":"application/rdap+json"
          }
        ],
        "redacted": [
          {
            "name": {
              "type": "Registry Domain ID"
            },
            "prePath": "$.domainSearchResults[0].handle",
            "pathLang": "jsonpath",
            "method": "removal",
            "reason": {
              "type": "Server policy"
            }
          }
        ]
      },
      {
        "objectClassName": "domain",
        "ldhName": "example2.com",
        "links":[
          {
            "value":"https://example.com/rdap/domain/example2.com",
            "rel":"self",
            "href":"https://example.com/rdap/domain/example2.com",
            "type":"application/rdap+json"
          },
          {
            "value":"https://example.com/rdap/domain/example2.com",
            "rel":"related",
            "href":"https://example.com/rdap/domain/example2.com",
            "type":"application/rdap+json"
          }
        ],
        "redacted": [
          {
            "name": {
              "description": "Registry Domain ID"
            },
            "prePath": "$.domainSearchResults[1].handle",
            "pathLang": "jsonpath",
            "method": "removal",
            "reason": {
              "description": "Server policy"
            }
          }
        ]
      }
    ]
  }
</sourcecode>
        </figure>
      </section>
    </section>
    <section anchor="jsonpath-considerations" numbered="true" removeInRFC="false" toc="include" pn="section-5">
      <name slugifiedName="name-jsonpath-considerations">JSONPath Considerations</name>
      <t indent="0" pn="section-5-1"><xref target="RFC9535" format="default" sectionFormat="of" derivedContent="RFC9535">JSONPath</xref> is the default
      JSON path expression language.  This section includes JSONPath considerations for clients and servers.</t>
      <section anchor="jsonpath-client-considerations" numbered="true" removeInRFC="false" toc="include" pn="section-5.1">
        <name slugifiedName="name-jsonpath-client-considerati">JSONPath Client Considerations</name>
        <t indent="0" pn="section-5.1-1">This section covers considerations for clients that receive responses from
          servers using JSONPath <xref target="RFC9535" format="default" sectionFormat="of" derivedContent="RFC9535"/> to identify
          redacted RDAP fields with the "prePath", "postPath", or "replacementPath" member of redacted objects in the "redacted" member.
        The list of JSONPath client considerations include:</t>
        <ol spacing="compact" indent="adaptive" start="1" type="1" pn="section-5.1-2">
          <li pn="section-5.1-2.1" derivedCounter="1.">When the server is using the <xref target="redaction-removal" format="default" sectionFormat="of" derivedContent="Section 3.1">Redaction by Removal Method</xref> or the <xref target="redaction-replacement-value" format="default" sectionFormat="of" derivedContent="Section 3.4">Redaction by Replacement Value Method</xref> with an alternative field value,
          the JSONPath expression of the "prePath" member will not resolve successfully with the redacted response.
          The client can key off the "name" member for display logic related to the redaction.</li>
        </ol>
      </section>
      <section anchor="jsonpath-server-considerations" numbered="true" removeInRFC="false" toc="include" pn="section-5.2">
        <name slugifiedName="name-jsonpath-server-considerati">JSONPath Server Considerations</name>
        <t indent="0" pn="section-5.2-1">This section covers considerations for servers
        using JSONPath <xref target="RFC9535" format="default" sectionFormat="of" derivedContent="RFC9535"/> to identify
        redacted RDAP fields with the "prePath", "postPath", or "replacementPath" member of redacted objects in the "redacted" member.
        The list of JSONPath considerations include:</t>
        <ol spacing="normal" indent="adaptive" start="1" type="1" pn="section-5.2-2">
          <li pn="section-5.2-2.1" derivedCounter="1.">Use absolute paths with the '$' JSONPath element.  An example is "$.handle" for the "Registry Domain ID" in a lookup response or "$.domainSearchResults[0].handle" in a search response.</li>
          <li pn="section-5.2-2.2" derivedCounter="2.">Validate a JSONPath expression with the non-redacted RDAP response when using the "prePath" member, where evaluating the expression results in returning the redacted field.</li>
          <li pn="section-5.2-2.3" derivedCounter="3.">Reference the removed object field when redacting an entire object by the  <xref target="redaction-removal" format="default" sectionFormat="of" derivedContent="Section 3.1">Redaction by Removal Method</xref>, where all of the object's child fields are explicitly removed.
          An example is "$.entities[?(@.roles[0]=='administrative')]" for the entire "Administrative Contact".</li>
          <li pn="section-5.2-2.4" derivedCounter="4.">Use multiple bases for the redaction of
certain content. For example, if server policy is such that all
administrative-role entities are redacted and all technical-role
entities are redacted, then an entity having both the
administrative role and the technical role could be redacted for
two different reasons. In this situation, a server is required to
include at least one "redacted" entry, but it should consider
including a separate "redacted" entry for each applicable basis
for redaction to clearly document the server policies that
are relevant to redaction in each instance.</li>
          <li pn="section-5.2-2.5" derivedCounter="5.">Reference the removed field when using the <xref target="redaction-removal" format="default" sectionFormat="of" derivedContent="Section 3.1">Redaction by Removal Method</xref>.  An example is "$.handle" for the "Registry Domain ID".</li>
          <li pn="section-5.2-2.6" derivedCounter="6.">Reference index 0 of the jCard property array, which is the jCard "name" property,
          with a filter expression containing the name of the field when redacting a jCard field using the <xref target="redaction-removal" format="default" sectionFormat="of" derivedContent="Section 3.1">Redaction by Removal Method</xref>.
          An example is "$.entities[?(@.roles[0]=='registrant')].vcardArray[1][?(@[0]=='email')]" for the "Registrant Email".</li>
          <li pn="section-5.2-2.7" derivedCounter="7.">Reference the jCard field value or values redacted by array index 3 and greater
          when redacting a jCard field using the <xref target="redaction-empty-value" format="default" sectionFormat="of" derivedContent="Section 3.2">Redaction by Empty Value Method</xref>.
          The jCard property array index 3 and greater contain the property values, where the property values set with an empty value
          are referenced directly in place of the jCard property name.  Servers can then systematically redact the jCard
          field value or values based on the JSONPath expressions, and clients will directly know which jCard property values have been redacted.
          An example is "$.entities[?(@.roles[0]=='registrant')].vcardArray[1][?(@[0]=='fn')][3]" for the "Registrant Name" or "$.entities[?(@.roles[0]=='registrant')].vcardArray[1][?(@[0]=='adr')][3][5]"
          for the "Registrant Postal Code".</li>
          <li pn="section-5.2-2.8" derivedCounter="8.">RDAP extensions should define any special JSONPath considerations required to identify redacted RDAP fields if these considerations are insufficient.</li>
        </ol>
      </section>
    </section>
    <section anchor="iana-considerations" numbered="true" removeInRFC="false" toc="include" pn="section-6">
      <name slugifiedName="name-iana-considerations">IANA Considerations</name>
      <section anchor="rdap-extensions-registry" numbered="true" removeInRFC="false" toc="include" pn="section-6.1">
        <name slugifiedName="name-rdap-extensions-registry">RDAP Extensions Registry</name>
        <t indent="0" pn="section-6.1-1">IANA has registered the following value in the "RDAP
           Extensions" registry:</t>
        <dl spacing="normal" indent="3" newline="false" pn="section-6.1-2">
          <dt pn="section-6.1-2.1">Extension Identifier:</dt>
          <dd pn="section-6.1-2.2">redacted</dd>
          <dt pn="section-6.1-2.3">Registry Operator:</dt>
          <dd pn="section-6.1-2.4">Any</dd>
          <dt pn="section-6.1-2.5">Specification:</dt>
          <dd pn="section-6.1-2.6">RFC 9537</dd>
          <dt pn="section-6.1-2.7">Contact:</dt>
          <dd pn="section-6.1-2.8">IETF &lt;iesg@ietf.org&gt;</dd>
          <dt pn="section-6.1-2.9">Intended Usage:</dt>
          <dd pn="section-6.1-2.10">This extension identifies the redacted fields in an RDAP response.</dd>
        </dl>
      </section>
      <section anchor="json-values-registry" numbered="true" removeInRFC="false" toc="include" pn="section-6.2">
        <name slugifiedName="name-rdap-json-values-registry">RDAP JSON Values Registry</name>
        <t indent="0" pn="section-6.2-1"><xref target="RFC9083" section="10.2" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc9083#section-10.2" derivedContent="RFC9083"/> defines the
        "RDAP JSON Values" registry with predefined Type field values and a
        registration policy of Expert Review <xref target="RFC8126" format="default" sectionFormat="of" derivedContent="RFC8126"/>.
        This specification defines three new Type field
        values that can be used to register predefined redacted name, reason, and
        expression language values. IANA has updated the "RDAP JSON Values" registry to accept these additional Type field values as follows:</t>
        <dl indent="4" newline="false" spacing="normal" pn="section-6.2-2">
          <dt pn="section-6.2-2.1">"redacted name":</dt>
          <dd pn="section-6.2-2.2">Redacted name being registered.  The registered redacted name
          is referenced using the "type" field of the redacted "name" field.</dd>
          <dt pn="section-6.2-2.3">"redacted reason":</dt>
          <dd pn="section-6.2-2.4">Redacted reason being registered.  The registered redacted reason
          is referenced using the "type" field of the redacted "reason" field.</dd>
          <dt pn="section-6.2-2.5">"redacted expression language":</dt>
          <dd pn="section-6.2-2.6">Redacted expression language being registered.  The registered redacted expression
          language is referenced using the "pathLang" field.</dd>
        </dl>
        <t indent="0" pn="section-6.2-3">IANA has also listed this document as a reference for the "RDAP JSON Values" registry and has registered the following value:</t>
        <dl indent="4" newline="false" spacing="normal" pn="section-6.2-4">
          <dt pn="section-6.2-4.1">Value:</dt>
          <dd pn="section-6.2-4.2">jsonpath</dd>
          <dt pn="section-6.2-4.3">Type:</dt>
          <dd pn="section-6.2-4.4">redacted expression language</dd>
          <dt pn="section-6.2-4.5">Description:</dt>
          <dd pn="section-6.2-4.6">JSON path expression language, as defined in RFC 9535.</dd>
          <dt pn="section-6.2-4.7">Registrant:</dt>
          <dd pn="section-6.2-4.8">IETF</dd>
          <dt pn="section-6.2-4.9">Contact Information:</dt>
          <dd pn="section-6.2-4.10">iesg@ietf.org</dd>
          <dt pn="section-6.2-4.11">Reference:</dt>
          <dd pn="section-6.2-4.12">RFC 9537</dd>
        </dl>
      </section>
    </section>
    <section anchor="security-considerations" numbered="true" removeInRFC="false" toc="include" pn="section-7">
      <name slugifiedName="name-security-considerations">Security Considerations</name>
      <t indent="0" pn="section-7-1">The extension described in this document does not provide any security services 
      beyond those described by <xref target="RFC9083" format="default" sectionFormat="of" derivedContent="RFC9083"/>.</t>
    </section>
  </middle>
  <back>
    <displayreference target="I-D.ietf-regext-rdap-jscontact" to="RDAP-JSCONTACT"/>
    <references pn="section-8">
      <name slugifiedName="name-references">References</name>
      <references pn="section-8.1">
        <name slugifiedName="name-normative-references">Normative References</name>
        <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" quoteTitle="true" derivedAnchor="RFC2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t indent="0">In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC6350" target="https://www.rfc-editor.org/info/rfc6350" quoteTitle="true" derivedAnchor="RFC6350">
          <front>
            <title>vCard Format Specification</title>
            <author fullname="S. Perreault" initials="S." surname="Perreault"/>
            <date month="August" year="2011"/>
            <abstract>
              <t indent="0">This document defines the vCard data format for representing and exchanging a variety of information about individuals and other entities (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio clips, etc.). This document obsoletes RFCs 2425, 2426, and 4770, and updates RFC 2739. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6350"/>
          <seriesInfo name="DOI" value="10.17487/RFC6350"/>
        </reference>
        <reference anchor="RFC7095" target="https://www.rfc-editor.org/info/rfc7095" quoteTitle="true" derivedAnchor="RFC7095">
          <front>
            <title>jCard: The JSON Format for vCard</title>
            <author fullname="P. Kewisch" initials="P." surname="Kewisch"/>
            <date month="January" year="2014"/>
            <abstract>
              <t indent="0">This specification defines "jCard", a JSON format for vCard data. The vCard data format is a text format for representing and exchanging information about individuals and other entities, for example, telephone numbers, email addresses, structured names, and delivery addresses. JSON is a lightweight, text-based, language- independent data interchange format commonly used in Internet applications.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7095"/>
          <seriesInfo name="DOI" value="10.17487/RFC7095"/>
        </reference>
        <reference anchor="RFC8126" target="https://www.rfc-editor.org/info/rfc8126" quoteTitle="true" derivedAnchor="RFC8126">
          <front>
            <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
            <author fullname="M. Cotton" initials="M." surname="Cotton"/>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <author fullname="T. Narten" initials="T." surname="Narten"/>
            <date month="June" year="2017"/>
            <abstract>
              <t indent="0">Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA).</t>
              <t indent="0">To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry.</t>
              <t indent="0">This is the third edition of this document; it obsoletes RFC 5226.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="26"/>
          <seriesInfo name="RFC" value="8126"/>
          <seriesInfo name="DOI" value="10.17487/RFC8126"/>
        </reference>
        <reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174" quoteTitle="true" derivedAnchor="RFC8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t indent="0">RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
        <reference anchor="RFC8259" target="https://www.rfc-editor.org/info/rfc8259" quoteTitle="true" derivedAnchor="RFC8259">
          <front>
            <title>The JavaScript Object Notation (JSON) Data Interchange Format</title>
            <author fullname="T. Bray" initials="T." role="editor" surname="Bray"/>
            <date month="December" year="2017"/>
            <abstract>
              <t indent="0">JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Language Standard. JSON defines a small set of formatting rules for the portable representation of structured data.</t>
              <t indent="0">This document removes inconsistencies with other specifications of JSON, repairs specification errors, and offers experience-based interoperability guidance.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="90"/>
          <seriesInfo name="RFC" value="8259"/>
          <seriesInfo name="DOI" value="10.17487/RFC8259"/>
        </reference>
        <reference anchor="RFC9082" target="https://www.rfc-editor.org/info/rfc9082" quoteTitle="true" derivedAnchor="RFC9082">
          <front>
            <title>Registration Data Access Protocol (RDAP) Query Format</title>
            <author fullname="S. Hollenbeck" initials="S." surname="Hollenbeck"/>
            <author fullname="A. Newton" initials="A." surname="Newton"/>
            <date month="June" year="2021"/>
            <abstract>
              <t indent="0">This document describes uniform patterns to construct HTTP URLs that may be used to retrieve registration information from registries (including both Regional Internet Registries (RIRs) and Domain Name Registries (DNRs)) using "RESTful" web access patterns. These uniform patterns define the query syntax for the Registration Data Access Protocol (RDAP). This document obsoletes RFC 7482.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="95"/>
          <seriesInfo name="RFC" value="9082"/>
          <seriesInfo name="DOI" value="10.17487/RFC9082"/>
        </reference>
        <reference anchor="RFC9083" target="https://www.rfc-editor.org/info/rfc9083" quoteTitle="true" derivedAnchor="RFC9083">
          <front>
            <title>JSON Responses for the Registration Data Access Protocol (RDAP)</title>
            <author fullname="S. Hollenbeck" initials="S." surname="Hollenbeck"/>
            <author fullname="A. Newton" initials="A." surname="Newton"/>
            <date month="June" year="2021"/>
            <abstract>
              <t indent="0">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.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="95"/>
          <seriesInfo name="RFC" value="9083"/>
          <seriesInfo name="DOI" value="10.17487/RFC9083"/>
        </reference>
        <reference anchor="RFC9535" target="https://www.rfc-editor.org/info/rfc9535" quoteTitle="true" derivedAnchor="RFC9535">
          <front>
            <title>JSONPath: Query Expressions for JSON</title>
            <author fullname="S. Gössner" initials="S." role="editor" surname="Gössner"/>
            <author fullname="G. Normington" initials="G." role="editor" surname="Normington"/>
            <author fullname="C. Bormann" initials="C." role="editor" surname="Bormann"/>
            <date month="February" year="2024"/>
            <abstract>
              <t indent="0">JSONPath defines a string syntax for selecting and extracting JSON (RFC 8259) values from within a given JSON value.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9535"/>
          <seriesInfo name="DOI" value="10.17487/RFC9535"/>
        </reference>
      </references>
      <references pn="section-8.2">
        <name slugifiedName="name-informative-references">Informative References</name>
        <reference anchor="I-D.ietf-regext-rdap-jscontact" target="https://datatracker.ietf.org/doc/html/draft-ietf-regext-rdap-jscontact-17" quoteTitle="true" derivedAnchor="RDAP-JSCONTACT">
          <front>
            <title>Using JSContact in Registration Data Access Protocol (RDAP) JSON Responses</title>
            <author fullname="Mario Loffredo" initials="M." surname="Loffredo">
              <organization showOnFrontPage="true">IIT-CNR/Registro.it</organization>
            </author>
            <author fullname="Gavin Brown" initials="G." surname="Brown">
              <organization showOnFrontPage="true">CentralNic Group plc</organization>
            </author>
            <date day="7" month="December" year="2023"/>
            <abstract>
              <t indent="0">This document describes an RDAP extension which represents entity contact information in JSON responses using JSContact.</t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-regext-rdap-jscontact-17"/>
          <refcontent>Work in Progress</refcontent>
        </reference>
      </references>
    </references>
    <section anchor="Acknowledgements" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.a">
      <name slugifiedName="name-acknowledgements">Acknowledgements</name>
      <t indent="0" pn="section-appendix.a-1">The authors wish to thank the following persons for their feedback and suggestions:
        <contact fullname="Marc Blanchet"/>,
        <contact fullname="Tom Harrison"/>,
        <contact fullname="Scott Hollenbeck"/>,
        <contact fullname="Pawel Kowalik"/>,
        <contact fullname="Mario Loffredo"/>,
        <contact fullname="Gustavo Lozano"/>,
        <contact fullname="Andy Newton"/>,
        <contact fullname="Jasdip Singh"/>,
    and <contact fullname="Rick Wilhelm"/>.
      </t>
    </section>
    <section anchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.b">
      <name slugifiedName="name-authors-addresses">Authors' Addresses</name>
      <author fullname="James Gould" initials="J." surname="Gould">
        <organization showOnFrontPage="true">VeriSign, Inc.</organization>
        <address>
          <postal>
            <street>12061 Bluemont Way</street>
            <city>Reston</city>
            <region>VA</region>
            <code>20190</code>
            <country>United States of America</country>
          </postal>
          <email>jgould@verisign.com</email>
          <uri>http://www.verisign.com</uri>
        </address>
      </author>
      <author fullname="David Smith" initials="D." surname="Smith">
        <organization showOnFrontPage="true">VeriSign, Inc.</organization>
        <address>
          <postal>
            <street>12061 Bluemont Way</street>
            <city>Reston</city>
            <region>VA</region>
            <code>20190</code>
            <country>United States of America</country>
          </postal>
          <email>dsmith@verisign.com</email>
          <uri>http://www.verisign.com</uri>
        </address>
      </author>
      <author fullname="Jody Kolker" initials="J." surname="Kolker">
        <organization showOnFrontPage="true">GoDaddy Inc.</organization>
        <address>
          <postal>
            <street>14455 N. Hayden Rd., #219</street>
            <city>Scottsdale</city>
            <region>AZ</region>
            <code>85260</code>
            <country>United States of America</country>
          </postal>
          <email>jkolker@godaddy.com</email>
          <uri>http://www.godaddy.com</uri>
        </address>
      </author>
      <author fullname="Roger Carney" initials="R." surname="Carney">
        <organization showOnFrontPage="true">GoDaddy Inc.</organization>
        <address>
          <postal>
            <street>14455 N. Hayden Rd., #219</street>
            <city>Scottsdale</city>
            <region>AZ</region>
            <code>85260</code>
            <country>United States of America</country>
          </postal>
          <email>rcarney@godaddy.com</email>
          <uri>http://www.godaddy.com</uri>
        </address>
      </author>
    </section>
  </back>
</rfc>
