New Top Level Domains Geoff Huston IAHC

Top Level Domain Names l Country-code name spaces.au.jp.sg.de l Special purpose name spaces.in-addr.arpa.int.mil l generic use name spaces.com.net.org

Who’s who in Domain Names ISOC IAB Delegated National Domain Administrators InterNIC services Network Solutions Charter and Appeal Internet Assigned Numbers Authority IANA.au.com.net.org.edu.gov Delegation. (root name servers) Delegation Charter and Appeal

Generic TLDs l 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 l IANA proposal to create competition in supply of gTLDs –more top level domains –more operators of these domains –ISOC endorsement l 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 l The Registry and the Registrars –the registry is the data repository –The registrar is the agent providing data updates

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

Shared Registrars l compete on –services –price –charge models

Shared Registrars l cooperate on –domain policy –validity and integrity of registry transactions –registry interaction format –synchronisation of transactions

Shared Registrars l competitive access to a common underlying resource

The Registry’s Role l provide a public record of association of –an entity with –a public resource (Domain Name) l provide processes to allow management of such associations l a network resource title office

Shared Registry l single primary zone file constructed from registry database l multiple entry points for –secure mechanism for initiating database update –secure mechanism for distributing data updates l May use replicated or distributed data models

A Replicated Registry model l Each registry has a unique identifier l Each data item has a single-value registry field user:Handle: GH29-AU user:Registry: whois.aunic.net

A Replicated Registry model l 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

A Distributed Registry model l Each data item exists in only one registry l 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 l All updates are undertaken directly at the referenced registry

A Distributed Registry model l The primary zone file is a data item of references to delegated entries for acme.biz whois://whois.reg1/primary-zone/biz acme.biz: whois://whois.reg1/primary-zone/acme.biz whois://whois.reg1/primary-zone/acme.biz domain: whois://whois.aunic.net/domain/acme.biz

Shared Registeries l Do not exist at present l Further effort required: –developmental effort –trial implementations –testing –initial deployment –scaling of deployment

Activities l Completion of IAHC report l Agreement from referenced parties l Implementation –gTLDs –selection of registrars –development of shared registeries –oversight and evolution