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