RFC
2870 - Root Name Server Operational Requirements
Doesn't seem to be THAT difficult ?
Anyone got the time to cost out how much it
would cost to configure something that more than meets the minimum
standard in the above document ?
Could this be a fast-track, quick-win project ?
-- Samiuela LV Taufa sa...@nomoa.com -or- samt...@gmail.com www.nomoa.com; www.tongatapu.net.to Ph: +676()62-717 Fax: +676()24-099
Sam Thanks for raising this important issue. The Department has many issues to resolve and this being one. Can you guess the other? What are your views on this? Malo Alfred
TO is a nomeclature chosen a long time ago by ITU for assigning shortened letters for individual countries in their 'network' of telephony services. ITU chose not to copyright the use of these two letter combinations and were subsequently adapted by ISO and the people who were putting the Internet together. TO is a standard for communications. TO may stand for Tonga, depending on who you're talking with. TO stands for Tonga to the ISO, and ICANN the internet numbers people. TN stands for Tonga to NATO (North Atlantic Treaty Organisation), FIPS U.S. Government for geographical data processing in many publications, such as the CIA World Factbook. TO to them stands for TOGO. TO is part of the standards for 2 letter representations, there are also 3 letter and 4 letter representations of countries. /Currency Three letter designation/. To designate currency, ISO standardised with the first letter of the currency "P" to the Two letter country name "TO" and we have "TOP" as the designation of our currency. Tonga TO + Pa'anga P ==> TOP United States of America US + Dollar D ==> USD Fiji FJ + Dollar D ==> FJD Australia AU + Dollar D ==> AUD But there are more than ISO standards for names. Tonga is referenced as TGA by the IOC, and FIFA but we are TON to the ISO-3Alpha and the UN. In the three digit classification, Tonga is designated by ITU as 676 (our telephone country code) but ISO/UN says we are 776. Can Tonga Own the equipment and organisation to service *.TO domain names? I don't know. RFC 2870 - Root Name Server Operational Requirements <http://www.faqs.org/rfcs/rfc2870.html>
Doesn't seem to be THAT difficult ? Anyone got the time to cost out how much it would cost to configure something that more than meets the minimum standard in the above document ? Could this be a fast-track, quick-win project ? -- Samiuela LV Taufa sa...@nomoa.com -or- samt...@gmail.com www.nomoa.com; www.tongatapu.net.to
Ph: +676()62-717 Fax: +676()24-099 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.