[CWG-Stewardship] For your review - version V3.3

[Jaap Akkerhuis]

The discussion about INT last night made me have an close look at the INT pargraph at this version.

I do notice that

a) since .INT is already delegated, RFC 6761 (Special-Use Names)
   doesn't really play any roll here so there is no need to mention
   it;

b) likewise, there is no need to mention for what purose the eligible
   registrant might use it;

c) policy for INT is actually described in 1951 and further restricted
   to just the international organisations (See iana.org for the
   eligiblity rules. The last infrastructural database (ip6.int) was
   removed per RFC 4152 in 2005.

Therefore I propose the following rewrite of section e, page 36 (Final
Clean draft V3 in pdf).

Regards,

	jaap



----

e) Redelegation and Operation of the .INT TLD (NTIA IANA Functions
   Contract: C.2.9.4)

 * Description of the function: Historically, the policy for INT is
   described in IETF RFC 1591. The policy allowed registration for
   both international organisations and for use for international
   databases for infrastructure use. Specifically, the policy for INT
   related to international databases for infrastructure use was
   determined by the IETF. RFC 3172 recommended that such uses move
   under ARPA, and the only then-extant use of INT for such
   infrastructure (the IPv6 reverse mapping tree) was in fact moved
   under ARPA; all subsequent infrastructure uses have been under
   ARPA. Since this change, it is only possible for an international
   treaty organizations to register domain names under INT for use for
   the organization itself.

 * Customers of the function: Eligible registrants for registration in
   .INT (http://www.iana.org/domains/int/policy).


 * What registries are involved in providing the function: Root Zone
   database, Root Zone WHOIS, .INT Zone database, .INT WHOIS database.

 * Overlaps or interdependencies: Historically policy has partially
   been determined by IETF, however per RFC 3172, .INT is no longer
   used for international databases for infrastructure use, instead
   ARPA TLD is used for this.