Dear IRT members, Per my email<https://lists.icann.org/hyperkitty/list/subpro-irt@icann.org/thread/PGLC3NTN...> from earlier, please see below links to the Name Collison language that we will put out for public comment on Friday 14 February 2025. You find links to the redline version that shows edits and responses to comments and a clean version that will be published. A pdf of the clean version is also attached. As noted in my earlier email<https://lists.icann.org/hyperkitty/list/subpro-irt@icann.org/thread/TJAGBWDT6NJAJTDOMWGNNLSIA4I4FACM/>,* Anne had made a comment on list re: Name Collision and today’s (11 Feb 13:00 UTC) and I responded to that in the email thread. We will ensure that the relevant language in ‘Applicant Journey’ (that we will share tomorrow (12 Feb) by COB Central European time) will be consistent with this. Please note: feel free to share this document with your respective community groups, in case you’d like to start working already on the public comment. Best wishes, Lars Redline: https://docs.google.com/document/d/17VZM1Jx9Waw7qKnkSZ5Hx8CeRwosFiSlB_ZGXrVR... Clean: https://docs.google.com/document/d/13-9imDsDH3cbCjPz_e7ZlVTH3dZrG_7nkJs-Oo5U... *For some reason the listsever thread does not show my email at the top, it is about half way through, starting with “Hi Anne, Thank you again for reaching out and raising these points. We had several discussions internally […].”
Thanks Lars. This is helpful but I believe Section 4 contains an inaccurate statement based on the work done by NCAP to verify that RSSAC advice on the rate of delegation need not necessarily apply in the Temporary Delegation phase of Name Collision Risk Assessment. The inaccurate statement is as follows: *The rate at which strings will be temporarily delegated will be limited to ensure that the DNS root zone does not grow by approximately more than 5% per calendar month. * In fact, PTI confirmed to the NCAP that this "rate of delegation" advice was likely only applicable where names are actually being sold in a TLD and not in the Temporary Delegation phase. *You should find confirmation of this statement from PTI in the GNSO Council meeting minutes and Zoom from the GNSO Council meeting in Hamburg. Please check this before the Public Comment.* In addition, I think there was an idea floated that a string which proved "high risk" on Temporary Delegation might promptly be pulled back out of the root. I am also asking Jim Galvin to confirm by reply my recollection that PTI confirmed that the 5% per month delegation rate was not applicable to this Name Collision Temporary Delegation testing process. My recollection is that Co-Chair Suzanne Woolfe was very careful to track this down before the NCAP Final Report issued, so I am also copying Suzanne. Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com On Tue, Feb 11, 2025 at 7:50 PM Lars Hoffmann via SubPro-IRT < subpro-irt@icann.org> wrote:
Dear IRT members,
Per my email <https://lists.icann.org/hyperkitty/list/subpro-irt@icann.org/thread/PGLC3NTN...> from earlier, please see below links to the Name Collison language that we will put out for public comment on Friday 14 February 2025. You find links to the redline version that shows edits and responses to comments and a clean version that will be published. A pdf of the clean version is also attached.
As noted in my earlier email <https://lists.icann.org/hyperkitty/list/subpro-irt@icann.org/thread/TJAGBWDT6NJAJTDOMWGNNLSIA4I4FACM/>,* Anne had made a comment on list re: Name Collision and today’s (11 Feb 13:00 UTC) and I responded to that in the email thread. We will ensure that the relevant language in ‘Applicant Journey’ (that we will share tomorrow (12 Feb) by COB Central European time) will be consistent with this.
Please note: feel free to share this document with your respective community groups, in case you’d like to start working already on the public comment.
Best wishes,
Lars
Redline: https://docs.google.com/document/d/17VZM1Jx9Waw7qKnkSZ5Hx8CeRwosFiSlB_ZGXrVR...
Clean: https://docs.google.com/document/d/13-9imDsDH3cbCjPz_e7ZlVTH3dZrG_7nkJs-Oo5U...
*For some reason the listsever thread does not show my email at the top, it is about half way through, starting with “Hi Anne, Thank you again for reaching out and raising these points. We had several discussions internally […].” _______________________________________________ SubPro-IRT mailing list -- subpro-irt@icann.org To unsubscribe send an email to 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.
Thank you, Anne. We confirmed with with Kim Davies, VP IANA Services and President PTI, and also went back to the transcript and could not detect any instance in which Kim or anyone else in PTI/IANA said what you suggest. Could you kindly point us to the relevant source so we can check this, please? In addition, we reconfirmed with IANA and IANA is of the view that rate-of-change limits would need to be applied for all transaction, even including those for temporary delegations. Best wishes Lars From: Anne ICANN <anneicanngnso@gmail.com> Date: Thursday, 13 February 2025 at 07:43 To: Lars Hoffmann <lars.hoffmann@icann.org>, Suzanne Woolf <swoolf@pir.org>, "suzworldwide@gmail.com" <suzworldwide@gmail.com>, James Galvin <galvin@elistx.com> Cc: Lars Hoffmann via SubPro-IRT <subpro-irt@icann.org> Subject: [Ext] Re: [SubPro-IRT] Name Collison Thanks Lars. This is helpful but I believe Section 4 contains an inaccurate statement based on the work done by NCAP to verify that RSSAC advice on the rate of delegation need not necessarily apply in the Temporary Delegation phase of Name Collision Risk Assessment. The inaccurate statement is as follows: The rate at which strings will be temporarily delegated will be limited to ensure that the DNS root zone does not grow by approximately more than 5% per calendar month. In fact, PTI confirmed to the NCAP that this "rate of delegation" advice was likely only applicable where names are actually being sold in a TLD and not in the Temporary Delegation phase. You should find confirmation of this statement from PTI in the GNSO Council meeting minutes and Zoom from the GNSO Council meeting in Hamburg. Please check this before the Public Comment. In addition, I think there was an idea floated that a string which proved "high risk" on Temporary Delegation might promptly be pulled back out of the root. I am also asking Jim Galvin to confirm by reply my recollection that PTI confirmed that the 5% per month delegation rate was not applicable to this Name Collision Temporary Delegation testing process. My recollection is that Co-Chair Suzanne Woolfe was very careful to track this down before the NCAP Final Report issued, so I am also copying Suzanne. Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Tue, Feb 11, 2025 at 7:50 PM Lars Hoffmann via SubPro-IRT <subpro-irt@icann.org<mailto:subpro-irt@icann.org>> wrote: Dear IRT members, Per my email [lists.icann.org]<https://urldefense.com/v3/__https:/lists.icann.org/hyperkitty/list/subpro-ir...> from earlier, please see below links to the Name Collison language that we will put out for public comment on Friday 14 February 2025. You find links to the redline version that shows edits and responses to comments and a clean version that will be published. A pdf of the clean version is also attached. As noted in my earlier email [lists.icann.org]<https://urldefense.com/v3/__https:/lists.icann.org/hyperkitty/list/subpro-irt@icann.org/thread/TJAGBWDT6NJAJTDOMWGNNLSIA4I4FACM/__;!!PtGJab4!-SEKhKMflM9a8hphteSauK-DBDuiCDq62wSFKUaB59U6DofSAa20zZKs-BHRiQNCRJXO0swuUYc89Mx37O3vFaofXpPDgYyx$>,* Anne had made a comment on list re: Name Collision and today’s (11 Feb 13:00 UTC) and I responded to that in the email thread. We will ensure that the relevant language in ‘Applicant Journey’ (that we will share tomorrow (12 Feb) by COB Central European time) will be consistent with this. Please note: feel free to share this document with your respective community groups, in case you’d like to start working already on the public comment. Best wishes, Lars Redline: https://docs.google.com/document/d/17VZM1Jx9Waw7qKnkSZ5Hx8CeRwosFiSlB_ZGXrVR... [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/17VZM1Jx9Waw7q...> Clean: https://docs.google.com/document/d/13-9imDsDH3cbCjPz_e7ZlVTH3dZrG_7nkJs-Oo5U... [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/13-9imDsDH3cbC...> *For some reason the listsever thread does not show my email at the top, it is about half way through, starting with “Hi Anne, Thank you again for reaching out and raising these points. We had several discussions internally […].” _______________________________________________ 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.
Thanks Lars. I defer to Jim and Suzanne. My recollection is that I posed this question directly to Kim in the GNSO Council meeting in Hamburg and received a different answer but again, I think Suzanne and Jim could provide more detail. The fact that you spoke with Kim probably means there is confusion/disagreement on this issue. Obviously following the rate of delegation advice at %5 per month for Temporary Delegation could slow things down. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com On Thu, Feb 13, 2025 at 10:47 AM Lars Hoffmann <lars.hoffmann@icann.org> wrote:
Thank you, Anne.
We confirmed with with Kim Davies, VP IANA Services and President PTI, and also went back to the transcript and could not detect any instance in which Kim or anyone else in PTI/IANA said what you suggest. Could you kindly point us to the relevant source so we can check this, please? In addition, we reconfirmed with IANA and IANA is of the view that rate-of-change limits would need to be applied for all transaction, even including those for temporary delegations.
Best wishes
Lars
*From: *Anne ICANN <anneicanngnso@gmail.com> *Date: *Thursday, 13 February 2025 at 07:43 *To: *Lars Hoffmann <lars.hoffmann@icann.org>, Suzanne Woolf < swoolf@pir.org>, "suzworldwide@gmail.com" <suzworldwide@gmail.com>, James Galvin <galvin@elistx.com> *Cc: *Lars Hoffmann via SubPro-IRT <subpro-irt@icann.org> *Subject: *[Ext] Re: [SubPro-IRT] Name Collison
Thanks Lars. This is helpful but I believe Section 4 contains an inaccurate statement based on the work done by NCAP to verify that RSSAC advice on the rate of delegation need not necessarily apply in the Temporary Delegation phase of Name Collision Risk Assessment. The inaccurate statement is as follows:
*The rate at which strings will be temporarily delegated will be limited to ensure that the DNS root zone does not grow by approximately more than 5% per calendar month.*
In fact, PTI confirmed to the NCAP that this "rate of delegation" advice was likely only applicable where names are actually being sold in a TLD and not in the Temporary Delegation phase. *You should find confirmation of this statement from PTI in the GNSO Council meeting minutes and Zoom from the GNSO Council meeting in Hamburg. Please check this before the Public Comment.*
In addition, I think there was an idea floated that a string which proved "high risk" on Temporary Delegation might promptly be pulled back out of the root.
I am also asking Jim Galvin to confirm by reply my recollection that PTI confirmed that the 5% per month delegation rate was not applicable to this Name Collision Temporary Delegation testing process. My recollection is that Co-Chair Suzanne Woolfe was very careful to track this down before the NCAP Final Report issued, so I am also copying Suzanne.
Thank you,
Anne
Anne Aikman-Scalese
GNSO Councilor
NomCom Non-Voting 2022-2026
anneicanngnso@gmail.com
On Tue, Feb 11, 2025 at 7:50 PM Lars Hoffmann via SubPro-IRT < subpro-irt@icann.org> wrote:
Dear IRT members,
Per my email [lists.icann.org] <https://urldefense.com/v3/__https:/lists.icann.org/hyperkitty/list/subpro-ir...> from earlier, please see below links to the Name Collison language that we will put out for public comment on Friday 14 February 2025. You find links to the redline version that shows edits and responses to comments and a clean version that will be published. A pdf of the clean version is also attached.
As noted in my earlier email [lists.icann.org] <https://urldefense.com/v3/__https:/lists.icann.org/hyperkitty/list/subpro-irt@icann.org/thread/TJAGBWDT6NJAJTDOMWGNNLSIA4I4FACM/__;!!PtGJab4!-SEKhKMflM9a8hphteSauK-DBDuiCDq62wSFKUaB59U6DofSAa20zZKs-BHRiQNCRJXO0swuUYc89Mx37O3vFaofXpPDgYyx$>,* Anne had made a comment on list re: Name Collision and today’s (11 Feb 13:00 UTC) and I responded to that in the email thread. We will ensure that the relevant language in ‘Applicant Journey’ (that we will share tomorrow (12 Feb) by COB Central European time) will be consistent with this.
Please note: feel free to share this document with your respective community groups, in case you’d like to start working already on the public comment.
Best wishes,
Lars
Redline: https://docs.google.com/document/d/17VZM1Jx9Waw7qKnkSZ5Hx8CeRwosFiSlB_ZGXrVR... [docs.google.com] <https://urldefense.com/v3/__https:/docs.google.com/document/d/17VZM1Jx9Waw7q...>
Clean: https://docs.google.com/document/d/13-9imDsDH3cbCjPz_e7ZlVTH3dZrG_7nkJs-Oo5U... [docs.google.com] <https://urldefense.com/v3/__https:/docs.google.com/document/d/13-9imDsDH3cbC...>
*For some reason the listsever thread does not show my email at the top, it is about half way through, starting with “Hi Anne, Thank you again for reaching out and raising these points. We had several discussions internally […].”
_______________________________________________ SubPro-IRT mailing list -- subpro-irt@icann.org To unsubscribe send an email to 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.
My recollection is the same as Kim's. Which is why I even created for NCAP a spreadsheet estimating the impact of temporary delegation strategies on delegation rate. Rubens
Em 13 de fev. de 2025, à(s) 14:47, Lars Hoffmann via SubPro-IRT <subpro-irt@icann.org> escreveu:
Thank you, Anne.
We confirmed with with Kim Davies, VP IANA Services and President PTI, and also went back to the transcript and could not detect any instance in which Kim or anyone else in PTI/IANA said what you suggest. Could you kindly point us to the relevant source so we can check this, please? In addition, we reconfirmed with IANA and IANA is of the view that rate-of-change limits would need to be applied for all transaction, even including those for temporary delegations.
Best wishes Lars
From: Anne ICANN <anneicanngnso@gmail.com <mailto:anneicanngnso@gmail.com>> Date: Thursday, 13 February 2025 at 07:43 To: Lars Hoffmann <lars.hoffmann@icann.org <mailto:lars.hoffmann@icann.org>>, Suzanne Woolf <swoolf@pir.org <mailto:swoolf@pir.org>>, "suzworldwide@gmail.com <mailto:suzworldwide@gmail.com>" <suzworldwide@gmail.com <mailto:suzworldwide@gmail.com>>, James Galvin <galvin@elistx.com <mailto:galvin@elistx.com>> Cc: Lars Hoffmann via SubPro-IRT <subpro-irt@icann.org <mailto:subpro-irt@icann.org>> Subject: [Ext] Re: [SubPro-IRT] Name Collison
Thanks Lars. This is helpful but I believe Section 4 contains an inaccurate statement based on the work done by NCAP to verify that RSSAC advice on the rate of delegation need not necessarily apply in the Temporary Delegation phase of Name Collision Risk Assessment. The inaccurate statement is as follows:
The rate at which strings will be temporarily delegated will be limited to ensure that the DNS root zone does not grow by approximately more than 5% per calendar month.
In fact, PTI confirmed to the NCAP that this "rate of delegation" advice was likely only applicable where names are actually being sold in a TLD and not in the Temporary Delegation phase. You should find confirmation of this statement from PTI in the GNSO Council meeting minutes and Zoom from the GNSO Council meeting in Hamburg. Please check this before the Public Comment.
In addition, I think there was an idea floated that a string which proved "high risk" on Temporary Delegation might promptly be pulled back out of the root.
I am also asking Jim Galvin to confirm by reply my recollection that PTI confirmed that the 5% per month delegation rate was not applicable to this Name Collision Temporary Delegation testing process. My recollection is that Co-Chair Suzanne Woolfe was very careful to track this down before the NCAP Final Report issued, so I am also copying Suzanne.
Thank you, Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com <mailto:anneicanngnso@gmail.com>
On Tue, Feb 11, 2025 at 7:50 PM Lars Hoffmann via SubPro-IRT <subpro-irt@icann.org <mailto:subpro-irt@icann.org>> wrote:
Dear IRT members,
Per my email [lists.icann.org] <https://urldefense.com/v3/__https:/lists.icann.org/hyperkitty/list/subpro-ir...> from earlier, please see below links to the Name Collison language that we will put out for public comment on Friday 14 February 2025. You find links to the redline version that shows edits and responses to comments and a clean version that will be published. A pdf of the clean version is also attached.
As noted in my earlier email [lists.icann.org] <https://urldefense.com/v3/__https:/lists.icann.org/hyperkitty/list/subpro-irt@icann.org/thread/TJAGBWDT6NJAJTDOMWGNNLSIA4I4FACM/__;!!PtGJab4!-SEKhKMflM9a8hphteSauK-DBDuiCDq62wSFKUaB59U6DofSAa20zZKs-BHRiQNCRJXO0swuUYc89Mx37O3vFaofXpPDgYyx$>,* Anne had made a comment on list re: Name Collision and today’s (11 Feb 13:00 UTC) and I responded to that in the email thread. We will ensure that the relevant language in ‘Applicant Journey’ (that we will share tomorrow (12 Feb) by COB Central European time) will be consistent with this.
Please note: feel free to share this document with your respective community groups, in case you’d like to start working already on the public comment.
Best wishes, Lars
Redline: https://docs.google.com/document/d/17VZM1Jx9Waw7qKnkSZ5Hx8CeRwosFiSlB_ZGXrVR... [docs.google.com] <https://urldefense.com/v3/__https:/docs.google.com/document/d/17VZM1Jx9Waw7q...> Clean: https://docs.google.com/document/d/13-9imDsDH3cbCjPz_e7ZlVTH3dZrG_7nkJs-Oo5U... [docs.google.com] <https://urldefense.com/v3/__https:/docs.google.com/document/d/13-9imDsDH3cbC...>
*For some reason the listsever thread does not show my email at the top, it is about half way through, starting with “Hi Anne, Thank you again for reaching out and raising these points. We had several discussions internally […].” _______________________________________________ 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.
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.
HI Rubens, I remember your having done this and this was the reason that Suzanne Woolf chased this down to get a clarification. I certainly defer to Suzanne and to Jim Galvin on this point. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com On Thu, Feb 13, 2025 at 12:37 PM Rubens Kuhl via SubPro-IRT < subpro-irt@icann.org> wrote:
My recollection is the same as Kim's. Which is why I even created for NCAP a spreadsheet estimating the impact of temporary delegation strategies on delegation rate.
Rubens
Em 13 de fev. de 2025, à(s) 14:47, Lars Hoffmann via SubPro-IRT < subpro-irt@icann.org> escreveu:
Thank you, Anne.
We confirmed with with Kim Davies, VP IANA Services and President PTI, and also went back to the transcript and could not detect any instance in which Kim or anyone else in PTI/IANA said what you suggest. Could you kindly point us to the relevant source so we can check this, please? In addition, we reconfirmed with IANA and IANA is of the view that rate-of-change limits would need to be applied for all transaction, even including those for temporary delegations.
Best wishes Lars
*From: *Anne ICANN <anneicanngnso@gmail.com> *Date: *Thursday, 13 February 2025 at 07:43 *To: *Lars Hoffmann <lars.hoffmann@icann.org>, Suzanne Woolf < swoolf@pir.org>, "suzworldwide@gmail.com" <suzworldwide@gmail.com>, James Galvin <galvin@elistx.com> *Cc: *Lars Hoffmann via SubPro-IRT <subpro-irt@icann.org> *Subject: *[Ext] Re: [SubPro-IRT] Name Collison
Thanks Lars. This is helpful but I believe Section 4 contains an inaccurate statement based on the work done by NCAP to verify that RSSAC advice on the rate of delegation need not necessarily apply in the Temporary Delegation phase of Name Collision Risk Assessment. The inaccurate statement is as follows:
*The rate at which strings will be temporarily delegated will be limited to ensure that the DNS root zone does not grow by approximately more than 5% per calendar month.*
In fact, PTI confirmed to the NCAP that this "rate of delegation" advice was likely only applicable where names are actually being sold in a TLD and not in the Temporary Delegation phase. *You should find confirmation of this statement from PTI in the GNSO Council meeting minutes and Zoom from the GNSO Council meeting in Hamburg. Please check this before the Public Comment.*
In addition, I think there was an idea floated that a string which proved "high risk" on Temporary Delegation might promptly be pulled back out of the root.
I am also asking Jim Galvin to confirm by reply my recollection that PTI confirmed that the 5% per month delegation rate was not applicable to this Name Collision Temporary Delegation testing process. My recollection is that Co-Chair Suzanne Woolfe was very careful to track this down before the NCAP Final Report issued, so I am also copying Suzanne.
Thank you, Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com
On Tue, Feb 11, 2025 at 7:50 PM Lars Hoffmann via SubPro-IRT < subpro-irt@icann.org> wrote:
Dear IRT members,
Per my email [lists.icann.org] <https://urldefense.com/v3/__https:/lists.icann.org/hyperkitty/list/subpro-ir...> from earlier, please see below links to the Name Collison language that we will put out for public comment on Friday 14 February 2025. You find links to the redline version that shows edits and responses to comments and a clean version that will be published. A pdf of the clean version is also attached.
As noted in my earlier email [lists.icann.org] <https://urldefense.com/v3/__https:/lists.icann.org/hyperkitty/list/subpro-irt@icann.org/thread/TJAGBWDT6NJAJTDOMWGNNLSIA4I4FACM/__;!!PtGJab4!-SEKhKMflM9a8hphteSauK-DBDuiCDq62wSFKUaB59U6DofSAa20zZKs-BHRiQNCRJXO0swuUYc89Mx37O3vFaofXpPDgYyx$>,* Anne had made a comment on list re: Name Collision and today’s (11 Feb 13:00 UTC) and I responded to that in the email thread. We will ensure that the relevant language in ‘Applicant Journey’ (that we will share tomorrow (12 Feb) by COB Central European time) will be consistent with this.
Please note: feel free to share this document with your respective community groups, in case you’d like to start working already on the public comment.
Best wishes, Lars
Redline: https://docs.google.com/document/d/17VZM1Jx9Waw7qKnkSZ5Hx8CeRwosFiSlB_ZGXrVR... [docs.google.com] <https://urldefense.com/v3/__https:/docs.google.com/document/d/17VZM1Jx9Waw7q...> Clean: https://docs.google.com/document/d/13-9imDsDH3cbCjPz_e7ZlVTH3dZrG_7nkJs-Oo5U... [docs.google.com] <https://urldefense.com/v3/__https:/docs.google.com/document/d/13-9imDsDH3cbC...>
*For some reason the listsever thread does not show my email at the top, it is about half way through, starting with “Hi Anne, Thank you again for reaching out and raising these points. We had several discussions internally […].” _______________________________________________ SubPro-IRT mailing list -- subpro-irt@icann.org To unsubscribe send an email to 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.
_______________________________________________ SubPro-IRT mailing list -- subpro-irt@icann.org To unsubscribe send an email to 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.
_______________________________________________ SubPro-IRT mailing list -- subpro-irt@icann.org To unsubscribe send an email to 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)
-
Anne ICANN -
Lars Hoffmann -
Rubens Kuhl