RE: [gnso-whoissurvey-dt] DRAFT - WHOIS Access Response to the GNSO Council On another note

["Michael Young" <myoung@xxxxxxxxxxxxxxxxxxxx>]

Hi all,

We were suppose to review the following document as well for this call.  

www.icann.org/en/committees/security/sac051.pdf

I did not review it as of yet, I am remiss and apologize.  I will do so
before the next call.  

We may need to adjust our terminology  upon review.


Best Regards,

Michael Young
M:+1-647-289-1220


-----Original Message-----
From: owner-gnso-whoissurvey-dt@xxxxxxxxx
[mailto:owner-gnso-whoissurvey-dt@xxxxxxxxx] On Behalf Of Don Blumenthal
Sent: December-05-11 1:00 PM
To: Berry Cobb; gnso-whoissurvey-dt@xxxxxxxxx
Subject: Re: [gnso-whoissurvey-dt] DRAFT - WHOIS Access Response to the GNSO
Council


To take care of some items in advance of the meeting

1) The link to the final RAP report is
http://gnso.icann.org/issues/rap/rap-wg-final-report-29may10-en.pdf. The one
in the draft points to a draft.
2) Should it be "deliverable" in line 1?
3) I think that the two items under Compliance efforts need clarification.
4) I believe that the answer is Yes but, to be sure, is the Whois AOC Review
Team the same as the Whois Policy Review Team? Stop reading if I'm wrong.
Depending on when this response goes to the GNSO, the Team's whois
accessibility recommendations already may be on the record. From what I
understand, the Whois Team report is expected to be out within the next week
and certainly will be filed by the group's end of year deadline.

Talk to you, or at least some, in a couple of hours.

Don

DON M. BLUMENTHAL, Esq.
Senior Policy Advisor
.ORG, The Public Interest Registry
Direct: +1 734 418-8242  | Mobile: +1 202 431-0874 | Skype: donblumenthal |

Find us on Facebook<http://www.facebook.com/pir.org>  |  .ORG
Blog<http://blog.pir.org/> | Flickr<http://flickr.com/orgbuzz> |
YouTube<http://youtube.com/orgbuzz> | Twitter<http://twitter.com/ORGBuzz> |

Confidentiality Note:  Proprietary and confidential to .ORG, The Public
Interest Registry.  If received in error, please inform sender and then
delete.

From: Berry Cobb <mail@xxxxxxxxxxxxx<mailto:mail@xxxxxxxxxxxxx>>
Date: Sat, 3 Dec 2011 02:20:14 -0500
To: "gnso-whoissurvey-dt@xxxxxxxxx<mailto:gnso-whoissurvey-dt@xxxxxxxxx>"
<gnso-whoissurvey-dt@xxxxxxxxx<mailto:gnso-whoissurvey-dt@xxxxxxxxx>>
Subject: [gnso-whoissurvey-dt] DRAFT - WHOIS Access Response to the GNSO
Council

WSWG Team,

Below you find the draft response to the GNSO Council on the RAP
Recommendation for WHOIS Access.  We will review this at out WSWG Call next
Monday.  Thank you.

-----

The WHOIS Survey Working Group (WSWG) would like to thank the GNSO Council
for reaching out to determine if the important issue of WHOIS Accessibility
can be included within the survey being created as a major deliver of the
WSWG's charter.  After careful review of the RAP's recommendation and
supporting information, the WG determined that the RAPWG was only focused on
the policy and compliance aspects with respect to WHOIS Access.  Given the
WSWG's current charter to construct a survey around the technical
requirements of a WHOIS system and infrastructure, the WSWG determined
inclusion of the RAP's recommendation aligned more with policy and thus the
WSWG considered it to be out of scope.  However, given the breadth of WHOIS
experience on the team, the WSWG also wanted to provide the Council will
additional information so that it may make a better informed decision:


.         Since the RAP submitted its final recommendations to the Council,
the ICANN Compliance team efforts have improved and expanded the monitoring
of WHOIS access with the accredited Registrars.

o   Use of the WHOIS Port 43 probe tool and compliance notices sent on
exceeded thresholds

o   Posting of results at least once per year to the Compliance page, with
plans of more frequent reporting intervals

.         At the time of the RAP Recommendations, The WHOIS AoC Review Team
did not exist and ICANN staff understands the topic of WHOIS accessibility
has since been discussed.  However, it is unclear if the output from the AoC
team will translate in to meaningful policy changes, but it is possible that
accessibility recommendations may be submitted.

.         In parallel to RAPWG, RAA Amendments & Law Enforcement efforts
were conducted where sets of issues around WHOIS are in the process of
negotiation or pending PDP.  Such topics include:

o   Service Level Agreements on WHOIS availability

o   Several other issues identified with respect to accuracy. (RAP report
touches on accuracy but at a difference between Port 43 & Web and not as a
function of data accuracy)

For the Council's convenience, the RAP Recommendation and Council's
Resolution are included below.

RAP Recommendation on WHOIS Access
The GNSO should determine what additional research and processes may be
needed to ensure that WHOIS data is accessible in an appropriately reliable,
enforceable, and consistent fashion. The GNSO Council should consider how
such might be related to other WHOIS efforts, such as the upcoming review of
WHOIS policy and implementation required by ICANN's new Affirmation of
Commitments.

Link to Final Report:
https://community.icann.org/download/attachments/8945716/RAPWG+Draft+Final+-
+27+May+2010.doc?version=1&modificationDate=1314119718000


GNSO Resolved
Included in a Resolution to Address Remaining Registration Abuse Policies
Working Group Recommendations:  RESOLVED, in response to WHOIS Access
recommendation #1, the GNSO Council requests the WHOIS Survey Drafting Team
to consider including the issue of WHOIS Access as part of the survey it has
been tasked to develop. If the WHOIS Survey Drafting Team is of the view
that it is not appropriate or timely to include WHOIS Access as part of the
survey, it should inform the GNSO Council accordingly so that the GNSO
Council can determine what next steps, if any, might be appropriate at this
stage in relation to this recommendation.

Link to Resolution Statements of 10/6 Council meeting:
https://community.icann.org/display/gnsocouncilmeetings/Motions+22+September
+2011







Berry Cobb
Internet Corporation for Assigned Names and Numbers (ICANN)

Email: mail@xxxxxxxxxxxxx<mailto:mail@xxxxxxxxxxxxx>
Tel: +1 720 839 5735
Skype ID: berry.cobb