Yes, "occurrence" implies it is triggered any time an inaccuracy exists within the system - this actually sounds wonderful but it is not what they are doing and not the issue, they have in fact often claimed this level of automation and proactive action is outside their role and technically impossible. This is about community input and response to that, we must make it work to that end. On 4/7/13 1:16 PM, Carlton Samuels wrote:
I could live with these changes.
Carlton
============================== Carlton A Samuels Mobile: 876-818-1799 *Strategy, Planning, Governance, Assessment& Turnaround* =============================
On Sat, Apr 6, 2013 at 9:18 PM, Alan Greenberg<alan.greenberg@mcgill.ca>wrote:
The final version has been posted at https://community.icann.org/x/xZRwAg.
The substantive changes made to the previous version are:
- The trigger action requiring Registrar action of inaccurate Whois (Section 5 of the Whois Accuracy Specification) has been slightly changed. We are recommending that replacing the "Upon the occurrence of a" with “Upon a validated report or discovery of a…”, or alternately, "Upon learning of a...".
- Changing the Registrar Whois Port 43 requirement to require Port 43, but only until there are no longer any Thin registries.
Alan
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)