1 / 32

Interoperability: Key link to deployment

Interoperability: Key link to deployment. Gopi Garge IPv6 Forum India and IISC-ERNET, India gopi@ece.iisc.ernet.in. Deployment. Needs customer demand Does customer really know/care about IPv6? Must be clear benefits Must be simple to use Must offer significant advantages

elana
Download Presentation

Interoperability: Key link to deployment

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Interoperability: Key link to deployment Gopi Garge IPv6 Forum India and IISC-ERNET, India gopi@ece.iisc.ernet.in

  2. Deployment • Needs customer demand • Does customer really know/care about IPv6? • Must be clear benefits • Must be simple to use • Must offer significant advantages • Vendors are developing IPv6 solutions • Host, router and mobile devices

  3. IPv6 Deployment Strategies • Plan A: Driven by new applications • 3GPP/UMTS - mobile IPv6 handsets • Home networking - plug and play devices • Metering - utility services • Plan B: Transition of existing Internet • IPv4 and IPv6 must co-exist • access IPv4 applications from IPv6 networks • and vice-versa

  4. Translating Gateway IPv6 Enterprise IPv4 Enterprise IPv6 Enterprise Service Provider MPLS Backbone CE Router IPv6 Enterprise IPv6 over MPLS

  5. IP Mobility and Access • IPv6 enables a mobile information society • end-to-end security/transparency with QoS • Key benefit is global reachability • scalable mobile IP methods • Run over multiple media • WaveLAN, IR, Bluetooth, Ethernet, 3G

  6. WAP & Mobile • WAP geared for mobile PDA devices • IPv6 enables unique global IP addressing • thus all devices/handsets addressable with IP • 3GPP partners building All-IP core networks • e.g. Nokia • UMTS handsets may run IPv6 • e.g. Ericsson multimedia handsets

  7. Standards bodies • Internet Engineering Task Force • Defining Internet (including IP) standards • Led by implementations, very open • ITU, ETSI (and 3GPP) • Defining 3G mobile • Driven more “by committee” • Both work, but need to work together for 3G

  8. IPv6 Standards Status • Core IETF specifications already completed • Many (inter)national deployments exist • Vendors are delivering commercial support • ISPs are rolling out commercial services • 3GPP has adopted IPv6 • Real IPv6 address space is being assigned

  9. IPv6 Platforms • Solaris 8: with IPv6 since March 2000 • Windows 2000: preview released Oct 2000 • FreeBSD: IPv6 as standard in FreeBSD4.1 • Linux: IPv6 packages available • Compaq: Tru64 Unix v5.1 includes IPv6 • IBM: AIX 4.3 • HP: HP/UX 11.0

  10. Building IPv6 applications • New applications • Enabled by global reachability • Following peer-to-peer model • Might possibly be “standalone” • Porting existing applications • Use new IPv6 APIs • Already quite well-defined • New API extensions under development

  11. New IPv6 apps? • Need (real-time) end-to-end services • Access to databases and directory services • Tailored, seamless services, per user • Location-based user interface • Migrating agent services • Access to home network equipment • High performance visualisation experiments • Telephony, video streaming • Available anywhere, anytime

  12. IPv6 APIs • Need APIs to develop applications! • Solaris, Linux, KAME • use C • Sun’s “socket scrubber” is a handy tool • http://www.sun.com/solaris/ipv6/ • Many Web/Internet applications use Java • awaiting IPv6-enabled Java from Sun

  13. The Quake API test • Took 32 hours for 2 programmers from Viagenie (Canada) to retrieve the source, find where to make changes, code the changes, setup a public Quake server and play the first Quake game over IPv6. • http://www.viagenie.qc.ca/en/ipv6/quake/ipv6-quake.shtml

  14. IPv6 Routers • Cisco IOS: commercial version January 2001 • Telebit: first commercial router, TBC2000 • FreeBSD 3.5 or 4.1 (KAME stack) • Zebra (GNU router project) • 3Com Netbuilder II • Hitachi NR60, GR2000 • Bay Networks

  15. Core applications • DNS • BIND 9 offers native IPv6 DNS lookups • Viagenie preparing IPv6 root name server • World Wide Web • Apache server • MSIE, Netscape, Mozilla and Lynx browsers. • E-mail • Sendmail 8.10 has IPv6 built-in, as does qmail.

  16. IPv6 Deployments • Commercial ISPs • IIJ, NTT, BT • International deployments • 6bone, WIDE (Japan), Internet 2 (US/Canada) • European academic networks • JANET, DFN, Surfnet, ACONet, Renater • European projects • 6INIT, GTPv6

  17. 6bone stats (Summer 2000) • Now in 46 countries AR, AU, AT, BE, BR, BG, CM, CA, CN, CZ, DK, EE, FI, FR, DE, GR, HK, HU, IN, IE, IT, JP, KZ, KR, LT, MY, MX, NL, NZ, NO, PL, PT, RO, RU, SG, SK, SI, ZA, ES, SE, CH, TW, UA, UK, US, UY • 571 networks/sites 135 US, 66 DE, 38 JP, 28 FR, 28 UK, 20 SE, 10 CN, 9 RU, 4 MX etc. • 68 pTLA’s (backbone tier ISPs)recent additions: UUNET and Deutsche Telekom

  18. 12 partner EU project (Jan’00 - Apr’01) • Pan-European deployment, 5 regional clusters • www.6init.org • Applications: • stock exchange, news-on-demand, streaming • IPv4/IPv6 integration issues • Also deploying: • QoS (DiffServ), IPsec (FreeSWAN), VoIPv6 (SIP) • 6WINIT wireless follow-up project

  19. 6INIT clusters UK Scandinavia BT, UoS, NTT, Telscom NAT PT Telia, Telebit, Netmedia, erFP NAT PT BT IPv6 Exchange Tunnels Internet Native IPv6 Canada Germany France NAT PT Thomson, Renata II T-Nova, IABG NTT, CRC NAT PT Greece Intracom

  20. Transition from IPv4 to IPv6 • IPv4/IPv6 interworking • IPv6-in-IPv4 tunnels • Automated tunnel brokers, e.g. www.freenet6.net • NAT/PT and Ultima (BT) • Dual stack IPv4 and IPv6 • easier if you have enough IPv4 addresses • Proxy methods • DSTM, 6to4, 6over4, ... • Different scenarios require different tools

  21. IPv6 in IPv4 tunnels • Encapsulates IPv6 in IPv4 • Thus uses IPv4 routing/properties • Loses special IPv6 features in doing so • But can run over existing Internet • Much of the 6bone is tunnelled not native IPv6 • Similar concept to the Mbone tunnelling of multicast • Requires a hole in firewall • To allow through Protocol 41 (IP in IP) • (IPv6 firewalls are scarce right now)

  22. Tunnel brokers • If a manually configured tunnel is not possible • Perhaps admin at site won’t configure on router • Can dynamically gain tunnel to a “tunnel server” • Server responds to Web request with commands to run on the local host (or a script) • Has problem of authentication of broker user • If using dialup, your IPv4 address probably changes with each session • Best example is www.freenet6.net (Viagenie) • Has scaling issues

  23. NAT-PT • Is similar in style to NAT • But translates protocol IPv4-IPv6 as well • Allows island of IPv6-only devices to communicate to an IPv4 external network • Developed by BT (George Tsirtsis et al) • Has scaling issues, and DNS issues • Ultima allows two IPv6-only islands to communicate over an IPv4 netwok

  24. Dual stack • Probably the easiest • Will require IPv6 routes to/from network • All devices run IPv4 and IPv6 stacks • Assumes enough IPv4 addresses • Thus suitable at a University, but probably not a small business • Needs care over security issues • Commonplace “solution”

  25. Proxy methods • Abstracts integration to application layer • e.g. a Web cache • Runs both IPv4 and IPv6 • Can relay requests between protocols as required • Seen as acceptable given current usage • Can also do e-mail and other services • But only a medium term answer

  26. 6to4 • Allows IPv6 network to exist behind a single IPv4 address • Uses special 2002::/16 prefix • Next 32 bits are the IPv4 address • Requires router knowledge of 6to4 prefixes • 6to4 router can establish IPv4 endpoint of required tunnel from “IPv4” part of the address • e.g. an IPv6 network “hidden” behind 84.78.64.32 would be 2002:544e:4020::/48

  27. Best method? • No ideal solution in all cases • Single user may like tunnel broker • University may run dual stack with native IPv6 route from disjoint IPv6 exit router • Small business might prefer 6to4 • Full analysis of these and other methods is required…

  28. Southampton IPv6

  29. IPv6 deployment barriers • Cost is most significant factor • but not so much for new applications • Need confidence in technology • pilots: WIDE, vBNS, NTT, 6INIT • Need clear benefits • manageability • scalability • IPv4 “does the job” • but will it in 5 years, and then what cost? ?

  30. Conclusions • Commerical IPv6 products are here • Widespread deployment is not • Business case can be made • Depending on the application domain • Needs major network carrier to deploy • May be led by Cisco commercial support • May be easier to deploy new IPv6 apps? • Integration would then follow by demand

  31. If you’re new to IPv6... • Read IPv6 Forum articles • Deploy IPv6 software • FreeBSD 3.5.1 with KAME stack (www.kame.net) • excellent for host/router/API trials • Get connected to the 6bone • apply for pTLA or use www.freenet6.net • Track standards bodies • ipng and ngtrans IETF working groups/e-mail lists

  32. Sites to visit • IPv6 Forum - http://www.ipv6forum.com • conference presentations and reports • implementation and deployment lists • IETF - http://www.ietf.org • standards and draft standards • ipng and ngtrans working groups • My e-mail: tjc@ecs.soton.ac.uk

More Related