August 2018 - Ccnso-council

Call for presentations: ccTLD News | ICANN63
by Joke Braeken Aug. 14, 2018

Aug. 14, 2018

Dear All, The call for presentations for the upcoming ccNSO Member Meeting (ccTLD news session) is now open. The ccNSO Meeting Programme Working Group invites you to share your best practices, project solutions, implementations and case studies by presenting at the ccTLD news session, covering for instance recent developments, ccTLD activities and ccTLD management related topics. The ccTLD news session is tentatively scheduled for day 2 of the ccNSO Members Meeting, on Wednesday, 24 October 2018 in Barcelona (ICANN63). If your registry is interested in presenting at the ccTLD News Session, please contact Joke Braeken (joke.braeken(a)icann.org)<mailto:joke.braeken@icann.org)>, no later than Wednesday, 5 September 2018. Candidate presenters are invited to send the following information to Joke Braeken (joke.braeken(a)icann.org)<mailto:joke.braeken@icann.org)>, at their earliest convenience - no later than 5 September 2018. = = = = = * Exact title of your presentation * First name of the presenter * Last name of the presenter * Company/ccTLD of the presenter * Short summary of your presentation (few sentences) Please note: Has your presentation been shown at another industry event? If so, kindly specify where. In order to avoid unnecessary overlap with other meetings, you are kindly encouraged to adopt the presentation to a global audience. = = = = = Each submission is reviewed and evaluated by the ccNSO Meeting Programme Working Group. A short description of the scheduled presentations will be published online, prior to the meeting. Depending on the amount of submissions, the Programme Working Group cannot always guarantee a speaking slot for all volunteers. No interpretation services will be provided during the ccNSO Members meeting, therefore please take into consideration that presentations are to be held in English. The ccNSO Meeting Programme Working Group looks forward to your feedback. Thank you! Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 2

Re: [ccnso-council] [ccnso-members] FW: EPDP Team Request for Early Input
by Stephen Deerhake Aug. 13, 2018

Aug. 13, 2018

El, By way of my replying, your reply to me has made it to the Council list. One major obstacle to any ccNSO participation was the wording of the request for participation, which (and I believe Katrina touched on this previously) basically stated that whoever did participate from another SO/AC would be considered to be representing the views of that SO/AC. This made it very problematic for ccNSO participation, either by a Council member, but especially so for any member of the ccNSO/ccTLD Community. /Stephen On 8/13/18, 04:46, "Dr Eberhard W Lisse" <el(a)lisse.na> wrote: Stephen, I would have rather preferred this to remain on the list, and I am not sure I can post to the council list in the first place. Please ensure that it arrives on the Council list if I can't. My views are, while I most certainly do not have the time, this could have/should have been put to the members/non members and if there was a volunteer or two, Council could have chosen from them, or not; I also do not agree that this decision (not to participate) is one for Council to make, but for the members. Hence I would appreciate if Council put to the members whether to participate and if there was some interest ask members/non members for volunteers. greetings, el On 13/08/2018 01:21, Stephen Deerhake wrote: > (I've brought this discussion off the ccNSO Community list, but have > left it on the ccNSO council list) > > El, > > As a follow-on to Katrina's comments, let me say that first of all > this is not our concern. If the various houses of the GNSO wish to > wage war on themselves over this, then so be it. The US based > intellectual property (IP) lawyers and Law Enforcement (LE) are > screaming for complete access; the European Regulators are telling > them "No Way". The GTLD registries are caught in the middle: > contractually obligated to ICANN, yet under (sometimes extreme) > pressure from the LE/IP community to ignore these Regulators at great > risk to their financial wellbeing due to the potential fines mandated > under GDPR. > > It was also made clear at some point along the way that the EPDP group > was looking for something like 30 hours per week of active > participation from members, which in my mind was basically a means to > stack it with IP interests from large law firms who could task > personnel to this effort. Sorry to be so cynical, but they have a > track record... > > In my view, the effort of this EPDP will ultimately turn out to be "A > bridge too far". And that conclusion is made independent of ICANN's > recent failures in the German courts to maintain the old "whois > order". > > Become an observer if you are interested; it could well be interesting > given the linkage between the EPDP's chair and ICANN. > > As Katrina stated, the Council considered but rejected becoming an > active participant in the GNSO's EPDP. I supported that decision as a > Council member, and I continue to support it. > > Best Regards > /Stephen [...] -- Dr. Eberhard W. Lisse / Obstetrician & Gynaecologist (Saar) el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 / Bachbrecht, Namibia ;____/

1 0

Re: [ccnso-council] [ccnso-members] FW: EPDP Team Request for Early Input
by Katrina Sataki Aug. 13, 2018

Aug. 13, 2018

