インターネットにおけるIPv6の導入に関する考察 : IPv4からのプロトコルマイグレーションの実現(本文)

Transcription

1 2014 IPv6 IPv4

2 ( )

3 IPv6 IPv4 ARPANET (Advanced Research Projects Agency) 1980 IP(Internet Protocol) IP (Internet Protocol) IP IPv4 IP IP ICANN (Internet Corporation for Assigned Names and Numbers) IPv4 IP IPv4 IPv4 IPv IPv4 IPv i

4 IP 2 IPv6 2 IPv6 2 IPv6 IPv4,, IPv6 IPv4, ii

5 Deploying IPv6 into the Internet: How to achieve protocol migration from IPv4 Abstract The Internet was based on a network, named ARPANET (the Advanced Research Projects Agency Network). At the beginning of the Internet, only a few computers were connected. Currently, innumerable terminals are connected to the Internet all over the world. The Internet uses a unique protocol, IP (Internet Protocol), for communication. This protocol was introduced around 1980s. The fact that a single unique protocol has been used for almost quarter of a century is evidence of the excellency of its design. Today, the Internet is used all over the world, and its infrastructure is of critical importance. However, because of its expansion, issues have occurred. One of these relates to the limitations of its identifier, the IP address. IP addresses are analogous to telephone numbers in a telephone network, and every terminal needs a unique IP address when connecting to the Internet. The protocol version used from the beginning of the Internet is IPv4 (Internet Protocol version 4), and its addresses are 32 bits long. The total number of possible addresses is therefore only 4.3 billion, which is much smaller than the current world s population. In fact, in February 2011, the Internet Corporation for Assigned Names and Numbers, which manages Internet number resources, announced that they finished distributing their IPv4 address stock. An expanding routing-table is yet another problem with the current IPv4 version. Intermediate nodes in the Internet must store routing information (i.e., the routing table) to keep track of the locations of IP addresses. Because of the worldwide deployment of the Internet, the routing information has become massive, and it is increasing monotonically. As a result, the stability of the Internet is at risk. To resolve such problems, a new successive Internet protocol, IPv6 (the Internet Protocol version 6), has been standardized. IPv6 was used commercially during the late 1990s. However, despite the limitations to IPv4 addresses, IPv6 has not yet been deployed widely. iii

6 Until now, the Internet has been deployed with the following two aspects: protocol standardization and resource management. To further deploy IPv6, these two aspects must be considered simultaneously. In addition, to addressing these two aspects, it is important to consider some of the global aspects of the Internet, along with its situation at the regional and national level. This paper describes the deployment of IPv6 from the perspective of these two aspects, and discusses what is required in order to further deploy IPv6 from a global and regional perspective. Moreover, the paper describes the author s activities in the Internet s number-resource management community, with a focus on the intractable limitations to IPv4 addresses and the potential impact that implementing IPv6 will have on this community. Keywords: Internet development, Internet resource management, Address policy, IPv6, IPv4 Graduate School of Media Design, Keio University Tomohiro Fujisaki iv

7 IP IP IP AS AS ICANN RIR IETF ICANN IPv IPv IPv IPv v

8 3.2.1 IPv IPv IPv IPv IPv IPv IPv IPv IPv IPv IPv bone IPv IPv IPv IPv IPv IPv6/IPv IPv IPv IPv IPv IPv IPv6 Day IPv vi

9 5.4. IPv IPv IPv IPv IPv IPv6 IPv IPv IPv IPv IPv IPv ISP IPv IPv RIR IPv APNIC IPv IPv IPv IPv IPv IPv APNIC RIR IPv RIR IPv IPv IPv IPv vii

10 IPv APNIC IPv IPv APNIC IPv4 IPv APNIC IP A 130 A.1. ICANN ASO/AC A.1.1 ASO/AC A.1.2 ASO/AC A.1.3 ASO/AC A.2. IETF Nomcom A.2.1 IETF Nomcom IETF A A.3.1 prop A.3.2 prop A.3.3 prop A.3.4 prop A.3.5 prop A.3.6 prop A.3.7 prop A.3.8 RFC viii

11 ICANN APNIC IETF RFC IETF ALE WG (1994) IPv NTTv6Net IPv6/IPv ICMPv ICMPv IPv ISP IPv IPv RIR IPv /8 ( ) IPv Sparse allocation / ix

12 7.3 CONFER x

13 3.1 IPv4 ( ) IPv IPv IPv Sparse allocation xi

14 1 ARPANET (Advanced Research Projects Agency) 1980 IP(Internet Protocol) IP IP IPv4 (Internet Protocol Version 4) IP IP ICANN (Internet Corporation for Assigned Names and Numbers) IPv4 IP IPv4 1

15 IPv4 IPv6 (Internet Protocol Version 6) 1990 IPv4 IPv IP 2 IPv6 2 IPv6 2 IPv6 IPv4 2 IP 3 IPv4 IPv6 IPv6 4 IPv4 IPv6 5 IPv6 6 IPv

16 2 IPv4 IPv IPv6( 3 ) IPv6 IPv JPNIC 2008 APNIC ASO/AC(A.1) APNIC 3

17 ASO/AC APNIC APNIC IP IP Internet Protocol/ ) IP DEC DECnet[1] IBM SNA(Systems Network Architecture)[2] IP IP IP IP PC Web Web Web IP IP IP IP IP IP IP IP IP IP IP 4

18 IP IP IP IP IP IP IPv4 32 IPv6 128 IP IPv IPv4 / IPv6 64 ( /64) AS AS (AS: Autonomous System) AS AS AS AS BGP[3] BGP AS AS IP

19 2.3.1 ARPANET IETF (Internet Engineering Task Force) 1 IAB (Internet Architecture Board) 2 IAB ISOC (Internet Society) IP AS ICANN (Internet Corporation for Assigned Names and Numbers) 4 IANA (Internet Assigned Numbers Authority) 5 IANA IP AS (RIRs: Regional Internet Registries, 5 (

20 2.1 ARIN(American Registry for Internet Numbers) 6, RIPE- NCC(Réseaux IP Européens Network Coordination Centre) 7, APNIC(Asia Pacific Network Information Centre) 8, LACNIC (Latin American and Caribbean Internet Addresses Registry) 9, AfirNIC (African Network Information Center) 10 ) ) RIR ISP LIR (Local Internet Registry) NIR: National Internet Registry JPNIC (Japan Network Information Center) NIR ICANN ICANN ICANN [4]

21 (a) (b) IP AS (c) 2. DNS ICANN ICANN 16 5 ICANN NomCom: Nominating Committee 8 3 ICANN SO: Supporting Organization ASO: Address Supporting Organization GNSO: Generic Names Supporting Organization ccnso: Country Code Names Supporting Organization 2 6 At Large ALAC: At-Large Advisory Committee 8

22 1 ICANN CEO 1 5 RSSAC SSAC IETF TLG ITU-T W3C ICANN GAC: Governmental Advisory Committee ICANN IP AS RIR AS IANA RIR RIR RIR RIR RIR (Policy Development Process: PDP) 9

