Taiwan Network Information Center2002/10/31 IPv6 Policy and Development Status TWNIC 歐陽拾瓊

2002/10/31 Taiwan Network Information Center

IPv6 Policy and Development Status

TWNIC 歐陽拾瓊

2002/10/31© Taiwan Network Information Center 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


Why IPv6 ？


Why IPv6 - IPv4 位址不足

Internetworking Required:

Time

IPv4

IPv6

Total

Vo

lum

e2005 20151990

2001 2002 2003 2004 2005

Commercial IPv6 routers available

IPv6 in most OS for developers IPv6 specified for 3G

Many IPv6 apps. available IPv6 Operationally Viable

Operational 3G Systems

IPv4 address exhaustion

2006


亞太地區 IPv4 目前使用狀況 ( 一 )

Other Orgs42%

Unallocated30%

"Special purpose"

14%

RIPE NCC4%

ARIN 6%

APNIC 4%


亞太地區各國 IPv4 分配狀況

亞太地區 IPv4 目前使用狀況 ( 二 )

0

8

16

24

32

40

JP CN KR AU TW HK IN TH MY SG Other

Mill

ion

s

2002

2001

2000

1999

1998

1997

1996

Pre-1996


目前 Routing Table entry 已超過 10 萬筆

現有 Internet 的 Routing Table 成長越來越快，將會導致全球整體網路效能變差，並增加 CPU 、 Memory 、 Bandwidth 等資源的耗費。

Why IPv6 - Routing Table 成長遽增的問題



DeploymentPeriod of CIDR

Moore’s Law and CIDRmade it work for a while

But they cannot berelied on forever

Projected routing table growth without CIDR



0 20000 40000 60000 80000 100000 120000 140000

Nov-01

Dec-01

Jan-02

Feb-02

Mar-02

Apr-02

May-02

Jun-02

Jul-02<16

16

17

18

19

20

21

22

23

24

>24


Why IPv6 – IPv4 無法滿足網路應用發展

未來網路應用各項服務品質 (QoS) 之要求亦不斷提升，舉凡移動性（ Mobility ）、網路安全（ Security ）、保障頻寬、分級服務 (Differentiated Service)… 等，現行 IPv4 已漸無法滿足需求。


Why IPv6 – IPv6 改善 IPv4 的問題

擴充的位址簡化的表頭格式改善的選項及延伸表頭流量標籤認證與機密具有階層結構的位址設定及路由結構


Addressing


IPv4 & IPv6 之 header 比較– IPv4 header– IPv6 header– 差異比較

IPv6 定址架構– 簡介– 定址模式

定址模式介紹位址類型

– Link-Local 及 Site-Local 位址– Interface ID– Unicast Global address– Multicast address– Anycast address

– 定址空間– 亞太地區 IPv6 位址發放統計資料

Addressing


0 bits 84 16 31

Ver IHL Total Length

Identifier Flags Fragment Offset

32 bit Source Address

32 bit Destination Address

24

Service Type

Options and Padding

Time to Live Header ChecksumProtocol

RemovedChanged

Header 比較 --IPv4 Header20 Octets+Options : 13 fields, include 3 flag bits


0 31

Version Class Flow Label

Payload Length Next Header Hop Limit

128 bit Source Address

128 bit Destination Address

4 12 2416

Header 比較 --IPv6 Header40 Octets, 8 fields


IPv4 & IPv6 之 header 比較 ( 一 )

IPv4 中多餘的 header options 在 IPv6 被刪除 :

– Type of service– Flags– Identification– Fragmentation offset (IPv6 uses path MTU

discovery)– Header Checksum


IPv4 & IPv6 之 header 比較 ( 二 )

被改名的欄位 :length => payloadprotocol type => next headertime to live => hop limit

One field revised:Option mechanism (variable length field replaced

by fixed length extension header)新增的兩個 Two fields added:

ClassFlow Label


128 bits long. Fixed size 2128 = 3.4×1038 addresses => 6.65×1023

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

IPv6 定址架構


Link-LocalSite-LocalGlobal

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

IPv6 -- 定址模式 (一 )


Top Level

Next Level Next LevelNext Level

Site Level Site Level

Public Topology (Transit providers,ISPs & Exchanges)

Site Topology (LAN)

&Interface ID (link)

IPv6 -- 定址模式 (二 )


LAN addressing

– Subnet prefix + MAC address = /128

