System Overview

1
Internet Protocol Version 6 (IPv6)
???????????? ????? E-mail nfhuang_at_cs.nthu.edu.tw
URLhttp//www.cs.nthu.edu.tw/nfhuang
2
??

• IPv6 Introduction
• Routing and Addressing
• Plug and Play
• Security/QoS Supports
• IPv4/Ipv6 Transition Mechanisms
• IPv6 Current Status

3
IPv6 Applications

• Home Appliance Controllers
• VoIP/Video Streaming
• Remote Controllers
• 3G/4G
• Games
• Home Automation
• Others

4
IP????????
5
The Design of IPv6

• The Internet could not have been so successful in
  the past years if IPv4 had contained any major
  flaw.
• IPv4 was a very good design, and IPv6 should
  indeed keep most of its characteristics.
• It could have been sufficient to simply increase
  the size of addresses and to keep everything else
  unchanged.
• However, 10 years of experience brought lessons.
• IPv6 is built on this additional knowledge. It is
  not a simple derivation of IPv4, but a definitive
  improvement.

6
IPv6Header Format
IPv6 Header
IPv4 Header
7
A Comparison of Two Headers

• Six fields were suppressed
• Header Length, Type of Service, Identification,
  Flags, Fragment Offset, Header Checksum.
• Three fields were renamed
• Length, Protocol Type, Time to Live
• The option mechanism was entirely revised.
• Source Routing
• Route Recording
• Two new fields were added
• Priority and Flow Label (to handle the real-time
  traffic).

8
A Comparison of Two Headers

• Three major simplifications
• Assign a fixed format to all headers (40 bytes)
• Remove the header checksum
• Remove the hop-by-hop segmentation procedure

9
From Options to Extension Headers

• Hop-by-Hop options header
• Routing header
• Fragment header
• Authentication header
• Encrypted security payload
• Destination options header

IPv6 Header Next HeaderTCP
TCP Header
IPv6 Header Next Header Routing
Routing Header Next Header TCP
TCP Header
IPv6 Header Next Header Routing
Routing Header Next Header Fragment
Fragment Header Next Header TCP
Fragment of TCP Header
10
Routing Header
11
Fragment Header
Frame Length 2800 octets
I
P
v
6
f
r
a
g
m
e
n
t


F
i
r
s
t

1
4
0
0

o
c
t
e
t
s
h
e
a
d
e
r
h
e
a
d
e
r

1
I
P
v
6
f
r
a
g
m
e
n
t


L
a
s
t

1
4
0
0

o
c
t
e
t
s
h
e
a
d
e
r
h
e
a
d
e
r

2
N
e
x
t

H
e
a
d
e
r
R
e
s
e
r
v
e
d
F
r
a
g
m
e
n
t

O
f
f
s
e
t
R
e
s
M
More
I
d
e
n
t
i
f
i
e
r
12
IPv6 Addressing

• Three categories of IPv6 addresses
• Unicast
• Multicast
• Anycast
• Notation of IPv6 Addresses
• Write 128 bits as eight 16-bit integers separated
  by colons
• Example
• FEDCBA9876543210FEDCBA9876543210
  
• A set of consecutive null 16-bit numbers can be
  replaced by two colons
• Example 10800008800200C417A gt
  10808800200C417A

13
Addressing
H
H
H

• Some Addresses formats
• Provider Addresses
• Link Local Addresses
• Site Local Addresses
• Multicast Addresses
• Anycast Addresses

LAN
Link
Link
R
LAN
H
H
LAN
Site
Link
R
Site
Internet
Site (?????)
14
Global Unicast Addresses
interface ID
SLA
NLA
TLA
001
site topology (16 bits)
interface identifier (64 bits)
public topology (45 bits)

• TLA Top-Level AggregatorNLA Next-Level
  Aggregator(s)SLA Site-Level Aggregator(s)
• all subfields variable-length, non-self-encoding
  (like CIDR)
• TLAs may be assigned to providers or exchanges

15
Link-Local?Site-Local??

• Link-local addresses for use during
  auto-configuration and when no routers are
  present
• Site-local addresses for independence from
  changes of TLA / NLA

16
Interface IDs

• Lowest-order 64-bit field of unicast address may
  be assigned in several different ways
• auto-configured from a 64-bit EUI-64, or expanded
  from a 48-bit MAC address (e.g., Ethernet
  address)