23 APNIC APNIC APNIC SIG Policy Working Group JPOPF (Japan Open Policy Forum) IAB IESG (Internet Engineering Steering Group) IETF, IRSG (Internet Research Steering Group), IRTF (Internet Research Task Force) IAB (Internet Architecture Board) IAB (big picture) IETF IAB IAB IETF IETF WG (Working Group) IAB IAB IAB IRTF IETF IESG IAB

24 IETF IESG IESG IAOC RFC Series Oversight Committee (RSOC), RFC IANA ISOC IETF IAB (NomCom) ISOC 2 IESG (Internet Engineering Steering Group) 12 IESG IETF IESG ISOC IESG IESG Steering Group IESG IETF / IETF / RFC IESG 8 Application Area, General Area, Internet Area, Operations and Management Area, Real-time Applications and Infrastructure Area, Routing Area, Security Area, Transport Area 2 AD AD 2 IRSG (Internet Research Steering Group) 13 IRSG IRTF IRTF IRSG IRTF IRTF IRTF

25 IESG IETF IAB IRSG IRTF IRSG IRTF [5] [6] IRTF (Internet Research Task Force) 14 IRTF IETF Internet Society (ISOC) ISOC IETF

26 2.4.1 RIR IP AS RIR PDP PDP APNIC APNIC Policy deployment process [7] 1(prop-001) APNIC face-to-face APNIC APOPM APNIC APNIC 3 APNIC SIG(Special Interested Group) face-to-face 13

27 4 APNIC SIG SIG face-toface APOPM APOPM APOPM SIG APNIC AMM AMM APNIC APOPM AMM APNIC AMM 4 8 APOPM SIG APNIC APNIC APNIC 3 APNIC

28 2.4 APNIC 15

29 2.4.2 IETF IETF RFC(Request for Comments) RFC Proposed Standard ( ) Standard ( ) Best Current Practice ( ) Informational ( ) Experimental ( ) Historic ( ) Proposed Standard RFC Standard RFC Standard Track RFC IETF IETF (Internet Drafts, IDs) 2.5 RFC 2.5 IETF RFC 16

30 IETF IETF 8 RFC 1. IETF IESG IESG IETF last call IETF 8. IESG IESG 9. RFC ICANN ICANN ICANN 17

31 ICANN ICANN 3 ICANN ICANN Web 15 ICANN ICANN RIR ICANN ASO ICANN IP /AS IP /AS ICANN IP /AS IP ICANN 2.5. APNIC IP APNIC (APOPM) RIR RIR

32 RIR RIR IANA ITU ISO 16 IP APNIC SIG APNIC NIR IP APNIC APOPM APNIC face-to-face APOPM APOPM NIR ( ) ISP LIR) APNIC RIR IETF [8] 19

33 NIR RIR 2 3 APNIC 17 IPv4 IPv6 IPv4 IPv6 IPv6 17 APNIC 20

34 3 IPv6 IPv IPv4 30 IPv4 IPv4 IPv IPv IPv4 32 4,294,967,296 IP 21

35 C /24, 256 B /16, 65,535 A (/8, 16,777,216 ) IPv4 [9] A B C Aggregation IETF ALE WG (Address Lifetime Expectations Working Group) IPv IPv4 IETF ALE WG IETF ALE WG (1994) 22

36 IPv4 IPv IPv IPv4 IANA RIR RIR ISP IANA IPv4 RIR /8 ( A ) 2 IANA APNIC 2 /8 5 /8 5 RIR 1990 IPv4 RIR RIR IPv4 RIR RIR IPv4 IPv4 IPv4 APNIC RIPE-NCC /8 (IPv =16, 777, 216 ) LACNIC, ARIN /10 (IPv =4, 194, 304 ) IPv4 APNIC, RIPE-NCC, LACNIC IPv4 IPv RIR IPv RIR IPv4 /8 23

37 3.1 IPv4 ( ) RIR (/8 ) APNIC / RIPE-NCC / LACNIC / ARIN / AfirNIC IPv IPv4 IPv4 IPv4 1 JPNIC (Japan Network Information Center) 2 IPv4 3 3 [10] 1. IPv4 IPv4 IPv4 ISP IPv4 NAT NAT 1 IPv6, sosiki/joho tsusin/policyreports/chousa/ipv6 internet/

38 2. IPv4 IPv4 IPv4 IPv4 IPv4 IPv4 IPv4 IPv4 IPv4 IPv4 Class E 3. IPv6 IPv4 IPv6 IPv4 IPv6 IPv4 IPv6 IPv4 IPv IPv6 IPv6 IPv4 IAB IPv IPv IETF 25

39 IPv6 [11] 1995 IPv6 6bone 4 IPv6 6bone RFC2471[12] IPv6 IPv IPv6 IPv IPv IPv IPv6 IPv6 OS PC OS OS IPv6 OS IPv

40 IPv4 IPv6 IPv6 IPv6 IPv6 Verizon IPv6 KDDI, NTT Docomo IPv6 Google, Facebook IPv6 IPv IPv6 IPv6 IPv4 IPv4 IPv6 1. OSI 3 4 TCP, UDP 2. 2 IPv6 3 IPv6 86dd IPv6 27

41 3. IPv6 4. IPv4 IPv6 IPv4 IPv6 IPv4 IPv6 5. IPv4 IPv6 FQDN(Fully Qualified Domain Name) IPv4 IPv IPv6 IPv4 IPv6 IAB IETF, RIR IPv6 IPv6 IPv4 IPv6 IPv IETF IPv6 IPv4 IPv6 IPv4 IPv6 IETF 2008 IPv6 IPv4 IPv6 28

42 3.2 IPv6 IPv4 IPv6 IPv4 IPv6 IPv6 IPv6 29

43 4 IPv IP IP AS 30

44 2.3.2 IP AS ICANN 5 RIR IPv IP 2000 IPv4 IETF RFC2050[13] RFC2050 RFC7020[14] RFC2050 IP RIR IPv4 RFC2050 /21 ( ) IPv4 / APNIC / IPv6 RFC2050 IPv4 IPv4 IPv4 RIR 31

45 IPv6 IPv6, 6bone IETF /35 IPv / /48 8, /32 65,536 [15] IP IPv6 RIR RIR IPv IPv IPv6 IPv6 32

46 4.2. IPv CIDR (Classless Inter Domain Routing) IPv4 IPv4 IPv4 A 2 24 =16, 777, 216, B( 2 16 =65, 536 ) C ( 2 8 = 256 ) 3 1. C B 2. IPv4 Variable Length Subnet Mask: VLSM CIDR CIDR IPv4 33

47 VLSM CIDR IPv4 CIDR VLSM proxy ARP[16] flag day