/128

SUBNET PREFIX /64

/128

/128/128

IPv6 -- 定址模式 (三 )


Address syntax– Hexadecimal values of eight 16 bit fields

X:X:X:X:X:X:X:X (X=16 bit number, eg: A2FE) 16 bit number is converted to a 4 digit hexadecimal number

IPv6 位址表示方式– Preferred form: 1080:0:FF:0:8:800:200C:417A– Compressed form:FF01:0:0:0:0:0:0:43 becomes FF01::43– IPv4-compatible: 0:0:0:0:0:0:211.72.211.1 or ::211.72.21

1.1– IPv6 prefix: 2001:0200::/23

IPv4 位址表示方式– 211.72.211.1

IPv6 -- 定址模式 (四 )位址表示方式


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


各個 RIR 的 IPv6 範圍– APNIC 2001:0200::/23 – ARIN 2001:0400::/23– RIPE NCC 2001:0600::/23 – RIPE NCC 2001:0800::/23 – APNIC 2001:0C00::/23

6Bone 3FFE::/16

6to4 tunnels 2002::/16

IPv6 -- 定址模式 ( 六 ) IPv6 位址範圍


sitetopology(16 bits)

interfaceidentifier(64 bits)

publictopology(45 bits)

interface IDSLA*NLA*TLA001

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

IPv6 位址類型 ( 一 )Global Unicast Addresses

0 3 16 24 48 64 127 Res


unspecified address– 0:0:0:0:0:0:0:0– 與 IPv4 的 0.0.0.0 意義相同

loopback address– 0:0:0:0:0:0:0:1– 與 IPv4 的 127.0.0.1 意義相同

IPv6 位址類型 ( 二 )特殊 Unicast 位址


Link-local addresses for use during auto-configuration and when no routers are present:

Site-local addresses for independence from changes of TLA / NLA*:

1111111010 0 interface ID

1111111011 0 interface IDSLA*

IPv6 位址類型 ( 三 ) Link-Local 及 Site-Local 位址


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

IPv6 位址類型 ( 四 ) - Interface IDs

xxxxxx00 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx 11111111 11111110

xxxxxx00 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx

1( 取補數 )

MAC

EUI-64


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)

FP (8bits)

Flags (4bits)

Scope (4bits) Group ID (32bits)

11111111 000T Lcl/Sit/Gbl Locally administered

RESERVED (80bits)

MUST be 0

IPv6 位址類型 ( 五 ) - Multicast Address Format


Anycast:– Is one-to-nearest type of address.– Has a current limited use.– 只能作目的位址，並且只能指派給 router

IPv6 位址類型 ( 六 ) - Anycast Address

n bits 128 - n bits

000…000Subnet Prefix


Allocation Space Prefix (binary) Fraction of Address Space

Reserved 0000 0000 1/256 Unassigned 0000 0001 1/256 Reserved for NSAP Allocation 0000 001 1/128 Reserved for IPX Allocation 0000 010 1/128 Unassigned 0000 011 1/128 Unassigned 0000 1 1/32 Unassigned 0001 1/16 Unassigned 010 1/8 Provider-Based Unicast Address 001 1/8 Unassigned 011 1/8 Reserved for Geographic-Based Unicast Addresses

100 1/8

Unassigned 101 1/8 Unassigned 110 1/8 Unassigned 1110 1/16 Unassigned 1111 0 1/32 Unassigned 1111 10 1/64 Unassigned 1111 110 1/128 Unassigned 1111 1110 0 1/512 Link Local Use Addresses 1111 1110 10 1/1024 Site Local Use Addresses 1111 1110 11 1/1024 Multicast Addresses 1111 1111 1/256

IPv6 位址類型 ( 七 ) 定址空間


亞太地區 IPv6 位址發放統計資料 ( 一 )APNIC 現今 IPv6 位址發放狀況

日本

韓國

台灣

澳洲

中國大陸

新加坡

泰國

馬來西亞

香港

印尼巴布亞

新幾內亞合計

48 15 6 4 4 4 3 2 1 1 1 89

54%

17%

7%

4%

4%

4%

3%

2%

1%

1%

1%

100%

日本 , 55%

馬來西亞 , 2%

香港 , 1%

印尼 , 1%

巴布亞新幾內亞 , 1%

韓國 , 18%

台灣 , 7%澳洲 , 4%

新加坡 , 4%

