Dedicated to preserving the central coordinating functions of the global Internet for the public good.

1

• Dedicated to preserving the central coordinating
  functions of the globalInternet for the public
  good.
• John L. Crain, Chief Technical Officer, ICANN
• crain_at_icann.org

2
A little about the IANA

• Jon Postel first started keeping track of numbers
  around 1969. (In a notebook)
• Added staff in the early 80s (Joyce Reynolds,
  now RFC editor)
• Started being called the IANA in the late 80s
• Became a function of ICANN in 1998

3
What does the IANA do?

• Registers Unique Identifiers and related
  information for use on the Internet.
• IP Addresses, AS s, Port s, many others
  including TLDs in the root.
• That last bit effects you ?

4
Country Code Top Level Domains

• Referred to as a CcTLD
• codes are assigned from a table known as
  ISO-3166-1
• IANA current practices summary is called ICP1
• http//www.icann.org/icp/icp-1.htm

5
Services for CcTLDs

• Mainly related to changes in the root zone or
  whois data.
• Change of DNS servers
• Change of IP addresses for DNS servers
• Change of POC details (Point Of Contact)

6
CcTLD changes

• Make sure you have all of your data in order
• Check at
• http//www.iana.org/cctld/cctld-whois.htm

7
Samples

• http//www.iana.org/root-whois/nl.htm
• .nl Netherlands
• http//www.iana.org/root-whois/br.htm
• .br - Brazil

8
Making Changes

• Be sure of the changes that you want to make!
• Think them through! Write them down!
• Make sure that everyone involved at your end is
  aware of the upcoming change!!
• (Tech Contact and Admin Contact)

9
The Template

• Text version currently available from IANA
  website
• http//www.iana.org/tld/cctld-template.txt
• Will automatically generate templates in the
  future

10
Fill out the relevant parts

• Fill in each section but if no change,
• write No Change
• Will save every ones time ?

11
(1) Description and (2) TLD

• 1. Purpose/Description............. Free text
  describing the change
• Renumbering Server, Changing contact data,
  Adding servers, Deleting Server
• 2. Top-Level Domain Name........... Country Code
• zw, ke, ls, etc.

12
(3) Sponsoring Organisation

• 3a. Organization Name (Registrant).. No
  Change
• 3b. Street Address..................
• 3c. City............................
• 3d. State...........................
• 3e. Postal Code.....................
• 3f. Country Code (2 letter).........

13
(4) Administrative Contact

• 4a. (omitted)
• 4b. (I)ndividual or (R)ole?......... No Change
• 4c. Name............................
• 4d. Organization Name...............
• 4e. Street Address..................
• 4f. City............................
• 4g. State...........................
• 4h. Postal Code.....................
• 4i. Country Code (2 letter).........
• 4j. Phone Number....................
• 4k. Fax Number......................
• 4l. Email Address...................

14
(5) Technical Contact

• 5a. (omitted)
• 5b. (I)ndividual or (R)ole?.........
• 5c. Name............................
• 5d. Organization Name...............
• 5e. Street Address..................
• 5f. City............................
• 5g. State...........................
• 5h. Postal Code.....................
• 5i. Country Code (2 letter).........
• 5j. Phone Number....................
• 5k. Fax Number......................
• 5l. Email Address...................

15
(6) Primary Name Server

• 6a. Primary Server Hostname.........
• 6b. Primary Server Netaddress.......
• a is the name such as ns.primary.nl
• b is the IP address such as 193.0.0.193

16
(7) Secondary Name Server (repeat as needed)

• 7a. Secondary Server Hostname.......
• 7b. Secondary Server Netaddress.....
• 7a. Secondary Server Hostname.......
• 7b. Secondary Server Netaddress.....

17
(8) Registration and (9)Whois

• 8. URL for Registration Services...
• http//www.nic.nl
• 9. Whois Server....................
• whois.nic.nl

18
Confirmation

• IANA staff will ask for confirmation from both
  the administrative contact and the technical
  contact.
• Make sure they both know the changes are
  happening!!
• Changes dont take place without their
  confirmation.

19
Technical checks

• IANA staff will check that the servers are there
  and responding correctly.
• If there are technical issues, IANA staff will
  work with you to resolve them.

20
Current policy issues

• Policies will and do change
• http//www.iana.org/procedures/comments.html
• (Refer to document)

21
Assuming all is ok

• IANA will forward the changes to the NTIA of the
  USDoC who check only that process was followed.
• The changes get forwarded to VeriSign who update
  the zone.

22
Policy and ICANN

• ccNSO http//ccnso.icann.org/
• The ccNSO is the policy development body for a
  narrow range of global ccTLD issues within the
  ICANN structure
• Joining?
• http//ccnso.icann.org/applications/clean-app.shtm
  l

23
Usefull links

• IANA main page
• http//www.iana.org
• CcTLD whois data
• http//www.iana.org/cctld/cctld-whois.htm
• ICP1 (IANA practices)
• http//www.icann.org/icp/icp-1.htm
• Format, Content, and Technical Requirements for
  Requests to Change TLD Contact Information
• http//www.iana.org/cctld/contact-change-requests-
  09may01.htm

24
Useful links

• Template for changes
• http//www.iana.org/tld/cctld-template.txt
• Step by step procedure
• http//www.iana.org/cctld/nameserver-change-proced
  ures-13may03.htm
• ICANN main page
• http//www.icann.org
• ccNSO
• http//ccnso.cann.org