idnits 2.17.1 draft-ietf-regext-rdap-redacted-08.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == There is 1 instance of lines with non-ascii characters in the document. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (24 June 2022) is 671 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: '1' on line 1391 -- Looks like a reference, but probably isn't: '0' on line 1392 -- Looks like a reference, but probably isn't: '3' on line 1392 -- Looks like a reference, but probably isn't: '5' on line 1392 == Outdated reference: A later version (-17) exists of draft-ietf-regext-rdap-jscontact-12 == Outdated reference: A later version (-21) exists of draft-ietf-jsonpath-base-05 Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J.G. Gould 3 Internet-Draft D.S. Smith 4 Intended status: Standards Track VeriSign, Inc. 5 Expires: 26 December 2022 J.K. Kolker 6 R.C. Carney 7 GoDaddy Inc. 8 24 June 2022 10 Redacted Fields in the Registration Data Access Protocol (RDAP) Response 11 draft-ietf-regext-rdap-redacted-08 13 Abstract 15 This document describes an RDAP extension for explicitly identifying 16 redacted RDAP response fields, using JSONPath as the default 17 expression language. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at https://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on 26 December 2022. 36 Copyright Notice 38 Copyright (c) 2022 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 43 license-info) in effect on the date of publication of this document. 44 Please review these documents carefully, as they describe your rights 45 and restrictions with respect to this document. Code Components 46 extracted from this document must include Revised BSD License text as 47 described in Section 4.e of the Trust Legal Provisions and are 48 provided without warranty as described in the Revised BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 53 2. Conventions Used in This Document . . . . . . . . . . . . . . 3 54 3. Redaction Methods . . . . . . . . . . . . . . . . . . . . . . 3 55 3.1. Redaction by Removal Method . . . . . . . . . . . . . . . 4 56 3.2. Redaction by Empty Value Method . . . . . . . . . . . . . 5 57 3.3. Redaction by Replacement Value Method . . . . . . . . . . 6 58 4. Redacted RDAP Response . . . . . . . . . . . . . . . . . . . 8 59 4.1. RDAP Conformance . . . . . . . . . . . . . . . . . . . . 8 60 4.2. "redacted" Member . . . . . . . . . . . . . . . . . . . . 8 61 5. JSONPath Considerations . . . . . . . . . . . . . . . . . . . 29 62 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 63 6.1. RDAP Extensions Registry . . . . . . . . . . . . . . . . 31 64 6.2. JSON Values Registry . . . . . . . . . . . . . . . . . . 31 65 7. Implementation Status . . . . . . . . . . . . . . . . . . . . 31 66 7.1. IIT-CNR/Registro.it RDAP Server . . . . . . . . . . . . . 32 67 8. Security Considerations . . . . . . . . . . . . . . . . . . . 32 68 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 32 69 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 32 70 10.1. Informative References . . . . . . . . . . . . . . . . . 32 71 10.2. Normative References . . . . . . . . . . . . . . . . . . 33 72 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 34 73 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 34 74 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 35 75 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 35 76 A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 35 77 A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 36 78 A.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 36 79 A.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 36 80 A.8. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 36 81 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 36 83 1. Introduction 85 This document describes an RDAP extension for explicitly identifying 86 redacted RDAP response fields, using JSONPath as the default 87 expression language. A redacted RDAP field is one that has data 88 removed or replaced in the RDAP response due to server policy, such 89 as the lack of client privilege to receive the field. This extension 90 can be used to identify redacted RDAP fields in any RDAP object 91 class, as defined in [RFC9083], or RDAP fields defined in RDAP 92 extensions. Because an RDAP response may exclude a field due to 93 either the lack of data or based on the lack of RDAP client 94 privileges, this extension is used to explicitly specify which RDAP 95 fields are not included in the RDAP response due to redaction. It 96 thereby provides a capability for disambiguation between redaction 97 and possible other reasons for data or field absence. 99 In [RFC9082] RDAP supports both lookup and search queries, where a 100 lookup query responds with a single object and a search query 101 responds with a list of objects. This document applies to redaction 102 of a single object of a lookup response and in each of the objects of 103 a search response. 105 JSONPath, as defined in [I-D.ietf-jsonpath-base], is used as the 106 default expression language to reference RDAP fields that have been 107 redacted. The redacted JSON fields will either be removed or have 108 empty values in the RDAP response. JSON is defined by [RFC8259]. 110 2. Conventions Used in This Document 112 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 113 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 114 "OPTIONAL" in this document are to be interpreted as described in BCP 115 14 [RFC2119] [RFC8174] when, and only when, they appear in all 116 capitals, as shown here. 118 The JSON examples include extra line breaks and whitespace. For 119 instance, the JSONPath expressions are broken out into multiple lines 120 when required for illustration. 122 3. Redaction Methods 124 Redaction in RDAP can be handled in multiple ways. The use of 125 placeholder text for the values of the RDAP fields, such as the 126 placeholder text "XXXX", MUST NOT be used for redaction. A 127 placeholder text value will not match the format requirements of each 128 of the RDAP fields and provides an inconsistent and unreliable 129 redaction signal. This section covers the redaction methods that can 130 be used with the redaction signaling defined in Section 4.2. 132 RDAP responses, as defined in [RFC9083], include a mix of JSON 133 objects and JSON arrays, where JSON arrays are heavily used for 134 entity objects with jCard [RFC7095]. jCard [RFC7095] is a JSON 135 representation of vCard [RFC6350] that inherits its dependency on 136 arrays. An example is the vCard [RFC6350] "ADR" property / jCard 137 [RFC7095] "adr" property that defines a sequence of address 138 components. According to [RFC6350], when an "ADR" property component 139 value is missing, the associated component separator MUST still be 140 specified. jCard [RFC7095] extends the use of arrays with each 141 individual vCard property being represented by an array of three 142 fixed elements, followed by one or more additional elements. The mix 143 of JSON objects and JSON arrays impacts the methods used for 144 redaction in RDAP. 146 The redaction of RDAP fields fall into the three categories defined 147 in the following sub-sections. 149 3.1. Redaction by Removal Method 151 The Redaction by Removal Method is when the RDAP field is removed 152 from the RDAP response, which is the preferred method. The Redaction 153 by Removal Method can be done for all RDAP response fields other than 154 response fields using the position in an array to signal the redacted 155 field (e.g., the JSON arrays used with jCard [RFC7095]). RDAP 156 extensions such as JSContact in Registration Data Access Protocol 157 (RDAP) JSON Responses [I-D.ietf-regext-rdap-jscontact] do not have a 158 dependency on the use of positional JSON arrays and are therefore 159 suited for the Redaction by Removal Method. 161 When an RDAP object is redacted by removal, all of the RDAP object's 162 child fields are also removed. Only the redacted RDAP object needs 163 to be referenced in the list of redacted fields, as defined in 164 Section 4.2. 166 An example of redacting an RDAP object is removing the administrative 167 contact from the RDAP response and including the following "redacted" 168 member: 170 "redacted": [ 171 { 172 "name": { 173 "type": "Administrative Contact" 174 }, 175 "path": "$.entities[?(@.roles[0]=='administrative')]", 176 "method": "removal" 177 } 178 ] 180 Figure 1: Redacted Administrative Contact 182 The Redaction by Removal Method MUST NOT be used to remove a field 183 using the position in a fixed length array to signal the redacted 184 field. For example, removal of an individual data field in jCard 185 [RFC7095] will result in a non-conformant jCard [RFC7095] array 186 definition. 188 3.2. Redaction by Empty Value Method 190 The Redaction by Empty Value Method is when a redacted field is not 191 removed, but its value is set to an empty value, such as "" for a 192 jCard [RFC7095] Text ("text") property or null for non-Text ("text") 193 properties. The empty jCard [RFC7095] values ("" or null) are 194 referenced in the "redacted" member in place of the jCard [RFC7095] 195 property name, such as referencing the "fn" jCard property value at 196 position 3 instead of referencing the "fn" jCard property name at 197 position 0. The Redaction by Empty Value Method SHOULD be used only 198 when redacting JSON response fields that use the position in an array 199 to signal the redacted field (e.g., jCard [RFC7095] arrays). 200 Optional jCard [RFC7095] properties SHOULD use the Redaction by 201 Removal Method (Section 3.1) to redact the entire property. The 202 required jCard [RFC7095] "fn" property, defined in section 6.2.1 of 203 vCard [RFC6350], MUST use the Redaction by Empty Value Method to 204 redact the property value. Removing the "fn" property would violate 205 vCard [RFC6350] and removing the property value would violate the 206 fixed array positions defined in jCard [RFC7095]. 208 An example of the redacted "fn" jCard property using the Redaction by 209 Empty Value Method: 211 [ 212 "fn", 213 {}, 214 "text", 215 "" 216 ] 218 Figure 2: Redacted "fn" jCard property using Redaction by Empty 219 Value Method 221 An example of the "redacted" member for the redacted "fn" jCard 222 property value, which is array position 3: 224 "redacted": [ 225 { 226 "name": { 227 "type": "Registrant Name" 228 }, 229 "path": "$.entities[?(@.roles[0]=='registrant')]. 230 vcardArray[1][?(@[0]=='fn')][3]", 231 "pathLang": "jsonpath", 232 "method": "emptyValue", 233 "reason": { 234 "type": "Server policy" 235 } 236 } 237 ] 239 Figure 3: Redacted Registrant Name using Array Position 241 3.3. Redaction by Replacement Value Method 243 The Redaction by Replacement Value Method is when a redacted field is 244 not removed, but its value is replaced with a different value, such 245 as protecting the "email" jCard [RFC7095] property value with an 246 anonymized email "text" value or the use of an alternate "uri" value 247 to a web form. Replacing a property value is a form of redaction, 248 since it protects the true property value for privacy reasons. 250 An example of the redacted "email" jCard property using the Redaction 251 by Replacement Value Method with an anonymized email: 253 [ 254 "email", 255 {}, 256 "text", 257 "anonymized123@example.com" 258 ] 260 Figure 4: Redacted "email" jCard property using Redaction by 261 Replacement Value Method with an anonymized email 263 An example of the "redacted" member for the redacted registrant 264 "email" jCard property value with an anonymized "text" value. 266 "redacted": [ 267 { 268 "name": { 269 "type": "Registrant Email" 270 }, 271 "path": "$.entities[?(@.roles[0]=='registrant')]. 272 vcardArray[1][?(@[0]=='email')][3]", 273 "pathLang": "jsonpath", 274 "method": "replacementValue", 275 } 276 ] 278 Figure 5: Redacted Email using Replacement Value with an 279 anonymized "text" value 281 An example of the redacted "email" jCard property using the Redaction 282 by Replacement Value Method with a [RFC8605] "contact-uri" jCard 283 property to a web form: 285 [ 286 "contact-uri", 287 {}, 288 "uri", 289 "https://email.example.com/123" 290 ] 292 Figure 6: Redacted "email" jCard property using Redaction by 293 Replacement Value Method with a "contact-uri" jCard property to a 294 web form 296 An example of the "redacted" member for the redacted registrant 297 "email" jCard property value with a [RFC8605] "contact-uri" jCard 298 property to a web form: 300 "redacted": [ 301 { 302 "name": { 303 "type": "Registrant Email" 304 }, 305 "path": "$.entities[?(@.roles[0]=='registrant')]. 306 vcardArray[1][?(@[0]=='email')][3]", 307 "replacementPath": "$.entities[?(@.roles[0]=='registrant')]. 308 vcardArray[1][?(@[0]=='contact-uri')][3]", 309 "pathLang": "jsonpath", 310 "method": "replacementValue", 311 } 312 ] 313 Figure 7: Redacted Email using Replacement Value with a "contact- 314 uri" jCard property to a web form 316 4. Redacted RDAP Response 318 4.1. RDAP Conformance 320 RDAP responses that contain values described in this document MUST 321 indicate conformance with this specification by including an 322 "rdapConformance" ([RFC9083]) value of "redacted_level_0_3". The 323 "redacted_level_0_3" extension identifier is described in 324 Section 6.1. 326 Example "rdapConformance" member with the redacted extension: 328 "rdapConformance": [ 329 "rdap_level_0", 330 "redacted_level_0_3" 331 ] 333 Figure 8: "rdapConformance" with Redacted Extension 335 4.2. "redacted" Member 337 The "redacted" member MUST be added to the RDAP response when there 338 is one or more redacted fields. The "redacted" member is included as 339 a member of the object class in a lookup response, such as the object 340 classes defined in [RFC9083], and as a member of the object instances 341 in a search response, such as the object instances defined in 342 [RFC9083]. The "redacted" member contains an array of redacted 343 objects with the following child members: 345 "name": A logical name for the redacted field. The logical name 346 used for the redacted field is up to server policy. The logical 347 name is defined using an object with a "type" field denoting a 348 registered redacted name (see Section 6.2) or a "description" 349 field denoting an unregistered redacted name. The registered 350 redacted names and the chosen unregistered names can meet the 351 needs of different RDAP services or industries. 353 "path": The JSON expression references a removed JSON field in the 354 case of Redaction By Removal Method (Section 3.1), an empty field 355 in the case of Redaction by Empty Value Method (Section 3.2), or 356 the field that is replaced in the case of Redaction by 357 Replacement Value Method (Section 3.3). The replaced field can 358 be either removed or empty when using a replacement field 359 referenced by the "replacementPath" member. 361 "replacementPath": OPTIONAL JSON expression of the replacement field 362 of the redacted field with the Redaction by Replacement Value 363 Method (Section 3.3), using the expression language defined by 364 the "pathLang" member. 366 "pathLang": OPTIONAL JSON path expression language used, with the 367 default value of "jsonpath" for JSONPath 368 ([I-D.ietf-jsonpath-base]). Other JSON path expression languages 369 MAY be used based on server policy. 371 "method": OPTIONAL redaction method used; with one of the following 372 values: 374 * "removal" indicating the Redaction By Removal Method 375 (Section 3.1), 377 * "emptyValue" indicating the Redaction by Empty Value Method 378 (Section 3.2), or 380 * "replacementValue" indicating the Redaction by Replacement 381 Value Method. (Section 3.3) 383 The default value is "removal" when not provided. 385 "reason": OPTIONAL human readable reason(s) for the redacted field 386 in the language defined by the [RFC9083] "lang" member. The 387 default language is "en" if the [RFC9083] "lang" member is not 388 specified. The reason is defined using an object with an 389 OPTIONAL "type" field denoting a registered redacted reason (see 390 see Section 6.2) and an OPTIONAL "description" field denoting an 391 unregistered redacted reason. The "description" field MUST NOT 392 be a client processing dependency. 394 Example unredacted version of an RDAP lookup response: 396 { 397 "rdapConformance": [ 398 "rdap_level_0" 399 ], 400 "objectClassName": "domain", 401 "handle": "ABC123", 402 "ldhName": "example.com", 403 "secureDNS": { 404 "delegationSigned": false 405 }, 406 "notices": [ 407 { 408 "title": "Terms of Use", 409 "description": [ 410 "Service subject to Terms of Use." 411 ], 412 "links": [ 413 { 414 "rel": "self", 415 "href": "https://www.example.com/terms-of-use", 416 "type": "text/html", 417 "value": "https://www.example.com/terms-of-use" 418 } 419 ] 420 } 421 ], 422 "nameservers": [ 423 { 424 "objectClassName": "nameserver", 425 "ldhName": "ns1.example.com" 426 }, 427 { 428 "objectClassName": "nameserver", 429 "ldhName": "ns2.example.com" 430 } 431 ], 432 "entities": [ 433 { 434 "objectClassName": "entity", 435 "handle": "123", 436 "roles": [ 437 "registrar" 438 ], 439 "publicIds": [ 440 { 441 "type": "IANA Registrar ID", 442 "identifier": "1" 443 } 444 ], 445 "vcardArray": [ 446 "vcard", 447 [ 448 [ 449 "version", 450 {}, 451 "text", 452 "4.0" 453 ], 454 [ 455 "fn", 456 {}, 457 "text", 458 "Example Registrar Inc." 459 ], 460 [ 461 "adr", 462 {}, 463 "text", 464 [ 465 "", 466 "Suite 100", 467 "123 Example Dr.", 468 "Dulles", 469 "VA", 470 "20166-6503", 471 "US" 472 ] 473 ], 474 [ 475 "email", 476 {}, 477 "text", 478 "contact@organization.example" 479 ], 480 [ 481 "tel", 482 { 483 "type": "voice" 484 }, 485 "uri", 486 "tel:+1.7035555555;ext=1234" 487 ], 488 [ 489 "tel", 490 { 491 "type": "fax" 492 }, 493 "uri", 494 "tel:+1.7035555556" 495 ] 496 ] 497 ], 498 "entities": [ 499 { 500 "objectClassName": "entity", 501 "roles": [ 502 "abuse" 503 ], 504 "vcardArray": [ 505 "vcard", 506 [ 507 [ 508 "version", 509 {}, 510 "text", 511 "4.0" 512 ], 513 [ 514 "fn", 515 {}, 516 "text", 517 "Abuse Contact" 518 ], 519 [ 520 "email", 521 {}, 522 "text", 523 "abuse@organization.example" 524 ], 525 [ 526 "tel", 527 { 528 "type": "voice" 529 }, 530 "uri", 531 "tel:+1.7035555555;ext=1234" 532 ] 533 ] 534 ] 535 } 536 ] 537 }, 538 { 539 "objectClassName": "entity", 540 "handle": "XXXX", 541 "roles": [ 542 "registrant" 543 ], 544 "vcardArray": [ 545 "vcard", 546 [ 547 [ 548 "version", 549 {}, 550 "text", 551 "4.0" 552 ], 554 [ 555 "fn", 556 {}, 557 "text", 558 "Registrant User" 559 ], 560 [ 561 "org", 562 {}, 563 "text", 564 "Example Inc." 565 ], 566 [ 567 "adr", 568 {}, 569 "text", 570 [ 571 "", 572 "Suite 1235", 573 "4321 Rue Somewhere", 574 "Quebec", 575 "QC", 576 "G1V 2M2", 577 "Canada" 578 ] 579 ], 580 [ 581 "email", 582 {}, 583 "text", 584 "registrant.user@example.com" 585 ], 586 [ 587 "tel", 588 { 589 "type": "voice" 590 }, 591 "uri", 592 "tel:+1-555-555-1235;ext=123" 593 ], 594 [ 595 "tel", 596 { 597 "type": "fax" 598 }, 599 "uri", 600 "tel:+1-555-555-5321" 601 ] 603 ] 604 ] 605 }, 606 { 607 "objectClassName": "entity", 608 "handle": "YYYY", 609 "roles": [ 610 "technical" 611 ], 612 "vcardArray": [ 613 "vcard", 614 [ 615 [ 616 "version", 617 {}, 618 "text", 619 "4.0" 620 ], 621 [ 622 "fn", 623 {}, 624 "text", 625 "Technical User" 626 ], 627 [ 628 "org", 629 {}, 630 "text", 631 "Example Inc." 632 ], 633 [ 634 "adr", 635 {}, 636 "text", 637 [ 638 "", 639 "Suite 1234", 640 "4321 Rue Somewhere", 641 "Quebec", 642 "QC", 643 "G1V 2M2", 644 "Canada" 645 ] 646 ], 647 [ 648 "email", 649 {}, 650 "text", 651 "technical.user@example.com" 652 ], 653 [ 654 "tel", 655 { 656 "type": "voice" 657 }, 658 "uri", 659 "tel:+1-555-555-1234;ext=321" 660 ], 661 [ 662 "tel", 663 { 664 "type": "fax" 665 }, 666 "uri", 667 "tel:+1-555-555-4321" 668 ] 669 ] 670 ] 671 }, 672 { 673 "objectClassName": "entity", 674 "handle": "ZZZZ", 675 "roles": [ 676 "administrative" 677 ], 678 "vcardArray": [ 679 "vcard", 680 [ 681 [ 682 "version", 683 {}, 684 "text", 685 "4.0" 686 ], 687 [ 688 "fn", 689 {}, 690 "text", 691 "Administrative User" 692 ], 693 [ 694 "org", 695 {}, 696 "text", 697 "Example Inc." 698 ], 700 [ 701 "adr", 702 {}, 703 "text", 704 [ 705 "", 706 "Suite 1236", 707 "4321 Rue Somewhere", 708 "Quebec", 709 "QC", 710 "G1V 2M2", 711 "Canada" 712 ] 713 ], 714 [ 715 "email", 716 {}, 717 "text", 718 "administrative.user@example.com" 719 ], 720 [ 721 "tel", 722 { 723 "type": "voice" 724 }, 725 "uri", 726 "tel:+1-555-555-1236;ext=789" 727 ], 728 [ 729 "tel", 730 { 731 "type": "fax" 732 }, 733 "uri", 734 "tel:+1-555-555-6321" 735 ] 736 ] 737 ] 738 }, 739 { 740 "objectClassName": "entity", 741 "handle": "WWWW", 742 "roles": [ 743 "billing" 744 ], 745 "vcardArray": [ 746 "vcard", 747 [ 749 [ 750 "version", 751 {}, 752 "text", 753 "4.0" 754 ], 755 [ 756 "fn", 757 {}, 758 "text", 759 "Billing User" 760 ], 761 [ 762 "email", 763 {}, 764 "text", 765 "billing.user@example.com" 766 ] 767 ] 768 ] 769 } 770 ], 771 "events": [ 772 { 773 "eventAction": "registration", 774 "eventDate": "1997-06-03T00:00:00Z" 775 }, 776 { 777 "eventAction": "last changed", 778 "eventDate": "2020-05-28T01:35:00Z" 779 }, 780 { 781 "eventAction": "expiration", 782 "eventDate": "2021-06-03T04:00:00Z" 783 } 784 ], 785 "status": [ 786 "server delete prohibited", 787 "server update prohibited", 788 "server transfer prohibited", 789 "client transfer prohibited" 790 ] 791 } 793 Figure 9: Unredacted RDAP Lookup Response 795 Example redacted version of an RDAP lookup response: 797 { 798 "rdapConformance": [ 799 "rdap_level_0", 800 "redacted_level_0_3" 801 ], 802 "objectClassName": "domain", 803 "ldhName": "example.com", 804 "secureDNS": { 805 "delegationSigned": false 806 }, 807 "notices": [ 808 { 809 "title": "Terms of Use", 810 "description": [ 811 "Service subject to Terms of Use." 812 ], 813 "links": [ 814 { 815 "rel": "self", 816 "href": "https://www.example.com/terms-of-use", 817 "type": "text/html", 818 "value": "https://www.example.com/terms-of-use" 819 } 820 ] 821 } 822 ], 823 "nameservers": [ 824 { 825 "objectClassName": "nameserver", 826 "ldhName": "ns1.example.com" 827 }, 828 { 829 "objectClassName": "nameserver", 830 "ldhName": "ns2.example.com" 831 } 832 ], 833 "entities": [ 834 { 835 "objectClassName": "entity", 836 "handle": "123", 837 "roles": [ 838 "registrar" 839 ], 840 "publicIds": [ 841 { 842 "type": "IANA Registrar ID", 843 "identifier": "1" 844 } 846 ], 847 "vcardArray": [ 848 "vcard", 849 [ 850 [ 851 "version", 852 {}, 853 "text", 854 "4.0" 855 ], 856 [ 857 "fn", 858 {}, 859 "text", 860 "Example Registrar Inc." 861 ], 862 [ 863 "adr", 864 {}, 865 "text", 866 [ 867 "", 868 "Suite 100", 869 "123 Example Dr.", 870 "Dulles", 871 "VA", 872 "20166-6503", 873 "US" 874 ] 875 ], 876 [ 877 "email", 878 {}, 879 "text", 880 "contact@organization.example" 881 ], 882 [ 883 "tel", 884 { 885 "type": "voice" 886 }, 887 "uri", 888 "tel:+1.7035555555" 889 ], 890 [ 891 "tel", 892 { 893 "type": "fax" 895 }, 896 "uri", 897 "tel:+1.7035555556" 898 ] 899 ] 900 ], 901 "entities": [ 902 { 903 "objectClassName": "entity", 904 "roles": [ 905 "abuse" 906 ], 907 "vcardArray": [ 908 "vcard", 909 [ 910 [ 911 "version", 912 {}, 913 "text", 914 "4.0" 915 ], 916 [ 917 "fn", 918 {}, 919 "text", 920 "Abuse Contact" 921 ], 922 [ 923 "email", 924 {}, 925 "text", 926 "abuse@organization.example" 927 ], 928 [ 929 "tel", 930 { 931 "type": "voice" 932 }, 933 "uri", 934 "tel:+1.7035555555" 935 ] 936 ] 937 ] 938 } 939 ] 940 }, 941 { 942 "objectClassName": "entity", 943 "handle": "XXXX", 944 "roles": [ 945 "registrant" 946 ], 947 "vcardArray": [ 948 "vcard", 949 [ 950 [ 951 "version", 952 {}, 953 "text", 954 "4.0" 955 ], 956 [ 957 "fn", 958 {}, 959 "text", 960 "" 961 ], 962 [ 963 "adr", 964 {}, 965 "text", 966 [ 967 "", 968 "", 969 "", 970 "", 971 "QC", 972 "", 973 "Canada" 974 ] 975 ] 976 ] 977 ] 978 }, 979 { 980 "objectClassName": "entity", 981 "handle": "YYYY", 982 "roles": [ 983 "technical" 984 ], 985 "vcardArray": [ 986 "vcard", 987 [ 988 [ 989 "version", 990 {}, 991 "text", 992 "4.0" 993 ], 994 [ 995 "fn", 996 {}, 997 "text", 998 "" 999 ], 1000 [ 1001 "org", 1002 {}, 1003 "text", 1004 "Example Inc." 1005 ], 1006 [ 1007 "adr", 1008 {}, 1009 "text", 1010 [ 1011 "", 1012 "Suite 1234", 1013 "4321 Rue Somewhere", 1014 "Quebec", 1015 "QC", 1016 "G1V 2M2", 1017 "Canada" 1018 ] 1019 ] 1020 ] 1021 ] 1022 } 1023 ], 1024 "events": [ 1025 { 1026 "eventAction": "registration", 1027 "eventDate": "1997-06-03T00:00:00Z" 1028 }, 1029 { 1030 "eventAction": "last changed", 1031 "eventDate": "2020-05-28T01:35:00Z" 1032 }, 1033 { 1034 "eventAction": "expiration", 1035 "eventDate": "2021-06-03T04:00:00Z" 1036 } 1037 ], 1038 "status": [ 1039 "server delete prohibited", 1040 "server update prohibited", 1041 "server transfer prohibited", 1042 "client transfer prohibited" 1043 ], 1044 "redacted": [ 1045 { 1046 "name": { 1047 "type": "Registry Domain ID" 1048 }, 1049 "path": "$.handle", 1050 "pathLang": "jsonpath", 1051 "method": "removal", 1052 "reason": { 1053 "type": "Server policy" 1054 } 1055 }, 1056 { 1057 "name": { 1058 "type": "Registrant Name" 1059 }, 1060 "path": "$.entities[?(@.roles[0]=='registrant')]. 1061 vcardArray[1][?(@[0]=='fn')][3]", 1062 "pathLang": "jsonpath", 1063 "method": "emptyValue", 1064 "reason": { 1065 "type": "Server policy" 1066 } 1067 }, 1068 { 1069 "name": { 1070 "type": "Registrant Organization" 1071 }, 1072 "path": "$.entities[?(@.roles[0]=='registrant')]. 1073 vcardArray[1][?(@[0]=='org')]", 1074 "pathLang": "jsonpath", 1075 "method": "removal", 1076 "reason": { 1077 "type": "Server policy" 1078 } 1079 }, 1080 { 1081 "name": { 1082 "type": "Registrant Street" 1083 }, 1084 "path": "$.entities[?(@.roles[0]=='registrant')]. 1085 vcardArray[1][?(@[0]=='adr')][3][:3]", 1086 "pathLang": "jsonpath", 1087 "method": "emptyValue", 1088 "reason": { 1089 "type": "Server policy" 1090 } 1091 }, 1092 { 1093 "name": { 1094 "type": "Registrant City" 1095 }, 1096 "path": "$.entities[?(@.roles[0]=='registrant')]. 1097 vcardArray[1][?(@[0]=='adr')][3][3]", 1098 "pathLang": "jsonpath", 1099 "method": "emptyValue", 1100 "reason": { 1101 "type": "Server policy" 1102 } 1103 }, 1104 { 1105 "name": { 1106 "type": "Registrant Postal Code" 1107 }, 1108 "path": "$.entities[?(@.roles[0]=='registrant')]. 1109 vcardArray[1][?(@[0]=='adr')][3][5]", 1110 "pathLang": "jsonpath", 1111 "method": "emptyValue", 1112 "reason": { 1113 "type": "Server policy" 1114 } 1115 }, 1116 { 1117 "name": { 1118 "type": "Registrant Email" 1119 }, 1120 "path": "$.entities[?(@.roles[0]=='registrant')]. 1121 vcardArray[1][?(@[0]=='email')]", 1122 "method": "removal", 1123 "reason": { 1124 "type": "Server policy" 1125 } 1126 }, 1127 { 1128 "name": { 1129 "type": "Registrant Phone" 1130 }, 1131 "path": "$.entities[?(@.roles[0]=='registrant')]. 1132 vcardArray[1][?(@[1].type=='voice')]", 1133 "method": "removal", 1134 "reason": { 1135 "type": "Server policy" 1136 } 1137 }, 1138 { 1139 "name": { 1140 "type": "Technical Name" 1141 }, 1142 "path": "$.entities[?(@.roles[0]=='technical')]. 1143 vcardArray[1][?(@[0]=='fn')][3]", 1144 "method": "emptyValue", 1145 "reason": { 1146 "type": "Server policy" 1147 } 1148 }, 1149 { 1150 "name": { 1151 "type": "Technical Email" 1152 }, 1153 "path": "$.entities[?(@.roles[0]=='technical')]. 1154 vcardArray[1][?(@[0]=='email')]", 1155 "method": "removal", 1156 "reason": { 1157 "type": "Server policy" 1158 } 1159 }, 1160 { 1161 "name": { 1162 "type": "Technical Phone" 1163 }, 1164 "path": "$.entities[?(@.roles[0]=='technical')]. 1165 vcardArray[1][?(@[1].type=='voice')]", 1166 "method": "removal", 1167 "reason": { 1168 "type": "Server policy" 1169 } 1170 }, 1171 { 1172 "name": { 1173 "type": "Technical Fax" 1174 }, 1175 "path": "$.entities[?(@.roles[0]=='technical')]. 1176 vcardArray[1][?(@[1].type=='fax')]", 1177 "reason": { 1178 "type": "Client request", 1179 "description": "Client requested the field redacted" 1180 } 1181 }, 1182 { 1183 "name": { 1184 "description": "Administrative Contact" 1185 }, 1186 "path": "$.entities[?(@.roles[0]=='administrative')]", 1187 "method": "removal", 1188 "reason": { 1189 "description": "Refer to the technical contact" 1190 } 1191 } 1192 { 1193 "name": { 1194 "description": "Billing Contact" 1195 }, 1196 "path": "$.entities[?(@.roles[0]=='billing')]", 1197 "method": "removal", 1198 "reason": { 1199 "description": "Refer to the registrant contact" 1200 } 1201 } 1202 ] 1203 } 1205 Figure 10: Redacted RDAP Lookup Response 1207 Example unredacted version of an RDAP search response: 1209 { 1210 "rdapConformance": [ 1211 "rdap_level_0" 1212 ], 1213 "domainSearchResults":[ 1214 { 1215 "objectClassName": "domain", 1216 "handle": "ABC121", 1217 "ldhName": "example1.com", 1218 "links":[ 1219 { 1220 "value":"https://example.com/rdap/domain/example1.com", 1221 "rel":"self", 1222 "href":"https://example.com/rdap/domain/example1.com", 1223 "type":"application/rdap+json" 1224 }, 1225 { 1226 "value":"https://example.com/rdap/domain/example1.com", 1227 "rel":"related", 1228 "href":"https://example.com/rdap/domain/example1.com", 1229 "type":"application/rdap+json" 1230 } 1231 ] 1232 }, 1233 { 1234 "objectClassName": "domain", 1235 "handle": "ABC122", 1236 "ldhName": "example2.com", 1237 "links":[ 1238 { 1239 "value":"https://example.com/rdap/domain/example2.com", 1240 "rel":"self", 1241 "href":"https://example.com/rdap/domain/example2.com", 1242 "type":"application/rdap+json" 1243 }, 1244 { 1245 "value":"https://example.com/rdap/domain/example2.com", 1246 "rel":"related", 1247 "href":"https://example.com/rdap/domain/example2.com", 1248 "type":"application/rdap+json" 1249 } 1250 ] 1251 } 1252 ] 1253 } 1255 Figure 11: Unredacted RDAP Search Response 1257 Example redacted version of an RDAP search response: 1259 { 1260 "rdapConformance": [ 1261 "rdap_level_0", 1262 "redacted_level_0_3" 1263 ], 1264 "domainSearchResults":[ 1265 { 1266 "objectClassName": "domain", 1267 "ldhName": "example1.com", 1268 "links":[ 1269 { 1270 "value":"https://example.com/rdap/domain/example1.com", 1271 "rel":"self", 1272 "href":"https://example.com/rdap/domain/example1.com", 1273 "type":"application/rdap+json" 1274 }, 1275 { 1276 "value":"https://example.com/rdap/domain/example1.com", 1277 "rel":"related", 1278 "href":"https://example.com/rdap/domain/example1.com", 1279 "type":"application/rdap+json" 1280 } 1281 ], 1282 "redacted": [ 1283 { 1284 "name": { 1285 "type": "Registry Domain ID" 1286 }, 1287 "path": "$.domainSearchResults[0].handle", 1288 "pathLang": "jsonpath", 1289 "method": "removal", 1290 "reason": { 1291 "type": "Server policy" 1292 } 1293 } 1294 ] 1295 }, 1296 { 1297 "objectClassName": "domain", 1298 "ldhName": "example2.com", 1299 "links":[ 1300 { 1301 "value":"https://example.com/rdap/domain/example2.com", 1302 "rel":"self", 1303 "href":"https://example.com/rdap/domain/example2.com", 1304 "type":"application/rdap+json" 1306 }, 1307 { 1308 "value":"https://example.com/rdap/domain/example2.com", 1309 "rel":"related", 1310 "href":"https://example.com/rdap/domain/example2.com", 1311 "type":"application/rdap+json" 1312 } 1313 ], 1314 "redacted": [ 1315 { 1316 "name": { 1317 "type": "Registry Domain ID" 1318 }, 1319 "path": "$.domainSearchResults[1].handle", 1320 "pathLang": "jsonpath", 1321 "method": "removal", 1322 "reason": { 1323 "type": "Server policy" 1324 } 1325 } 1326 ] 1327 } 1328 ] 1329 } 1331 Figure 12: Redacted RDAP Search Response 1333 5. JSONPath Considerations 1335 JSONPath [I-D.ietf-jsonpath-base] is the default JSON path expression 1336 language. This section covers considerations for servers using 1337 [I-D.ietf-jsonpath-base] to identify redacted RDAP fields with the 1338 "path" member of redacted objects in the "redacted" member. The list 1339 of JSONPath considerations include: 1341 1. Use absolute paths with the '$' JSONPath element. An example is 1342 "$.handle" for the "Registry Domain ID" in a lookup response or 1343 "$.domainSearchResults[0].handle" in a search response. 1344 2. Validate a JSONPath expression using a non-redacted RDAP 1345 response, where evaluating the expression results in returning 1346 the redacted field. 1347 3. Reference the removed object field when redacting an entire 1348 object by the Redaction by Removal Method (Section 3.1), where 1349 all of the object's child fields are explicitly removed. An 1350 example is "$.entities[?(@.roles[0]=='administrative')]" for the 1351 entire "Administrative Contact". 1353 4. When an entity has multiple roles, include "redacted" members for 1354 each role using the role index. This will result in duplicate 1355 "redacted" members, but will enable the client to treat redaction 1356 consistently when there is a single role per entity or multiple 1357 roles per entity. An example is when the "roles" member has the 1358 value '["registrant","administrative"]', redacting the "name" 1359 member of the entity will result in two "redacted" members with 1360 the JSONPath expressions "$.entities[?(@.roles[0]=='registrant')] 1361 .vcardArray[1][?(@[0]=='fn')][3]" and "$.entities[?(@.roles[1]==' 1362 administrative')].vcardArray[1][?(@[0]=='fn')][3]". 1363 5. When there are multiple entities with the same role, include 1364 "redacted" members for each entity using the entity index instead 1365 of the role. A JSONPath can be created that identifies the 1366 entity based on an index of a role selector nodelist, such as 1367 "$.entities[?(@.roles[0]=='technical')][0]" for the first entity 1368 with the "technical" role. Using the entity index, such as 1369 "$.entities[1]", is simpler and recommended. 1370 6. Reference the removed field when using the Redaction by Removal 1371 Method (Section 3.1). An example is "$.handle" for the "Registry 1372 Domain ID". 1373 7. Reference index 0 of the jCard [RFC7095] property array, which is 1374 the jCard [RFC7095] "name" property, with a filter expression 1375 containing the name of the field, when redacting a jCard 1376 [RFC7095] field using the Redaction by Removal Method 1377 (Section 3.1). An example is "$.entities[?(@.roles[0]=='registra 1378 nt')].vcardArray[1][?(@[0]=='email')]" for the "Registrant 1379 Email". 1380 8. Reference jCard [RFC7095] field value or values redacted by array 1381 index 3 and greater, when redacting a jCard [RFC7095] field using 1382 the Redaction by Empty Value Method (Section 3.2). The jCard 1383 [RFC7095] property array index 3 and greater contain the property 1384 values, where the property values set with an empty value are 1385 referenced directly in place of the jCard [RFC7095] property 1386 name. Servers can then systematically redact jCard [RFC7095] 1387 field value or values based on the JSONPath expressions and 1388 clients will directly know which jCard [RFC7095] property values 1389 have been redacted. An example is "$.entities[?(@.roles[0]=='reg 1390 istrant')].vcardArray[1][?(@[0]=='fn')][3]" for the "Registrant 1391 Name" or "$.entities[?(@.roles[0]=='registrant')].vcardArray[1][? 1392 (@[0]=='adr')][3][5]" for the "Registrant Postal Code". 1393 9. RDAP extensions should define any special JSONPath considerations 1394 required to identify redacted RDAP fields if these considerations 1395 are insufficient. 1397 6. IANA Considerations 1398 6.1. RDAP Extensions Registry 1400 IANA is requested to register the following value in the RDAP 1401 Extensions Registry: 1403 Extension identifier: redacted_level_0_3 1404 Registry operator: Any 1405 Published specification: This document. 1406 Contact: IESG 1407 Intended usage: This extension identifier is used for an 1408 "rdapConformance" value when returning the "redacted" member in 1409 the JSON response. 1411 Extension identifier: redacted 1412 Registry operator: Any 1413 Published specification: This document. 1414 Contact: IESG 1415 Intended usage: This extension prefix identifier is used for the 1416 "redacted" member returned in the JSON response. 1418 6.2. JSON Values Registry 1420 Section 10.2 of [RFC9083] defines the JSON Values Registry with pre- 1421 defined Type field values and the use of the "Expert Review" policy 1422 defined in [RFC8126]. Two new JSON Values Registry Type field values 1423 are used to register pre-defined redacted name and reason values: 1425 "redacted name": Redacted name being registered. The registered 1426 redacted name is referenced using the "type" field of the 1427 redacted "name" field. 1429 "redacted reason": Redacted reason being registered. The registered 1430 redacted reason is referenced using the "type" field of the 1431 redacted "reason" field. 1433 7. Implementation Status 1435 Note to RFC Editor: Please remove this section and the reference to 1436 RFC 7942 [RFC7942] before publication. 1438 This section records the status of known implementations of the 1439 protocol defined by this specification at the time of posting of this 1440 Internet-Draft, and is based on a proposal described in RFC 7942 1441 [RFC7942]. The description of implementations in this section is 1442 intended to assist the IETF in its decision processes in progressing 1443 drafts to RFCs. Please note that the listing of any individual 1444 implementation here does not imply endorsement by the IETF. 1445 Furthermore, no effort has been spent to verify the information 1446 presented here that was supplied by IETF contributors. This is not 1447 intended as, and must not be construed to be, a catalog of available 1448 implementations or their features. Readers are advised to note that 1449 other implementations may exist. 1451 According to RFC 7942 [RFC7942], "this will allow reviewers and 1452 working groups to assign due consideration to documents that have the 1453 benefit of running code, which may serve as evidence of valuable 1454 experimentation and feedback that have made the implemented protocols 1455 more mature. It is up to the individual working groups to use this 1456 information as they see fit". 1458 7.1. IIT-CNR/Registro.it RDAP Server 1460 Responsible Organization: Institute of Informatics and Telematics of 1461 National Research Council (IIT-CNR)/Registro.it 1463 Location: https://rdap.pubtest.nic.it/ 1465 Description: This implementation includes support for RDAP queries 1466 using data from the public test environment of .it ccTLD. The 1467 "redacted" array can be returned in the response to the domain lookup 1468 that is the only available to anonymous users. 1470 Level of Maturity: This is an "alpha" test implementation. 1472 Coverage: This implementation includes all of the features described 1473 in this specification. 1475 Contact Information: Mario Loffredo, mario.loffredo@iit.cnr.it 1477 8. Security Considerations 1479 The server including a redacted signal provides an unauthorized 1480 client additional information related to the existence of data. 1481 Servers MAY exclude the redacted members for RDAP fields that are 1482 considered a privacy issue in providing a data existence signal. 1484 9. Acknowledgements 1486 The authors wish to thank the following persons for their feedback 1487 and suggestions: Marc Blanchet, Scott Hollenbeck, Mario Loffredo, 1488 Gustavo Lozano, and Rick Wilhelm. 1490 10. References 1492 10.1. Informative References 1494 [I-D.ietf-regext-rdap-jscontact] 1495 Loffredo, M. and G. Brown, "Using JSContact in 1496 Registration Data Access Protocol (RDAP) JSON Responses", 1497 Work in Progress, Internet-Draft, draft-ietf-regext-rdap- 1498 jscontact-12, 2 May 2022, 1499 . 1502 [RFC8605] Hollenbeck, S. and R. Carney, "vCard Format Extensions: 1503 ICANN Extensions for the Registration Data Access Protocol 1504 (RDAP)", RFC 8605, DOI 10.17487/RFC8605, May 2019, 1505 . 1507 10.2. Normative References 1509 [I-D.ietf-jsonpath-base] 1510 Gössner, S., Normington, G., and C. Bormann, "JSONPath: 1511 Query expressions for JSON", Work in Progress, Internet- 1512 Draft, draft-ietf-jsonpath-base-05, 25 April 2022, 1513 . 1516 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1517 Requirement Levels", BCP 14, RFC 2119, 1518 DOI 10.17487/RFC2119, March 1997, 1519 . 1521 [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, 1522 DOI 10.17487/RFC6350, August 2011, 1523 . 1525 [RFC7095] Kewisch, P., "jCard: The JSON Format for vCard", RFC 7095, 1526 DOI 10.17487/RFC7095, January 2014, 1527 . 1529 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 1530 Code: The Implementation Status Section", BCP 205, 1531 RFC 7942, DOI 10.17487/RFC7942, July 2016, 1532 . 1534 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 1535 Writing an IANA Considerations Section in RFCs", BCP 26, 1536 RFC 8126, DOI 10.17487/RFC8126, June 2017, 1537 . 1539 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 1540 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 1541 May 2017, . 1543 [RFC8259] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data 1544 Interchange Format", STD 90, RFC 8259, 1545 DOI 10.17487/RFC8259, December 2017, 1546 . 1548 [RFC9082] Hollenbeck, S. and A. Newton, "Registration Data Access 1549 Protocol (RDAP) Query Format", STD 95, RFC 9082, 1550 DOI 10.17487/RFC9082, June 2021, 1551 . 1553 [RFC9083] Hollenbeck, S. and A. Newton, "JSON Responses for the 1554 Registration Data Access Protocol (RDAP)", STD 95, 1555 RFC 9083, DOI 10.17487/RFC9083, June 2021, 1556 . 1558 Appendix A. Change History 1560 A.1. Change from 00 to 01 1562 1. Changed rdapConformance to use pointed "redacted_0.1" value to 1563 support structural changes of the extension up to the target of 1564 "redacted_1.0". 1565 2. Updates based on the Gustavo Lozano feedback: 1566 1. Updated the language to change the special treatment of jCard 1567 to be more generic for future RDAP extensions that leverage 1568 fixed length JSON arrays. 1569 2. Added "RDAP extensions should define any special JSONPath 1570 considerations required to identify redacted RDAP fields if 1571 the these considerations are insufficient." to the JSONPath 1572 Considerations section to generalize it. 1573 3. Updates based on the Marc Blanchet feedback: 1574 1. Added a reference to draft-ietf-regext-rdap-jscontact as an 1575 example of an RDAP extension that is suited for the Redaction 1576 by Removal Method based on the lack of dependency on 1577 positional JSON arrays. 1578 2. Added support for registered and unregistered (free-form) 1579 redaction reasons by changing the "reason" property to be a 1580 JSON object with the "type" and "description" properties. 1581 The "type" property includes registration in the IANA JSON 1582 Values Registry. 1583 3. Added a "JSON Values Registry" section in the IANA 1584 Considersations section to define the "redaction reason" JSON 1585 Values Registry Type values to support the registration of 1586 redaction reasons. 1587 4. Updates based on the Mario Loffredo feedback: 1589 1. Added support for registered and unregistered (free-form) 1590 redaction names by changing the "reason" property to be a 1591 JSON object with the "type" and "description" properties. 1592 The "type" property includes registration in the IANA JSON 1593 Values Registry. 1594 2. Added a "JSON Values Registry" section in the IANA 1595 Considersations section to define the "redaction name" JSON 1596 Values Registry Type values to support the registration of 1597 redaction names. 1598 3. Added a JSONPath Considerations item associated with handling 1599 entities with multiple roles. 1600 4. Added language to restrict the extension to responses. 1602 A.2. Change from 01 to 02 1604 1. Updates to add support for RDAP search responses: 1605 1. Replaced "RDAP lookup response" with "RDAP response" 1606 throughout the draft to expand the scope to include search. 1607 2. Updated the description in the second paragraph of the 1608 Introduction to cover both a lookup response and a search 1609 response. 1610 3. Added an example of the use of an absoluate path for a search 1611 response to the "JSONPath Considerations" section. 1612 4. Added a description of the placement of the "redacted" member 1613 in a lookup response and a search response in the ""redacted" 1614 Member" section. 1615 5. Added an example of an unredacted search response and a 1616 redacted search response in the ""redacted" Member" section. 1618 A.3. Change from 02 to 03 1620 1. Fixed mismatch of the extension identifier, which was updated to 1621 "redacted_0.1" throughout the draft based on feedback from Mario 1622 Loffredo. 1623 2. Added the JSONPath Considerations item associated with redacting 1624 fields for multiple entities with the same role based on 1625 implementation feedback from Mario Loffredo. 1626 3. Added the Implementation Status section that includes the server 1627 implementation by Mario Loffredo. 1628 4. Added use of numbered figures for easy reference for JSON Values 1629 Registry registrations. 1630 5. Updated the example unredacted and redacted lookup responses to 1631 include the "objectClassName" and "handle" members. 1632 6. Changed RFC7482 and RFC7483 references to RFC9082 and RFC9083, 1633 respectively. 1635 A.4. Change from 03 to 04 1636 1. Changed the extension identifier to be "redacted" instead of a 1637 versioned value, which will be leveraged for both the 1638 rdapConformance value and the JSON Values. 1639 2. Changed the RDAP Conformance to be "redacted_level_0.2", which 1640 leveraged the extension identifier as a prefix along with 1641 "_level_" and a pointed version number. The version number will 1642 become "1.0" once the draft passes WGLC. 1643 3. Added the Redaction by Replacement Value Method. 1645 A.5. Change from 04 to 05 1647 1. Update the RDAP Extensions Registry entries to include the 1648 identifier that is used for the RDAP conformance value and to 1649 include the "redacted" prefix indentifier to use for the JSON 1650 response member. 1651 2. Changed the RDAP Conformance to be "redacted_level_0_3", which is 1652 registered in the RDAP Extensions Registry. The RDAP Conformance 1653 value will become "redacted_level_1" once the draft passes WGLC. 1655 A.6. Change from 05 to 06 1657 1. Fixed a couple nits. 1658 2. Updated the Redaction by Replacement Value Method email web form 1659 examples to use the "contact-uri" jCard property of RFC 8605. 1661 A.7. Change from 06 to 07 1663 1. Added the optional replacementPath child member for use with the 1664 Redaction by Replacement Value Method. 1666 A.8. Change from 07 to 08 1668 1. Updates based on the Rick Wilhelm feedback: 1669 1. Updated the definition of a redacted RDAP field in the 1670 Introduction section. 1671 2. Updated the reference to three methods instead of two in the 1672 Redaction Methods section. 1673 3. Created a new paragraph for the example in the Redaction by 1674 Removal Method section. 1675 4. Explicity specified one or more redacted fields for inclusion 1676 of the "redacted" member in the "redacted" Member section. 1677 5. Updated the description of the "method" member in the 1678 "redacted" Member section. 1680 Authors' Addresses 1681 James Gould 1682 VeriSign, Inc. 1683 12061 Bluemont Way 1684 Reston, VA 20190 1685 United States of America 1686 Email: jgould@verisign.com 1687 URI: http://www.verisigninc.com 1689 David Smith 1690 VeriSign, Inc. 1691 12061 Bluemont Way 1692 Reston, VA 20190 1693 United States of America 1694 Email: dsmith@verisign.com 1695 URI: http://www.verisigninc.com 1697 Jody Kolker 1698 GoDaddy Inc. 1699 14455 N. Hayden Rd. #219 1700 Scottsdale, AZ 85260 1701 United States of America 1702 Email: jkolker@godaddy.com 1703 URI: http://www.godaddy.com 1705 Roger Carney 1706 GoDaddy Inc. 1707 14455 N. Hayden Rd. #219 1708 Scottsdale, AZ 85260 1709 United States of America 1710 Email: rcarney@godaddy.com 1711 URI: http://www.godaddy.com