May 2021 - GNSO-TPR - lists.icann.org

Notes and action items - TPR WG Meeting #2 - 21 May 2021
by Caitlin Tubergen 21 May '21

21 May '21

Dear TPR WG, Please find below the notes from today’s TPR Meeting #2. As a reminder, the next TPR meeting will be Tuesday, 25 May at 16:00 UTC. We wish everyone a wonderful weekend. Best regards, Emily, Berry, and Caitlin Transfer Policy Review PDP Meeting #2 21 May 2021, 18:00 UTC Meeting Notes 1. Roll Call & SOI Updates (5 minutes) 2. Welcome & Chair updates (Chair) (5 minutes) * For the first few weeks of meetings, the team will be reviewing all of the topics and associated charter questions. We’ll be deciding if the topic is small, medium, or large or, said another way, easy, medium, difficult. * We will discuss the topic broadly to ensure everyone understands it and gather initial feelings of difficulty. * We will also denote potential dependencies (if any). * Following review of the charter questions, does the WG think anything is missing? * We will be using the charter questions as the outreach questions for SOs/ACs. * A few weeks from now, we should have a general road map for how long Phase 1A and Phase 1B will take. * The Support Staff Team needs more information regarding the context of the topics. As we review through the policy topics and charter questions, please think about roughly how long deliberations on a particular topic may take. For each one of these topics, we will utilize “the crank”. We will discuss, staff will document, and the WG will arrive at preliminary conclusions and preliminary recommendations. * This review covers two primary tasks: (i) production of a work plan with reasonable delivery dates back to the Council; (ii) preliminary outreach to the SOs/ACs – this discussion will assist in arriving at the final outreach model. * In terms of the duration, how long will it take for the WG to deliberate these topics – this will entail determining the complexity of the issue and how far apart the group is on the issue. * We will not be using a calendar-based approach for this assessment. Instead, how many hours of on-call deliberations will it likely take for the group to move through this topic? * This discussion is critical for developing the project plan. * Can some of these topics be discussed in parallel or are there dependencies? For example, is there a dependency to getting to preliminary conclusions on Gaining and Losing FOAs, or can the group discuss Auth-info codes in parallel? It’s critical for the group to flag dependencies during this exercise. 3. High-level Review of Phase 1A Charter Topics & Charter Questions (30 minutes) * Gaining and Losing FOAs * We will review terminology everyone should be familiar with for the first charter topic. * Gaining Registrar: The registrar to which the registrant is transferring the domain name. * Losing Registrar: The registrar from which the registrant is transferring the domain name. * Gaining Form of Authorization: A required form sent by the Gaining Registrar to the Registered Name Holder to confirm the Registered Name Holder’s intent to transfer the domain name. * Typically an email to Registered Name Holder to confirm intent by clicking a designated link. * Losing Form of Authorization: Losing Registrar sends the Registered Name Holder a notice to confirm Registered Name Holder’s intent to transfer. * EPDP included the workaround from the Temporary Specification in its recommendations, which were adopted by the ICANN Board. * Registrars identified challenges in ICANN org’s position that a Gaining Registrar is required to send a Gaining FOA where the email address “is available”, as there is no guarantee that the email goes directly to the registrant. * ICANN Board passed a resolution to defer contractual compliance enforcement of the Gaining FOA requirement pending further work in this area. * Contracted Party House Tech Ops Subcommittee has developed a proposal for a proposed transfer process. * Auth-Info Code * What is the auth-info code? * Unique code created by a registrar on a per-domain basis to identify the registrant of the domain name. * How is the auth-info code used? * AuthInfo Code needs to be provided to the gaining registrar as part of the inter-registrar transfer process. * How is it provided? * Losing registrar may provide AuthInfo Code via control panel, or by other means within 5 calendar days (email, SMS, etc). * EPDP Rec. 27. * Recommendation 27 in the EPDP Team’s Phase 1 Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-gtld…> recommends updating existing policies / procedures to ensure consistency with the EPDP’s outputs. * In its Wave 1 Report, ICANN org performed a detailed analysis of 15 policies and procedures, including the Transfer Policy and Transfer Dispute Resolution Policy. * There are items in the Wave 1 report related to FOA, Change of Registrant, and TDRP. * For Wave 1 report items related to each topic, the Working Group will consider how the issues should be addressed and whether any need to be resolved urgently. * How will these issues be addressed, and there is anything that needs to be resolved urgently? 4. Phase 1A Charter Topic #01 Discussion – Gaining FOA (30 minutes) * The effort for the FOA should be relatively easy. * Based on the tentative removal of this requirement due to GDPR, we can likely sunset the gaining FOA soon. * The Gaining FOA is very different from the Losing FOA since it requires an action by registrant. It was an automated process. Because some information is redacted, it could not work anymore. It’s been almost 3 years since this requirement was removed, and there does not seem to have been an increase or uptick in unauthorized transfer request, which seems to indicate the requirement can be removed. * How long will this issue take for the Team to deliberate this? * This should not take much time. * Small to medium effort for this topic. * Seems most agree that we should eliminate the FOA, and the level of effort will be small or medium. 5. Phase 1A Charter Topic #02 Discussion – Losing FOA (15 minutes and time permitting) – - Tech Ops process is a helpful starting point for this work, so the amount of work to make this decision is lower. Would scope this as low. - Keeping the Losing FOA makes sense, but there may be changes to the Losing FOA - Suggest review of available data for this question and the gaining FOA question - If there is no source of compliance data, take it at face value and move forward. - Are there any concerns about the registrant not able to get the auth-code from the registrar? The group should look into this - If we keep locks, we should document why. - For the level of effort associated with locking – this could be a large issue – it may be a medium effort. - If the lock were to go away, a name could be hijacked multiple times in a matter of days. - Is 60 days the correct number? - Is it possible to have a trusted mechanism in terms of a registrant actually initiating this request? - There seems to be widespread misunderstanding of the locking issue. It may be interesting to see some data from ccTLDs regarding this. If this is a permissive regime, there should be some consideration if it is affirmatively required to registrants. This is a medium issue. - There are multiple locks – for example, a 60-day lock after change of registrant that the registrant can opt out of Auth Codes - The Tech Ops paper has a lot of feedback on this issue - This topic is tough – should there be an automatic ACK? This is really the hardest question to answer regarding the original transfer process. It is a large issue. - There are many registrants who do not understand what an auth-code is and how to use it. It’s difficult to get the auth-code. May need to consider processes that enable the registrant to get the auth-code more easily. - Is it worth discussing these issues prior to FOA discussions? - There are two important parts of an auth-code – identifying a registrant and on the backend in the case of the incumbent registrar, there were some discussions about the role of the registry in auth-code management. This issue deserves a fair amount of discussion. If the auth code is properly managed, this could establish a proper paper trail. This is a high-touch topic. - The WG seems open to discussing the auth-info code prior to deliberating on the FOAs. 6. Next steps & closing (5 minutes) – - WG members should have received 3 invites. The tentative meeting time is Tuesdays at 16:00 UTC. - The 1 June meeting will be 60 minutes so as not to interfere with the GNSO Policy webinar. There will be also be a break the week after ICANN71. - We will review this time in the coming weeks to make sure it still works for everyone.