Eberhard, >while I most certainly do not have the time, this could have/should have been put to the members/non members and if there was a volunteer or two, Council could have chosen from them, or not; >I also do not agree that this decision (not to participate) is one for Council to make, but for the members. As I already noted in my email, we were given 8 days to seek for volunteers and make a decision. "A volunteer or two" would not suffice. We would need two members and at least one alternate in case a member steps down. Again, as I explained in my email, anything our appointed members would say, was supposed to be an official position of the ccNSO, i.e. everything would have to be accepted by ccNSO members. Even European ccTLDs have opposing views on the ways the requirements of the GDRP should be implemented! The Council considered the short timeframe for the decision, the efforts required, possible volunteers among Councillors, scope of the ccNSO policy as defined in the Bylaws, priorities, and the need for volunteers in other efforts of high importance for ccTLDs (e.g. IFR). As the result, in order not to delay the work of the EPDP team, the ccNSO Council decided not to appoint members but encourage ccTLDs to participate individually. Kind regards, ]{atrina On 13/08/2018 01:21, Stephen Deerhake wrote: > (I've brought this discussion off the ccNSO Community list, but have > left it on the ccNSO council list) > > El, > > As a follow-on to Katrina's comments, let me say that first of all > this is not our concern. If the various houses of the GNSO wish to > wage war on themselves over this, then so be it. The US based > intellectual property (IP) lawyers and Law Enforcement (LE) are > screaming for complete access; the European Regulators are telling > them "No Way". The GTLD registries are caught in the middle: > contractually obligated to ICANN, yet under (sometimes extreme) > pressure from the LE/IP community to ignore these Regulators at great > risk to their financial wellbeing due to the potential fines mandated > under GDPR. > > It was also made clear at some point along the way that the EPDP group > was looking for something like 30 hours per week of active > participation from members, which in my mind was basically a means to > stack it with IP interests from large law firms who could task > personnel to this effort. Sorry to be so cynical, but they have a > track record... > > In my view, the effort of this EPDP will ultimately turn out to be "A > bridge too far". And that conclusion is made independent of ICANN's > recent failures in the German courts to maintain the old "whois > order". > > Become an observer if you are interested; it could well be interesting > given the linkage between the EPDP's chair and ICANN. > > As Katrina stated, the Council considered but rejected becoming an > active participant in the GNSO's EPDP. I supported that decision as a > Council member, and I continue to support it. > > Best Regards > /Stephen [...] -- Dr. Eberhard W. Lisse / Obstetrician & Gynaecologist (Saar) el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 / Bachbrecht, Namibia ;____/

1 0

ICANN63 Barcelona: draft high-level ccNSO schedule
by Joke Braeken Aug. 13, 2018

Aug. 13, 2018

Dear All, This is to inform you about the draft high-level ccNSO schedule for the upcoming ICANN Annual General Meeting (ICANN63) in Barcelona. The AGM runs from 20 to 25 October 2018. The final schedule by ICANN will be published on 1 October 2018. * SATURDAY, 20 OCT ‘18: Working Group Meetings * SUNDAY, 21 OCT ‘18: Working Group Meetings, TLD-OPS workshop (disaster recovery and business continuity) * MONDAY, 22 OCT ‘18: Tech Day * TUESDAY, 23 OCT ‘18: ccNSO Members Meeting, Day 1 * WEDNESDAY, 24 OCT ‘18: ccNSO Members Meeting, Day 2. ccNSO Council meeting Links to bookmark now: * ccNSO Members Meeting: https://community.icann.org/display/ccnsowkspc/ICANN63+%7C+ccNSO+Members+Me… (draft schedule available soon, subject to changes) * Tech Day: https://community.icann.org/display/ccnsowkspc/TechDay+Barcelona+-+Agenda (draft agenda to be published once available) * ccNSO remote participation hub: https://community.icann.org/display/ccnsowkspc/ICANN63+-+Barcelona * ICANN62 meeting website: https://meetings.icann.org/en/barcelona63 (including info regarding transportation, venue map etc.) Please make sure to register for the meeting if you are planning to attend. The comprehensive meeting schedule will be posted on 1 October 2018. Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

Re: [ccnso-council] [ccnso-members] FW: EPDP Team Request for Early Input
by Stephen Deerhake Aug. 12, 2018

Aug. 12, 2018

(I've brought this discussion off the ccNSO Community list, but have left it on the ccNSO council list) El, As a follow-on to Katrina's comments, let me say that first of all this is not our concern. If the various houses of the GNSO wish to wage war on themselves over this, then so be it. The US based intellectual property (IP) lawyers and Law Enforcement (LE) are screaming for complete access; the European Regulators are telling them "No Way". The GTLD registries are caught in the middle: contractually obligated to ICANN, yet under (sometimes extreme) pressure from the LE/IP community to ignore these Regulators at great risk to their financial wellbeing due to the potential fines mandated under GDPR. It was also made clear at some point along the way that the EPDP group was looking for something like 30 hours per week of active participation from members, which in my mind was basically a means to stack it with IP interests from large law firms who could task personnel to this effort. Sorry to be so cynical, but they have a track record... In my view, the effort of this EPDP will ultimately turn out to be "A bridge too far". And that conclusion is made independent of ICANN's recent failures in the German courts to maintain the old "whois order". Become an observer if you are interested; it could well be interesting given the linkage between the EPDP's chair and ICANN. As Katrina stated, the Council considered but rejected becoming an active participant in the GNSO's EPDP. I supported that decision as a Council member, and I continue to support it. Best Regards /Stephen On 8/11/18, 13:14, "Dr Eberhard W Lisse" <el(a)lisse.NA> wrote: Katrina, I wasn't thinking of myself. But there are surely some larger ccTLDs which have an opinion and could support the staffing.... greetings, el On 2018-08-11 17:09 , Katrina Sataki wrote: > Eberhard, > > On 12 July, we received a request from the GNSO to appoint two members > and two alternates to the EPDP by 20 July. Members were expected to > have knowledge of GDPR and commit to actively participate in the work > of the EPDP, i.e. devote at least 4-6 hours weekly for at least 6 > months. In addition, it is a requirement of the EPDP charter that > members represent the formal position of their appointing > organization, not individual views or positions. Taking all this into > account, the ccNSO Council decided not to appoint members and > alternates to the EPDP. However, we would like to encourage individual > ccTLDs to share their experience and help the EPDP team to achieve > their goals. > > Please note that the EPDP is open for observers (observers are > subscribed to the mailing list and have the capacity to listen to call > in real-time through an audiocast). > > Kind regards, > > ]{atrina > > > [...] -- Dr. Eberhard W. Lisse / Obstetrician & Gynaecologist (Saar) el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 / Bachbrecht, Namibia ;____/

1 0

Re: [ccnso-council] [ccnso-members] FW: EPDP Team Request for Early Input
by Katrina Sataki Aug. 11, 2018

Aug. 11, 2018

Eberhard, On 12 July, we received a request from the GNSO to appoint two members and two alternates to the EPDP by 20 July. Members were expected to have knowledge of GDPR and commit to actively participate in the work of the EPDP, i.e. devote at least 4-6 hours weekly for at least 6 months. In addition, it is a requirement of the EPDP charter that members represent the formal position of their appointing organization, not individual views or positions. Taking all this into account, the ccNSO Council decided not to appoint members and alternates to the EPDP. However, we would like to encourage individual ccTLDs to share their experience and help the EPDP team to achieve their goals. Please note that the EPDP is open for observers (observers are subscribed to the mailing list and have the capacity to listen to call in real-time through an audiocast). Kind regards, ]{atrina On 10/08/2018, 21:20, "Dr Eberhard W Lisse" <el(a)lisse.NA> wrote: Katrina, would it not be better to have a representative on that Wg? el On 2018-08-10 19:51 , Katrina Sataki wrote: > > > Dear All, > > > > The Expedited Policy Development Process Team of the GNSO is considering > the Temporary Specification for gTLD Registration Data > <https://gnso.icann.org/sites/default/files/file/field-file-attach/temp-spec…> > and is seeking the written opinion on the topic from each Supporting > Organization, Advisory Committee and GNSO Stakeholder Group / > Constituency (see below). > > > > I am sure that individual ccTLDs have a lot of experience with > registration data and GDPR compliance they would like to share with the > team. Although the ccNSO did not appoint official members to the EPDP > team, ccTLDs are welcome to provide advice and support to the team. Any > such feedback from ccTLDs will not be viewed as the official position of > the ccNSO. However, the EPDP team would appreciate if all feedback from > ccTLDs would be consolidated and sent in one package. Therefore, if you > have any comments or suggestions, please send them to > ccnsosecretariat(a)icann.org <mailto:ccnsosecretariat@icann.org> or to me. > > > > Thank you! > > > > Kind regards, > > > > ]{atrina > > > > ----- > > > > *To: ICANN Supporting Organizations / Advisory Committees / GNSO > Stakeholder Groups / GNSO Constituencies * > > * * > > *From: EPDP Team on the Temporary Specification for gTLD Registration Data * > > * * > > *Subject: EPDP Team Request for Early Input* > > * * > > > > 1 August 2018 > > > > Dear Community Leader: > > > > I am writing you on behalf of the Expedited Policy Development Process > Team that is considering the Temporary Specification for gTLD > Registration Data > <https://gnso.icann.org/sites/default/files/file/field-file-attach/temp-spec…>. > In accordance with the GNSO Policy Development Process, we are seeking > the written opinion on the topic from each Supporting Organization, > Advisory Committee and GNSO Stakeholder Group / Constituency. While > every Supporting Organisation and Stakeholder Group has been invited to > participate in the discussion, we still wish to comply of this Policy > Develop Process requirement and afford you the opportunity to make a > written submission. > > > > As this is an /expeditedpolicy development > <https://www.icann.org/resources/pages/governance/bylaws-en/#annexA1>/, > we are going to take advantage of the tighter timeframe afforded to us > and require the input in 21 days from today, i.e., on 22 August. We do > so because: > > 1. the working group will start substantive discussions immediately, so > timely input is required if it is to be considered, > 2. every ICANN stakeholder group has been afforded the opportunity to > participate in the working group so the opportunity for this early > input is somewhat redundant, and > 3. we will provide an additional opportunity with a lengthier timeframe > for written input on more complex issues such as the provision of > access to full non-public registration data. > > > > There are three deliverables set out in the GNSO Charter > <https://gnso.icann.org/sites/default/files/file/field-file-attach/temp-spec…>, > that we will work on and deliver in order: > > * a triage document of the Temporary Specification, which includes > items that have the Full Consensus support of the EPDP Team that > these should be adopted as is. > * an Initial Report which will include the items that received full > consensus support per the triage document as well as all other items > of the Temporary Specification (not including the Annex) that were > considered and deliberated upon > * an Initial Report outlining a proposed model of a system for > providing accredited access to non-public registration data > > > > Given the tight timeframe, it is recommended that you focus your early > input focus on the first two deliverables only. (As stated above, we > will provide an opportunity for input on the more complex issue of > “access” in the near future.) > > > > To make the most effective comment and have it folded cleanly and > clearly into the team’s documentation library, your written response > should: > > 1. Clearly identify the section of the Temporary Specification > <https://www.icann.org/resources/pages/gtld-registration-data-specs-en/#temp…> > on which you are commenting, either by line numbers or paragraph. > 2. Then clearly state whether your respective group: > 1. Supports that section as is (where clearly labelled rationale is > optional), > 2. Supports that section with modification with substitute language > provided and clearly labeled rationale, or > 3. Supports the elimination of the section with clearly labeled > rationale > > > > Comments without clearly labelled rationale will probably not add much > to the discussion as we are attempted to develop consensus through > collaboration and not voting. If you do not comment on a specific > section of the document, that absence will not be taken as assent or any > other opinion. > > > > Of course, you are welcome to provide any other input that you deem > helpful in facilitating the EPDP Team’s deliberations, but as to the > immediate deliverables of the working group, your input on the questions > outlined above will be most valuable. > > > > Please submit your response to gnso-secs(a)icann.org > <mailto:gnso-secs@icann.org>. Timely input will be summarized in a > document and provided to the team. Input received after the due date may > be introduced into the discussion by you stakeholder group > representative, ICANN staff support or me as the pertinent topic arises. > > > > Thank you very much and I look forward to receiving your input. You can > contact me anytime via email (kurt(a)kjpritz.com) > <mailto:kurt@kjpritz.com%29>. > > > > On behalf of the EPDP Team, > > > > Kurt Pritz > > EPDP Team Chair > > * * > > *Background* > > > > On 17 May 2018, the ICANN Board of Directors (ICANN Board) adopted the > Temporary Specification for generic top-level domain (gTLD) Registration > Data > <file:///Volumes/GoogleDrive/My%20Drive/Migrated%20DropBox%20Files/Documents/EPDP%20Temp%20Spec/System%20for%20Standardized%20Access%20to%20Non-Public%20Registration%20Data> > (“Temporary Specification”) pursuant to the procedures for the > establishment of temporary policies in ICANN’s agreements with Registry > Operators and Registrars (“Contracts”). The Temporary Specification > provides modifications to existing requirements in the Registrar > Accreditation and Registry Agreements to help bring them into compliance > with the European Union’s General Data Protection Regulation (“GDPR”). > Per the procedure for Temporary Policies as outlined in the Contracts, > following adoption of the temporary specification, the Board “shall > immediately implement the Consensus Policy development process set forth > in ICANN’s Bylaws”. Per the requirements of the procedure for Temporary > Policies, this Consensus Policy development process on the temporary > specification would need to be carried out within a one-year period as > the Temporary Specification can only remain in force for up to 1 year, > from the effective date of 25 May 2018. > > > > At its meeting on 19 July 2018, the GNSO Council initiated an Expedited > Policy Development Process on the Temporary Specification for gTLD > Registration Data and adopted the EPDP Team Charter > <https://gnso.icann.org/sites/default/files/file/field-file-attach/temp-spec…>. > The charter outlines a number of questions that the EPDP Team is > expected to answer. The scope of the EPDP Team’s efforts includes > confirming, or not, the Temporary Specification by 25 May 2019 (the date > the Temporary Specification will expire). Additionally, the proposed > scope includes discussion of a standardized access model to nonpublic > registration data; however, the discussion of a standardized access > model will occur only after the EPDP Team has comprehensively answered a > series of “gating questions”, which have been specified in the EPDP > Team’s Charter. > > > > > > > > _______________________________________________ > Ccnso-members mailing list > Ccnso-members(a)icann.org > https://mm.icann.org/mailman/listinfo/ccnso-members > -- Dr. Eberhard W. Lisse / Obstetrician & Gynaecologist (Saar) el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 / Bachbrecht, Namibia ;____/

1 0

FW: EPDP Team Request for Early Input
by Katrina Sataki Aug. 10, 2018

Aug. 10, 2018

Dear All, The Expedited Policy Development Process Team of the GNSO is considering the Temporary Specification for gTLD Registration Data and is seeking the written opinion on the topic from each Supporting Organization, Advisory Committee and GNSO Stakeholder Group / Constituency (see below). I am sure that individual ccTLDs have a lot of experience with registration data and GDPR compliance they would like to share with the team. Although the ccNSO did not appoint official members to the EPDP team, ccTLDs are welcome to provide advice and support to the team. Any such feedback from ccTLDs will not be viewed as the official position of the ccNSO. However, the EPDP team would appreciate if all feedback from ccTLDs would be consolidated and sent in one package. Therefore, if you have any comments or suggestions, please send them to ccnsosecretariat(a)icann.org or to me. Thank you! Kind regards, ]{atrina ----- To: ICANN Supporting Organizations / Advisory Committees / GNSO Stakeholder Groups / GNSO Constituencies From: EPDP Team on the Temporary Specification for gTLD Registration Data Subject: EPDP Team Request for Early Input 1 August 2018 Dear Community Leader: I am writing you on behalf of the Expedited Policy Development Process Team that is considering the Temporary Specification for gTLD Registration Data. In accordance with the GNSO Policy Development Process, we are seeking the written opinion on the topic from each Supporting Organization, Advisory Committee and GNSO Stakeholder Group / Constituency. While every Supporting Organisation and Stakeholder Group has been invited to participate in the discussion, we still wish to comply of this Policy Develop Process requirement and afford you the opportunity to make a written submission. As this is an expedited policy development, we are going to take advantage of the tighter timeframe afforded to us and require the input in 21 days from today, i.e., on 22 August. We do so because: the working group will start substantive discussions immediately, so timely input is required if it is to be considered, every ICANN stakeholder group has been afforded the opportunity to participate in the working group so the opportunity for this early input is somewhat redundant, and we will provide an additional opportunity with a lengthier timeframe for written input on more complex issues such as the provision of access to full non-public registration data. There are three deliverables set out in the GNSO Charter, that we will work on and deliver in order: a triage document of the Temporary Specification, which includes items that have the Full Consensus support of the EPDP Team that these should be adopted as is. an Initial Report which will include the items that received full consensus support per the triage document as well as all other items of the Temporary Specification (not including the Annex) that were considered and deliberated upon an Initial Report outlining a proposed model of a system for providing accredited access to non-public registration data Given the tight timeframe, it is recommended that you focus your early input focus on the first two deliverables only. (As stated above, we will provide an opportunity for input on the more complex issue of “access” in the near future.) To make the most effective comment and have it folded cleanly and clearly into the team’s documentation library, your written response should: Clearly identify the section of the Temporary Specification on which you are commenting, either by line numbers or paragraph. Then clearly state whether your respective group: Supports that section as is (where clearly labelled rationale is optional), Supports that section with modification with substitute language provided and clearly labeled rationale, or Supports the elimination of the section with clearly labeled rationale Comments without clearly labelled rationale will probably not add much to the discussion as we are attempted to develop consensus through collaboration and not voting. If you do not comment on a specific section of the document, that absence will not be taken as assent or any other opinion. Of course, you are welcome to provide any other input that you deem helpful in facilitating the EPDP Team’s deliberations, but as to the immediate deliverables of the working group, your input on the questions outlined above will be most valuable. Please submit your response to gnso-secs(a)icann.org. Timely input will be summarized in a document and provided to the team. Input received after the due date may be introduced into the discussion by you stakeholder group representative, ICANN staff support or me as the pertinent topic arises. Thank you very much and I look forward to receiving your input. You can contact me anytime via email (kurt(a)kjpritz.com) On behalf of the EPDP Team, Kurt Pritz EPDP Team Chair Background On 17 May 2018, the ICANN Board of Directors (ICANN Board) adopted the Temporary Specification for generic top-level domain (gTLD) Registration Data (“Temporary Specification”) pursuant to the procedures for the establishment of temporary policies in ICANN’s agreements with Registry Operators and Registrars (“Contracts”). The Temporary Specification provides modifications to existing requirements in the Registrar Accreditation and Registry Agreements to help bring them into compliance with the European Union’s General Data Protection Regulation (“GDPR”). Per the procedure for Temporary Policies as outlined in the Contracts, following adoption of the temporary specification, the Board “shall immediately implement the Consensus Policy development process set forth in ICANN’s Bylaws”. Per the requirements of the procedure for Temporary Policies, this Consensus Policy development process on the temporary specification would need to be carried out within a one-year period as the Temporary Specification can only remain in force for up to 1 year, from the effective date of 25 May 2018. At its meeting on 19 July 2018, the GNSO Council initiated an Expedited Policy Development Process on the Temporary Specification for gTLD Registration Data and adopted the EPDP Team Charter. The charter outlines a number of questions that the EPDP Team is expected to answer. The scope of the EPDP Team’s efforts includes confirming, or not, the Temporary Specification by 25 May 2019 (the date the Temporary Specification will expire). Additionally, the proposed scope includes discussion of a standardized access model to nonpublic registration data; however, the discussion of a standardized access model will occur only after the EPDP Team has comprehensively answered a series of “gating questions”, which have been specified in the EPDP Team’s Charter.

1 0

Call for Expression of Interest: IANA Naming Function Review Team (IFRT).
by Kimberly Carlson Aug. 10, 2018

Aug. 10, 2018

Dear All, The ccNSO Secretariat is launching a call for Expression of Interest (EoI) for 3 members of the IANA Naming Function Review Team (IFRT). The call for EoI will be open today Friday, 10 August 2018 and will close on Friday, 24 August 2018 (17:00 UTC). If interested, please send the following documents to: ccnsosecretariat(a)icann.org<mailto:ccnsosecretariat@icann.org> no later than Friday 24 August 2018 (17:00 UTC). 1. Completed application form (see attachment), both the Word doc and fillable pdf is included for your convenience. 2. Your resume, curriculum vitae, or biography. 3. If applicable, a letter of support from your employer in respect to the required time commitment to participate actively in the IFRT. Composition of the review team The three ccNSO appointed members to the IFRT are to be appointed in accordance with the rules and procedures of the ccNSO and must be from different ICANN regions. The composition of the review team, which is specified by the Bylaws, includes, among others: (a) Two representatives appointed by the ccNSO from its ccTLD registry operator representatives; (b) One non-ccNSO ccTLD representative who is associated with a ccTLD registry operator that is not a representative of the ccNSO, appointed by the ccNSO; it is strongly recommended that the ccNSO consult with the regional ccTLD organizations (i.e., AfTLD, APTLD, LACTLD, and CENTR) in making its appointment; Further details on the candidate qualification requirements are included at the bottom of this email. Next Steps Once we have received your intent to volunteers as IFRT member, the ccNSO Secretariat will send you a link to an online Acknowledgement of Terms Form. Via this form, you consent to ICANN processing data in order to add you as a member of the IFRT and its mailing list(s). The form explains the information ICANN will process to administer your participation in the IFRT and how the information will be used this purpose. It also describes the rights you have regarding your information. (Terms of Service<https://www.icann.org/privacy/tos>) Background As this is the first time the ccNSO needs to select members to the IFRT, to ensure that all requirements set in the Bylaws are met, the ccNSO Council agreed to follow the procedure as described in a temporary guideline (attached). The purpose of this temporary guideline is to document processes and procedures pertaining to the ccNSO Council's responsibilities with respect to the appointment of members to the IFRT and to serve as a basis for a guideline for future appointments. Links/Attachments * Temporary ccNSO Guideline ccNSO Actions with Respect to the Selection of ccNSO Appointed Members to the IFRT * IFRT membership application Form (Word and PDF) Thank you. Best regards, Kim Carlson IFRT Candidate Qualification Requirements Skill set and experience * Direct experience and knowledge of the IANA naming functions. * Understanding the purpose of the IFR. * Analytical skills, ability to interpret quantitative and qualitative evidence, and the capacity to draw conclusions purely based on evidence. * Experience in managing and/or participating in committees (e.g. meeting coordination, reporting, and escalation) to contribute meaningfully to IFR processes. * Demonstrated ability in relationship management to support discussion, consensus-driven decision making, and productive negotiation. * Excellent communication skills to represent ccTLD interests and to keep the ccNSO Council and broader ccTLD community informed on progress. * Ability to work and communicate in written and spoken English. Further a candidate: * Should indicate why she or he is interested in becoming involved in the IFR. * Indicate the ccTLD manager with whom the candidate is associated. * Should be employed or have active backing by the ccTLD manager with whom the candidate is associated. * Demonstrate the support by the ccTLD manager in respect to the required time commitment to participate actively in the IFR. * Indicate whether willing to stand as co-chair * Commit to abide by the rules of the IFRT and the temporary Guideline. In addition, and in accordance with the requirements with respect to the composition of an IFRT, only if a candidate is considered to meet the above criteria, functional and cultural diversity criteria should be taken into account. _______________________________________________________________________________________________ Kimberly Carlson ccNSO Support Lead Administrator Internet Corporation for Assigned Names and Numbers Skype kimberly.carlson.icann www.icann.org Top of Form Bottom of Form

1 0

Selection ccNSO appointee NomCom Fy2019
by Kimberly Carlson Aug. 10, 2018

Aug. 10, 2018

Dear all, As you recall, the council will need to appoint the ccNSO representative on the Fy2019 NomCom. The applications period closed last Friday (3 August) and we received two applications: * Pablo Rodriguez, .pr * Paulos Nyirenda, .mw In a separate email, I will forward the applications individually to all eligible councilors. Please find below, the agreed upon procedure and the call for volunteers, which includes the selection criteria. Kind regards, Kim Selection Procedure by Councillors On 6 August 2018, the secretariat will send Councillors all applications received by 3 August 17.00 UTC. Each Councillor should list the candidates in order of preference and inform the secretariat accordingly. To do this, the candidates should be ranked in order of preference. The most preferred candidate should be ranked nr 1, the second preferred next nr 2 etc. If a candidate does not meet the requirements or is not considered suited do not include that person in the list. When selecting the candidates Councillors are supposed to take into account and be guided by the selection criteria in the call for volunteers (included for reference) The list should be included in an email to the member of the secretariat assigned to run the selection process. The email should include as subject line: NomCom FY 19 candidate. PLEASE SEND YOUR EMAIL TO KIMBERLY CARLSON (Kimberly.carlson(a)icann.org<mailto:Kimberly.carlson@icann.org>) BY FRIDAY 17 August 2018, 17.00 UTC Administrative Procedure On 16 July the secretariat will send out a call for volunteers, which will close 3 August 2018. The secretariat will send Councillors all applications received to Councillors eligible to select the ccNSO member on NomCom. Councillors will send an email to Kimberly Carlson by 17 August 2017, 17.00 UTC, who - in return - will send an email to acknowledge receipt of the email and include a ballot number and the date of receipt. On Monday, 20 August 2018 the designated member of the secretariat will circulate a list to Council with the following format: - Ballot number, - Date ballot was received, - level of preference per candidate. As agreed the candidate with highest level of preference is considered to be selected. The selection procedure will be confirmed at the upcoming Council meeting: 23 August 2018. Call for volunteers Dear all, In accordance with the ccNSO Guideline: Appointment of delegate to the Nominating Committee (http://ccnso.icann.org/workinggroups/appointment-nomcom-delegate-05nov08.pdf) the ccNSO Council is now looking for a volunteer to serve on ICANN's Nominating Committee (NomCom) on behalf of the ccNSO. Candidates may self-nominate. Please note that you are required to be associated with a ccTLD manager. In addition, after being selected, you will need to consent to ICANN processing your personal data for the purpose of serving on the NomCom under ICANN's data protection policy (Terms of Service<https://www.icann.org/privacy/tos>) If you are interested in serving in this position, please, send an email to the ccNSO Secretariat (ccnsosecretariat(a)icann.org<mailto:ccnsosecretariat@icann.org>), and include a short motivation letter why you wish to serve on the NomCom and explain briefly how you meet the selection criteria listed below. Closing date for nomination is Friday 3 August 2018, 17.00 UTC. The list of candidates will be presented to all ccNSO Councillors eligible to vote and who will then take a decision by email vote. Under the 1 October 2016 Bylaws the NomCom is an independent committee tasked with nominating eight members of the Board of Directors and other key positions within ICANN's structure. The 2018 NomCom will select Directors of the ICANN Board, member(s) of the ALAC, member(s)of the GNSO Council, 1 member of the ccNSO Council. More information on the criteria for serving as appointee on the NomCom can be found at the end of this email and on the NomCom itself at: https://www.icann.org/resources/pages/nomcom-2013-12-13-en . On behalf of the ccNSO Secretariat, kind regards, Kimberly Carlson Selection Criteria Specific criteria for selecting a delegate to the NomCom are provided in Article 8, Section 4 of ICANN's Bylaws (https://www.icann.org/resources/pages/governance/bylaws-en/#article8) "Section 4. CRITERIA FOR SELECTION OF NOMINATING COMMITTEE DELEGATES Delegates to the ICANN Nominating Committee shall be: 1. Accomplished persons of integrity, objectivity, and intelligence, with reputations for sound judgment and open minds, and with experience and competence with collegial large group decision-making; 2. Persons with wide contacts, broad experience in the Internet community, and a commitment to the success of ICANN; 3. Persons whom the selecting body is confident will consult widely and accept input in carrying out their responsibilities; 4. Persons who are neutral and objective, without any fixed personal commitments to particular individuals, organizations, or commercial objectives in carrying out their Nominating Committee responsibilities; 5. Persons with an understanding of ICANN's mission and the potential impact of ICANN's activities on the broader Internet community who are willing to serve as volunteers, without compensation other than the reimbursement of certain expenses; and 6. Persons who are able to work and communicate in written and spoken English." All FY 2019 NomCom members should be able to attend the first formal meeting of the 2019 NomCom (during or around ICANN 63). Travel and hotel accommodation will be provided. In addition: * NomCom delegates should have a high-level network of contacts essential to candidate recruitment. * The person should be able to join monthly teleconferences (typically 13:00 or 14:00 UTC). Note that the committee's workload will increase significantly during Apr/May/June 2019 when the candidate assessment process will be at its busiest. Conference calls are held more frequently (typically weekly) during this time as well. * The person must be able to attend the NomCom selection meeting in late June 2018. * The person should be willing to work in a large, consensus-oriented committee. The NomCom has its own guideline <https://www.icann.org/resources/pages/2015-guidelines-2014-11-14-en> and procedure <https://www.icann.org/resources/pages/2015-procedures-2014-11-14-en> . These reference documents provide additional information about the work of the NomCom. _______________________________________________________________________________________________ Kimberly Carlson ccNSO Support Lead Administrator Internet Corporation for Assigned Names and Numbers Skype kimberly.carlson.icann www.icann.org Top of Form Bottom of Form

1 1

proposed triage recommendations [36, 37, 38, 39- 2018]
by Joke Braeken Aug. 8, 2018

Aug. 8, 2018

Dear ccNSO council members, Please find below the proposed triage recommendation(s) [36,37,38,39- 2018]. Kindly provide me with your input by the end of 10 August 2018, 23:59 UTC, in case you do not agree with the proposed recommendation(s). Thank you. Topic: 36-2018: Recommendations for Managing IDN Variant Top-Level Domains Summary of request: Recommendations for managing Internationalized Domain Name (IDN) variant labels for top level domains (TLDs) have been developed by ICANN organization. The relevant materials along with these proposed recommendations are being published to seek community feedback. Read more: https://www.icann.org/news/announcement-2018-07-25-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Date received: 27 July 2018 Last day for comments/input/response, if any: 3 September 2018 Recommended action, if any: share with ccnso-council(a)icann.org<mailto:ccnso-council@icann.org>, ccnso-members(a)icann.org<mailto:ccnso-members@icann.org>; ccTLDcommunity(a)cctld-managers.org<mailto:ccTLDcommunity@cctld-managers.org> and on the ccNSO social media channels. Expertise needed, if any: IDN, TLDs, Variant labels Date of submission to Triage Committee: 3 August 2018 Deadline Triage Committee input: 7 August 2018, 23:59 UTC Date of submission to Council: 8 August 2018 Deadline Council decision: Thu, 10 August 2018, 23:59 UTC Impact on ccNSO/ccTLDs: Low = = = = Topic: 37-2018: Proposals for Devanagari, Gurmukhi, and Gujarati Scripts' Root Zone Label Generation Rules Summary of request: The Neo-Brahmi Script Generation Panel (NBGP) was formed by nine communities that use scripts derived from the Brahmi script. NBGP is developing Root Zone Label Generation Rules (LGR) for Bengali, Devanagari, Gujarati, Gurmukhi, Kannada, Malayalam, Oriya, Tamil and Telugu scripts. The GP intends to publish the proposals for the LGRs of these nine scripts in three sets, releasing proposals for the scripts which share cross-script variant code points together to the extent possible. The first set includes the following: (1) Proposal for the Devanagari Script Label Generation Rules for the Root Zone, (2) Proposal for the Gurmukhi Script Label Generation Rules for the Root Zone, and (3) Proposal for the Gujarati Script Label Generation Rules for the Root Zone. As per the LGR Procedure [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…>, these proposals are being posted for public comments to allow those who have not participated in the NBGP to make their views known. Based on the feedback, the NBGP will finalize each proposal for its evaluation and integration into the Label Generation Rules for the Root Zone. Read more: https://www.icann.org/news/announcement-2018-07-27-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Date received: 30 July 2018 Last day for comments/input/response, if any: 10 September 2018 Recommended action, if any: share with ccnso-council(a)icann.org<mailto:ccnso-council@icann.org>, ccnso-members(a)icann.org<mailto:ccnso-members@icann.org>; ccTLDcommunity(a)cctld-managers.org<mailto:ccTLDcommunity@cctld-managers.org> and on the ccNSO social media channels. Expertise needed, if any: IDN, LGR Procedure Date of submission to Triage Committee: 3 August 2018 Deadline Triage Committee input: 7 August 2018, 23:59 UTC Date of submission to Council: 8 August 2018 Deadline Council decision: Thu, 10 August 2018, 23:59 UTC Impact on ccNSO/ccTLDs: Low = = = = Topic: 38-2018: Draft ICANN Africa Strategic Plan 2016-2020 V3.0 Summary of request: ICANN organization (org.) is seeking public comments on the draft reviewed ICANN - Africa Strategy FY16-FY20 Ver3.0 Read more: https://www.icann.org/news/announcement-2018-07-30-en Date received: 1 August 2018 Last day for comments/input/response, if any: 10 September 2018 Recommended action, if any: share with ccnso-council(a)icann.org<mailto:ccnso-council@icann.org>, ccnso-members(a)icann.org<mailto:ccnso-members@icann.org>; ccTLDcommunity(a)cctld-managers.org<mailto:ccTLDcommunity@cctld-managers.org> and on the ccNSO social media channels. Expertise needed, if any: Africa Strategic Plan Date of submission to Triage Committee: 3 August 2018 Deadline Triage Committee input: 7 August 2018, 23:59 UTC Date of submission to Council: 8 August 2018 Deadline Council decision: Thu, 10 August 2018, 23:59 UTC Impact on ccNSO/ccTLDs: Low = = = = Topic: 39-2018: Study Technical Use Root Zone Label Generation Rules Summary of request: Second version of the Root Zone Label Generation Rules (RZ-LGR-2) was released in August 2017, integrating six script proposals, as other LGR script proposals are being finalized. The Root Zone Label Generation Rules Study Group (RZ-LGR-SG) has been constituted to study and make recommendations for the technical use of RZ-LGR in a harmonized way across Internationalized Domain Name (IDN) Top-Level Domains (TLDs). RZ-LGR-SG has identified its scope of work [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> [PDF, 128 KB], which is being shared with the community. The SG seeks feedback from the community on whether the questions identified are all relevant for this study and whether there are any other issues it should also consider. RZ-LGR-SG will take into account the community input to finalize the scope of its work, develop the related recommendations and share these recommendations with the community before finalization. Read more: https://www.icann.org/news/announcement-2018-08-02-en Date received: 3 August 2018 Last day for comments/input/response, if any: 11 September 2018 Recommended action, if any: share with ccnso-council(a)icann.org<mailto:ccnso-council@icann.org>, ccnso-members(a)icann.org<mailto:ccnso-members@icann.org>; ccTLDcommunity(a)cctld-managers.org<mailto:ccTLDcommunity@cctld-managers.org> and on the ccNSO social media channels. Expertise needed, if any: Root Zone Label Generation Rules, IDN, TLDs Date of submission to Triage Committee: 3 August 2018 Deadline Triage Committee input: 7 August 2018, 23:59 UTC Date of submission to Council: 8 August 2018 Deadline Council decision: Thu, 10 August 2018, 23:59 UTC Impact on ccNSO/ccTLDs: Low = = = = Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

latest newsletter by the New gTLD Subsequent Procedures PDP Working Group
by Joke Braeken Aug. 7, 2018

Aug. 7, 2018

Dear all, On behalf of the leadership team of the New gTLD Subsequent Procedures PDP Working Group, I am writing to share the latest edition of the Working Group newsletter: http://go.icann.org/SubPro<https://urldefense.proofpoint.com/v2/url?u=http-3A__go.icann.org_SubPro&d=D…>. The newsletter includes – among others -information regarding Work Track 5, Geographic Names at the Top Level. An archive of previous editions of the newsletter is available on the WG wiki<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_pa…> and on the GNSO website<https://gnso.icann.org/en/news/working-group-newsletters>. About the New gTLD Subsequent Procedures PDP Working Group In June 2014, the GNSO Council established a Discussion Group that was intended to evaluate the experiences of the 2012 round gTLD Program and to identify possible areas for future GNSO policy development. The Discussion Group’s deliverables served as the basis for the GNSO Council’s request for a Preliminary Issue Report in June of 2015. Following the publication of the Final Issue Report, the GNSO Council adopted the charter for the PDP Working Group, which began its work in February 2016. The Working Group initially concentrated on a set of overarching issues and has since established five separate Work Tracks to consider specific topic areas: * Work Track 1 - Overall Process/Support/Outreach, * Work Track 2 - Legal/Regulatory, * Work Track 3: String Contention/Objections & Disputes, * Work Track 4: Internationalized Domain Names/Technical & Operations, * Work Track 5: Geographic Names at the Top Level. Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

ICANN64 Fellowship Application Round Now Open
by Joke Braeken Aug. 7, 2018

Aug. 7, 2018

Dear all, ICANN is launching application round for applicants interested in participating in the ICANN64 Public Meeting through the Fellowship Program. ICANN64 will take place from 9-14 March 2019 in Kobe, Japan. The deadline to apply is 3 September 2018, 23:59 UTC. Successful candidates will be announced on 12 November 2018 on https://icann.org/ [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_&d=DwMFa…>. ICANN Fellowship Program The Fellowship Program [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_about…> is open to all applicants interested in, or already engaged in, the various aspects of ICANN's work in policymaking, the operation of the Domain Name System, and the security and stability of the global Internet. The goal of the program is to help create a more diverse and a broader base of knowledgeable constituents who can engage in the ICANN multistakeholder process and become the new voices of experience in their regions and on the global stage. Since its creation in 2007, the Fellowship Program has built a strong group of fellows who are actively participating in ICANN communities and in other Internet governance entities in the Internet ecosystem. Participation covers a range of activities: * Writing articles and blogs * Giving online or in-person public comments about bottom-up policymaking * Participating in Internet conferences and panel discussions * Joining working groups * Mentoring newcomers * Assisting our regional leaders * Becoming leaders themselves More information<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_about…>: https://www.icann.org/news/announcement-2018-08-03-en<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

German Appellate Court Rules on ICANN Request to Preserve WHOIS Data
by Joke Braeken Aug. 7, 2018

Aug. 7, 2018

Dear all, ICANN announced that a German appeal court (Appellate Court of Cologne) has issued a decision on the injunction proceedings ICANN initiated against EPAG, a Germany-based, ICANN-accredited registrar that is part of the Tucows Group. The Appellate Court has determined that it would not issue an injunction against EPAG. In making its ruling, the Appellate Court stated that the interpretation of provisions of the GDPR was not material to its decision, so there was no obligation to refer the matter to the European Court of Justice. Rather, the Appellate Court simply found that it was not necessary for it to issue a preliminary injunction to avoid imminent and substantial disadvantages, and noted that ICANN could pursue its claims in the main proceedings in order to enforce the rights it asserts. ICANN is considering its next steps, including possible additional filings before the German courts, as part of its public interest role in coordinating a decentralized global WHOIS for the generic top-level domain system and will provide additional information in the coming days. Read more: https://www.icann.org/news/announcement-2-2018-08-03-en Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

Methodology Review of the Domain Abuse Activity Reporting (DAAR) System
by Joke Braeken Aug. 3, 2018

Aug. 3, 2018

Dear All, ICANN announced the publication of a paper describing the methodology used in the Domain Abuse Activity Reporting (DAAR) system and two reviews of that methodology. DAAR was designed to provide the ICANN community with a reliable, persistent, and reproducible data from which security threat (abuse) analyses could be performed. The DAAR project has produced a system for studying and reporting domain name registration and security threat (domain abuse) behavior across top-level domain (TLD) registries and registrars. The overarching purpose of DAAR is to report security threat activity as it is experienced in network operations to the ICANN community, which can then use the data to facilitate informed policy decisions. To inform the community of the DAAR project design objectives and the ways by which those objectives have been met, the ICANN organization has prepared a methodology white paper. The paper explains the purposes of the DAAR project and gives an overview of the system, describes the security threats that DAAR observes, and how DAAR compiles threat data from high-confidence threat reputation data feeds. To foster confidence in the DAAR system, the ICANN org has engaged two independent experts to review the methodology paper, to comment on the threat data that DAAR consumes, and to experiment with the reporting system. The purpose of these reviews is to have experts in the field validate the methodology, attest to the reproducibility of DAAR's findings and reporting, and to attest to the quality and reliability of the reputation data that the ICANN org has chosen to use for this project. We welcome your comments on the reports and reviews. Please send them to daar(a)icann.org<mailto:daar@icann.org>, by 24 August 2018. The findings and recommendations from the reviewers and parties who comment will be considered in the final drafting of the methodology paper. Read more here: https://www.icann.org/news/announcement-2018-07-20-en Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

ICANN 2018 Nominating Committee Announces Selections
by Joke Braeken Aug. 3, 2018

Aug. 3, 2018

Dear all, The ICANN 2018 Nominating Committee announced its selections for eight leadership positions within ICANN, including the NomCom appointees to the ccNSO Council: * Laura Margolis (Latin America / Caribbean Islands), Three-year term * Ajay Data (Asia / Australia / Pacific Islands), Two-year term Those selected will take up their positions after the end of ICANN’s Annual General Meeting, which will take place during ICANN63, scheduled for 20 October – 25 October 2018 in Barcelona, Spain. The Nominating Committee is charged with recruiting and selecting a portion of ICANN’s leadership and is mandated to ensure that ICANN’s overall leadership is diverse in geography, culture, skills, experience, and perspective. Read more here: https://www.icann.org/news/announcement-2-2018-08-02-en Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

Registry System Testing (RST) Documentation update
by Joke Braeken Aug. 2, 2018

Aug. 2, 2018

Dear all, ICANN announced an RST documentation <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> update. The update includes new documentation related to domain name system (DNS), Internationalized Domain Name (IDN) and WHOIS testing. The FAQ document <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> was also updated to reflect the related changes. * DNS <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> test documentation was updated to align with backend changes to the DNS test engine. * IDN <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> test documentation was updated to reflect procedural changes in support of LGR formatted tables. * WHOIS <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> test documentation was updated to accommodate the requirements specified in the Temporary Specification for gTLD Registration Data<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

ccNSO Activity Summary | July 2018
by Kimberly Carlson Aug. 1, 2018

Aug. 1, 2018

ccNSO Activity Summary July 2018 Pre-call for presenters at ICANN63! Please contact the Tech WG<mailto:ccNSO-techday@icann.org> if you have questions or interested in presenting at TechDay Working/Study Group Meeting Output: Recordings of various Working Group Meetings can be found here: http://ccnso.icann.org/calendar 30 July - Meetings Programme Working Group - wiki<https://community.icann.org/x/hDCAAw> 19 July - ccPDP on Retirement Working Group - Wiki<https://community.icann.org/x/HolHBQ> 18 July - ccNSO Study Group on Use of Emoji as SLD - Wiki<https://community.icann.org/x/KgJdBQ> 16 July - Guidelines Review Committee Telephone Conference - Wiki<https://community.icann.org/x/1YdHBQ> ccNSO Council: ccNSO Council has combined their July and August call and will take place on 23 August 2018 ccNSO Council preparation material and output can be found here: http://ccnso.icann.org/about/council/minutes.htm ccNSO Council Decisions and Resolutions: http://ccnso.icann.org/about/council/decisions-resolutions.htm ccNSO Council Wiki space <https://community.icann.org/x/BiyAAw> Links and Announcements regarding the IANA Stewardship Transfer and ICANN's Accountability Process: IANA Stewardship Transition Implementation Page<https://www.icann.org/stewardship-implementation> CSC Reports and Findings<https://www.icann.org/en/csc/reports> Initial Report on Review of the Customer Standing Committee (CSC) Charter<https://www.icann.org/news/announcement-2-2018-04-11-en> Other Announcements: ICANN Publishes ICANN62 By the Numbers Report<https://www.icann.org/news/announcement-2018-07-31-en> - 31 July 2018 ICANN Announces Participants NextGen@ICANN63<https://www.icann.org/news/announcement-2-2018-07-30-en> - 30 July 2018 Data Protection/Privacy Update: Key GDPR WHOIS Updates and Next Steps<https://www.icann.org/news/blog/data-protection-privacy-update-key-gdpr-who…> - ICANN Blog - 27 July 2018 Recommendations for Managing IDN Variant Top-Level Domains<https://www.icann.org/news/announcement-2018-07-25-en> - 25 July 2018 Methodology Review of the Domain Abuse Activity Reporting (DAAR) System<https://www.icann.org/news/announcement-2018-07-20-en> - 20 July 2018 Minimal User Impact Expected From Root Zone Key Signing Key (KSK) Rollover<https://www.icann.org/news/blog/minimal-user-impact-expected-from-root-zone…> - ICANN Blog - 18 July 2018 Successful Candidates Announced for ICANN63 Fellowship<https://www.icann.org/news/announcement-2018-07-16-en> - 16 July 2018 ICANN Board of Directors Submits Comments Regarding NTIA's Notice of Inquiry on International Internet Policy Priorities<https://www.icann.org/news/announcement-2018-07-13-en> - 13 July 2018 Root Server System Advisory Committee Review: Final Report Now Available<https://www.icann.org/news/announcement-2018-07-10-en> - 10 July 2018 Initial Report on the New gTLD Subsequent Procedures Policy Development Process (Overarching Issues & Work Tracks 1-4)<https://www.icann.org/public-comments/gtld-subsequent-procedures-initial-20…> - 3 July 2018 _______________________________________________________________________________________________ Kimberly Carlson ccNSO Support Lead Administrator Internet Corporation for Assigned Names and Numbers Skype kimberly.carlson.icann www.icann.org Top of Form Bottom of Form

1 0

DECISION NEEDEDL: Two options for IFRT
by Katrina Sataki Aug. 1, 2018

Aug. 1, 2018

Dear Councillors, DECISION IS NEEDED As you remember, we must to appoint three members to IANA Function Review team (IFRT). We have to appoint 2 representatives from ccTLDs that are ccNSO members and 1 representative from a ccTLD that is not a ccNSO member. Plus, each our appointed member has to be from a different ICANN region. That is - we need to select three people from three ICANN regions. Appointment is due 28 August but it is already clear that we will not make it in time. The GRC has discussed different scenarios but does not have a clear opinion on what would be the best way forward. Currently, we have come up with a temporary guideline. The idea is to test it in real life and then tweak it for future use. I am sending you two versions - version A and version B. I will try to briefly describe the difference between the two. Version A. The entire Council participates in selection of each candidate. Candidates are divided in two pools (Pool A for ccNSO members and Pool B for ccNSO non-members). The voting takes place in three rounds - during each round we select ONE member from the least regionally diverse pool (or from both pools simultaneously if they are equally diverse and non-ccNSO member candidate has not been selected yet). Pluses: - it allows every Councillor to participate in the selection of each candidate - it allows to weight candidates every time we know who has already been selected (gives more opportunity for diversity - except regional diversity) Minuses: - the algorithm is pretty complex (but that is the only one I can think of if we want 17 people to select members that match all of the requirements) - does not take into account the willingness of candidates to be a co-chair - short times to vote for each candidate (3 working days) - takes longer in total (at least 9 working days plus weekends) Version B. The entire Council ranks all the candidates in one long list. Then the Chair and Vice-chairs go through the list and hand-pick three candidates that match regional diversity and membership criteria, taking into account Council's choices as much as possible. Pluses: - simpler and faster (7 working days for voting plus a couple of days to hand-pick three) - longer time to evaluate and rank the candidates (7 working days) - might be possible to take into account the willingness to serve as a co-chair (but that might not be easy). Minuses: - the ccNSO Council ranks the candidates only once and then three people determine the final outcome. As this is temporary procedure, we can follow it or agree on a completely different mechanism. The only problem - we need to act quickly. Therefore, by 5 August, please send your preference - Version A or Version B - to the mailing list. If you wish to propose a version C (D, E, F.), please feel free to do it. If we agree on the procedure, then: - 7 August: send out a call for Expression of Interest - 21 August: closure of the call for EoI - Depending on the preferred procedure: o Version A - 5 September: three members selected o Version B - 30 August: three members selected Please let us know your preference by 5 August! Kind regards, ]{atrina

14 14