• auto-generated pseudo-random number (to address
  privacy concerns)
• assigned via DHCP
• manually configured
• possibly other methods in the future

17
????
18
TheEvolutionof ICMP

• The ICMP for IPv4 was streamlined, and was made
  more complete by incorporating the multicast
  control functions of the IPv4 Group Membership
  Protocol.

19
IPv6 Routing

• As in IPv4, IPv6 supports IGP and EGP routing
  protocols
• IGP for within an autonomous system are
• RIPng (RFC 2080)
• OSPFv3 (RFC 2740)
• Integrated IS-ISv6 (draft-ietf-isis-ipv6-02.txt)
• EGP for peering between autonomous systems
• MP-BGP4 (RFC 2858 and RFC 2545)
• BGP4
• Added IPv6 address-family
• Added IPv6 transport
• Runs within the same process - only one AS
  supported
• All generic BGP functionality works as for IPv4
• Added functionality to route-maps and
  prefix-lists

20
Plug-and-Play -- Auto-configuration

• Autoconfiguration means that a computer will
  automatically discover and register the
  parameters that it needs to use in order to
  connect to the Internet.
• One should be able to change addresses
  dynamically as one changes providers.
• Addresses would be assigned to interfaces for a
  limited lifetime.
• Two modes for address configuration
• Stateless mode
• Stateful mode (using an IPv6 version of DHCP)

21
Link State Addresses

• When an interface is initialized, the host can
  build up a link local address for this interface
  by concatenating the well-known link local prefix
  and a unique token (48-bit Ethernet address).
• A typical link local address
• FE800000XXXXXXXXXXXX
• Link local address can only be used on the local
  link.

22
Stateless Autoconfiguration

• IPv6 nodes join the all nodes multicast group by
  programming their interfaces to receive all the
  packets for the address FF021.
• Send a solicitation message to the routers on the
  link, using the all routers address, FF022.
• Routers reply with a router advertisement
  message.
• Does not require any servers
• Relatively inefficient use of the address space
• Lack of network access control

23
Plug-and-Play --Address Resolution

• The neighbor discovery procedure offers the
  functions of ARP as well as those of router
  discovery. Defined as part of IPv6 ICMP.
• Host maintains four separate caches
• The destinations cache.
• The neighbors cache.
• The prefix list.
• The router list.

24
Destinations Cache

• The destinations cache has an entry for each
  destination address toward which the host
  recently sent packets.
• It associates the IPv6 address of the destination
  with that of the neighbor toward which the
  packets were sent.

Destination Neighbor
IPv6 Address (To) IPv6 Address (Via)
25
Neighbors Cache

• The neighbors cache has an entry for the
  immediately adjacent neighbor to which packets
  were recently relayed.
• It associates the IPv6 address of that neighbor
  with the corresponding media address (MAC
  address).

Neighbor Neighbor IPv6
Address MAC address
26
Prefix List and Router List

• The prefix list includes the prefixes that have
  been recently learned from router advertisements.
• The router list includes the IPv6 addresses of
  all routers from which advertisements have
  recently been received.

27
Basic Algorithm

• To transmit a packet, the host must first find
  out the next hop for the destination. The next
  hop should be a neighbor directly connected to
  the same link as the host.
• In most cases, the neighbor address will be found
  in the destinations cache.
• If not, the host will check whether one of the
  cached prefixes matches the destination address.
• If this is the case, the destination is local,
  the next hop is the destination itself.

28
Basic Algorithm

• Otherwise, the destination is probably remote. A
  router should be selected from the router list as
  the next hop.
• Once the next hop has been determined, the
  corresponding entry is added to the destinations
  cache, and the neighbors cache is looked up to
  find the media address (MAC) of that neighbor.

29
Neighbor Solicitation and Neighbor Advertisement
messages (IPv6 ?MAC)

• IPv6 source address link local address of the
  interface.
• Hop count 1.
• IPv6 destination address solicited node
  multicast address, which is formed by
  cancatenating a fixed 96-bit prefix,
  FF0200001, and the last 32 bits of the
  nodes IPv6 address.

Neighbor Solicitation
Type 136 Code 0 Checksum
R S Reserved
Target address
Options ... (Source link-level address)
Neighbor Advertisement
30
Real-time Support and Flows

