Changes

* In the ICANN Board and SSAC Joint Meeting, [[Maarten Botterman]] asked [[Geoff Huston]] whether there would be a way to know if the DNS can survive future rounds of additional TLDs and second-level strings. His response:

* In the ICANN Board and SSAC Joint Meeting, [[Maarten Botterman]] asked [[Geoff Huston]] whether there would be a way to know if the DNS can survive future rounds of additional TLDs and second-level strings. His response:

** Sac117 (see also octo-15). Root zone can’t grow infinitely. Is there a way to see whether there will be imminent demise of the dns? We can collect and analyze data about the DNS's behavior/nature but it’s not possible to have an early warning system or no when it will collapse

** Sac117 (see also octo-15). Root zone can’t grow infinitely. Is there a way to see whether there will be imminent demise of the DNS? We can collect and analyze data about the DNS's behavior/nature but it’s not possible to have an early warning system or no when it will collapse

** flattening the DNS solves some technical issues but creates problems around resolving queries for which the hierarchical architecture is better suited; if different labels lead to different behaviors, then we will be in unchartered territory; we've seen a little a bit of this with [[IDN]]s. It will be unpredictable for the entire system

** flattening the DNS solves some technical issues but creates problems around resolving queries for which the hierarchical architecture is better suited; if different labels lead to different behaviors, then we will be in unchartered territory; we've seen a little a bit of this with [[IDN]]s. It will be unpredictable for the entire system

** support for RSAC002, 047 (measuring the DNS)

** support for RSAC002, 047 (measuring the DNS)

===Data Accuracy===

===Data Accuracy===

* The GNSO Council created a Registration Data Accuracy Scoping Team to consider current enforcement and reporting; measurement of accuracy, and effectiveness<ref>[https://community.icann.org/display/gnsocouncilmeetings/Registration+Data+Accuracy+Scoping+Team+-+ICANN72 RDA Scoping Team, GNSO Council Meetings]</ref>; this meeting spent a significant amount of time discussing the [https://www.icann.org/resources/pages/raa-whois-accuracy-2015-11-16-en definition of accuracy] and spent a little bit of time on determining [https://community.icann.org/download/attachments/175244888/Working%20draft%20-%20Discussion%20timeline%20-%20upd%2022%20October%202021.pdf how much time each step will take] to answer whether changes should be recommended to improve accuracy levels; how and by whom they would be developed; and whether existing contractual requirements may necessitate a PDP or contractual negotiations.

* The GNSO Council created a Registration Data Accuracy Scoping Team to consider current enforcement and reporting; measurement of accuracy; and effectiveness<ref>[https://community.icann.org/display/gnsocouncilmeetings/Registration+Data+Accuracy+Scoping+Team+-+ICANN72 RDA Scoping Team, GNSO Council Meetings]</ref>. This meeting spent a significant amount of time discussing the [https://www.icann.org/resources/pages/raa-whois-accuracy-2015-11-16-en definition of accuracy] and spent a little bit of time on determining [https://community.icann.org/download/attachments/175244888/Working%20draft%20-%20Discussion%20timeline%20-%20upd%2022%20October%202021.pdf how much time each step will take] to answer whether changes should be recommended to improve accuracy levels; how and by whom they would be developed; and whether existing contractual requirements may necessitate a PDP or contractual negotiations.

* In the [[GAC]] session called 'GAC Discussion: WHOIS and Data Protection,' [[Laureen Kapin]] led a discussion on the need for validated "operational" accuracy, as opposed to merely syntactical accuracy, in terms of registrants' contact information, as GAC members often represent law enforcement and regulatory bodies.

* In the [[GAC]] session called 'GAC Discussion: WHOIS and Data Protection,' [[Laureen Kapin]] led a discussion on the need for validated "operational" accuracy, as opposed to merely syntactical accuracy, in terms of registrants' contact information, as GAC members often represent law enforcement and regulatory bodies.

# A domain name is more at risk of being [[Domain Name Hijacking|hijacked]] if the authInfo code is not managed based on best practice security principles.

# A domain name is more at risk of being [[Domain Name Hijacking|hijacked]] if the authInfo code is not managed based on best practice security principles.

====RPM Phase 2====

====RPM Phase 2====

* The [[IPC]] held a discussion on scoping concerns for the [[UDRP]] Review (by [[Susan Payne]]), based on a list of suggestions sent by [[John McElwaine]] to [[GDD]], including reducing the negativity toward the UDRP to reflect the reality of the majority report (that it has been a relative success); making it data-driven (from [[WIPO]], providers, trends for analysis, [[INTA]]); and not starting from scratch. The [[BC]] supports the IPC's concerns.  

* The [[IPC]] held a discussion on scoping concerns for the [[UDRP]] Review (by [[Susan Payne]]), based on a list of suggestions sent by [[John McElwaine]] to [[GDD]], including reducing the negativity toward the UDRP to reflect the reality of the majority report (that it has been a relative success); making it data-driven (from [[WIPO]], providers, trends for analysis, [[INTA]]); and not starting from scratch. The [[BC]] supports the IPC's concerns. Their suggestions included:

**Use [[Consensus Playbook]]  

** Use [[Consensus Playbook]]; and that

**RPM Phase 1 was a disaster, spent too much time on chartering; must do it differently this time ([[Lori Schulman]]), use [[WIPO]] reports as precedent, use data that is already available

** RPM Phase 1 was a disaster, as the WG spent too much time on chartering; the group must do it differently this time (said [[Lori Schulman]]); use [[WIPO]] reports as precedent; and incorporate data that is already available.

==References==

==References==

{{reflist}}

{{reflist}}

[[Category:ICANN Meetings]]

[[Category:ICANN Meetings]]