泰國 , 3%

其他 , 6%

中國大陸


亞太地區 IPv6 位址發放統計資料 ( 二 )APNIC--IPv6 Prefixes Allocated

0

10

20

30

40

50

60

70

80

Jul-99 Jan-00 Jul-00 Jan-01 Jul-01 Jan-02 Jul-02

2002: 29

2001: 26

2000: 15


IPv6 Address Policy


IP 位址申請單位介紹 IPv6 位址政策發展狀況 IPv6 位址政策介紹 IPv6 位址政策— Allocation IPv6 位址政策— Assignment IPv6 位址政策— PI APNIC IPv6 申請表格

IPv6 位址政策


IP 位址申請單位介紹 ( 一 )


ASO(and Address Council)

IANAMarina del Rey, CA, US

LIR

LIR

LIR

LIR LIR

NIR

APNICBrisbane, Australia

ISP ISP

ISP ISP

ISP

ARINReston, VA, US

LIR LIR LIR LIR LIR

RIPE-NCCAmsterdam, The Netherlands

ICANN

IP 位址申請單位介紹 ( 二 )


– 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

IPv6 位址政策發展狀況


By RIRs and community

Discussions with RIR community

Liaison with other RIRs

Policy meetings & SIGs, mailing lists etc

Global Consensus

Consensus of community

Policy is implemented

RegionalPolicy

Variations

GlobalPolicies

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

IPv6 位址政策


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

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)

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

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 demonstrat

ed 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

IPv6 位址政策— Allocation( 四 )


IPv6 位址政策— Allocation( 五 ) Utilization

((48-P) * HD)

T = 2

– T ： Utilization threshold– P ： prefix– HD ： HD-ratio

Example: HD-ratio = 0.8 Prefix = 32 ， ((48-32) *0.8)

Threshold = 2 = 7132

Utilization = 7132 / 65536 = 10.9%


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

IPv6 位址政策— Allocation( 六 )


IPv6 address space for regional organisations – Can request for separate /32 blocks for routing purpo

ses– 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

IPv6 位址政策— Allocation( 七 )


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

IPv6 位址政策— Assignment


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

IPv6 PI assignments for IXPs


IPv6 address request form

Requestor Template

Network Template

IPv6 Usage Template

Additional information

Requestor Template

Network Template

IPv6 Usage Template

Additional information


IPv6 申請表格 - REQUESTOR TEMPLATE

nameprovide the full name of the person completing the request form

emailprovide the email address of the person completing the request formacct-name TWNIC account name ( ex: HiNet-TW )org-relationshipdescribes the relationship of the person completing the request form to the organization intending to use the address space

nameprovide the full name of the person completing the request form

emailprovide the email address of the person completing the request formacct-name TWNIC account name ( ex: HiNet-TW )org-relationshipdescribes the relationship of the person completing the request form to the organization intending to use the address space

#[REQUESTOR TEMPLATE]# name: email: acct-name: org-relationship:


IPv6 申請表格 - NETWORK TEMPLATE

#[NETWORK TEMPLATE] #

netname: descr:descr: country: admin-c: tech-c: remarks: changed: mnt-lower:



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

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



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

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


IPv6 申請表格 - USAGE TEMPLATE

#[IPV6 USAGE TEMPLATE]#

services:cust-types: cust-network:infrastructure:network-plan:


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): <subnet-size> <netname>

Infrastructure summarize the IPv6 address assignments made to the organization's network infrastructure format (using multiple lines as necessary): <subnet-size> <descr>

network-plan summarize the address assignments planned for the organisation's network infrastructure, for up to two years format (using multiple lines as necessary):<subnet-size> <now/1yr/2yr><descr> Ex:network-plan: /50 /56,/56,/50 Head Office Lan(Support, marketing, sales etc)

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): <subnet-size> <netname>

Infrastructure summarize the IPv6 address assignments made to the organization's network infrastructure format (using multiple lines as necessary): <subnet-size> <descr>

network-plan summarize the address assignments planned for the organisation's network infrastructure, for up to two years format (using multiple lines as necessary):<subnet-size> <now/1yr/2yr><descr> Ex:network-plan: /50 /56,/56,/50 Head Office Lan(Support, marketing, sales etc)


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.

#[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.


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 )


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


Evaluation

Provide v6 connectivity– Service types: Leased-line, ISP

– Network Devices and diagram

