ICANN ICANN Email List Archives

[soac-newgtldapsup-wg]


<<< Chronological Index >>>    <<< Thread Index >>>

[soac-newgtldapsup-wg] On the v6 requirement

  • To: "soac-newgtldapsup-wg@xxxxxxxxx" <SOAC-newgtldapsup-wg@xxxxxxxxx>
  • Subject: [soac-newgtldapsup-wg] On the v6 requirement
  • From: Eric Brunner-Williams <ebw@xxxxxxxxxxxxxxxxxxxx>
  • Date: Thu, 23 Dec 2010 08:51:51 -0500


Colleagues,

Yesterday I was able to obtain support from ARIN for new gTLD operators to be able to receive post-exhaustion provider independent address space from the reserve proposed for Criticial Infrastructure (CI).

While this does not assist any new gTLD operator demonstrate the v6 requirement that is in the DAG, it reduces the possible impulse for the contractual requirement, which is imposed as early as when the application is submitted (and "frozen"), or as late as the transition to delegation, if that impulse is that new gTLD registries must be able to operate in a post-v4-exhaustion environment.

Whether the v6 requirement is relaxed from an unconditional requirement, or made conditional upon the purpose of the applicant and therefore the presumed address capability of the registrars, registrants, and name-to-address resolving users, the access to CI reserved resources is something that needs-qualified applicants will benefit by, and not have to purchase provider independent v4 address assets in the transfer market, or settle for provider dependent v4 address assets as a tenant of a hosting operator, registry technical services provider, or competitor.

One more tool in the assistance toolkit. Post-v4-exhaustion PI blocks reserved for CI.

The proposal is ARIN-prop-123. Reserved Pool for Critical Infrastructure.

Next, making the same request to the other regional registries -- RIPE, APNIC, AfriNIC, LACNIC.

Eric



<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy