ICANN/GNSO GNSO Email List Archives

[dow3tf]


<<< Chronological Index >>>    <<< Thread Index >>>

[dow3tf] apologies: cannot make 22 Sept meeting

  • To: <dow3tf@xxxxxxxxxxxxxx>
  • Subject: [dow3tf] apologies: cannot make 22 Sept meeting
  • From: Barbara Roseman <roseman@xxxxxxxxx>
  • Date: Tue, 21 Sep 2004 23:30:31 -1000
  • Sender: owner-dow3tf@xxxxxxxxxxxxxx

I will unexpectedly be unable to attend the 22 September con call of the Task Force. I will listen to the mp3 as soon as its available.

I would like to point the TF to the discussion of the GNSO Council in KL that addressed the work of the Whois TFs. In particular, Bruce Tonkin gave the following summary of work arising from the TF 3 report. Please forgive all caps, that's how it's presented in the real-time captioning. The full meeting captioning can be found at: http://www.icann.org/meetings/kualalumpur/captioning-gnso-council-20jul04.htm


TASK FORCE 3 REPORT HAS SOME -- CURRENTLY THERE'S SOME RECOMMENDATIONS FOR WORK THAT ICANN SHOULD DO, PARTICULARLY IN THE AREAS OF ENFORCEMENT AND MEASUREMENT AND MONITORING. THERE'S SOME COSTS ASSOCIATED WITH THAT. WE NEED TO REQUEST ICANN TO INDICATE WHAT THE COSTS WOULD BE OF DOING THAT MONITORING. THEN IDENTIFY IS THAT COVERED UNDER THE CURRENT BUDGET OR WOULD ICANN NEED TO SEEK FURTHER FUNDING TO CARRY OUT THAT WORK, AND HOW WOULD THEY FUND THAT, WHERE WOULD THE FUNDING COME FROM.


THERE'S SOME ASPECTS OF EXISTING POLICY. FOR EXAMPLE, REGISTRARS MUST USE REASONABLE EFFORTS TO CONTACT THE REGISTRANT IN THE CASE OF A COMPLAINT ABOUT THE DATA. AND THE TERM "REASONABLE" POTENTIALLY CAN BE DEFINED IN MORE DETAIL, AND ESSENTIALLY PROVIDE SOME MORE CONCRETE OBLIGATIONS ON THE REGISTRAR AS TO WHAT EFFORTS THEY MUST TAKE TO FOLLOW A COMPLAINT.

AGAIN, THAT'S AN ITEM THAT WILL NEED TO BE ANALYZED FROM THE POINT OF VIEW OF HOW DO YOU IMPLEMENT THE ADDITIONAL EFFORTS, WHAT'S THE COST OF IMPLEMENTATION, HOW IS THAT IMPLEMENTATION FUNDED.

THEN IT CAN GO TO ANOTHER LEVEL, AND THIS TASK FORCE 3 ALSO SUGGESTED POTENTIALLY DOING VERIFICATION OF THE DATA, WHICH WOULD BE A NEW OBLIGATION. AND WE NEED TO ASSESS WHAT'S THE COST OF THAT. IF WE WERE DOING DATA VERIFICATION WOULD WE DO IT FOR EVERYBODY OR ONLY IN THE CASE OF A COMPLAINT?

AND SO AGAIN, I NOTE IF IT'S DONE FOR EVERYBODY, THE COST IS INCURRED BY ALL REGISTRANTS. IF IT'S ONLY DONE IN THE CASE OF A COMPLAINT, POTENTIALLY THE COST COULD BE PASSED ON IN THAT INSTANCE.

SO THERE'S A SERIES OF STEPS AGAIN THAT TASK FORCE 3 NEEDS TO LOOK AT BETWEEN WHAT IT'S REQUESTING OF ICANN AND CAN IT BE DONE UNDER THE EXISTING FUNDING, WHAT IT'S REQUESTING OF REGISTRARS, WHAT IS THE COST OF DOING THAT, AND IN ALL OF THESE, BOTH TASK FORCE 1, 2, AND 3, WHAT WE'RE ATTEMPTING TO IDENTIFY IS WHAT SMALL STEPS CAN WE MOVE ON IN A SHORT TIME FRAME, IN A MATTER OF A MONTH OR TWO, WHERE WE GET A TANGIBLE IMPROVEMENT; TO PRIORITIZE OUR ANALYSIS AROUND THOSE SMALL STEPS. ONCE THOSE STEPS ARE TAKEN, WE CAN THEN GO TO THE NEXT STEP AND DO THE ANALYSIS FOR THE NEXT STEP AND SO ON.




<<< Chronological Index >>>    <<< Thread Index >>>