IPv6 Policy and Development Status

1
IPv6 Policy and Development Status

• TWNIC ????

2
Agenda

• Why IPv6 The problems of IPv4
• Addressing IPv6 header, addressing structure,
  allocation status
• Address policy and application IPv6 address
  allocation and assignment policy, request form
• Global IPv6 actions Status of IPv6 products,
  networks, specifications
• Taiwan IPv6 actions Taiwan development status

3

• Why IPv6?

4
Why IPv6 - IPv4 ????
5
????IPv4??????(?)
6
????IPv4??????(?)

• ??????IPv4????

7
Why IPv6 - Routing Table ???????

• ??Routing Table entry ???10??
• ??Internet?Routing Table??????,??????????????,???C
  PU?Memory?Bandwidth???????

8
Why IPv6 - Routing Table ???????
9
Why IPv6 - Routing Table ???????
10
Why IPv6 IPv4??????????

• ????????????(QoS)????????,?????(Mobility)?????(Sec
  urity)??????????(Differentiated
  Service)?,??IPv4?????????

11
Why IPv6 IPv6 ?? IPv4 ???

• ?????
• ???????
• ??????????
• ????
• ?????
• ????????????????

12

• Addressing

13
Addressing

• IPv4 IPv6?header??
• IPv4 header
• IPv6 header
• ????
• IPv6????
• ??
• ????
• ??????
• ????
• Link-Local?Site-Local??
• Interface ID
• Unicast Global address
• Multicast address
• Anycast address
• ????
• ????IPv6????????

14
Header??--IPv4 Header20 OctetsOptions 13
fields, include 3 flag bits
31
24
0 bits
8
4
16
Ver
IHL
Total Length
Service Type
Identifier
Flags
Fragment Offset
Time to Live
Header Checksum
Protocol
32 bit Source Address
32 bit Destination Address
Options and Padding
15
Header??--IPv6 Header40 Octets, 8 fields
16
IPv4 IPv6?header??(?)

• IPv4????header options?IPv6???
• Type of service
• Flags
• Identification
• Fragmentation offset (IPv6 uses path MTU
  discovery)
• Header Checksum

17
IPv4 IPv6?header??(?)

• ??????
• length gt payload
• protocol type gt next header
• time to live gt hop limit
• One field revised
• Option mechanism (variable length field replaced
  by fixed length extension header)
• ?????Two fields added
• Class
• Flow Label

18
IPv6????

• 128 bits long. Fixed size
• 2128 3.41038 addresses gt 6.651023 addresses
  per m2 of earth surface
• If assigned at the rate of 106/?s, it would take
  20 years
• Allows multiple interfaces per host
• Allows multiple addresses per interface

19
IPv6 --????(?)

• Addresses are assigned to interfaces
• No change from IPv4 Model
• Interface expected to have multiple addresses
• Addresses have scope
• Link Local
• Site Local
• Global
• Addresses have lifetime
• Valid and Preferred lifetime

20
IPv6 --????(?)
21
IPv6 --????(?)

• LAN addressing
• Subnet prefix MAC address /128

/128
SUBNET PREFIX /64
/128
/128
/128
22
IPv6 --????(?)??????

• Address syntax
• Hexadecimal values of eight 16 bit fields
• XXXXXXXX (X16 bit number, eg A2FE)
• 16 bit number is converted to a 4 digit
  hexadecimal number
• IPv6??????
• Preferred form 10800FF08800200C417A
• Compressed formFF0100000043 becomes
  FF0143
• IPv4-compatible 000000211.72.211.1 or
  211.72.211.1
• IPv6 prefix 20010200/23
• IPv4??????
• 211.72.211.1

23
IPv6 --????(?)????

• Unicast
• Address of a single interface
• Delivery to single interface
• Multicast
• Address of a set of interfaces
• Delivery to all interfaces in the set
• Anycast
• Address of a set of interfaces
• Delivery to a single interface in the set
• No more broadcast addresses

24
IPv6 --????(?) IPv6????