48 CIDR VLSM AS 32 AS(Autonomous System) 16 AS 32 AS BGP4 [17] 32 AS 32 AS 16 AS 32 AS IANA 16 AS 32 AS 16 AS 16 AS 32 AS 16 AS 32 AS ISP BGP4 32 AS BGP 35

49 flag day Transit ISP AS Transit ISP BGP 32 AS Transit ISP 32 AS AS 32 AS

50 1953 VHF(1-12ch) UHF(13-62ch) UHF(13-52ch) TV CATV CATV ( [18]) CATV 37

51 CATV flag day 1972 [19] ( 730 [20]) 38

52 flag day (flag day)

53 flag day 40

54 4.2.4 IPv6 3 IPv4 IPv6 IPv6 IPv6, 41

55 5 IPv6 IPv4 IPv6 1. IPv6 2. IPv6 3. IPv IPv6 IPv4 IPv6 IPv6 6bone 6bone IPv bone IPv6 NTT

56 6bone IPv6 IPv6 NTTv6Net [21] NTTv6Net NTTv6Net NXPIXP6 PAIX/6TAP AMS-IX Internet Exchange (IX) IPv6 IX IPv IETF NTTv6Net IETF IPv6 [22] IPv6 IPv6 IPv6 [23] IPv6. Global IPv6 Service Launch NTTv6Net

57 5.2. IPv6 IPv4 IPv IPv6 NTT 1999 IPv IPv6 6bone 6bone NTT NTT ISP IPv6 NTT IPv IPv6 IPv6 IPv4 IPv IPv6 NTT IETF history.html 44

58 APNIC IPv6 IPv6 ( ) ISP IPv4 IPv6 IPv6 IPv6 ISP IPv6 IPv6 IPv6 ISP IPv6 IPv6 IPv6 IPv6 IPv6 5.2 ISP ISP IPv6 IPv6 IPv6 ISP ISP ISP 45

59 5.2 [24] ISP ISP IPv6 IPv6 RFC6724[25]. RFC RFC IPv6 IP IETF IPv6 Default Address Selection Policy Option DHCPv6 IPv6 DHCP-PD 46

60 DNS DHCPv6 RFC ISP IPv6 IPv6 5.4 [26] 47

61 5.4 IP IPv4 IPv4 HGW) NAT IPv IPv DHCP IETF DHC WG (Dynamic Host Configuration WG) DHCPv6 [27] IETF RFC6724 ( RFC3484) [28] IPv6 IPv6 48

62 6man WG (IPv6 Maintenance WG) ( ipv6 WG) v6ops WG (IPv6 Operations WG) [29] v6ops WG WG [30] [31] [32], [33] RFC DHCP 6man WG DHCPv6 [34] IPv6/IPv IETF IPv6/IPv IPv6 P2P IPv6 IPv6 IPv6 IPv6 IPv6 IPv6/IPv4 IPv6 IPv4 IPv6 IPv4 IPv6 IPv4 49

63 IPv6 IPv4 FQDN Fully Qualified Domain Name IPv6 IPv4 FQDN IPv6 IPv4 DNS FQDN IP IPv6 AAAA IPv4 A IPv4 IPv6 IPv6 RFC IPv6 IPv4 IPv6/IPv4 IPv6 IPv6 IPv4 IPv6 IPv4 IPv6 IPv4 IPv6 IPv4 [35] 5.5 IPv6/IPv4 50

64 IPv6/IPv4 IPv6/IPv4 IPv6 IPv6 IPv6/IPv4 6to4[4] IPv6 IPv6 AAAA DNS IPv6 IPv6 VPN IPv6 IPv4 Web Web 20 IP ICMP Internet Control Message Protocol IPv6 ICMPv6[36] 5.6 IPv6 5.6 ICMPv6 51

65 TCP ICMP RFC1122[37] RFC ICMP TCP TCP IPv4 ICMP ICMPv4 ICMPv6 TCP OS, ICMPv6 IPv6/IPv4 PC IPv6/IPv4 Web PC IPv6 PC IPv6 IPv4 0 6 ICMPv6 TCP Reset PC IPv6 TCP SYN IPv4 TCP SYN ( ) 5.7 ICMPv6 52

66 5.7 ICMPv6 WIDE IPv6 fix 3 TCP ICMPv6 IETF [38] APRICOT [39][40] IETF IETF Transport Area Area Director RFC5461[41] Acknowledgments IPv4/IPv6 Happy Eyeballs[42] IPv IPv IPv6 IPv6 WG SWG (Sub-Working Group) ISP [43] [44] IPv

67 2007 IPv6 ISP IPv6 IPv6 IPv6 IPv4/IPv6 WG IPv6 SWG 4 SWG SWG IPv6 (TR-124) IPv6 IPv6 Ready Logo 5 CPE(Customer Premises Equipment ) SWG IPv [45] IPv [46] IPv6 2 TR-124i [47] IPv6 Home Router Guideline ( Ver.1.0 June ) [48] IPv6 Home Router Guideline ( Ver.2.0 July / Translated January )[49] IPv

68 2007 IPv6 IPv4 IPv IPv6/IPv4 IPv6 IPv4 IPv6 IPv6 fix WIDE IPv6 IPv6 IPv6 IPv4/IPv6 WG IPv6 SWG 6 SWG SWG IPv6 [50] IPv6 30 IPv6 IPv6 [51] Web, DNS IPv6 ISP IPv6 WG IPv6 Day IPv6 WG [52] SWG IPv IPv

69 2007 IPv6 ISP IPv6 IPv6 IPv6 IPv4/IPv6 WG IPv6 IPv6 SWG 7 SWG SWG IPv6 IPv6 1.0 [53] BSD Socket IPv6 IP Asterisk IPv6 IPv6 Web IPv IPv IPv6 IPv6 IPv6 IPv6 WG WG IPv6 SP [54]

70 IPv6 WG IPv6 1.0 [55] IPv6 WG IPv6 Security List of Considerations 6SLoC Ver1.0-cfc [56] IPv6 APRICOT IPv6 Security Device BoF [57] IPv6 Day 2011 IPv6 IPv IPv6 IPv6 Day 8 Internet Society (ISOC) ISOC Web IPv6 IPv6 Day IPv6 Day ISOC IPv6 Day IPv IPv IPv w6d.html 57

71 IPv6 OSC IPv4 IPv6 [58][59] Asia Pacific IPv6 Task Force IPv6 [60][61] IPv6 Summit in Taiwan IPv6 [62][63] APNIC IPv6 Readiness Measurement BoF IPv6 [64] [65] IPv6 Day in Vietnam IPv6 [66][67] IPv6 Summit (1999 ) 10 IPv6 (2003 ) 11 Internet Week IPv6 (2009 ) IPv6 IPv6 IPv6 VPN

72

73 6 IPv6 IPv4 IPv6 1. IPv6 2. IPv6 IPv4 IPv IPv6 IPv4 IPv6 IPv6 IPv IPv6 RIR

