IPv6 Overview and Status

1
IPv6Overview and Status

• Robert M. Hinden

NOKIA
2
TALK OVERVIEW

• IPng Overview
• Proposed TLA/NLA Assignment Rules
• Current Status
• Deployment Timetable

3
IP NEXT GENERATION

• New Version of the Internet Protocol
• Assigned Version 6 (IPv6)
• Expands Scope of Routing and Addressing to Meet
  Internet Growth
• Solves Next Set of Pressing Problems
• Good Example of Internet Technology Evolution

4
CHANGES FROM IPv4

• Larger 128-bit Hierarchical Addresses
• Supports Much Larger Internet
• Allows Embedded IEEE 802 MAC Address for
  Auto-Configuration
• Simplified Header w/ 64bit Alignment
• Flow Label for Real Time Support
• Flexible Extension Header Mechanism
• Security
• Route Selection

5
NEW FEATURES

• Plug and Play Auto Configuration
• Authentication and Privacy Extensions
• Flexible Scaleable Routing Architecture
• Multicast Improved and Made Standard
• Incremental Deployment

6
IPv6 HEADER FORMAT
Version
Flow Label
Class
Payload Length
Next Header
Hop Limit
Source Address
40 bytes
Destination Address
32 bits
7
IPv4 HEADER FORMAT
Length
Vers
TOS
HdrL
Identification
Frag. Offset
Flags
20 bytes
Header Checksum
Protocol
TTL
Source Address
Destination Address
Options
Padding
32 bits
8
EXTENSION HEADERS
9
IPv6 ADDRESSING

• 128 Bit Addresses can Identify Large Number of
  End Points 340,282,366,920,938,463,463,374,60
  7,431,768,211,456
• 15 Initially Assigned, 85 Reserved for Future
  Growth

10
IPv6 ADDRESS TYPES

• Unicast (one-to-one)
• Global
• Link-Local
• Site-Local
• Compatible (IPv4, IPX, NSAP)
• Multicast (one-to-many)
• Anycast (one-to-nearest)

11
ADDRESS FORMATS

• Aggregatable Unicast
• Link Local Unicast
• Site Local Unicast
• Multicast

SLA ID
NLA ID
Interface ID
TLA ID
001
R
Interface ID
111111010
0000.............0000
Subnet ID
Interface ID
111111011
000...000
Group ID
Flags
Scope
11111111
12
AGGREGATABLE UNICAST ADDRESSES

• Unicast Address Format for IPv6
• Supports Provider and Exchange Models
• Great Improvement in ISP Routing Scaling
• Limits Size of Top Level Routing
• Exchanges Support Site
• Multihoming to Long Haul Providers
• Changing Long Haul Providers w/out Renumbering

13
FORMAT
3 13 8 24 16
64
FP TLA R NLA SLA
INTERFACE ID
Public Topology
Site Topology
Interface Identifier
14
FIELDS

• FP Format Prefix (010)
• TLA ID Top Level Aggregation ID
• RES Reserved for Future Use
• NLA ID Next Level Aggregation ID
• SLA ID Site Level Aggregation ID
• INTERFACE ID Interface Identifier

15
TOP LEVEL AGGREGATION ID

• Top Level in Addressing Hierarchy
• Assigned to Organizations providing Transit
  Topology
• Not for Leaf Topology
• Supports 213 TLA IDs (8K)
• Expansion possible using Reserved field
• IANA Assigns Blocks to Registries
• Registries assign TLA IDs to organizations
• Registries get more from IANA

16
NEXT LEVEL AGGREGATION ID

• Used by TLA ID holders to
• Create TLA Hierarchy
• Identify Sites
• TLA ID holders may support NLAs in their own
  Site ID space
• NLA holders may support NLAs in their..
• Works exactly like CIDR delegation
• TLA holders assume registry duties for NLAs

17
NLA IDS
NLA1 SITE ID SLA ID
INTERFACE ID
NLA2 SITE ID SLA ID
INTERFACE ID
NLA3SITE SLA ID INTERFACE ID
18
INTERFACE IDS

