- Gnso-epdp-team - lists.icann.org

Meeting Invitation / Observers / GNSO Temp Spec gTLD RD EPDP-P2 call / Tuesday, 22 October 2019 at 14:00 UTC
by Andrea Glandon Oct. 17, 2019

Oct. 17, 2019

As a result of various requests to facilitate observers to follow the EPDP Phase 2 deliberations in real time, audio cast will be made available for the EPDP plenary meetings. Staff will be monitoring audio cast attendance numbers so that the EPDP leadership can assess its usage. As a reminder, the zoom recording, mp3 recording, chat transcript and transcript of the EPDP plenary meetings will be publicly posted as soon as available on the EPDP wiki page and GNSO master calendar. Dear all, The next meeting of the GNSO Temp Spec gTLD RD EPDP – Phase 2 is scheduled on Tuesday, 22 October 2019 at 14:00 UTC for 120 minutes. (calls will be scheduled for 120 minutes but aim to keep to 90 minutes) 07:00 PDT, 10:00 EDT, 16:00 Paris CEST, 19:00 Karachi PKT, 23:00 Tokyo JST, (Wednesday) 01:00 Melbourne AEDT For other times: https://tinyurl.com/y4ngx989 Agenda Wiki: https://community.icann.org/x/I5ACBw 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…> Meeting Audio Cast (for 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<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Kind Regards, Andrea If needed, an option to join via telephone has been added for this meeting. **New join information - Conference Bridge: Toll-free access number (US and Canada): 800 550 6865 and Toll 213 233 3193 Other telephone numbers found here: http://www.adigo.com/icann [adigo.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.adigo.com_icann&d=D…> Enter passcode on telephone: 7349

1 0

**On in 15 minutes** Meeting Invitation / Observers / GNSO Temp Spec gTLD RD EPDP-P2 call / Thursday, 17 October 2019
by Julie Bisland Oct. 17, 2019

Oct. 17, 2019

**On in 15 minutes** As a result of various requests to facilitate observers to follow the EPDP Phase 2 deliberations in real time, audio cast will be made available for the EPDP plenary meetings. Staff will be monitoring audio cast attendance numbers so that the EPDP leadership can assess its usage. As a reminder, the zoom recording, mp3 recording, chat transcript and transcript of the EPDP plenary meetings will be publicly posted as soon as available on the EPDP wiki page and GNSO master calendar. Dear all, The next meeting of the GNSO Temp Spec gTLD RD EPDP – Phase 2 is scheduled on Thursday, 17 October 2019 at 14:00 UTC for 120 minutes. (calls will be scheduled for 120 minutes but aim to keep to 90 minutes) 07:00 PDT, 10:00 EDT, 16:00 Paris CEST, 19:00 Karachi PKT, 23:00 Tokyo JST, (Friday) 01:00 Melbourne AEDT For other times: https://tinyurl.com/y3gx4fla [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_y3gx4fla&d…> Agenda Wiki: https://community.icann.org/x/A4YCBw 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…> Meeting Audio Cast (for 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<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Kind Regards, Terri If needed, an option to join via telephone has been added for this meeting. **New join information - Conference Bridge: Toll-free access number (US and Canada): 800 550 6865 and Toll 213 233 3193 Other telephone numbers found here: http://www.adigo.com/icann [adigo.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.adigo.com_icann&d=D…> Enter passcode on telephone: 7349

1 0

**Reminder** Meeting Invitation / Observers / GNSO Temp Spec gTLD RD EPDP-P2 call / Thursday, 17 October 2019
by Julie Bisland Oct. 16, 2019

Oct. 16, 2019