74 5.1.1 IETF Rough consensus and running code IPv6 IPv6 6bone 6bone RFC2374[68] IETF RFC2471[12] ISP 6bone IPv6 IPv6 (Provisional IPv6 assignment and allocation policy) [15] RIR IPv6 WIDE IPv IPv IPv6 Provisional IPv6 assignment and allocation policy document IPv4 IPv6 IPv4 slow start IPv4 ( IP 80% ) IPv6 61

75 APNIC ARIN,RIPE-NCC RIR IP JPNIC IPv6 policy drafting team IPv6 RIR IPv6 address allocation and assignment policy IPv6 IPv6 TLA, NLA [69] /35 /32 /35 /32 80% HD [70] 62

76 [71] IPv6 RIR 2015 RIR IPv6 IPv6 APNIC IPv6 RIR IPv6 APNIC IPv6 IPv6 [72] APNIC IPv6 IPv6 IPv6 63

77 2 IPv IPv6 APNIC IPv RIR 2002 /32 /32 APNIC APNIC [73] IPv6 /32 /32 IPv4 IPv4 IPv6 2 IPv4 IPv6 64

78 / IPv IPv4 IPv6 IPv4 /32 IPv6 IPv6 IPv6 IPv6 IPv IPv6 IPv APNIC [74]