1 0

Meeting Invitation | Observers | Transfer Policy Review PDP WG call | Tuesday, 25 May 2021 at 16:00 UTC
by Andrea Glandon 21 May '21

21 May '21

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 25 May 2021 at 16:00 UTC for 90 minutes. Join the Zoom Webinar: https://icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/95363727469?pwd=N3A3OWFS…> Passcode: @TP/^*4wg# Observers will have ability to join the call via Zoom Webinar, and will be able to view members’ chat as well as information shared in the Zoom Webinar room. Observers will not be able to use chat or raise hands. The recordings and transcriptions of the calls will be posted on the GNSO Master Calendar page: https://gnso.icann.org/en/group-activities/calendar [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…> Before joining the call: Please be sure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en> Visit the Wiki Agenda meeting page: https://community.icann.org/x/4wjQCQ Check your time zone: https://tinyurl.com/y5m7k372 Audio only: One tap mobile: US: +19294362866,,95363727469#,,,,*7490739013# or +13017158592,,95363727469#,,,,*7490739013# Telephone: Dial (for higher quality, dial a number based on your current location): US: +1 929 436 2866 or +1 301 715 8592 or +1 312 626 6799 or +1 669 900 6833 or +1 253 215 8782 or +1 346 248 7799 or 888 788 0099 (Toll Free) or 877 853 5247 (Toll Free) Webinar ID: 953 6372 7469 Passcode: 7490739013 International numbers available: https://icann.zoom.us/u/acdLFXPLp6 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/acdLFXPLp6__;!!PtGJab4!v…> Thank you. Kind regards, Andrea

