Changes

</div>

</div>

</div>

</div>

<h2 class="sectionheader2"><span style="margin:25px 0 0 15px;font-size:2.5vw;">Venue Map</span></h2>

<h2 class="sectionheader2"><span style="margin:25px 0 0 15px">Venue Map</span></h2>

<div class="mw-collapsible-content>

<div class="mw-collapsible mw-collapsed">

<div class=" mw-collapsible-content flexbox">

<br />

[[File:VenueMap.png|class=venuemap]]

[[File:VenueMap.png|class=venuemap]]

</div>

</div>

</div>

</div></div>

     <h1 class="sectionheader"><span style="padding:0 0 0 15px;font-size:2.5vw;">Edit-a-Thon</span></h1>

     <h1 class="sectionheader"><span style="padding:0 0 0 15px;font-size:2.5vw;">Edit-a-Thon</span></h1>

<div class="flexbox mw-collapsible mw-collapsed">

<div class="flexbox mw-collapsible mw-collapsed">

<h1 class="sectionheader"><span style="padding:0 0 0 15px;font-size:2.5vw;">Key Topics</span></h1>

<h1 class="sectionheader"><span style="padding:0 0 0 15px;font-size:2.5vw;">Key Topics</span></h1>

<div class="flexbox mw-collapsible mw-collapsed" >

<div class="flexbox mw-collapsible mw-collapsed" >

<div class="mw-collapsible mw-collapsed">

<div class="mw-collapsible mw-collapsed">

<h2 class="sectionheader2"><span style="margin:25px 0 0 15px">IANA Transition</span></h2>

<div style="wdith:100%;height:40px;background-color:transparent;"></div>

<div class="mw-collapsible-content primertextbox">  

<div class="mw-collapsible-content primertextbox">  

In March 2014, the US Department of Commerce’s National Telecommunications and Information Administration announced its intention to transition the  oversight role of the IANA Functions to the global multistakeholder community on 30 September 2015 (later extended to 30 September 2016). The announcement asked ICANN to initiate a multistakeholder process to develop a proposal to be submitted to the NTIA for approval. The proposal requires broad support and follows the following principles:

In March 2014, the US Department of Commerce’s National Telecommunications and Information Administration announced its intention to transition the  oversight role of the IANA Functions to the global multistakeholder community on 30 September 2015 (later extended to 30 September 2016). The announcement asked ICANN to initiate a multistakeholder process to develop a proposal to be submitted to the NTIA for approval. The proposal requires broad support and follows the following principles:

*Support and enhance the multistakeholder model

*Support and enhance the multistakeholder model

</div></div>

</div></div>

<div class="mw-collapsible mw-collapsed">

<div class="mw-collapsible mw-collapsed">

<h2 class="sectionheader2"><span style="margin:25px 0 0 15px">Enhancing ICANN Accountability</span></h2>

<div style="wdith:100%;height:40px;background-color:transparent;"></div>

<div class=" mw-collapsible-content primertextbox">

<div class=" mw-collapsible-content primertextbox">

During initial discussions relating to the IANA Stewardship Transition, the ICANN community raised concerns about the impact that the transition would have on ICANN Accountability. In response, the Enhancing ICANN Accountability process was launched to develop a proposal, seeking to implement accountability measures that will hold ICANN accountable to the global stakeholder community in the absence of the “accountability backstop” provided by the historical contractual relationship with the U.S. Government. This proposal is the final piece of the IANA Transition puzzle and when submitted to the ICG will complete the proposal that the U.S. government asked for two years ago, in March 2014.

During initial discussions relating to the IANA Stewardship Transition, the ICANN community raised concerns about the impact that the transition would have on ICANN Accountability. In response, the Enhancing ICANN Accountability process was launched to develop a proposal, seeking to implement accountability measures that will hold ICANN accountable to the global stakeholder community in the absence of the “accountability backstop” provided by the historical contractual relationship with the U.S. Government. This proposal is the final piece of the IANA Transition puzzle and when submitted to the ICG will complete the proposal that the U.S. government asked for two years ago, in March 2014.