– Outline the list of existing v4 downstream customers


Global IPv6 actions


IPv6 標準現況 IPv6 建置現況 IPv6 產品發展現況 IPv6 位址分配現況日本發展現況韓國發展現況

Global IPv6 actions


IPv6 標準現況

Core IPv6 specifications are IETF Draft Standards(well-tested and stable)

IPv6 base specICMPv6Neighbor DiscoveryIPv6-over-Ethernet, IPv6-over-…

Other important specs are progressing and in good shape

3GPP wireless standard mandates IPv6


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


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


IPv6 位址分配現況

ARIN: 37 allocations

RIPE NCC : 113 allocations

APNIC : 89 allocations

資料來源 :

http://www.ripe.net/cgi-bin/ipv6allocs


日本發展現況 ( 一 )

Governmental - IPv6 Council

- JGN (Japan Gigabit Network) IPv6

R&D - 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)


日本發展現況 ( 二 )

IPv6 Deployment in Japan

Common Carrier

iDC

ISP/CATV...Enterprise

IPv6Network

Home

Mobile

Global Center Japan + HnB+Hitachi

e-Japan NTT-C,KDDI,

etc.

IIJ,etc.


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.

JAPAN -- IPv6 Council


IPv6 Deployment Policy

6Bone-KR

IPv6 Commercial Network

KRv6 Project

IPv6 Address Allocation

IPv6 Forum Korea

• Government Strategies • Since Feb 2001

• 8 /35 prefix sTLA allocations• Since 1999 • KRNIC, ETRI, KOREN, etc.

• 6NGIX: IPv6 Next Generation Internet eXchange

• KT, KOREN, KOSINET6, etc.

• IPv6 Research & Development• IPv4/IPv6 Translator, BIA, etc.• Since 2000

• National Forum since 2000 for the promotion of IPv6

• 61 regular organizational members • Korea-EU IPv6 Network• Partnership with 6WINIT• Since 2001

Trans-Eurasia Project

• Experimental IPv6 Testbed• 2 pTLAs• Since 1996

韓國發展現況 ( 一 )


韓國發展現況 ( 二 )

Transition Roadmap by Government (23 Feb 2001)

Complete native IPv6CommercialIPv6 Service

(wire/wireless)

Phase I(~2001)

Phase I(~2001)

Phase II(2002~2005)

Phase II(2002~2005)

Phase III(2006~2010)


Phase IV(2011~)

Phase IV(2011~)

IPv4 Only IPv4 Ocean

IPv6 Island

IPv4 Island

IPv6 Ocean

IPv6 Only

• Validation• Operation• Promotion

• IMT2000 Service• Translation Service

IPv4/IPv6 Translation Required

ExperimentalIPv6 Network


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.

韓國發展現況 ( 三 )


100% IPv6 readiness by 2005

Prime Minister of Japan Yoshiro Mori

Korean MIC followed Japan Feb 23, 2001


Taiwan IPv6 actions


Address allocation status

IPv6 推動相關單位我國 IPv6 建置發展計畫

Taiwan IPv6 actions


IPv6 Address Allocation

Chunghwa Telecom Labs.Chunghwa Telecom Labs. 3FFE:3600::/24 (Feb. 1999) 3FFE:3600::/24 (Feb. 1999)

HiNet, Chunghwa TelecomHiNet, Chunghwa Telecom 2001:0238::/32 (Feb.8, 2000) 2001:0238::/32 (Feb.8, 2000)

TANet (Taiwan Academic Network)TANet (Taiwan Academic Network) 2001:0288::/35 (Oct. 2000) 2001:0288::/35 (Oct. 2000)

ASNet (Academia Sinica Network)ASNet (Academia Sinica Network) 2001:0C08::/32 (July 2002) 2001:0C08::/32 (July 2002)

TTN (Taiwan Telecommunication Network) 2001:0C50::/32 TTN (Taiwan Telecommunication Network) 2001:0C50::/32

(Aug. 2002)(Aug. 2002)

6REN-TW (IPv6 6REN-TW (IPv6 Research and Education NetworksResearch and Education Networks ) 2001:0C58::/3 ) 2001:0C58::/3

22

(Aug. 2002)(Aug. 2002)

CHTTL (Chunghwa Telecom TL) 2001:0CAC::/32 (Oct. 2002)CHTTL (Chunghwa Telecom TL) 2001:0CAC::/32 (Oct. 2002)