1 0

**REMINDER** Meeting Invitation | Observers | Transfer Policy Review PDP WG call | Friday, 21 May 2021 at 18:00 UTC
by Julie Bisland 20 May '21

20 May '21

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Friday, 21 May 2021 at 18:00 UTC for 90 minutes. Join the Zoom Webinar: https://icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/95363727469?pwd=N3A3OWFS…> Passcode: @TP/^*4wg# Observers will have ability to join the call via Zoom Webinar, and will be able to view members’ chat as well as information shared in the Zoom Webinar room. Observers will not be able to use chat or raise hands. The recordings and transcriptions of the calls will be posted on the GNSO Master Calendar page: https://gnso.icann.org/en/group-activities/calendar [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…> Before joining the call: Please be sure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en> Visit the Wiki Agenda meeting page: https://community.icann.org/x/5AXQCQ Check your time zone: https://tinyurl.com/2f3zddzs [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2f3zddzs__;!!PtGJab4!ox-nAJs…> Audio only: One tap mobile: US: +19294362866,,95363727469#,,,,*7490739013# or +13017158592,,95363727469#,,,,*7490739013# Telephone: Dial (for higher quality, dial a number based on your current location): US: +1 929 436 2866 or +1 301 715 8592 or +1 312 626 6799 or +1 669 900 6833 or +1 253 215 8782 or +1 346 248 7799 or 888 788 0099 (Toll Free) or 877 853 5247 (Toll Free) Webinar ID: 953 6372 7469 Passcode: 7490739013 International numbers available: https://icann.zoom.us/u/acdLFXPLp6 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/acdLFXPLp6__;!!PtGJab4!v…> Thank you. Kind regards, Julie -- Julie Bisland GNSO SO/AC Support coordinator Internet Corporation for Assigned Names and Numbers (ICANN) 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…>

1 0

Welcome to the Transfer Policy PDP WG
by Roger D Carney 18 May '21

18 May '21