• A flow is a sequence of packets sent from a
  particular source to a particular (unicast or
  multicast) destination for which the source
  desires special handling by the intervening
  routers.
• Flow label may be used together with routing
  header.
• Supporting Reservations
• Real-time flows
• Using RSVP and Flows
• Using Hop-by-Hop Options

31
Security
32
IPv6 Security

• All implementations required to support
  authentication and encryption headers (IPsec)
• Authentication separates from encryption for use
  in situations where encryption is prohibited or
  prohibitively expensive
• Key distribution protocols
• Support for manual key configuration required

33
Authentication Header

• Destination Address SPI identifies security
  association state (key, lifetime, algorithm,
  etc.)
• Provides authentication and data integrity for
  all fields of IPv6 packet that do not change
  en-route
• Default algorithm is Keyed MD5

34
Encapsulating Security Payload (ESP)
35
Migration from Ipv4 to Ipv6
36
IPv4-IPv6 Transition /Co-Existence

• A wide range of techniques have been identified
  and implemented, basically falling into three
  categories
• (1)Dual-stack techniques, to allow IPv4 and IPv6
  toco-exist in the same devices and networks
• (2)Tunneling techniques, to avoid order
  dependencies when upgrading hosts, routers, or
  regions
• (3)Translation techniques, to allow IPv6-only
  devices to communicate with IPv4-only devices
• Expect all of these to be used, in combination

37
Next Generation Transition
Dual Stack
NGTRANS
Translator
Tunneling
38
Transition Approaches

• Dual Stack
• system completely supports IPv6
• Tunneling
• IPv6 packets are encapsulated for transmission
  over existing IPv4 infrastructure
• Translation
• IPv6 packets are translated into IPv4 packets and
  vice versa
• Header information is preserved as much as
  possible

39
Dual Stack

• RFC 1933

• NGTRANS draft
• Draft-ietf-ngtrans-dstm-07.txt

IPv6
IPv4/IPv6
IPv4
AIIH (DHCPv6, DNS)
Dual Stack
Dual Stack
Dual Stack
40
Dual Stack Approach
Application
Preferred method on Applications servers
TCP
UDP
TCP
UDP
IPv4
IPv6
IPv4
IPv6
Frame Protocol ID
0x0800
0x86dd
0x0800
0x86dd
Data Link (Ethernet)
Data Link (Ethernet)

• Dual stack node means
• Both IPv4 and IPv6 stacks enabled
• Applications can talk to both
• Choice of the IP version is based on name lookup
  and application preference

41
Dual Stack Mechanisms

• Simple dual stack
• Both IPv4 and IPv6 are directly supported
• Dual Stack Transition Mechanism (DSTM)
• Temporary IPv4 addresses are assigned when
  communicating with an IPv4-only host.
• Cooperation between DNS and DHCPv6
• Dynamic Tunnel Interface encapsulates the IPv4
  packets

42
Dual Stack

• RFC 1933 -- Transition Mechanisms for IPv6
  Hosts and Routers
• NGTRANS draft
• Draft-ietf-ngtrans-dstm-07.txt

43
RFC 1933
Routing protocols
TCP/UDP
IPV4
IPV6
Device Driver
V6 network
V4/V6 network
V4 network
44
Draftietfngtransdstm-07

• Dual Stack Transition Mechanism (DSTM)

45
Dual Stack Transition Mechanism

• What is it for?
• DSTM assures communication between IPv4
  applications in IPv6 only networks and the rest
  of the Internet.

?
IPv4 only
IPv6 only
IPv4 Applications
46
DSTM
47
DSTM Principles

• Assumes IPv4 and IPv6 stacks are available on
  host
• IPv4 stack is configured only when one or more
  applications need it
• A temporal IPv4 address is given to the host
• All IPv4 traffic coming from the host is tunneled
  towards the DSTM gateway (IPv4 over IPv6).
• DSTM gw encapsulates/decapsulates packets
• Maintains an _at_v6 ? _at_v4 mapping table

48
DSTM How it works (v6 ? v4)
DSTM
DNS
DNS
C
B
A
DSTM GW

• In A, the v4 address of C is used by the
  application, which sends v4 packet to the kernel

• The interface asks DSTM Server for a v4 source
  address

• DSTM server returns - A temporal IPv4 address
  for A
• - IPv6 address of DSTM gateway