On 23 February 2016, after the necessary changes had been made the CCWG released the supplemental final proposal in time for the Chartering Organizations to deliberate prior to ICANN 55. If it is approved by all of the organizations, the proposal will be ready to submit to the ICANN Board, which will then be able to send the a complete proposal to the NTIA.

On 23 February 2016, after the necessary changes had been made the CCWG released the supplemental final proposal in time for the Chartering Organizations to deliberate prior to ICANN 55. If it is approved by all of the organizations, the proposal will be ready to submit to the ICANN Board, which will then be able to send the a complete proposal to the NTIA.

</div></div>

</div></div>

<div class=" mw-collapsible mw-collapsed">

<div class=" mw-collapsible mw-collapsed">

<h2 class="sectionheader2"><span style="margin:25px 0 0 15px">Next-Gen RDS</span></h2>

<div style="wdith:100%;height:40px;background-color:transparent;"></div>

<div class="mw-collapsible-content primertextbox">

<div class="mw-collapsible-content primertextbox">

WHOIS was created in the 1980s as a service to identify network operators on the Internet. Since this time, the Internet has changed far beyond expectations, evolving from a research network into a global commercial network that is integrated into everyday life. The usage of WHOIS has changed along with the evolution of the Internet, but the protocol has changed very little.

WHOIS was created in the 1980s as a service to identify network operators on the Internet. Since this time, the Internet has changed far beyond expectations, evolving from a research network into a global commercial network that is integrated into everyday life. The usage of WHOIS has changed along with the evolution of the Internet, but the protocol has changed very little.

As these processes develop, the outdated WHOIS Policy and Protocol will receive an overdue update, making improvements on the issues of accuracy, privacy and access. The Next-Gen PDP WG will hold their first face-to-face meeting at ICANN 55 to work toward their phase one goals.  

As these processes develop, the outdated WHOIS Policy and Protocol will receive an overdue update, making improvements on the issues of accuracy, privacy and access. The Next-Gen PDP WG will hold their first face-to-face meeting at ICANN 55 to work toward their phase one goals.  

</div></div>

</div></div>

<div class=" mw-collapsible mw-collapsed">

<div class=" mw-collapsible mw-collapsed">

<h2 class="sectionheader2"><span style="margin:25px 0 0 15px">Universal Acceptance</span></h2>

<div style="wdith:100%;height:40px;background-color:transparent;"></div>

<div class="mw-collapsible-content primertextbox">

<div class="mw-collapsible-content primertextbox">

Universal Acceptance is the state in which all valid domains names are useable in all Internet enabled applications, devices, and systems regardless of length, script, or newness to the DNS.

Universal Acceptance is the state in which all valid domains names are useable in all Internet enabled applications, devices, and systems regardless of length, script, or newness to the DNS.

             <div class="AcronymButton" type="button" data-hover="Registrar Stakeholder Group" data-active="Registrar Stakeholder Group"><span>RrSG</span></div>

             <div class="AcronymButton" type="button" data-hover="Registrar Stakeholder Group" data-active="Registrar Stakeholder Group"><span>RrSG</span></div>

             <div class="AcronymButton" type="button" data-hover="World Wide Web Consortium" data-active="World Wide Web Consortium"><span>W3C</span></div>

             <div class="AcronymButton" type="button" data-hover="World Wide Web Consortium" data-active="World Wide Web Consortium"><span>W3C</span></div>

           </div>

           </di

 

 

 

     </div>

     </div>

     </div>

     </div>

     <h1 class="sectionheader"><span style="padding:0 0 0 15px;font-size:2.5vw;">Fadi Farewell</span></h1>

     <h1 class="sectionheader"><span style="padding:0 0 0 15px;font-size:2.5vw;">Fadi Farewell</span></h1>