• ??RIR?IPv6??
• APNIC 20010200/23
• ARIN 20010400/23
• RIPE NCC 20010600/23
• RIPE NCC 20010800/23
• APNIC 20010C00/23
• 6Bone 3FFE/16
• 6to4 tunnels 2002/16

25
IPv6????(?)Global Unicast Addresses
0 3 16 24 48
64
127
NLA
interface ID
SLA
TLA
001
Res
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

26
IPv6????(?)??Unicast??

• unspecified address
• 00000000
• ?IPv4?0.0.0.0????
• loopback address
• 00000001
• ?IPv4?127.0.0.1????

27
IPv6????(?) 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

28
IPv6????(?) - 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
• auto-generated pseudo-random number(to address
  privacy concerns)
• assigned via DHCP
• manually configured
• possibly other methods in the future

29
IPv6????(?) - Multicast Address Format

• flag field
• low-order bit indicates permanent/transient group
• (three other flags reserved)
• scope field
• 1 - node local 8 - organization-local
• 2 - link-local B - community-local
• 5 - site-local E - global
• (all other values reserved)

30
IPv6????(?) - Anycast Address

• Anycast
• Is one-to-nearest type of address.
• Has a current limited use.
• ???????,???????router

31
IPv6????(?) ????
32
????IPv6????????(?)APNIC??IPv6??????
33
????IPv6????????(?)APNIC--IPv6 Prefixes Allocated
34

• IPv6 Address Policy

35
IPv6????

• IP????????
• IPv6 ????????
• IPv6??????
• IPv6 ????Allocation
• IPv6 ????Assignment
• IPv6????PI
• APNIC IPv6????

36
IP????????(?)
37
IP????????(?)
38
IPv6 ????????

• Oct 1998 Initial discussions RIRs/IETF and
  RIR communities
• Jul 1999 Provisional policy document
  released
• Aug 1999 IPv6 allocation service began
• Oct 1999 Review of policy document after
  early deployment experience
• May 2002 Revised policy document (latest
  draft) released
• Policies always subject to change

39
IPv6 ??????????
Discussions with RIR community
Policy meetings SIGs, mailing lists etc

Consensus of community
Liaison with other RIRs
Global Policies
Global Consensus
Regional Policy Variations
By RIRs and community
Policy is implemented
40
IPv6????

• Accordance with the Regional Internet Registry
  IPv6 policy document
• http//www.apnic.net/policies.html
• Goals
• Internet is able to function and grow to the
  maximum extent possible
• Aggregation of routing information limiting the
  number of routing entries advertised into the
  Internet (through hierarchy)
• Efficient address usage
• Registration of addresses

41
IPv6 ????Allocation(?)

• Be an LIR and
• Not be an end site and
• Plan to provide IPv6 connectivity to
  organisations and to end sites and
• Have a plan for making at least 200 /48
  assignments to other organisations within two
  years

42
IPv6 ????Allocation(?)

• Slow start
• First allocation to a LIR will be a /32
• /48s to organisations other than itself and
  provide connectivity to those other organisations
• An exception can be based on topological grounds
• No more than initial /32 will be given to
  requestors who cannot demonstrate previous
  assignment history
• Initial allocation allows the LIR to create a
  hierarchy within the allocation
• Ex an organization can receive 65,536 endsites
  (/48s)

43
IPv6 ????Allocation(?)

• What is a end site?
• An end user who has a business relationship
  with a provider carrying traffic
• E.g Consumer (dial up/cable/DSL)
• E.g Enterprise (leased line)
• How do you measure utilisation?
• Count the number of /48s assigned. No need to
  consider usage within each /48

44
IPv6 ????Allocation(?)

• Subsequent Allocations
• Calculated based on the HD ratio
• In a hierarchical address plan, as the size of
  the allocation increases, the density of
  assignments will decrease
• Count /48s assigned
• Meet utilisation threshold in HD ratio table for
  prefix
• Allocation size
• Size of subsequent allocation will depend on the
  demonstrated usage rate of the previous
  allocations