79 IPv6 ISP APNIC IPv6 ( ) APNIC IPv6 240f::/24 JP ::/20 KR :180::/28 KR :4000::/22 JP e::/24 CN e::/20 CN d::/27 JP :e40::/29 JP :fb0::/31 TH ::/22 KR :800::/20 CN APNIC (

80 6.1.6 IPv IPv6 IPv4 IPv6 IPv6 ISP IPv4 ISP Shim6[75] Shim6 1 IPv IPv6 IPv APNIC [76] Shim6 67

81 IPv6 PI IPv IPv [77] IPv6 IPv6 IoT(Internet of Things: ) IoT IPv6 IPv6 IPv4 IoT IPv4 IPv6 [77] APNIC 68

82 6.1.7 IPv IPv4 IANA RIR IPv4 IPv4 RIR IPv4 5 9 [78] IANA RIR /8 2 RIR IPv4 RIR JPNIC IPv4 countdown policy team RIR JPNIC IANA IPv4 /8 5 RIR /8 IANA RIR IPv4 /8 69

83 APNIC [79] IANA RIR RIR ICANN IANA [80] APNIC /8 [81] IPv4 / IANA APNIC 2 /8 IANA / RIR /8 IANA IPv APNIC /8 APNIC /8 IPv IPv6 IPv6 IPv4 IPv ISP IPv

84 ポリシ策定の背景 IPv4 アドレス在庫の不足が進行し 対応のため 少数の IPv4 アドレスを複数 のユーザで利用する IPv4 アドレス共有技術の導入が ISP 等で検討され始めた ポリシ策定の経緯 内容 IPv4 アドレス共有技術を導入する場合 共有される IPv4 アドレスはインター ネット中でユニークである必要があるが ユーザに割り当てられるアドレスは 同 じ IPv4 アドレスを共有するユーザ間で重ならなければよいため ISP 間で同じア ドレス空間 共有 IPv4 空間 が使用可能である 図 6.2 に共有 IPv4 空間のイメー ジを示す APNIC25 Policy SIG 発表資料 より抜粋 図 6.2 ISP 共有 IPv4 アドレス空間 図 6.2 の User と LIR 間の IPv4 アドレス空間 図中 Shared /8 は 各 ISP 間 71

85 RIR APNIC [82] APNIC IETF RFC IETF [83] IETF RFC [84] ARIN IPv / IPv4 APNIC IPv4 (LIR) / IP IP RIR IPv4 IPv4 IPv4 APNIC IPv4 72

86 IPv4 APNIC RIR IPv4 RIR IP IPv4 RIR APNIC APNIC IPv4 APNIC IPv4 / 12 APNIC IPv4 /8 APNIC APNIC APNIC IPv4 IPv4 APNIC IPv4 73

87 APNIC IPv4 APNIC APNIC IPv4 APNIC APNIC 2011 RIR ( ) NIR TWNIC KRNIC IPv4 CNNIC VNNIC IPv4 APNIC JPNIC,IRINN IDNIC RIR IPv APNIC RIR

88 AfriNIC IPv4 IPv4 6.3 IPv4 /8 IPv IPv4 6.3 ARIN IPv4 RIR 2 APNIC 75

89 [85] 6.4 RIR 6.4 RIR RIR ( ) IPv4 24 IPv

90 APNIC APNIC ARIN APNIC RIR IPv4 IPv APNIC IPv4 APNIC IPv4 IPv4 APNIC IPv4 RIR RIR ARIN RIR RIR ARIN IPv4 ARIN ARIN IPv4 APNIC APNIC ARIN 77

91 APNIC APNIC APNIC [86] IPv4 RIR APNIC ARIN IPv4 6.5 APNIC 6.5 IPv4 APNIC38 APNIC ( pptx) APNIC IPv4 RIR ARIN 6.5 Inter-RIR ARIN IPv4 ARIN 118 (55%) (13%) (8%) APNIC

92 RIPE-NCC IPv IPv IPv6 IPv [87] APNIC IPv6 ISP IPv6 IPv IPv

93 IPv4 IPv4 RIR IPv4 RIR IANA RIR IANA IANA IPv4 RIR 2012 [88][89] 5 RIR IPv4 / RIR LACNIC IPv4 /9 [90] IANA IPv APNIC IANA IANA IPv4 [91] APNIC IPv4 / /8 IPv4 IPv4 103/8 IPv4 /22 IPv4 APNIC /8 APNIC IPv4 / [92] /8 6.6 / / IPv4 IANA IANA RIR IPv4 RIR 80

94 APNIC 6.6 /8 ( ) IPv IPv APNIC [93] IPv4 IPv4 Recovered Pool IPv4 IPv4 IPv IPv6 81

95 6.7 IPv4 APNIC38 APNIC ( pptx) 2010 IPv6 IETF IPv4 IPv6 6rd[94] IPv6 /32 6rd IPv4 IPv6 /32 6rd IPv6 [95] IETF RFC 82

96 APNIC IPv6 [96] APNIC [95] IPv APNIC IANA IPv6 IPv6 /32 / IPv6 sparse allocation 6.8 APNIC sparse allocation Sparse allocation 83

97 Sparse allocation 2006 APNIC IANA sparse allocation sparse allocation /32 / [97] sparse allocation / APNIC IPv6 IPv4 IPv6 RIR IPv4 APNIC ARIN IPv4 APNIC ARIN RIR IPv4 APNIC IPv4 IPv4 84

98 6.4. IPv6 IPv4 IPv IPv4 IPv6 IPv4 IPv6 IPv4 IPv4/IPv6 IPv6 IPv6 IPv4 flag day World IPv6 Day ( ) World IPv6 Launch ( ) PC IPv6 ISP IPv6 IPv6 ISP ISP IPv6 ISP IPv4 IPv6 85

99 ISOC RIR IPv6 IPv6 IPv4 IPv6 IETF flag day IPv6 IPv4 2 IPv4 IPv6 IPv6 IPv4/IPv6 IPv4 IPv6 IPv4 IPv6 IPv6 IPv4 IPv

100 6.2 IPv6 1 IPv4 2 IPv6 3 IPv6 4 IPv6 IPv4 IPv4 IPv6 IPv6 IPv6 87

101 7 6 APNIC IPv4 IPv6 APNIC IP 7.1. APNIC APNIC APNIC APNIC APOPM 4. APNIC AMM APNIC 88

102 7. 1. APNIC (APOPM) 2. APOPM 3. APOPM 2 APOPM 1. APOPM 2. APNIC (AMM) AMM APNIC 3. SIG 4. APNIC 1 APOPM APOPM 2001 APNIC11 APOPM APOPM 1. APNIC 89

103 APOPM APNIC (NIR) APOPM NIR NIR NIR APOPM IP ISP LIR NIR APOPM NIR 4. 1 APNIC Transcript APNIC APNIC ( 7.4 ) 90

104 7.2. RIR IPv RIR IPv4 IPv6 IPv4 IPv6 IPv4 IPv4 IPv4 IPv4 IPv4 IPv4 IPv4 RIR RIR 7.1 IPv RIR RIPE-NCC ARIN APNIC LACNIC AfriNIC RIR IPv4 ARIN ARIN IPv4 RIR 2011 ARIN [98] ARIN RIR IPv4 IPv4 APNIC RIR APNIC IPv4 91

105 ( ) APNIC IPv4 APNIC APNIC IPv4 IPv4 ARIN IPv4 APNIC ARIN ARIN APNIC RIR IPv4 ARIN RIR IPv4 IPv4 RIR IPv4 1. RIR IPv4 ( ) APNIC RIR RIR IPv4 2. APNIC ( ) APNIC IPv APNIC31 APOPM IPv ARIN IPv4 1 2 APOPM ARIN ARIN RIR 92

106 AP- NIC IPv4 ( ) Geoff Huston IPv4 RIR RIR Geoff ARIN IPv4 APNIC APNIC APNIC APNIC32 APOPM APNIC32 APOPM APNIC 7.3. IPv APNIC 2011 /8 IPv4 ISP LIR IPv4 /8 IPv4 IPv4 93

107 /8 IPv4 RIR ARIN APNIC IPv IPv4 IPv JPNIC JPOPM22 (22nd JPNIC Open Policy Meeting) IPv4 /8 IANA [89] /8 IPv4 IPv4 /8 /24 IPv4 APNIC (1/1 6/1) JPOPM22 APNIC IPv4 APNIC APOPM 94

108 APOPM, JPNIC IPv4 (7/30 411) 61 (15%) 1. /8 IPv4 / IPv / 4. IPv4 IPv6 IPv6 / / IPv6? 5. /8 IPv4 IPv6 APNIC 1. /8 67%, 33% IPv6. IPv6 59%, 47% 95

109 2. IPv % IPv6 4. : / % / APNIC34 APOPM APNIC /8 /22 APNIC APNIC APNIC APNIC APNIC LIR, JPNIC LIR 89 (56 LIR) 61 LIR APNIC 1. /8 70%, 30% IPv6. IPv6 75%, 53% 96

110 2. IPv % IPv6 4. : /22 ( 7.1) % / APNIC38 APNIC 7.2 / /22 97

111 7.2 / APNIC 7.4. IPv APNIC IPv ( ) IPv6 /32 / sparse allocation sparse allocation 98

112 7.3 Sparse allocation 2001:cd0:: allocated 2001:cd1:: 32 available 2001:cd2:: 31 available 2001:cd4:: 30 available 2001:cd8:: allocated 2001:cd9:: 32 available 2001:cda:: 31 available 2001:cdc:: 30 available 2001:ce0:: allocated 2001:ce1:: 32 available 2001:ce2:: 31 available 2001:ce4:: 30 available 2001:ce8:: allocated 2001:ce9:: 32 available 2001:cea:: 31 available 2001:cec:: 30 available APNIC, allocated ISP 2001:cd0::/ :cd1::/32, 2001:cd2::/31, 2001:cd4::/

113 sparse allocation IPv / IPv /32 /29 IPv6 sparse allocation APNIC [97] 1. IPv6 [71] IPv6 /32 /29 (/32 /29 ) 2006 sparse allocation /23 /32 / sparse allocation IANA /12 sparse allocation APNIC APNIC guidelines for IPv6 allocation and assignment requests [99] 100

114 / /12 Sparse allocation /32 /24 /32 (/35 ) /32 [100][101] ISP /32 /32 /29 /32, /31, /30 2. IPv6 /29 /32 /29 3. RIPE-NCC ISP /29 4. IPv6 /32 /29 IPv6 IPv6 /29 5. IPv6 101

115 /32 IPv6 6. /29 IPv6 IP IPv6 /29 /28 1 APNIC APNIC HD [102][103] IPv6 /32 ISP 2. IPv6 /29 /32 /29 102

116 3. IPv6 /32 /29 IPv6 IPv6 / APNIC APNIC APNIC APNIC 7.5. APNIC APNIC IPv4 IPv6 6 APNIC IPv6 IPv6 IPv6 3 IPv4 1 APNIC IPv6 IPv6 103

117 IPv6 IPv6 IPv6 IPv4 IPv IPv6 IPv6 IPv6 3 IPv4 4 AS 1 [104] IPv6 IPv6 IPv6 IPv APOPM SIG APNIC38 APOPM CONFER CONFER web CONFER 7.3 SIG 104

118 7.3 CONFER APNIC38 APOPM APOPM CONFER CONFER CONFER 105

119 CONFER 7.7. APNIC RIR APNIC APNIC APOPM NIR 106

120 APNIC APNIC APNIC 107

121 8 IPv4 IPv6 3 IPv4 IPv6 IPv4 IPv6 IPv4 IPv6 IPv4 IPv6 IPv4 IPv6 108

122 8.1. IPv4 IPv6 IP IP IPv4/IPv6, IPv6 ) IP IPv6/IPv4 IPv4/IPv6 IPv6 1 IP VPN IPv6 IETF 2 IPv4/IPv6 IPv6 IPv6 IPv6/IPv4 109

123 IPv6 IPv6 IPv6 IPv6 IPv6 IPv6 IPv4 IPv6 5 (RIR) APNIC RIR RIR RIR APNIC IPv4 IPv4 IANA IPv4 IPv4 IANA / RIR /8 RIR /8 IPv4 IPv4 IPv4 RIR IPv4 APNIC IPv4 RIR RIR RIR APNIC 110

124 APNIC IPv4 ARIN IPv4 ARIN APNIC IPv4 IANA IPv4 IPv4 IPv4 APNIC IPv6 IPv6 IPv6 IPv6 IPv6 IPv6 IPv6 IPv6 IPv6 IPv6 IPv6 IPv6 IPv6 AS 111

