idnits 2.17.1 draft-diao-aeip-nam-08.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There is 1 instance of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (February 14, 2017) is 2618 days in the past. Is this intentional? Checking references for intended status: None ---------------------------------------------------------------------------- == Missing Reference: 'RFC2119' is mentioned on line 114, but not defined == Missing Reference: 'S' is mentioned on line 430, but not defined == Unused Reference: 'RFC 791' is defined on line 417, but no explicit reference was found in the text == Unused Reference: 'RFC1034' is defined on line 420, but no explicit reference was found in the text == Unused Reference: 'RFC1035' is defined on line 423, but no explicit reference was found in the text == Unused Reference: 'RFC2460' is defined on line 426, but no explicit reference was found in the text == Unused Reference: 'RFC1918' is defined on line 429, but no explicit reference was found in the text == Unused Reference: 'RFC1518' is defined on line 433, but no explicit reference was found in the text == Unused Reference: 'RFC2663' is defined on line 436, but no explicit reference was found in the text == Unused Reference: 'RFC1706' is defined on line 442, but no explicit reference was found in the text == Unused Reference: 'RFC3596' is defined on line 445, but no explicit reference was found in the text == Unused Reference: 'RFC2782' is defined on line 449, but no explicit reference was found in the text == Unused Reference: 'AIP' is defined on line 453, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2460 (Obsoleted by RFC 8200) Summary: 2 errors (**), 0 flaws (~~), 15 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Diao Yuping 3 Internet-Draft Guangdong University of Finance & Economics 4 Intended status: - Diao Yongping 5 Expires: August 14, 2017 Guangzhou, China 6 Liao Ming 7 Guangzhou, China 8 February 14, 2017 10 Autonomous Extensible Internet 11 with Network Address Multiplexing(AEIP NAM) 12 draft-diao-aeip-nam-08.txt 14 Abstract 16 The two key issues of today's Internet are autonomy and 17 extensibility. Autonomous Internet(AIP) technology can provide 18 extensible internet architecture, own independent root DNS servers 19 and self management internet network; Furthermore, based on the 20 Autonomous Internet, here provides a way with extensible address 21 capacity to solve IP address deficiency and realize 22 Autonomous Extensible Internet(AEIP) with global network address 23 and multiplexing local network address. This AEIP with Network 24 Address Multiplexing(AEIP NAM) can realize autonomy and extensibility 25 with minimal cost. 27 Status of this Memo 29 This Internet-Draft is submitted to IETF in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at http://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on August 14, 2017. 44 Copyright Notice 46 Copyright (c) 2017 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (http://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 04 62 1.1. Specification of Requirements . . . . . . . . . . . . . . 04 63 2. Autonomous Internet Technology . . . . . . . . . . . . . . . . 04 64 3. Autonomous Extensible Internet (AEIP NAM) . . . . . . . . . . 05 65 3.1. Network Extensible Design . . . . . . . . . . . . . . . . 05 66 3.2. DNS Firewall . . . . . . . . . . . . . . . . . . . . . . . 08 67 3.3. Address Firewall . . . . . . . . . . . . . . . . . . . . . 08 68 3.4. Extensible Address Capacity . . . . . . . . . . . . . . . 09 69 3.5. Constraint Condition of Extensible Address Space . . . . . 10 70 4. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . 11 71 5. Security Considerations . . . . . . . . . . . . . . . . . . . 11 72 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 73 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11 74 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 75 8.1. Normative References . . . . . . . . . . . . . . . . . . . 12 76 8.2. Informative References . . . . . . . . . . . . . . . . . . 12 77 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13 79 1. Introduction 81 Internet has become an important strategic resource for its rapid 82 development all over the world. Therefore, to solve the two key 83 issues of Internet, autonomy and scalability, is particularly 84 important. 86 The essence of Internet autonomous problem is to solve the domain 87 name problem, so as to provide extensible architecture, provide 88 multi-polar, self-control, self-management over the Internet, own 89 independent root domain name server in each autonomous internet (AIP) 90 network, and safeguard global Internet without quarrel. 92 The essence of Internet scalability problem is to solve the IP 93 address shortage problem. Private network solution, dynamic address 94 assignment technology, VLSM technology and NAT technology proposed 95 in the field can only slow down the speed of the IP address 96 depletion. Due to slow progress and many unsolved problems, IPv6 can 97 not timely solve the IP address shortage problem and meet the needs 98 of rapid developing Internet. The huge demand of Internet encourages 99 that people must seriously consider the scalability of the IP 100 network in reality. 102 This article will discuss the IP network's scalability on the 103 base of Autonomous Internet, so as to solve the current problems 104 caused by IP address shortage, to realize the autonomy and extension 105 of the Internet. 107 1.1. Specification of Requirements 109 In this document, several words are used to signify the requirements 110 of the specification. These words are often capitalized. The key 111 words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", 112 "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document 113 are to be interpreted as described in [RFC2119]. 115 2. Autonomous Internet Technology 117 Autonomous Internet(AIP) technology provides a way to own independent 118 root domain name servers to realize Autonomous Internet without 119 necessary to overturn the Internet infrastructure. It provides 120 Internet global equality, secure autonomy, green extensibility. 122 According to the AIP autonomous DNS, the domain name hierarchy can 123 be designed distributedly and provide each AIP network autonomy; 124 Each AIP network has its root DNS servers, which are responsible 125 for all the DNS resolution in this AIP network. Other DNS 126 servers of this AIP network should point to these root DNS servers by 127 default. Each AIP network is almost the same as the current Internet, 128 and the internal domain name resolution and IP node communication 129 have not any change. The only change is that the destination domain 130 name need add domain name suffix of the destination AIP network when 131 IP nodes communicate between different AIP networks. Domain node 132 "www.yahoo.com" in network B is expressed as "www.yahoo.com.B" for 133 its external domain name. So each AIP domain name hierarchy tree 134 adds the top-level domain name "ex(i)", so as to map the other 135 external AIP domain name hierarchy trees accessible from this AIP 136 network. When ex(i)=B, it means that the other AIP network B is 137 accessible from this AIP network. At the same time, each AIP network 138 will add a kind of device called "AIP DNS gateway" to support domain 139 name resolution between AIP networks. 141 3. Autonomous Extensible Internet (AEIP NAM) 143 Autonomous Extensible Internet(AEIP) is feasible not only in 144 practice but also in technology. In practice, the communication 145 traffic is relatively much smaller between different languages and 146 cultures, and convergence of language and communication traffic 147 brings the reality of Internet autonomy. In technology, AIP can 148 deploy easily and cause the least change, provide security, autonomy 149 and extension in architecture. AIP is distributed Internet 150 architecture. This architectural distribution provides more choices 151 and possibilities in solving IP address deficiency problem. 153 Hereinafter, a technology would be introduced to realize extensible 154 Internet, which is so call Autonomous Extensible Internet with 155 Network Address Multiplexing (AEIP NAM). AEIP NAM mainly adopts 156 global network address, and multiplex local network address, which 157 is based on AIP architecture. 159 3.1. Network Extensible Design 161 AIP can not only solve the Internet autonomous problem but also 162 make architecture extensible with its distributed architecture. 163 The internet network can realize extension by adding some AIP 164 network entities as need. But IP network address deficiency makes 165 it necessary to further achieve scalability on the IP network 166 address, so as to realize the extensible Internet indeed. IP network 167 scalable address space realization method is described as following: 169 First of all, the Global Network Address(GNA, namely public IP 170 address) is adopted for interoperability between different AIP 171 networks. Unique GNA between AIP networks need global negotiation and 172 unified plan. (In special situation, it can be negotiated and planed 173 by directly connected AIP networks themselves.) Different GNA ranges 174 will be arranged to different AIP networks. GNA is assigned for IP 175 node used for global server or mainly used for interoperability 176 among AIP networks. Here would not be any change to current global 177 communication with public IP address. After new added AIP network 178 realize autonomy by AIP technology, it can use current or reserved 179 public IP address for inter-network communication. Therefore, 180 current Internet public IP address space arrangement can almost keep 181 unchanged. 183 Secondly, based on each AIP network, the concept of "Local Network 184 Address(LNA)" is introduced to extend global Internet IP address 185 quantity. LNA is only used for inner communication within AIP network 186 as need. LNA consists of considerable ratio part of the whole IPv4 187 32-bit address capacity. It is designed for AIP single system and 188 can be multiplexed for each different AIP single system. 189 Now the IP address is almost exhausted up, so LNA needs 190 to be converted from public IP address, no matter whether these 191 public IP addresses are already in actual use or not. Then 192 the total available IP addresses of each AIP network is the sum of 193 reusable LNA and unique GNA arranged for this AIP network. 194 For example, if the multiplexing LNA occupies 1/4 ratio of 195 the total IP address space, namely about 1 billion IP addresses, so 196 there are billions of addresses besides its currently used GNA for 197 each AIP network and can satisfy its address quantity requirement. 198 Furthermore, multiple AIP networks can be added as need and provide 199 additional times of available IP address quantity. Generally in each 200 AIP network, IP nodes only configure LNA or GNA and they can 201 communicate to each other peer-to-peer directly. AEIP NAM network 202 is almost the same as AIP network in Autonomous Internet technology. 203 Its internal communication is independent from external AIP network 204 and it is not necessary any upgrade and transformation for current 205 IP nodes. 207 Moreover, Private Network Address (PNA, namely private IP address) 208 would still keep using as multiplexing private network address 209 within each AIP network of AEIP NAM. 211 Fig. 1 shows the realization of Autonomous Extensible Internet 212 (AEIP NAM) 213 . 214 +-------------------------------.-------------------------------+ 215 |+---------+ . | 216 ||Root DNS <--------------------+ | 217 || | .\ | 218 |+----^----+ . +-----------------------+ | 219 | | . | | 220 |+----v----+ . +----v----+| 221 || DNS | . | DNS || 222 || (.us) | . | (.cn) || 223 |+----^----+ . +----^----+| 224 | | . | | 225 |+----v----+ . +----v----+| 226 || Host | . | Host || 227 || N1(G1) | . | N2(G2) || 228 |+---------+ . +---------+| 229 | Internet | 230 +-------------------------------.-------------------------------+ 231 \./ 232 V 233 +------------------------------+ +------------------------------+ 234 |+----------+ +----------+| |+----------+ +----------+| 235 || Root DNS <------> AIP DNS <+-+> AIP DNS <------> Root DNS || 236 || (A) | | GW A || || GW B | | (B) || 237 |+----^-----+ +----^-----+| |+----^-----+ +----^-----+| 238 | | | | | | 239 |+----v-----+ | |+----------+ +----v-----+| 240 || DNS | | || Host | | DNS || 241 ||(.us/.com)| | || LNb4(Lb4)<--+ |(.cn/.com)|| 242 |+----^-----+ | |+----------+ | +----^-----+| 243 | | | | | | | 244 |+----v-----+ +----------+| |+----------+ | +----v-----+| 245 || Host <------> Firewall <+-+> Firewall | +---> Host || 246 || Na1(Ga1) | | A || || B <------> Nb2(Gb2) || 247 |+----------+ +----^-----+| |+----^-----+ +----------+| 248 | Internet/AEIP NAM network A | | AEIP NAM network B | 249 +------------------------------+ +------------------------------+ 251 Figure 1: AEIP NAM realization 252 Note: IP host is labeled as DomainName(IPAddress). Prefix "L" 253 denotes nodes with LNA. Prefix "G" denotes nodes with GNA. 254 AIP DNS GW is a gateway for DNS resolution between AIP networks. 256 3.2. DNS Firewall 258 In order to realize AIP network's thoroughly independent domain 259 name management and avoid internal domain name revealed to other 260 AIP networks, domain name can be isolated by AIP network DNS gateway 261 in AEIP NAM. 263 In order to prevent unauthorized access to AIP network internal 264 domain name from other AIP networks, domain name range opened to 265 other AIP network access can be set in this AIP network DNS gateway 266 ingress. 268 Correspondingly, in order to prevent unauthorized access to other 269 AIP network internal domain name from this AIP network, domain name 270 range opened to this AIP network access can be set in this AIP 271 network DNS gateway egress. 273 3.3. Address Firewall 275 In order to prevent causing confusion and avoid LNA used in this 276 AIP network revealed to other AIP networks, LNA can be isolated by 277 AIP network firewall in AEIP NAM. 279 In order to prevent IP packet with LNA in its source address field 280 or destination address field infiltrating into this AIP network from 281 other AIP networks, access denial to IP packet with LNA in its 282 source address field from other AIP networks should be set in this 283 AIP network firewall ingress; and access denial to IP packet with 284 LNA in its destination address field from other AIP networks should 285 be set in this AIP network firewall ingress. 287 IP nodes using LNA is generally only suitable for AIP network 288 internal communication. In order to prevent IP packet with LNA in 289 its source address field or destination address field infiltrating 290 into other AIP networks from this AIP network, access denial to 291 IP packet with LNA in its destination address field from this 292 AIP network should be set in this AIP network firewall egress. 294 Moreover, access denial to IP packet with LNA in its source address 295 field from this AIP network should be set in this AIP network 296 firewall egress. Or some unidirectional dynamic communication 297 between AIP networks such as web browsing, can be implemented by 298 simple NAT method and might have some service limitation. 300 3.4. Extensible Address Capacity 302 Based on the extensible network architecture of autonomous internet, 303 AEIP NAM designs a set of multiplexing address space and can always 304 provide a set of ready address space for new added single AIP 305 network system entity. Thus it can effectively solve IP address 306 deficiency problem of Internet and remove the barrier to Internet 307 extension. 309 This set of multiplexing address space includes three parts: 310 the LNA L, the GNA G and the Private Network Address P. These 311 three types of network addresses are divided properly using 312 existing Internet 32-bit address space C. The size of the existing 313 Internet address space is C=2^32, and P=2^16+2^20+2^24. Then we 314 have C=G+L+P and approximately 315 C=G+L (1) 317 The GNA subspace is not for multiplexing. The LNA resources in 318 each AIP network of AEIP NAM include a certain proportion of address 319 space of existing Internet, and they can be multiplexed in different 320 AIP network. In general, all IP nodes can communicate with each 321 other directly within each AIP network no matter they are assigned 322 LNA or GNA. But only IP nodes which are assigned GNA in one AIP 323 network can communicate directly with those nodes that are assigned 324 GNA in other AIP networks. 326 Assume that there are m of such AIP networks, each of them has 327 GNA quantity g(i) and LNA quantity l(i). Then the total capacity 328 of the AEIP NAM extensible address space C' can be counted as 329 C'=m*[g(i)+l(i)] (2) 331 Since the LNA is multiplexed in different AIP networks and each 332 AIP network can use the entire LNA space L, so the maximum total 333 capacity of the AEIP NAM address space 334 C'max=m*[g(i)+L]=C+(m-1)L (3) 336 According to (3), we can obtain the Change trend figure of total 337 address extension capacity. The maximum address capacity C'max 338 increases linearly when the AIP network number m increasing with 339 specific ratio LNA capacity. In this way, the design of AEIP NAM 340 can add AIP networks as need and greatly increase the IP address 341 capacity synchronously. So the extension of network is achievable. 343 3.5. Constraint Condition of Extensible Address Space 345 According to the statistics, most of the several thousand languages 346 surviving currently have less than 100 thousand users, so call 347 "ethnic language". Some of them have only thousands of or even 348 hundreds of users. The 90% of them will disappear after several 349 generations. There are about 200-250 languages which have more than 350 1 million users. Twelve languages among them have more than 100 351 million users, which cover most of the countries all over the 352 world (the simple accumulative total number of countries is 201) 353 and is used by over 3.5 billion users or 60% of the world 354 population. 356 The six work languages approved formally by United Nations are 357 English, French, Russian, Chinese, Spanish and Arabic. The 358 population using Chinese is 907 million or 15% of the world 359 population. There are over 1.3 billion people in China and most of 360 them use Chinese while some minorities use their own languages. 361 The population using English are 456 million, but the number of 362 people who are learning English is more than 1 billion. English 363 is the most powerful language in the world and is used as official 364 language by 75 countries all over the world. In addition, French 365 has been applied widely in the international social and diplomatic 366 activities, whose rank is only secondary to English. It is not only 367 the official language of France, but also the official language or 368 common language of 42 countries or regions in five continents. The 369 population speaking French are about 120 million including over 370 50 million native French. 372 Therefore, in order to aggregate the great communication traffic 373 using the same language, a single AIP network need to reach about 374 1 billion users or C/4 IP address scale at least. So the capacity 375 of Local Network Address L designed in Autonomous Extensible 376 Internet AEIP NAM should be greater than or equal to C/4. Thus 377 the capacity of Global Network Address G is less than or equal to 378 3C/4 according to (1). In addition, the design idea of AEIP NAM 379 is mainly based on the global address. The capacity of Global 380 Network Address G should be greater than or equal to C/2 and L is 381 less than or equal to C/2 accordingly. So the constraint condition 382 of AEIP NAM extensible address space is 383 L~[C/4,C/2]; G~[3C/4,C/2] (4) 385 4. Conclusion 387 Based on Autonomous Internet architecture, Autonomous Extensible 388 Internet with Network Address Multiplexing (AEIP NAM) mainly 389 adopts Global Network Address, and multiplexes Local Network Address 390 to realize extensible Internet. It provides an integrated solution 391 to Internet autonomy and extension issues. In practice, it has 392 little reformation work, smooth transition and can be implemented 393 even in unilateral technical action to realize Autonomous 394 Extensible Internet. 396 5. Security Considerations 398 There is no additional security requirement than current Internet 399 system. Security issues are not discussed in this memo. 401 6. IANA Considerations 403 According to the AEIP NAM solution and the constraint condition of 404 extensible address space, IANA need to plan proper ratio 405 of GNA and LNA in 32-bit IP version 4 address capacity and adjust 406 their assignment in different AIP networks. 408 7. Acknowledgments 410 The authors would like to thank everybody for their valuable opinion 411 and evaluation to this document. 413 8. References 415 8.1. Normative References 417 [RFC 791] Postel, J., ed., "Internet Protocol - DARPA Internet 418 Program Protocol Specification", RFC 791, September 1981. 420 [RFC1034] Mockapetris, P., "Domain names - concepts and facilities", 421 STD 13, RFC 1034, November 1987. 423 [RFC1035] Mockapetris, P., "Domain names - Implementation and 424 Specification", STD 13, RFC 1035, November 1987. 426 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 427 (IPv6) Specification", RFC 2460, December 1998. 429 [RFC1918] Rekhter Y, Moskowitz B, Karrenberg D, et al, "Address 430 Allocation for Private Internets", RFC 1918[S], 431 February 1996. 433 [RFC1518] Rekhter, Y, Li T. "An Architecture for IP Address 434 Allocation with CIDR", RFC 1518, September 1993. 436 [RFC2663] Srisuresh P, Holdrege M. "IP Network Address Translator 437 (NAT) Terminology and Considerations", RFC 2663, 438 August 1999. 440 8.2. Informative References 442 [RFC1706] B. Manning, and R. Colella, "DNS NSAP Resource Records", 443 RFC 1706, October 1994. 445 [RFC3596] S. Thomson, C. Huitema, V. Ksinant, and M. Souissi, "DNS 446 Extensions to Support IP Version 6", RFC 3596, October 447 2003. 449 [RFC2782] A. Gulbrandsen, P. Vixie, and L. Esibov, "A DNS RR for 450 specifying the location of services (DNS SRV)", RFC 2782, 451 February 2000. 453 [AIP] Diao Yuping, Diao Yongping, Liao Ming, "DNS Extension for 454 Autonomous Internet", draft-diao-aip-dns(work in 455 progress), June 2012. 457 Authors' Addresses 459 Diao Yuping 460 Information Institute of Guangdong University of Finance & Economics, 461 21 Luntou Road, Haizhu District, 462 Guangzhou 510320, China. 464 Email: diaoyp73@yahoo.com 466 Diao Yongping 467 China Telecom-Guangzhou Institute 468 109 West Zhongshan Ave, 469 Guangzhou 510630, China. 471 Email: diaoyp@yahoo.com 473 Liao Ming 474 610 Tianhe North Road, 475 Guangzhou 510631, China. 477 Email: luminous_liao@yahoo.com