Procedurally, the last official version was what the ICANN Org team published after analysis of the public comments. Kind regards, Laureen Kapin Assistant Director International Consumer Protection Federal Trade Commission Sent via mobile phone Please excuse unintended autocorrect outcomes ________________________________ From: IRT.RegDataPolicy <irt.regdatapolicy-bounces@icann.org> on behalf of Rubens Kuhl via IRT.RegDataPolicy <irt.regdatapolicy@icann.org> Sent: Friday, July 28, 2023 12:50:53 PM To: irt.regdatapolicy@icann.org <irt.regdatapolicy@icann.org> Subject: Re: [IRT.RegDataPolicy] Still concerned about loose ends
Em 28 de jul. de 2023, à(s) 16:39, Kapin, Laureen via IRT.RegDataPolicy <irt.regdatapolicy@icann.org> escreveu:
Hi folks,
I agree with many of the important points that Steve raises, except for one. I don’t think we have in fact yet reached consensus because as Gabe and I indicated in our emails to the IRT, in our view, the circulated language does not match the discussion we had during the last call.
Which is simply wrong, because the language matches what was discussed, since the complex requests issue was not discussed at all. Something can’t match or don’t match a theme that nobody talked to. But if the new language has not reached consensus, which is a decision I’m glad I don’t have to make, we can just go back to the language that reached consensus and was published for public comments. Rubens