49
DSTM How it works (v6 ? v4)
DSTM
DNS
DNS
C
B
A
DSTM GW

• A creates the IPv4 packet (A4 ? C4)

• A tunnels the v4 packet to B using IPv6 (A6 ? B6)

• B decapsulates the v4 packet and send it to C4

• B keeps the mapping between A4 ? A6 in the
  routing table

50
DSTM
51
Tunneling

• RFC 1933
• RFC 2529
• RFC 3053
• RFC 3056
• Draft-ietf-ngtrans-isatap-04.txt

52
Tunneling
6over4

• RFC 2529
• RFC 3056
• RFC 3053

IPv4
IPv6
IPv6
6to4
IPv4
IPv6
IPv6
Tunnel Broker
IPv4
IPv4/ IPv6
IPv6
53
Using Tunnels for IPv6 Deployment

• Many techniques are available to establish a
  tunnel
• Manually configured
• Manual Tunnel (RFC 2893)
• GRE (RFC 2473)
• Semi-automated
• Tunnel broker
• Automatic
• Compatible IPv4 (RFC 2893)
• 6to4 (RFC 3056)
• 6over4
• ISATAP

54
RFC 1933

• Transition Mechanisms for IPv6 Hosts and Routers

55
RFC1933

• Configured tunnels
• Connects IPv6 hosts or networks over an existing
  IPv4 infrastructure
• Generally used between sites exchanging traffic
  regularly
• Automatic tunnels
• Tunnel is created then removed after use
• Requires IPv4 compatible addresses

56
Configured Tunnel

• Mechanism to carry IPv6 packets over IPv4
  infrastructure
• Encapsulate IPv6 in IPv4
• Tunnel endpoints are explicitly configured
• All IPv6 implementations support this
• Tunnel endpoints must be dual stack nodes
• The IPv4 address is the endpoint for the tunnel

Routing protocols
TCP/UDP
IPV6
IPV4
Device Driver
57
Configured Tunnel
IPv4 Networks
IPv6 Island
IPv6 Island
IPv4 Tunnel
Dual-stack node
Dual-stack node
IPv4 H
IPv6 H
Payload
IPv6 H
Payload
IPv6 H
Payload
58
Automatic Tunnel

• Node is assigned an IPv4 compatible address
• 140.114.1.101
• If destination is an IPv4 compatible address,
  automatic tunneling is used (tunneling to
  destination)
• Routing table redirects /96 to automatic tunnel
  interface

0000
IPv4 address
0000 . . . . . . . . 0000
16
32
80
59
Automatic Tunnel
Dual-stack node
Dual-stack node
IPv6 Island
IPv4 Tunnel
IPv4 Internet
IPv4 H
IPv6 H
Payload
IPv6 H
Payload
60
IPv6 Tunnel Broker

• RFC 3053

61
Motivation

• IPv6 tunneling over the internet requires heavy
  manual configuration
• Network administrators are faced with
  overwhelming management load
• Getting connected to the IPv6 world is not an
  easy task for IPv6 beginners
• The Tunnel Broker approach is an opportunity to
  solve the problem
• The basic idea is to provide tunnel broker
  servers to automatically manage tunnel requests
  coming from the users
• Benefits
• Stimulate the growth of IPv6 interconnected hosts
• Allow to early IPv6 network providers the
  provision of easy access to their IPv6 networks

62
Tunnel broker

• Tunnel broker automatically manages tunnel
  requests coming from the users
• The Tunnel Broker fits well for small isolated
  IPv6 sites, especially isolated IPv6 hosts on the
  IPv4 Internet
• Client node must be dual stack (IPv4/IPv6)
• The client IPv4 address must be globally routable
  (no NAT)
• RFC 3053

63
Tunnel broker architecture
64
How does it work?(1)
65
How does it work?(2)
66
IPv6/Ipv4 Translator

• RFC 2765
• RFC 2766
• RFC 2767
• RFC 3089
• RFC 3142

67
Translator

• RFC 2765RFC 2766
• RFC 2767
• RFC 3089RFC 3142

IPv6
IPv4
NATPT
SIIT
IPv4 Apps
IPv4 Apps
BITS
BITS
IPv6 Stack
IPv6 Stack
Socks-Gateway TCPUDP-Relay
IPv6 Host
IPv4 Host
IPv6
IPv4
68
Stateless IP/ICMP Translation algorithm (SIIT)

