Debian Codegraph @

rfc1005.html

raw
1 <pre>Network Working Group Atul Khanna, Andy Malis
2 Request for Comments: 1005 BBN Communications Corp.
3 May 1987
4
5
6 <span class="h1">The ARPANET AHIP-E Host Access Protocol (Enhanced AHIP)</span>
7
8
9 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Status of this Memo</span>
10
11 This RFC is a proposed specification for the encoding of Class A
12 IP addresses for use on ARPANET-style networks such as the Milnet
13 and Arpanet, and for enhancements to the ARPANET AHIP Host Access
14 Protocol (AHIP; formerly known as 1822). These enhancements
15 increase the size of the PSN field, allow ARPANET hosts to use
16 logical names to address each other, allow for the communication
17 of type-of-service information from the host to the PSN and
18 enable the PSN to provide congestion feedback to the host on a
19 connection basis. Distribution of this memo is unlimited.
20 Comments on this RFC should be sent to the netmail address
21 "[email protected]".
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 <span class="grey">Khanna &amp; Malis [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
55
56
57 Table of Contents
58
59
60 <a href="#section-1">1</a> INTRODUCTION.......................................... <a href="#page-4">4</a>
61
62 <a href="#section-2">2</a> IP ISSUES............................................. <a href="#page-6">6</a>
63 2.1 Current Interpretation of Class A IP Address
64 Fields
65 ................................................... <a href="#page-6">6</a>
66 2.2 Requirements and Constraints Affecting New
67 Class A Mapping
68 ................................................... <a href="#page-7">7</a>
69 <a href="#section-2.3">2.3</a> New Interpretation of IP Address Fields............. <a href="#page-8">8</a>
70 <a href="#section-2.4">2.4</a> Discussion of the New Mapping.......................<a href="#page-10">10</a>
71 2.5 Interoperability between Current AHIP and
72 AHIP-E
73 ...................................................<a href="#page-11">11</a>
74
75 <a href="#section-3">3</a> LOGICAL ADDRESSING................................... <a href="#page-13">13</a>
76 <a href="#section-3.1">3.1</a> Addresses and Names................................ <a href="#page-13">13</a>
77 <a href="#section-3.2">3.2</a> Name Translations.................................. <a href="#page-14">14</a>
78 <a href="#section-3.2.1">3.2.1</a> Authorization and Effectiveness.................. <a href="#page-15">15</a>
79 <a href="#section-3.2.2">3.2.2</a> Translation Policies............................. <a href="#page-16">16</a>
80 <a href="#section-3.2.3">3.2.3</a> Reporting Destination Host Downs................. <a href="#page-17">17</a>
81 <a href="#section-3.3">3.3</a> Establishing Host-PSN Communications............... <a href="#page-18">18</a>
82 <a href="#section-3.4">3.4</a> Name Server........................................ <a href="#page-19">19</a>
83
84 <a href="#section-4">4</a> OTHER CHANGES........................................ <a href="#page-20">20</a>
85 <a href="#section-4.1">4.1</a> Type-of-Service Specification...................... <a href="#page-20">20</a>
86 <a href="#section-4.2">4.2</a> Subnet Congestion Feedback......................... <a href="#page-21">21</a>
87 <a href="#section-4.3">4.3</a> Precedence Level Information....................... <a href="#page-21">21</a>
88
89 <a href="#section-5">5</a> FORMATS FOR NEW AHIP-E MESSAGES...................... <a href="#page-23">23</a>
90 <a href="#section-5.1">5.1</a> Host-to-PSN AHIP-E Leader Format................... <a href="#page-23">23</a>
91 <a href="#section-5.2">5.2</a> PSN-to-Host AHIP-E Leader Format................... <a href="#page-27">27</a>
92
93 <a href="#section-6">6</a> AHIP-E VERSIONS...................................... <a href="#page-33">33</a>
94
95 <a href="#section-7">7</a> REFERENCES........................................... <a href="#page-34">34</a>
96
97
98
99
100
101
102
103
104
105
106
107
108 <span class="grey">Khanna &amp; Malis [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
111
112
113 FIGURES
114
115 <a href="#section-2.1">2.1</a> IP Class A Mapping................................... <a href="#page-6">6</a>
116 <a href="#section-2.2">2.2</a> New Class A IP Address Interpretation................ <a href="#page-8">8</a>
117 <a href="#section-2.3">2.3</a> AHIP-E Address and Name.............................. <a href="#page-9">9</a>
118 <a href="#section-3.1">3.1</a> Current AHIP Address Format......................... <a href="#page-13">13</a>
119 <a href="#section-3.2">3.2</a> AHIP-E Address Format............................... <a href="#page-14">14</a>
120 <a href="#section-3.3">3.3</a> Logical Name Format................................. <a href="#page-14">14</a>
121 <a href="#section-5.1">5.1</a> Host-to-PSN AHIP-E Leader Format.................... <a href="#page-23">23</a>
122 <a href="#section-5.2">5.2</a> NDM Message Format.................................. <a href="#page-25">25</a>
123 <a href="#section-5.3">5.3</a> PSN-to-Host AHIP-E Leader Format.................... <a href="#page-27">27</a>
124 <a href="#section-5.4">5.4</a> Name Server Reply Format............................ <a href="#page-30">30</a>
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 <span class="grey">Khanna &amp; Malis [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
167
168
169 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a> INTRODUCTION</span>
170
171 This RFC is a proposed specification for the encoding of Class A
172 IP addresses for use on ARPANET-style networks such as the Milnet
173 and Arpanet, and for enhancements to the AHIP Protocol (AHIP is the
174 preferred term for what has previously been known as the 1822
175 protocol). These enhancements and modifications are partially
176 motivated by a need to overcome the current address limitation
177 of 256 PSNs per network and by a desire to allow hosts to take
178 advantage of logical addressing with minimal change to their AHIP
179 software. This enhanced AHIP protocol will be referred to as
180 "AHIP-E". These enhancements will:
181
182
183 1. Increase the size of the PSN field to 10 bits.
184
185 2. Allow hosts to use logical names (i.e., host names that are
186 independent of physical location on the network) in addition to
187 physical port addresses to communicate with each other.
188
189 3. Enable the host to specify a type-of-service to the PSN.
190
191 4. Provide a mechanism for the PSN to communicate subnetwork
192 congestion information to the host on a destination host basis.
193 This will give the host an opportunity to selectively reduce
194 its congesting flows, thus preventing all of its flows from
195 being blocked b y the network. Currently, a host has no way of
196 knowing which of its flows is experiencing congestion;
197 consequently, it is possible that one congesting flow can
198 result in the blocking of all the host's flows .
199
200 5. Enable the PSN to inform the host about changes in precedence
201 cutoff levels and about precedence level violations.
202
203 A host can take advantage of the extended and logical addressing
204 capabilities without making substantial changes to its AHIP
205 implementation. In particular, the specification provides three
206 versions of AHIP-E: version 0 is current AHIP with no changes; version 1
207 allows use of logical and extended addressing with minimal change to
208 code; version 2 constitutes full-fledged AHIP-E. This is described in
209 further detail in chapter 6.
210
211 This RFC's terminology is consistent with that used in BBN Report 1822
212 [<a href="#ref-1" title="&quot;Specifications for the Interconnection of a Host and an PSN&quot;">1</a>], and any new terms are defined when they are first used.
213 Familiarity with Report 1822 (<a href="#section-3">section 3</a> in particular) is assumed. As
214 could be expected, the RFC makes many references to Report 1822. As a
215 result, it uses, as a convenient abbreviation, "see 1822(x)" instead of
216 "please refer to Report 1822, section x, for further details".
217
218
219
220 <span class="grey">Khanna &amp; Malis [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
223
224
225 The rest of this RFC is organized as follows. Chapter 2 describes the
226 new mapping between IP class A addresses and subnetwork hosts. Chapter
227 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a> discusses logical addressing. </span>Chapter 4 describes the enhancements
228 related to type-of-service and reliability specification and to
229 congestion and precedence feedback. Chapter 5 includes a specification
230 of the new message types and their formats. Finally, chapter 6
231 describes the AHIP-E version numbering scheme.
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 <span class="grey">Khanna &amp; Malis [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
279
280
281 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a> IP ISSUES</span>
282
283 This section discusses the changes to the mapping between Class A IP
284 addresses [<a href="#ref-5" title="&quot;Address Mappings&quot;">5</a>] and subnet addresses. These changes are made necessary
285 by:
286
287 1. The introduction of logical names.
288
289 2. The expansion of the PSN-number field.
290
291
292 Note that this RFC does not affect Class B and C mappings [<a href="#ref-5" title="&quot;Address Mappings&quot;">5</a>].
293
294
295 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a> Current Interpretation of Class A IP Address Fields</span>
296
297 Class A IP addresses are 32 bits in length, with 8 bits devoted to
298 network number and 24 to the local address. In particular, they are of
299 the form n.h.l.i, where n,h,l and i are decimal integers less than 256.
300 AHIP addresses are 24 bits in length. The current ARPANET-style class A
301 mapping is as follows (from <a href="./rfc796">RFC 796</a>):
302
303
304
305
306 0 7 8 15 16 23 24 31
307 +--------+--------+-------+---------+
308 | net # | HOST | LH | PSN | IP Address
309 +--------+--------+-------+---------+
310 8 8 8 8
311
312
313 8 8 8
314 +--------+--------+--------+
315 | HOST | ZERO | PSN | AHIP Physical Address
316 +--------+--------+--------+
317 41 48 49 56 57 64
318 (bit positions in the AHIP leader)
319
320 IP Class A Mapping
321 Figure 2.1
322
323
324
325 The LH (logical host) field is used by the hosts only and is not passed
326 to the network.
327
328
329
330
331
332 <span class="grey">Khanna &amp; Malis [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
335
336
337 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a> Requirements and Constraints Affecting New Class A Mapping</span>
338
339 This section discusses some of the requirements and constraints that
340 were considered significant in determining the new address mapping.
341
342 1. Address Mapping Stability Requirement:
343
344 Any current IP physical address with l (logical host) = 0
345 should remain unchanged under the new design. For example,
346 the binary string corresponding to 10.0.0.51 should continue
347 to refer to sri-nic.arpa (assuming, of course, that sri-nic
348 continues to reside on psn 51, port 0). This requirement is
349 motivated by a desire to avoid a network-wide address
350 switchover.
351
352 2. Existing implementation compatibility:
353
354 Existing compliant implementations of AHIP should continue to
355 function for destinations with addresses fitting the
356 restrictions in 1. In other words, such addresses should
357 continue to refer to their original destinations, not only
358 with the AHIP-E implementation (which is the condition in 1),
359 but also with current ones.
360
361 3. Compatibility between X.25's IP address to subnet host mapping
362 and AHIP's IP address to subnet host mapping:
363
364 The AHIP-E IP to host mapping should be able to co-exist in
365 some sense with the IP to host mapping specified by the DDN
366 X.25 Specification [<a href="#ref-6" title="&quot;Defense Data Network X.25 Host Interface Specification&quot;">6</a>]. In particular, restricted use of the
367 revised IP to DDN host mapping should produce addresses that
368 are consistent with the current X.25 mapping. In other words,
369 there should be a set that includes "sufficiently many"
370 logical names and physical addresses, with the property that
371 each address/name in the set maps onto the same host under
372 both the AHIP and X.25 mappings.
373
374 4. Maximum number of PSNs that can be supported:
375
376 The new design should support a maximum of more than 256 PSNs
377 per network.
378
379
380
381
382
383
384
385
386
387
388 <span class="grey">Khanna &amp; Malis [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
391
392
393 <span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a> New Interpretation of IP Address Fields</span>
394
395 The following is the new interpretation of the IP address field, in the
396 context of ARPANET-style networks:
397
398
399 Proposed IP Address Interpretation
400
401 8 8 1 5 10
402 +--------+--------+-+-----+----------+
403 | net # | HOST |0|XXXXX| PSN | Physical Address
404 +--------+--------+-+-----+----------+
405 0 7 8 15 17 21 22 31
406
407
408 8 8 2 6 8
409 +--------+--------+--+------+--------+
410 | net # | UPPER |11|XXXXXX| LOWER | Logical Name
411 +--------+--------+--+------+--------+
412 0 7 8 15 18 23 24 31
413
414
415 16 2 14
416 +-----------------+--+---------------+
417 | |10| | Reserved Format
418 +-----------------+--+---------------+
419 0 15 18 31
420
421 (X = don't care)
422
423 New Class A IP Address Interpretation
424 Figure 2.2
425
426
427 The fields have the following meanings:
428
429 HOST = host-number
430
431 PSN = 10 bit PSN-number field
432
433 UPPER = upper 8 bits of the 16-bit logical name
434
435 LOWER = lower 8 bits of the 16-bit logical name
436
437
438
439
440
441
442
443
444 <span class="grey">Khanna &amp; Malis [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
447
448
449 AHIP-E physical addresses and logical names have the following formats:
450
451 8 1 5 10
452 +--------+-+-----+----------+
453 | HOST |0|XXXXX| PSN | Physical Address
454 +--------+-+-----+----------+
455 41 48 55 64
456 (bit positions in the AHIP leader)
457 (X = don't care)
458
459
460 8 2 6 8
461 +--------+--+------+--------+
462 | UPPER |11|XXXXXX| LOWER | Logical Name
463 +--------+--+------+--------+
464 41 48 57 64
465 (bit positions in the AHIP leader)
466
467
468 +--------+--+---------------+
469 | |10| | Reserved Address Format
470 +--------+--+---------------+
471 41 48 51 64
472 (bit positions in the AHIP leader)
473
474
475 AHIP-E Address and Name
476 Figure 2.3
477
478 The reserved address format is currently undefined and will be rejected
479 by the PSN, which will return an error message (message type 6, subtype
480 3) to the host.
481
482 -----------------------------------------------------------------
483 |This design does not require the AHIP-E host to do any processing|
484 |of the address -- the host need only copy bits 8-31 of the IP |
485 |address into bits 41-64 of the AHIP leader. The host no longer |
486 |needs to zero out bits 49-56 of the AHIP leader. The PSN will |
487 |take care of the AHIP to subnet address conversion. In other |
488 |words, bits 8-31 of the IP address field should be passed |
489 |unchanged to the PSN, which interprets them exactly as shown in |
490 |figure 2.3. |
491 -----------------------------------------------------------------
492
493
494
495
496
497
498
499
500 <span class="grey">Khanna &amp; Malis [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
503
504
505 <span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a> Discussion of the New Mapping</span>
506
507 This section presents an evaluation of the design in terms of the
508 requirements in <a href="#section-2.2">section 2.2</a>
509
510 1. Address mapping stability requirement:
511
512 Current physical IP addresses will not have to be changed, as
513 long as they have been following the convention of setting LH
514 = 0. This ensures that bit 16 is set to 0, indicating that
515 the address is physical, and that the PSN number comes out
516 right.
517
518
519 2. Existing implementation compatibility:
520
521 The design meets this requirement, as the address that gets to
522 the PSN has its second octet = 0, which results in its correct
523 interpretation as a physical address.
524
525 3. Compatibility with the current X.25 IP address to DDN host
526 mapping:
527
528 The current X.25 IP to HOST mapping [<a href="#ref-6" title="&quot;Defense Data Network X.25 Host Interface Specification&quot;">6</a>] is as follows: If h &lt;
529 64, the address is considered physical, i.e., it refers to
530 host h on PSN i. If h &gt;= 64, the address is considered
531 logical, i.e., it refers to the host whose logical name is h
532 concatenated with i.
533
534 The design is compatible in a limited sense with the current
535 X.25 logical addressing implementation, as long as logical
536 names are assigned such that host-number &gt; 63 (also PSN-number
537 &lt; 256 which is automatic, given the 16-bit size of the logical
538 name field) and physical addresses are in the range host-
539 number &lt; 64 and PSN- number &lt; 256, with the appropriate
540 setting of bits 16 and 17 of the IP address field. This works
541 because the X.25 mapping ignores the value of the l field,
542 i.e., the third IP address octet.
543
544 Given the desire to be able to address more than 64 hosts
545 physically and for PSN numbers &gt; 255, this address assignment
546 restriction should not be considered permanent, but rather as
547 an interim compromise until the hosts' X.25 implementations
548 are revised to incorporate the new mapping between IP and DDN
549 addresses.
550
551
552
553
554
555
556 <span class="grey">Khanna &amp; Malis [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
559
560
561 4. Maximum number of PSNs that can be supported:
562
563 The design allows addressing of up to 1024 PSNs per network.
564
565 <span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a> Interoperability between Current AHIP and AHIP-E</span>
566
567 This section discusses the interoperability between hosts using current
568 AHIP and AHIP-E. It also discusses the general issue of current AHIP
569 host operation in the AHIP-E addressing environment.
570
571 The proposed modifications to AHIP have been designed with backward
572 compatibility in mind. However, note that bits 41-64 of the PSN-to-host
573 leader (see 1822(3.4)) will always contain the physical address of the
574 source host. This means that an error could occur when a host on a PSN
575 numbered greater than 255 attempts to send a message to a host running a
576 current AHIP implementation, which interprets the address of the source
577 host as one with PSN-number &lt; 256.
578
579 There are other possibilities for errors, caused by incorrect address
580 translation between IP and current AHIP:
581
582 1. A host running current AHIP cannot physically address
583 any host on a PSN numbered greater than 255 (see Figure
584 3.1). Consequently, an error will result if the host
585 attempts to use an address from the NIC host table that
586 has PSN-number &gt; 255.
587
588 2. If a host running current AHIP attempts to use a
589 logical name that it might have in its host table, an
590 error will occur. This is because the logical name flag
591 bits 16 and 17 of the IP address, bits 49 and 50 of the
592 AHIP leader. Recal that bits 49 - 56 of the AHIP
593 leader get set to zero with current AHIP (see figure
594 2.1).
595
596 Since these errors cannot be detected by the subnetwork, it is essential
597 that all hosts implement at least version 1 AHIP-E (see chapter 6)
598 before PSN numbers over 255 and logical names are assigned.
599
600
601
602
603
604
605
606
607
608
609
610
611
612 <span class="grey">Khanna &amp; Malis [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
615
616
617 Another aspect of interoperability has to do with the IP LH field, which
618 is currently used by a handful of Arpanet hosts to demultiplex a single
619 host port. The 5 don't-care bits of the physical IP address (bits 17-
620 21) and the 6 don't-care bits of the IP logical name (bits 18-23) can be
621 used for this purpose -- in particular, the use of these bits is divided
622 between the network and external devices, based on administrative
623 agreement. At the very least, the IP addresses of such hosts will have
624 to change to reflect the changed position of the LH field. However, the
625 preferred way to demultiplex a single host port is via the mechanism of
626 logical names. The only change this involves is to get the port
627 expander implementation to look at the entire IP address, rather than
628 just the LH field.
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668 <span class="grey">Khanna &amp; Malis [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
671
672
673 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a> LOGICAL ADDRESSING</span>
674
675 The modifications to AHIP allow a host to use logical addressing to
676 communicate with other hosts on the network. Basically, logical
677 addressing allows hosts to refer to each other using a logical name (see
678 <a href="#section-3.1">section 3.1</a>) which is independent of a host's physical location in the
679 network. IEN 183 (also published as BBN Report 4473) [<a href="#ref-2" title="&quot;ARPANET Routing Algorithm Improvements&quot;">2</a>] gives the use
680 of logical addressing considerable justification. Among the advantages
681 it cites are:
682
683 o The ability to refer to each host on the network by a name
684 independent of its location in the network (especially
685 important if the host has to move to another physical port).
686
687 o Allowing different hosts to share the same host port on a
688 time-division basis.
689
690 o Allowing a host to use multi-homing (where a single host uses
691 more than one port to communicate with the network).
692
693 o Allowing several hosts that provide the same service to share
694 the same name.
695
696 o Allowing a host to provide services that have their own unique
697 names.
698
699 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a> Addresses and Names</span>
700
701 The AHIP-E protocol allows two forms of host specification. The first
702 is a slightly modified version of the form used by the current AHIP
703 protocol, the physical address. The second form is the logical name
704 (the terms "name", "logical name" and "logical address" are used
705 interchangeably in this document).
706
707 Current AHIP addresses are the 24-bit host addresses found in AHIP
708 leaders. They have the following format:
709
710 8 8 8
711 +-------------+--------+------------+
712 | host-number |00000000| PSN-number |
713 +-------------+--------+------------+
714 41 48 49 56 57 64
715 (bit positions in the AHIP leader)
716
717 Current AHIP Address Format
718 Figure 3.1
719
720
721
722
723
724 <span class="grey">Khanna &amp; Malis [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
727
728
729 AHIP-E addresses have the following format:
730
731
732 8 1 5 10
733 +--------+-+-----+----------+
734 | HOST |0|XXXXX| PSN | Physical Address
735 +--------+-+-----+----------+
736 41 48 55 64
737 (bit positions in the AHIP leader)
738 (X = don't care)
739
740 AHIP-E Address Format
741 Figure 3.2
742
743 Logical names are 16-bit unsigned numbers that serve as a logical
744 identifier for one or more hosts. A logical name is the concatenation
745 of two separate octets in the AHIP leader, bits 41-48 (Upper 8) and 57-
746 <span class="h2"><a class="selflink" id="section-64" href="#section-64">64</a> (Lower 8) in particular.</span>
747
748
749 8 2 6 8
750 +--------+--+------+--------+
751 | UPPER |11|XXXXXX| LOWER |
752 +--------+--+------+--------+
753 41 48 57 64
754 (bit positions in the AHIP leader)
755 (X = don't care)
756
757
758 Logical Name Format
759 Figure 3.3
760
761 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a> Name Translations</span>
762
763 There are a number of factors that determine how a logical name is
764 translated by the PSN into a physical address on the network. These
765 factors include which translations are legal; in what order different
766 translations for the same name should be attempted; and which legal
767 translations should not be attempted because a particular host port is
768 down. These issues are discussed in the following sections.
769
770
771
772
773
774
775
776
777
778
779
780 <span class="grey">Khanna &amp; Malis [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
783
784
785 <span class="h4"><a class="selflink" id="section-3.2.1" href="#section-3.2.1">3.2.1</a> Authorization and Effectiveness</span>
786
787 Every host on a PSN, regardless of whether it is using the AHIP or
788 AHIP-E protocol to access the network, can have one or more logical
789 names. Hosts using AHIP-E can then use these names to address the hosts
790 in the network independent of their physical locations.
791
792 At this point, several questions arise: How are these names assigned,
793 how do they become known to the PSNs (so that translations to physical
794 addresses can be made), and how do the PSNs know which host is currently
795 using a shared port? To answer each question in order:
796
797 Names are assigned by a central network administrator. When each name
798 is created, it is assigned to a host (or a group of hosts) at one or
799 more specific host ports. The host(s) are allowed to reside at those
800 specific host ports, and nowhere else. If a host moves, it will keep
801 the same name, but the administrator has to update the central database
802 to reflect the new host port. Changes to this database are distributed
803 to the PSNs by the Monitoring Center (MC). For a while, the host may be
804 allowed to reside at either of (or both) the new and old ports. Once
805 the correspondence between a name and one or more hosts ports where it
806 may be used has been made official by the administrator, that name is
807 said to be authorized. Physical addresses, which actually refer to
808 physical host ports, are always authorized in this sense.
809
810 When the PSN detects that a host has come up on one of its ports, it
811 makes effective the default name(s), if any, for that host. This
812 default action is specified in the configuration table for that host,
813 and can be one of the following: Enable All Names, Enable No Names,
814 Enable One Particular Name. In the case of an AHIP-E host, the default
815 name might not be the one that the host desires to be known as (recall
816 that several hosts may share the same port, or one host may prefer to be
817 known by different names at different times). This requires that an
818 AHIP-E host be able to declare its name to the PSN. This function is
819 performed by a new host-to-PSN message, the Name Declaration Message
820 (NDM), which lists the names that the host would like to be known by.
821 The PSN checks its tables to see if each of the names is authorized, and
822 sends an NDM Reply to the host saying which names were actually
823 authorized and can now be used for sending and receiving messages (i.e.,
824 which names are effective). A host can also use an NDM message to
825 change its list of effective names (it can add to and delete from the
826 list) at any time. The only constraint on the host is that any names it
827 wishes to use can become effective only if they are authorized.
828
829 If a host is using the current AHIP protocol, it can still receive
830 messages from hosts via its logical name. Of course, it can also
831 receive messages from a current AHIP host via its physical address as
832 well. (Remember, the distinction between logical names and physical
833
834
835
836 <span class="grey">Khanna &amp; Malis [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
839
840
841 addresses is that the addresses correspond to physical locations on the
842 network, while the names are strictly logical identifiers).
843
844 The third question above has by now already been answered. An AHIP-E
845 host can use the NDM message to tell the PSN which host it is (which
846 names it is known by). Thus, even if this is a shared port, the PSN
847 knows which host is currently connected.
848
849 WHENEVER A HOST GOES DOWN, ITS NAMES AUTOMATICALLY BECOME NON-
850 EFFECTIVE. When it comes back up, the default action (from the host's
851 configuration) is taken. If the host wishes to be known by a name other
852 than the default, it will have to issue a NDM. It will also have to do
853 this upon receipt of reset NOPS from the PSN.
854
855 <span class="h4"><a class="selflink" id="section-3.2.2" href="#section-3.2.2">3.2.2</a> Translation Policies</span>
856
857 Several hosts can share the same logical name. If more than one of
858 these hosts is up at the same time, any messages sent to that logical
859 name will be delivered to just one of the hosts sharing that name, and a
860 RFNM will be returned as usual. However, the sending host will not
861 receive any indication of which host received the message, and
862 subsequent messages to that name are not guaranteed to be sent to the
863 same host. Typically, hosts providing exactly the same service could
864 share the same logical name in this manner.
865
866 Similarly, when a host is multi-homed, the same logical name may refer
867 to more than one host port (all connected to the same host). If the
868 host is up on only one of those ports, that port will be used for all
869 messages addressed to the host. However, if the host were up on more
870 than one port, the message would be delivered over just one of those
871 ports, and the subnet would choose which port to use. This port
872 selection could change from message to message. If a host wanted to
873 insure that certain messages were delivered to it on specific ports,
874 these messages could use either the port's physical address or a
875 specific logical name that referred to that port alone.
876
877 Three different address selection policies are available for the name
878 mapping process. When translated, each name uses one of the three
879 policies (the policy is administratively pre-determined on a per-name
880 basis). The three policies are:
881
882 o Attempt each translation in the order in which the physical
883 addresses are listed in the PSN's translation tables, to find
884 the first reachable physical host address. This list is
885 always searched from the top whenever a new virtual circuit
886 connection has to be created. This is the most commonly used
887 policy.
888
889
890
891
892 <span class="grey">Khanna &amp; Malis [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
895
896
897 o Selection of the closest physical address, which uses the
898 PSN's internal routing tables to find the translation to the
899 destination PSN with the least cost path for the particular
900 type-of-service whenever a new virtual circuit connection has
901 to be created.
902
903 o Use load leveling. This is similar to the first policy, but
904 differs in that searching the address list for a valid
905 translation starts at the address following where the
906 previous translation search ended whenever a new virtual
907 circuit connection has to be created. This attempts to
908 spread out the load from any one PSN's hosts to the various
909 host ports associated with a particular name. Note that
910 this is NOT network-wide load leveling, which would require
911 knowledge about flows throughout the network.
912
913 <span class="h4"><a class="selflink" id="section-3.2.3" href="#section-3.2.3">3.2.3</a> Reporting Destination Host Downs</span>
914
915 As is explained in Report 1822, whenever regular messages are sent by a
916 host, the PSN opens a virtual circuit connection to each destination
917 host from the source host. A new connection is opened for each new
918 source-address/destination-name (or address, as the case might
919 be)/handling-type/type-of-service combination. A connection will stay
920 open at least as long as there are any outstanding (un-RFNMed) messages
921 using it and both the source and destination hosts stay up. Connections
922 are also closed after a period of inactivity.
923
924 However, the destination host may go down for some reason during the
925 lifetime of a connection. If the host goes down while there are no
926 outstanding messages to it in the network, then the connection is closed
927 and no other action is taken until the source host submits the next
928 message for that destination. At that time, ONE of the following events
929 will occur:
930
931 A1. If a physical address is being used to specify the
932 destination host, then the source host will receive a type
933 7, subtype 0 (Destination Host Dead) message from the PSN.
934
935 A2. If a logical name is being used to specify the
936 destination host, and the name maps to only one authorized
937 host port,then a type 7, subtype 0 message will be sent to
938 the source host.
939
940 A3. If a logical name is being used to specify the destination
941 host, and the name maps to more than one authorized host
942 port, then the PSN attempts to open a connection to another
943 authorized and effective host port for that name. If no
944 such connection can be made, the host will receive a type
945
946
947
948 <span class="grey">Khanna &amp; Malis [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
951
952
953 15 (AHIP Name or Address Error), subtype 5 (no effective
954 translations) message (see <a href="#section-5.2">section 5.2</a>). Note that a type
955 7 message cannot be returned to the source host, since type
956 7 messages refer to a particular destination host port, and
957 the name maps to more than one destination port. However,
958 in the case of a version 0 or 1 host, a type 7, subtype 0
959 message will be returned for each outstanding message. See
960 chapter 6 for further details on version numbers.
961
962 Things get a bit more complicated if there are any outstanding messages
963 on the connection when the destination host goes down. The connection
964 will be closed, and one of the following will occur:
965
966 B1. If a physical address is being used to specify the
967 destination host, then the source host will receive a type
968 7 message for each outstanding message.
969
970 B2. If a logical name is being used to specify the
971 destination host, then the source host will receive a type
972 9 (Incomplete Transmission), subtype 6 (message lost due to
973 logically addressed host going down) message for each
974 outstanding message. The next time the source host
975 submits another message for that same destination name,
976 the previous algorithm will be used (either step A2 or
977 step A3). However,in the case of a version 0 or 1 host, a
978 type 7,subtype 0 message will be returned for each
979 outstanding message. See chapter 6 for further details
980 on version numbers.
981
982 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a> Establishing Host-PSN Communications</span>
983
984 When a host comes up on a PSN, or after there has been a break in the
985 communications between the host and its PSN (see 1822 (3.2)),the orderly
986 flow of messages between the host and the PSN needs to be properly (re-
987 )established. This allows the PSN and host to recover from almost any
988 failure in the other or in their communications path, including a break
989 in mid-message.
990
991 The first messages that a host should send to its PSN are three NOPs.
992 Three messages are required to ensure that at least one message will be
993 properly read by the PSN (the first NOP could be concatenated to a
994 previous message if communications had been broken in mid-stream, and
995 the third provides redundancy for the second). These NOPs serve to
996 synchronize the PSN with the host, to inform the PSN about how much
997 padding the host requires between the message leader and its body and to
998 specify the host's AHIP-E version number to the PSN (see chapter 6).
999
1000 Similarly, the PSN will send three NOPs to the host when it detects that
1001
1002
1003
1004 <span class="grey">Khanna &amp; Malis [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
1007
1008
1009 the host has come up. The NOPs will be followed by an Interface Reset
1010 message. These NOPs will contain the physical address of the host
1011 interface.
1012
1013 Once the PSN and the host have sent each other the above messages,
1014 regular communications can commence. See 1822(3.2) for further details
1015 concerning the ready line, host tardiness, and other issues.
1016
1017 <span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a> Name Server</span>
1018
1019 There may be times when a host wants to perform its own translations, or
1020 might need the full list of physical addresses to which a particular
1021 name maps. For example, a connection- based host-to-host protocol may
1022 require that the same physical host port on a multi-homed host be used
1023 for all messages using that host-to-host connection, and the host does
1024 not wish to trust the PSN to always deliver messages using a destination
1025 name to the same host port.
1026
1027 In these cases, the host can submit a type 11 (Name Server Request)
1028 message to the PSN, which requests the PSN to translate the destination
1029 name and return a list of the addresses to which it maps. The PSN will
1030 respond with a type 11 (Name Server Reply) message, which contains the
1031 selection policy in use for that name, the number of addresses to which
1032 the name maps, the addresses themselves, and for each address, whether
1033 it is effective and its routing distance (for the particular type-of-
1034 service specified in the Name Server Request message) from the PSN. See
1035 <a href="#section-5.2">section 5.2</a> for a complete description of these messages' contents.
1036
1037 Using this information, the source host could make an informed decision
1038 on which of the physical host ports corresponding to a logical name to
1039 use and then send the messages to that port, rather than to the name.
1040
1041 The PSN also supports a different type of name service. A host needs to
1042 issue a Name Declaration Message to the PSN in order to change its
1043 effective names, but it may not wish to keep its names in some table or
1044 file in the host. In this case, it can ask the PSN to tell it which
1045 names it is authorized to use.
1046
1047 In this case, the host submits a type 12 (Port List Request) message to
1048 the PSN, and the PSN replies with a type 12 (Port List Reply) message.
1049 It contains, for the host port over which the PSN received the request
1050 and sent the reply, the number of names that map to the port, the list
1051 of names, and whether or not each name is effective. The host can then
1052 use this information in order to issue the Name Declaration Message.
1053 <a href="#section-5.2">Section 5.2</a> contains a complete description of the reply's contents.
1054
1055
1056
1057
1058
1059
1060 <span class="grey">Khanna &amp; Malis [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
1063
1064
1065 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a> OTHER CHANGES</span>
1066
1067 This section describes the enhancements to the AHIP protocol involving
1068 type-of-service specification, subnet congestion feedback and network
1069 precedence level feedback. Note that only version 2 hosts will receive
1070 the congestion and precedence messages described in this section.
1071
1072 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a> Type-of-Service Specification</span>
1073
1074 Bits 9 and 10 of the AHIP leader, currently unused, will be used by the
1075 host to specify desired delay and throughput characteristics to the PSN.
1076 Bit 11, also currently unused, will be used to specify reliability. The
1077 bits have the following meaning:
1078
1079 Bit 9: delay bit
1080
1081 0 -- normal delay
1082 1 -- low delay
1083
1084 Bit 10: throughput bit
1085
1086 0 -- normal throughput
1087 1 -- high throughput
1088
1089 Bit 11: reliability bit
1090
1091 0 -- normal reliability
1092 1 -- high reliability
1093
1094
1095 The values of these bits are consistent with those of IP, and bits 11,
1096 <span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a> and 13 of the IP header can be copied directly into bits 9, 10 and 11</span>
1097 of the AHIP leader.
1098
1099 The type-of-service bits should be considered as extensions of the
1100 "Handling Type" field (bits 33-40 of the AHIP leader -- see 1822 (3.3)).
1101 Messages from host A to host B using the same destination name and of
1102 the same handling type and type-of- service will use the same
1103 connection, while those that differ in either type-of-service,
1104 destination name or handling type will use separate connections. In
1105 other words, for a given source host and destination name pair, a new
1106 connection will be established whenever a message with a new handling-
1107 type/type-of- service combination is received.
1108
1109
1110
1111
1112
1113
1114
1115
1116 <span class="grey">Khanna &amp; Malis [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
1119
1120
1121 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a> Subnet Congestion Feedback</span>
1122
1123 This section describes the new messages that are part of the mechanism
1124 used by the PSN to communicate subnetwork congestion information to the
1125 host. Note that a host will be blocked by the PSN when its share of
1126 buffers in the PSN is used up. Thus, this information, which is
1127 communicated on a connection basis, will give the host an opportunity to
1128 selectively reduce its congesting flows, thus preventing all of its
1129 flows from getting blocked. Currently, a host has no way of knowing
1130 which of its flows is experiencing congestion; consequently, it is
1131 possible that one congesting flow can result in the blocking of all the
1132 host's flows.
1133
1134 Three new PSN-to-host messages have been created. These messages are:
1135
1136 1. STOP: Blocking Imminent -- Stop Sending on this
1137 Connection (Message type 13)
1138
1139 2. SLOW: Subnet Congestion -- Send at Slow Rate on this
1140 Connection (Message type 14) -- Maintain Window Size of
1141 1, i.e., do not send a new message to this destination
1142 host with this type-of-service and handling type until
1143 all previous messages have been acknowledged by RFNMs.
1144
1145 3. GO: Congestion Subsided -- Send at Regular Rate on this
1146 Connection (Message type 16) -- Maintain Window Size of
1147 8
1148
1149
1150 These messages may be sent in any order and correspond to states, not
1151 transitions. A participating host should support three states with
1152 effective windows of 8, 1 and 0. The format of these messages can be
1153 found in <a href="#section-5.2">section 5.2</a>.
1154
1155
1156 <span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a> Precedence Level Information</span>
1157
1158 Two new messages have been created:
1159
1160 1. Network Not Accepting Messages at this Precedence Level
1161 (Message type 9, subtype 7).
1162
1163 2. Network Precedence Level Cutoff Change (Message type
1164 17).
1165
1166 The first message will be generated whenever the host attempts to send a
1167 message at a precedence level lower than the cutoff. The cutoff
1168 represents a precedence level below which no traffic may be submitted
1169
1170
1171
1172 <span class="grey">Khanna &amp; Malis [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
1175
1176
1177 into the subnetwork; note that a cutoff set to the lowest possible
1178 precedence level implies that no precedence restrictions are in effect.
1179 If the host has chosen not to receive the new AHIP-E messages, then the
1180 PSN will send a type 7, sub-type 3 message (communication with the
1181 destination host is administratively prohibited) instead. The second
1182 message will be generated whenever the network precedence level cutoff
1183 changes. Both messages contain the network precedence cutoff value.
1184 The format of these messages can be found in <a href="#section-5.2">section 5.2</a>.
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228 <span class="grey">Khanna &amp; Malis [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
1231
1232
1233 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a> FORMATS FOR NEW AHIP-E MESSAGES</span>
1234
1235 The following sections describe the formats of the leaders that precede
1236 messages between an AHIP-E host and its PSN. The formats are almost
1237 identical to those of AHIP (see 1822(3.3) and 1822(3.4)). New message
1238 types are marked by margin bars (as shown | here).
1239
1240 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a> Host-to-PSN AHIP-E Leader Format</span>
1241
1242 1 4 5 8 13 16 17 20 21 22 24 25 32
1243 +---------+--------+-+-+-+-+------+--------+-+------+----------------+
1244 | | FORMAT |D|T|R|U| | |T|LEADER| |
1245 | UNUSED | FLAG |E|H|E|N| VERS | UNUSED |R|FLAGS | MESSAGE TYPE |
1246 | | (15) |L|R|L|U| | |C| | |
1247 +---------+--------+-+-+-+-+------+--------+-+------+----------------+
1248
1249 33 40 41 64
1250 +----------------------+----------------------------------------------+
1251 | | |
1252 | HANDLING TYPE | DESTINATION HOST |
1253 | | |
1254 +----------------------+----------------------------------------------+
1255
1256 65 76 77 80 81 96
1257 +-------------------------+--------+----------------------------------+
1258 | | | |
1259 | MESSAGE ID |SUB-TYPE| UNUSED |
1260 | | | |
1261 +-------------------------+--------+----------------------------------+
1262
1263 Host-to-PSN AHIP-E Leader Format
1264 Figure 5.1
1265
1266
1267 Bits 1-4: Unused, must be set to zero.
1268
1269 Bits 5-8: Format Flag
1270 This field is set to decimal 15 (1111 in binary).
1271
1272 Bits 9-11: Type-of-Service
1273
1274 Bit 9: Delay Bit:
1275 0 -- normal delay
1276 1 -- low delay
1277 Bit 10: Throughput Bit:
1278 0 -- normal throughput
1279 1 -- high throughput
1280 Bit 11: Reliability Bit:
1281
1282
1283
1284 <span class="grey">Khanna &amp; Malis [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
1287
1288
1289 0 -- normal reliability
1290 1 -- high reliability
1291
1292 Bit 12: Unused, must be set to zero.
1293
1294
1295 Bits 13-16: AHIP-E Version number
1296 Ignored by the PSN except in the case of a NOP -- see
1297 chapter 6.
1298
1299 Bits 17-20: Unused, must be set to zero.
1300
1301 Bit 21: Trace Bit:
1302 If equal to one, this message is designated for tracing as
1303 it proceeds through the network. See 1822(5.5).
1304
1305 Bits 22-24: Leader Flags:
1306
1307 Bit 22: A flag available for use by the destination host.
1308 See AHIP(3.3) for a description of its use by the
1309 PSN's TTY Fake Host.
1310 Bits 23-24: Reserved for future use, must be zero.
1311
1312 Bits 25-32: Message Type:
1313
1314 Type 0: Regular Message - All host-to-host communication
1315 occurs via regular messages, which have several sub-
1316 types, found in bits 77-80. These sub-types are:
1317 0: Standard - The PSN uses its full message and error
1318 control facilities, and host blocking may occur.
1319 3: Uncontrolled Packet - The PSN will perform no
1320 message-control functions for this type of
1321 message, and network flow and congestion control
1322 may cause loss of the packet. Also see
1323 1822(3.6). 1-2,4-15: Unassigned.
1324
1325 Type 1: Error Without Message ID - See 1822(3.3).
1326
1327 Type 2: Host Going Down - see 1822(3.3).
1328
1329 Type 3: Name Declaration Message (NDM) - This message is |
1330 used by the host to declare which of its logical names |
1331 is or is not effective (see <a href="#section-3.2.1">section 3.2.1</a>), or to make |
1332 all of its names non-effective. The first 16 bits of |
1333 the data portion of the NDM message, following the |
1334 leader and any leader padding, contains the number of |
1335 logical names contained in the message. This is |
1336 followed by the logical name entries, each 32 bits |
1337
1338
1339
1340 <span class="grey">Khanna &amp; Malis [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
1343
1344
1345 long, of which the first 16 bits is a logical name and |
1346 the second 16 bits contains either of the integers |
1347 zero or one. Zero indicates that the name should not |
1348 be effective, and one indicates that the name should be |
1349 effective. Note that only the names explicitly in the |
1350 NDM will remain enabled after the NDM is processed |
1351 (assuming that they are authorized). The PSN will |
1352 reply with a NDM Reply message (see <a href="#section-5.2">section 5.2</a>) |
1353 indicating which of the names are now effective and |
1354 which are not. Pictorially, a NDM message has the |
1355 following format including the leader, which is printed |
1356 in hexadecimal, and without any leader padding): |
1357
1358
1359 1 16 17 32 33 48
1360 +----------------+----------------+----------------+
1361 | | | |
1362 | 0F00 | 0003 | 0000 |
1363 | | | |
1364 +----------------+----------------+----------------+
1365 49 64 65 80 81 96
1366 +----------------+----------------+----------------+
1367 | | | |
1368 | 0000 | 0000 | 0000 |
1369 | | | |
1370 +----------------+----------------+----------------+
1371 97 112 113 128 129 144
1372 +----------------+----------------+----------------+
1373 | | | |
1374 | # of entries | name #1 | 0 or 1 |
1375 | | | |
1376 +----------------+----------------+----------------+
1377 145 160 161 176
1378 +----------------+----------------+
1379 | | |
1380 | name #2 | 0 or 1 | etc.
1381 | | |
1382 +----------------+----------------+
1383
1384
1385 NDM Message Format
1386 Figure 5.2
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396 <span class="grey">Khanna &amp; Malis [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
1399
1400
1401 An NDM with zero entries will cause all current
1402 effective names for the host to become non-effective.
1403
1404 Type 4: NOP -- see 1822(3.3). Bits 13-16 of the NOP leader |
1405 are used to determine the host's AHIP-E version -- see |
1406 chapter 6. |
1407
1408 Type 8: Error with Message ID - see 1822(3.3).
1409
1410 Type 11: Name Server Request - This allows the host to use |
1411 the PSN's logical addressing tables as a name server. |
1412 The destination name in the AHIP-E leader is |
1413 translated, and the PSN replies with a Name Server |
1414 Reply message, which lists the physical host addresses |
1415 to which the destination name maps. The type-of- |
1416 service bits (bits 9-11) should be set correctly by |
1417 the host, as the Name Server Reply message contains |
1418 information about characteristics of the subnetwork |
1419 route(s) to that destination, which will depend on the |
1420 type-of-service. |
1421
1422 Type 12: Port List Request - This allows the physical host |
1423 to request the list of names that map to the host port |
1424 over which this request was received by the PSN. The |
1425 PSN replies with a Port List Reply message, which |
1426 lists the names that map to the port. |
1427
1428 Types 5-7,9-10,13-255: Unassigned.
1429
1430 Bits 33-40: Handling Type:
1431 The top two bits (33 and 34) specify the precedence of the
1432 connection. There are 4 precedence levels, level 3 being
1433 the highest and level 0 the lowest. Bits 35-40 are used to
1434 specify up to 64 separate connections at a particular
1435 precedence level and type-of-service.
1436
1437 Bits 41-64: Destination Host:
1438 This field contains the name or address of the destination
1439 host, as described in figures 3.3 and 3.2 respectively. If
1440 it contains a name, the name will be checked for
1441 effectiveness, with an error message returned to the source
1442 host if the name is not effective.
1443
1444 Bits 65-76: Message ID:
1445 This is a host-specified identification used in all type 0
1446 and type 8 messages, and is also used in type 2 messages.
1447 When used in type 0 messages, bits 65-72 are also known as
1448 the Link Field, and should contain values specified in
1449
1450
1451
1452 <span class="grey">Khanna &amp; Malis [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
1455
1456
1457 Assigned Numbers [<a href="#ref-3" title="&quot;Assigned Numbers&quot;">3</a>] appropriate for the host-to-host
1458 protocol being used.
1459
1460 Bits 77-80: Sub-type:
1461 This field is used as a modifier by message types 0, 2, 4,
1462 and 8.
1463
1464 Bits 81-96: Unused
1465
1466
1467 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a> PSN-to-Host AHIP-E Leader Format</span>
1468
1469
1470 1 4 5 8 12 16 17 20 21 22 24 25 32
1471 +--------+--------+-+-+-+--------+--------+-+------+----------------+
1472 | | FORMAT |D|T|R| | |T|LEADER| |
1473 | UNUSED | FLAG |E|H|E| UNUSED | UNUSED |R|FLAGS | MESSAGE TYPE |
1474 | | (15) |L|R|L| | |C| | |
1475 +--------+--------+-+-+-+--------+--------+-+------+----------------+
1476
1477 33 40 41 64
1478 +----------------------+----------------------------------------------+
1479 | | |
1480 | HANDLING TYPE | SOURCE HOST |
1481 | | |
1482 +----------------------+----------------------------------------------+
1483
1484 65 76 77 80 81 96
1485 +-------------------------+--------+----------------------------------+
1486 | | | |
1487 | MESSAGE ID |SUB-TYPE| MESSAGE LENGTH |
1488 | | | |
1489 +-------------------------+--------+----------------------------------+
1490
1491 PSN-to-Host AHIP-E Leader Format
1492 Figure 5.3
1493
1494 Bits 1-4: Unused and set to zero.
1495
1496 Bits 5-8: Format Flag
1497 This field is set to decimal 15 (1111 in binary).
1498
1499 Bits 9-11: Type-of-Service
1500 Specified by the source host (see <a href="#section-5.1">section 5.1</a>).
1501
1502 Bits 12-20: Unused, must be set to zero.
1503
1504 Bit 21: Trace Bit:
1505
1506
1507
1508 <span class="grey">Khanna &amp; Malis [Page 27]</span></pre>
1509 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1510 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
1511
1512
1513 If equal to one, the source host has designated this
1514 message for tracing as it proceeds through the network.
1515 See 1822(5.5).
1516
1517 Bits 22-24: Leader Flags:
1518
1519 Bit 22: Available as a destination host flag.
1520 Bits 23-24: Reserved for future use, set to zero.
1521
1522 Bits 25-32: Message Type:
1523
1524 Type 0: Regular Message - All host-to-host communication
1525 occurs via regular messages, which have several sub-
1526 types. The sub-type field (bits 77-80) is the same as
1527 that sent in the host-to-PSN leader (see <a href="#section-5.1">section 5.1</a>).
1528
1529 Type 1: Error in Leader - See 1822(3.4).
1530
1531 Type 2: PSN Going Down - See 1822(3.4).
1532
1533 Type 3: NDM Reply - This is a reply to the NDM host-to-PSN |
1534 message (see <a href="#section-5.1">section 5.1</a>). It has the same number of |
1535 entries as the NDM message to which it replies, and |
1536 each listed name is accompanied by a zero or a one |
1537 (see figure 5.2). A zero signifies that the name is |
1538 not effective, and a one means that the name is now |
1539 effective. |
1540
1541 Type 4: NOP - The host should discard this message. It is
1542 used during initialization of the PSN/host
1543 communication. The Destination Host field will
1544 contain the physical address of the host port over
1545 which the NOP is being sent. All other fields are
1546 unused.
1547
1548 Type 5: Ready for Next Message (RFNM) - See 1822(3.4).
1549
1550 Type 6: Dead Host Status - See 1822(3.4).
1551
1552 Type 7: Destination Host or PSN Dead (or unknown) - See
1553 1822(3.4).
1554
1555 Type 8: Error in Data - See 1822(3.4).
1556
1557 Type 9: Incomplete Transmission - See 1822(3.4). In
1558 addition to its already defined sub-types, this
1559 message has two new sub-types:
1560 6: Logically Addressed Host Went Down - A logically |
1561
1562
1563
1564 <span class="grey">Khanna &amp; Malis [Page 28]</span></pre>
1565 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
1566 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
1567
1568
1569 addressed message was lost in the network because |
1570 the destination host to which it was being |
1571 delivered went down. The message should be |
1572 resubmitted by the source host, since there may |
1573 be another effective host port to which the |
1574 message could be delivered (see <a href="#section-2.2.3">section 2.2.3</a>). |
1575 7: Network Not Accepting Messages at this Precedence |
1576 Level - bits 33 and 34 encode the minimum |
1577 precedence level currently being accepted by the |
1578 network. See <a href="#section-4.3">section 4.3</a>.
1579
1580 Type 10: Interface Reset - See 1822(3.4).
1581
1582 Type 11: Name Server Reply - This reply to the Name Server |
1583 Request host-to-PSN message contains, following the |
1584 leader and any leader padding, a word with the |
1585 selection policy and the number of physical addresses |
1586 to which the destination name maps, followed by five |
1587 octets per physical address: the first three octets |
1588 contain an AHIP-E address, and the last two contain a |
1589 bit signifying whether or not that particular |
1590 translation is effective and the routing distance |
1591 (expected network transmission delay, in 6.4 ms units) |
1592 to the address's PSN for the type-of-service specified |
1593 in the Name Server Request being replied to. This |
1594 type-of-service will be included in the Name Server |
1595 Reply leader. In figure 5.4, which includes the |
1596 leader without any leader padding and has type-of |
1597 -service set to 000, EFF is 1 for effective and 0 |
1598 for non-effective, the destination name is in the format |
1599 of figure 3.3, and POL is a two-bit number indicating |
1600 the selection policy for the name (see <a href="#section-3.2.2">section 3.2.2</a>): |
1601
1602 0: First reachable.
1603 1: Closest physical address. |
1604 2: Load leveling. |
1605 3: Unused.
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620 <span class="grey">Khanna &amp; Malis [Page 29]</span></pre>
1621 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
1622 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
1623
1624
1625 1 16 17 32 33 40
1626 +----------------+----------------+--------+
1627 | | | |
1628 | 0F00 | 000B | 00 |
1629 | | | |
1630 +----------------+----------------+--------+
1631
1632 41 64 65 80
1633 +------------------------+-----------------+
1634 | | |
1635 | Destination name | 0000 |
1636 | | |
1637 +------------------------+-----------------+
1638 81 96 97 112
1639 +----------------+-+--------------+
1640 | |P| |
1641 | 0000 |O| # of addrs |
1642 | |L| |
1643 +----------------+-+--------------+
1644
1645 113 136 137 152
1646 +--------------------------+-+-------------+
1647 | |E| |
1648 | AHIP-E addr #1 |F| routing dist|
1649 | |F| |
1650 +--------------------------+-+-------------+
1651
1652 153 176 177 192
1653 +--------------------------+-+-------------+
1654 | |E| |
1655 | AHIP-E addr #2 |F| routing dist| etc.
1656 | |F| |
1657 +--------------------------+-+-------------+
1658
1659 Name Server Reply Format
1660 Figure 5.4
1661
1662 Type 12: Port List Reply - This is the reply to the Port |
1663 List Request host-to-PSN message. It contains the |
1664 number of names that map to this physical host port, |
1665 followed by two words per name: the first word |
1666 contains a logical name that maps to this port, and |
1667 the second contains either a zero or a one, |
1668 signifying whether or not that particular translation |
1669 is effective. The format is identical to the type 3 |
1670 NDM Reply message(see figure 5.2). |
1671
1672 Type 13: STOP -- Stop Sending on this Connection. See |
1673
1674
1675
1676 <span class="grey">Khanna &amp; Malis [Page 30]</span></pre>
1677 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
1678 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
1679
1680
1681 <a href="#section-4.2">section 4.2</a>. |
1682
1683 Type 14: SLOW -- maintain window size of 1 on this |
1684 connection. See <a href="#section-4.2">section 4.2</a>. |
1685
1686 Type 15: Name or Address Error - This message is sent in |
1687 response to a type 0 message from a host that |
1688 contained an erroneous Destination Host field. Its |
1689 sub-types are: |
1690 2: The Destination Host name is not authorized. |
1691 3: The physical host to which this singly-homed |
1692 Destination Host name translated is authorized |
1693 and up, but not effective. If the host was |
1694 actually down, a type 7 message would be |
1695 returned, not a type 15. |
1696 5: The multi-homed Destination Host name is |
1697 authorized but has no available effective |
1698 translations. |
1699 6: A logically-addressed uncontrolled packet was sent |
1700 to a dead or non-effective host port. However, |
1701 if it is resubmitted, there may be another |
1702 effective host port to which the PSN may be able |
1703 to attempt to send the packet. |
1704 7: Logical addressing is not in use. |
1705 The PSN has no table of mappings from logical |
1706 addresses to physical host ports. |
1707 0, 1, 4, 8-15: Unassigned |
1708
1709 Type 16: GO -- maintain window size of 8 on this |
1710 connection. See <a href="#section-4.2">section 4.2</a>. |
1711
1712 Type 17: Network Precedence Level Cutoff Change -- bits 33 |
1713 and 34 encode the minimum precedence level currently |
1714 being accepted by the network. See <a href="#section-4.3">section 4.3</a>.
1715
1716 Types 18-255: Unassigned.
1717
1718 Bits 33-40: Handling Type:
1719 This has the value assigned by the source host (see
1720 1822(3.1)). This field is only used in message types 0, 5-
1721 9, and 13-16.
1722
1723 Bits 41-64: Source Host:
1724 See 1882(3.4). For type 0 messages this contains the
1725 physical address of the source host, in the format detailed
1726 in figure 3.2. For type 4 messages, this contains the
1727 physical address of the local host. For messages of type
1728 5-9, 11 and 13-16 which are responses to messages from the
1729
1730
1731
1732 <span class="grey">Khanna &amp; Malis [Page 31]</span></pre>
1733 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
1734 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
1735
1736
1737 local host, this contains the destination name as specified
1738 in the message from the local host.
1739
1740 Bits 65-76: Message ID:
1741 For message types 0, 5, 7-9, and 15, this is the value
1742 assigned by the source host to identify the message (see
1743 <a href="#section-5.1">section 5.1</a>). This field is also used by message types 2
1744 and 6.
1745
1746 Bits 77-80: Sub-type:
1747 This field is used as a modifier by message types 0-2, 5-7,
1748 9, and 15.
1749
1750 Bits 81-96: Message Length:
1751 This field is contained in type 0 messages only, and is the
1752 actual length in bits of the message (exclusive of leader,
1753 leader padding, and hardware padding) as computed by the
1754 PSN.
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788 <span class="grey">Khanna &amp; Malis [Page 32]</span></pre>
1789 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
1790 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
1791
1792
1793 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a> AHIP-E VERSIONS</span>
1794
1795 This specification provides three versions of AHIP-E and allows a host
1796 to specify its version in bits 13-16 of the leader of the NOP. The PSN
1797 will set the version of a host based on the value contained in the most
1798 recent NOP that it has received from the host. Thus, a host can change
1799 the PSN's idea of its version by issuing a NOP containing a different
1800 version value. Note that the version field in all other host-to-PSN
1801 messages will be ignored by the PSN.
1802
1803 Version 0:
1804
1805 A host that doesn't change its current AHIP implementation will
1806 presumably have the version bits in the AHIP leader set to zero.
1807 Version 0, thus, is nothing but current AHIP.
1808
1809 A version 0 host will not receive any of the new AHIP-E messages from
1810 the PSN, nor will the PSN expect any of the new host-to-PSN message
1811 types from the host. The type-of-service bits will always be set to
1812 zero in the PSN-to-host leader.
1813
1814 Version 1:
1815
1816 A version 1 host will be able to use logical names to address other
1817 hosts, will be able to use the 10-bit PSN field, will be able to specify
1818 desired type-of-service to the PSN, but will not receive any of the new
1819 AHIP-E messages from the PSN. The PSN will not expect any of the new
1820 host-to-PSN message types from the host either.
1821
1822 To implement version 1, a host need only make the following changes to
1823 its AHIP implementation:
1824
1825 1. Set the version number field to 1 when sending type 4
1826 messages (NOPs).
1827
1828 2. When sending type 0 messages, copy IP address bits 8-31
1829 into bits 41-64 of the AHIP leader.
1830
1831 3. When sending type 0 messages, copy IP header bits 11-13
1832 to AHIP leader bits 9-11.
1833
1834 Version 2:
1835
1836 A version 2 host is one that is fully compliant with the AHIP-E protocol
1837 as described in this document. In addition to being able to take
1838 advantage of the features described under version 1 above, it should be
1839 able to send and receive all the new AHIP-E messages described in this
1840 document.
1841
1842
1843
1844 <span class="grey">Khanna &amp; Malis [Page 33]</span></pre>
1845 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
1846 <span class="grey"><a href="./rfc1005">RFC 1005</a> May 1987</span>
1847
1848
1849 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a> REFERENCES</span>
1850
1851 [<a id="ref-1">1</a>] "Specifications for the Interconnection of a Host and an
1852 PSN", BBN Report 1822, as found in "DDN Protocol Handbook",
1853 December 1985, vol. 3, <a href="#section-3.10">section 3.10</a>.
1854
1855 [<a id="ref-2">2</a>] E. C. Rosen et. al., "ARPANET Routing Algorithm
1856 Improvements", Internet Experimenter's Note 183 (also
1857 published as BBN Report 4473, Vol. 1), August 1980, pp. 55-
1858 107.
1859
1860 [<a id="ref-3">3</a>] J. Reynolds and J. Postel, "Assigned Numbers", Request For
1861 Comments 990, November 1986.
1862
1863 [<a id="ref-4">4</a>] J. Postel, ed., "Internet Protocol -- DARPA Internet
1864 Program Protocol Specification", Request for Comments 791,
1865 September 1981.
1866
1867 [<a id="ref-5">5</a>] J. Postel, "Address Mappings", Request for Comments 796,
1868 September 1981, as found in "DDN Protocol Handbook", vol.
1869 3, <a href="#section-3.4">section 3.4</a>.
1870
1871 [<a id="ref-6">6</a>] "Defense Data Network X.25 Host Interface Specification",
1872 pp. 497-498, DDN protocol handbook, vol. 1, December 1985.
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900 Khanna &amp; Malis [Page 34]
1901 </pre>