Changes

Originally, .arpa was established as a temporary domain to serve as a transition mechanism for a set of host names in the [[ARPANET]] that were administered by [[DARPA]]. The host names were to be phased out after a replacement was created under the categorized TLDs which include [[.com]], [[.edu]], [[.mil]], [[.net]], [[.gov]] and [[.org]].<ref>[http://tools.ietf.org/rfc/rfc920.txt RFC 920]</ref> Although the initial plan for .arpa was to purge everything after the transition, the sub-domain in-addr.arpa remained active and it has been utilized for reverse [[DNS]] queries of [[IP Address|Internet Protocol addresses]].<ref>[http://tools.ietf.org/html/rfc3172#appendix-A RFC 3172]</ref>

Originally, .arpa was established as a temporary domain to serve as a transition mechanism for a set of host names in the [[ARPANET]] that were administered by [[DARPA]]. The host names were to be phased out after a replacement was created under the categorized TLDs which include [[.com]], [[.edu]], [[.mil]], [[.net]], [[.gov]] and [[.org]].<ref>[http://tools.ietf.org/rfc/rfc920.txt RFC 920]</ref> Although the initial plan for .arpa was to purge everything after the transition, the sub-domain in-addr.arpa remained active and it has been utilized for reverse [[DNS]] queries of [[IP Address|Internet Protocol addresses]].<ref>[http://tools.ietf.org/html/rfc3172#appendix-A RFC 3172]</ref>

In 2000, the IAB informed the technical community that .arpa had been re-designated as an Address and Routing Parameter Area. .arpa is to serve as a domain space where all new infrastructure sub-domains will be placed to maintain the stability of the internet. The IAB also recommended to the [[IESG|Internet Engineering Steering Group]] (IESG) that no new infrastructure domains were to be added to [[.int]], that protocols requiring specific domain roots should be rooted elsewhere, and that new infrastructure domains from the [[IETF|Internet Engineering Task Force]] (IETF) protocols must be allocated to the .arpa TLD. Management is to be handled by IANA. In addition. the IAB also suggested the review of all existing IETF infrastructures allocated under .int, and if the costs of transferring them is greater than the risk of staying in place. <ref>[http://www.iab.org/documents/correspondence-reports-documents/docs2000/iab-statement-on-infrastructure-domain-and-subdomains-may-2000/ IAB Statement on Infrastructure Domain and Subdomains, May 2000]</ref>

In 2000, the IAB informed the technical community that .arpa had been re-designated as an Address and Routing Parameter Area. .arpa is to serve as a domain space where all new infrastructure sub-domains will be placed to maintain the stability of the Internet. The IAB also recommended to the [[IESG|Internet Engineering Steering Group]] (IESG) that no new infrastructure domains were to be added to [[.int]], that protocols requiring specific domain roots should be rooted elsewhere, and that new infrastructure domains from the [[IETF|Internet Engineering Task Force]] (IETF) protocols must be allocated to the .arpa TLD. Management is to be handled by IANA. In addition. the IAB also suggested the review of all existing IETF infrastructures allocated under .int, and if the costs of transferring them is greater than the risk of staying in place. <ref>[http://www.iab.org/documents/correspondence-reports-documents/docs2000/iab-statement-on-infrastructure-domain-and-subdomains-may-2000/ IAB Statement on Infrastructure Domain and Subdomains, May 2000]</ref>

==Uses for .arpa==

==Uses for .arpa==