As a result of various requests to facilitate observers to follow the EPDP Phase 2 deliberations in real time, audio cast will be made available for the EPDP plenary meetings. Staff will be monitoring audio cast attendance numbers so that the EPDP leadership can assess its usage. As a reminder, the zoom recording, mp3 recording, chat transcript and transcript of the EPDP plenary meetings will be publicly posted as soon as available on the EPDP wiki page and GNSO master calendar. Dear all, The next meeting of the GNSO Temp Spec gTLD RD EPDP – Phase 2 is scheduled on Thursday, 17 October 2019 at 14:00 UTC for 120 minutes. (calls will be scheduled for 120 minutes but aim to keep to 90 minutes) 07:00 PDT, 10:00 EDT, 16:00 Paris CEST, 19:00 Karachi PKT, 23:00 Tokyo JST, (Friday) 01:00 Melbourne AEDT For other times: https://tinyurl.com/y3gx4fla [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_y3gx4fla&d…> Agenda Wiki: https://community.icann.org/x/A4YCBw 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…> Meeting Audio Cast (for 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<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Kind Regards, Terri If needed, an option to join via telephone has been added for this meeting. **New join information - Conference Bridge: Toll-free access number (US and Canada): 800 550 6865 and Toll 213 233 3193 Other telephone numbers found here: http://www.adigo.com/icann [adigo.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.adigo.com_icann&d=D…> Enter passcode on telephone: 7349

1 0

ICANN66: GNSO Sessions How to Get Organized and Remote Participation Details
by Julie Bisland Oct. 15, 2019

Oct. 15, 2019

Dear all, The one-stop wiki page for all your Remote Participation queries is now available. This wiki page covers remote participation details for all GNSO open and public meetings. In addition to this, ICANN Meetings’ Team has put together an updated ICANN meeting website which allows you to download all GNSO-related meetings to your inbox calendar in one go. 2 LINKS TO BOOKMARK NOW: ICANN66 Meeting Schedule<https://66.schedule.icann.org/> GNSO Remote Participation Wiki Page<https://community.icann.org/x/LYvkBg> Step 1 – Create a profile and your personalized ICANN66 schedule Go to the Meeting Schedule webpage and create a profile and login. Every session on the full schedule can be selected and added to your individual schedule by clicking the Add box to the bottom right of each meeting, this adds it to your individual schedule which you can then email to yourself or add to your calendar. See next step. Step 2 - There are two ways to import your schedule into Outlook: once you’ve added all your chosen meetings to “My Schedule” go to Export. · Downloading creates a one-time snapshot of your schedule and copies it into Outlook. If you subsequently make changes to your Pathable calendar, they will not be reflected in Outlook. · Subscribing creates a live feed of your schedule in Outlook. Outlook checks for changes every few hours and updates your calendar appropriately. Step 3 All sessions allowing remote participation will use Zoom rooms. You can find the Zoom room links for public meetings on the ICANN66 Meeting Schedule<https://66.schedule.icann.org> and on the <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> GNSO Remote Participation Wiki Page<https://community.icann.org/x/LYvkBg>. Zoom access details for closed meetings will be communicated separately. There are three options to connect your audio: 1) Via VoIP, choose Computer Audio 2) Getting a dial out from Zoom to your phone, choose Call Me 3) Phoning into the audio bridge (access numbers and Meeting ID are provided for that option), choose Telephone Audio If you cannot log into the Zoom room, but wish to connect via telephone only, to dial into the audio refer to the GNSO Remote Participation Wiki Page<https://community.icann.org/x/LYvkBg> for access numbers and individual Meeting IDs. Step 4 Please download the mobile app by searching for “ICANN Meetings” in your app stores. Nathalie Peregrine and Terri Agnew will be onsite in Montreal to assist you directly. For all GNSO meeting related queries (RP or others), please email us at: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team -- Julie Bisland GNSO SO/AC Support coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Email: julie.bisland(a)icann.org<mailto:julie.bisland@icann.org> Skype ID: 79613b691cb8a6c1 Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> See All SO and AC events on the ICANN Global calendar<https://features.icann.org/calendar>

1 0

Proposed Agenda - EPDP Team Meeting #25 on Thursday 17 October 2019
by Marika Konings Oct. 14, 2019

Oct. 14, 2019

