6INIT Overview

1
6INIT Overview

• Tim Chown
• tjc_at_ecs.soton.ac.uk

2
Project scope

• EU 5th Framework
• 11 partners, plus two international
• 16 months in first instance
• Currently in architecture definition stage
• Focus on deployment issues
• Project scaled down from 36 months

3
Partners

• Telecomms
• BT, T-Nova, Telia
• Router suppliers
• Ericsson-Telebit, Thomson-CSF Detexis
• Research
• IABG, Soton
• Providers
• Intracom, Telscom, Netmedia, NFP
• International partners NTT, Viagenie

4
Network topology

• Cluster definition
• UK, Germany, France and Scandinavia
• One exchange per cluster
• BT hosting a UK exchange
• Issues
• Connectivity between clusters
• Connectivity to 6bone and beyond
• IPv4 interoperability methods

5
Services

• QoS
• Thomson edge device with DiffServ
• IPsec
• IABG port of FreeS/WAN
• Transition methods
• BT Ultima and NAT/PT, tunnel broker
• Telebit NAT/PT implementation
• Also 6to4

6
Services

• VoIP
• Telscom/Telia/Telebit/BT
• SIP client, with IPv4/v6 interworking (ALG)
• Ideally a Java/V6 client
• Security
• Thomson VPNs, secure dial-up
• Soton IPv6 firewalls
• Management and Accounting
• T-Nova monitoring, autoconf, renumbering

7
Standard boring stuff

• Web services
• Apache, virtual domain hosting
• e.g. http//www.6init.org, http//www.ipv6.org.uk
• E-mail
• Sendmail 8.10
• DNS
• BIND 9, A6 records, etc.
• FTP
• ncftp

8
Applications

• Publishing
• Netmedia
• Stock exchange
• NFP
• Multimedia
• Intracom, Soton
• Java-based?
• Audio and video streaming tools

9
6INIT-QTPv6 common interests

• Deployment Issues
• Interoperability
• DNS
• Applications
• Management/monitoring
• IPv6 DiffServ
• But not (currently)
• Multihoming

10
Soton Network

• April 2000

11
Current hosts

• Solaris 8 release, Sparc and Intel
• FreeBSD3.4 and 4.0
• Windows NT4 and 2000
• Linux Redhat 6.1
• DEC Tru64 v5.0

12
Current routers

• Cisco 2501 and 4500
• Telebit TBC2000
• FreeBSD4.0, Zebra router daemon
• 3Com Netbuilder II

13
Connectivity

• QTPv6
• 3ffe803c/34, 512kbit PVC
• Bermuda (UCL, Soton, Lancs)
• 200106301fff/48, 2Mbit PVC
• Enables 2Mbit link through to BT
• UUNET (since 1997)
• 3ffe1108800/40, 64kbit X21
• Tunnels

14
Interests

• Deployment
• e.g. teaching labs
• the boring stuff
• subnetworking via Zebra boxes
• Interoperability
• Research
• 6INIT, Hystream, pervasive computing
• Multihoming

15
Multihoming Issues

• April 2000

16
Why multihome?

• Resilience
• Load sharing
• Get best value for a service
• These problems exist in IPv4
• Is it appropriate at academic sites?
• We must keep aggregation principles

17
Multihoming variants

• A host with multiple addresses
• A host with multiple interfaces
• A cluster inheriting multiple prefixes
• e.g. under 3ffe803c and 20010630
• A site with multiple external links
• Need to define scenarios for QTPv6

18
Things can change in IPv6

• Prefix may be changed live
• router renumbering
• Additional prefix may be inherited
• add a new interface, e.g. via a tunnel
• Host may be mobile
• May lose an interface
• e.g. unplug Ethernet to roam on 802.11
• what about active TCP sessions?
• Ultimate desire to plug and play

19
Multiple prefix issues

• Routing is a routers job
• how does host know what to use?
• How to pick the best route
• what happens when one link fails?
• want to receive traffic addressed to an interface
  that is down
• should traffic with given source prefix leave via
  that prefixs interface?

20
Src/Dst Address selection

• Draves Internet Draft
• Have multiple addresses/interfaces
• on sender and receiver
• Need to choose
• source address
• destination address
• Consider
• address scope and longest match prefix

21
Some solutions

• Address selection
• longest prefix matching
• use scope and deprecation status
• try multiple paths at session start-up
• use of an admin precedence policy
• Multiple ISPs and prefixes
• mutual peering
• peering with a primary ISP only (Yu)

22
Some more solutions

• Continuity of existing connection
• use of mobile IP methods
• use of router renumbering protocol
• Other possibly useful features
• use of globally unique EUI-64 part
• But that wont necessarily be unique
• proposal to use site-local addressing
• But intuitively feels rather NAT-like

23
Some scenarios

• Multihoming for resilience
• but has load-sharing issues
• is the resilient link used?
• Ability to choose ISP services
• per site
• per application
• per connection (e.g. VoIP call)

24
Multihoming for QTPv6

• Define scenarios
• two-prefix site, 6bone and SubTLA
• Choose methods to trial
• mutual peering
• primary ISP peering (Yu)
• mobile IP for resilience (Dupont)
• What is required for deliverable?
• presumably overview experiences?