| 1 |
<pre>Network Working Group Z. Wang |
| 2 |
Request for Comments: 1385 University College London |
| 3 |
November 1992 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">EIP: The Extended Internet Protocol</span> |
| 7 |
<span class="h1">A Framework for Maintaining Backward Compatibility</span> |
| 8 |
|
| 9 |
Status of this Memo |
| 10 |
|
| 11 |
This memo provides information for the Internet community. It does |
| 12 |
not specify an Internet standard. Distribution of this memo is |
| 13 |
unlimited. |
| 14 |
|
| 15 |
Summary |
| 16 |
|
| 17 |
The Extended Internet Protocol (EIP) provides a framework for solving |
| 18 |
the problem of address space exhaustion with a new addressing and |
| 19 |
routing scheme, yet maintaining maximum backward compatibility with |
| 20 |
current IP. EIP can substantially reduce the amount of modifications |
| 21 |
needed to the current Internet systems and greatly ease the |
| 22 |
difficulties of transition. This is an "idea" paper and discussion is |
| 23 |
strongly encouraged on [email protected]. |
| 24 |
|
| 25 |
Introduction |
| 26 |
|
| 27 |
The Internet faces two serious scaling problems: address exhaustion |
| 28 |
and routing explosion [1-2]. The Internet will run out of Class B |
| 29 |
numbers soon and the 32-bit IP address space will be exhausted |
| 30 |
altogether in a few years time. The total number of IP networks will |
| 31 |
also grow to a point where routing algorithms will not be able to |
| 32 |
perform routing based a flat network number. |
| 33 |
|
| 34 |
A number of short-term solutions have been proposed recently which |
| 35 |
attempt to make more efficient use of the the remaining address space |
| 36 |
and to ease the immediate difficulties [3-5]. However, it is |
| 37 |
important that a long term solution be developed and deployed before |
| 38 |
the 32-bit address space runs out. |
| 39 |
|
| 40 |
An obvious approach to this problem is to replace the current IP with |
| 41 |
a new internet protocol that has no backward compatibility with the |
| 42 |
current IP. A number of proposals have been put forward: Pip[7], |
| 43 |
Nimrod [<a href="#ref-8" title=""A New IP Routing and Addressing Architecture"">8</a>], TUBA [<a href="#ref-6" title=""TCP and UDP with Bigger Addresses (TUBA), a Simple Proposal for Internet Addressing and Routing"">6</a>] and SIP [<a href="#ref-14" title=""SIP: Simple Internet Protocol"">14</a>]. However, as IP is really the |
| 44 |
cornerstone of the current Internet, replacing it with a new "IP" |
| 45 |
requires fundamental changes to many aspects of the Internet system |
| 46 |
(e.g., routing, routers, hosts, ARP, RARP, ICMP, TCP, UDP, DNS, FTP). |
| 47 |
|
| 48 |
Migrating to a new "IP" in effect creates a new "Internet". The |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Wang [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc1385">RFC 1385</a> EIP November 1992</span> |
| 55 |
|
| 56 |
|
| 57 |
development and deployment of such a new "Internet" would take a very |
| 58 |
large amount of time and effort. In particular, in order to maintain |
| 59 |
interoperability between the old and new systems during the |
| 60 |
transition period, almost all upgraded systems have to run both the |
| 61 |
new and old versions in parallel and also have to determine which |
| 62 |
version to use depending on whether the other side is upgraded or |
| 63 |
not. |
| 64 |
|
| 65 |
Let us now have a look at the detailed changes that will be required |
| 66 |
to replace the current IP with a completely new "IP" and to maintain |
| 67 |
the interoperability between the new and the old systems. |
| 68 |
|
| 69 |
1) Border Routers: Border routers have to be upgraded and to provide |
| 70 |
address translation service for IP packets across the boundaries. |
| 71 |
Note that the translation has to be done on the outgoing IP |
| 72 |
packets as well as the in-coming packets to IP hosts. |
| 73 |
|
| 74 |
2) Subnet Routers: Subnet Routers have to be upgraded and have to |
| 75 |
deal with both the new and the old packet formats. |
| 76 |
|
| 77 |
3) Hosts: Hosts have to be upgraded and run both the new and the |
| 78 |
old protocols in parallel. Upgraded hosts also have to determine |
| 79 |
whether the other side is upgraded or not in order to choose the |
| 80 |
correct protocol to use. |
| 81 |
|
| 82 |
4) DNS: The DNS has to be modified to provide mapping for domain |
| 83 |
names and new addresses. |
| 84 |
|
| 85 |
5) ARP/RARP: ARP/RARP have to be modified, and upgraded hosts and |
| 86 |
routers have to deal with both the old and new ARP/RARP packets. |
| 87 |
|
| 88 |
6) ICMP: ICMP has to be modified, and the upgraded routers have to |
| 89 |
be able to generate both both old and new ICMP packets. However, |
| 90 |
it may be impossible for a backbone router to determine |
| 91 |
whether the packet comes from an upgraded host or an IP host but |
| 92 |
translated by the border router. |
| 93 |
|
| 94 |
7) TCP/UDP Checksum: The pseudo headers may have to be modified to |
| 95 |
use the new addresses. |
| 96 |
|
| 97 |
8) FTP: The DATA PORT (PORT) command has to be changed to pass new |
| 98 |
addresses. |
| 99 |
|
| 100 |
In this paper, we argue that an evolutionary approach can extend the |
| 101 |
addressing space yet maintain backward compatibility. The Extended |
| 102 |
Internet Protocol (EIP) we present here can be used as a framework by |
| 103 |
which a new routing and addressing scheme may solve the problem of |
| 104 |
address exhaustion yet maintain maximum backward compatibility to |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Wang [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc1385">RFC 1385</a> EIP November 1992</span> |
| 111 |
|
| 112 |
|
| 113 |
current IP. |
| 114 |
|
| 115 |
EIP has a number of very desirable features: |
| 116 |
|
| 117 |
1) EIP allows the Internet to have virtually unlimited number of |
| 118 |
network numbers and over 10**9 hosts in each network. |
| 119 |
|
| 120 |
2) EIP is flexible to accommodate most routing and addressing |
| 121 |
schemes, such as those proposed in Nimrod [<a href="#ref-8" title=""A New IP Routing and Addressing Architecture"">8</a>], Pip [<a href="#ref-7" title=""Pip: The 'P' Internet Protocol"">7</a>], NSAP [<a href="#ref-9" title=""Guidelines for OSI NSAP Allocation in the Internet"">9</a>] |
| 122 |
and CityCodes [<a href="#ref-10" title=""City Codes: An Alternative Scheme for OSI NSAP Allocation in the Internet"">10</a>]. EIP also allows new fields such as Handling |
| 123 |
Directive [<a href="#ref-7" title=""Pip: The 'P' Internet Protocol"">7</a>] or CI [<a href="#ref-11" title=""Building routers for the routing of tomorrow"">11</a>] to be added. |
| 124 |
|
| 125 |
3) EIP can substantially reduce the amount of modifications to |
| 126 |
current systems and greatly ease the difficulties in transition. |
| 127 |
In particular, it does not require the upgraded hosts and subnet |
| 128 |
routers to run two set of protocols in parallel. |
| 129 |
|
| 130 |
4) EIP requires no changes to all assigned IP addresses and subnet |
| 131 |
structures in local are networks. and requires no modifications |
| 132 |
to ARP/RARP, ICMP, TCP/UDP checksum. |
| 133 |
|
| 134 |
5) EIP can greatly ease the difficulties of transition. During the |
| 135 |
transition period, no upgrade is required to the subnet routers. |
| 136 |
EIP hosts maintain full compatibility with IP hosts within the |
| 137 |
same network, even after the transition period. During the |
| 138 |
transition period, IP hosts can communicate with any hosts in |
| 139 |
other networks via a simple translation service. |
| 140 |
|
| 141 |
In the rest of the paper, IP refers to the current Internet Protocol |
| 142 |
and EIP refers to the Extended Internet Protocol (EIP is pronounced |
| 143 |
as "ape" - a step forward in the evolution :-). |
| 144 |
|
| 145 |
Extended Internet Protocol (EIP) |
| 146 |
|
| 147 |
The EIP header format is shown in Figure 1 and the contents of the |
| 148 |
header follows. |
| 149 |
|
| 150 |
|
| 151 |
|
| 152 |
|
| 153 |
|
| 154 |
|
| 155 |
|
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Wang [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc1385">RFC 1385</a> EIP November 1992</span> |
| 167 |
|
| 168 |
|
| 169 |
0 1 2 3 |
| 170 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 |
| 171 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 172 |
|Version| IHL |Type of Service| Total Length | |
| 173 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 174 |
| Identification |Flags| Fragment Offset | |
| 175 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 176 |
| Time to Live | Protocol | Header Checksum | |
| 177 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 178 |
| Source Host Number | |
| 179 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 180 |
| Destination Host Number | |
| 181 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 182 |
| EIP ID | EIP Ext Length| EIP Extension (variable) | |
| 183 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 184 |
|
| 185 |
Figure 1: EIP Header Format |
| 186 |
|
| 187 |
Version: 4 bits |
| 188 |
|
| 189 |
The Version field is identical to that of IP. This field is set |
| 190 |
purely for compatibility with IP hosts. It is not checked by EIP |
| 191 |
hosts. |
| 192 |
|
| 193 |
IHL: 4 bits |
| 194 |
|
| 195 |
Internet Header Length is identical to that of IP. IHL is set to |
| 196 |
the length of EIP header purely for compatibility with IP. This |
| 197 |
field is not checked by EIP hosts. see below the EIP Extension |
| 198 |
Length field for more details) |
| 199 |
|
| 200 |
Type of Service: 8 bits |
| 201 |
|
| 202 |
The ToS field is identical to that of IP. |
| 203 |
|
| 204 |
Total Length: 16 bits |
| 205 |
|
| 206 |
The Total Length field is identical to that of IP. |
| 207 |
|
| 208 |
Identification: 16 bits |
| 209 |
|
| 210 |
The Identification field is identical to that of IP. |
| 211 |
|
| 212 |
Flags: 3 bits |
| 213 |
|
| 214 |
The Flags field is identical to that of IP. |
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Wang [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc1385">RFC 1385</a> EIP November 1992</span> |
| 223 |
|
| 224 |
|
| 225 |
Fragment Offset: 13 bits |
| 226 |
|
| 227 |
The Fragment Offset field is identical to that of IP. |
| 228 |
|
| 229 |
Time to Live: 8 bits |
| 230 |
|
| 231 |
The Time to Live field is identical to that of IP. |
| 232 |
|
| 233 |
Protocol: 8 bits |
| 234 |
|
| 235 |
The Protocol field is identical to that of IP. |
| 236 |
|
| 237 |
Header Checksum: 16 bits |
| 238 |
|
| 239 |
The Header Checksum field is identical to that of IP. |
| 240 |
|
| 241 |
Source Host Number: 32 bits |
| 242 |
|
| 243 |
The Source Host Number field is used for identifying the |
| 244 |
source host but is unique only within the source network |
| 245 |
(the equivalent of the host portion of the source IP address). |
| 246 |
|
| 247 |
Destination Host Number: 32 bits |
| 248 |
|
| 249 |
The Destination Host Number field is used for identifying the |
| 250 |
destination host but is unique only within the destination network |
| 251 |
(the equivalent of the host portion of the destination IP address). |
| 252 |
|
| 253 |
EIP ID: 8 bits |
| 254 |
|
| 255 |
The EIP ID field equals to 0x8A. The EIP ID value is chosen |
| 256 |
in such a way that, to IP hosts and IP routers, an EIP appears |
| 257 |
to be an IP packet with a new IP option of following parameters: |
| 258 |
|
| 259 |
COPY CLASS NUMBER LENGTH DESCRIPTION |
| 260 |
---- ----- ------ ------ ----------- |
| 261 |
1 0 TBD var |
| 262 |
|
| 263 |
Option: Type=TBD |
| 264 |
|
| 265 |
EIP Extension Length: 8 bits |
| 266 |
|
| 267 |
The EIP Extension Length field indicates the total length |
| 268 |
of the EIP ID field, EIP Extension Length field and the |
| 269 |
EIP Extension field in octets. The maximum length that the |
| 270 |
IHL field above can specify is 60 bytes, which is considered |
| 271 |
too short in future. EIP hosts actually use the EIP Extension |
| 272 |
Length field to calculate the total header length: |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Wang [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc1385">RFC 1385</a> EIP November 1992</span> |
| 279 |
|
| 280 |
|
| 281 |
The total header length = EIP Extension Length + 20. |
| 282 |
|
| 283 |
The maximum header length of an EIP packet is then 276 bytes. |
| 284 |
|
| 285 |
EIP Extension: variable |
| 286 |
|
| 287 |
The EIP Extension field holds the Source Network Number, |
| 288 |
Destination Network Number and other fields. The format |
| 289 |
of the Extension field is not specified here. In its simplest |
| 290 |
form, it can be used to hold two fixed size fields as the |
| 291 |
Source Network Number and Destination Network Number as the |
| 292 |
extension to the addressing space. Since the Extension |
| 293 |
field is variable in length, it can accommodate almost any |
| 294 |
routing and addressing schemes. For example, the Extension |
| 295 |
field can be used to hold "Routing Directive" etc specified |
| 296 |
in Pip [<a href="#ref-7" title=""Pip: The 'P' Internet Protocol"">7</a>] or "Endpoint IDs" suggested in Nimrod [<a href="#ref-8" title=""A New IP Routing and Addressing Architecture"">8</a>], or the |
| 297 |
"CityCode" [<a href="#ref-10" title=""City Codes: An Alternative Scheme for OSI NSAP Allocation in the Internet"">10</a>]. It can also hold other fields such as the |
| 298 |
"Handling Directive" [<a href="#ref-7" title=""Pip: The 'P' Internet Protocol"">7</a>] or "Connectionless ID" [<a href="#ref-11" title=""Building routers for the routing of tomorrow"">11</a>]. |
| 299 |
|
| 300 |
EIP achieves maximum backward compatibility with IP by making the |
| 301 |
extended space appear to be an IP option to the IP hosts and routers. |
| 302 |
|
| 303 |
When an IP host receives an EIP packets, the EIP Extension field is |
| 304 |
safely ignored as it appears to the IP hosts as an new, therefore an |
| 305 |
unknown, IP option. As a result, there is no need for translation |
| 306 |
for in-coming EIP packets destined to IP hosts and there is also no |
| 307 |
need for subnet routers to be upgraded during the transition period |
| 308 |
see later section for more details). |
| 309 |
|
| 310 |
EIP hosts or routers can, however, determine whether a packet is an |
| 311 |
IP packet or an EIP packet by examining the EIP ID field, whose |
| 312 |
position is fixed in the header. |
| 313 |
|
| 314 |
The EIP Extension field holds the Source and Destination Network |
| 315 |
Numbers, which are only used for communications between different |
| 316 |
networks. For communications within the same network, the Network |
| 317 |
Numbers may be omitted. When the Extension field is omitted, there is |
| 318 |
little difference between an IP packet and an EIP packet. Therefore, |
| 319 |
EIP hosts can maintain completely compatibility with IP hosts within |
| 320 |
one network. |
| 321 |
|
| 322 |
In EIP, the Network Numbers and Host Numbers are separate and the IP |
| 323 |
address field is used for the Host Number in EIP. There are a number |
| 324 |
of advantages: |
| 325 |
|
| 326 |
1) It maintains full compatibility between IP hosts and EIP hosts |
| 327 |
for communications within one network. Note that the Network |
| 328 |
Number is not needed for communications within one network. A |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Wang [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc1385">RFC 1385</a> EIP November 1992</span> |
| 335 |
|
| 336 |
|
| 337 |
host can omit the Extension field if it does not need any other |
| 338 |
information in the Extension field, when it communicates with |
| 339 |
another host within the same network. |
| 340 |
|
| 341 |
2) It allows the IP subnet routers to route EIP packet by treating |
| 342 |
the Host Number as the IP address during the transition period, |
| 343 |
therefore the subnet routers are not required to be updated |
| 344 |
along the border routers. |
| 345 |
|
| 346 |
3) It allows ARP/RARP to work with both EIP and IP hosts without |
| 347 |
any modifications. |
| 348 |
|
| 349 |
4) It allows the translation at the border routers much easier. |
| 350 |
During the transition period when the IP addresses are still |
| 351 |
unique, the network portion of the IP addresses can be directly |
| 352 |
extracted and mapped to EIP Network Numbers. |
| 353 |
|
| 354 |
Modifications to IP Systems |
| 355 |
|
| 356 |
In this section, we outline the modifications to the IP systems that |
| 357 |
are needed for transition to EIP. Because of the similarity between |
| 358 |
the EIP and IP, the amount of modifications needed to current systems |
| 359 |
are substantially reduced. |
| 360 |
|
| 361 |
1) Network Numbers: Each network has to be assigned a new EIP Network |
| 362 |
Number based on the addressing scheme used. The mapping |
| 363 |
between the IP network numbers and the EIP Network Numbers can |
| 364 |
be used for translation service (see below). |
| 365 |
|
| 366 |
2) Host Numbers: There is no need for assigning EIP Host Numbers. |
| 367 |
All existing hosts can use their current IP addresses as their |
| 368 |
EIP Host Numbers. New machines may be allocated any number from |
| 369 |
the 32-bit Host Number space since the structure posed on IP |
| 370 |
addressing is no longer necessary. However, during the transition, |
| 371 |
allocation of EIP Host Numbers should still follow the IP |
| 372 |
addressing rule, so that the EIP Host Numbers are still globally |
| 373 |
unique and can still be interpreted as IP addresses. This will |
| 374 |
allow a more gradual transition to EIP (see below). |
| 375 |
|
| 376 |
3) Translation Service: During the transition period when the EIP |
| 377 |
Host Numbers are still unique, an address translation service |
| 378 |
can be provided to IP hosts that need communicate with hosts in |
| 379 |
other networks cross the upgraded backbone networks. The |
| 380 |
translation service can be provided by the border routers. When a |
| 381 |
border router receives an IP packet, it obtains the Destination |
| 382 |
Network Number by looking up in the mapping table between IP |
| 383 |
network numbers and EIP Network Numbers. The border router then |
| 384 |
adds the Extension field with the Source and Destination Network |
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Wang [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc1385">RFC 1385</a> EIP November 1992</span> |
| 391 |
|
| 392 |
|
| 393 |
Numbers into the packet, and forwards to the backbone networks. |
| 394 |
It is only necessary to translate the out-going IP packets to |
| 395 |
the EIP packets. There is no need to translate the EIP packets |
| 396 |
back to IP packets even when they are destined to IP hosts. |
| 397 |
This is because that the Extension field in the EIP packets |
| 398 |
appears to IP hosts just an unknown IP option and is ignored by |
| 399 |
the IP hosts during the processing. |
| 400 |
|
| 401 |
4) Border Routers: The new EIP Extension has to be implemented and |
| 402 |
routing has to be done based on the Network Number in the EIP |
| 403 |
Extension field. The border routers may have to provide the |
| 404 |
translation service for out-going IP packets during the transition |
| 405 |
period. |
| 406 |
|
| 407 |
5) Subnet Routers: No modifications are required during the transition |
| 408 |
period when EIP Host Numbers (which equals to the IP |
| 409 |
addresses) are still globally unique. The subnet routing is carried |
| 410 |
out based on the EIP Host Numbers and when the EIP Host |
| 411 |
IDs are still unique, subnet routers can determine, by treating |
| 412 |
the EIP Host Number as the IP addresses, whether a packet is |
| 413 |
destined to remote networks or not and forward correctly. The |
| 414 |
Extension field in the EIP packets also appear to the IP subnet |
| 415 |
routers an unknown IP option and is ignored in the processing. |
| 416 |
However, subnet routers eventually have to implement the EIP |
| 417 |
Extension and carry out routing based on Network Numbers when |
| 418 |
EIP Host Numbers are no longer globally unique. |
| 419 |
|
| 420 |
6) Hosts: The EIP Extension has to be implemented. routing has to |
| 421 |
be done based on the Network Number in the EIP Extension field, |
| 422 |
and also based on the Host Number and subnet mask if subnetting |
| 423 |
is used. IP hosts may communication with any hosts within the |
| 424 |
same network at any time. During the transition period when the |
| 425 |
EIP Host Numbers are still unique, IP hosts can communicate with |
| 426 |
any hosts in other network via the translation service. |
| 427 |
|
| 428 |
7) DNS: A new resource record (RR) type "N" has to be added for EIP |
| 429 |
Network Numbers. The RR type "A", currently used for IP |
| 430 |
addresses, can still be used for EIP Host Numbers. RR type "N" |
| 431 |
entries have to be added and RR type "PTR" to be updated. All |
| 432 |
other entries remain unchanged. |
| 433 |
|
| 434 |
8) ARP/RARP: No modifications are required. The ARP and RARP are |
| 435 |
used for mapping between EIP Host Numbers and physical |
| 436 |
addresses. |
| 437 |
|
| 438 |
9) ICMP: No modifications are required. |
| 439 |
|
| 440 |
10) TCP/UDP Checksum: No modifications are required. The pseudo |
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Wang [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc1385">RFC 1385</a> EIP November 1992</span> |
| 447 |
|
| 448 |
|
| 449 |
header includes the EIP Source and Destination IDs instead of |
| 450 |
the source and destination IP addresses. |
| 451 |
|
| 452 |
11) FTP: No modifications are required during the transition period |
| 453 |
when the IP hosts can still communicate with hosts in other |
| 454 |
networks via the translation service. After the transition period, |
| 455 |
however, the "DATA Port (Port)" command has to be modified to |
| 456 |
pass the port number only and ignore the IP address. A new FTP |
| 457 |
command may be created to pass both the port number and the EIP |
| 458 |
address to allow a third party to be involved in the file |
| 459 |
transfer. |
| 460 |
|
| 461 |
Transition to EIP |
| 462 |
|
| 463 |
In this section, we outline a plan for transition to EIP. |
| 464 |
|
| 465 |
EIP can greatly reduce the complexity of transition. In particular, |
| 466 |
there is no need for the updated hosts and subnet routers to run two |
| 467 |
protocols in parallel in order to achieve interoperability between |
| 468 |
old and new systems. During the transition, IP hosts can still |
| 469 |
communicate with any machines in the same network without any |
| 470 |
changes. When the EIP Host Numbers (i.e., the 32-bit IP addresses) |
| 471 |
are still globally unique, IP hosts can contact hosts in other |
| 472 |
networks via translation service provided in the border routers. |
| 473 |
|
| 474 |
The transition goes as follows: |
| 475 |
|
| 476 |
Phase 0: |
| 477 |
a) Choose an addressing and routing scheme for the Internet. |
| 478 |
b) Implement the routing protocol. |
| 479 |
c) Assign new Network Numbers to existing networks. |
| 480 |
|
| 481 |
Phase 1: |
| 482 |
a) Update all backbone routers and border routers. |
| 483 |
b) Update DNS servers. |
| 484 |
c) Start translation service. |
| 485 |
|
| 486 |
Phase 2: |
| 487 |
a) Update first the key hosts such as mail servers, DNS servers, |
| 488 |
FTP servers and central machines. |
| 489 |
b) Update gradually the rest of the hosts. |
| 490 |
|
| 491 |
Phase 3: |
| 492 |
a) Update subnet routers |
| 493 |
b) Withdraw the translation service. |
| 494 |
|
| 495 |
The translation service can be provided as long as the Host IDs |
| 496 |
(i.e., the 32-bit IP address) are still globally unique. When the IP |
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Wang [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc1385">RFC 1385</a> EIP November 1992</span> |
| 503 |
|
| 504 |
|
| 505 |
address space is exhausted, the translation service will be withdrawn |
| 506 |
and the remaining IP hosts can only communicate with hosts within the |
| 507 |
the same network. At the same time, networks can use any numbers in |
| 508 |
the 32-bit space for addressing their hosts. |
| 509 |
|
| 510 |
Related Work |
| 511 |
|
| 512 |
A recent proposal called IPAE by Hinden and Crocker also attempts to |
| 513 |
minimize the modifications to the current IP system yet to extend the |
| 514 |
addressing space [<a href="#ref-12" title=""A Proposal for IP Address Encapsulation (IPAE): A Compatible Version of IP with Large Addresses"">12</a>]. IPAE uses encapsulation so that the extended |
| 515 |
space is carried as IP data. However, it has been found that the 64 |
| 516 |
bits IP data returned by an ICMP packet is too small to hold the |
| 517 |
Global IP addresses. Thus, when a router receives an ICMP generated |
| 518 |
by an old IP host, it is not able to convert it into a proper ICMP |
| 519 |
packet. More details can be found in [<a href="#ref-13" title=""Re: Note on implementing IPAE"">13</a>]. |
| 520 |
|
| 521 |
Discussions |
| 522 |
|
| 523 |
EIP does not necessary increase the header length significantly as |
| 524 |
most of the fields in the current IP will be still needed in the new |
| 525 |
internet protocol. There are debates as to whether fragmentation and |
| 526 |
header checksum are necessary in the new internet protocol but no |
| 527 |
consensus has been reached. |
| 528 |
|
| 529 |
EIP assumes that IP hosts and routers ignore unknown IP option |
| 530 |
silently as required by [<a href="#ref-15" title=""Requirements for Internet Hosts -- Communication Layers"">15</a>,<a href="#ref-16" title=""Requirements for IP Routers"">16</a>]. Some people have expressed some |
| 531 |
concerns as to whether current IP routers and hosts in the Internet |
| 532 |
can deal with unknown IP options properly. |
| 533 |
|
| 534 |
In order to look into the issues further, we carried out a number of |
| 535 |
experiments over the use of IP option. We selected 35 hosts over 30 |
| 536 |
countries across the Internet. A TCP test program (based on ttcp.c) |
| 537 |
then transmitted data to the echo port (tcp port 7) of each of the |
| 538 |
hosts. Two tests were carried out for each host, one with an unknown |
| 539 |
option (type 0x8A, length 40 bytes) and the other without any |
| 540 |
options. |
| 541 |
|
| 542 |
It is difficult to ensure that the conditions under which the two |
| 543 |
tests run are identical but we tried to make them as close as |
| 544 |
possible. The two tests (test-opt and test-noopt) run on the same |
| 545 |
machine a Sun4) in parallel, i.e., "test-opt& ; test-noopt&" and then |
| 546 |
again in the reverse order, i.e., "test-noopt& ; test-opt&", so each |
| 547 |
test pair actually run twice. Each host was ping'ed before the tests |
| 548 |
so that the domain name information was cached before the name |
| 549 |
lookup. |
| 550 |
|
| 551 |
The experiments were carried out at three sites: UCL, Bellcore and |
| 552 |
Cambridge University. The tcp echo throughput (KB/Sec) results are |
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Wang [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc1385">RFC 1385</a> EIP November 1992</span> |
| 559 |
|
| 560 |
|
| 561 |
listed in Appendix. |
| 562 |
|
| 563 |
The results show that the IP option was dealt with properly and there |
| 564 |
is no visible performance difference under the test setup. |
| 565 |
|
| 566 |
References |
| 567 |
|
| 568 |
[<a id="ref-1">1</a>] Chiappa, N., <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&q=inurl:draft-+%22The+IP+Addressing+Issue%22'>"The IP Addressing Issue"</a>, Work in Progress, October |
| 569 |
1990. |
| 570 |
|
| 571 |
[<a id="ref-2">2</a>] Clark, D., Chapin, L., Cerf, V., Braden, R., and R. Hobby, |
| 572 |
"Towards the Future Architecture", <a href="./rfc1287">RFC 1287</a>, MIT, BBN, CNRI, ISI, |
| 573 |
UCDavis , December 1991. |
| 574 |
|
| 575 |
[<a id="ref-3">3</a>] Solensky, F. and F. Kastenholz, "A Revision to IP Address |
| 576 |
Classifications", Work in Progress, March 1992. |
| 577 |
|
| 578 |
[<a id="ref-4">4</a>] Fuller, V., Li, T., Yu, J., and K. Varadhan, "Supernetting: an |
| 579 |
Address Assignment and Aggregation Strategy", <a href="./rfc1338">RFC 1338</a>, BARRNet, |
| 580 |
cisco, Merit, OARnet, June 1992. |
| 581 |
|
| 582 |
[<a id="ref-5">5</a>] Wang, Z., and J. Crowcroft, "A Two-Tier Address Structure for the |
| 583 |
Internet: a solution to the problem of address space exhaustion", |
| 584 |
<a href="./rfc1335">RFC 1335</a>, University College London, May 1992. |
| 585 |
|
| 586 |
[<a id="ref-6">6</a>] Callon, R., "TCP and UDP with Bigger Addresses (TUBA), a Simple |
| 587 |
Proposal for Internet Addressing and Routing", <a href="./rfc1347">RFC 1347</a>, DEC, |
| 588 |
June 1992. |
| 589 |
|
| 590 |
[<a id="ref-7">7</a>] Tsuchiya, P., <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&q=inurl:draft-+%22Pip%3A+The+%27P%27+Internet+Protocol%22'>"Pip: The 'P' Internet Protocol"</a>, Work in Progress, |
| 591 |
May 1992 |
| 592 |
|
| 593 |
[<a id="ref-8">8</a>] Chiappa N., <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&q=inurl:draft-+%22A+New+IP+Routing+and+Addressing+Architecture%22'>"A New IP Routing and Addressing Architecture"</a>, Work |
| 594 |
in Progress, 1992. |
| 595 |
|
| 596 |
[<a id="ref-9">9</a>] Colella, R., Gardner, E., and R. Callon, "Guidelines for OSI NSAP |
| 597 |
Allocation in the Internet" <a href="./rfc1237">RFC 1237</a>, NIST, Mitre, DEC, July |
| 598 |
1991. |
| 599 |
|
| 600 |
[<a id="ref-10">10</a>] Deering, S., "City Codes: An Alternative Scheme for OSI NSAP |
| 601 |
Allocation in the Internet", Work in Progress, January 1992. |
| 602 |
|
| 603 |
[<a id="ref-11">11</a>] Clark, D., "Building routers for the routing of tomorrow", in his |
| 604 |
message to [email protected], 14 July 1992. |
| 605 |
|
| 606 |
[<a id="ref-12">12</a>] Hinden, R., and D. Crocker, "A Proposal for IP Address |
| 607 |
Encapsulation (IPAE): A Compatible Version of IP with Large |
| 608 |
Addresses", Work in Progress, July 1992. |
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Wang [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc1385">RFC 1385</a> EIP November 1992</span> |
| 615 |
|
| 616 |
|
| 617 |
[<a id="ref-13">13</a>] Partridge, C., "Re: Note on implementing IPAE", in his message to |
| 618 |
[email protected], 17 July 1992. |
| 619 |
|
| 620 |
[<a id="ref-14">14</a>] Deering, S., <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&q=inurl:draft-+%22SIP%3A+Simple+Internet+Protocol%22'>"SIP: Simple Internet Protocol"</a>, Work in Progress, |
| 621 |
September 1992. |
| 622 |
|
| 623 |
[<a id="ref-15">15</a>] Braden, R., Editor, "Requirements for Internet Hosts |
| 624 |
-- Communication Layers", <a href="./rfc1122">RFC 1122</a>, ISI, October 1989. |
| 625 |
|
| 626 |
[<a id="ref-16">16</a>] Almquist, P., Editor, <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&q=inurl:draft-+%22Requirements+for+IP+Routers%22'>"Requirements for IP Routers"</a>, Work in |
| 627 |
Progress, October 1991. |
| 628 |
|
| 629 |
Appendix |
| 630 |
|
| 631 |
Throughput Test from UCL (sartre.cs.ucl.ac.uk) |
| 632 |
|
| 633 |
Destination Host test-noopt test-opt |
| 634 |
------------------- ---------- --------- |
| 635 |
oliver.cs.mcgill.ca 1.128756 1.285345 |
| 636 |
oliver.cs.mcgill.ca 1.063096 1.239709 |
| 637 |
bertha.cc.und.ac.za 0.094336 0.043917 |
| 638 |
bertha.cc.und.ac.za 0.075681 0.057120 |
| 639 |
vnet3.vub.ac.be 2.090622 2.228181 |
| 640 |
vnet3.vub.ac.be 1.781374 1.692740 |
| 641 |
itdsrv1.ul.ie 1.937596 2.062579 |
| 642 |
itdsrv1.ul.ie 1.928313 1.936784 |
| 643 |
sunic.sunet.se 11.064797 11.724055 |
| 644 |
sunic.sunet.se 10.861720 10.840306 |
| 645 |
pascal.acm.org 2.463790 0.810133 |
| 646 |
pascal.acm.org 1.619088 0.860198 |
| 647 |
iti.gov.sg 1.565320 1.983795 |
| 648 |
iti.gov.sg 1.564788 1.921803 |
| 649 |
rzusuntk.unizh.ch 9.903805 11.335920 |
| 650 |
rzusuntk.unizh.ch 9.597806 10.678098 |
| 651 |
funet.fi 9.897876 9.382925 |
| 652 |
funet.fi 10.487118 11.023745 |
| 653 |
odin.diku.dk 5.851407 5.482946 |
| 654 |
odin.diku.dk 5.992257 6.243283 |
| 655 |
cphkvx.cphk.hk 0.758044 0.844406 |
| 656 |
cphkvx.cphk.hk 0.784532 0.745606 |
| 657 |
bootes.cus.cam.ac.uk 28.341705 29.655824 |
| 658 |
bootes.cus.cam.ac.uk 24.804125 23.240990 |
| 659 |
pesach.jct.ac.il 1.045922 1.115802 |
| 660 |
pesach.jct.ac.il 1.330429 0.978184 |
| 661 |
sun1.sara.nl 10.546733 11.500778 |
| 662 |
sun1.sara.nl 9.624833 10.214136 |
| 663 |
cocos.fuw.edu.pl 1.747777 1.702324 |
| 664 |
cocos.fuw.edu.pl 1.676151 1.716435 |
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Wang [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc1385">RFC 1385</a> EIP November 1992</span> |
| 671 |
|
| 672 |
|
| 673 |
apple.com 4.449559 4.145081 |
| 674 |
apple.com 6.431675 5.520443 |
| 675 |
gorgon.tf.tele.no 1.199810 1.374546 |
| 676 |
gorgon.tf.tele.no 0.508642 0.993261 |
| 677 |
kogwy.cc.keio.ac.jp 3.626448 3.249590 |
| 678 |
kogwy.cc.keio.ac.jp 3.913777 4.094849 |
| 679 |
exu.inf.puc-rio.br 1.913925 1.795235 |
| 680 |
exu.inf.puc-rio.br 1.154936 1.114775 |
| 681 |
inria.inria.fr 2.299561 0.599665 |
| 682 |
inria.inria.fr 1.219282 0.873672 |
| 683 |
kum.kaist.ac.kr 0.252704 0.254199 |
| 684 |
kum.kaist.ac.kr 0.236196 0.172367 |
| 685 |
sunipc1.labein.es 1.398777 1.243588 |
| 686 |
sunipc1.labein.es 0.876177 0.602964 |
| 687 |
wifosv.wsr.ac.at 0.531153 0.803387 |
| 688 |
wifosv.wsr.ac.at 0.773935 0.557798 |
| 689 |
uunet.uu.net 7.813556 6.764543 |
| 690 |
uunet.uu.net 7.969203 6.657325 |
| 691 |
infnsun.aquila.infn.it 2.321197 2.402477 |
| 692 |
infnsun.aquila.infn.it 2.400196 2.695016 |
| 693 |
muttley.fc.ul.pt 0.545775 0.434672 |
| 694 |
muttley.fc.ul.pt 0.284124 0.266017 |
| 695 |
dmssyd.syd.dms.csiro.au 2.734685 2.857545 |
| 696 |
dmssyd.syd.dms.csiro.au 1.168154 1.462789 |
| 697 |
hamlet.caltech.edu 2.552804 2.897286 |
| 698 |
hamlet.caltech.edu 3.839141 2.407945 |
| 699 |
sztaki.hu 0.294196 0.403697 |
| 700 |
sztaki.hu 0.236260 0.388755 |
| 701 |
menvax.restena.lu 0.465066 0.515361 |
| 702 |
menvax.restena.lu 0.358646 0.511985 |
| 703 |
nctu.edu.tw 0.484372 0.816722 |
| 704 |
nctu.edu.tw 0.705733 1.109228 |
| 705 |
xalapa.lania.mx 0.899529 0.822544 |
| 706 |
xalapa.lania.mx 1.150058 0.881713 |
| 707 |
truth.waikato.ac.nz 1.438481 1.993749 |
| 708 |
truth.waikato.ac.nz 1.325041 1.833999 |
| 709 |
|
| 710 |
|
| 711 |
|
| 712 |
|
| 713 |
|
| 714 |
|
| 715 |
|
| 716 |
|
| 717 |
|
| 718 |
|
| 719 |
|
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Wang [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc1385">RFC 1385</a> EIP November 1992</span> |
| 727 |
|
| 728 |
|
| 729 |
Throughput Test from Bellcore (latour.bellcore.com) |
| 730 |
|
| 731 |
Destination Host test-noopt test-opt |
| 732 |
------------------ ---------- --------- |
| 733 |
oliver.cs.mcgill.ca 1.820014 2.128104 |
| 734 |
oliver.cs.mcgill.ca 1.979981 1.866815 |
| 735 |
bertha.cc.und.ac.za 0.099289 0.035877 |
| 736 |
bertha.cc.und.ac.za 0.118627 0.103763 |
| 737 |
vnet3.vub.ac.be 0.368476 0.694463 |
| 738 |
vnet3.vub.ac.be 0.443269 0.644050 |
| 739 |
itdsrv1.ul.ie 0.721444 0.960068 |
| 740 |
itdsrv1.ul.ie 0.713952 0.953275 |
| 741 |
sunic.sunet.se 2.989907 2.956766 |
| 742 |
sunic.sunet.se 2.100563 2.010292 |
| 743 |
pascal.acm.org 2.487185 3.896253 |
| 744 |
pascal.acm.org 1.944085 4.269323 |
| 745 |
iti.gov.sg 2.401733 2.735445 |
| 746 |
iti.gov.sg 2.950990 2.793121 |
| 747 |
rzusuntk.unizh.ch 4.094820 3.618023 |
| 748 |
rzusuntk.unizh.ch 2.952650 2.245001 |
| 749 |
funet.fi 6.703408 5.928008 |
| 750 |
funet.fi 7.389722 5.815122 |
| 751 |
odin.diku.dk 2.094152 2.450695 |
| 752 |
odin.diku.dk 5.362362 4.690722 |
| 753 |
cphkvx.cphk.hk 0.092698 0.106880 |
| 754 |
cphkvx.cphk.hk 0.496394 0.681994 |
| 755 |
bootes.cus.cam.ac.uk 2.632951 2.631322 |
| 756 |
bootes.cus.cam.ac.uk 3.717170 1.335914 |
| 757 |
pesach.jct.ac.il 0.684029 0.921621 |
| 758 |
pesach.jct.ac.il 0.390263 1.095265 |
| 759 |
sun1.sara.nl 3.186035 2.325166 |
| 760 |
sun1.sara.nl 3.053797 3.081236 |
| 761 |
cocos.fuw.edu.pl 0.154405 0.124795 |
| 762 |
cocos.fuw.edu.pl 0.120283 0.105825 |
| 763 |
apple.com 12.588979 12.957880 |
| 764 |
apple.com 13.861733 12.211125 |
| 765 |
gorgon.tf.tele.no 1.280217 1.112675 |
| 766 |
gorgon.tf.tele.no 0.243205 0.631096 |
| 767 |
kogwy.cc.keio.ac.jp 6.249789 5.075968 |
| 768 |
kogwy.cc.keio.ac.jp 3.387490 4.583511 |
| 769 |
exu.inf.puc-rio.br 2.089536 2.233711 |
| 770 |
exu.inf.puc-rio.br 2.476758 2.249439 |
| 771 |
inria.inria.fr 0.653974 0.866246 |
| 772 |
inria.inria.fr 0.739127 1.130521 |
| 773 |
kum.kaist.ac.kr 1.541682 1.312546 |
| 774 |
kum.kaist.ac.kr 0.906632 1.042793 |
| 775 |
sunipc1.labein.es 0.101496 0.091456 |
| 776 |
sunipc1.labein.es 0.054245 0.101585 |
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Wang [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc1385">RFC 1385</a> EIP November 1992</span> |
| 783 |
|
| 784 |
|
| 785 |
wifosv.wsr.ac.at 1.044443 0.369528 |
| 786 |
wifosv.wsr.ac.at 0.596935 0.870377 |
| 787 |
uunet.uu.net 9.530348 8.999789 |
| 788 |
uunet.uu.net 8.941888 6.075660 |
| 789 |
infnsun.aquila.infn.it 1.619418 1.569645 |
| 790 |
infnsun.aquila.infn.it 1.156780 1.158000 |
| 791 |
muttley.fc.ul.pt 0.353632 0.416126 |
| 792 |
muttley.fc.ul.pt 0.221522 0.155505 |
| 793 |
dmssyd.syd.dms.csiro.au 3.433901 3.272839 |
| 794 |
dmssyd.syd.dms.csiro.au 3.408975 3.130188 |
| 795 |
hamlet.caltech.edu 5.367756 6.325031 |
| 796 |
hamlet.caltech.edu 4.828718 5.676571 |
| 797 |
sztaki.hu 0.301120 0.362481 |
| 798 |
sztaki.hu 0.253222 0.519892 |
| 799 |
menvax.restena.lu 0.364221 0.480789 |
| 800 |
menvax.restena.lu 0.456882 0.580778 |
| 801 |
nctu.edu.tw 0.246523 1.199412 |
| 802 |
nctu.edu.tw 0.423476 0.630833 |
| 803 |
xalapa.lania.mx 0.748642 0.607284 |
| 804 |
xalapa.lania.mx 0.716781 0.643030 |
| 805 |
truth.waikato.ac.nz 2.197595 2.072601 |
| 806 |
truth.waikato.ac.nz 2.489748 2.186684 |
| 807 |
|
| 808 |
|
| 809 |
|
| 810 |
|
| 811 |
|
| 812 |
|
| 813 |
|
| 814 |
|
| 815 |
|
| 816 |
|
| 817 |
|
| 818 |
|
| 819 |
|
| 820 |
|
| 821 |
|
| 822 |
|
| 823 |
|
| 824 |
|
| 825 |
|
| 826 |
|
| 827 |
|
| 828 |
|
| 829 |
|
| 830 |
|
| 831 |
|
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Wang [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc1385">RFC 1385</a> EIP November 1992</span> |
| 839 |
|
| 840 |
|
| 841 |
Throughput Test from Cam U (cus.cam.ac.uk) |
| 842 |
|
| 843 |
Destination Host test-noopt test-opt |
| 844 |
------------------ ---------- --------- |
| 845 |
oliver.cs.mcgill.ca 1.128756 1.285345 |
| 846 |
oliver.cs.mcgill.ca 1.063096 1.239709 |
| 847 |
bertha.cc.und.ac.za 0.031218 0.031221 |
| 848 |
bertha.cc.und.ac.za 0.034405 0.034925 |
| 849 |
vnet3.vub.ac.be 0.568487 0.731320 |
| 850 |
vnet3.vub.ac.be 0.558238 0.581415 |
| 851 |
itdsrv1.ul.ie 1.064302 1.284707 |
| 852 |
itdsrv1.ul.ie 0.852089 1.025779 |
| 853 |
sunic.sunet.se 7.179942 6.270326 |
| 854 |
sunic.sunet.se 5.772485 6.689160 |
| 855 |
pascal.acm.org 1.661248 1.726725 |
| 856 |
pascal.acm.org 1.557839 1.428193 |
| 857 |
iti.gov.sg 0.600616 0.926690 |
| 858 |
iti.gov.sg 0.772887 0.956636 |
| 859 |
rzusuntk.unizh.ch 3.645913 4.504969 |
| 860 |
rzusuntk.unizh.ch 1.853503 2.671272 |
| 861 |
funet.fi 4.190147 3.421110 |
| 862 |
funet.fi 2.270988 3.789678 |
| 863 |
odin.diku.dk 1.361227 0.993901 |
| 864 |
odin.diku.dk 1.977774 2.415716 |
| 865 |
cphkvx.cphk.hk 1.173451 1.298421 |
| 866 |
cphkvx.cphk.hk 1.151376 1.184210 |
| 867 |
bootes.cus.cam.ac.uk 269.589141 238.920081 |
| 868 |
bootes.cus.cam.ac.uk 331.203020 293.556436 |
| 869 |
pesach.jct.ac.il 0.343598 0.492202 |
| 870 |
pesach.jct.ac.il 0.582809 0.930958 |
| 871 |
sun1.sara.nl 1.529277 1.470571 |
| 872 |
sun1.sara.nl 0.896041 0.894923 |
| 873 |
cocos.fuw.edu.pl 0.131180 0.142239 |
| 874 |
cocos.fuw.edu.pl 0.137697 0.148895 |
| 875 |
apple.com 1.330794 0.453590 |
| 876 |
apple.com 0.856476 0.714661 |
| 877 |
gorgon.tf.tele.no 0.094793 0.099981 |
| 878 |
gorgon.tf.tele.no 0.167257 0.151625 |
| 879 |
kogwy.cc.keio.ac.jp 0.154681 0.178868 |
| 880 |
kogwy.cc.keio.ac.jp 1.095814 0.871496 |
| 881 |
exu.inf.puc-rio.br 0.454272 0.384484 |
| 882 |
exu.inf.puc-rio.br 0.705198 0.690708 |
| 883 |
inria.inria.fr 0.149511 0.150021 |
| 884 |
inria.inria.fr 0.071125 0.077257 |
| 885 |
kum.kaist.ac.kr 0.721184 0.549511 |
| 886 |
kum.kaist.ac.kr 0.250285 0.296195 |
| 887 |
sunipc1.labein.es 0.519284 0.491745 |
| 888 |
sunipc1.labein.es 0.990174 1.009475 |
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Wang [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc1385">RFC 1385</a> EIP November 1992</span> |
| 895 |
|
| 896 |
|
| 897 |
wifosv.wsr.ac.at 0.360751 0.418554 |
| 898 |
wifosv.wsr.ac.at 0.344268 0.326605 |
| 899 |
uunet.uu.net 4.247430 3.305592 |
| 900 |
uunet.uu.net 3.139251 2.945469 |
| 901 |
infnsun.aquila.infn.it 0.480731 0.782631 |
| 902 |
infnsun.aquila.infn.it 0.230471 0.292273 |
| 903 |
muttley.fc.ul.pt 0.239624 0.334286 |
| 904 |
muttley.fc.ul.pt 0.586156 0.419485 |
| 905 |
dmssyd.syd.dms.csiro.au 3.630623 3.607504 |
| 906 |
dmssyd.syd.dms.csiro.au 1.743162 2.994665 |
| 907 |
hamlet.caltech.edu 5.897946 4.650703 |
| 908 |
hamlet.caltech.edu 5.118200 5.622022 |
| 909 |
sztaki.hu 0.338358 0.225206 |
| 910 |
sztaki.hu 0.113328 0.112637 |
| 911 |
menvax.restena.lu 0.224967 0.359237 |
| 912 |
menvax.restena.lu 0.452945 0.472345 |
| 913 |
nctu.edu.tw 2.549709 2.037245 |
| 914 |
nctu.edu.tw 2.229093 2.469851 |
| 915 |
xalapa.lania.mx 0.713586 0.810107 |
| 916 |
xalapa.lania.mx 0.612278 0.731705 |
| 917 |
truth.waikato.ac.nz 1.438481 1.993749 |
| 918 |
truth.waikato.ac.nz 1.325041 1.833999 |
| 919 |
|
| 920 |
Security Considerations |
| 921 |
|
| 922 |
Security issues are not discussed in this memo. |
| 923 |
|
| 924 |
Author's Address |
| 925 |
|
| 926 |
Zheng Wang |
| 927 |
Dept of Computer Science |
| 928 |
University College London |
| 929 |
London WC1E 6BT, UK |
| 930 |
|
| 931 |
EMail: [email protected] |
| 932 |
|
| 933 |
|
| 934 |
|
| 935 |
|
| 936 |
|
| 937 |
|
| 938 |
|
| 939 |
|
| 940 |
|
| 941 |
|
| 942 |
|
| 943 |
|
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
Wang [Page 17] |
| 949 |
</pre> |