• Identify Interfaces on a Link
• Required to be Unique on Link
• May be Unique over a broader scope
• Constructed in IEEE EUI-64 format
• Usually from Hardware Token
• Ethernet MAC, etc.
• May be created from limited scope token
• Local Talk, tunnels, etc.
• Future work may use Interface ID as an Node
  Identifier

19
IPv6 ROUTING

• Longest-Prefix Match Routing
• Same as IPv4 CIDR Routing
• Extensions to Existing IPv4 Routing Protocols
• Unicast RIPv2, OSPF, ISIS, BGP4, ...
• Multicast PIM, MOSPF, , ...
• Support for Policy Routing by use of Routing
  Header with Anycast Addresses
• Provider Selection, Policy Routing, etc.

20
IPv6 SECURITY

• All implementations expected to support
  authentication and encryption headers
• Authentication separate from encryption for use
  in situations where encryption is prohibited or
  prohibitively expensive
• Support for manual key configuration required
• Key distribution protocols are under development
• Independent of IPv4 / IPv6

21
PLUG-AND-PLAY AUTOCONFIGURATION

• Hosts automatically learn subnet prefix from
  router advertisements
• Fabricate own address by adding local unique ID
  (e.g., Ethernet address)
• New subnet prefixes can be added, and old ones
  deleted, to cause automatic renumbering
• Automatic address fabrication can be overridden
  by DHCP service, for more local control
• Work underway on dynamic DNS updating and
  automatic service location (anycast/multicast)

22
REAL TIME