• RFC 2765

69
SIIT
70
SIIT

• Suppress the v4 stack
• Translate the v6 header into a v4 header on some
  point of the network
• Routing can direct packet to those translation
  points.
• Translate ICMP from both worlds
• No State in translators (? NAT)

71
SIIT
SIIT
IPv4 network
IPv4 host
IPv6 host
Pool of IPv4 addresses
Using SIIT for a single IPv6-only subnet
72
SIIT
IPv4 network
SIIT
Dual network
IPv6 host
IPv4 host
Pool of IPv4 addresses
Using SIIT for an IPv6-only or dual cloud which
contains some IPv6-only hosts as well as IPv4
hosts
73
SIIT

• Suitable for use when IPv6 side has no IPv4, for
  instance, for embedded systems with stack on
  chip.
• Ipv6 side uses special, translatable addresses,
  which preserve TCP/UDP checksum value
• Translatable source address is received by the
  IPv6 node from a shared pool translatable
  destination address is made from IPv4 DNS entry

74
RFC 2766

• Network Address Translation Protocol
  Translation (NAT-PT)

75
NAT-PT

• NAT-PT
• stands for Network Address Translation-Protocol
  Translation.
• translates IP address between IPv4 (32bits) and
  IPv6 (128bits).
• uses a pool of IPv4 addresses and ports.
• composes and manages a mapping table (IPv4 and
  IPv6)
• is similar to NAT in IPv4 network.

• SIIT
• stands for Stateless IP/ICMP Translation
  Algorithm.
• translates between IPv4 and IPv6 packet headers
  (including ICMP headers) in separate translator
  boxes in the network without requiring any
  per-connection state in those boxes.
• can be used as part of a solution that allows
  IPv6 hosts, which do not have a permanently
  assigned IPv4 address, to communicate with
  IPv4-only hosts.

76
NAT-PT
IPv4 packet
129.254.165.141 203.243.253.15 DATA
Mapping table Pool of address
32bits
32bits
NAT-PT
IPv6 packet
2001203201200ae01ff102ecd3ffe 200120320113f1e2ea2ff102f3c DATA
128bits
128bits
IPv4 header
ICMPv4 header
Ver HDlen TOS Total len
Type Code checksum
Identification flag Fragment offset
SIIT
TTL Protocol checksum
IPv6 header
ICMPv6 header
Ver Traffic Class Flow Label
Type Code checksum
Payload Length Next Header44 Hop Limit
IPv6 fragment header
Next Header Reserved Fragment Offset Res M
Identification
77
Configuration Requirements
TRANSLATOR
6
4
DNSv6 Server
IPv4 Host
Local area
IPv6 Server
IPv4 INTERNET
IPv6 Host
IPv6 Intranet
Tunneling path
Dual stack Host

• Network Configuration Requirements
• IPv4 Interface (eth0)
• IPv6 Interface (eth1)
• IPv6 Intranet Network Prefix(/96)
• Default outbound IPv6 Gateway
• Pool of IPv4 addresses and ports
• Static mapping for DNS server
• Support tunneling path(not yet)

IPv6 Host
IPv6 Intranet
78
Configuration requirements

• System Requirements
• NAT-PT must be border router between
  only-IPv4-network and only-IPv6-network.
• It is mandatory that all requests and responses
  pertaining to a session be routed via the same
  NAT-PT router.
• NAT-PT does not apply to packets originating from
  or directed to dual-stack nodes that do not
  require packet translation.
• End-to-end network layer security is not
  possible.