台灣與亞太地區 IPv6 位址核發量比較 ( 截至 2002.10.18)

1999 年 7-12月 2000 年 1-6 月2000 年 7-12

月 2001 年 1-6 月2001 年 7-12月 2002 年 1-6 月

2002 年 7-12 月

7

5

10

7

19

14

27

0 1 10 0 0

40

5

10

15

20

25

30

台灣地區亞太地區

資料來源：台灣網路資訊中心彙整


TANetTANet

• IPv6 address allocation:IPv6 address allocation:

2001:0288::/35 (2000.10.6)2001:0288::/35 (2000.10.6)

• 100% connectivity penetration rat100% connectivity penetration rate to the domestic schools (all level) e to the domestic schools (all level) and universitiesand universities

• 3 million Internet users base3 million Internet users base

• Peering with Cisco and HiNETPeering with Cisco and HiNET

• Plan to implement island-wide natPlan to implement island-wide native IPv6 by the end of 2002ive IPv6 by the end of 2002


ASNeASNett

• 2001:0C08::/32 2001:0C08::/32 (2002.7.11)(2002.7.11)

• APAN member since APAN member since 2000, APAN-TW.2000, APAN-TW.

• STM-1 link to APANSTM-1 link to APAN• Provide TANET/ Provide TANET/

TANET2 APAN transit. TANET2 APAN transit. • IPv6 Peering with 20 IPv6 Peering with 20

organizations organizations


HiNetHiNet

2001:0238::/32 (2000.2.8)2001:0238::/32 (2000.2.8)

The first ISP launched IPv6 The first ISP launched IPv6 commercial trial service since commercial trial service since

July, 1, 2001 July, 1, 2001

– 6 IPv6 POPs6 IPv6 POPs

– LL, ADSL IPv6 connectionLL, ADSL IPv6 connection

Native connectionNative connection

6to4Relay6to4Relay

TunnelingTunneling

TWIXv6 peeringTWIXv6 peering

Taipei(S2)

Taoyuan

Hsinchu

Taichung

Tainan Kaoshiung

Frame Relay

T1~64Kbps

T1~64K

T1~64K

T1~64K

T1~64K

T1~64K

HiNetTWIXv6

FE TWIXv6

ISP1

ISP2


NCHNCHCC

NCHC manages 2 NCHC manages 2 advanced networks, advanced networks, TANET2 and NBEN TANET2 and NBEN

12 GigaPOPs in 12 GigaPOPs in universities universities

Some have been Some have been interconnected with interconnected with native IPv6 native IPv6

Major universities Major universities have built native IPv6 have built native IPv6 campus networks campus networks


TWNITWNICC

Member of global IPv6 ForumMember of global IPv6 ForumAssisting IPv6 address space Assisting IPv6 address space acquirement acquirementPromoting the use of IPv6Promoting the use of IPv6Increasing IPv6 awarenessIncreasing IPv6 awarenessActively sponsoring and Actively sponsoring and hosting hosting IPv6 events IPv6 eventsInitiator and key player of both Initiator and key player of both IPv6 Forum Taiwan and IPv6 IPv6 Forum Taiwan and IPv6 Steering Committee Steering Committee


CCL, ITRICCL, ITRI(Computer and Communications Research Lab)(Computer and Communications Research Lab)

One of the largest research lab One of the largest research lab

Leading figure of local 3C R&D workLeading figure of local 3C R&D work

Leader of IPv6 Promotion Task Force, IPv6 Leader of IPv6 Promotion Task Force, IPv6 Steering Committee Steering Committee

Established IPv6 forum Taiwan Established IPv6 forum Taiwan

Formed IPv6 Industry R&D allianceFormed IPv6 Industry R&D alliance


Chunghwa Telecom Labs.Chunghwa Telecom Labs.

• 1st active node in Chinese Taipei on 6bone, CHT Labs became one of the 6bone backbone sites

• 3ffe:3600::/24 since Feb 1999.

• Hosting IPv6 Testing & Interop Task Force of NICI IPv6 Steering Committee

• To build up IPv6 Demonstration and Interoperability Testing Lab


已被列入政府「挑戰 2008- 數位化台灣」中之旗艦計畫

計畫期間： 2002~2007 六年計畫總經費： 3.2 億

我國 IPv6 建置發展計畫