• Flows
• Sequence of Packets that desire Real-Time service
• Flow Label used to identify Flow
• Traffic Classes
• Interactive (prefer Low Latency over Throughput
• Explicit Congestion Notification
• Priority

23
IPv6 TRANSITION

• Philosophy
• Make IPv6 Implementations Compatible with IPv4
• Make it Easy to Deploy
• Get Experience Early in Transition
• Goals
• Allow Incremental Upgrade of Hosts and Routers to
  IPv6
• Few or No Upgrade Dependencies
• Complete Transition before IPv4 Addresses Run Out

24
GENERAL TRANSITION MODEL
Phase 1 Phase 2
time
IPv4 Only IPv4 IPv6
IPv6
25
TRANSITION TECHNIQUES

• Dual IP Layer
• Nodes Support IPv4 and IPv6
• IPv4 Compatibility Addresses
• IPv4 Address Embedded within IPv6 Address
• IPv6 in IPv4 Encapsulation
• Tunnel IPv6 Datagrams across IPv4 Infrastructure
• Translation

26
CURRENT IPv4 OPERATION
IPv4 Router
IPv4 Router
IPv4 Host
IPv4 Host
27
INTEROPERATION WITH IPv4
IPv4 Router
IPv4 Router
IPv6/IPv4 Host
IPv4 Host
28
TUNNELING OVER IPv4
IPv4 Router
IPv4 Router
IPv6/IPv4 Host
IPv6/IPv4 Host
29
IPv6 AND TUNNELING
IPv4 Router
IPv4/IPv6 Router
IPv6/IPv4 Host
IPv6/IPv4 Host
30
IPv6 - IPv4 TRANSLATION
IPv4 Router
IPv4/IPv6 Translator
IPv6 Host
IPv4 Host
31
IPv6 OPERATION
IPv4/IPv6 Router
IPv4/IPv6 Router
IPv6/IPv4 Host
IPv6/IPv4 Host
32
PROPOSED TLA/NLA ASSIGNMENT RULES
33
MOTIVATION FORPROPOSED ASSIGMENT RULES

• Limit Number of Top Level Prefixes to Manageable
  Size
• Assign Top Level Prefixes only to Transit
  Providers
• Not assigned to Leaf Sites
• Assign Top Level Prefixes to Organizations who
• Are Capable of providing service
• Plan IPv6 service in near term

34
MOTIVATION (CONTINUED)

• Assignment policy match current IPv4 Practice
• Assignees make registration data available to
  Registries
• Assignments consistent w/ Aggregation Format
• Limit Prefix to /48
• Sites always get 80 bits (16bit SLA 64bit I ID)

35
TWO STAGE TLA ALLOCATION

• First Stage - Allocate Sub-TLA ID
• Create Sub-TLA out of TLA ID 1
• Second Stage - Allocate TLA ID
• When assignee demonstrates 90 usage of Sub-TLA

3 13 13 19 16
64
FP TLA Sub- NLA SLA
INTERFACE ID TLA
36
PROPOSED ASSIGNMENT REQUIREMENTS

• Plan to offer native IPv6 service within 9 months
  of assignment
• Verifiable track record of providing Internet
  transit service or capability of same
• No assignments to leaf sites
• Registration fee to IANA and/or
  service/registration fees to Registries

37
PROPOSED ASSIGNMENT REQUIREMENTS (CONTINUED)

• Provide Registry services for NLA space it is
  responsible
• Database of assignments publicly available to
  Registries
• Periodically provide Utilization statistics to
  Registry
• Must show 90 utilization prior to additional TLA
  assignments

38
DOCUMENTS

• Proposed TLA and NLA Assignment Rules
• ltdraft-ietf-ipngwg-tla-assignment-03.txtgt
• An Aggregatable Global Unicast Address Format
• ltdraft-ietf-ipngwg-unicast-aggr-04.txtgt

39
CURRENT STATUS
40
IPng STANDARDS STATUS

• IPv6 IETF Standards
• IPv6 Protocol
• Addressing Architecture
• ICMP
• DNS
• Security
• Unicast Aggregation Formats
• Transition Mechanisms
• Neighbor Discovery
• Address Auto-configuration
• OSI NSAP Mappings
• IPv6 over Ethernet
• IPv6 over FDDI
• IPv6 over PPP
• Jumbo Grams
• Routing Protocols (RIPng, OSPFv3, ISIS, BGP4)

• Tunneling
• MIBs
• IETF Completing Work
• Routing Protocols (PIM)
• Header Compression
• MIBs
• IPv6 over ltlinkgt
• Router Renumbering
• DHCP
• Service Location
• Mobility Support

41
IPv6 IMPLEMENTATIONS

• Host Systems
• Apple
• BSDI
• Digital
• Epiloque
• FTP Software (WIN)
• IBM (AIX)
• INRIA (NetBSD, FreeBSD)
• Linux
• Mentat (Streams)
• Microsoft
• Novell
• NRL (4.4-lite BSD)
• Pacific Softworks
• Process Software (VMS)
• SCO
• SICS/HP (HP-UX)

• Siemens Nixdorf
• Sun Microsystems
• UNH
• WIDE Consortium (NAIST, Hitachi, Sony, NTT)
• Routers
• 3Com
• Bay Networks
• Cisco Systems
• Digital
• Hitachi, Ltd.
• Merit
• Nokia
• NTH University
• Sumitomo Electric
• Telebit AS

42

• Testbed for IPv6 Testing and Deployment
• Modeled after MBONE
• Uses IPv6 in IPv4 Tunnels
• Currently
• 265 Sites
• 34 Countries
• 4 Continents

43
NOKIA
44
TOPOLOGY
45
DEPLOYMENT TIMETABLE
46
DEPLOYMENT TIMETABLE

• 1997-1998
• Product Development Continues
• Protocols Refined based on Experience
• 1998-1999
• IPv6 Appears in Users Systems as part of Software
  Upgrades
• Users Tryout IPv6
• 1999-2000
• Organizations start Converting to IPv6
• Translate to IPv4 at Organizational Boundaries

47
FOR MORE INFORMATION

• IPng Web Pages (General Info, Mailing Lists,
  etc.) http//playground.sun.com/ipng http//w
  ww.6bone.net
• Books
• IPng, Internet Protocol Next Generation
• by Scott O. Bradner Allison Mankin
  (Addison-Wesley)
• IPv6, The New Internet Protocol
• by Christian Huitema (Prentice Hall)
• IPng and the TCP/IP Protocols
• by Stephen Thomas (Wiley)

48
SUMMARY

• IPng is a New Version of IP
• Solves Current Critical Growth Problems
• Compatible with IPv4
• Improves IP in Many Areas
• Builds a Strong Base for the Future Growth