This hands-on working session will allow the ICANN Thick WHOIS Implementation Team to review the status of key tasks, deliverables and timelines with the Implementation Review Team.
Cloud Computing Legal Risks And Best Practiceslisaabe
Cloud Computing: Legal Risks and Best Practices
1. Security and Data Privacy.
2. Recent OPC Guidelines.
3. Compliance Issues.
4. Negotiating Contracts with Cloud Providers.
5. New Trends and Challenges.
6. Practical Tips
An explanation of how Internet domain name and addressing policy is developed at ICANN. This is a presentation made by ICANN staff and used by me in my role as Subject Matter Expert for the At-Large's ATLAS II summit in London, June 2014. http://atlas.icann.org/
OSDC 2012 | Data Protection, Software Licences and other Legal Issues in the ...NETWAYS
Cloud computing and data protection are a bad match at first sight: On the one hand distributed data storage in an unknown IT infrastructure and on the other hand the requirement of a controlled data processing in a known environment. Add web services and you have issues regarding (software) licensing as well.
The talk will give an overview of legal hurdles that are to be overcome in Germany when dealing with cloud computing.
Cloud Computing Legal Risks And Best Practiceslisaabe
Cloud Computing: Legal Risks and Best Practices
1. Security and Data Privacy.
2. Recent OPC Guidelines.
3. Compliance Issues.
4. Negotiating Contracts with Cloud Providers.
5. New Trends and Challenges.
6. Practical Tips
An explanation of how Internet domain name and addressing policy is developed at ICANN. This is a presentation made by ICANN staff and used by me in my role as Subject Matter Expert for the At-Large's ATLAS II summit in London, June 2014. http://atlas.icann.org/
OSDC 2012 | Data Protection, Software Licences and other Legal Issues in the ...NETWAYS
Cloud computing and data protection are a bad match at first sight: On the one hand distributed data storage in an unknown IT infrastructure and on the other hand the requirement of a controlled data processing in a known environment. Add web services and you have issues regarding (software) licensing as well.
The talk will give an overview of legal hurdles that are to be overcome in Germany when dealing with cloud computing.
Vernon Technology Solutions offers clients the ability to rent computers and electronics and save money. Make sure to also check out their computer recycling services.
Infobrokering and Searching the Deep Web - the New Role of Employee of the Department of Medical Scientific Information.
Presentation from EAHIL Workshp Kraków 2007.
Ghassan Shahrour, The 70th anniversary of the atomic bombings at Hiroshima an...Ghassan Shahrour
The 70th anniversary of the atomic bombings at Hiroshima and Nagasaki by Ghasssan Shahrour, MD
Hiroshima Red Cross Hospital & Atomic-bomb Survivors Hospital
Dr Marcel Junod: like the palm of a hand.
‘We (…) witnessed a sight totally unlike anything we had ever seen before. The centre of the city was a sort of white patch, flattened and smooth like the palm of a hand. Nothing remained. The slightest trace of houses seemed to have disappeared.
Weapons must not cause damage to the natural environment that is widespread, long-term and severe.
The effects of nuclear weapons are catastrophic and cannot be contained.
Disarmament efforts and treaties
Potentially equal Hiroshima X 7
No adequate medical / humanitarian response would be possible
Blast could be followed by worldwide famin
ICRC General Assembly Conf. since 1948.
At NPT and IAEA.
- Partial Test Ban Treaty in 1963,
- Nuclear Non-proliferation Treaty in 1968,
- Comprehensive Nuclear-Test-Ban Treaty, 1996.
The Global Conference on the Catastrophic Humanitarian Consequences of any use of NWs in Oslo 2013, Mexico 2014 and Vienna 2014.
ICRC marks the 70th anniversary of the atomic bombings of Hiroshima and Nagasaki. This anniversary is a stark reminder of the appalling human costs of nuclear weapons. It should inspire all States to reaffirm their commitment to the elimination of nuclear weapons. We know now more than ever before that the risks of nuclear weapons are too high and the dangers too real. It is time to bring the era of nuclear weapons to an end and we urge this Review Conference to take the bold steps needed to achieve this noble goal.
My web typography presentation at Web Directions South 2010, Sydney: Setting standards-friendly web type. The talk focused on the options currently available for setting type on the web with a strong focus on webfonts (part one) and a supplementary section on then styling the selected type (lots of micro-typography; part two). Enjoy. (:
Presented by Paul Wilson, Director General of APNIC and Chair of APrIGF Multistakeholder Steering Group at the Asia Pacific Internet Leadership Program as part of 2016 APrIGF Taipei
ICANN 50: What’s New with the Global Domains DivisionICANN
This session provided an overview of the Global Domains Division (GDD) including its mission, structure and services. The overview was followed by a high-level update on the New gTLD Program, a wide range of domain name industry services and other high-interest topics. Time was allotted for questions and answers at the end of the session.
Vernon Technology Solutions offers clients the ability to rent computers and electronics and save money. Make sure to also check out their computer recycling services.
Infobrokering and Searching the Deep Web - the New Role of Employee of the Department of Medical Scientific Information.
Presentation from EAHIL Workshp Kraków 2007.
Ghassan Shahrour, The 70th anniversary of the atomic bombings at Hiroshima an...Ghassan Shahrour
The 70th anniversary of the atomic bombings at Hiroshima and Nagasaki by Ghasssan Shahrour, MD
Hiroshima Red Cross Hospital & Atomic-bomb Survivors Hospital
Dr Marcel Junod: like the palm of a hand.
‘We (…) witnessed a sight totally unlike anything we had ever seen before. The centre of the city was a sort of white patch, flattened and smooth like the palm of a hand. Nothing remained. The slightest trace of houses seemed to have disappeared.
Weapons must not cause damage to the natural environment that is widespread, long-term and severe.
The effects of nuclear weapons are catastrophic and cannot be contained.
Disarmament efforts and treaties
Potentially equal Hiroshima X 7
No adequate medical / humanitarian response would be possible
Blast could be followed by worldwide famin
ICRC General Assembly Conf. since 1948.
At NPT and IAEA.
- Partial Test Ban Treaty in 1963,
- Nuclear Non-proliferation Treaty in 1968,
- Comprehensive Nuclear-Test-Ban Treaty, 1996.
The Global Conference on the Catastrophic Humanitarian Consequences of any use of NWs in Oslo 2013, Mexico 2014 and Vienna 2014.
ICRC marks the 70th anniversary of the atomic bombings of Hiroshima and Nagasaki. This anniversary is a stark reminder of the appalling human costs of nuclear weapons. It should inspire all States to reaffirm their commitment to the elimination of nuclear weapons. We know now more than ever before that the risks of nuclear weapons are too high and the dangers too real. It is time to bring the era of nuclear weapons to an end and we urge this Review Conference to take the bold steps needed to achieve this noble goal.
My web typography presentation at Web Directions South 2010, Sydney: Setting standards-friendly web type. The talk focused on the options currently available for setting type on the web with a strong focus on webfonts (part one) and a supplementary section on then styling the selected type (lots of micro-typography; part two). Enjoy. (:
Presented by Paul Wilson, Director General of APNIC and Chair of APrIGF Multistakeholder Steering Group at the Asia Pacific Internet Leadership Program as part of 2016 APrIGF Taipei
ICANN 50: What’s New with the Global Domains DivisionICANN
This session provided an overview of the Global Domains Division (GDD) including its mission, structure and services. The overview was followed by a high-level update on the New gTLD Program, a wide range of domain name industry services and other high-interest topics. Time was allotted for questions and answers at the end of the session.
Webinar presented live on May 11, 2017.
As data is increasingly accessed and shared across geographic boundaries, a growing web of conflicting laws and regulations dictate where data can be transferred, stored, and shared, and how it is protected. The Object Management Group® (OMG®) and the Cloud Standards Customer Council™ (CSCC™) recently completed a significant effort to analyze and document the challenges posed by data residency. Data residency issues result from the storage and movement of data and metadata across geographies and jurisdictions.
Attend this webinar to learn more about data residency:
• How it may impact users and providers of IT services (including but not limited to the cloud)
• The complex web of laws and regulations that govern this area
• The relevant aspects – and limitations -- of current standards and potential areas of improvement
• How to contribute to future work
Read the OMG's paper, Data Residency Challenges and Opportunities for Standardization: http://www.omg.org/data-residency/
Read the CSCC's edition of the paper, Data Residency Challenges: http://www.cloud-council.org/deliverables/data-residency-challenges.htm
Purchasing from the Cloud, Cross Border Procurement and the role of GEANT as ...EOSC-hub project
EOSC-hub Week presentation as part of the session on Understanding the demand for digital services in research and the role of public procurement. Topics include GEANT introduction, supply chain, national deployments, NREN roles, Iaas framework updates, intro to IaaS and more
2.2. Case Study #2 DTGOVDTGOV is a public company that was crea.docxeugeniadean34240
2.2. Case Study #2: DTGOV
DTGOV is a public company that was created in the early 1980s by the Ministry of Social Security. The decentralization of the ministry’s IT operations to a public company under private law gave DTGOV an autonomous management structure with significant flexibility to govern and evolve its IT enterprise.
At the time of its creation, DTGOV had approximately 1,000 employees, operational branches in 60 localities nation-wide, and operated two mainframe-based data centres. Over time, DTGOV has expanded to more than 3,000 employees and branch offices in more than 300 localities, with three data centres running both mainframe and low-level platform environments. Its main services are related to processing social security benefits across the country.
DTGOV has enlarged its customer portfolio in the last two decades. It now serves other public-sector organizations and provides basic IT infrastructure and services, such as server hosting and server collocation. Some of its customers have also outsourced the operation, maintenance, and development of applications to DTGOV.
DTGOV has sizable customer contracts that encompass various IT resources and services. However, these contracts, services, and associated service levels are not standardized—negotiated service provisioning conditions are typically customized for each customer individually. DTGOV’s operations are resultantly becoming increasingly complex and difficult to manage, which has led to inefficiencies and inflated costs.
The DTGOV board realized, some time ago, that the overall company structure could be improved by standardizing its services portfolio, which implies the reengineering of both IT operational and management models. This process has started with the standardization of the hardware platform through the creation of a clearly defined technological lifecycle, a consolidated procurement policy, and the establishment of new acquisition practices.
Technical Infrastructure and Environment
DTGOV operates three data centres: one is exclusively dedicated to low-level platform servers while the other two have both mainframe and low-level platforms. The mainframe systems are reserved for the Ministry of Social Security and therefore not available for outsourcing.
The data centre infrastructure occupies approximately 20,000 square feet of computer room space and hosts more than 100,000 servers with different hardware configurations. The total storage capacity is approximately 10,000 terabytes. DTGOV’s network has redundant high-speed data links connecting the data centres in a full mesh topology. Their Internet connectivity is considered to be provider-independent since their network interconnects all of the major national telecom carriers.
Server consolidation and virtualization projects have been in place for five years, considerably decreasing the diversity of hardware platforms. As a result, systematic tracking of the investments and operational costs related to th.
ICANN 51: Rights Protection Mechanisms: User Feedback SessionICANN
ICANN put in place robust Rights Protection Mechanisms (RPMs) for the roll out of the New gTLD Program. One year later, we are gathering feedback from IP stakeholders, trademark rights holders, registries and registrars who have used the Trademark Clearinghouse and Claims service, the Uniform Rapid Suspension (URS) system, and the Post-Delegation Dispute Resolution Procedures (PDDRPs). This vital feedback will help inform forthcoming reviews of the RPMs.
A presentation on cloud computing and its impact in the boardroom. Presented to the Australian Institute of Company Directors , this presentation covers:
1. What legal contracts and provisions should be put in place for IT?
2. Liability issues – what insurance do you need?
3. Privacy obligations and protecting data – key legislation and its application
Brendon Noney
Privacy and the GDPR: How Cloud computing could be your failingIT Governance Ltd
This webinar covers:
- An overview of the GDPR
- Breach notification requirements under the GDPR and a showcase of recent data breaches and their costs
- Organisations' responsibilities when storing data in the Cloud, and the roles of controller and processor
- The outcome of subcontracting on Cloud service providers and notifications on activities in the Cloud
- The role and responsibilities of the Cloud adoption team
- ISO 27018 and implementing security controls for PII in the Cloud.
A recording of this webinar is available here:
https://www.youtube.com/watch?v=mcLPEEGqvr4
KT/KTDS Case Study: Open Source Database Adoption in TelecomEDB
Join this session to hear this real-life story from KT/KTDS. They will share the experience of the migration of their Oracle Database to EDB Postgres. Their story will include adoption history, technology verification, governance, diffusion, adoption effect and open source database technical support. Furthermore, they will discuss their application methodology approach and migration tools deployed. Don't miss this session to learn from their experience and insights.
In today's fast paced and digital world, many in government are looking to the cloud as a means to transform their agency. The cloud allows us to easily collaborate, share resources, receive on demand computing power, and change the way we deliver services to citizens. With the cloud, this all can be done faster and more efficiently than ever before.
There has been continuing interest in the expansion of the gTLD ecosystem, and one of the questions most often posed is “When will the next application round commence?” Join this session for an update on the next steps and estimated timeframes for a new phase of additional choice and competition on the Internet.
ICANN Expected Standards of Behavior | FrenchICANN
Those who take part in ICANN's multistakeholder process, including Board, staff and all those involved in Supporting Organization and Advisory Committee councils undertake to...
Those who take part in ICANN's multistakeholder process, including Board, staff and all those involved in Supporting Organization and Advisory Committee councils undertake to...
ICANN Expected Standards of Behavior | RussianICANN
Those who take part in ICANN's multistakeholder process, including Board, staff and all those involved in Supporting Organization and Advisory Committee councils undertake to...
ICANN Expected Standards of Behavior | ArabicICANN
Those who take part in ICANN's multistakeholder process, including Board, staff and all those involved in Supporting Organization and Advisory Committee councils undertake to...
ICANN Expected Standards of Behavior | ChineseICANN
Those who take part in ICANN's multistakeholder process, including Board, staff and all those involved in Supporting Organization and Advisory Committee councils undertake to...
ICANN Expected Standards of Behavior | SpanishICANN
Those who take part in ICANN's multistakeholder process, including Board, staff and all those involved in Supporting Organization and Advisory Committee councils undertake to...
APNIC Foundation, presented by Ellisha Heppner at the PNG DNS Forum 2024APNIC
Ellisha Heppner, Grant Management Lead, presented an update on APNIC Foundation to the PNG DNS Forum held from 6 to 10 May, 2024 in Port Moresby, Papua New Guinea.
Gen Z and the marketplaces - let's translate their needsLaura Szabó
The product workshop focused on exploring the requirements of Generation Z in relation to marketplace dynamics. We delved into their specific needs, examined the specifics in their shopping preferences, and analyzed their preferred methods for accessing information and making purchases within a marketplace. Through the study of real-life cases , we tried to gain valuable insights into enhancing the marketplace experience for Generation Z.
The workshop was held on the DMA Conference in Vienna June 2024.
Italy Agriculture Equipment Market Outlook to 2027harveenkaur52
Agriculture and Animal Care
Ken Research has an expertise in Agriculture and Animal Care sector and offer vast collection of information related to all major aspects such as Agriculture equipment, Crop Protection, Seed, Agriculture Chemical, Fertilizers, Protected Cultivators, Palm Oil, Hybrid Seed, Animal Feed additives and many more.
Our continuous study and findings in agriculture sector provide better insights to companies dealing with related product and services, government and agriculture associations, researchers and students to well understand the present and expected scenario.
Our Animal care category provides solutions on Animal Healthcare and related products and services, including, animal feed additives, vaccination
1. Text
Thick Whois Implementation
Working Session
#ICANN51
16 October 2014
Fabien Betremieux
Senior Services & Engagement Manager
Registry Services Team
2. Agenda
Text
• Background
• Implementation Considerations
• Impact on Affected Parties
• Current Status of Implementation
• Proposed Next Steps
• Discussion with IRT
#ICANN51
4. Milestones
Text
30 May 2011 IRTP B Working Group recommended requiring Thick Whois
#ICANN51
for incumbent registries in order to improve security, stability and
reliability of the domain transfer process
14 Mar. 2012 GNSO Council initiated a Policy Development Process regarding the
use of thick Whois by all gTLD registries, existing and future
21 Oct. 2013 The Thick Whois PDP Working Group reached full consensus on
the recommendations
31 Oct. 2013 GNSO Council recommended the adoption of the recommendations
from the Working Group by the ICANN Board, subject to review by an
Implementation Review Team
7 Feb. 2014 ICANN Board adopted the GNSO Council Policy Recommendations
and directed the President and CEO to develop and execute on an
implementation plan consistent with the guidance provide by the GNSO
Council
5. WG Deliberations on the value of Thick Whois
Text
• Improved response consistency
• Improved stability (increased availability in case of business/technical failure)
• Improved access to Whois data (registry vs. registrars accessibility)
• No specific data protection issues (in addition to already known issues)
• Privacy issues are much larger than the policy issue of migrating to thick Whois
• No overly burdensome cost impact on providers of Whois data
• No detrimental effect of transition from thin to thick on data synchronization
• No detrimental effect on authoritativeness (specific policy not necessary)
• More level playing field for competition between registry providers
• No substantive detrimental effect on existing Whois application
• More copies of escrowed data in the event of a failure
• Irrelevance of Port 43 Whois requirement for registrar addressed in RAA 2013
#ICANN51
6. Recommendations of the WG
Text
1. The provision of thick Whois services,
with a consistent labeling and display as per the model outlined
in specification 3 of the 2013 RAA, should become a requirement
for all gTLD registries, both existing and future
2. Following the adoption of this report and recommendations by the
GNSO Council, the subsequent public comment forum (prior to Board
consideration) and the notification by the ICANN Board to the GAC,
specifically request input on any considerations related to the
transition from thin to thick Whois that would need to be taken into
account as part of the implementation process
#ICANN51
7. Recommendations of the WG
Text
3. As part of the implementation process, a legal review of law
applicable to the transition of data from a thin to thick model
not already been considered in the EWG memo is undertaken,
and due consideration is given to potential privacy issues that may
arise from the discussions on the transition from thin to thick
Whois, including, for example, guidance on how the long-standing
contractual requirement that registrars give notice to, and obtain
consent from, each registrant for uses of any personally identifiable
data submitted by the registrant should apply to registrations involved
in the transition. Should any privacy issues emerge from these
transition discussions that were not anticipated by the WG and
which would require additional policy consideration, the
Implementation Review Team is expected to notify the GNSO
Council of these so that appropriate action can be taken
#ICANN51
8. EWG Memo
Text
• Staff paper to the Expert Working Group on gTLD registration data
(29 August 2013)
o Scope: General principles of international data protection laws with respect to the
use, processing and transfer of personal data
in connection with (…) a Whois database replacement platform
• Main contributions relevant to thick Whois Policy implementation
o The administration of the Whois database may implicate the laws of (i) the country
where the Whois database platform is located, (ii) the country where the data owner/
licensor/controller (controller) is located, (iii) the country where the data subjects (e.g.,
registrants) are located
o Generally speaking, E.U. Data Protection Directive 95/46/EC imposes the most
comprehensive and stringent standards on data collection, processing, and transfers
o The purpose for which data was originally collected is of greatest importance and
impacts the application of the remaining data privacy and protection principles
o The transfer of personal data will likely require data subject consent
#ICANN51
10. Implementation Considerations (§7.2)
Text
Costs
implications
#ICANN51
• One-off costs expected in the transition from thin to thick,
with implementation synergies that could minimize such costs
(e.g. synchronize transfer of data with escrow data submissions)
• Hardly any learning curve or software development expected
Existing
provisions or
exemptions
No impact expected on :
• 2013 RAA-based waiver in the collection/retention of data
element violating applicable local law
• Procedure for handling Whois conflicts with privacy law
Guidelines for
conducting
transition
• Implementation of one part of the recommendation (transition
from thin to thick) should not necessarily delay the
implementation of another part of the recommendation
(consistent labeling and display of data)
• A team of experts from parties most affected by this transition
should work out the details with ICANN staff
• Valuable information may be learned from the transition of .org
• Implementation plan shared with the community for input
12. Provision of Thick Whois Services
Text
Affected
#ICANN51
TLDs
.COM .NET .JOBS
Currently operating under
a thin Whois model
All other gTLDs,
current and future
Operating a thick Whois model
Registries VeriSign, Inc
Employ Media LLC All Others
Registrars 959 entities
(as of June 2014)
327 (RAA 2009)
833 (RAA 2013)
(as of 12 Oct 2014)
Impact
Registries
Whois & SRS development
Data transfer, management &
storage
None
Registrars
EPP implementation Update
Whois systems update
End of Port 43 requirement
None
Registrants
Potential change to terms of
registrations
Potential privacy issues
None
End-users Potential change of source for
Whois information None
13. Consistent Labeling & Display Per 2013 RAA
Text
#ICANN51
Affected
TLDs
All gTLDs,
current and future
Registries
Registrars
327 (RAA 2009)
833 (RAA 2013)
(as of 12 Oct 2014)
Impact
Registries
Whois data structure
Whois output (format + data)
SRS EPP extension
Registrars SRS EPP extension
(new data to be provided to Ry)
Registrants None
End-users Modification of output
14. Summary of Expected Outcomes
Text
1. Transition from thin to thick Whois for .COM, .NET
and .JOBS, including:
- Legal review of laws applicable to the transition of data
- Due consideration to privacy issues that may arise
- Careful preparation and implementation (number of registrations)
2. Consistent labeling & display as per the model outlined in
Specification 3 of the 2013 RAA
#ICANN51
16. Text
Current Implementation Plan 2014-2015
Development of implementation plan,
documents and guidelines
Legal Review
Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun
2014 2015
Registries Draft
Implementation
Plan
Community outreach
& industry education Webinar
for Ry/Rr Publish
FAQ
17. Text
Current Implementation Plan 2015-2016
Preparation for
Transition by
Registries and
Registrars
Transition to
Thick Whois
registration
Registries and
Registrars conduct
testing (OT&E)
Data Transfer
from Registrars
to Registries
Post-transition
verification &
problem
resolution
Jun Aug Oct Dec Feb Apr
2015 2016
Post Data
Transfer
issue
resolution
Jul Sep Nov Jan Mar May Jun Jul Aug Sep Oct Nov Dec
18. Legal Review
Text
• Status
o Legal research and analysis started in August 2014
o Conclusions to be available in November
• Scope
o Consistent with recommendation #3 of the WG
o Issues associated with the transition from thin to thick Whois
o Focus on specific new risks, if any, that may be posed by the
transition to the thick Whois model for the three impacted TLDs
#ICANN51
19. Legal Review Focus (1)
Text
• What type of personal data issues may arise in the
transition from thin to thick Whois ?
o Data protection: are the RAA requirements sufficient ?
o Registrant consent to the sharing of personal data:
§ Currently sufficient to authorize transition and display by registry ?
§ How broad does it need to be, can it be revoked ?
o Would there be a registrant right to require correction and erasure ?
o Is the transfer of data permissible from registrars located in various
jurisdictions to a registry operator in the United States ? If so, what
mechanisms must be in place ?
#ICANN51
20. Legal Review Focus (2)
Text
• What practical solutions would be available to facilitate the
implementation of thick Whois in terms of cross-border data
transfer ?
o Standard clauses in the registration agreements
o Safe harbors frameworks
o Regionalization of data stores
o Mandatory notices and purpose descriptions to registrants
o Data Protection requirements, specifications, limitations
o Onward transfer agreements with adequate protections for third
parties managing thick Whois data
#ICANN51
21. Implementation Documentation - Drafting
Text
• Guidelines to Registries and Registrars on Transition
- Inform affected parties on requirements, process and timeline
- Includes best practices and input from affected parties
• Transition Verification Document
- Support and monitor the timely transition form thin to thick Whois
- Explain purpose and roles of parties involved
• (Post-)Transition Problem Resolution Plan
- Support problem resolution of issues in transition form thin to thick
- Lists possible issues and mitigation measures
#ICANN51
23. Proposed Next Steps
Text
1. Decoupling implementation of the two expected outcomes
2. Inviting experts from parties most affected by the
transition from thin to thick to work out implementation
details
3. Discussing the opportunity of synchronizing Thick Whois
Implementation with a potential roll out of RDAP
4. Next meetings on Thick Whois Implementation
#ICANN51
24. Proposed Next Steps (1)
Text
• Decoupling implementation of the two expected outcomes
o Guideline for implementation from the WG Final Report
#ICANN51
25. Text
Proposed Overall Timeline 2014-2016
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2014 2015
2016
Legal Review
Transition
from thin to thick Whois
of .COM, .NET, .JOBS
26. Text
Proposed Overall Timeline 2014-2016
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2014 2015
2016
Legal Review
Transition
from thin to thick Whois
of .COM, .NET, .JOBS
Consistent labeling
and display
of Whois output
as per RAA 2013
27. Text
Proposed Overall Timeline 2014-2016
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2014 2015
2016
Legal Review
Preparation for
implementation of transition
Implementation of
transition by affected
parties
Transition
from thin to thick Whois
of .COM, .NET, .JOBS
Consistent labeling
and display
of Whois output
as per RAA 2013
28. Text
Proposed Overall Timeline 2014-2016
Implementation by affected parties
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2014 2015
2016
Legal Review
Preparation for
implementation of transition
Implementation of
transition by affected
parties
Transition
from thin to thick Whois
of .COM, .NET, .JOBS
Consistent labeling
and display
of Whois output
as per RAA 2013
Implementation
plan and outreach Notice to affected parties
Effective date
29. Proposed Next Steps (1)
Text
• Decoupling implementation of the two expected outcomes
o Guideline for implementation from the WG Final Report
o Benefit: Incremental and more timely delivery of outcomes
o To be adressed:
- More analysis of impact on affected parties of consistent labeling &
display of Whois output per RA 2013
- Detailed implementation plan
- What requirement for Thin Whois Registries (not transitionned yet) ?
#ICANN51
30. Proposed Next Steps (2)
Text
• Inviting experts from parties most affected by the transition
from thin to thick to work out implementation details
#ICANN51
31. Text
Proposed Overall Timeline 2014-2016
Implementation by affected parties
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2014 2015
2016
Legal Review
Preparation for
implementation of transition
Implementation of
transition by affected
parties
Transition
from thin to thick Whois
of .COM, .NET, .JOBS
Consistent labeling
and display
of Whois output
as per RAA 2013
Implementation
plan and outreach Notice to affected parties
Effective date
32. Text
Proposed Overall Timeline 2014-2016
Implementation by affected parties
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2014 2015
2016
Legal Review
Design of implementation
plan with experts from
affected parties
Preparation for
implementation of transition
Implementation of
transition by affected
parties
Transition
from thin to thick Whois
of .COM, .NET, .JOBS
Consistent labeling
and display
of Whois output
as per RAA 2013
Implementation
plan and outreach Notice to affected parties
Effective date
33. Proposed Next Steps (2)
Text
• Inviting experts from parties most affected by the transition
from thin to thick to work out implementation details
o Who should be invited ? How should we reach out to them ?
o How should these experts be assembled ? As a specific team, for a
limited duration ? Or simply by joining the IRT ?
#ICANN51
34. Proposed Next Steps (3)
Text
• Discussing the opportunity of synchronizing Thick Whois
Implementation with a potential roll out of RDAP
o Registration Data Access Protocal (RDAP)
o IETF development since 2012, stemming from SAC 051 Advisory for
the ICANN community to evaluate and adopt a replacement to Whois
o Expected Standardization of RDAP RFCs in the coming months
o Potential synergies with thick Whois Implementation
- Redirect features could help with potential data transfer issues
- RDAP could be an incremental step towards a potential policy outcome
from the EWG report
#ICANN51
35. Proposed Next Steps (4)
Text
• Next Meetings on Thick Whois Implementation
o IRT Meetings
- Thursday 30 October 14:00 UTC
- Thursday 27 November 14:00 UTC
o Experts Meetings on thin to thick Whois transition – TBD with IRT
#ICANN51