ICANN/GNSO GNSO Email List Archives

[ispcp]


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

AW: [ispcp] RAP "uniformity of reporting" question before Council

  • To: <mike@xxxxxxxxxx>, <ispcp@xxxxxxxxx>
  • Subject: AW: [ispcp] RAP "uniformity of reporting" question before Council
  • From: <KnobenW@xxxxxxxxxx>
  • Date: Wed, 30 May 2012 23:24:09 +0200
  • Accept-language: de-DE
  • Acceptlanguage: de-DE
  • In-reply-to: <4CFE760D-D432-483E-880A-7CC7D8D86C51@haven2.com>
  • List-id: ispcp@xxxxxxxxxxxxxx
  • References: <4CFE760D-D432-483E-880A-7CC7D8D86C51@haven2.com>
  • Sender: owner-ispcp@xxxxxxxxxxxxxx
  • Thread-index: Ac0+ftsIoCvHPOVIRuWwDZVcGt9eVgAK6ZRQ
  • Thread-topic: [ispcp] RAP "uniformity of reporting" question before Council

Thanks Mikey, very helpful



Best regards
Wolf-Ulrich



________________________________
Von: owner-ispcp@xxxxxxxxxxxxxx [mailto:owner-ispcp@xxxxxxxxxxxxxx] Im Auftrag von Mike O'Connor
Gesendet: Mittwoch, 30. Mai 2012 18:06
An: ispcp@xxxxxxxxx
Betreff: [ispcp] RAP "uniformity of reporting" question before Council

hi all,

one of my actions from the call today was to resend the little writeup i did about the Uniformity of Reporting recommendation that's coming up before Council this Friday.  i've attached my (somewhat ragged, apologies).  we ask that you speak up soon if you OPPOSE our supporting the recommendation to find a way to move forward with this initiative.

here's a sketch of some talking points for Wolf during the Council meeting:

-- Proposed next step -- develop ideas on how to move this "meta issue" forward, noting that it may fall outside the PDP process because the issue spans more than just the GNSO

-- Proposed action -- add this issue to the Prague agenda and look for community input and ideas during that session -- with an eye to both the substance of the work and the process by which it is done

-- Proposed position -- don't kill off a broadly supported recommendation simply because it falls outside familiar processes or is too much work.  there are substantial benefits to be gained.  here's a list, based on the WG report;

Improving the "complaint reporting and notification" process for end-users and registrants and the "tracking and compliance" processes by ICANN will provide the following benefits:
* Reduce errors and wasted time for all parties by providing "just in time" education and knowledge to people wanting to report problems
* Improve quality by making it easier to submit a valid complaint
* Reduce the cost of making (and responding to) erroneous complaints, for all parties
* Improving understanding of the limits of ICANN policies and other options to pursue if the issue is not covered by policy
* Improving the effectiveness of policy-compliance activities
* Improving the data available for GNSO (working-group) and ICANN (advisory-group) policy-making
* Improving the data available for compliance activities
* Answering the question "which comes first, policy-process or definitive data describing the problem?" along with suggestions as to how data can be gathered when it hasn't yet been included in the reporting process.

- - - - - - - - -
phone  651-647-6109
fax   866-280-2356
web  http://www.haven2.com
handle OConnorStP (ID for public places like Twitter, Facebook, Google, etc.)



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