Dear EPDP Team, Please find below the proposed agenda for the next EPDP Team meeting which is scheduled for Thursday 17 October at 14.00 UTC. Prior to the meeting, please: * Make sure you have reviewed the updates made to the accreditation building block following last week’s meeting. If there is any violent disagreement with the updates made to the policy principles, please flag those in advance of Thursday’s meeting to plan accordingly as the expected focus is to be on the implementation guidance section. * Put forward ideas/suggestions for policy recommendations and/or implementation guidance that should be included as part of the terms of use / disclosure agreements / privacy policies building block. Best regards, Caitlin, Berry and Marika =============================== EPDP Phase 2 - Meeting #25 Proposed Agenda Thursday, 17 October 2019 at 14.00 UTC 1. Roll Call & SOI Updates (5 minutes) 2. Confirmation of agenda (Chair) 3. Welcome and housekeeping issues (Chair) (5 minutes) a) Update from legal committee b) Status of building blocks<https://community.icann.org/x/k5ICBw> 4. Accreditation<https://docs.google.com/document/d/1zAEBygpoddKOJOfb1whMtaQHcik856aZZc9BoDk…> (building block f and j) – second reading continued (30 minutes) a) Overview of implementation guidance section b) Feedback from EPDP Team c) Confirm next steps 5. Financial Sustainability<https://docs.google.com/document/d/1Ci-wvA1P9yoKjJ5DPeRbZ5FOHL2D8ExGsN2SV9T…> (building block n) – second reading a) Overview of updates made following first reading b) Feedback from EPDP Team c) Confirm next steps 6. Terms of use / disclosure agreements / privacy policies<https://docs.google.com/document/d/1eZBzRclRtEXPp1EScDfftnfnv9tneD7ovxmGe84…> (building block m) – first reading a) Review building block b) Feedback from EPDP Team c) Confirm next steps 7. Wrap and confirm next EPDP Team meeting (5 minutes): a) Tuesday 22 October 2019 at 14.00 UTC b) Confirm action items c) Confirm questions for ICANN Org, if any Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>.

1 0

schedule problem: Legal vs. Natural issue
by Greg Aaron Oct. 14, 2019

Oct. 14, 2019

The Phase 1 report said: "EPDP Team Recommendation #17. 1) The EPDP Team recommends that Registrars and Registry Operators are permitted to differentiate between registrations of legal and natural persons, but are not obligated to do so. 2) The EPDP Team recommends that as soon as possible ICANN Org undertakes a study, for which the terms of reference are developed in consultation with the community, that considers: * The feasibility and costs including both implementation and potential liability costs of differentiating between legal and natural persons; * Examples of industries or other organizations that have successfully differentiated between legal and natural persons; * Privacy risks to registered name holders of differentiating between legal and natural persons; and * Other potential risks (if any) to registrars and registries of not differentiating. 3) The EPDP Team will determine and resolve the Legal vs. Natural issue in Phase 2." The homework above looks like a pre-requisite for completing the charter and delivering the Final Report, but AFAIK it is not underway. How are we going to solve this dilemma? I note that some guidance about the above is contained in the Bird & Bird "legal versus natural" memo delivered at the end of Phase 1. All best, --Greg

4 4

Post Call | GNSO Temp Spec gTLD RD EPDP – Phase 2 - Small Call| Friday, 11 October 2019 at 13:00 UTC
by Terri Agnew Oct. 11, 2019

Oct. 11, 2019

Dear all, All recordings for the GNSO Temp Spec gTLD RD EPDP – Phase 2 – Small Call held on Friday, 11 October 2019 at 13:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/XoAzBw> (attendance included). These include: * Attendance (please let me know if your name has been left off the attendance list) * Audio recording * Zoom chat archive * Zoom recording (including audio, visual, rough transcript) As a reminder only members and alternates can join the call, observers can listen to the recordings and read the zoom transcript afterwards. For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-epdp-team/> and the main wiki page<https://community.icann.org/x/IYEpBQ>. Thank you. With kind regards, Terri

1 0

Notes and action items - EPDP Phase 2 Meeting #24 - 10 October 2019
by Caitlin Tubergen Oct. 11, 2019

Oct. 11, 2019