79
Address Translation (IPv4 -gt IPv6)
DA20012302 SAaaaa129.254.15.15
DA132.146.134.184 SA129.254.15.15
DNS(v4) 129.254.15.15
DNS(v6) 20012302
TRANSLATOR prefix aaaa/96
resource data (20012301)
DNS response resource data(132.146.134.180)
IPv6
IPv4
v6.opicom.co.kr ?
DA is changed to mappied address SA is added and
removed prefix/96
DA20012301 SAaaaa129.254.165.141
DA132.146.134.180 SA129.254.165.141
v4.etri.re.kr 129.254.165.141
v6.opicom.co.kr 20012301
DNS static Mapping
132.146.134.184 20012302
Mapping table
132.146.134.180 0001
132.146.134.180 20012301
132.146.134.181 0002
POOL of IPv4 ADDRESS
After mapping is verified either it is existed or
not, DNS-ALG makes the mapping table of IPv4
inside resource data
80
NAT-PT operations with DNS-ALG(IPv4?IPv6)
3FFE3600B3 ipv6DNS.cs.nthu.edu.tw
140.114.78.1 ipv4DNS.cs.nthu.edu.tw
(2)
(3)
IPv6 DNS
IPv4 DNS
A6
A
DNS-ALG
(4)
(6)
A6
A
Address allocation and create address mapping
(5)
(1)
NAT-PT
(7)
(8)
IPv6 host
IPv4 Host
140.114.78.58 ipv4.cs.nthu.edu.tw
3FFE3600B2 ipv6.cs.nthu.edu.tw
V4 address pool
IPv4 address pool
IPv6 lt-gt IPv4 Address Mapping Table
Final Result
140.114.78.51 140.114.78.52 140.114.78.53 140.114.
78.54 140.114.78.55
3FFE3600B2 lt-gt 140.114.78.51
IPv4 Host think its communicating with
140.114.78.51 IPv6 Host think its communicating
with 3FFE3600b140.114.78.58
81
Address Translation (IPv6 -gt IPv4)
DA129.254.15.15 SA132.146.134.184
DAaaaa129.254.15.15 SA20012302
DNS(v4) 129.254.15.15
TRANSLATOR prefix aaaa/96
DNS(v6) 20012302
resource data (129.254.165.141)
resource data (aaaa129.254.165.141)
IPv6
IPv4
v4.etri.re.kr ?
SA is changed to mappied address DA is added and
removed prefix/96
DA129.254.165.141 SA132.146.134.180
DAaaaa129.254.165.141 SA20012301
v4.etri.re.kr 129.254.165.141
v6.opicom.co.kr 20012301
132.146.134.184 20012302
DNS static Mapping
132.146.134.180 0001
132.146.134.180 20012301
132.146.134.181 0002
Mapping table
POOL of IPv4 ADDRESS
After mapping is verified either it is existed or
not, NAT-PT makes the mapping table of IPv6
source address
82
NAT-PT operations with DNS-ALG(IPv6?IPv4)
3FFE3600B3 ipv6DNS.cs.nthu.edu.tw
140.114.78.1 ipv4DNS.cs.nthu.edu.tw
IPv6 DNS
IPv4 DNS
A6
A
(2)
(3)
DNS-ALG
(4)
(6)
A6
A
Address allocation(get IPv6 prefix)
(1)
(5)
NAT-PT
(7)
(9)
IPv6 host
IPv4 Host
(8)
140.114.78.58 ipv4.cs.nthu.edu.tw
3FFE3600B2 ipv6.cs.nthu.edu.tw
V4 address pool
IPv6 lt-gt IPv4 Address Mapping Table
Final Result
140.114.78.51 140.114.78.52 140.114.78.53 140.114.
78.54 140.114.78.55
3FFE3600B2 lt-gt 140.114.78.51
IPv6 Host think its communicating with
3FFE3600b140.114.78.58 IPv4 Host think its
communicating with 140.114.78.51
83
Trend and Plan
ROUTER
Today IPv4 INTERNET OCEAN
ROUTER
NAT
Give me address
There are all IPv4 ISLAND
IPv4 connection
IPv6 connection
84
Trend and Plan
TRANSLATOR
Tomorrow IPv4 INTERNET OCEAN
TRANSLATOR
TRANSLATOR
There are some IPv6 ISLAND
IPv4 connection
IPv6 connection
85
Trend and Plan
TRANSLATOR
The day after tomorrow IPv6 INTERNET OCEAN
TRANSLATOR
Translator is still there
TRANSLATOR
There are some IPv4 ISLAND
IPv4 connection
IPv6connection
86
Global IPv6 actions

• IPv6 ????
• IPv6 ????
• IPv6??????
• ??????
• ??????
• ??????

87
IPv6 ????

• Core IPv6 specifications are IETF Draft
  Standards(well-tested and stable)
• IPv6 base spec
• ICMPv6
• Neighbor Discovery
• IPv6-over-Ethernet, IPv6-over-
• Other important specs are progressing and in
  good shape
• 3GPP wireless standard mandates IPv6

