| 1 |
<pre>Network Working Group K. Siyan |
| 2 |
Request for Comments: 1365 Siyan Consulting Services |
| 3 |
September 1992 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">An IP Address Extension Proposal</span> |
| 7 |
|
| 8 |
Status of This Memo |
| 9 |
|
| 10 |
This memo provides information for the Internet community. It does |
| 11 |
not specify an Internet standard. Distribution of this memo is |
| 12 |
unlimited. |
| 13 |
|
| 14 |
Abstract |
| 15 |
|
| 16 |
This RFC suggests an extension to the IP protocol to solve the |
| 17 |
shortage of IP address problem, and requests discussion and |
| 18 |
suggestions for improvements. |
| 19 |
|
| 20 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction and Background</span> |
| 21 |
|
| 22 |
The Internet community has a well-developed, mature set of protocols |
| 23 |
that have been quite successful in providing network and transport |
| 24 |
services to users. However, because of the spectacular success of the |
| 25 |
TCP/IP protocols and the number of networks that desire connection to |
| 26 |
the Internet, there is a shortage of network numbers that can be |
| 27 |
assigned. |
| 28 |
|
| 29 |
The current network addressing scheme uses a 32-bit IP address that |
| 30 |
has a network part and a local address part. The division between |
| 31 |
the network part and the local address part has been defined in terms |
| 32 |
of 5 address classes: class A, B, C, D, E. Of these, only class A, |
| 33 |
B, C addresses are assigned to hosts. Class D is used for |
| 34 |
multicasting and class E is reserved. |
| 35 |
|
| 36 |
Class A has the highest order bit set to 0, a 7 bit network number |
| 37 |
and a 24 bit host address. |
| 38 |
|
| 39 |
Class B has the two higher order bits set to 10, a 14 bit network |
| 40 |
number and a 16 bit host address. |
| 41 |
|
| 42 |
Class C has the three higher order bit set to 110, a 21 bit network |
| 43 |
number and a 8 bit host address. |
| 44 |
|
| 45 |
Class D has the four higher order bits set to 1110. |
| 46 |
|
| 47 |
Class E has four higher address bits set to 1111. |
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Siyan [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc1365">RFC 1365</a> An IP Address Proposal September 1992</span> |
| 55 |
|
| 56 |
|
| 57 |
Increasing the size of the IP address field to more than 32 bits |
| 58 |
would solve the problem, but at the expense of making a new IP header |
| 59 |
definition that would be incompatible with the existing base of IP |
| 60 |
implementations. OSI based solutions such as using CLNP have been |
| 61 |
proposed but would take time to implement. |
| 62 |
|
| 63 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Proposal for IP extension</span> |
| 64 |
|
| 65 |
The IP header format should not be modified to minimize the changes |
| 66 |
necessary for supporting the address extensions that are proposed in |
| 67 |
this RFC. Instead an "escape" mechanism can be used to specify larger |
| 68 |
address. The IP header length field is 4 bits and this allows a |
| 69 |
maximum of fifteen 32-bit words where each word is 4 octets. The |
| 70 |
minimum size of the IP header without options is 5 words, which |
| 71 |
leaves 10 words for options. One can reserve 6 words (24 octets) for |
| 72 |
the normal options and leave the remaining (4 words or 16 octets) for |
| 73 |
a new option type that specifies an extended address. The details of |
| 74 |
this mechanism are discussed below. |
| 75 |
|
| 76 |
Class E should be defined with the its five high order bits set to |
| 77 |
11110. Its current definition is that four 1's in the most |
| 78 |
significant bits represent a class E address. |
| 79 |
|
| 80 |
A new class F is proposed with its six high order bits set to 111110. |
| 81 |
The new class F address would be placed in the same locations that |
| 82 |
are used for source and destination IP address in the IP header, but |
| 83 |
would specify that part of the addressing information is in the |
| 84 |
options part of the IP header. This is illustrated in the figure |
| 85 |
below: |
| 86 |
|
| 87 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 88 |
| Ver. | IHL | TOS | Total Length | |
| 89 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 90 |
| Identification |Flags| Fragment Offset | |
| 91 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 92 |
|1|1|1|1|1|0| Offset| Reserved | Source IP address part 1 | |
| 93 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 94 |
|1|1|1|1|1|0| Offset| Reserved | Destination IP address part 1 | |
| 95 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 96 |
: Options : |
| 97 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 98 |
: SADDR Code |Len adr. part 2| Source IP address part 2 : |
| 99 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 100 |
: DADDR Code |Len adr. part 2| Destination IP address part 2 : |
| 101 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 102 |
: Data : |
| 103 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Siyan [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc1365">RFC 1365</a> An IP Address Proposal September 1992</span> |
| 111 |
|
| 112 |
|
| 113 |
The "Offset" field specifies the offset in words from the beginning |
| 114 |
of the IP header where the second part of the IP address is located. |
| 115 |
Its purpose is to avoid searching the options part for addressing |
| 116 |
information. The address in the options part is in the Type-Length- |
| 117 |
Value form for consistency with other IP options that are found in |
| 118 |
this part. The "Len adr. part" indicates the length of the second IP |
| 119 |
address part in octets. The lengths should be defined so that the |
| 120 |
second part of the IP address ends on a word boundary. For example, |
| 121 |
the possible length values are 4, 8 octets. It is proposed that new |
| 122 |
IP option codes be used for the SADDR and DADDR codes respectively. |
| 123 |
|
| 124 |
The IP address is the 2 bytes in the fixed IP header part plus the |
| 125 |
address field defined in the options part. |
| 126 |
|
| 127 |
If the "Len adr. part" field has a value of 4, the new class is |
| 128 |
designated as the F-4 class (Class F with IP address length of 4 |
| 129 |
octets). |
| 130 |
|
| 131 |
If the "Len adr. part" field has a value of 8, the new class is |
| 132 |
designated as the F-8 class (Class F with IP address length of 8 |
| 133 |
octets). |
| 134 |
|
| 135 |
Each of the F-4 and F-8 IP address class can be further subdivided |
| 136 |
into a network number and a host number field in a manner that is |
| 137 |
similar to the current IP addressing scheme. |
| 138 |
|
| 139 |
The sub-class definitions for F-4 class are shown below. Though the 4 |
| 140 |
octets are drawn contiguously, the first 2 octets and the last 2 |
| 141 |
octets are not contiguous in the IP header. |
| 142 |
|
| 143 |
Class F-4A has the highest order bit set to 0, a 7 bit network number |
| 144 |
and a 24 bit host address. |
| 145 |
|
| 146 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 147 |
|0| net number | local part | |
| 148 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 149 |
|
| 150 |
Class F-4B has the two higher order bits set to 10, a 14 bit network |
| 151 |
number and a 16 bit host address. |
| 152 |
|
| 153 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 154 |
|1|0| net number | local part | |
| 155 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Siyan [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc1365">RFC 1365</a> An IP Address Proposal September 1992</span> |
| 167 |
|
| 168 |
|
| 169 |
Class F-4C has the three higher order bit set to 110, a 21 bit |
| 170 |
network number and a 8 bit host address. |
| 171 |
|
| 172 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 173 |
|1|1|0| net number | local part | |
| 174 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 175 |
|
| 176 |
Class F-4D has the four higher order bits set to 1110. Class F-4D is |
| 177 |
reserved for multicasting. |
| 178 |
|
| 179 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 180 |
|1|1|1|0| | multicast | |
| 181 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 182 |
|
| 183 |
The sub-class definitions for F-8 class are shown below. Though the 8 |
| 184 |
octets are drawn contiguously, the first 2 octets and the last 6 |
| 185 |
octets are not contiguous in the IP header. |
| 186 |
|
| 187 |
Class F-8A has the highest order bit set to 0, a 7 bit network number |
| 188 |
and a 56 bit host address. |
| 189 |
|
| 190 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 191 |
|0| net number | local part | |
| 192 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 193 |
| local part | |
| 194 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 195 |
|
| 196 |
Class F-8B has the two higher order bits set to 10, a 14 bit network |
| 197 |
number and a 48 bit host address. |
| 198 |
|
| 199 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 200 |
|1|0| net number | local part | |
| 201 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 202 |
| local part | |
| 203 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 204 |
|
| 205 |
Class F-8C has the three higher order bit set to 110, a 21 bit |
| 206 |
network number and a 40 bit host address. |
| 207 |
|
| 208 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 209 |
|1|1|0| net number | local part | |
| 210 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 211 |
| local part | |
| 212 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 213 |
|
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Siyan [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc1365">RFC 1365</a> An IP Address Proposal September 1992</span> |
| 223 |
|
| 224 |
|
| 225 |
Class F-8D has the four higher order bits set to 1110, a 28 bit |
| 226 |
network number and a 32 bit host address. |
| 227 |
|
| 228 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 229 |
|1|1|1|0| net number | |
| 230 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 231 |
| local part | |
| 232 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 233 |
|
| 234 |
Class F-8E has the five higher order bits set to 11110, a 35 bit |
| 235 |
network number and a 24 bit host address. |
| 236 |
|
| 237 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 238 |
|1|1|1|1|0| net number | |
| 239 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 240 |
| net number | local part | |
| 241 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 242 |
|
| 243 |
Class F-8F has the six higher order bits set to 111110, a 44 bit |
| 244 |
network number and a 16 bit host address. |
| 245 |
|
| 246 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 247 |
|1|1|1|1|1|0| net number | |
| 248 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 249 |
| net number | local part | |
| 250 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 251 |
|
| 252 |
Class F-8G has the seven higher order bits set to 1111110, a 49 bit |
| 253 |
network number and a 8 bit host address. |
| 254 |
|
| 255 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 256 |
|1|1|1|1|1|0| net number | |
| 257 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 258 |
| net number | local part | |
| 259 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 260 |
|
| 261 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Interoperability Issues</span> |
| 262 |
|
| 263 |
If the new class F address is seen by a host that does not support it |
| 264 |
the IP datagram will be ignored. So communication will not be |
| 265 |
possible with existing hosts, but the amount of modification for |
| 266 |
existing hosts is much less than implementing an entirely different |
| 267 |
IP header structure or a different protocol. |
| 268 |
|
| 269 |
The receiving host must be modified to contain the following code |
| 270 |
sketched below: |
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Siyan [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc1365">RFC 1365</a> An IP Address Proposal September 1992</span> |
| 279 |
|
| 280 |
|
| 281 |
if (Destination_IP_address & 0xFC000000 == 0xF8000000) |
| 282 |
{ |
| 283 |
|
| 284 |
/* New extended class F address */ |
| 285 |
Class_F_Processing(Destination_IP_address); |
| 286 |
|
| 287 |
} |
| 288 |
|
| 289 |
The Class_F_Processing() procedure can be defined in a separate |
| 290 |
module. There will be other changes required to communicate the |
| 291 |
results of processing the class F address to the main IP processing |
| 292 |
module but they should not be so extensive. |
| 293 |
|
| 294 |
Security Considerations |
| 295 |
|
| 296 |
Security issues are not discussed in this memo. |
| 297 |
|
| 298 |
Author's Address |
| 299 |
|
| 300 |
Karanjit Siyan |
| 301 |
Siyan Consulting Services |
| 302 |
49 Taurus Road, Box 960 |
| 303 |
North Glastonbury |
| 304 |
Emigrant, Montana 59027 |
| 305 |
|
| 306 |
Phone: 406-333-4491 |
| 307 |
|
| 308 |
EMail: [email protected] |
| 309 |
|
| 310 |
|
| 311 |
|
| 312 |
|
| 313 |
|
| 314 |
|
| 315 |
|
| 316 |
|
| 317 |
|
| 318 |
|
| 319 |
|
| 320 |
|
| 321 |
|
| 322 |
|
| 323 |
|
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
Siyan [Page 6] |
| 333 |
</pre> |