> -----Original Message----- > From: regext <regext-boun...@ietf.org> On Behalf Of Antoin Verschuren > Sent: Monday, April 4, 2022 9:19 AM > To: regext <regext@ietf.org> > Subject: [EXTERNAL] [regext] WG LAST CALL: draft-ietf-regext-rdap-reverse- > search > > 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. > > Dear Working Group, > > The authors of the following working group document have indicated that it > is believed to be ready for submission to the IESG for publication as a > standards track document:
[SAH] I generally agree that the document is ready, but I do have a question that might drive a change or two: Section 2.1 describes search using vcardArray RDAP properties. Will additional/different search properties be required if an RDAP server operator switches from jCard to JSContact? If so, it might be worth noting that these search properties can be affected by RDAP extensions that modify RDAP data structures. It might also mean that the JSContact draft will need to include some text to describe reverse search implications of the data structures it describes. Scott _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
