新一代網際網路協定互通認證計畫
挑戰IPv6新紀元座談會
報告人：黃勝雄博士 /
新一代網際網路協定互通認證計畫法規政策分項主持人
中華民國國家資訊基本建設 (NII) 產業推廣協進會
2011/03/29
1
History of Internet
•1945 Memex Conceived
•1948 Mathematical Theory of Communication
•1958 Silicon Chip
•1964 Packet Switching Invented
•1962 First Vast Computer Network Envisioned
•1965 Hypertext Invented
1968
•1969 ARPANET Demonstrated
•1972 TCP/IP Invented
•First Gateway
1980
1986
1993
•NSI-Net Initiated
•Multi-Protocol Environment
•1989 WWW Created
•ARPANET Widely Used
•1981 IPv4 RFC 791 Published
•1984 Internet Named and Goes TCP/IP
•MILNET ARPANET Split
•1993 Mosaic Created
•1995 eCommerce Emerged
•1998 IPv6 RFC 2460 Published
2
Data: (1) William F. Slater, Chicago Chapter of ISOC, (2) IETF
IPv4 Exhaustion
The End of The Beginning
Global Pool Exhausted at
2011. Feb.3
Asia Pacific Pool Exhausted at
2011. April
Final /8 : Dualstack purpose
ISP gets /22, total 16384s
3
Now What
Option
稀釋IPv4
Option
NAT/CGN
私
部
門
Option
回收IPv4
Option
Transfer
Reclamation
Recommended
v4/v6雙協定
Dual-stack
原因:
1 RIR Policy
2 IETF Recommendations
公
部
門
Mandatory
原因:
1 IPv6是IPv4枯竭後唯一可發放
之位址. 具有資源排它性
4
2 滿足電信法(詳後)
IPv6 Future Bet
IPv6 / IPv4 BGP Table Size Ratio
量化成本
政府IPv6網路建置成本
• 缺乏概化基礎 (Lack of Generalizability)
– 不同部會 IPv6準備度不同, 致使移轉成本不同
• 財務風險
– 無法評估精確財務風險
– 透過部署範圍規範 (Sizing & Scoping), 可以將財務風
險控制在可預測範圍.參考[成本-時程建議]節
• 非財務風險
– 採用或修改後採用現行資訊服務作業規範以求最大
程度控制非財務風險, 例如資訊服務品質 ITIL 標準
、資訊安全 ISO27000系列標準、或美國政府之IT
Enterprise Architecture
6
財務風險
政府IPv6網路Initial Sizing
• DNS Capacity (IPv6 gov.tw)
– 啟用: 現有 DNS 啟用雙協定新增 AAAA 紀錄
– 擴充: 無擴充. 預期現有系統可滿足新增v6需求
– 接取 : 接取IPv6網路或DNS hosting
• WWW Capacity
– 啟用: 現有系統啟用雙協定
– 擴充: 現有IPv4 WWW系統承載量 x 3%-5% 估算
– 接取 : 接取IPv6網路或採取IPv6 Colocation
• Network Capacity
–
–
–
–
啟用: 啟動路由系統雙協定
擴充: 以現有IPv4訊務量x3%-5%估算
上鏈(Transit): 採購IPv6 Transit
互鏈(Peering): 配置Layer2 交換器, 啟用階段即配置IPv6公共網路交
換中心 (6PIX: IPv6 Public Internet Exchange) 以滿足公私部門互鏈需
求
7
Priority Matrix
政府IPv6網路建置優先順序
External
A Services
Perceived Value
H
Nodes < 1K?
WWW, DNS, Email Tiered Deploy ?
Tier Criteria
Transit/Peering
Backbone , IX
B
M
Nodes <10K?
Connectivity
Expansion
Access Networks
Internal Use
C & All IPv6
L
Nodes < 10M?
L
Internal Services,
Database, Desktop
H/W, S/W
M
Cost Estimate
H
8
Non-financial Risk
Issue List
1 v6/v4 fallback
Host
IPv6
IPv4
Web
IPv6
IPv4
X
over 20 Seconds
Why:
Poor IPv6 Connectivity
1 Unmanaged transition mechanism
2 No IPv6 connectivity but AAAA RR existed
3 No IPv6 global connectivity
2 DNS query increase
FeeBSD
Linux
MacOS
Vista
A & AAAA
query sequence order
A first
AAAA first
A first
A first
When does domain
name completion
occur
After A+AAAA
All AAAA
completion
Alter A+AAAA
9
Continue
3 Operational practice/technology takes time
IP
TCP
Telnet
IDN
IPv6
Idea
1969
1974
1969
1998
1994
Current
1981
1981
1983
2004
1998
4 Cost of management for long term overlapping period
•doubles number of service
interfaces
•requires changes above &
below
•major interoperability issues
Resiliency at Core vs. Resiliency at Edge
10
Gain & Loss
Every action has a price and pleasure
Perceived Gain
Perceived Loss
1. 基於公共資源排它性, 滿
足電信法需求, 政府提供
IPv6服務
2. 滿足未來可能網路位址
成長需求, mobileInternet, Internet of
Things
3. 增進我國ICT競爭優勢
1. 財務成本:導入成本(參考
成本說明)
2. 非財務成本: 服務品質可
能影響 (ref. Issue List)
3. 未來管理成本 (IPv4
Post-Transition)
11
對應價值之合理性分析
項目
必要性
對應價值
必要
因應公共資源排它性, 滿足
1 電信法20條普及服務: 全體國民享有一定品質電信服務
2 電信法21條電信服務: 公平提供服務, 不得為差別處理
3 電信法22條電信傳遞: 非依法律,不得拒絕電信的接受與
傳遞
必要
因應公共資源排它性, 滿足
1 電信法20條普及服務: 全體國民享有一定品質電信服務
2 電信法21條電信服務: 公平提供服務, 不得為差別處理
3 電信法22條電信傳遞: 非依法律,不得拒絕電信的接受與
傳遞
External
A Services
WWW, DNS, Email
Transit/Peering
Backbone, IX
B
Connectivity
Expansion
Access Networks
Internal Use
C & All IPv6
Internal Services,
Database, Desktop
H/W, S/W
選擇性
1 IPv6 在此階段具備市場經濟價值, 即 IPv6具備正向外
部性效益(Externality)
2 全面性推動 IPv6 增進外部性價值 及發揮網路效益
12
Proposed Schedule
Position
0 Statement
Government
Official Support
T0
External
A Services
WWW, DNS, Email
Transit/Peering
Backbone, IX
Ta
Connectivity
Expansion
Internal Use
C & All IPv6
Access Networks
Internal Services,
Database, Desktop
H/W, S/W
B
Tb
Tc
Proposed schedule Reason
Remark
T0
Now
Ref : Activation Time
Must
Ta
T0+2 Y
12M after IPv4 exhaustion
Must
Tb
T0+4Y
Ref other country policy
Adjusted by
budget
Tc
T0+4Y
Ref other country policy
Adjusted by
budget 13
Policy defined, It is just the beginning
IPv6 is not “plug and play”
Standards/mandatory ?
Infrastructure readiness ?
Transit/peering ?
Addressing ?
Dual-stack/tunnelling ?
v6 Routing protocols?
Security?
Cost?
Think Post-Transition Strategy First
Transition
Strategy
AS IS
Internet
TO BE
Internet
Mutation
> 20 Years ?
Overlapping Period
Post Transition Management
TO BE
Internet
Mutation
The easiest solution : Turn off IPv6
15
Strategic Policy for IPv6 Deployment
1. Political Return
P1 policy
making
• Position statement for
IPv6 deployment
P2 Greater
participation
• RIR policy development
P3. Risk
management
P4. Economic
impact
2. Constituent Service
C1 increase
value
C2 reduce
• Training and awareness
• IPv6 product certification
• technology
cost
• Industrial innovative Act: Tax
Credit
• IPv4 exhaustion
C3 single POC
• IPv6 transition office
• Reduce risk of ISP/ICP
C4 service
availability
• Government network
dualstack
3 Operation Efficiency
• Government IPv6
deployment
O2 Policy Goal
• Business / service
continuity
O3
Government
responsibility
• complied with Telecom
Act
Feasibility
O1 service
transform
Technology
Operation
Economy
Legal
Policy Value Assessment
Current State
Intended State
Project
Component
Clear IPv6 Strategy
Position Statement
Political Return
Policy making
Greater participation
RIR participation
RIR participation
Crisis management
IPv4 exhaustion
Minimal impact
IPv6 Transition
Constituent value
Certification/tech transfer
IPv6 Tech Support Center
Lower constituent cost
Lower cost for ISPs
Industrial innovation act
Single point of contact
Single POC
IPv6 Transition Office
IPv4 only
IPv4/IP6 availability
GSN dualstack deployment
Service Transformation
Ad hoc
Best practice
Phased IPv6 transition plan
Policy objectives
Service availability
Sustained service availability
Secure IPv6 migration
Complied with Telecom Act
IPv6 transition plan
Constituent Service
Greater service availability
Operational Efficiency
Gov responsibility
17
IPv6 Policy Deliveries
+6 Million
v6 Users
6PIX
CapEx
OpEx
Procurement
Drive Innovation
18
Summary
• IPv4與IPv6共存將是漫長道路, 共存環境仍有
許多待修復與改善的地方
– 過去四十年來IPv4基礎建設必須重新部署、更新配置或
更新軟硬體、甚者部份軟體服務無法使用
– 努力維繫新舊技術並存的結果可能僅是強差人意的網
路品質
• 我們需要作什麼
–
–
–
–
學習面對這些問題
學習尋求解決方案
學習不厭其煩的檢驗網路環境
學習拒絕關閉IPv6的誘惑
19
簡報完畢，敬請指教。
20