New Top Level Domains

Geoff Huston

IAHC

Top Level Domain Names Country-code name spaces

.au .jp .sg .de Special purpose name spaces

.in-addr.arpa .int .mil generic use name spaces

.com .net .org

Who’s who in Domain Names

ISOC

IAB

Delegated National Domain Administrators

InterNIC servicesNetwork Solutions

Charter and Appeal

Internet Assigned Numbers AuthorityIANA

.au

.com .net .org .edu .gov

Delegation

. (root name servers)

Delegation

Charter and Appeal

Generic TLDs InterNIC NSF CoA

.com .net .org

– Growth Issues- Contract service levels falling- Charging for .com- Exclusive trader concerns- Pressure to create “natural competition”- Renegade root name domains appear

But do we need more gTLDs?

We’re here

.... because we’re here

IAHC IANA proposal to create competition in

supply of gTLDs– more top level domains– more operators of these domains– ISOC endorsement

International Ad-Hoc Committee to– investigate policy issues– implement more gTLDs

Features of the IAHC proposal

– international– shared – operation

of a DNS registry environment for additional gTLDs

Shared Operation

The Registry and the Registrars– the registry is the data repository– The registrar is the agent providing data

updates

The Registrar’s Role certify the client’s identify certify the client’s request certify the validity of the transaction pass the data to the registry

Shared Registrars compete on

– services– price– charge models

Shared Registrars cooperate on

– domain policy– validity and integrity of registry transactions– registry interaction format– synchronisation of transactions

Shared Registrars competitive access to a common

underlying resource

The Registry’s Role provide a public record of association of

– an entity

with– a public resource (Domain Name)

provide processes to allow management of such associations

a network resource title office

Shared Registry single primary zone file constructed from

registry database multiple entry points for

– secure mechanism for initiating database update

– secure mechanism for distributing data updates May use replicated or distributed data

models

A Replicated Registry model Each registry has a unique identifier Each data item has a single-value

registry fielduser:Handle: GH29-AU

user:Registry: whois.aunic.net

A Replicated Registry model All updates to the data item are passed

to the referenced registry– The referenced registry imposes

synchronisation locks for the data item– The referenced registry initiates flood

update

whois.aunic.net

whois.reg1

whois.reg2

update GH29-AU

update GH29-AU

A Distributed Registry model Each data item exists in only one

registry All references to the data item are a

compound reference of registry identifier and a locally significant handle

whois://whois.aunic.net/user/GH29-AU

All updates are undertaken directly at the referenced registry

A Distributed Registry model The primary zone file is a data item of

references to delegated entries

for acme.bizwhois://whois.reg1/primary-zone/biz

acme.biz: whois://whois.reg1/primary-zone/acme.biz

whois://whois.reg1/primary-zone/acme.bizdomain: whois://whois.aunic.net/domain/acme.biz

Shared Registeries Do not exist at present Further effort required:

– developmental effort– trial implementations– testing– initial deployment– scaling of deployment

Activities Completion of IAHC report Agreement from referenced parties Implementation

– gTLDs– selection of registrars– development of shared registeries– oversight and evolution