This is a repository of JSON file containing examples of RDAP responses using the RFC 9537 redaction extension. It's purpose is to provide examples for testing.

These files may be used in integrated test suites or with the ICANN RDAP Server.

The following describes the files.

This is basically Figure 12 from RFC 9537. It does the following redactions:

1. handle of the domain by removal.
2. name of the registrant by emptyValue
3. organization of the registrant by removal
4. street address of the registrant by emptyValue
5. city of registrant by emptyValue
6. postal code of registrant by emptyValue
7. email of registrant by removal
8. name of the technical contact by emptyValue
9. email of the technical contact by removal
10. phone of the technical contact by removal
11. fax of the technical contact by removal
12. the entire administrative contact by removal
13. the entire billing contact by removal

Same as example-1.net except all the dot notation is replaced with bracket notation.

Same as example-1.net except all emptyValue redactions are change to partialValue redactions.

For each top level entity (i.e. not the registrar abuse):

1. name by emptyValue
2. organization by removal
3. street address by emptyValue
4. city by emptyValue
5. postal code by emptyValue
6. email by removal

For all entities recursively:

1. name by emptyValue
2. organization by removal
3. street address by emptyValue
4. city by emptyValue
5. postal code by emptyValue
6. email by removal

Same structure as example-1.net. This file only has registrant redactions, which are all referenced using a negative index (-2).

1. name of the registrant by emptyValue
2. organization of the registrant by removal
3. street address of the registrant by emptyValue
4. city of registrant by emptyValue
5. postal code of registrant by emptyValue
6. email of registrant by removal

In this file, the registrant, billing, and technical contacts have been merged into one entity and the "registrant" is the first element in the roles array. The file only has the following registrant redactions:

1. name of the registrant by emptyValue
2. organization of the registrant by removal
3. street address of the registrant by emptyValue
4. city of registrant by emptyValue
5. postal code of registrant by emptyValue
6. email of registrant by removal

Same as example-7.net except "registrant" is the last role in the roles array.

This example is a domain with only a registrar entity. It has the following redaction:

1. email of the registrar by replacementValue

Same as example-9.net, however the registrant doesn't have an email address but a contact-uri, and the redaction is a replacementValue of the registrant's email with the contact-uri (from Figure 9 in RFC 9537).

This example is similar to example-9.net, except the email address is an empty string and there are two overlapping redactions:

1. removal of the registrant's email (the entire JSON object).
2. redaction of the registrant's email address by emptyValue (the specific JSON string).

This is the same as example-1.net except all the redactions are illegal in that when they should have a postPath they have a prePath and vice-versa.