May 2017 - NA-Discuss - lists.icann.org

fucked.nyc
by Joly MacFie Sept. 21, 2018

Sept. 21, 2018

I have just been contacted by the former registrant of fucked.nyc. He registered it via namecheap.com on March 3 2015 and renewed it earlier this week. On Feb 18 2017 he received a msg from Neustar informing him that it had been found non-compliant with the "Seven Word Policy" and deleted. Neustar advised him to contact his registrar for any refunds they might care to make. He contacted NameCheap who essentially said "Forgettaboutit'", despite him pointing out that at no time had he been notified about, or agreed to be bound by, any such policy. Here is NameCheap's response: *Recently, you contacted our Live Chat support regarding deletion offucked.nyc <http://fucked.nyc/>. Feel free to use chat ID XQR-359-35382 for reference.We wanted to let you know, that we have forwarded a suggestion about special notices for .NYC domains to the corresponding team.We are really sorry that you faced such a situation and our replies were not so helpful. Different Registry companies can have different policies in regards of registration their domains and they usually reserve a right to change their requirements or delete domains which do not meet them.This does not happen often, still it is not possible to keep customers informed about all the Registry policies or their changes on a contant manner, to our regret.The amount you paid for the domain purchase was used to register/renew the domain at the .NYC Registry. However, the Registry still can delete domains without any refund if they do not meet their requirements. We are working on improving our performance and hopefully special messages on the site can help to avoid such situations in future.If you have questions or require assistance, feel free to contact us at any time.* The registrant did some further research and surmised that Neustar's vigilance could well be due to my Feb 6 letter <http://isoc-ny.org/misc/2017-02-06_isoc-ny_dotnyc.pdf> pointing out they were asleep at the wheel. It appeared to him the relevant page <http://www.ownit.nyc/restricted-reserved> had been hurriedly updated. Since, apparently he has other domains that might also be considered variants on the 7 words, he got back on to Neustar for some clarification, demanded to see a list. 'Guy' at Neustar support informed him that nothing of the like existed - that it was decided on case by case basis - and to add insult to injury sany deleted restricted names might, as policies change, be released and sold to the highest bidder without any recourse for the original registrant. Thus he writes *I have concluded that all of my .nyc domain names (more than 20) were registered without binding terms or a policy of any kind on behalf of Namecheap or Neustar / ownit.nyc <http://ownit.nyc/>, and I suspect that this is a case for a large percentage of sold .nyc domains. Yet my domain name was seized for a breach of policy, a policy I was never introduced to nor agreed to. If any of my other names are added to the list, they can seize it at any time, despite the fact that I've owned them for 2 years now.* *The greatest ethical concern I have is that an entity operating in this way reserves the right to put a domain name on the reserved/restricted list at any point in time, even if it was already sold and owned for 2 years. I was informed by "Guy" at Neustar support that there is a possibility reserved/restricted names will be released in the future, however they are released back to the public (they go back up for sale), not to the original owner. I have many .nyc domain names that appear as variations according to their list.* *Where is the oversight? Who is to prevent Neustar from seizing a domain name for a period of time, then conveniently releasing it later only to buy it themselves using an alias or through a third party?* <snip> *It just doesn't seem right. If Neustar was unable to properly inform name holders on policy creations, changes, and updates in the past 5 years on city tax dollars, I don't think they should operate for another second. It shouldn't take a committee to generate a "no", I think their shady track record in the past 5 years speaks for itself. And this being New York City, we deserve better.* I've responded to him, noting that 7 word policy is in the City's .nyc contract (appears to have been published April 1 2015, and the .nyc Acceptable Use Policy (which doesn't mention that policy but says they can delete at will) has been public since July 2014. Caveat emptor. I noted that Neustar is obligated to file copies of Registrar Registry Agreements with the City, and he could FOIL it to see if NameCheap had met their obligations. I also opined that, in the unlikely event Neustar were to resell a previously deleted name, they would be asking for trouble, However I think he rightfully raises the wider issue of the right of registrants to be properly informed of restrictive gTLD policies before they put their money on the line. Is there something like that in existing policy? And also, to possibly the wider amusement of schoolboys etc, maybe ICANN or somebody should perhaps maintain a definitive reference of unacceptable variants of the 7 words. joly -- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast -------------------------------------------------------------- -

3 3

Homework from GA: short para about NARALO mtg and ARIN participation.
by avri doria June 6, 2017

June 6, 2017