125 IPv RIR /8 APNIC /8 IPv4 IANA RIR IPv4 IPv4 RIR IPv4 IPv4 RIR IPv4 APNIC IPv4 ARIN IPv4 ARIN RIR (55%) (13%) (8%) APNIC IPv4 IPv IPv ,

126 APNIC IPv4 IPv6 IPv6 IPv6 ISP IPv6 IPv4 IPv IPv4 IPv6 IPv6 AS AS IPv4 IPv6 IPv6 113

127 IoT(Internet of Things: ) IPv6 IPv6 IPv APNIC APNIC APNIC APNIC RIR RIR IANA ITU ISO IP APNIC SIG APNIC 114

128 NIR IP face-to-face APNIC (APOPM) APOPM APOPM NIR NIR NIR ( ) ISP LIR) APNIC APNIC RIR APNIC IPv4 IPv6 APOPM APOPM 115

129 APNIC RIR IP IP IP RIR IPv4 116

130 APOPM IPv4 APNIC NIR TWNIC KRNIC IPv4 ARIN RIR APNIC IPv4 NIR IPv4 ISP APOPM IPv6 APNIC 117

131 APNIC APNIC IPv4 IPv6 RIPE-NCC Transcript APNIC 118

132 NIR 8.3. IP ARPANET TCP/IP IP 32 IP 64 IPv4 IPv6 WWW(World Wide Web) 119

133 ITU ISO ISP IPv4 IPv6 IPv4 IPv4 IPv6 IPv IPv6 IPv6 IPv4 IPv4/IPv6 IPv6 Google IPv6 IPv4 5% IPv6 LAN IPv6 120

134 IETF APNIC Randy Bush Geoff Huston 121

135 APNIC JPNIC APNIC Sanjaya Guangliang Pan 122

136 IETF IETF prop-021: Expansion of the initial allocation space for existing IPv6 address space holders[74] APNIC prop-082: Removing aggregation criteria for IPv6 initial allocations[87] APNIC prop-087: IPv6 address allocation for deployment purposes[95] APNIC prop-095: Inter-RIR IPv4 address transfer proposal[85] APNIC 123

137 prop-096: Maintaining demonstrated needs requirement in transfer policy after the final /8 phase[86] APNIC prop-105: Distribution of returned IPv4 address blocks (Modification of prop-088)[93] APNIC prop-107: AS number transfer policy proposal[104] APNIC prop-111: Request-based expansion of IPv6 default allocation size[97] APNIC RFC7078: Distributing Address Selection Policy Using DHCPv6[34] IETF 6man WG WG WG Internet-draft: TCP Reaction to ICMPv6 Error Messages[38] ML IETF 124

138 IPv6/IPv4 [44] IPv6 [22] IPv6 [23] IPv4 IPv6 [26] IPv6 Summit 2006 Clear and Present Danger of IPv6 - IPv6/IPv4 fallback and DNS queries [39] APRICOT 2014 IPv6 Security activities in Japan [57] APNIC 32 World IPv6 Day in Japan [60] APNIC 34 Economy update Japan [61] IPv6 Summit in TAIWAN 2013 Japan IPv6 Measurement [62] IPv6 Summit in TAIWAN 2013 Japan IPv6 deployment status [63] APNIC 36 JP IPv6 Measurement [64] 125

139 APNIC 37 Japan IPv6 Measurement [65] IPv6 Event in Vietnam IPv6 deployment in Japan [66] VIETNAM IPV6 DAY 2014 Updates on IPv6 deployment in Japan [67] OSC 2011 IPv4 IPv4 [58] OSC 2011 IPv4 IPv4 [59] ASO/AC APNIC 27 ASO AC Report [105] APNIC 29 ASO AC Report [106] APNIC 30 ASO AC Report [107] APNIC 31 ASO AC Report [108] APNIC 32 ASO AC Report [109] APNIC 33 ASO AC Report [110] APNIC 34 ASO AC Report [111] APNIC 35 ASO AC Report [112] 126

140 APNIC 36 ASO AC Report [113] APNIC 37 ASO AC Report [114] IPv6 address allocation and assignment policy[71] RIR prop-035: IPv6 portable assignment for multihoming[76] prop-055: Global policy for the allocation of the remaining IPv4 address space[79], prop-106: Restricting excessive IPv4 address transfers under the final /8 block[115] RFC, RFC5220: Problem Statement for Default Address Selection in Multi-Prefix Environments: Operational Issues of RFC 3484 Default Rules[32] RFC5221: Requirements for Address Selection Mechanisms[33] 127

141 NTT - NTT IPv6 (NTTv6net) [21] IPv6 IPv6 WG IPv6 [43] WG IPv [45] WG ( ) IPv [46] WG ( ) IPv6 2 TR-124i [47] WG ( ) IPv6 Home Router Guideline ( Ver.1.0 June ) [48] WG ( ) IPv6 Home Router Guideline ( Ver.2.0 July / Translated January )[49] WG IPv6 WG IPv6 [50] WG ( ) 128

142 IPv6 [51] WG ( ) IPv6 WG IPv6 1.0 [53] WG ( ) IPv6 WG IPv6 1.0 [55] WG ( ) IPv6 WG IPv6 Security List of Considerations 6SLoC Ver1.0-cfc [56] WG ( ) NTT IPv6 Deployment Issues[52] APRICOT 2011 Operational Problems in IPv6: Fallback Issues [40]. 129

143 A A.1. ICANN ASO/AC , APNIC ICANN ASO/AC ASO/AC A.1.1 ASO/AC ASO ICANN ICANN 3 SO Supporting Organization IP AS ASO Address Supporting Organization ASO 15 ASO/AC ASO Address Council ASO/AC IANA RIR RIR ICANN RIR RIR,ICANN. ICANN

144 ICANN A.1.2 ASO/AC ASO/AC RIR 2 RIR APNIC 2012.APNIC ASO/AC 2 1 A.1.3 ASO/AC ASO/AC IPv4 RIR [80] IANA IPv4 [89] AS [116] RIR ICANN ICANN AS ICANN [117] ASO ICANN ICANN ASO ICANN ASO Workshop 3 ICANN ASO/AC ITU IPv4 131

145 APNIC 2 APNIC APNIC ASO/AC [105][106][107][108][109][110][111][112][113][114]. 132

146 A.2. IETF Nomcom A.2.1 IETF Nomcom IETF 2.3 IAB, IAOC, IESG IETF IETF Nomcom IETF 1 IAB 5 IAOC 1 IESG Oct 2013 Deadline for nominations, call for feedback 25 Oct 2013 Deadline for questionnaires 03 Nov 2013 In-person interviews (thru 08 Nov) 11 Nov 2013 Online interviews (thru 20 Nov) 20 Nov 2013 End of feedback period Early Feb 2014 Announcement of IAOC, IESG selections Mid-Feb 2014 Announcement of IAB slate IETF

