The JANET IPv6 Experimental Service

1
The JANET IPv6 Experimental Service

• Rob Evans
• JANET NOSC
• University of London Computer Centre

2
Agenda

• Don't worry about taking notes, slides are on the
  web, URL is at the end.
• Introduction
• History of IPv6 on JANET
• Current IPv6 Service
• Network
• DNS
• Support

3
Agenda (cont'd)

• How do I join in the fun?
• What should I be planning for?
• References.
• Questions.

4
Introduction

• JANET NOSC _at_ ULCC.
• Responsible for day-to-day operations of JANET
  backbone.
• Track developmental technologies to assess impact
  on production network.

5
What is the IPv6 Experimental Service?

• A way for UKERNA, the JANET NOSC, and JANET
  customers to start to deploy IPv6.
• Gain familiarity and experience before it becomes
  a necessity.
• Connected to other networks around the world with
  the same purpose.

6
History of IPv6 on JANET

• Initially joined the 6BONE in 1997.
• Address space 3FFE2100/24
• Test images of IOS on borrowed router.
• Native connection to Pipex's IPv6 tests.
• Unofficial service for a long time, run by the
  NOSC as we were interested and wanted to gain
  experience.

7
Current IPv6 Service

• Based around three dedicated routers, two at ULCC
  and one at Telehouse.
• Two of the routers are Cisco 7505s (IOS 12.2T),
  and the third is a Cisco 12404 (IOS 12.0S)
• 12404 contributed by Cisco as part of the 6NET
  project (see talk later on by Tim Chown on EC
  funded projects).
• Router at Telehouse connects to IPv6 internet
  exchange points UK6X and LINX.

8
Current IPv6 Service (cont'd)

• Routers at ULCC connect to 6NET, 6BONE, UCL,
  network for IPv6 systems, handle tunnel
  terminations, and connect to JANET backbone.
• Native connections
• ULCC to Telehouse
• 6NET, LINX and UK6X
• UCL
• Ethernets for IPv6 systems at ULCC.

9
Current IPv6 Service (cont'd)

• All other connections currently tunnelled (but
  see futures talk this afternoon).
• Currently 17 JANET sites connected to the pilot
  service.
• Although not all are active, and some are using
  old addresses.
• Routing to sites is either static, RIPng or
  BGP4.
• Following IPv4 routing, static or BGP4 is
  preferred.

10
IPv6 Network Diagram
11
Addressing

• Original addresses and delegations were from
  6BONE prefix 3FFE2100/24.
• Once IPv6 started to settle, allocation heirarchy
  changed to follow IPv4
• IANA allocates large chunks to Regional Internet
  Registries (in our case, RIPE).
• RIPE allocates addresses to the Local Internet
  Registries (UKERNA/JANET).
• LIR allocates to customers.

12
Addressing (cont'd)

• JANET assigned 2001630/35 by RIPE.
• Expanded in line with new addressing
  recommendations to 2001630/32.
• When you join the experimental service, you will
  be assigned an address range from 2001630/32.
• 6BONE will die, sites using allocations from old
  6BONE prefix (3FFE2100/24) must renumber.

13
Addressing (cont'd)

• Every JANET customer gets a /48 when they ask.
• Current recommendations are that ALL subnets are
  /64 (even point-to-point links).
• 65,536 subnets per site.
• If you need more than one /48, you need to submit
  an addressing plan.
• Just like IPv4.
• But it will use much more paper.

14
DNS

• Forward lookups are easy.
• Just use 'AAAA' record instead of 'A'.
• Reverse delegations within ip6.int and ip6.arpa
• ip6.int is historic and will be phased out.
• Delegations can look a bit ugly. If you have
  been allocated 20016301234/48, reverse zones
  are
• 4.3.2.1.0.3.6.0.1.0.0.2.ip6.int
• 4.3.2.1.0.3.6.0.1.0.0.2.ip6.arpa

15
DNS (cont'd)

• Your DNS server does not need to talk IPv6 in
  order to answer lookups of IPv6 addresses.
• JANET NOSC can offer secondary server available
  over IPv6 transport.
• sixpack.ipv6.ja.net.
• ns0.ja.net will be available over IPv6 transport
  in very near future (days).

16
Webserver

• http//www.ipv6.ja.net/
• Accessible over IPv4 and native IPv6 (currently
  resides on same systems as IPv6 DNS server).
• Not much content at the moment
• Slides from talks given at last year's
  Networkshop, SERJUG earlier in year and this.
• View of the routing table on one of the routers.
• Designed by an engineer.

17
What do you need to join the fun?

• Something to terminate the tunnel on.
• Could be a Cisco, could be a Linux box, could be
  a FreeBSD/NetBSD/OpenBSD box.
• Make sure your firewall will allow IPv6-in-IPv4
  packets through from pilot service router.
• You might want filters on your IPv6 connection in
  the same way that you filter your IPv4 connection
  to limit crackers and script kiddies.
• It will probably have to be a tunnel for now.

18
What do you need to join? (cont'd)

• Some time to tinker.
• Some PCs or UNIX boxes with IPv6 support in the
  operating system.
• See next talk by Tim and Duncan.
• Submit an application form available from
• http//www.ja.net/development/ipv6/experimental_se
  rvice.html

19
What should I be planning for?

• DON'T PANIC!
• IPv4 is not about to die.
• IPv6 is not about to become ubiquitous.
• Experimental service is exactly that a chance
  to experiment.

20
What should I be planning? (cont'd)

• Have a look at some of the 6NET deliverables.
• http//www.6net.org/publications/
• D2.3.1, published last year, covers some of the
  mechanisms for site networks.
• D2.3.2, which should be submitted to the EC next
  week, first draft of a transition cookbook for
  end-sites and universities.
• Loads of configuration examples!

21
What should I be planning? (cont'd)

• Think about enabling some of your networks with
  IPv6 to gain familiarity and experience.
• Think about making some servers available over
  IPv6.
• DNS Supported in BIND 9.
• WWW Supported in Apache 2.
• Sendmail/Exim/Postfix.

22
Support

• Community support via JISCmail list
• ipv6-users_at_jiscmail.ac.uk
• JANET NOSC support is best-efforts.
• Problems on the production network come first!
• Reasonable knowledge of configuring IPv6 on Cisco
  IOS.
• Some knowledge of using NetBSD and Solaris on
  end-systems (but not as routers).
• Little (OK, no) knowledge of Linux.

23
Applications

• Despite the spiel on servers a couple of slides
  back, I just shift packets...
• Tim will mention this later in his talk on
  end-systems.

24
References

• Size of subnets
• draft-ietf-ipngwg-addr-arch-v3-11.txt
• draft-ietf-ipv6-unicast-aggr-v2-01.txt
• Will replace RFCs 2373 and 2374.
• ip6.int phaseout
• RFC3152

25
References

• UKERNA IPv6 pages
• http//www.ja.net/development/ipv6/index.html
• http//www.ipv6.ac.uk/
• JISCmail ipv6-users list
• http//www.jiscmail.ac.uk/archives/ipv6-users.html

26
Questions?

• Slides available at
• http//www.ipv6.ja.net/0302-conf/