Dear EPDP Team, Please find below the notes and action items from today’s EPDP meeting. The next EPDP meeting will be Thursday, 17 October at 1400 UTC. Best regards, Marika, Berry, and Caitlin -- EPDP Phase 2 - Meeting #24 Thursday, 10 October 2019 at 14.00 UTC Action Items Based on today’s meeting discussion, Support Staff to update the accreditation principles (Building Block F/J) via the Google Doc. EPDP Team to review and comment on updated principles by Wednesday, 16 October. Notes These high-level notes are designed to help the EPDP Team navigate through the content of the call and are not meant as a substitute for the transcript and/or recording. The MP3, transcript, and chat are provided separately and are posted on the wiki at: https://community.icann.org/x/ZwPVBQ. 1. Roll Call & SOI Updates (5 minutes) · Please remember to review your SOIs on a regular basis and update as needed. Updates are required to be shared with the EPDP Team. 2. Confirmation of agenda (Chair) 3. Welcome and housekeeping issues (Chair) (5 minutes) a) Status of letter to ICANN Board · The EPDP Team has been discussing the last sentence of the draft letter. · The circulated language was discussed by board liaisons · Is the consternation over the last sentence of the letter, or sending the letter more generally? · Issue with final sentence - it is not clear the EPDP Team needs to abandon the centralized model. If ICANN cannot answer the question, the EPDP Team will assume that ICANN is unwilling to do this, and the EPDP Team will draft policy recommendations accordingly. · The GAC has not objected to the letter, but strong language will help express the urgency of the situation. The Team should ask for a written response from ICANN. The language may be reworded so that it’s not a zero-sum situation. · In the second paragraph, the last sentence may need an update. · The original text was less definitive, and the proposed rewrite, in consultation with the board liaisons, made the question stronger. Perhaps revert to the original language. · Removing the last sentence entirely invalidates the point of sending the letter. · Time is of the essence, so the Team should not iterate indefinitely. · Action: EPDP Team members to send updated draft text to James immediately following the call. James to distribute updated version of the letter to the EPDP Team for 2 hours of silent procedure. b) Status of building blocks · Building Block A is closed and will be included in the Initial Report · Support Staff made updates to Building Block E - EPDP Team has 24 hours to flag additional issues · All other building blocks are under development 4. Accreditation [docs.google.com] (building block f and j) – second reading continued (30 minutes) a) Overview of updates made · As noted on the Team’s last call, Support Staff distributed the accreditation building block document, which incorporates input provided from the group’s submissions. The document separates policy principles and implementation-related guidance. · Nothing in the document has been agreed to; this is a Support Staff proposal based on the input received to date. · In certain areas, there may need to be further clarity on who is responsible for what. · The definitions that have been included were from Alex’s document, but the definitions have not been cross-checked with the draft text of the building block. b) Feedback from EPDP Team Principle a: · Concerned with why individuals cannot be accredited. · What is the reason for this? · Some team members argue that organizations can be more easily verified, while this is difficult to do with individuals. However, this can be removed if no agrees. · Could it be possible that only individuals or legal entities would have access to certain types of justifications for request? For example, a law enforcement officer may need to request on behalf of an LEA not on behalf of itself. There could be a distinction, not a prohibition. · Accredited entities can be both legal and natural persons. · The uniform baseline application for legal persons may be different than natural persons. · Why are non-accredited entities prohibited from sending in requests? · Oppose SSAD being limited to only certain types of users · Do not support limiting the system to accredited users only · Almost all individuals will be associated with a business · Accredited entities may be legal persons and individuals. Principle b: · Pointing out a trademark requirement is not appropriate here, or come up with a better example · Remove the example · Add the point that the baseline approach may be different for individuals vs. legal persons Principle c: · “Or automate” should be deleted b/c there is a logical issue in the statement · Adopt Brian K’s suggestion - “accreditation alone must not” · Review of the request could be automated, but not the disclosure of information · Accreditation is not purely for authentication of identity - it could be a wider verification than just knowing who the person is - an individual could submit to a code of conduct, for example · Is it worth starting out with the definition of terms authentication, accreditation, automation? · Staff to reword the “or automate” language Principle d: · Agree with this in principle, but more detail is needed from an operational perspective · System abuse could be an example of why de-accreditation occur, rather than having it as a definitive statement. As an example, there may be situations where trademark holder may lose a trademark - in that sense, if demonstrating that holding a valid trademark is a prerequisite to accreditation, losing the trademark could warrant de-accreditation. · Using “abuse” should not be the only reason for de-accreditation. For example, would violating the code of conduct be considered system abuse? · “in case of system abuse or in cases where pre-requisites for accreditation no longer exist” · In the BC proposal, there is a renewal procedure. The renewal process would require individuals and entities to confirm the accreditation criteria still exist. · Insert full stop after de-accreditation and insert examples of when de-accreditation may occur. Principle e: · Brian suggested changing clearinghouse to clearinghouses (no disagreement) Principle f: · No objections Principle g: · It’s not clear that this entity would be an accreditation authority or a sub-contractor. · Agree with this principle, but operationalizing this principle is subject to interpretation. More detail is needed here - for example, what information is subject to an audit, what information is not subject to an audit, etc. · With respect to auditing, the Team agreed to have a separate building block for auditing. The suggestions could be included in the new building block. Principle h: · G and H could be merged Principle i: · This should be considered in the financial considerations building block · This should be replaced completely with “the accreditation service may be part of a cost-recovery system” · Replace “must” with “likely” · Drop the second sentence, with the understanding that there are additional considerations with respect to the financial model · It is absolutely critical to have principles related to cost causation and cost recovery and the assignment of cost to specific parties; however, rates should not be determined at this stage · Individuals who are accredited and the entities who are accrediting must be self-sustaining · Elements of cost associated with accreditation need to be discussed in building block M Principle j: · Do not see the benefit of this bullet · Should be updated to entities and individuals · This does have merit b/c the Team wants to ensure that regular users are accredited to minimize the work. If there is a group such as IP attorneys or security researchers, this should be streamlined as much as possible. · What does the Team expect as the outcome of this statement? It’s unclear how to implement this. The statement should be dropped altogether. · Proposal to delete this point completely. Principle k: · The idea is that after accreditation that particular entity or individual is recognized as accredited. · Support Staff to reword to clarify. · “Confirm” is confusing everyone - change this word to make this clear · Support Staff to review Hadia’s input and Marc A’s input when updating this principle Principle l: · Wording needs to be tightened here · Accreditation should be renewed periodically should be added as an additional policy principle. c) Confirm next steps · Based on today’s meeting discussion, Support Staff to update the accreditation principles via the Google Doc. EPDP Team to review and comment on updated principles by Wednesday, 16 October. · EPDP Team to review Hadia’s message in advance of the next meeting. · The question regarding RDAP overlaps with principle k. 5. Receipt of acknowledgement [docs.google.com] (building block k) – second reading (15 minutes) a) Overview of updates made following first reading b) Feedback from EPDP Team · No objections to reworded text - this building block is now complete c) Confirm next steps 6. Response requirements / expectations, including timeline/SLAs [docs.google.com] (building block g) – first reading (15 minutes) a) Review building block · Does the group want to check back in on Phase 1 recommendations and Phase 1 implementation, or would the group prefer to take a clean-state approach? · Should sometime be added here about technical failures? · Would this be different if this is a centralized or decentralized model? · It may be helpful to read the questions below the building block to show what the building block is scheduled to address. b) Feedback from EPDP Team c) Confirm next steps 7. Wrap and confirm next EPDP Team meeting (5 minutes): a) Thursday 18 October 2019 at 14.00 UTC b) Confirm action items c) Confirm questions for ICANN Org, if any