• Existing allocation doubled
• E.g. /32 will be expanded to a /31
• May be larger
• Allocations based on two year plan

45
IPv6 ????Allocation(?)

• Utilization
• ((48-P) HD)
• T 2
• TUtilization threshold
• P prefix
• HDHD-ratio
• Example
• HD-ratio 0.8 Prefix
  32,
• ((48-32)
  0.8)
• Threshold 2 7132
• Utilization 7132 / 65536
  10.9

46
IPv6 ????Allocation(?)

• LIR to ISP allocation
• Policy determined by LIR
• Must be able to meet HD ratio for subsequent
  allocations
• LIR responsible for tracking all /48s
• DB registration
• All /48 and shorter prefix allocations and
  assignments must be registered
• Existing /35 holders
• Eligible to have /35 expanded to a single /32
  prefix

47
IPv6 ????Allocation(?)

• IPv6 address space for regional organisations
• Can request for separate /32 blocks for routing
  purposes
• Need to apply from the respective RIR
• Organization's networks should satisfy the
  criteria for allocation of /32 space in each of
  the relevant regions

48
IPv6 ????Assignment

• Previous global consensus
• /48 generally
• /64 only one subnet
• /128 only one device connecting
• Multiple /48s
• Should be reviewed by RIR/NIR (until experience
  is gained)
• Second opinion process follows
• ISP infrastructure
• /48 per POP

49
IPv6 PI assignments for IXPs

• IXPs may need portable assignments
• IXPs are considered as a site eligible to receive
  a portable assignment
• Need to demonstrate the open peering policy
• Have 3 or more peers
• APNIC consensus /64
• All other needs should be met through normal
  processes
• ARIN region agreed /64
• RIPE region agreed /48

50
IPv6 address request form

• Requestor Template
• Network Template
• IPv6 Usage Template
• Additional information

51
IPv6???? - REQUESTOR TEMPLATE
REQUESTOR TEMPLATE name email acct-name
org-relationship
name provide the full name of the person
completing the request form email provide the
email address of the person completing the
request form acct-name TWNIC account name ( ex
HiNet-TW ) org-relationship describes the
relationship of the person completing the request
form to the organization intending to use the
address space
52
IPv6???? - NETWORK TEMPLATE
NETWORK TEMPLATE netname descr descr
country admin-c tech-c remarks changed
mnt-lower
53
IPv6???? - NETWORK TEMPLATE

• netname
• should be a short, but meaningful name for this
  network.
• identifies the network and relates to the
  organization that is requesting the
• address space.
• should be a word of single less than 25 capital
  alphanumeric characters.
• descr
• should be a brief description of the
  organization
• should include the location of the organization
• enough detail to distinguish it from other
  organizations
• country
• should contain the most appropriate two-letter
  ISO-3166 country code
• admin-c
• must be someone who is physically located at the
  site of the network
• may specify more than one admin-c for the
  network
• should enter these contacts in the NIC handle
  format

54
IPv6???? - NETWORK TEMPLATE

• tech-c
• must be a person responsible for the day-to-day
  operation of the network,
• but does not need to be physically located at
  the site of the network.
• may specify more than one tech-c for the network
  
• should enter these contacts in the NIC handle
  format
• remarks
• can be used for any remarks about the address
  space in this network that
• cannot be expressed in any of the other
  attributes
• may use multiple lines, but please keep remarks
  to a minimum
• changed
• is used to record the e-mail address of the
  person completing or updating this
• template, followed by the corresponding date
• date should be in the format of YYYYMMDD
• mnt-lower
• A maintainer object is a database object used to
  authorize updates to the
• APNIC database

55
IPv6???? - USAGE TEMPLATE
IPV6 USAGE TEMPLATE services cust-types
cust-network infrastructure network-plan
56
IPv6???? - USAGE TEMPLATE

• Services
• list the types of network services to be offered
  in the IPv6 network
• cust-types
• lists the types of customer that will be
  provided services from this network
