Changes

301 bytes added ,  12 years ago
no edit summary
Line 18: Line 18:  
[[ICANN]] 11 took place in Marina Del Ray, California. This was to be the second ICANN Event that was hosted on this area, and was also hosted in the same hotel, the Marina Beach Marriot Hotel. The meeting was the first event to not follow the original ICANN meeting format, as between the dates of the 13th – 15th November, all meetings were restricted to discuss the Security and Stability of the Internet naming and address allocation systems, which was to be followed by a meeting of the ICANN board of directors on the final afternoon.
 
[[ICANN]] 11 took place in Marina Del Ray, California. This was to be the second ICANN Event that was hosted on this area, and was also hosted in the same hotel, the Marina Beach Marriot Hotel. The meeting was the first event to not follow the original ICANN meeting format, as between the dates of the 13th – 15th November, all meetings were restricted to discuss the Security and Stability of the Internet naming and address allocation systems, which was to be followed by a meeting of the ICANN board of directors on the final afternoon.
   −
The First day of the event was still to be scheduled for an Open forum to discuss all other topics. As always the meetings on the first day, were not to be restricted, and were open for all interested persons to attend. Due to the heightened security status for the event, Pre-registration was required for all who wished to attend the meetings on the first day.
+
The First day of the event was still to be scheduled for an Open forum to discuss all other topics. As always the meetings on the first day, were not to be restricted, and were open for all interested persons to attend. Due to the heightened security status for the event, Pre-registration was required for all who wished to attend the meetings on the first day.<ref>[http://archive.icann.org/en/meetings/mdr2001/#agenda]</ref>
       
==Meeting==
 
==Meeting==
   −
This event was schedualed to hold various differnt sessions, over the four days the event had lasted. All sessions held a good reception and there were many topics and discussions as a part of these sessions. Some of the more disinguished sessions from the event were as follows -  
+
This event was schedualed to hold various differnt sessions, over the four days the event had lasted. All sessions held a good reception and there were many topics and discussions as a part of these sessions. Some of the more disinguished sessions from the event were as follows -<ref>[http://archive.icann.org/en/meetings/mdr2001/schedule.htm#agenda]</ref>
      Line 50: Line 50:  
==Developments==
 
==Developments==
   −
[[ICANN]] 11 had discuseed many key topics, with the main subject being on securirty and stability. This event held various sesison which included the use of panels.  
+
[[ICANN]] 11 had discuseed many key topics, with the main subject being on securirty and stability. This event held various sesison which included the use of panels. <ref>[http://archive.icann.org/en/meetings/mdr2001/schedule.htm#agenda]</ref>
      Line 78: Line 78:  
After a long and drawn out governmental procurement process, the United States Government had entered into an agreement with NeuStar, Inc. which was to provide registry services for the .us country-code top-level domain (ccTLD), which then replacing VeriSign, Inc. Consistent with this change in the contracted operators, on Friday, 16 November 2001, the .us ccTLD was to be redelegated from VeriSign to NeuStar.
 
After a long and drawn out governmental procurement process, the United States Government had entered into an agreement with NeuStar, Inc. which was to provide registry services for the .us country-code top-level domain (ccTLD), which then replacing VeriSign, Inc. Consistent with this change in the contracted operators, on Friday, 16 November 2001, the .us ccTLD was to be redelegated from VeriSign to NeuStar.
   −
This redelegation had occurred before the final completion of the normal IANA requirements. The United States Government had informed ICANN in the November of 2001 that, because of complexities of U.S. procurement laws, it was not able to now extend the existing arrangements with VeriSign nor were they able to complete the necessary three-way set of communications among itself, ICANN, and NeuStar. This then presented a peculiar set of circumstances: ICANN was now faced with the choice of either authorizing a redelegation, or creating a situation where the event could have occurred regardless, but there would be inconsistent data in the IANA database. Given ICANN's primary mission statement which is a  focus on stability (and security as part of achieving stability), ICANN had authorized an emergency redelegation prior to an appropriate contract.
+
This redelegation had occurred before the final completion of the normal IANA requirements. The United States Government had informed ICANN in the November of 2001 that, because of complexities of U.S. procurement laws, it was not able to now extend the existing arrangements with VeriSign nor were they able to complete the necessary three-way set of communications among itself, ICANN, and NeuStar. This then presented a peculiar set of circumstances: ICANN was now faced with the choice of either authorizing a redelegation, or creating a situation where the event could have occurred regardless, but there would be inconsistent data in the IANA database. Given ICANN's primary mission statement which is a  focus on stability (and security as part of achieving stability), ICANN had authorized an emergency redelegation prior to an appropriate contract.<ref>[http://www.icann.org/en/news/announcements/announcement-19nov01-en.htm]</ref>
    
==References==
 
==References==