88
IPv6 ????

• ???? ( the 6bone )
• for testing and debugging IPv6 protocols and
  operations
• ?????????? ( the 6ren )
• CAIRN, Canarie, CERNET, Chunahwa Telecom,
  Dante, ESnet, Internet 2, IPFNET, NTT, Renater,
  Singren, Sprint, SURFnet, vBNS, WIDE
• ????
• a few ISPs (IIJ, NTT, SURFnet, Trumpet,) have
  announced commercial IPv6 service or service
  trials

89
IPv6??????

• ???? IP stack ????? IPv6 ??
• 3Com, BSD(KAME), Epilogue, Ericsson/Telebit,
  IBM, Hitachi, Nortel, Sun, Trumpet , Juniper,
  Cisco, Compaq, HP, Linux community, Microsoft,
  6wind, ETRI, etc

90
??????(?)

• Governmental - IPv6 Council
• - JGN (Japan Gigabit
  Network) IPv6
• RD - WIDE IPv6 / NSPIXP6 / Kame / Usagi / TAHI
• Industrial - IAJapan IPv6 Deployment Committee
  
• - JPNIC IPv6 project
• - IPv6 Operation Study Group
• - IPv6 Summit in Japan
• Publication - IPv6 Journal (RIIS)
• - v6start (Nikkei BP)

91
??????(?)
IPv6 Deployment in Japan
92
JAPAN -- IPv6 Council

• Initiated by Ministry of Public Management, Home
  Affairs, Posts and Telecommunications
• Chair Jun Murai
• Not only router vendors and service providers,
  but home appliance developers etc. are involved
• TAO (Telecommunications Advancement Organization
  of Japan) conducts a nation-wide IPv6 experiment
  including home appliance application development,
  using budget of 8 billion Yen ( 800k).

93
??????(?)
94
??????(?)
Transition Roadmap by Government (23 Feb 2001)
Phase I (2001)
Phase II (20022005)
Phase III (20062010)
Phase IV (2011)
IPv4 Only
IPv4 Ocean
IPv4 Island
IPv6 Only
IPv4/IPv6 Translation Required
Experimental IPv6 Network
IPv6 Ocean
IPv6 Island
Complete native IPv6
Commercial IPv6 Service (wire/wireless)

• Validation
• Operation
• Promotion

• IMT2000 Service
• Translation Service

95
??????(?)

• The government plans to develop
• IPv6-applied high speed Internet equipments
  including routers, IMT2000 terminals and
  information home appliances by investing 46.8
  billion won of government budget and 36.8 billion
  won of private fund, a total of 83.6 billion won
  until 2003.

96
Taiwan IPv6 actions
97
Taiwan IPv6 actions

• ??????
• TANET
• NBEN
• ????
• NICI IPv6??????
• ????
• Hinet
• IPv6 Forum Taiwan

98
TANET????

• APNIC????TANet?IPv6 sTLA??? 2001288/35
• TANet???IPv6????
• ???????????NLA
• ?????????????NLA
• ?????????,???Prefix /48
• ?????
• ??????? 20012880000/41
• ???? 20012880200/42
• ???? 20012880380/44
• ???? 20012880182/48
• ???????? 200128803A0/44
• ???? 20012880300/41
• ???? 20012880140/42

99
NICI IPv6????????

• ????IPv6 Forum Taiwan,??IPv6????
• ???????????
• ??????????
• ????????
• ??IPv6??
• http//www.ipv6.org.tw
• ??????
• ???????????????
• ??IPv6???????????
• IPv6????

100
NICI IPv6????????

• ??????????IPv6????????
• ????????,??????,?????????
• ,?????????????,??????????
• ????,????????????????????
• ?????IPv6,???????????IPv6????
• ,??????????IPv6?????
• ??????
• ??????IPv6 ?????
• ???IPv6????
• ???IPv6??????

?????????????????IPv6???,?????????????????????????
????
101
NICI IPv6????????
NICI ???????????
NICI?? ?????
IPv6?????? ??? ????? ???????????TWNIC
??? ????????????TWNIC ???
IPv6 Forum Taiwan

??????
??????
??????
??????
??? ???????? ????? ???? ?????????
?? ??????????
??? ???? ????? ???? ????????? ????
?????
??? ?????? ???
??? ?????? ????? ????
??????????? ??????????