• cust-network
• summarize past IPv6 assignments made to
  customers of this network
• format (using multiple lines as necessary)
  ltsubnet-sizegt ltnetnamegt
• Infrastructure
• summarize the IPv6 address assignments made to
  the organization's network
• infrastructure
• format (using multiple lines as necessary)
  ltsubnet-sizegt ltdescrgt
• network-plan
• summarize the address assignments planned for
  the organisation's network
• infrastructure, for up to two years
• format (using multiple lines as
  necessary)ltsubnet-sizegt ltnow/1yr/2yrgtltdescrgt
  
  
• Exnetwork-plan /50 /56,/56,/50 Head Office
  Lan(Support, marketing, sales etc)
  

57
IPv6???? - ADDITIONAL INFORMATION
ADDITIONAL INFORMATION 1. If your
organization has published information online
about its proposed IPv6 services, please
provide a URL where APNIC view that
information. 2. Please provide a network diagram
showing your planned IPv6 network. In your
diagram, please indicate approximate deployment
dates for planned infrastructure and
estimates of the amount of IPv6 address
space to be assigned in each part of the network.
3. If you are requesting an initial allocation
greater than the /32 minimum allocation,
then you may provide details of your IPv4
network here. Please provide a network diagram
showing your IPv4 network, indicating the
number of IPv4 customers that are currently
subscribed to your services. This information is
separate from the IPv6 customer network
details provided in the "IPv6 Usage
Template" above.
58
Evaluation

• Be LIR not an end-site
• Assigning address space to the end user
• Providing transit service for the end user to
  other sites
• Advertising an aggregate prefix route (Includes
  end user's assignments )

59
Evaluation

• 200 /48 assignments within 2 years
• Service types, requirement for customer
  assignment
• Infrastructure can support the number of planned
  customers
• Network Devices and Diagram
• Existing V4 infrastructure network and number of
  customer

60
Evaluation

• Provide v6 connectivity
• Service types Leased-line, ISP
• Network Devices and diagram
• Outline the list of existing v4 downstream
  customers

61
Global IPv6 actions
62
Global IPv6 actions

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

63
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

64
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

65
IPv6??????

• ???? IP stack ????? IPv6 ??
• ?release
• ? 3Com, BSD(KAME), Epilogue, Ericsson/Telebit,
  IBM, Hitachi, Nortel, Sun, Trumpet , Juniper,
  Cisco, Compaq, HP, Linux community, Microsoft
• ???
• ? Apple, Bull, Mentat, Novell, SGI

66
IPv6??????

• ARIN 37 allocations
• RIPE NCC 113 allocations
• APNIC 89 allocations
• ????
• http//www.ripe.net/cgi-bin/ipv6allocs

67
??????(?)

• 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)

68
??????(?)
IPv6 Deployment in Japan
69
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.

70
??????(?)
71
??????(?)
Transition Roadmap by Government (23 Feb 2001)
72
??????(?)

• 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.

73
100 IPv6 readiness by 2005

• Prime Minister of Japan Yoshiro Mori

• Korean MIC followed Japan Feb 23, 2001

74
Taiwan IPv6 actions
75
Taiwan IPv6 actions

• Address allocation status
• IPv6 ??????
• ??IPv6??????

76
IPv6 Address Allocation

• Chunghwa Telecom Labs. 3FFE3600/24 (Feb.
  1999)
• HiNet, Chunghwa Telecom 20010238/32 (Feb.8,
  2000)
• TANet (Taiwan Academic Network) 20010288/35
  (Oct. 2000)
• ASNet (Academia Sinica Network) 20010C08/32
  (July 2002)
• TTN (Taiwan Telecommunication Network)
  20010C50/32
• (Aug. 2002)
• 6REN-TW (IPv6 Research and Education Networks )
  20010C58/32
• (Aug. 2002)
• CHTTL (Chunghwa Telecom TL) 20010CAC/32
  (Oct. 2002)

77
???????IPv6??????? (??2002.10.18)
78
TANet