Hi, Not sure this is where it was to be sent. What I valued most about the NAROLO GA was the chance to see the group functioning as a group. I am an only an alternate member of NARALO for ISOC-NY and often am looking elsewhere in ICANN, so perhaps have missed the degree of cooperation on the list. Seeing what sort of group we may be becoming, over the 3 days, was a good thing. Personally I think more time could have been spent on a smaller number of topics, but in general thought the agenda worked out well and was worth the time. I think the combination with an ARIN meeting was brilliant. The At-Large can give advice on any issue related to ICANN's mission in names or numbers, so it is good to be in understanding with our counterpart in the numbers space, not quite a sub-component of ASO, but virtually, sort of. Personally, though a long time subscriber to the policy list, and previous remote attendee, I was happy to finally participate in one. I appreciate their openness and they way their process allowed for our participation. There is a lot to be learned from the way in which they implement the multistakeholder process that i am still digesting. thanks avri --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

6 5

ARIN Policy on Community Networks
by Glenn McKnight June 4, 2017

June 4, 2017

Hi If you recall at the last ARIN meeting we saw many of our NARALO members comment on the ARIN Community Networks policy See policy document https://www.arin.net/policy/proposals/ARIN_prop_232_orig.html I spoke with ARIN staff about their programs on community networks today and they too are struggling with fee structure for AFRNIC Membership from community networks. Note they fund FIRE which has funded community networks in Uganda and in South Africa. Perhaps we need to ask our community to request financial support for ARIN for community networks as well. Comments? Glenn McKnight mcknight.glenn(a)gmail.com skype gmcknight twitter gmcknight 289-830 6259 .

7 12

NARALO Strategic Plans
by Glenn McKnight May 31, 2017

May 31, 2017

Hi Alfredo is working on the NARALO Strategic Plan and I will ask him to present at one of our meetings the plan and ask for you feedback Alfredo can you please share the link to the google doc for edits Thanks Glenn McKnight mcknight.glenn(a)gmail.com skype gmcknight twitter gmcknight 289-830 6259 .

1 0

CROPP STRATEGIC PLAN
by Glenn McKnight May 31, 2017

May 31, 2017

https://community.icann.org/display/atlarge/Draft+RALO+Outreach+Strategic+P… Please edit the document on our FY 18 plan and be prepared to discuss the plan at our next NARALO meeting in June. Note: Tom please provide more details for inclusion on the cCTLD trip Thanks Glenn McKnight mcknight.glenn(a)gmail.com skype gmcknight twitter gmcknight 289-830 6259 .

1 0

Vote Result: NARALO Election 2017
by ICANN At-Large Staff May 29, 2017

May 29, 2017

Dear All, Kindly note that the vote for the NARALO regional election is now closed. *** QUESTION: Who do you support to become the NARALO ALAC Member for the period of two years beginning at the end of the ICANN60 Meeting in November 2017? Please select one candidate from the list below (listed in alphabetical order of the family name): * John Laprise * Seth Reiss * None of the above As at Poll close: Friday 26 May 2017 23:59 UTC Number of voters: 21 · Group size: 24 · Percentage voted: 87.50 Ranked by votes Rank Options ID Options Votes % 1 15894049 John Laprise 14 66.67 2 15894050 Seth Reiss 7 33.33 3 15894179 None of the above 0 0.00 QUESTION: Which is your preferred candidate to be recommended to the ALAC as the Delegate to the Nominating Committee for the period of one year beginning at the end of the ICANN60 Meeting in November 2017? Please select one candidate from the list below (listed in alphabetical order of the family name): * Judith Hellerstein * Leah Symekher * None of the above As at Poll close: Friday 26 May 2017 23:59 UTC Number of voters: 20 · Group size: 24 · Percentage voted: 83.33 Ranked by votes Rank Options ID Options Votes % 1 15894131 Leah Symekher 13 65.00 2 15894130 Judith Hellerstein 7 35.00 3 15894132 None of the above 0 0.00 *** To confirm: · John Laprise is elected to become the NARALO ALAC Member for the period of two years beginning at the end of the ICANN60 Meeting in November 2017. You may view the result independently under https://www.bigpulse.com/pollresults?code=851273MkJyp2Tz56jiSnTpDrg. · NARALO recommends Leah Symekher to the ALAC as the Delegate to the Nominating Committee for the period of one year beginning at the end of the ICANN60 Meeting in November 2017. You may view the result independently under https://www.bigpulse.com/pollresults?code=85122myfTMqRcBWAZgnJfUhMb. ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

3 2

Congrats
by Glenn McKnight May 28, 2017

May 28, 2017

Dear John and Leah Congrats on the recent election and we look forward to your greater participation with ICANN and NARALO. Please outreach to me to discuss any concerns you may have and we can arrange an onboarding session with you A special thank you to Judith and Seth in stepping up and running for the positions and your dedication to a fair and open electoral process. G Glenn McKnight mcknight.glenn(a)gmail.com skype gmcknight twitter gmcknight 289-830 6259 .

6 9

ICANN News Alert -- Call for Volunteers for the Third Review of ICANN Accountability and Transparency (ATRT3) Extended
by ICANN At-Large Staff May 26, 2017

