----- Original Message ----- From: "Boyan Krosnov" <bkrosnov@lirex.bg> Can you please explain to us where exactly does your conclusion about "allocations flow" come from? I see the message posted to NANOG by the ARIN Director of Registration Services, Leslie Nobile, which says that IANA has allocated 82/8 to RIPE ====== Who is IANA ?..... Is ICANN IANA ? Is ARIN IANA ? Is the operator of the .ARPA servers IANA ? Who owns 82.IN-ADDR.ARPA ?....who updates that DNS entry ?...what is the value of that entry ? http://www.ngi.org/enum/pub/draft-iab-arpa-00.txt April 28, 2000 Mr. Louis Touton Vice-President, Secretary, and General Counsel Internet Corporation for Assigned Names and Numbers 4676 Admiralty Way, Suite 330 Marina del Rey, CA 90292 Re: Purchase Order No. 40SBNT067020: Administration of the ARPA Top Level Domain Dear Mr. Touton: As noted in your organization's quotation of February 2, 2000, the ARPA Top Level Domain (TLD) exists in the root zone of the domain name system as a limited use domain currently consisting of one record, in- addrARPA. On April 14, 2000, the Defense Advanced Research Projects Agency (DARPA), formerly known as the Advanced Research Projects Agency (ARPA), officially signaled its disassociation with the ARPA domain and its understanding the domain would be used by the Internet Corporation for Assigned Names (ICANN) and Numbers and the Internet Architecture Board (IAB) for additional Internet infrastructure uses. In keeping with the DARPA understanding, we believe that the ARPA domain should be made available for this specific, limited purpose. The Department of Commerce considers this an Internet Assigned Numbers Authority (IANA) function and has requested that the WHOIS entry for the ARPA domain reflect IANA as the registrant. Purchase Order No. 40SBNT067020 provides that "[ICANN] will perform other IANA functions as needed upon request of DOC." As such, the Department of Commerce requests that, as part of the IANA functions, ICANN undertake administration of the ARPA TLD in cooperation with the Internet technical community under the guidance of the IAB, as a limited use domain for Internet infrastructure applications, including the migration of Internet infrastructure applications that currently reside in the .int TLD. Further, as indicated by DARPA, the ARPA TLD string should be given a different expansion such as "Address and Routing Parameter Area" to avoid any implication that DARPA has operational responsibility for the domain. If you have any questions, please do not hesitate to contact me. Sincerely, Karen Rose Purchase Order Technical Representative

----- Original Message ----- From: "Boyan Krosnov" <bkrosnov@lirex.bg> Boyan Krosnov, CCIE#8701 http://boyan.ludost.net/ ==== BG was not selected for several reasons....the main one was that A would end up by itself... A...BG...HM...NR...SZ Since B is between A-M and A-C either of those nodes can be used to locate the BG TLD... It is up to the BG TLD Manager to then suggest that people use BG.AM or BG.AC... As for BG.EU that is a different plan some people have... Jim Fleming 128-bit DNS is closer than you think... IPv16...COM...NET...AM...NZ...AE...FM...NR...SZ...AC...DE...FI...JM...NO...PR...ST...UZ http://ipv8.dyndns.tv http://ipv8.dyns.cx http://ipv8.no-ip.com http://ipv8.no-ip.biz http://ipv8.no-ip.info http://ipv8.myip.us http://ipv8.dyn.ee