Hi Gavin, I hope you are well.
Please find ~3 observations/questions below. Regards Zaid The draft states the following in section 1: ".... This document describes how an RDAP server can use "Link" HTTP header fields in responses to HEAD and GET requests to provide RDAP clients with the URL of related RDAP records, without the need for a signalling mechanism for the client to tell the server that it is only interested in retrieving those URLs. " . Note: typo in "signalling" 1- In section 2, titled " RDAP Link Objects ", of draft "draft-brown-rdap-referrals", is the work "Link" supposed to equal to "Links" as it is stated in [https://datatracker.ietf.org/doc/html/rfc9083] section 4.2? The draft states the following in section 1: ".... This document describes how an RDAP server can use "Link" HTTP header fields in responses to HEAD and GET requests to provide RDAP clients with the URL of related RDAP records, without the need for a signalling mechanism for the client to tell the server that it is only interested in retrieving those URLs. " . 2- The "Links" RDAP object, as described in [https://datatracker.ietf.org/doc/html/rfc9083] section 4.2, contains a "value" field and a "href" field. Sometimes these two variables have different values. Does your draft propose sending both in the HTTP header or only one of them? If one of them, which one? Examples: 1- https://datatracker.ietf.org/doc/html/rfc9083 4.2. Links The "links" array is found in data structures to signify links to other resources on the Internet. The relationship of these links is defined by the IANA registry described by [RFC8288]. The following is an example of the link structure: { "value" : "https://example.com/context_uri";, "rel" : "self", "href" : "https://example.com/target_uri";, "hreflang" : [ "en", "ch" ], "title" : "title", "media" : "screen", "type" : "application/json" } 2- https://client.rdap.org/?type=domain&object=alphabet.com&follow-referral=1 Raw Data: { "rdapConformance": [ "rdap_level_0", "icann_rdap_technical_implementation_guide_1", "icann_rdap_response_profile_1" ], "objectClassName": "domain", "handle": "70035_DOMAIN_COM-VRSN", "ldhName": "alphabet.com", "secureDNS": { "delegationSigned": false }, "notices": [ { "title": "Terms of Use", "description": [ "Service subject to Terms of Use." ], "links": [ { "value": "https://rdap.cscglobal.com/dbs/rdap-api/v1/domain/alphabet.com";, "rel": "self", "href": "https://rdap.cscglobal.com/dbs/rdap-api/v1/domain/alphabet.com";, "type": "text/html" } ] }, { "title": "Status Codes", "description": [ "For more information on domain status codes, please visit https://icann.org/epp"; ], "links": [ { "value": "https://rdap.cscglobal.com/dbs/rdap-api/v1/domain/alphabet.com";, "rel": "glossary", "href": "https://icann.org/epp";, "type": "text/html" } ] }, { "title": "RDDS Inaccuracy Complaint Form", "description": [ "URL of the ICANN RDDS Inaccuracy Complaint Form: https://icann.org/wicf"; ], "links": [ { "value": "https://rdap.cscglobal.com/dbs/rdap-api/v1/domain/alphabet.com";, "rel": "help", "href": "https://icann.org/wicf";, "type": "text/html" } ] } ], "nameservers": [ { "objectClassName": "nameserver", "ldhName": "ns2.m-online.net" }, { "objectClassName": "nameserver", "ldhName": "ns3.m-online.net" }, { "objectClassName": "nameserver", "ldhName": "ns4.m-online.net" }, { "objectClassName": "nameserver", "ldhName": "ns.bmw.de" } ] } 3- In example 2 of point 2 above, does the draft propose returning all the links objects as shown in the raw output? On 8/12/25, 10:09 AM, "Gavin Brown" <gavin.br...@icann.org <mailto:gavin.br...@icann.org>> wrote: Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Greetings, I would like to ask the WG to consider adopting this document: http://secure-web.cisco.com/1yj6lugd9dopbtByDVnPNNoslYOGvQ4yhhiGpUrMYdxxj2U6m2-N2CsPhLUedOmeonVLGeUp-CpRO5IJoqsoG9oyg9tx379TrPxcV5oIP-ugZUxUJzIJaO13OzjEqYMVILQThmwFm2mGfsspwLywp315ykq1tGHwhfIils57c-x1dIOaaI21RheXS3jVYT2aW1JMktqFxhvd6TSK33yD7H7q2BVELlNIhWjtv_t3Naq2Mdd56eAhOccfqhw6ytWum1eG_WU0jrlWk7Xf7ksKrKoL2ECs6pmQvQ5YZPjm_8CyYYmUH2hK_X68bXjrcmq-zXlos3XklX45Z9eCYyRoOvQ/http%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-brown-rdap-referrals%2F <http://secure-web.cisco.com/1yj6lugd9dopbtByDVnPNNoslYOGvQ4yhhiGpUrMYdxxj2U6m2-N2CsPhLUedOmeonVLGeUp-CpRO5IJoqsoG9oyg9tx379TrPxcV5oIP-ugZUxUJzIJaO13OzjEqYMVILQThmwFm2mGfsspwLywp315ykq1tGHwhfIils57c-x1dIOaaI21RheXS3jVYT2aW1JMktqFxhvd6TSK33yD7H7q2BVELlNIhWjtv_t3Naq2Mdd56eAhOccfqhw6ytWum1eG_WU0jrlWk7Xf7ksKrKoL2ECs6pmQvQ5YZPjm_8CyYYmUH2hK_X68bXjrcmq-zXlos3XklX45Z9eCYyRoOvQ/http%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-brown-rdap-referrals%2F> Many thanks for your consideration! G. -- Gavin Brown Principal Engineer, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) https://secure-web.cisco.com/1Xe3neT4GDkQx2p36IkDRFX2K5uMmCBKwmtnL76thvrgGGWN4zwyLP2nobip1_54Rlm2Z6oZbkNGyqnI_ljEpxzZ3D25jRaBQrwPdjumjx1E6r0y9dPP54XvZCIHWOWSFNtTffdl3MTCJzArTEup7QJZcpY4YknNn7pltoUyCwI6_V0ybq5nsOGajBqMBThfauvGsAPF8gXIA4kTX1Y3sGIvnwChFTgQ2ZwD61knZ61eyd8UV5BYOdYS8k84GICp8Hl-MeOaXJwpyEdcZPF-XBtZVwFaNt960rxl3dXjQIo6yoB7YmZ7UBUA-FPCAkYDG3LHkGV8pMJf8P8te1LJldw/https%3A%2F%2Fwww.icann.org <https://secure-web.cisco.com/1Xe3neT4GDkQx2p36IkDRFX2K5uMmCBKwmtnL76thvrgGGWN4zwyLP2nobip1_54Rlm2Z6oZbkNGyqnI_ljEpxzZ3D25jRaBQrwPdjumjx1E6r0y9dPP54XvZCIHWOWSFNtTffdl3MTCJzArTEup7QJZcpY4YknNn7pltoUyCwI6_V0ybq5nsOGajBqMBThfauvGsAPF8gXIA4kTX1Y3sGIvnwChFTgQ2ZwD61knZ61eyd8UV5BYOdYS8k84GICp8Hl-MeOaXJwpyEdcZPF-XBtZVwFaNt960rxl3dXjQIo6yoB7YmZ7UBUA-FPCAkYDG3LHkGV8pMJf8P8te1LJldw/https%3A%2F%2Fwww.icann.org> _______________________________________________ regext mailing list -- regext@ietf.org <mailto:regext@ietf.org> To unsubscribe send an email to regext-le...@ietf.org <mailto:regext-le...@ietf.org> _______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