1 0

Re: [Gnso-epdp-team] [Board-Ops-Team] EPDP Phase 2 Team letter to ICANN Board Re. SSAD
by Wendy Profit Oct. 10, 2019

Oct. 10, 2019

Dear Marika, Thank you for forwarding the letter from the EPDP Phase 2 team to the Board. We are hereby acknowledging receipt on behalf of the Board and confirming the letter was forwarded to them. The letter was also forwarded internally for further processing. Thank you, Wendy Profit ICANN Board Operations Senior Manager 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 From: Board-Ops-Team <board-ops-team-bounces(a)icann.org> on behalf of Marika Konings <marika.konings(a)icann.org> Date: Thursday, October 10, 2019 at 3:04 PM To: ICANN Board Ops <board-ops-team(a)icann.org> Cc: Goran Marby <goran.marby(a)icann.org>, "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [Board-Ops-Team] EPDP Phase 2 Team letter to ICANN Board Re. SSAD Dear Board Ops Team, On behalf of the EPDP Phase 2 Team, please find attached correspondence to ICANN Board regarding the Standardized System for Access/Disclosure (SSAD). Best regards, Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>.

1 0

EPDP Phase 2 Team letter to ICANN Board Re. SSAD
by Marika Konings Oct. 10, 2019

Oct. 10, 2019

Dear Board Ops Team, On behalf of the EPDP Phase 2 Team, please find attached correspondence to ICANN Board regarding the Standardized System for Access/Disclosure (SSAD). Best regards, Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>.

1 0