- ALAC - lists.icann.org

ALAC Statement to accompany EPDP Phase 1 Final Report
by Alan Greenberg Feb. 17, 2019

Feb. 17, 2019

As discussed today the statement has been modified to address the issues raised on the CPWG teleconference. The SSAC has also issue a statement (https://mm.icann.org/pipermail/gnso-epdp-team/2019-February/001682.html) and I took the opportunity to add a few comments prompted by their document. A redline and clean version is attached. Alan

7 8

Fw: Meeting Invitation: GNSO Temp Spec gTLD RD EPDP call / Wednesday, 20 February 2019 at 14:00 UTC for 3 hours
by Hadia Abdelsalam Mokhtar EL miniawi Feb. 16, 2019

Feb. 16, 2019

For those interested in following the meeting Hadia ________________________________ From: Ntfy-gnso-epdp-team <ntfy-gnso-epdp-team-bounces(a)icann.org> on behalf of Andrea Glandon <andrea.glandon(a)icann.org> Sent: 11 February 2019 19:59 To: ntfy-gnso-epdp-team(a)icann.org Cc: gnso-secs(a)icann.org Subject: [Ntfy-gnso-epdp-team] Meeting Invitation: GNSO Temp Spec gTLD RD EPDP call / Wednesday, 20 February 2019 at 14:00 UTC for 3 hours **There are calls for both 19 & 20 February. I am sending both invitations now to get them on your calendars.** Dear all, The forty-seventh meeting of the GNSO Temp Spec gTLD RD EPDP Team is scheduled on Wednesday, 20 February 2019 at 14:00 UTC for 3 hours. 06:00 PST, 09:00 EST, 15:00 Paris CET, 19:00 Karachi PKT, 23:00 Tokyo JST, (Thursday) 01:00 Melbourne AEDT For other times: https://tinyurl.com/y4bzjqkv Agenda Wiki: https://community.icann.org/x/FoU2Bg Please ensure you read the below information: CONFERENCE CALL INFORMATION FOR MEMBERS Adobe Connect room: https://participate.icann.org/gnso-epdp-team If you’re having trouble joining, please check your plug ins: http://tinyurl.com/icannactest [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__tinyurl.com_icannactest…> Please allow yourself additional time before start of meeting to log into Adobe Connect. **Important**- Please log into Adobe Connect with your FIRST and LAST NAME-AFFILIATION/INDIVIDUAL Instructions explaining how to connect the audio in the Adobe Connect room are attached. A calendar invitation has equally been sent and an ical (if your inbox doesn’t receive direct calendar invitations) is available here as attachment for you to download to your calendar. ALTERNATES will be assigned by Members in case of Member absence for a determined period of time and will therefore replace the aforementioned Member on the mailing list and on conference calls. In case of absence, members must assign an appointed Alternate via the Alternate Assignment form [goo.gl]<https://urldefense.proofpoint.com/v2/url?u=https-3A__goo.gl_forms_xtfYf9mWF…>. MEETING AUDIO CAST AND VIEW ONLY ADOBE CONNECT (FOR ALTERNATES AND OBSERVERS) To join the event, click on the link: Listen in browser: http://stream.icann.org:8000/stream01 [stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Listen in application such as iTunes: http://stream.icann.org:8000/stream01.m3u [stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> View-Only Adobe Connect room for alternates and observers: https://participate.icann.org/gnso-epdp-observers If you require a dial-out or to send apologies (do not send to full working group) please send an email request with your preferred contact number to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: https://gnso.icann.org/en/group-activities/calendar<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> To join via Verizon Bridge, see dial in numbers and participant passcode below. Kind regards, Andrea ___________________________________________________________ To join the audio bridge, call in using the appropriate phone number below and provide the Participant Passcode verbally to the operator. Participant passcode: EPDP Dial in numbers: Country Toll Numbers Freephone/ Toll Free Number ARGENTINA 0800-777-0519 AUSTRALIA ADELAIDE: 61-8-8121-4842 1-800-657-260 AUSTRALIA BRISBANE: 61-7-3102-0944 1-800-657-260 AUSTRALIA CANBERRA: 61-2-6100-1944 1-800-657-260 AUSTRALIA MELBOURNE: 61-3-9010-7713 1-800-657-260 AUSTRALIA PERTH: 61-8-9467-5223 1-800-657-260 AUSTRALIA SYDNEY: 61-2-8205-8129 1-800-657-260 AUSTRIA 43-1-92-81-113 0800-005-259 BELGIUM 32-2-400-9861 0800-3-8795 BRAZIL RIO DE JANEIRO: 55-21-40421490 0800-7610651 BRAZIL SAO PAULO: 55-11-3958-0779 0800-7610651 CHILE 1230-020-2863 CHINA CHINA A: 86-400-810-4789 10800-712-1670 CHINA CHINA B: 86-400-810-4789 10800-120-1670 COLOMBIA 01800-9-156474 CROATIA 080-08-06-309 CZECH REPUBLIC 420-2-25-98-56-64 800-700-177 DENMARK 45-7014-0284 8088-8324 EGYPT 0800000-9029 ESTONIA 800-011-1093 FINLAND 358-9-5424-7162 0-800-9-14610 FRANCE LYON: 33-4-26-69-12-85 080-511-1496 FRANCE MARSEILLE: 33-4-86-06-00-85 080-511-1496 FRANCE PARIS: 33-1-70-70-60-72 080-511-1496 GERMANY 49-69-2222-20362 0800-664-4247 GREECE 30-80-1-100-0687 00800-12-7312 HONG KONG 852-3001-3863 800-962-856 HUNGARY 36-1-700-8856 06-800-12755 INDIA INDIA A: 000-800-852-1268 INDIA INDIA B: 000-800-001-6305 INDIA INDIA C: 1800-300-00491 INDONESIA 001-803-011-3982 IRELAND 353-1-246-7646 1800-992-368 ISRAEL 1-80-9216162 ITALY MILAN: 39-02-3600-6007 800-986-383 ITALY ROME: 39-06-8751-6018 800-986-383 ITALY TORINO: 39-011-510-0118 800-986-383 JAPAN OSAKA: 81-6-7878-2631 0066-33-132439 JAPAN TOKYO: 81-3-6868-2631 0066-33-132439 LATVIA 8000-3185 LUXEMBOURG 352-27-000-1364 8002-9246 MALAYSIA 1-800-81-3065 MEXICO GUADALAJARA (JAL): 52-33-3208-7310 001-866-376-9696 MEXICO MEXICO CITY: 52-55-5062-9110 001-866-376-9696 MEXICO MONTERREY: 52-81-2482-0610 001-866-376-9696 NETHERLANDS 31-20-718-8588 0800-023-4378 NEW ZEALAND 64-9-970-4771 0800-447-722 NORWAY 47-21-590-062 800-15157 PANAMA 011-001-800-5072065 PERU 0800-53713 PHILIPPINES 63-2-858-3716 1800-111-42453 POLAND 00-800-1212572 PORTUGAL 351-2-10054705 8008-14052 ROMANIA 40-31-630-01-79 RUSSIA 8-10-8002-0144011 SAUDI ARABIA 800-8-110087 SINGAPORE 65-6883-9230 800-120-4663 SLOVAK REPUBLIC 421-2-322-422-25 0800-002066 SOUTH AFRICA 080-09-80414 SOUTH KOREA 82-2-6744-1083 00798-14800-7352 SPAIN 34-91-414-25-33 800-300-053 SWEDEN 46-8-566-19-348 0200-884-622 SWITZERLAND 41-44-580-6398 0800-120-032 TAIWAN 886-2-2795-7379 00801-137-797 THAILAND 001-800-1206-66056 TURKEY 00-800-151-0516 UNITED ARAB EMIRATES 8000-35702370 UNITED KINGDOM BIRMINGHAM: 44-121-210-9025 0808-238-6029 UNITED KINGDOM GLASGOW: 44-141-202-3225 0808-238-6029 UNITED KINGDOM LEEDS: 44-113-301-2125 0808-238-6029 UNITED KINGDOM LONDON: 44-20-7108-6370 0808-238-6029 UNITED KINGDOM MANCHESTER: 44-161-601-1425 0808-238-6029 URUGUAY 000-413-598-3421 USA 1-517-345-9004 866-692-5726 VENEZUELA 0800-1-00-3702 VIETNAM 120-11751

1 0

Re: [ALAC] [registration-issues-wg] [CPWG] URGENT: DRAFT ALAC Statement on the EPDP Phase 1 Final Report
by Alan Greenberg Feb. 15, 2019

Feb. 15, 2019

Thanks Seun. Note that Rec #6 does allow you to specify that your contact information be disdplayed (on the registrar site only!) but no timeline when they must provide this option. If you are in general supporting the issuing of the statement, it would be helpful to put that on the record (no obligation obviously though!). On not accepting the report on the whole, this was debated on the last CPWG call and the consensus (but not unanimous) was that we not do that. Alan At 15/02/2019 04:59 AM, Seun Ojedeji wrote: Hello Alan, Thanks for sharing this which is good. A few minor editorials and comment: 1. "â€œthat it would be difficult to argue that *that* processing to prevent DNS...." 2 "...Phase 2 will *be* address the deferred issues as..." 3. I am not sure why we say "we do not accept" certain issues yet we seem to end our statement by accepting the report. Since/if we have red-lines then we should clearly not accept the report as a whole. However if we can live with the report as indicated in the last paragraph then I suggest we modify the following: "To be specific, the results which we cannot accept are:...." So it doesn't contradict the acceptance stated in the last paragraph. That said, I agree with Gorge, that the element of choice/consent is being taken away from registrants in terms of what they want to provide and publish. It's election period in my country, my apologies as I won't be present at upcoming cpwg call Regards Sent from my mobile Kindly excuse brevity and typos On Fri, 15 Feb 2019, 01:28 Alan Greenberg <alan.greenberg(a)mcgill.ca<mailto:alan.greenberg@mcgill.ca> wrote: As discussed on the CPWG call yesterday, attached please find the draft statement to be attached to the report. I believe that it addresses all of the issues we discussed and for which there was general concern. As decided, we will support the overall report, but note that some of the particular recommendations do not have our support. Others we will support but nevertheless have concerns. The lack of focus on public interest issues puts into question whether Phase 2 will suitably address access and other issues. THIS STATEMENT MUST BE SUBMITTED BY THE END OF FRIDAY. Please make any comments with utmost urgency. Maureen tells me that she will issue a VERY SHORT Consensus Call tomorrow, to complete prior to the submission deadline. WORD and PDF formats are attached. Alan _______________________________________________ CPWG mailing list CPWG(a)icann.org<mailto:CPWG@icann.org> https://mm.icann.org/mailman/listinfo/cpwg _______________________________________________ registration-issues-wg mailing list registration-issues-wg(a)atlarge-lists.icann.org<mailto:registration-issues-wg@atlarge-lists.icann.org> https://mm.icann.org/mailman/listinfo/registration-issues-wg

3 3

URGENT: DRAFT ALAC Statement on the EPDP Phase 1 Final Report
by Alan Greenberg Feb. 15, 2019

Feb. 15, 2019

As discussed on the CPWG call yesterday, attached please find the draft statement to be attached to the report. I believe that it addresses all of the issues we discussed and for which there was general concern. As decided, we will support the overall report, but note that some of the particular recommendations do not have our support. Others we will support but nevertheless have concerns. The lack of focus on public interest issues puts into question whether Phase 2 will suitably address access and other issues. THIS STATEMENT MUST BE SUBMITTED BY THE END OF FRIDAY. Please make any comments with utmost urgency. Maureen tells me that she will issue a VERY SHORT Consensus Call tomorrow, to complete prior to the submission deadline. WORD and PDF formats are attached. Alan

7 8

Re: [ALAC] [CPWG] URGENT: DRAFT ALAC Statement on the EPDP Phase 1 Final Report
by Maureen Hilyard Feb. 15, 2019

Feb. 15, 2019

Thank you Gordon. Maureen On Fri, Feb 15, 2019 at 6:20 AM Gordon Chillcott <gordontc(a)gmail.com> wrote: > I will make every effort to attend today's meeting, but in case I don't > - I support the Draft ALAC Statement. > > > Gordon Chillcott > > > > On Fri, 2019-02-15 at 00:28 +0000, Alan Greenberg wrote: > > As discussed on the CPWG call yesterday, attached please find the > > draft statement to be attached to the report. > > > > I believe that it addresses all of the issues we discussed and for > > which there was general concern. As decided, we will support the > > overall report, but note that some of the particular recommendations > > do not have our support. Others we will support but nevertheless have > > concerns. > > > > The lack of focus on public interest issues puts into question whether > > Phase 2 will suitably address access and other issues. > > > > THIS STATEMENT MUST BE SUBMITTED BY THE END OF FRIDAY. Please make any > > comments with utmost urgency. > > > > Maureen tells me that she will issue a VERY SHORT Consensus Call > > tomorrow, to complete prior to the submission deadline. > > > > WORD and PDF formats are attached. > > > > Alan > > _______________________________________________ > > CPWG mailing list > > CPWG(a)icann.org > > https://mm.icann.org/mailman/listinfo/cpwg > > > _______________________________________________ > CPWG mailing list > CPWG(a)icann.org > https://mm.icann.org/mailman/listinfo/cpwg >

1 0

Re: [ALAC] [CPWG] URGENT: DRAFT ALAC Statement on the EPDP Phase 1 Final Report
by Alan Greenberg Feb. 15, 2019

Feb. 15, 2019

Thanks George. Rec #6 requires that registrars must give registrants the choice of publishing contract details but there is no timeline when this will be done. So registrars could delay. Alan At 14/02/2019 08:54 PM, George Kirikos wrote: >Hi Alan, > >I have strong concerns that the current recommendations are >anti-choice, namely that they prevent registrants from even consenting >to publication of their full contact detail (i.e. all the contact >details that have historically been in the WHOIS). > >According to the Feb 11, 2019 draft version at: > >https://community.icann.org/display/EOTSFGRD/g.+Draft+Final+Report > >recommendation #10 forcibly redacts the registrant Name, Street, >Postal Code, Phone, Fax (which is completely missing in the table!). >Email is also redacted, subject to recommendation #13. Footnote 16 >says it can be replaced by a form or anonymized email, but that >suffers from the issues I pointed out at: > >https://mm.icann.org/pipermail/cpwg/2019-February/000853.html > >Now, Recommendation #13 also refers to "Recommendation X" >(non-existent!) which would allow the Registered Name Holder to >provider consent for publication of just its email address. However, >that doesn't seem to allow the registrant to consent to publication of >*ALL* of its contact details (i.e. name, phone number, fax, full >mailing address, etc.). > >Many registrants *want* that fully published, and these >recommendations take away that choice from the registrant. > >The same issue exists for the tech contact. Some folks want that >separate contact's full info to be collected and published, but aren't >going to be able to even consent to that (again, it just says "Yes" >for "Redacted", without the footnote to consent to publication). That >secondary contact point is going to be useful if the primary contact >has downtime, becomes invalid, is on vacation, or is otherwise >unavailable. With just 1 visible contact, it creates a single point of >failure, if communications are missed. > >In essence, these recommendations are overapplying the GDPR (e.g. to >non-persons, and to those outside the EU), *even* if the registrant >wants to fully consent to full publication of their own data (Rec #17 >shows that overapplication). It takes a "father knows best" approach, >to disregard the registrant's own wishes and doesn't give them the >opportunity to consent, to exercise their own choices. By all means, >if someone wants to not publish their data, respect that choice. But, >those who *do* want to publish their data are totally disrespected by >the current recommendations. > >Folks have many legitimate reasons for wanting to fully publish their >own data, including not wanting their communications to be intercepted >by the registrar, and also to be able to openly demonstrate that they >own their domains! The WHOIS is supposed to be the authoritative >record of domain ownership (simply putting the data on the website >associated with a domain name is *evidence* of ownership, but isn't >*proof* -- the WHOIS is the proof; e.g. the website or nameservers can >be hacked, and have false info in the "evidence", but the WHOIS itself >should always show the true owner). > >The text of the recommendations is also open to interpretation, which >is unwise. e.g. on page 40 it says openly: > >"The Team could not come to agreement on this issue and as such no >recommendation is included in this Final Report in relation to whether >optional also means, optional or required for the registrar to offer." > >i.e. if one can't even agree on what the recommendations *say*, that's >just wishy-washy, and doesn't help anyone. Recommendations should have >clarity, not purposeful ambiguity. > >By forcing more info to be private (even against the wishes of the >registrant), this will erode the trust of the entire DNS. > >BTW, for Recommendation #16, one might want to mention that registrars >routinely accurately determine the location of registrants, in order >to make sure that the correct sales tax is charged to them. I'm not >too concerned about loss of thick WHOIS (.com has proven that thin >WHOIS can work). > >Copying the message originator (on page 2 of the draft letter) isn't >going to work, as it would *enable* spam (unless the originator is >somehow verified in advance). This was pointed out in the first >paragraph of: > >https://mm.icann.org/pipermail/cpwg/2019-February/000853.html > >Sincerely, > >George Kirikos >416-588-0269 >http://www.leap.com/ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >On Thu, Feb 14, 2019 at 7:28 PM Alan Greenberg ><alan.greenberg(a)mcgill.ca> wrote: > > > > As discussed on the CPWG call yesterday, attached please find the > draft statement to be attached to the report. > > > > I believe that it addresses all of the issues we discussed and > for which there was general concern. As decided, we will support > the overall report, but note that some of the particular > recommendations do not have our support. Others we will support but > nevertheless have concerns. > > > > The lack of focus on public interest issues puts into question > whether Phase 2 will suitably address access and other issues. > > > > THIS STATEMENT MUST BE SUBMITTED BY THE END OF FRIDAY. Please > make any comments with utmost urgency. > > > > Maureen tells me that she will issue a VERY SHORT Consensus Call > tomorrow, to complete prior to the submission deadline. > > > > WORD and PDF formats are attached. > > > > Alan > > _______________________________________________ > > CPWG mailing list > > CPWG(a)icann.org > > https://mm.icann.org/mailman/listinfo/cpwg

1 0

Re: [ALAC] January 2019 ccNSO Update
by Barrack Otieno Feb. 5, 2019

Feb. 5, 2019

*Working/Study Group Meeting Output:* Recordings of various Working Group Meetings can be found here: *http://ccnso.icann.org/calendar <http://www.google.com/url?q=http%3A%2F%2Fccnso.icann.org%2Fcalendar&sa=D&sn…>* 31 January – ccPDP on Retirement Working Group Telephone Conference - Wiki <https://www.google.com/url?q=https%3A%2F%2Fcommunity.icann.org%2Fx%2FOIANBg…> 30 January - ccNSO Study Group on Use of Emoji as SLD Telephone Conference - Wiki <https://www.google.com/url?q=https%3A%2F%2Fcommunity.icann.org%2Fx%2FL4ANBg…> 23 January - TLD OPS Standing Committee and Playbook Drafting Team Telephone Conference 21 January – Meetings Programme Committee - Wiki <https://www.google.com/url?q=https%3A%2F%2Fcommunity.icann.org%2Fx%2FmgSfB&…> 17 January – ccPDP on Retirement Working Group Telephone Conference - Wiki <https://www.google.com/url?q=https%3A%2F%2Fcommunity.icann.org%2Fx%2FWQn_BQ…> 16 January - ccNSO Study Group on Use of Emoji as SLD Telephone Conference - Wiki <https://www.google.com/url?q=https%3A%2F%2Fcommunity.icann.org%2Fx%2FKoANBg…> 14 January – Guidelines Review Committee Telephone Conference - Wiki <https://www.google.com/url?q=https%3A%2F%2Fcommunity.icann.org%2Fx%2FGQb_BQ…> *ccNSO Council:* ccNSO Council call 17 January - wiki <https://www.google.com/url?q=https%3A%2F%2Fcommunity.icann.org%2Fx%2FQolHBQ…> ccNSO Council preparation material and output can be found here: http://ccnso.icann.org/about/council/minutes.htm <http://www.google.com/url?q=http%3A%2F%2Fccnso.icann.org%2Fabout%2Fcouncil%…> ccNSO Council Decisions and Resolutions: http://ccnso.icann.org/about/council/decisions-resolutions.htm <http://www.google.com/url?q=http%3A%2F%2Fccnso.icann.org%2Fabout%2Fcouncil%…> Thank you Best Regards -- Barrack O. Otieno +254721325277 +254733206359 Skype: barrack.otieno PGP ID: 0x2611D86A

1 0

Fwd: [cctldcommunity] the January 2019 ccNSO monthly newsletter is out!
by Barrack Otieno Jan. 23, 2019

Jan. 23, 2019

Dear ALAC Members, This might be of interest to you. Regards ---------- Forwarded message ---------- From: Joke Braeken <joke.braeken(a)icann.org> Date: Wed, 23 Jan 2019 09:46:58 +0000 Subject: [cctldcommunity] the January 2019 ccNSO monthly newsletter is out! To: "ccnso-members(a)icann.org" <ccnso-members(a)icann.org>, "ccTLDcommunity(a)cctld-managers.org" <ccTLDcommunity(a)cctld-managers.org>, ccnso-council <ccnso-council(a)icann.org> Dear all, The January 2019 edition of the ccNSO monthly newsletter is out. This month’s edition includes updates on the following topics: * Review of 2018 and outlook for 2019 by Katrina Sataki * Highlights from the 6 December ccNSO council meeting * Call for volunteers: The ccNSO seeks additional members to the SOPC and volunteers for the role of ccNSO appointed liaisons to GNSO and ALAC respectively. How to subscribe? We want to ensure you are not receiving unwanted emails. Please fill out this https://goo.gl/forms/WqdlgF6NSi8tM8If1<https://urldefense.proofpoint.com/v2/url?u=https-3A__goo.gl_forms_WqdlgF6NS…> to receive monthly updates by the ccNSO. If you do not wish to receive future ccNSO monthly newsletters, no action from you is needed. You can unsubscribe at any time, via a link in the newsletter itself. Archive Consult the ccNSO Newsletter Archive here: https://community.icann.org/display/ccnsowkspc/ccNSO+Newsletter 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 -- Barrack O. Otieno +254721325277 +254733206359 Skype: barrack.otieno PGP ID: 0x2611D86A

1 0

FY20 Additional Budget Requests and FBSC Decisions
by ICANN At-Large Staff Jan. 20, 2019

Jan. 20, 2019

Dear All, On behalf of Maureen Hilyard, ALAC Chair, please find the FY20 Additional Budget Requests and the FBSC decisions at: https://community.icann.org/display/atlarge/At-Large+FY20+Budget+Developmen… . They will be reviewed during the ALAC Monthly call scheduled for 22 January between 1:00 UTC and 3:00 UTC (see agenda at: https://community.icann.org/display/atlarge/2019-01-22+ALAC+Monthly+Telecon…) Kind regards, ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<http://atlarge.icann.org/> Facebook: facebook.com/icannatlarge<http://www.facebook.com/icannatlarge> Twitter: @ICANNAtLarge<http://www.twitter.com/ICANNAtLarge>

1 0

Fwd: [ccnso-members] CSC Findings on PTI Performance December 2018
by Barrack Otieno Jan. 18, 2019

Jan. 18, 2019

Dear Colleagues, Herewith please find an update to the ccNSO Council that could be of interest to the ALAC. Best Regards ---------- Forwarded message --------- From: Maria Otanes <maria.otanes(a)icann.org> Date: Fri, Jan 18, 2019 at 1:09 AM Subject: [ccnso-members] CSC Findings on PTI Performance December 2018 To: ccnso-members(a)icann.org <ccnso-members(a)icann.org> Dear all, On behalf of the chair of the CSC (Byron Holland), please find included following message and the latest CSC report. All the best, Ria Otanes -------------------------- 17 January 2019 Dear Community Members, As chair of the Customer Standing Committee I am providing you with our December 2018 monthly findings on the performance of Public Technical Identifiers (PTI). I am very pleased to inform you the CSC has concluded that PTI’s overall performance over December 2018 was “Excellent” - PTI met the service level agreement at 100%. The CSC was informed of no escalations. The related PTI report to the CSC, listing the individual service level metrics along with their actual and historical performance, can be found at: https://www.iana.org/performance/csc-reports. I’m also pleased to inform you that at its last meeting on 15 January 2019, and after extensive discussions and hard work the CSC has approved and adopted the amended Remedial Action Procedure (RAP), to meet the requirements of our updated Charter. The amended RAP will become effective after adoption by PTI and publication. The documents can be found on the CSC wikispace: https://community.icann.org/display/CSC/Documents The CSC regular meeting is scheduled at or around the 15th every month, and the CSC report on the PTI performance is sent out shortly after that meeting. If you would like to be informed of upcoming meetings or receive CSC reports directly, you may want to subscribe to our announce list at https://mm.icann.org/mailman/listinfo/csc-announce. Any comments on our reporting to you is welcome. The CSC became effective October 1, 2016. Background information on the committee along with transcripts of our meetings and other useful information can be found at https://www.icann.org/csc[icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_csc&d=Dg…> . Kind regards, Byron Holland Chair CSC _______________________________________________ Ccnso-members mailing list Ccnso-members(a)icann.org https://mm.icann.org/mailman/listinfo/ccnso-members -- Barrack O. Otieno +254721325277 +254733206359 Skype: barrack.otieno PGP ID: 0x2611D86A

1 0