147 A.3. A.3.1 prop-021 prop-021 Exapnsion of the initial allocation space for existing IPv6 address space holders IPv6 IPv6 IPv4 IPv6 IPv4 /32 IPv6 IPv6 IPv6 IPv6 IPv APNIC APNIC 9 APNIC prop-021-v001: Expansion of the initial allocation space for existing IPv6 address space holders Proposed by: Tomohiro Fujisaki, Nippon Telegraph and Telephone Corporation/JPNIC Policy WG Chair <fujisaki@syce.net> Version: 1.0 Date: 4 August 2004 Introduction: I propose making it possible for existing IPv6 address holders with the initial allocation address space to expand their address space without clearing the subsequent allocation requirement. This proposal has reached a consensus at JPNIC Open Policy Meeting. Summary of the current problem: In the past, many of the organizations had requested for the minimum 134

148 allocation size(/32) as an initial allocation due to the following reasons: + Based on the idea of the "slow start" in IPv4 policy, many organizations believed it would be difficult to justify all of their address requirements at an initial allocation. + It was difficult to estimate their needs as IPv6 network was not commercially developed. Many organizations requested for address space for a test service in order to kick off the commercial service, not for the commercial service itself. + PROVISIONAL IPv6 ASSIGNMENT AND ALLOCATION POLICY DOCUMENT specified the initial allocation size as /35. LIRs which received allocations under this policy were only allowed an upgrade of their allocations to a /32. In recent days, most of the ISPs learned that /32 space is too small for the real scale service deployment if they cover their existing IPv4 users. Organizations currently requesting for initial allocations can simply request for a larger space as the RIRs actively emphasize to their communities that they are able to request for allocations greater than /32, which is already a common practice. However, ISPs with the default address space need to design the IPv6 service network within the small space untill they clear the subsequent allocation requirement (HD-Ratio) for more address space. This makes the real IPv6 service deployment difficult, especially for large ISPs. Situation in other RIRs: none. Details of your proposal: Existing IPv6 initial allocation address holders should be able to expand their address space without satisfying subsequent allocation criteria if they are able to demonstrate their concrete plan. The same criteria should apply as organizations requesting for an initial allocation larger than /32. This proposal does not intend to change the current policy but to apply the current allocation practice to existing IPv6 address holders. If it is possible to expand the address space under the current policy, it is desirable to be documented clearly (e.g. in the guidelines document). Advantages and disadvantages of adopting the proposed policy: 135

149 Advantages: Existing IPv6 address holders will be possible to start their services under up-to-date situation. Disadvantages: none Effect on APNIC members: The expanded address space would be considered in the assessment of the APNIC membership tier of the organization, on the renewal of their membership. Effect on NIRs: NIRs providing IPv6 address allocation service should apply the same policy. A.3.2 prop-035 prop-035 IPv6 portable assignment for multihoming IPv6 IPv6 IPv APNIC 9 APNIC APNIC prop-035-v002: IPv6 portable assignment for multihoming Authors: Katsuyasu Toyama Takashi Arano Tomohiro Fujisaki Toshinori Ishii Kosuke Ito Dai Nishino, Noriaktsu Ohishi Izumi Okutani Version: 2 Date: 6 September

150 SIG: Policy Introduction This policy allows end-sites to be assigned IPv6 portable addresses only if the end-sites are multihomed, or plan to be multihomed. Summary of the current problem The current policy does not allow IPv6 portable assignment to any end-sites. This obstructs end-site organizations which need redundancy in internet connectivity for stable network operation. Shim6, another multihoming technology discussed in IETF, is not a perfect replacement of the current multihoming technology using BGP due to traffic engineering. In addition, it will take time to standardize and implement Shim6. Situation in other RIRs ARIN has been discussing the IPv6 Provider-independent address. The draft was proposed in 2005 and moved to the last call after the meeting consensus in April RIPE started PI discussion at RIPE in this May. AFRINIC and LACNIC discussed similar proposals recently in their Open Policy meetings. In those regions, the issue has been returned to their public mailing lists for further discussion. Note: APNIC uses the term "portable" rather than "provider-independent" (PI). Details (1) Assignment target: End-sites which are multihomed or plan to be multihomed, regardless of their size. (2) Assignment criteria: (2-a) The end site which is assigned IPv6 portable address space must be multihomed using the assigned portable address space in three (3) months. (2-b) If the portable address space is not used for multihoming after three (3) months, the address space should be reclaimed. 137

151 (2-c) The end site which is assigned IPv6 portable address space pays the normal APNIC fee for the space. (3) Portable address space: (3-a) The portable assignment should be made from a specified block separate from address space used for portable allocations (3-b) The portable assignment size to an end-site should be a /48, or a shorter prefix if the end-site can justify it. Pros/Cons Advantages: (1) Provides the solution for end-sites which require redundancy in IPv6 and currently not able to do so due to the lack of technical solutions. (2) Assignment of the portable address space is limited only to multihoming purposes ; only end-sites which are or planned to be multihomed can be assigned a portable address. This reduces the consumption of portable address space as well as the growth of the global routing table. (3) Portable assigned address space is separate from portable allocated address space, therefore: Disadvantages: (3-1) It helps preventing punching holes in the portable allocated address space because prefixes which are longer than /32 can be filtered in portable allocated space. (3-2) it is relatively easy to abandon the portable assigned address space in case some better techinical solutions are developed in the future. It may lead to growth in the global routing table, but we think the growth is almost the same in case that providers and end-sites start using punching holes for multihoming. Effect on APNIC No direct effect on the existing APNIC members, nor changes to the current IPv6 allocation criteria. Effect on NIRs

152 NIR can adopt this policy at its discretion. A.3.3 prop-055 prop-055 Global policy for the allocation of the remaining IPv4 address space IANA IPv4 IPv4 IANA IPv4 /8 5 RIR /8 IANA APNIC 8 APNIC APNIC RIR ICANN prop-055-v002: Global policy for the allocation of the remaining IPv4 address space Authors: Roque Gagliano, ANTEL Francisco Obispo, CENIT Haitham EL Nakhal, MCIT Didier Allain Kla, ISOC Cote d Ivoire JPNIC IPv4 countdown policy team - Akinori Maemura - Akira Nakagawa - Izumi Okutani - Kosuke Ito - Kuniaki Kondo - Shuji Nakamura - Susumu Sato - Takashi Arano - Tomohiro Fujisaki - Tomoya Yoshida - Toshiyuki Hosaka Version: 2 Date: 22 July Introduction 139

