ipv6 and.hk ben lee hkirc 01 march 2010. 2 agenda 1. why ipv6 for.hk 2. roadmap of ipv6 deployment...

15
IPv6 and .HK Ben Lee HKIRC 01 March 2010

Upload: branden-patten

Post on 01-Apr-2015

221 views

Category:

Documents


3 download

TRANSCRIPT

Page 1: IPv6 and.HK Ben Lee HKIRC 01 March 2010. 2 Agenda 1. Why IPv6 for.hk 2. Roadmap of IPv6 deployment 3. Current status 4. Considerations 5. Further work

IPv6 and .HK

Ben LeeHKIRC

01 March 2010

Page 2: IPv6 and.HK Ben Lee HKIRC 01 March 2010. 2 Agenda 1. Why IPv6 for.hk 2. Roadmap of IPv6 deployment 3. Current status 4. Considerations 5. Further work

2

Agenda

1. Why IPv6 for .hk2. Roadmap of IPv6 deployment 3. Current status4. Considerations5. Further work

Page 3: IPv6 and.HK Ben Lee HKIRC 01 March 2010. 2 Agenda 1. Why IPv6 for.hk 2. Roadmap of IPv6 deployment 3. Current status 4. Considerations 5. Further work

Why IPv6 for .hk?

DNS is one of the most important applications of the Internet

IPv6-readiness of .hk is a pre-requisite of Hong Kong Internet IPv6 deployment

ccTLDs should avoid becoming the critical path to IPv6 deployment in the region

Be one of the first example to use IPv6 and raise awareness with the community

Promote the use of IPv6

3

Page 4: IPv6 and.HK Ben Lee HKIRC 01 March 2010. 2 Agenda 1. Why IPv6 for.hk 2. Roadmap of IPv6 deployment 3. Current status 4. Considerations 5. Further work

.hk Roadmap of IPv6 deployment

1. DNS resolution - Post the AAAA records and incrementally add IPv6 connectivity to some (not necessary all) DNS and

2. DN Registration - update registration applications to accept IPv6 glue addresses from registrants

3. Infrastructure – Set up a site with IPv6 transit

4. Registry tools – provide website, WHOIS, EPP/API over IPv6 transit

4

Page 5: IPv6 and.HK Ben Lee HKIRC 01 March 2010. 2 Agenda 1. Why IPv6 for.hk 2. Roadmap of IPv6 deployment 3. Current status 4. Considerations 5. Further work

.hk DNS with IPv6 connectivity

>dig @a.root-servers.net. any hk.

… snip …

;; ADDITIONAL SECTION:

b.dns.tw. 172800 IN A 210.201.138.58

b.dns.tw. 172800 IN AAAA 2404:0:10a0::58

ns1.hkirc.net.hk. 172800 IN A 203.119.2.18

ns2.cuhk.edu.hk. 172800 IN A 137.189.6.21

ns2.cuhk.edu.hk. 172800 IN AAAA 2405:3000:3:60::21

ns2.hkirc.net.hk. 172800 IN A 203.119.2.19

ns3.cuhk.edu.hk. 172800 IN A 202.45.188.39

sec3.apnic.net. 172800 IN A 202.12.28.140

sec3.apnic.net. 172800 IN AAAA 2001:dc0:1:0:4777::140

adns1.berkeley.edu. 172800 IN A 128.32.136.3

adns2.berkeley.edu. 172800 IN A 128.32.136.14

hk-ns.pch.net. 172800 IN A 204.61.216.46

;; Query time: 28 msec

;; SERVER: 198.41.0.4#53(a.root-servers.net.)

;; WHEN: Tue Feb 23 16:02:29 2010

;; MSG SIZE rcvd: 465

5

Page 6: IPv6 and.HK Ben Lee HKIRC 01 March 2010. 2 Agenda 1. Why IPv6 for.hk 2. Roadmap of IPv6 deployment 3. Current status 4. Considerations 5. Further work

