Refunds for Changes to Program and because of Name Collisions
All, I spent some time reviewing the SubPro Final Report and the recommendation on refunds and I wanted to draw your attention to the following because it differs from what was discussed earlier today (or yesterday for some of you) when we were discussing that topic. Recommendation 18.4 states (pg 84): "Applicants must be allowed some type of refund if they decide to withdraw an application because substantive changes are made to the Applicant Guidebook or program processes and such changes have, or are reasonably likely to have, a material impact on applicants.117" FN 117 states: "This refund would differ from the normal refund schedule." Implementation Guidance 18.5 states: If the risk of name collisions will be determined after applications are submitted, ICANN should provide a full refund to applicants in cases where a new gTLD is applied for but later is not approved because of risk of name collision. However, the proposal today from ICANN was that the normal refund schedule would apply in both situations. Looking further to the Rationale: In connection with recommendations under Topic 2: Predictability, the Working Group agreed that there should be a clear and consistent framework for handling changes in the New gTLD Program, including changes to the Applicant Guidebook. The Working Group recommends that an applicant must be eligible for some type of refund if they decide to withdraw an application because substantive changes are made to the Applicant Guidebook or program processes and such changes have, or are reasonably likely to have, a material impact on applicants. The Working Group expects that the Implementation Review Team will conduct further work regarding the details of this refund. The Working Group also provided implementation guidance regarding recourse for cases where an applicant applies for a string and that application is later disqualified because of risk of name collision. (page 85 of 400) ON Name Collision (18.5): Understood that this is "Implementation Guidance", but Implementation Guidance means that it was "strongly recommended with a strong presumption that it will be implemented" although it recognizes that reasons may exist to not do exactly as it is worded. But ICANN must "make all efforts to achieve the purpose behind the recommended action as expressed in the rationale." Can we please have a further discussion on this topic? Sincerely, Jeff [cid:9c6e1ac8-f9c7-462f-a7a7-72ade0bcbb9c]
OFFICIAL Jeff Good afternoon, just to note how useful this was for our on-going dialogue; Best Nigel OFFICIAL From: Jeff Neuman via SubPro-IRT <subpro-irt@icann.org> Sent: 05 February 2025 04:27 To: subpro-irt@icann.org Subject: [SubPro-IRT] Refunds for Changes to Program and because of Name Collisions All, I spent some time reviewing the SubPro Final Report and the recommendation on refunds and I wanted to draw your attention to the following because it differs from what was discussed earlier today (or yesterday for some of you) when we were discussing that topic. Recommendation 18.4 states (pg 84): "Applicants must be allowed some type of refund if they decide to withdraw an application because substantive changes are made to the Applicant Guidebook or program processes and such changes have, or are reasonably likely to have, a material impact on applicants.117" FN 117 states: "This refund would differ from the normal refund schedule." Implementation Guidance 18.5 states: If the risk of name collisions will be determined after applications are submitted, ICANN should provide a full refund to applicants in cases where a new gTLD is applied for but later is not approved because of risk of name collision. However, the proposal today from ICANN was that the normal refund schedule would apply in both situations. Looking further to the Rationale: In connection with recommendations under Topic 2: Predictability, the Working Group agreed that there should be a clear and consistent framework for handling changes in the New gTLD Program, including changes to the Applicant Guidebook. The Working Group recommends that an applicant must be eligible for some type of refund if they decide to withdraw an application because substantive changes are made to the Applicant Guidebook or program processes and such changes have, or are reasonably likely to have, a material impact on applicants. The Working Group expects that the Implementation Review Team will conduct further work regarding the details of this refund. The Working Group also provided implementation guidance regarding recourse for cases where an applicant applies for a string and that application is later disqualified because of risk of name collision. (page 85 of 400) ON Name Collision (18.5): Understood that this is "Implementation Guidance", but Implementation Guidance means that it was "strongly recommended with a strong presumption that it will be implemented" although it recognizes that reasons may exist to not do exactly as it is worded. But ICANN must "make all efforts to achieve the purpose behind the recommended action as expressed in the rationale." Can we please have a further discussion on this topic? Sincerely, Jeff [cid:image001.png@01DB77D8.580E1200]
Jeff et al, I also found the reasoning behind not following IG 18.5 totally lacking. What Org is doing will only push future PDPs to hard-code everything in recommendations instead of leaving latitude for Org to fine tune decisions. This is a serious break of trust on Org’s part. Rubens
Em 5 de fev. de 2025, à(s) 01:26, Jeff Neuman via SubPro-IRT <subpro-irt@icann.org> escreveu:
All,
I spent some time reviewing the SubPro Final Report and the recommendation on refunds and I wanted to draw your attention to the following because it differs from what was discussed earlier today (or yesterday for some of you) when we were discussing that topic.
Recommendation 18.4 states (pg 84): "Applicants must be allowed some type of refund if they decide to withdraw an application because substantive changes are made to the Applicant Guidebook or program processes and such changes have, or are reasonably likely to have, a material impact on applicants.117"
FN 117 states: "This refund would differ from the normal refund schedule."
Implementation Guidance 18.5 states: If the risk of name collisions will be determined after applications are submitted, ICANN should provide a full refund to applicants in cases where a new gTLD is applied for but later is not approved because of risk of name collision.
However, the proposal today from ICANN was that the normal refund schedule would apply in both situations.
Looking further to the Rationale: In connection with recommendations under Topic 2: Predictability, the Working Group agreed that there should be a clear and consistent framework for handling changes in the New gTLD Program, including changes to the Applicant Guidebook. The Working Group recommends that an applicant must be eligible for some type of refund if they decide to withdraw an application because substantive changes are made to the Applicant Guidebook or program processes and such changes have, or are reasonably likely to have, a material impact on applicants. The Working Group expects that the Implementation Review Team will conduct further work regarding the details of this refund. The Working Group also provided implementation guidance regarding recourse for cases where an applicant applies for a string and that application is later disqualified because of risk of name collision. (page 85 of 400)
ON Name Collision (18.5): Understood that this is "Implementation Guidance", but Implementation Guidance means that it was "strongly recommended with a strong presumption that it will be implemented" although it recognizes that reasons may exist to not do exactly as it is worded. But ICANN must "make all efforts to achieve the purpose behind the recommended action as expressed in the rationale."
Can we please have a further discussion on this topic?
Sincerely,
Jeff
<Outlook-axgss43a.png> _______________________________________________ SubPro-IRT mailing list -- subpro-irt@icann.org <mailto:subpro-irt@icann.org> To unsubscribe send an email to subpro-irt-leave@icann.org <mailto:subpro-irt-leave@icann.org>
_______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
participants (3)
-
Hickson, Nigel (DSIT) -
Jeff Neuman -
Rubens Kuhl