idnits 2.17.1 draft-diao-aeip-nat-07.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 : ---------------------------------------------------------------------------- No issues found here. 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 (October 14, 2016) is 2751 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 508, but not defined == Unused Reference: 'RFC 791' is defined on line 495, but no explicit reference was found in the text == Unused Reference: 'RFC1034' is defined on line 498, but no explicit reference was found in the text == Unused Reference: 'RFC1035' is defined on line 501, but no explicit reference was found in the text == Unused Reference: 'RFC2460' is defined on line 504, but no explicit reference was found in the text == Unused Reference: 'RFC1918' is defined on line 507, but no explicit reference was found in the text == Unused Reference: 'RFC1518' is defined on line 511, but no explicit reference was found in the text == Unused Reference: 'RFC2663' is defined on line 514, but no explicit reference was found in the text == Unused Reference: 'RFC1706' is defined on line 520, but no explicit reference was found in the text == Unused Reference: 'RFC3596' is defined on line 523, but no explicit reference was found in the text == Unused Reference: 'RFC2782' is defined on line 527, but no explicit reference was found in the text == Unused Reference: 'AIP' is defined on line 531, but no explicit reference was found in the text == Unused Reference: 'AEIP NAM' is defined on line 535, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2460 (Obsoleted by RFC 8200) Summary: 1 error (**), 0 flaws (~~), 16 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Diao Yongping 3 Internet-Draft Guangzhou, China 4 Intended status: - Liao Ming 5 Expires: April 14, 2017 Guangzhou, China 6 Diao Yuping 7 Guangdong Commercial College 8 October 14, 2016 10 Autonomous Extensible Internet 11 with Network Address Translation(AEIP NAT) 12 draft-diao-aeip-nat-07.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). It mainly adopts local 23 network address based on per Autonomous IP network and uses 24 bilateral dynamic NAT with global network address between 25 Autonomous IP networks to solve IP address deficient problem. 26 This AEIP with Network Address Translation(AEIP NAT) can realize 27 autonomy and extensibility with minimal cost. 29 Status of this Memo 31 This Internet-Draft is submitted to IETF in full conformance with the 32 provisions of BCP 78 and BCP 79. 34 Internet-Drafts are working documents of the Internet Engineering 35 Task Force (IETF). Note that other groups may also distribute 36 working documents as Internet-Drafts. The list of current Internet- 37 Drafts is at http://datatracker.ietf.org/drafts/current/. 39 Internet-Drafts are draft documents valid for a maximum of six months 40 and may be updated, replaced, or obsoleted by other documents at any 41 time. It is inappropriate to use Internet-Drafts as reference 42 material or to cite them other than as "work in progress." 44 This Internet-Draft will expire on April 14, 2017. 46 Copyright Notice 48 Copyright (c) 2016 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents 53 (http://trustee.ietf.org/license-info) in effect on the date of 54 publication of this document. Please review these documents 55 carefully, as they describe your rights and restrictions with respect 56 to this document. Code Components extracted from this document must 57 include Simplified BSD License text as described in Section 4.e of 58 the Trust Legal Provisions and are provided without warranty as 59 described in the Simplified BSD License. 61 Table of Contents 63 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 04 64 1.1. Specification of Requirements . . . . . . . . . . . . . . 04 65 2. Autonomous Internet Technology . . . . . . . . . . . . . . . . 04 66 3. Autonomous Extensible Internet (AEIP NAT) . . . . . . . . . . 05 67 3.1. Network Extensible Design . . . . . . . . . . . . . . . . 06 68 3.2. Addressing Realization . . . . . . . . . . . . . . . . . . 08 69 3.3. DNS Resolution . . . . . . . . . . . . . . . . . . . . . . 11 70 4. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . 13 71 5. Security Considerations . . . . . . . . . . . . . . . . . . . 13 72 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 73 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13 74 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 75 8.1. Normative References . . . . . . . . . . . . . . . . . . . 14 76 8.2. Informative References . . . . . . . . . . . . . . . . . . 14 77 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15 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, are 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, free extension, and self-management. 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 NAT) 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 Translation (AEIP NAT). AEIP NAT, which 156 is based on AIP architecture, mainly adopts local 157 network address based on per Autonomous IP network and uses 158 bilateral dynamic NAT with global network address between 159 Autonomous IP networks to solve IP address deficient problem. 161 3.1. Network Extensible Design 163 Autonomous Internet can solve the problem of Internet autonomy. 164 Moreover, its distributed architecture design makes it extensible 165 in architecture level. To increase the number of AIP network 166 entities as need, we can realize the network extension. But the 167 existing IP network address is almost used up. In further step, 168 it is necessary to realize extension of the IP network address, 169 so as to realize the extension of Internet indeed. 171 The realization method of extensible network address space 172 is detailed as following: 174 First of all, the concept of the "Local Network Address (LNA)" 175 is introduced inside each AEIP NAT network. The local network 176 address resource (local IP address) within each AEIP NAT network 177 includes considerable part of the Internet address space and can be 178 duplicated in different AEIP NAT networks. In general, the network 179 node can only be assigned local network address and all IP nodes 180 within each AEIP NAT network can communicate to each other directly 181 through the local network address. In this way, there are about 182 several billions of IP address in each AEIP NAT network and it can 183 solve the IP address deficient problem within each AEIP NAT network; 184 Moreover, it can provide almost any needed IP address quantities 185 if owning more AEIP NAT networks as need, which can increase the 186 IP address quantity in times. To each AEIP NAT network such as 187 A or B, it is almost consistent with the status of AIP network 188 in Autonomous Internet and is not necessary to upgrade or change 189 existing network node. The internal communication within each 190 AEIP NAT is independent from other AEIP NAT networks. 192 Secondly, "Global Network Address (GNA)" (public IP address) is 193 adopted to communicate between different AEIP NAT networks. 194 The unique Global Network Address range between AEIP NAT networks 195 is negotiated and planned globally (Under the special circumstance, 196 it can be determined within the two AEIP NAT networks, which is 197 communicating with each other). Different AEIP NAT networks will 198 be allotted different GNA range. In each AEIP NAT network, DNS 199 Gateway is responsible for the dynamic assignment of GNA. And it 200 stores and maintains the GNA - LNA pairs table (G, L) and the domain 201 name - GNA pairs table (N, G). Any GNA - LNA pair, for example 202 (Ga, La), will be sent to NAT GW during its dynamical live period 203 in order to translate address between the AEIP NAT networks. 204 During its dynamic live period, any domain name - GNA pair, 205 for example (Nb, Gb), will provide DNS GW domain name resolution 206 and GNA query between AEIP NAT networks. So its smooth transition 207 method is almost the same as Autonomous Internet except that 208 upgrading the function of DNS GW and adding NAT GW device to 209 support the NAT functions between AEIP NAT networks. In particular, 210 if unilateral action is the only way available, the unilateral 211 transformation method is the same as the method mentioned in AIP 212 and mainly relates to external domain name between AEIP NAT networks. 213 Due to only public IP address is legal between AEIP NAT networks 214 before the existing Internet (the core part) can be transformed 215 into one AEIP NAT network, so the existing Internet (the core part) 216 does not need any transformation. Only in the new added AEIP NAT 217 network, it needs to upgrade the function of DNS GW and add NAT GW 218 device for cross-network address translation. The new added 219 AEIP NAT network can adopt existing or reserved public IP addresses 220 for cross-network communication. Thus the internal available 221 IP addresses will increase greatly and achieve the extension of 222 network. 224 In addition, the "Private Network Address" (PNA, namely existing 225 private IP address) is still retained. It is used as private 226 network address within each AEIP NAT network. 228 The realization of AEIP NAT is shown in Figure 1. 230 . 231 +-------------------------------.-------------------------------+ 232 |+---------+ . | 233 ||Root DNS <--------------------+ | 234 || | .\ | 235 |+----^----+ . +-----------------------+ | 236 | | . | | 237 |+----v----+ . +----v----+| 238 || DNS | . | DNS || 239 || (.us) | . | (.cn) || 240 |+----^----+ . +----^----+| 241 | | . | | 242 |+----v----+ . +----v----+| 243 || Host | . | Host || 244 || N1(G1) | . | N2(G2) || 245 |+---------+ . +---------+| 246 | Internet | 247 +-------------------------------.-------------------------------+ 248 \./ 249 V 250 +------------------------------+ +------------------------------+ 251 |+----------+ +-----------+| |+-----------+ +----------+| 252 || Root DNS <-----> AEIP NAT <+-+> AEIP NAT <-----> Root DNS || 253 || (A) | | DNS GW A || || DNS GW B | | (B) || 254 |+----^-----+ |{(Na.A,Ga)}|| ||{(Nb.B,Gb)}| +----^-----+| 255 | | +-----^-----+| |+----^------+ | | 256 |+----v-----+ | | | | +----v-----+| 257 || DNS | | | | | | DNS || 258 ||(.us/.com)| | | | | |(.cn/.com)|| 259 |+----^-----+ | | | | +----^-----+| 260 | | +----v-----+| |+----v-----+ | | 261 |+----v-----+ | AEIP NAT || || AEIP NAT | +----v-----+| 262 || Host <------> GW A <+-+> GW A <------> Host || 263 || Na1(La1) | | {(Ga,La)}|| || {(Gb,Lb)}| | Nb2(Lb2) || 264 |+----------+ +----------+| |+----------+ +----------+| 265 | Internet/AEIP NAT network A | | AEIP NAT network B | 266 +------------------------------+ +------------------------------+ 268 Figure 1: AEIP NAT realization 269 Note: IP host is labeled as DomainName(IPAddress). IP address with 270 Prefix "L" such as "La" denotes LNA, IP address with prefix "G" 271 such as "Ga" denotes GNA. AEIP NAT DNS GW is a gateway for DNS 272 resolution between AEIP NAT networks and GNA assignment for its 273 affiliated AEIP NAT network. AEIP NAT GW is a gateway for bilateral 274 dynamic NAT between AEIP NAT networks. 276 3.2. Addressing Realization 278 Within each AEIP NAT network, IP nodes communicate to each other 279 peer-to-peer directly adopting the Local Network Address. 281 Between different AEIP NAT networks, GNA will be adopted to locate 282 the IP node in different network. Assume that there is any one 283 IP node Na1(La1) in AEIP NAT network A, which has the domain name 284 Na1 and local network address La1. And there is any one IP node 285 Nb2(Lb2) in AEIP NAT network B, which has the domain name Nb2 and 286 local network address Lb2. The communication process from Na1 287 to Nb2 is shown as following: 289 1) Source Address NAT Addressing Process: 291 It is required that the packet destination address adopts dynamic 292 allocated GNA of specific destination AEIP NAT network, for 293 example Gb2 for IP node Nb2.B (It can be obtained by DNS resolution 294 between AEIP NAT networks). Thus the source node Na1 send a 295 cross-network packet denoted as {S(La1),D(Gb2)}, which has a 296 source address La1 and a destination address Gb2. Then this 297 cross-network packet will be firstly routed to this source 298 network's interworking gateway AEIP NAT GW A. And the AEIP NAT GW A 299 will do network address translation to the source address in the 300 cross-network packet. This source address NAT adressing process 301 is detailed as following: 303 Step 1: the AEIP NAT GW A querys the source IP node's LNA(La1) 304 corresponding record item in its GNA - LNA pairs table (G, L). 305 If corresponding GNA - LNA pair record, for example (Ga1, La1), 306 is return, the source network node's LNA(La1) in source address 307 field of packet will be replaced by corresponding GNA(Ga1). And 308 this packet, which is now denoted as {S(Ga1),D(Gb2)}, will be 309 routed to the AEIP NAT GW B of the destination network. It is 310 so called the source address NAT method. 312 Step 2: If the AEIP NAT GW A can not find the source IP node's 313 LNA(La1) corresponding record item, for example (Ga1, La1), in 314 its GNA - LNA pairs table (G, L). Then it will send a DNS PTR query 315 to corresponding AEIP NAT DNS GW A in order to obtain the 316 domain name of the soure IP node with LNA(La1): 318 (1) If the source node has a legal domain name, AEIP DNS GW A 319 will act as an inner-network DNS agent, query and obtain source 320 node's domain name and return it to AEIP NAT GW A in a traditional 321 DNS resolution way. Then both of AEIP DNS GW A and AEIP NAT GW A 322 have the source IP node's LNA(La1) corresponding record item 323 (Na1, La1) in its domain name - LNA pairs table (N, L). At the 324 same time, the source node is assigned GNA in the corresponding 325 domain name - GNA pair record item (Na1.A, Ga1) inside AEIP NAT 326 DNS GW A in order to be visited in cross-network access and 327 receive the return ip packets. In addition, the GNA - LNA 328 pair record item (Ga1, La1) is sent to the corresponding AEIP NAT 329 GW A for NAT translation. And this GNA - LNA pair record item 330 should keep consistent in AEIP NAT DNS GW A and in AEIP NAT 331 GW A during its life time. 333 (2) If the source node does not have the legal domain name, 334 AEIP NAT DNS GW A will assign it(local network address La1) a 335 corresponding global network address Ga1. In addition, the GNA -LNA 336 pair record item (Ga1,La1) is sent to the corresponding AEIP NAT 337 GW A for NAT translation. And this GNA - LNA pair record item 338 should keep consistent in AEIP NAT DNS GW A and in AEIP NAT 339 GW A during its life time. 341 (3) Then the source network node's LNA(La1) in source address field 342 of packet will be replaced by corresponding GNA(Ga1). And this 343 packet, which is now denoted as {S(Ga1),D(Gb2)}, will be 344 forwarded to the AEIP NAT GW B of the destination network. 346 2) Destination Address NAT Addressing Process: 348 The internetworking gateway AEIP NAT GW B in the destination 349 AEIP NAT network B will have a destination address NAT to the 350 destination address in cross-network data packet when the 351 cross-network data packet reaches the AEIP NAT GW B in AEIP NAT 352 network B. The process is detailed as following: 354 Step 3: the AEIP NAT GW B querys the destination IP node's GNA(Gb2) 355 corresponding record item in its GNA - LNA pairs table (G, L). 356 If corresponding GNA - LNA pair record, for example (Gb2, Lb2), 357 is return, the destination network node's GNA(Gb2) in destination 358 address field of packet will be replaced by corresponding LNA(Lb2). 359 And this packet, which is now denoted as {S(Ga1),D(Lb2)}, will 360 be forwarded into the AEIP NAT network B. It is so called the 361 destination address NAT method. Finally, the packet will be 362 routed and reach the destination node. 364 Step 4: If the AEIP NAT GW B can not find the destination IP node's 365 GNA(Gb2) corresponding record item, for example (Gb2, Lb2), in 366 its GNA - LNA pairs table (G, L). Then it will send a DNS PTR query 367 to corresponding AEIP NAT DNS GW B in order to obtain the 368 domain name of the destination IP node with GNA(Gb2): 370 (1) If the destination node has a legal domain name, it should 371 be pre-assignned the corresponding domain name - GNA pair 372 record item (Nb2.B, Gb2) inside AEIP NAT DNS GW B in order that 373 the destination node can be visited in cross-network access 374 and receive the return ip packets, and this would be return to 375 AEIP NAT GW B for DNS query; At the same time, AEIP DNS GW B 376 will act as a inner-network DNS agent, query and obtain 377 destination node's domain name - LNA pair record and return it 378 to AEIP NAT GW B in a traditional DNS resolution way. Then 379 both of AEIP DNS GW B and AEIP NAT GW B have the destination 380 IP node's corresponding record item (Nb2, Lb2) in its 381 domain name - LNA pairs table (N, L). In addition, AEIP NAT 382 DNS GW B will send the GNA - LNA pair record item (Gb2, Lb2) 383 to the corresponding AEIP NAT GW B for NAT translation. And 384 this GNA - LNA pair record item should keep consistent in 385 AEIP NAT DNS GW B and in AEIP NAT GW B during its life time. 387 (2) If the destination node does not have a legal domain name, 388 AEIP NAT DNS GW B should pre-assign it (local network address 389 Lb2) a corresponding global network address Gb2 for 390 cross-network communication. In addition, the GNA - LNA pair 391 record item (Gb2-Lb2) is sent to the corresponding AEIP NAT 392 GW B for NAT translation. And this GNA - LNA pair record item 393 should keep consistent in AEIP NAT DNS GW B and in AEIP NAT 394 GW B during its life time. 396 (3).Then AEIP NAT GW B would process the packet by the 397 destination address NAT method. Here the destination network 398 node's GNA(Gb2) in destination address field of packet will 399 be replaced by corresponding LNA(Lb2) and this packet, which 400 is now denoted as {S(Ga1),D(Lb2)}, will be forwarded into 401 the AEIP NAT network B. Finally, the packet will be routed 402 and reach the destination node. 404 3.3. DNS Resolution 406 Autonomous extensible internet AEIP NAT is evolved on the basis 407 of autonomous internet AIP. Each autonomous IP network has a 408 complete set of domain name system to support the resolution of 409 domain name and address within the network. Each network node 410 has a default unique network domain name suffix whether is marked 411 or not. The default unique network domain name suffix should be 412 added while accessing to this external network node. 414 The AEIP NAT DNS gateway (AEIP NAT DNS GW) in each AEIP NAT network 415 is evolved on the basis of AIP DNS GW to support cross-network 416 DNS resolution between AEIP NAT networks. AEIP NAT DNS GW forwards 417 the cross-network DNS query originated in this AEIP NAT network. 418 And it provides and/or stores the dynamic assigned GNA for IP node 419 in this AEIP NAT network. It responses with the corresponding 420 dynamic assigned GNA for IP node in this AEIP NAT network to the 421 cross-network DNS query originated in external AEIP NAT network. 423 The DNS resolution process is described as following: 425 Within each AEIP NAT network, the DNS resolution is the same a 426 s the traditional way. 428 Between different AEIP NAT networks, when the source IP node 429 originates a cross-network DNS resolution query, this query 430 would be routed to this source network's AEIP NAT DNS GW A and 431 then be forwarded to domain name affiliated destination network's 432 AEIP NAT DNS GW B. The AEIP NAT DNS GW B in destination network 433 would process this corss-network DNS query as following: 435 Step 1: First, the AEIP NAT DNS GW B will query whether there is 436 corresponding domain name - GNA pair record item (Nb2.B, Gb2) 437 in its record tables. If yes, AEIP NAT DNS GW B will return 438 the record item (Nb2.B, Gb2) to the DNS requester and eventually 439 it will reach the source IP node which originates the query. 441 Step 2: If the AEIP NAT GW B can not find the destination IP node's 442 corresponding domain name record or domain name - GNA pair 443 record item, for example (Nb2.B, Gb2), in its domain name - GNA pairs 444 table (N, G), it will act as a inner-network DNS agent, query and 445 obtain destination node's domain name - LNA pair record, for 446 example (Nb2, Lb2) and return it to AEIP NAT GW B in a traditional 447 DNS resolution way. At the same time, the destination node is 448 assignned the corresponding domain name - GNA pair record item 449 (Nb2.B, Gb2) inside AEIP NAT DNS GW B in order to be visited in 450 cross-network access. AEIP NAT DNS GW B will return the record item 451 (Nb2.B, Gb2) to the DNS requester and eventually it will reach the 452 source IP node which originates the query. In addition, the 453 GNA - LNA pair record item (Gb2, Lb2) is sent to the corresponding 454 AEIP NAT GW B for NAT translation. And this GNA - LNA pair record 455 item should keep consistent in AEIP NAT DNS GW B and in AEIP NAT 456 GW B during its life time. 458 4. Conclusion 460 The huge demand of Internet encourages that people must seriously 461 consider the scalability of the IP network. So as to solve the 462 two key issues of Internet, autonomy and scalability, are 463 particularly important. Based on Autonomous Internet architecture, 464 Autonomous Extensible Internet with Network Address Translation 465 (AEIP NAT) mainly adopts local network address based on per 466 Autonomous IP network and uses bilateral NAT with global network 467 address between Autonomous IP networks to solve IP address 468 deficient problem. It provides an integrated solution to Internet 469 autonomy and extension issues. In practice, it has little 470 reformation work, smooth transition and can be implemented 471 even in unilateral technical action to realize Autonomous 472 Extensible Internet. 474 5. Security Considerations 476 There is no additional security requirement than current Internet 477 system. Security issues are not discussed in this memo. 479 6. IANA Considerations 481 According to the AEIP NAT solution and the design of the 482 extensible address space, IANA need to plan proper ratio 483 of GNA and LNA in 32-bit IP version 4 address capacity and adjust 484 their assignment in different AEIP NAT networks. 486 7. Acknowledgments 488 The authors would like to thank everybody for their valuable opinion 489 and evaluation to this document. 491 8. References 493 8.1. Normative References 495 [RFC 791] Postel, J., ed., "Internet Protocol - DARPA Internet 496 Program Protocol Specification", RFC 791, September 1981. 498 [RFC1034] Mockapetris, P., "Domain names - concepts and facilities", 499 STD 13, RFC 1034, November 1987. 501 [RFC1035] Mockapetris, P., "Domain names - Implementation and 502 Specification", STD 13, RFC 1035, November 1987. 504 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 505 (IPv6) Specification", RFC 2460, December 1998. 507 [RFC1918] Rekhter Y, Moskowitz B, Karrenberg D, et al, "Address 508 Allocation for Private Internets", RFC 1918[S], 509 February 1996. 511 [RFC1518] Rekhter, Y, Li T. "An Architecture for IP Address 512 Allocation with CIDR", RFC 1518, September 1993. 514 [RFC2663] Srisuresh P, Holdrege M. "IP Network Address Translator 515 (NAT) Terminology and Considerations", RFC 2663, 516 August 1999. 518 8.2. Informative References 520 [RFC1706] B. Manning, and R. Colella, "DNS NSAP Resource Records", 521 RFC 1706, October 1994. 523 [RFC3596] S. Thomson, C. Huitema, V. Ksinant, and M. Souissi, "DNS 524 Extensions to Support IP Version 6", RFC 3596, October 525 2003. 527 [RFC2782] A. Gulbrandsen, P. Vixie, and L. Esibov, "A DNS RR for 528 specifying the location of services (DNS SRV)", RFC 2782, 529 February 2000. 531 [AIP] Diao Yuping, Diao Yongping, Liao Ming, "DNS Extension for 532 Autonomous Internet", draft-diao-aip-dns(work in 533 progress), June 2012. 535 [AEIP NAM] Diao Yuping, Diao Yongping, Liao Ming, "Autonomous 536 Extensible Internet with Network Address Multiplexing 537 (AEIP NAM)", draft-diao-aeip-nam(work in progress), 538 January 2013. 540 Authors' Addresses 542 Diao Yongping 543 China Telecom-Guangzhou Institute 544 109 Zhongshan Ave West, 545 Guangzhou 510630, China. 547 Email: diaoyp@yahoo.com 549 Liao Ming 550 610 Tianhe North Road, 551 Guangzhou 510631, China. 553 Email: luminous_liao@yahoo.com 555 Diao Yuping 556 Information Institute of Guangdong Commercial College, 557 21 Luntou Road, Haizhu District, 558 Guangzhou 510320, China. 560 Email: diaoyp73@yahoo.com