ICANN 61: Difference between revisions
Dustin Loup (talk | contribs) No edit summary |
Christiane (talk | contribs) m Christiane moved page ICANN 61 - San Juan to ICANN 61 over redirect: Standardize |
||
| (7 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
{{ | {{ICANNMeetings| | ||
| | | logo = ICANN61logo.PNG | ||
| | | dates = March 10-15, 2018 | ||
| | | location = San Juan, Puerto Rico | ||
| | | host = | ||
| | | venue = | ||
| | | website = [https://meetings.icann.org/en/sanjuan61 ICANN 61] | ||
| | | totalregistrants = | ||
| registration = | |||
| keyappointments = | |||
| historicalimport = | |||
}} | }} | ||
'''ICANN 61''' | |||
'''ICANN 61''' marked the 2018 Community Forum and was held the week of '''9 March 2018'''. There were [[PDP|policy development processes]] in action, cross-community discussions, and organizational and outreach activities by various constituencies and stakeholder groups. | |||
==ICANNWiki Edit-a-thon== | ==ICANNWiki Edit-a-thon== | ||
| Line 16: | Line 20: | ||
This goal is achieved by hands-on instruction between ICANNWiki staff and interested participants. Adding relevant information to a multistakeholder-built and aggregated site such as ICANNWiki ensures that the community feels empowered to build and research information related to how the Internet is maintained as a resource. | This goal is achieved by hands-on instruction between ICANNWiki staff and interested participants. Adding relevant information to a multistakeholder-built and aggregated site such as ICANNWiki ensures that the community feels empowered to build and research information related to how the Internet is maintained as a resource. | ||
The aim in hosting this event is to lower the barrier to the information available, shine a light on it and, if possible, translate it into Spanish, Portuguese, Swahili, Chinese, and Russian for a stronger, more empowered, global community. | |||
The event will be followed by a reception dinner for participants with prizes, food and more! | The event will be followed by a reception dinner for participants with prizes, food and more! | ||
| Line 29: | Line 33: | ||
==Key Topics== | ==Key Topics== | ||
===GDPR and Interim WHOIS=== | ===GDPR and Interim WHOIS=== | ||
With May 25th and GDPR enforcement looming, an Interim compliance model is being developed by ICANN to replace the current model until the outcome of the Next Generation gTLD RDS to Replace WHOIS PDP is implemented. During this process, there have been several food metaphors invoked. It began with comparing the potential Interim model to a | With May 25th and GDPR enforcement looming, an Interim compliance model is being developed by ICANN to replace the current model until the outcome of the Next Generation gTLD RDS to Replace WHOIS PDP is implemented. During this process, there have been several food metaphors invoked. It began with comparing the potential Interim model to a Hawaiian pizza, creating controversy around the validity of pineapple as a pizza topping. Most recently, ICANN released its “Calzone Model” proposal on the 28th of February, seeking a balance between competing elements included in the community-submitted models and the comments on the ICANN-proposed models. However, at this point, an egg-based metaphor could be more apt, because no matter what’s included it’s going to be a scramble. | ||
Under this proposed, | Under this proposed model, the collection, transfer, and retention of the full Thick [[WHOIS]] remains largely unchanged. However, minimal data would be available to the public, including an anonymized email address or web contact form. Access to the full set of data would be available through a yet-to-determined accreditation process, creating a layered/tiered model. These changes apply to the collection and processing of data linked to the European Economic Area (EEA) and is optional outside of the EEA. They apply to both natural and legal persons. | ||
===Next-Gen RDS PDP=== | ===Next-Gen RDS PDP=== | ||
The [[Next Generation gTLD RDS to Replace WHOIS PDP Working Group]] was formed in November 2015 to define the purpose of collecting, maintaining and providing access to gTLD registration data, and to consider safeguards for protecting data, using the recommendations in the EWG's Final Report as an input to, and, if appropriate, as the foundation for a new gTLD policy. | The [[Next Generation gTLD RDS to Replace WHOIS PDP Working Group]] was formed in November 2015 to define the purpose of collecting, maintaining, and providing access to gTLD registration data, and to consider safeguards for protecting data, using the recommendations in the EWG's Final Report as an input to, and, if appropriate, as the foundation for a new gTLD policy. | ||
This process is particularly relevant, given the impact that the GDPR is going to have on WHOIS through an Interim model that will be in place until the implementation of the outputs from this PDP. | This process is particularly relevant, given the impact that the GDPR is going to have on WHOIS through an Interim model that will be in place until the implementation of the outputs from this PDP. | ||
'''At ICANN 61, this Working Group | '''At ICANN 61, this Working Group met twice:''' | ||
*GNSO RDS PDP Working Group Meeting[https://61.schedule.icann.org/meetings/647687 8:30 - 12:00, Saturday, Mar 10, 2018] | *GNSO RDS PDP Working Group Meeting[https://61.schedule.icann.org/meetings/647687 8:30 - 12:00, Saturday, Mar 10, 2018] | ||
*GNSO RDS PDP Working Group Meeting - [https://61.schedule.icann.org/meetings/647768 Wednesday, March 14, 15:15 – 18:30 pm] | *GNSO RDS PDP Working Group Meeting - [https://61.schedule.icann.org/meetings/647768 Wednesday, March 14, 15:15 – 18:30 pm] | ||
Latest revision as of 21:43, 11 April 2024
 | |
| Dates: | March 10-15, 2018 |
| Location: | San Juan, Puerto Rico |
| Website: | ICANN 61 |
ICANN 61 marked the 2018 Community Forum and was held the week of 9 March 2018. There were policy development processes in action, cross-community discussions, and organizational and outreach activities by various constituencies and stakeholder groups.
ICANNWiki Edit-a-thon[edit | edit source]
The ICANNWiki Edit-a-thon is a community-centered learning and sharing event that aims to make Internet governance and ICANN-related content more accessible.
This goal is achieved by hands-on instruction between ICANNWiki staff and interested participants. Adding relevant information to a multistakeholder-built and aggregated site such as ICANNWiki ensures that the community feels empowered to build and research information related to how the Internet is maintained as a resource.
The aim in hosting this event is to lower the barrier to the information available, shine a light on it and, if possible, translate it into Spanish, Portuguese, Swahili, Chinese, and Russian for a stronger, more empowered, global community.
The event will be followed by a reception dinner for participants with prizes, food and more!
| Session Details |
|---|
|
Key Topics[edit | edit source]
GDPR and Interim WHOIS[edit | edit source]
With May 25th and GDPR enforcement looming, an Interim compliance model is being developed by ICANN to replace the current model until the outcome of the Next Generation gTLD RDS to Replace WHOIS PDP is implemented. During this process, there have been several food metaphors invoked. It began with comparing the potential Interim model to a Hawaiian pizza, creating controversy around the validity of pineapple as a pizza topping. Most recently, ICANN released its “Calzone Model” proposal on the 28th of February, seeking a balance between competing elements included in the community-submitted models and the comments on the ICANN-proposed models. However, at this point, an egg-based metaphor could be more apt, because no matter what’s included it’s going to be a scramble.
Under this proposed model, the collection, transfer, and retention of the full Thick WHOIS remains largely unchanged. However, minimal data would be available to the public, including an anonymized email address or web contact form. Access to the full set of data would be available through a yet-to-determined accreditation process, creating a layered/tiered model. These changes apply to the collection and processing of data linked to the European Economic Area (EEA) and is optional outside of the EEA. They apply to both natural and legal persons.
Next-Gen RDS PDP[edit | edit source]
The Next Generation gTLD RDS to Replace WHOIS PDP Working Group was formed in November 2015 to define the purpose of collecting, maintaining, and providing access to gTLD registration data, and to consider safeguards for protecting data, using the recommendations in the EWG's Final Report as an input to, and, if appropriate, as the foundation for a new gTLD policy.
This process is particularly relevant, given the impact that the GDPR is going to have on WHOIS through an Interim model that will be in place until the implementation of the outputs from this PDP.
At ICANN 61, this Working Group met twice:
- GNSO RDS PDP Working Group Meeting8:30 - 12:00, Saturday, Mar 10, 2018
- GNSO RDS PDP Working Group Meeting - Wednesday, March 14, 15:15 – 18:30 pm
For more information: Full Article