RFC 3071:Reflections on the DNS, RFC 1591, and Cat...
RFC-Ref

domain


Click on the red underlined text to get to the source

... delegation, and management of top- level domains. In particular, the ICANN Domain Name Supporting ...
... level domains. In particular, the ICANN Domain Name Supporting Organization (DNSO), and especially its ccTLD constituency, have been the home of many discussions ...
... described as generic TLDs would be bound to policies and categories of registration (see the "This domain is intended..." text in section 2) while ccTLDs were expected to be used primarily to support users and uses within and for a country and its residents. The ...
... section 2) while ccTLDs were expected to be used primarily to support users and uses within and for a country and its residents. The notion that different domains would be run in different ways --albeit within the broad contexts of "public service ...
... Internet has become more heavily used and, because the design of the world wide web has put domain names in front of users, top-level domain names and registrations ...
... world wide web has put domain names in front of users, top-level domain names and registrations in them have been heavily in demand: not only has the number of hosts ...
... hosts increased dramatically during that time, but the ratio between registered domain names and physical hosts has increased very significantly. ...
... of its elements have proven to work reasonably well, even in difficult situations. In particular, for many domains (some in 1591's "generic" list and others in its "country code" category) the ...
... qualifications, but where those qualifications are not tied to national boundaries. This list currently includes INT, EDU, the infrastructure domain ARPA, and, arguably, the specialized US Government TLDs MIL and GOV. There have been proposals from time ...
... describes them as "sponsored" TLDs. (iii) Country domains, operated according to the original underlying assumptions of 1591, i.e., registrants are largely expected to be people or other entities within the country. While ...
... registrations, nor does anyone expect to derive significant fee revenue from them. All current domains in this category are ccTLDs, but not all ccTLDs are in this category. ...
... the use of the IS 3166-1 registered code list [2] and two-letter "country" domain names. If that relationship is to be maintained (and I believe it is desirable), the only inherent requirement is ...


... ICANN and the community more generally to reduce controversies and move forward. Of course, there will be cases where the categorization of a particular domain and its operating style will not be completely clear-cut (see section 3, below). But having ICANN ...
... be required to have much interaction with ICANN or vice versa. Once a domain of this sort is established and delegated, and assuming that the "admin contact in the country" rule is strictly observed, the domain ...
... domain of this sort is established and delegated, and assuming that the "admin contact in the country" rule is strictly observed, the domain should be able to function effectively without ICANN intervention or oversight. In particular, while a country might ...
... management, issues that arise in these areas might equally well be dealt with exclusively under applicable national laws. If a domain chooses to use ICANN services that cost resources to provide, ...
... root servers, and any directory systems that are generally agreed upon to be necessary and in which the domain participates. ...
... By contrast, ccTLDs operated as generic domains ought to be treated as generic domains. ICANN ...
... By contrast, ccTLDs operated as generic domains ought to be treated as generic domains. ICANN dispute resolution and name management ...


... If appropriate policies are adopted, ccTLDs operated as generic domains (category (i) above) and those operated as country domains (category (iii) above) ought to be able to be self-identified. There ...
... If appropriate policies are adopted, ccTLDs operated as generic domains (category (i) above) and those operated as country domains (category (iii) above) ought to be able to be self-identified. There are several criteria that could be applied to make this ...
... (category (iii) above) ought to be able to be self-identified. There are several criteria that could be applied to make this determination. For example, either a domain is aggressively seeking outside registrations or it is not and either the vast majority of ...
... outside registrations or it is not and either the vast majority of registrants in a domain are in-country or they are not. One could also think of this as the issue of having some tangible level of presence in the jurisdiction - e.g., is the administrative contact ...
... registration rules such that it is reasonably likely that a court in the jurisdiction of the country associated with the domain can exercise jurisdiction and enforce a judgment against the registrant. ...
... One (fairly non-intrusive) rule ICANN might well impose on all top- level domains is that they identify and publish the policies they intend to use. E.g., registrants in a domain that will use the laws ...
... level domains is that they identify and publish the policies they intend to use. E.g., registrants in a domain that will use the laws of one particular country to resolve disputes should have a reasonable opportunity to understand those policies prior to ...
... IANA (as the root registrar) incorrect information about the purpose and use of a domain should be subject to challenge, and should be grounds for reviewing the appropriateness ...
... subject to challenge, and should be grounds for reviewing the appropriateness of the domain delegation, just as not acting consistently and equitably provides such grounds under the original provisions of RFC ...
... registration information the criteria must be consistent, and consistent with more traditional gTLDs, for all nominally country code domains operating as generic TLDs. ...


... The role of ICANN in country domains ...
... IANA) should, as described above, have as little involvement as possible in the direction of true country [code] domains (i.e., category (iii)). There is no particular reason why these domains should be subject ...
... domains (i.e., category (iii)). There is no particular reason why these domains should be subject to ICANN regulation beyond the basic ...


... ICANN to ask that the names be reserved. Then, since the reserved name would exist, they could insist that the domain be delegated. Worse, someone could use another organization to request reservation of the name by 3166/MA; ...
... ICANN could (and probably would be forced to) adopt additional criteria other than appearance on the "reserved list" in order to delegate such domains. But those criteria would almost certainly be nearly equivalent to determining which applicants were legitimate and stable enough to be considered a country, the ...
... Similar principles could be applied to the boundary between country- code-based generic TLDs and country domains. Different countries, under different circumstances, might prefer to operate the ccTLD either as a national service ...


... Postel, J., "Domain Name System Structure and Delegation", RFC 1591, March 1994. ...



Google
Web
RFC-Ref