藉由政府及民間之力量，分別透過「 IPv6 推動工作小組」及「 IPv6 Forum Taiwan 」共同進行 IPv6 推動計畫，以期整合產、官、學、研界資源，同步推動 IPv6 建置計畫，實現國內 IPv6 網際網路環境，並加速國內 IPv6 軟硬體研發、網路互連及測試、骨幹建設及推廣應用俾使我國即早邁入 IPv6 資訊網路新紀元。

計畫藍圖與願景


推動小組下成立各工作分組 IPv6 Forum Taiwan

Announcement

Phase I (~2002)NICI 成立 IPv6 推動工作小組

IPv6 骨幹建置

IPv6 網路互連及測試IPv6 軟硬體研發

IPv6 應用推廣

Phase II (2003~2005)

由 IPv4 轉換至 IPv6

Native IPv6


IPv6 Readiness:For any new network devices, Infrastructure and applications

計畫藍圖與願景


• 使我國網際網路相關軟硬體設備，皆能同時支援 IPv4 及 IPv6 。

• 我國網際網路之基礎設施，包括學術網路及各 ISP 之骨幹，皆能同時支援 IPv4 及 IPv6 。

• 全力支援 IPv4至 IPv6 網路轉換機制之研究發展建設，以提供各界導入 IPv6 平台之無縫解決方案。

• 全面宣導及推廣 IPv6 知識，加強 IPv6 科技人才之培育，並鼓勵以 IPv6 為平台開發新型態之網際網路應用。

• 促進與 IPv6社群之國際合作交流，積極參與各項國際標準制定活動，期與先進國家技術同步發展。

• 積極鼓勵 IA設備、無線通信業者及各項終端設備崁入 IPv6功能，提昇產品附加價值及國際競爭力。

• 整合政府及民間資源，共同推動我國 IPv6 之網路建設工作。

計畫目標


IPv6 推動工作小組召集人　：簡局長仁德副召集人：高副局長凱聲、曾董事長憲雄執行秘書：蘇總工程司宗宏、陳執行長文生

IPv6 推動工作小組召集人　：簡局長仁德副召集人：高副局長凱聲、曾董事長憲雄執行秘書：蘇總工程司宗宏、陳執行長文生

NICI總召集人：蔡政務委員清彥

NICI總召集人：蔡政務委員清彥 NICI 民間

諮詢委員會NICI 民間諮詢委員會

應用推廣分組研究發展分組標準測試分組骨幹建設分組

召集人 : 國家高速電腦中心莊主任哲男副召集人 :中華電信謝副總經理俊明教育部計算機中心陳主任景章中研院計算機中心林主任誠謙

召集人 : 國家高速電腦中心莊主任哲男副召集人 :中華電信謝副總經理俊明教育部計算機中心陳主任景章中研院計算機中心林主任誠謙

召集人 : 清華大學黃教授能富副召集人 :交通大學陳教授耀宗東華大學趙教授涵捷

召集人 : 清華大學黃教授能富副召集人 :交通大學陳教授耀宗東華大學趙教授涵捷

召集人 : 中華電信研究所梁所長隆星副召集人 :資策會網路及通訊實驗室張主任嘉祥中研院何副所長建明

召集人 : 中華電信研究所梁所長隆星副召集人 :資策會網路及通訊實驗室張主任嘉祥中研院何副所長建明

召集人 : 工研院電通所林所長寶樹副召集人 : 友訊科技副李董事長中旺教育部計算機中心陳主任景章TWNIC 陳執行長文生

召集人 : 工研院電通所林所長寶樹副召集人 : 友訊科技副李董事長中旺教育部計算機中心陳主任景章TWNIC 陳執行長文生

IPv6 Forum Taiwan

推動工作小組組織架構


於運作初期， IPv6 Forum Taiwan 將為 IPv6推動工作小組下之活動推廣分組主要工作，活動推廣　　分組召集人亦為 IPv6 Forum Taiwan 之召集人。　透過此 Forum ，業界之建議可直接反應至推動　小組，以使政府政策與民間需求一致，相互配　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　合，共同推動 IPv6 。

待此 Forum 運作成熟後，擬獨立由會員費收入　　及民間力量繼續運作。

推動工作小組與 Forum Taiwan 之關係


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產品。

預期效益及影響


The End

Documents

Taiwan Network Information Center2002/10/31 IPv6 Policy and Development Status TWNIC 歐陽拾瓊