Dear Working Group members, Welcome to the Working Group tasked with reviewing the Transfer Policy. I'm looking forward to working with all of you on this PDP. You should have received an invite for our first meeting, which is scheduled for this Friday, 14 May at 18:00 UTC, though not ideal for some, we did want to get moving and in our first meeting we will select a more agreeable reoccurring date/time for our regular meetings going forward. I want to share a few notes in advance of our first meeting to help ensure that we can get through all of the start-up tasks for the Working Group in a timely manner. In preparation for the first meeting, please take the time to begin familiarizing yourself with the following materials: * Working Group Charter<https://community.icann.org/display/TPRPDP/2.+WG+Charter> * Final Issue Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/final-iss…> * Transfer Policy<https://www.icann.org/resources/pages/transfer-policy-2016-06-01-en> * Consensus Playbook<https://gnso.icann.org/sites/default/files/file/field-file-attach/pdp-3-4-c…> * GNSO Working Group Guidelines<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-1-g…> & PDP Manual<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-p…> * ICANN70 session providing an introduction to the PDP<https://icann.zoom.us/rec/play/dK9qk08zEpYxTFWJSz7qomUQhdr9z-lbkWRYQN7D1TAR…> By the second Working Group meeting, I will expect that everyone has carefully read all of these documents. Once you have completed your document review, please confirm here<https://docs.google.com/forms/d/e/1FAIpQLSe3xz-e80x6moG8KSRDbCgYQOTN1Er6PYu…>. The goal of this exercise is to ensure that everyone is starting off on the same page with the same foundation of information, which will enable us to be a more effective team. In addition, a document library is included on the Working Group's workspace (see https://community.icann.org/x/UIaUCQ). An understanding of these documents and their contents will help to ensure your full and productive participation in Working Group deliberations. The following items will be on the agenda for the first meeting: 1. Introductions: As standard practice during the first meeting of a PDP WG, members will do a round of verbal introductions so we can get to know each other. Please be prepared to speak briefly (no more than two minutes) about your relevant experience/background and any objectives you have for participating. 2. Vice Chair: We have an opportunity to select one or two Vice Chairs for this Working Group, but we are not required to do so. For now, I would suggest that we proceed without a Vice Chair and revisit the topic if necessary in the future. 3. Charter: It would be helpful if everyone could read through the Charter<https://community.icann.org/display/TPRPDP/2.+WG+Charter> before the first call. We will briefly go over some key points and answer any questions that members have. 4. Operating Mode/Working Methods: In our first meeting, we'll talk about some of the logistical elements of how we will work, including the decision-making process for this Working Group. We'll also review what is expected of those participating in this Working Group. From the outset, I would like to emphasize the importance of working towards developing consensus recommendations, which means working constructively and collaboratively to find outcomes that members can ultimately accept. To this end, the Consensus Playbook<https://gnso.icann.org/sites/default/files/file/field-file-attach/pdp-3-4-c…> is among the resources that you are being asked to read by the second meeting. We'll be drawing on the methods and techniques in the playbook throughout the life of the PDP, so everyone should be familiar with it. 5. Work Plan: On our first call, we will have an opportunity to speak a bit about the Work Plan and what can be expected in our first weeks of work on this PDP. As a preview, the initial areas of focus will be: * High-level review of the topics within the Charter for Phase 1 * Prepare to request input from SO/AC/SG/Cs on topics in Phase 1 * Deliver Phase 1 Work Plan to GNSO Council 1. Meeting Frequency and Schedule: We'll have an opportunity to discuss the meeting frequency and the proposed day/time of the calls. I look forward to seeing all of you on the call. Thanks Roger

8 11

Proposed approach for initial meetings and agenda for meeting #2 on Friday 21 May 2021 at 18.00 UTC
by Emily Barabas 18 May '21

18 May '21

Dear Working Group members, Thank you all for joining Friday’s kick-off meeting. On the call, we spoke briefly about the areas of focus for the first weeks of Working Group: * High-level review of the topics within the Charter for Phase 1 * Prepare to request input from SO/AC/SG/Cs on topics in Phase 1 * Deliver Phase 1 Work Plan to GNSO Council In support of these three objectives, please find attached a proposed approach to conducting the high-level review of the topics within Phase 1. Please read the attached and share any questions on the mailing list. Below, drawing on this approach, you will find a proposed agenda for the Working Group meeting scheduled to take place on Friday 21 May 2021 at 18.00 UTC. In addition, two reminders in advance of Friday’s meeting: * Members, please complete the doodle poll to assist with finding a permanent time slot for Working Group meetings. * Please complete the background reading (see slide 19 here<https://community.icann.org/download/attachments/160728655/Transfers%20Poli…> for summary) and confirm here<https://docs.google.com/forms/d/e/1FAIpQLSe3xz-e80x6moG8KSRDbCgYQOTN1Er6PYu…> when you have done so. As always, please feel free to reach out with any questions. Kind regards, Emily, Caitlin and Berry Transfer Policy Review Phase 1 - Meeting #02 Proposed Agenda Friday 21 May 2021 at 18.00 UTC 1. Roll Call & SOI Updates (5 minutes) 2. Welcome & Chair updates (Chair) (5 minutes) 3. High-level Review of Phase 1A Charter Topics & Charter Questions (30 minutes) 4. Phase 1A Charter Topic #01 Discussion – Gaining FOA (30 minutes) 5. Phase 1A Charter Topic #02 Discussion – Losing FOA (15 minutes and time permitting) 6. Next steps & closing (5 minutes) Emily Barabas Policy Manager, GNSO Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) Phone: +31 (0)6 84507976 www.icann.org<http://www.icann.org/>

1 0

Re: [GNSO-TPR] Concurrent changes; transfer of DNS service
by Steve Crocker 18 May '21

18 May '21

Min Feng, Thanks for your email. Yes, the gaining registrar can provide concurrent DNS service in advance of the transfer. For an unsigned zone, this is helpful. However, this will likely not work well for a signed zone. In order to guarantee continuity of service, i.e. both resolution and validation, the name servers and the key(s) of the gaining DNS service have to be added to the losing DNS service. It's understandable the losing DNS operator might not be interested in cooperating with this transition. However, there is another way to look at the process. Some customers will be interested in having two or more DNS operators serve their zone. Therefore, the first part of the transfer process is the same for both adding a new operator and transferring to a new operator. Once both operators have the zone in operation, the customer may leave both in operation for an extended period of time or they may choose to fold down the old operation. Steve On Mon, May 17, 2021 at 9:46 PM registrar(a)22.cn <registrar(a)22.cn> wrote: > Hi Steve, > > My suggestion is that when the registrant moves their registration to > another registrars, as the gaining registrar, it should be able to allow > the registrant to use the current DNS service during the inter-registrars > transfer process or after the inter-registrars transfer is completed, then > it can be solved and without a disruption in resolution. In my opinion, > this is not a complicated function. Thanks. > > Best regards, > Min Feng > > ------------------------------ > International Affairs Team > 22Net, Inc > Phone: +86-571-88276021 > Fax: +86-571-88276022 > Address: 11/F,Bldg No.2, Hangzhou Internet Innovation Pioneer Park, No.176 > Zixia Street, Hangzhou, Zhejiang, China > Post code:310030 > > > *From:* Steve Crocker <steve(a)shinkuro.com> > *Date:* 2021-05-18 09:01 > *To:* Owen Smigelski <owen.smigelski(a)namecheap.com> > *CC:* gnso-tpr(a)icann.org > *Subject:* Re: [GNSO-TPR] Concurrent changes; transfer of DNS service > Owen, > > Thanks. The touchstone for me is whether a registrant can successfully > transfer his registration from one registrar to another. With respect to > the registrant's DNS service, I believe this is most often provided free of > charge by the registrar as part of the registrar's service. As a > consequence, when the registrant moves their registration to > another registrar, they will also have to move their DNS service. As > things stand, I believe this often means there will be a disruption in > resolution. And for a signed zone, this also means a disruption in > validation. > > If I understand your point, you're saying because this was not raised in > the issues report, it's not in scope for this PDP. Putting these points > together, the goal for this PDP is to reach consensus on how a registrant > can transfer their registration from one registrar to another with the > understanding they will likely not be able to sustain uninterrupted service. > > Steve > > > On Mon, May 17, 2021 at 8:49 PM Owen Smigelski via GNSO-TPR < > gnso-tpr(a)icann.org> wrote: > >> Hi Steve, >> >> Regarding inter-registrar transfers, that is covered by the Temp Spec >> (specifically Appendix G, Section 1.2). I do not think it needs to be tied >> to the inter-registrant process due to the post-Temp Spec transfer process >> due to limited registrant data in the RDDS. >> >> While I think the other issues you raise are worthy of consideration, >> they are outside of the scope for Phase 1a: gaining/losing FOA, auth-code >> management, and Wave 1, Recommendation 27. Looking ahead, I do not see them >> in the other phases as well. While I appreciate a desire for a holistic >> review, this PDP is bound by its charter which is based upon concerns >> raised in the issues report (which did not mention those items). We need to >> be wary of scope creep to ensure that we can timely focus on and resolve >> the items identified in our charter. >> >> Regards, >> >> Owen >> >> On May 16, 2021, at 20:53, Steve Crocker <steve(a)shinkuro.com> wrote: >> >> On the call Friday, I commented that a change of registrar may also >> require a change in DNS service at the same time. I also asked if the >> distinction between inter-registrant and inter-registrant mentioned in the >> charter covered the case where both the registrant and registrar were >> changing at the same time. >> >> Attached is a note digging into these cases. In brief, I >> recommend consideration of both the one-at-a-time changes AND full >> understanding of how to make multiple changes. >> >> Thanks, >> >> Steve >> >> <Consideration of Multiple Changes and the Inclusion of DNS Operations >> v2.docx>_______________________________________________ >> GNSO-TPR mailing list >> GNSO-TPR(a)icann.org >> https://mm.icann.org/mailman/listinfo/gnso-tpr >> >> >> _______________________________________________ >> GNSO-TPR mailing list >> GNSO-TPR(a)icann.org >> https://mm.icann.org/mailman/listinfo/gnso-tpr > >

2 1

Post Call | Transfer Policy Review PDP WG | Friday, 14 May 2021 at 18:00 UTC
by Julie Bisland 14 May '21

14 May '21

Dear all, All recordings for the Transfer Policy Review PDP WG call held on Friday, 14 May 2021 at 18:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/T4aUCQ> (attendance included) and the GNSO Master calendar<https://gnso.icann.org/en/group-activities/calendar>. 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) * Transcript As a reminder only members and alternates can join the call as a Panelist, observers can join as an Attendee to listen. For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-tpr/> and the main wiki page<https://community.icann.org/x/P4aUCQ>. Thank you. With kind regards, Julie

1 0

Notes and action items - TPR Meeting #1 - 14 May 2021
by Caitlin Tubergen 14 May '21

14 May '21

Dear Transfer Policy Review (TPR) Working Group Members, Please find below the notes and action items from today’s meeting below. The next TPR WG meeting will be Friday, 21 May at 18:00 UTC. Please note the permanent meeting time(s) of the group has not yet been decided. Have a wonderful weekend! Best regards, Emily, Berry, and Caitlin -- Action Items 1. TPR WG members to carefully review the following documents: * Working Group Charter<https://community.icann.org/display/TPRPDP/2.+WG+Charter> * Final Issue Report [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> * Transfer Policy<https://www.icann.org/resources/pages/transfer-policy-2016-06-01-en> * Consensus Playbook [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> * GNSO Working Group Guidelines [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> & PDP Manual [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> * ICANN70 session providing an introduction to the PDP [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/rec/play/dK9qk08zEpYxTFWJS…> 1. TPR Support Staff to send doodle poll to identify a new meeting time for the TPR WG. Meeting Notes Transfer Policy Review PDP Meeting #1 14 May 2021, 18:00 UTC 1. Introductions 1. Vice Chair The WG has the opportunity to select one or two Vice Chairs for this Working Group, but is not required to do so. * Chair recommend not appointing a vice-chair * Do not see any chair availability issues, and in the event of an unforeseen absence, Support Staff may assist * The vice-chair would need to be an impartial party, likely outside of this group * No objections to proceeding with no vice-chair at this time 1. Charter: It would be helpful if everyone could read through the Charter<https://community.icann.org/display/TPRPDP/2.+WG+Charter> before the first call. We will briefly go over some key points and answer any questions that members have. * Objective to conduct a holistic review of the Transfer Policy * The PDP is divided into two phases * Phase 1 will divided into two parts, Phase 1A and 1B – the division is to divide the work into more manageable, distinct chunks * Phase 1A will cover two issues – Form of Authorization (FOA) and Auth-info codes * Phase 1B will cover Change of Registrant * Phase 2 will cover multiple topics including Transfer Emergency Action Contact and reversing inter-registrar transfers, Transfer Dispute Resolution Policy (including Rec. 27, Wave 1 TDRP issues), NACKing transfers, ICANN-approved transfers * The WG’s Charter outlines a series of milestones – because of the way this is phased, the full PDP is initiated under a single charter. There will be an initial report for both Phase 1A and 1B, and there will be a combined Phase 1 Final Report. Following this, there will be a charter review, and then Phase 2 will begin. There will be one Initial Report for Phase 2. * If Phase 1 recs are approved by the GNSO Council, implementation of Phase 1 recs can begin to occur in parallel of Phase 2 work. * With respect to WG composition, all SOs/ACs/SGs/Cs were invited to appoint members and alternates. The numbers of members and alternates are different for different groups. * Membership structure: * Chair (Roger Carney), who serves as a neutral facilitator; * Members, who are responsible for active participation, preliminary deliberations, and consensus. Members represent the views of their appointing organizations in deliberations and consensus calls; * Alternates, who only participate if a Member is not available, but will be responsible for keeping up with Working Group. Alternates may always join calls but may only speak if they are "standing in" for a Member who is absent; * Observers, who may follow the work by listening to calls and following email traffic on the mailing lists; * GNSO Council Liaison, who is a neutral link to the GNSO Council. Greg DiBiase will serve as GNSO Council Liaison for this PDP, though he is currently on leave. 1. Operating Mode/Working Methods: Working Methods: * Regular Working Group meetings via Zoom. * Offline assignments between calls. * Sessions during ICANN meetings, as needed. * Community input through request for input from SO/AC/SG/Cs, as well as public comment on the Initial Reports. Member Roles: * Reminder: members represent the views of their appointing organizations, don't "switch hats." Transparency: * Mailing lists are publicly archived. * Calls are recorded and transcribed. Decision-making: * As outlined in the Charter, the Working Group will follow Working Group Guidelines Section 3.6: Standard Methodology for Making Decisions. * In addition, the Charter states: “The subject matter of this PDP is not equally of interest to and impactful on all SG/C/SO/ACs. As a result, the membership structure more heavily represents ICANN’s contracted parties, and specifically registrars. At the same time, the registrant’s perspective will be important to factor into the Working Group’s deliberations and final outputs. The Chair shall ensure that all perspectives are appropriately taken into account in assessing Consensus designations on the final recommendations.” Statement of Participation Highlights Members agree to: * Work cooperatively towards consensus. * Treat all members of the Working Group with civility, respecting their time and commitment. * Regularly attend all scheduled meetings and send apologies in advance when unable to attend. * Follow through on completing assignments between calls and meeting agreed deadlines. * As and when appropriate, seek to be replaced by a designated Alternate in accordance with the wishes of appointing organization. * Abide by working methods and rules of engagement outlined in the Charter. 1. Work Plan: The WG’s initial areas of focus will be: * High-level review of the topics within the Charter for Phase 1 * Prepare to request input from SO/AC/SG/Cs on topics in Phase 1 * Deliver Phase 1 Work Plan to GNSO Council * GNSO Council is the manager of the PDP * This WG is responsible for submitting a work plan to the GNSO Council * The WG will discuss the topics sequentially, with the Charter as its guide * Will lift the key charter topics and subsequent charter questions into a project plan and will highlight the key dependencies * This group will do a high-level review of all of the topics and questions – this is to get a better understanding of if one topic is more complex than another. This will help to inform the project schedule so that we can assign durations for each topic. Once we have completed the duration and dependency exercise, we will provide a date for when we can deliver an Initial Report. Once the group is satisfied with the proposed dates, Leadership will submit the project plan to the GNSO Council. * There are relief mechanisms if a date shift is required; (1) the Team can add additional slack time for its work plan. (2) The group could also provide a formal project change request to the GNSO Council – please note, though, this is not a guaranteed extension. The group would have to provide a rationale as to why more time is required. * Trying to determine duration is difficult, but one thing the group can do is utilize “the crank”. Each policy question will correspond to a block or chunk of work. As the WG review each question, the process for review will be the same. There will be an introduction, and the group will deliberate and form draft agreements, conclusions, recommendations, etc. Then, there will then be a first reading where the group will then deliberate further following by a second reading – after which, the topic remains stable. The WG will then move on to the next topic and will not return to previous topics unless new information becomes available. 1. Meeting Frequency and Schedule: We’ll have an opportunity to discuss the meeting frequency and the proposed day/time of the calls. * Support Staff to send out Doodle Poll to identify a time to meet * Use this time for one more week, with apologies to everyone in Europe

1 0

Meeting Invitation | Observers | Transfer Policy Review PDP WG call | Friday, 21 May 2021 at 18:00 UTC
by Julie Bisland 14 May '21

14 May '21

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Friday, 21 May 2021 at 18:00 UTC for 90 minutes. Join the Zoom Webinar: https://icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/95363727469?pwd=N3A3OWFS…> Passcode: @TP/^*4wg# Observers will have ability to join the call via Zoom Webinar, and will be able to view members’ chat as well as information shared in the Zoom Webinar room. Observers will not be able to use chat or raise hands. The recordings and transcriptions of the calls will be posted on the GNSO Master Calendar page: https://gnso.icann.org/en/group-activities/calendar [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…> Before joining the call: Please be sure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en> Visit the Wiki Agenda meeting page: https://community.icann.org/x/5AXQCQ Check your time zone: https://tinyurl.com/2f3zddzs [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2f3zddzs__;!!PtGJab4!ox-nAJs…> Audio only: One tap mobile: US: +19294362866,,95363727469#,,,,*7490739013# or +13017158592,,95363727469#,,,,*7490739013# Telephone: Dial (for higher quality, dial a number based on your current location): US: +1 929 436 2866 or +1 301 715 8592 or +1 312 626 6799 or +1 669 900 6833 or +1 253 215 8782 or +1 346 248 7799 or 888 788 0099 (Toll Free) or 877 853 5247 (Toll Free) Webinar ID: 953 6372 7469 Passcode: 7490739013 International numbers available: https://icann.zoom.us/u/acdLFXPLp6 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/acdLFXPLp6__;!!PtGJab4!v…> Thank you. Kind regards, Julie -- Julie Bisland GNSO SO/AC Support coordinator Internet Corporation for Assigned Names and Numbers (ICANN) 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…>

1 0

**Starts in 11 minutes** Meeting Invitation | Observers | First call of the Transfer Policy Review PDP WG | Friday, 14 May 2021 at 18:00 UTC
by Julie Bisland 14 May '21

14 May '21

**Starts in 11 minutes** Dear all, As per the results of the Doodle poll, and having taken into account the time and date preferred by most of the group's Members, the first meeting of the Transfer Policy Review PDP WG is scheduled for Friday, 14 May 2021 at 18:00 UTC for 90 minutes. Join the Zoom Webinar: https://icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/95363727469?pwd=N3A3OWFS…> Passcode: @TP/^*4wg# Observers will have ability to join the call via Zoom Webinar, and will be able to view members’ chat as well as information shared in the Zoom Webinar room. Observers will not be able to use chat or raise hands. The recordings and transcriptions of the calls will be posted on the GNSO Master Calendar page: https://gnso.icann.org/en/group-activities/calendar [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…> Before joining the call: Please be sure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en> Visit the Wiki Agenda meeting page: https://community.icann.org/x/T4aUCQ Check your time zone: https://tinyurl.com/w2hdyeba [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/w2hdyeba__;!!PtGJab4!pRII-HY…> Audio only: One tap mobile: US: +19294362866,,95363727469#,,,,*7490739013# or +13017158592,,95363727469#,,,,*7490739013# Telephone: Dial (for higher quality, dial a number based on your current location): US: +1 929 436 2866 or +1 301 715 8592 or +1 312 626 6799 or +1 669 900 6833 or +1 253 215 8782 or +1 346 248 7799 or 888 788 0099 (Toll Free) or 877 853 5247 (Toll Free) Webinar ID: 953 6372 7469 Passcode: 7490739013 International numbers available: https://icann.zoom.us/u/acdLFXPLp6 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/acdLFXPLp6__;!!PtGJab4!v…> Thank you. Kind regards, Julie -- Julie Bisland GNSO SO/AC Support coordinator Internet Corporation for Assigned Names and Numbers (ICANN) 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…>

1 0