153 The exhaustion of IPv4 address space is projected to take place within the next few years. This proposal seeks to focus on measures that should be taken globally in the address management area in order to prepare for the situation in all RIR regions. 2. Summary of current problem To continue applying a global coordinated policy for distribution of the last piece(s) of each RIR s unallocated address block does not match the reality of the situation in each RIR region. Issues each RIR region will face during the exhaustion period vary by region as the level of development of IPv4 and IPv6 are widely different. As a result, applying a global co-ordinated policy may not adequately address issues in a certain region while it could be work for the others. For example, in a region where late comers desperately need even small blocks of IPv4 addresses to access to the IPv4 Internet, a policy that defines the target of allocations/assignments of IPv4 address space to be late comers would be appropriate in such region. This would allow availablilty of IPv4 address space for such requirements for more years. Another example comes from difference in IPv6 deployment rate. For a region where IPv6 deployment rate is low, measures may be necessary to prolong IPv4 address life for the existing business as well as for new businesses until networks are IPv6 ready. Some regions may have strong needs to secure IPv4 address space for translators. A globally coordinated policy which addresses all the issues listed above to meet the needs for all RIR regions may result in not solving issues in any of the regions. 3. Situation in other RIRs This proposal has been be submitted to all RIRs. The status in each RIR region is as follows: AfriNIC Reached consensus at AfriNIC 8 ARIN LACNIC RIPE Reached consensus at ARIN XXI and approved by Board of Trustees (June 2008) Reached consensus at LACNIC XI Currently under discussion 4. Details of the proposal

154 This policy describes the process for the allocation of the remaining IPv4 space from IANA to the RIRs. When a minimum amount of available space is reached, one /8 will be allocated from IANA to each RIR, replacing the current IPv4 allocation policy. In order to fulfill the requirements of this policy, at the time it is adopted, one /8 will be reserved by IANA for each RIR. The reserved allocation units will no longer be part of the available space at the IANA pool. IANA will also reserve one /8 to any new RIR at the time it is recognized. The process for the allocation of the remaining IPv4 space is divided in two consecutive phases: 4.1. Existing Policy Phase: During this phase IANA will continue allocating IPv4 addresses to the RIRs using the existing allocation policy. This phase will continue until a request for IPv4 address space from any RIR to IANA either cannot be fulfilled with the remaining IPv4 space available at the IANA pool or can be fulfilled but leaving the IANA remaining IPv4 pool empty. This will be the last IPv4 address space request that IANA will accept from any RIR. At this point the next phase of the process will be initiated Exhaustion Phase: IANA will automatically allocate the reserved IPv4 allocation units to each RIR (one /8 to each one) and respond to the last request with the remaining available allocation units at the IANA pool (M units) Size of the final IPv4 allocations: During this phase IANA will automatically allocate one /8 to each RIR from the reserved space defined in this policy. IANA will also allocate M allocation units to the RIR that submitted the last request for IPv4 addresses Allocation of the remaining IPv4 Address space: After the completion of the evaluation of the final request for IPv4 addresses, IANA MUST: A) Immediately notify the NRO about the activation of the second phase of this policy. B) Proceed to allocate M allocation units to the RIR that submitted the last request for IPv4 address space. C) Proceed to allocate one /8 to each RIR from the 141

155 reserved space. 5. Advantages and disadvantages of the proposal Advantages: - It allows each RIR community to define a policy on how to distribute the last piece(s) of allocations which best matches their situation. Disadvantages: - Concerns could be raised about allocating a fixed size to all RIRs, that it artificially fastens the consumption rate of some RIR regions. However, its impact is kept to minimum by keeping the allocation size to a single /8 which makes merely 3-4 months difference. - Concerns could be raised that explicitly allowing regional policies will encourage RIR shopping. However, this should not happen if the requirements within each region is adequately reflected in each RIR s policy through PDP. RIR may also chose to add criteria to prevent LIRs from other regions submitting such requests. 6. Effect on APNIC members APNIC members will be able to define a policy on how to distribute the last piece(s) of allocations which best matches the situation in AP region. 7. Effect on NIRs The effect on APNIC members applies to members of NIRs. NIRs are therefore expected to inform their communities of the situation. A.3.4 prop-082 prop-082 Removing aggregation criteria for IPv6 initial allocations IPv6 IPv6 IPv APNIC 142

156 3 APNIC APNIC prop-082-v002: Removing aggregation criteria for IPv6 initial allocations Author: Co-authors: Tomohiro Fujisaki Akira Nakagawa Fuminori Tanizaki Masaru Akai Toshio Tachibana Version: 2 Date: 24 February Introduction This is a proposal to remove the aggregation requirement from the IPv6 initial allocation policy. 2. Summary of the current problem The initial IPv6 address allocation criteria requires that LIRs: "Plan to provide IPv6 connectivity to organizations to which it will make assignments, by advertising that connectivity through its single aggregated address allocation."[1] However, there is no similar aggregation requirement in either the criteria for subsequent allocations, or in the new IPv6 allocation criteria for APNIC members. Including the aggregation requirement is problematic for two reasons: 1. It is inconsistent the criteria for IPv6 allocations under two other APNIC policies, which do not require aggregation. These policies are: - Subsequent IPv6 allocations - The new kick start IPv6 allocation criteria to be implemented 10 February 2010 [2] 2. Registry policy should not concern itself strongly with routing issues. 143

157 3. Situation in other RIRs LACNIC: The LACNIC community is currently discussing the following proposal to remove the requirement to announce an initial allocation as a single prefix in favour of announcing the prefix with the minimum possible level of disaggregation: : Modifications to the IPv6 Prefix Initial Allocation Policy < LAC v3-propuesta-en.pdf> RIPE: The RIPE community has recently removed routing requirements from IPv6 policy: : Removing Routing Requirements from the IPv6 Address Allocation Policy < AfriNIC and ARIN initial IPv6 allocation criteria require a plan to aggregate, with no requirement for aggregation for subsequent allocation criteria. Neither RIR is has any proposal to modify these criteria. 4. Details This is a proposal to: 4.1 Remove the requirement under the initial IPv6 allocation criteria to advertise an initial allocation as a single (aggregate) prefix. 4.2 Include a stronger recommendation about the importance of aggregation to the IPv6 policy document. The APNIC IPv6 policy document currently does include information about the importance of aggregation[3]. However, it is the opinion of this proposal s authors that the recommendation should be more strongly expressed. 5. Pros/Cons Advantages - This policy reduces the number of requirements to obtain IPv6 address. 144

158 - Other RIR communities are discussing removing aggregation requirements from their policies, so it would be appropriate for APNIC policy to maintain similar criteria to other regions. 5.2 Disadvantages - By removing the aggregation requirement in the policy, deaggregated routes may begin to be announced more frequently. 6. Effect on APNIC members APNIC members can apply for IPv6 addresses without ensuring aggregation. 7. Effect on NIRs NIRs should remove the aggregation requirement from IPv6 initial allocation criteria. 8. References [1] See section 5.2.1, "IPv6 Address Allocation and Assignment Policy" < [2] prop-073: Simplifying allocation/assignment of IPv6 to APNIC members with existing IPv4 addresses < [3] See section 3.4, "IPv6 Address Allocation and Assignment Policy" < A.3.5 prop-095 prop-095 Inter-RIR IPv4 address transfer proposal RIR IPv4 IP IPv4 IPv4 IPv4 IPv4 IPv4 145