Sorry, typo, I meant in STEP 2! From: Gnso-epdp-team <gnso-epdp-team-bounces@icann.org> On Behalf Of Mueller, Milton L Sent: Thursday, October 10, 2019 10:01 AM To: Hadia Abdelsalam Mokhtar EL miniawi <Hadia@tra.gov.eg>; Marika Konings <marika.konings@icann.org>; gnso-epdp-team@icann.org Subject: Re: [Gnso-epdp-team] Proposed Agenda - EPDP Team Meeting #24 Thursday 10 October at 14.00 UTC Hi, Hadia If I understand what you are saying here, you are assuming that accreditation also means authorization. We have already ruled that out. Getting accredited will most certainly not mean that anyone accredited gets all they can eat access to any request. If that is not what you mean, please tell us who does the authorization mentioned in step 1. --MM From: Gnso-epdp-team <gnso-epdp-team-bounces@icann.org<mailto:gnso-epdp-team-bounces@icann.org>> On Behalf Of Hadia Abdelsalam Mokhtar EL miniawi Sent: Thursday, October 10, 2019 9:48 AM To: Marika Konings <marika.konings@icann.org<mailto:marika.konings@icann.org>>; gnso-epdp-team@icann.org<mailto:gnso-epdp-team@icann.org> Subject: Re: [Gnso-epdp-team] Proposed Agenda - EPDP Team Meeting #24 Thursday 10 October at 14.00 UTC Hi all, In attempt to answer the charter questions " How can RDAP, that is technically capable, allow Registries/Registrars to accept accreditation tokens and purpose for the query?" here are some initial thoughts . The answer to this question will depend on the model being used. If we are using the TSG proposed model in which the data resides with the contracted parties and nonpublic gTLD data is only transferred through ICANN, so ICANN is the RDAP gateway, the following steps will take place 1. The requestor is accredited and each requestor is given a unique identifier 2. The requestor (based on the purpose) is authorized to access a certain set of nonpublic gTLD data and given related attributes 3. The system associates a unique attribute to the requestor and a unique identifier to the each request 4. These attributes are passed to the ICANN RDAP 5. The system is capable of passing the requestors attributes the CP RDAP, whether this will be required or not is something we need to decide. So we have two Scenarios: 1. ICANN RDAP receives the attributes and makes the requests to the CP RDAP without passing the attributes 2. ICANN RDAP receives the attributes and passes it to the CP RDAP Please note that this analysis does not consider the authorization or authentication entity. So as I see it there is no extra requirements associated with the accreditation. It is just one extra step at the very beginning. Best Hadia From: Gnso-epdp-team [mailto:gnso-epdp-team-bounces@icann.org] On Behalf Of Marika Konings Sent: Tuesday, October 08, 2019 10:38 PM To: gnso-epdp-team@icann.org<mailto:gnso-epdp-team@icann.org> Subject: Re: [Gnso-epdp-team] Proposed Agenda - EPDP Team Meeting #24 Thursday 10 October at 14.00 UTC Please note that the hyperlink for item 4 was incorrect. This should have been fixed now. Best regards, Caitlin, Berry and Marika From: Gnso-epdp-team <gnso-epdp-team-bounces@icann.org<mailto:gnso-epdp-team-bounces@icann.org>> on behalf of Marika Konings <marika.konings@icann.org<mailto:marika.konings@icann.org>> Date: Tuesday, October 8, 2019 at 14:04 To: "gnso-epdp-team@icann.org<mailto:gnso-epdp-team@icann.org>" <gnso-epdp-team@icann.org<mailto:gnso-epdp-team@icann.org>> Subject: [Gnso-epdp-team] Proposed Agenda - EPDP Team Meeting #24 Thursday 10 October at 14.00 UTC Dear EPDP Team, Please find below the proposed agenda for the next EPDP Team meeting which is scheduled for Thursday 10 October at 14.00 UTC. Best regards, Caitlin, Berry and Marika EPDP Phase 2 - Meeting #24 Proposed Agenda Thursday, 10 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) Status of letter to ICANN Board b) Status of building blocks<https://community.icann.org/x/k5ICBw> 4. Accreditation<https://docs.google.com/document/d/1zAEBygpoddKOJOfb1whMtaQHcik856aZZc9BoDk3...> (building block f and j) – second reading continued (30 minutes) a) Overview of updates made b) Feedback from EPDP Team c) Confirm next steps 5. Receipt of acknowledgement<https://docs.google.com/document/d/1dSepSTKmaceu3oB1YLpp1wgdrJoERIQq7fg_8Ud-...> (building block k) – second reading (15 minutes) a) Overview of updates made following first reading b) Feedback from EPDP Team c) Confirm next steps 6. Response requirements / expectations, including timeline/SLAs<https://docs.google.com/document/d/1KqfkWfbC6gBIrmE3OTTw7MYpThciaMc03Lu6M9sk...> (building block g) – first reading (15 minutes) a) Review building block 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 Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings@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_gns...>.