IPv6 capable DNS software

BIND Resolver & Server BIND 9 - http://www.isc.org/products/BIND/

NSD Authoritative server only http://www.nlnetlabs.nl/nsd/

Microsoft Windows Resolver & Server Windows Server 2008 R2, 2008, 2003 Windows 7, Vista, XP SP2

6

Page 7: IPv6 and.HK Ben Lee HKIRC 01 March 2010. 2 Agenda 1. Why IPv6 for.hk 2. Roadmap of IPv6 deployment 3. Current status 4. Considerations 5. Further work

.hk now accepts IPv6 glue records

Add or Modify DN Host (Panel: Registrant, Reseller, Registry, Registrar and API )

7

Page 8: IPv6 and.HK Ben Lee HKIRC 01 March 2010. 2 Agenda 1. Why IPv6 for.hk 2. Roadmap of IPv6 deployment 3. Current status 4. Considerations 5. Further work

.hk now accepts IPv6 glue records

Allow input of IPv4 or IPv6 addresses

8

IPv4

IPv6

Page 9: IPv6 and.HK Ben Lee HKIRC 01 March 2010. 2 Agenda 1. Why IPv6 for.hk 2. Roadmap of IPv6 deployment 3. Current status 4. Considerations 5. Further work

Considerations - DNS IPv6 Operational Guidelines

Defined in RFC3901

All recursive name servers should be IPv4 only or dual stack hosts

All zones should be served by at least one authoritative IPv4 capable host

9

Page 10: IPv6 and.HK Ben Lee HKIRC 01 March 2010. 2 Agenda 1. Why IPv6 for.hk 2. Roadmap of IPv6 deployment 3. Current status 4. Considerations 5. Further work

Considerations – DNS packet size

Size of response packet becomes larger UDP packet size 512 bytes not all support EDNS0 the additional section of the response may be

truncated Some clients may fallback to TCP, hence network

and server loading may increase

10

Page 11: IPv6 and.HK Ben Lee HKIRC 01 March 2010. 2 Agenda 1. Why IPv6 for.hk 2. Roadmap of IPv6 deployment 3. Current status 4. Considerations 5. Further work

Considerations – DNS packet size

Minimize the number of name servers use anycast technology, one host name actually

supported by multiple servers (technical setup with a cost)

Utilize the name compression of name servers rename existing servers to shorter similar names e.g. a.nic.hk, b.nic.hk, c.nic.hk, …

11

Page 12: IPv6 and.HK Ben Lee HKIRC 01 March 2010. 2 Agenda 1. Why IPv6 for.hk 2. Roadmap of IPv6 deployment 3. Current status 4. Considerations 5. Further work

Future works

Add more .hk DNS with IPv6 Implement IPv6 in secondary site to support

additional Internet services (Websites, WHOIS, API, EPP, Email)

Implement IPv6 in office to test IPv6 Internet services

Implement IPv6 in primary site Measure the usage of IPv6 in .hk

12

Page 13: IPv6 and.HK Ben Lee HKIRC 01 March 2010. 2 Agenda 1. Why IPv6 for.hk 2. Roadmap of IPv6 deployment 3. Current status 4. Considerations 5. Further work

13

Page 14: IPv6 and.HK Ben Lee HKIRC 01 March 2010. 2 Agenda 1. Why IPv6 for.hk 2. Roadmap of IPv6 deployment 3. Current status 4. Considerations 5. Further work

14

Page 15: IPv6 and.HK Ben Lee HKIRC 01 March 2010. 2 Agenda 1. Why IPv6 for.hk 2. Roadmap of IPv6 deployment 3. Current status 4. Considerations 5. Further work

15

Disclaimer

This document carries no legal authority. The arrangement mentioned in this document is subject to change at any time by HKDNR and shall not be deemed to be the final arrangement. Hong Kong Domain Name Registration Company Limited shall not be held responsible for any consequences caused by any omissions, inaccuracies or future changes of the arrangement.