• IPv6 address allocation
• 20010288/35 (2000.10.6)
• 100 connectivity penetration rate to the
  domestic schools (all level) and universities
• 3 million Internet users base
• Peering with Cisco and HiNET
• Plan to implement island-wide native IPv6 by the
  end of 2002

79
ASNet

• 20010C08/32 (2002.7.11)
• APAN member since 2000, APAN-TW.
• STM-1 link to APAN
• Provide TANET/ TANET2 APAN transit.
• IPv6 Peering with 20 organizations

80
HiNet

• 20010238/32 (2000.2.8)
• The first ISP launched IPv6 commercial
  trial service since July, 1, 2001
• 6 IPv6 POPs
• LL, ADSL IPv6 connection
• Native connection
• 6to4Relay
• Tunneling
• TWIXv6 peering

81
NCHC

• NCHC manages 2 advanced networks, TANET2
  and NBEN
• 12 GigaPOPs in universities
• Some have been interconnected with native
  IPv6
• Major universities have built native IPv6
  campus networks

82
TWNIC

• Member of global IPv6 Forum
• Assisting IPv6 address space acquirement
• Promoting the use of IPv6
• Increasing IPv6 awareness
• Actively sponsoring and hosting IPv6 events
• Initiator and key player of both IPv6 Forum
  Taiwan and IPv6 Steering Committee

83
CCL, ITRI(Computer and Communications Research
Lab)

• One of the largest research lab
• Leading figure of local 3C RD work
• Leader of IPv6 Promotion Task Force, IPv6
  Steering Committee
• Established IPv6 forum Taiwan
• Formed IPv6 Industry RD alliance

84
Chunghwa Telecom Labs.

• 1st active node in Chinese Taipei on 6bone,
  CHT Labs became one of the 6bone
  backbone sites
• 3ffe3600/24 since Feb 1999.
• Hosting IPv6 Testing Interop Task Force of
  NICI IPv6 Steering Committee
• To build up IPv6 Demonstration and
  Interoperability Testing Lab

85
??IPv6??????

• ?????????2008-????????????
• ????20022007 ????
• ???3.2?

86
???????
??????????,?????IPv6 ?????????IPv6 Forum
Taiwan?????IPv6????,??????????????,????IPv6????,??
??IPv6??????,?????IPv6????????????????????????????
???IPv6????????
87
???????
88
????

• ??????????????,?????? IPv4 ? IPv6?
• ???????????,????????ISP???,?? ???? IPv4 ?IPv6?
• ????IPv4?IPv6?????????????,???????IPv6 ??????????
• ??????? IPv6 ??,?? IPv6 ???????,????IPv6
  ????????????????
• ???IPv6?????????,??????????????,?????????????
• ????IA??????????????????IPv6??,???????????????
• ?????????,??????IPv6????????

89
??????????
NICI ???????????
NICI?? ?????
IPv6?????? ??? ????? ????????????????? ????
??????????????
IPv6 Forum Taiwan

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

??? ?????? ????? ????
??????????? ????????????? TWNIC ??????
90
??????? Forum Taiwan ???

• ?????,IPv6 Forum Taiwan??IPv6???
• ???????????????,????
• ???????IPv6 Forum Taiwan?????
• ??? Forum,?????????????
• ??,?????????????,???
  
• ?,????IPv6?
• ?? Forum ?????,?????????
• ??????????

91
???????
1. ??????92???100?? IPv6,??ISP??96??
?100?? IPv6? 2.?92????????IPv4?IPv6?????
? 3.92-93????1-2?IPv6????(IPv6 Killer
Application) ??? 4.??????????96??????IPv6?
5.??(92-96??) ?????????? IPv6 ????? ??
6.?95????????????? IPv6 ??????? 7.92??????IPv6???
ISP??5??93??15??94? ?30??95???50?,96???100?
8.??????(??IPv6??????)????IPv6? SOC/Devices???
92
The End
Internet for everything? IPv6 is the answer!