May 26, 2017

News Alert https://www.icann.org/news/announcement-2017-04-20-en Call for Volunteers for the Third Review of ICANN Accountability and Transparency (ATRT3) Extended 20 April 2017 Represent the global stakeholder community by participating in ICANN Reviews. Apply today to join the team of global experts that will help improve the transparency and accountability of ICANN, and ensure it meets its commitments to the global community. ICANN is seeking volunteers to serve on the third review of ICANN Accountability and Transparency (ATRT3). To apply, please click here [PDF, 2.78 MB] to fill out your Statement of Interest. You may also print out the Statement of Interest form and submit it to reviews(a)icann.org. The ATRT3 Call for Volunteers was scheduled from 31 January to 21 April 2017. This call is now extended to Friday, 2 June 2017, 23:59 UTC to give more time to community members to learn about this review and submit their applications. The goal is to have a pool of diverse and skilled applicants for the SO/ACs to select from. All applications and supporting materials will be published as they are received on the public ATRT3 wiki page. Selection of the Review Team Under the new Bylaws, each SO/AC will have an opportunity to nominate up to seven applicants to serve on the Review Team. An applicant's name will only be presented to the SO/AC identified by the applicant for consideration. After SO/AC nomination process concludes, all nominations will be provided to the SO/AC leaders to conduct the selection process for the Review Team according to the specified expertise and geographic and gender diversity from the nominations received. The Review Team may contain up to 21 members, plus an ICANN Board member (designated by the ICANN Board). For candidates that are seeking a nomination of an SO or AC, we suggest that you communicate and establish a relationship with the leadership of the respective SO or AC. Context and Chronology The specific objectives for the ATRT3 are to review ICANN's execution of its commitment to maintain and improve robust mechanisms for public input, accountability, and transparency to ensure that the outcomes of its decision-making reflect the public interest and are accountable to the Internet community. ICANN's Accountability and Transparency Review originated under the Affirmation of Commitments in 2009. Effective 1 October 2016, ICANN's obligation to conduct this review was incorporated into ICANN Bylaws. The composition of the Review Team will be determined by the ICANN community. For more information, please see Section 4.6. of the ICANN Bylaws. More information is included in the "Background" section below to provide an overview of events leading up to this Call for Volunteers. Scope of the Accountability and Transparency Review ICANN Bylaws mandate that the community conduct a periodic Review to assess how ICANN is executing its commitment to maintain and improve robust mechanisms for public input, accountability, and transparency. This ensures that the outcomes of its decision-making reflect the public interest and are accountable to the Internet community. The focus of the ATRT3 Review may include, but is not limited to, the following: Assess and improve Board governance which may include an ongoing evaluation of Board performance, the Board selection process, the extent to which the Board's composition and allocation structure meets ICANN's present and future needs, and the appeal mechanisms for Board decisions contained in the Bylaws; Assess the role and effectiveness of the GAC's interaction with the Board and with the broader ICANN community; and make recommendations for improvements to ensure effective consideration by ICANN of GAC input on the public policy aspects of the technical coordination of the DNS; Assess and improve the processes by which ICANN receives public input (including adequate explanation of decisions taken and rationale); Assess the extent to which ICANN's decisions are supported and accepted by the Internet community; Assess the policy development process to facilitate enhanced cross community deliberations, and effective and timely policy development; Assess and improve the Independent Review Process; and Assess the extent to which prior Accountability and Transparency Review recommendations have been implemented and the extent to which implementation of such recommendations has resulted in the intended effect. Compensation ATRT3 Review Team members will not receive compensation from ICANN for their service on the team. However, travel, meal and lodging costs for Review Team members who participate in Review Team meetings will be reimbursed upon request in accordance with ICANN's community support travel guidelines. Responsibilities Review Team members will have the following general responsibilities: Participate in creation of charter documents for the Review Team; Select appropriate performance indicators and benchmarks; Consider public, ICANN Organization and Board input and incorporate it as appropriate in Review Team recommendations; Determine whether additional data or analysis is needed and participate in an ensuing provider selection, if necessary, in accordance with ICANN procurement practices; Provide timely updates to the community on the status of the Review Team's work; Analyze findings; Draw conclusions based on findings, develop useful, feasible and implementable recommendations; Provide guidance on prioritization of recommendations and definition of desired outcomes; Post the Draft Report of the Review Team for public review and comment; Deliver a Final Report of the Review Team; Designate several Review Team members to participate in the implementation planning work that follows the delivery of the Final Report of the Review Team and Board action on the recommendations. Skills and Experience To compose a well-balanced Review Team, ICANN seeks members who, in the aggregate, possess the following skills and experience: Performance assessment and audits Good governance and board performance Performance measurement Process improvement Knowledge of recognized frameworks for organizational excellence Principles of accountability applicable to organizations broadly similar to ICANN Expertise with Cross Community Working Group (CCWG) Work Stream 1 (WS1) and Work Stream 2 (WS2) highly desired Desired Attributes Applicants should possess the following professional and personal attributes: Commitment and time to participate Multistakeholder community understanding Team spirit, adaptability, consensus-seeking attitude Willingness to learn Readiness to contribute Capacity to reason objectively, putting aside personal opinions or preconceptions Analytical skills Good communication skills using multiple methods and tools Methodology, Budget and Support ICANN will provide the Review Team with a clearly articulated review budget. Throughout the Review, the Review Team will periodically report on its progress related to planned schedule and budget. ICANN organizational support will be made available to the Review Team. Support will include assistance with project management, organization of work, documents and activities, and sharing of tools and best practices for conducting an effective review. English is the working language of the Review Team. Key communications and documents will be translated in accordance with the ICANN Language Services policies [PDF, 277 KB]. Review Team calls are conducted using Adobe Connect. Background The ICANN Bylaws stipulate that "The Accountability and Transparency Review shall be conducted no less frequently than every five years measured from the date the previous Accountability and Transparency Review Team was convened." That would mean that the Call for Volunteers would take place no later than 4 October 2017. However, prior to the incorporation of this review into the ICANN Bylaws, several events took place leading up to ICANN's current commitment to launch the Call for Volunteers for ATRT3 in January 2017. The information presented below provides an overview of events leading up to this Call for Volunteers. October 2012 – Call for Volunteers for the Second Accountability and Transparency Review Team (ATRT2). February 2013 – ATRT2 Review Team announced. December 2013 – ATRT2 issued Final Report [PDF, 3.46 MB] and Recommendations. June 2014 - the ICANN Board of Directors accepted all twelve ATRT2 Recommendations and directed the President and CEO of ICANN, through his designee(s), to proceed with the implementation - Resolution 2014.06.26.14. For more information on the status of the implementation activities, please visit the ATRT2 Implementation Wiki. July 2015 - In response to community concerns about workload, the ICANN Board delayed the start of ATRT3 until July 2017 via Resolution 2015.07.28.09. Note that under the Affirmation of Commitments, reviews were on a shorter cycle. January 2016 - In response to concerns raised by The National Telecommunications and Information Administration (NTIA) about delaying ATRT3 until July 2017, ICANN noted [PDF, 469 KB] that the Call for Volunteers to form the ATRT3 Review Team will be launched in January 2017. August 2016 - the Co-Chairs of the Cross Community Working Group on ICANN Accountability (CCWG-Accountability) wrote [PDF, 118 KB] to the ICANN Board, presenting possible options of how to combine Work Stream 2 (WS2) efforts and the ATRT3 work, to avoid work duplication. The co-Chairs took this step because as the IANA Stewardship Transition was being completed, and the ICANN Community was engaged in WS2 to address remaining issues, many of the WS2 topics were related to issues expected to be addressed in the ATRT3, i.e. accountability and transparency. October 2016 - The ICANN Board responded. [PDF, 439 KB] that, "It is not up to the Board to dictate the scope of this important community review. While we share the concerns raised of avoiding duplication of resources, it is essential that the broader ICANN community have a voice in determining how the ATRT3 should be scoped in alignment with the Bylaws. The Board and the ICANN Organization stand ready to support the community's direction." December 2016 - the CCWG-Accountability Co-Chairs contacted the SO/AC Chairs, proposing a limited scope for ATRT3 as well as a reduced-size Review Team. They suggested that if the broader ICANN Community agrees with the proposal and rationale, the SO/AC chairs issue a public statement or letter to the ICANN CEO and Board Chair that explains why a limited scope is appropriate and indicate the level of support among the ICANN community for this limitation. ICANN organization is not aware of any collective community response to the CCWG-Accountability Co-Chair's note.

1 0

At-Large Review Final Report Translations Are Published
by ICANN At-Large Staff May 25, 2017

May 25, 2017

Dear All, The Final Report on the Review of the At-Large Community has been translated into Arabic, Chinese, French, Russian, and Spanish. All language versions are available for download here: https://community.icann.org/x/4ifwAw ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org Website: atlarge.icann.org Facebook: facebook.com/icannatlarge Twitter: @ICANNAtLarge

1 0

Naralo election REMINDER
by Glenn McKnight May 24, 2017

May 24, 2017

Hi All We are in the midst of our NARALO election which wraps up on May 26th and you should have received a Big Pulse ballot. Please let me know if you didn't receive the ballot Thanks Glenn McKnight mcknight.glenn(a)gmail.com skype gmcknight twitter gmcknight 289-830 6259 .

1 0