Debian Codegraph @

rfc2209.html

raw
1 <pre>Network Working Group R. Braden
2 Request For Comments: 2209 ISI
3 Category: Informational L. Zhang
4 UCLA
5 September 1997
6
7 <span class="h1">Resource ReSerVation Protocol (RSVP) --</span>
8 <span class="h1">Version 1 Message Processing Rules</span>
9
10 Status of this Memo
11
12
13 This memo provides information for the Internet community. It does
14 not specify an Internet standard of any kind. Distribution of this
15 memo is unlimited.
16
17 Abstract
18
19 This memo contains an algorithmic description of the rules used by an
20 RSVP implementation for processing messages. It is intended to
21 clarify the version 1 RSVP protocol specification.
22
23 This memo provides a generic description of the rules for the
24 operation of Version 1 of RSVP [<a href="./rfc2205">RFC 2205</a>]. It is intended to outline
25 a set of algorithms that will accomplish the needed function,
26 omitting many details.
27
28 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. GENERIC DATA STRUCTURES</span>
29
30 This memo assumes the generic interface calls defined in [<a href="./rfc2005">RFC 2005</a>]
31 and the following data structures. An actual implementation may use
32 additional or different data structures and interfaces. The data
33 structure fields that are shown are required unless they are
34 explicitly labelled as optional.
35
36 o PSB -- Path State Block
37
38 Each PSB holds path state for a particular (session, sender)
39 pair, defined by SESSION and SENDER_TEMPLATE objects,
40 respectively, received in a PATH message.
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Braden &amp; Zhang Informational [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc2209">RFC 2209</a> RSVP-Message Processing September 1997</span>
55
56
57 PSB contents include the following values from a PATH message:
58
59 - Session
60
61 - Sender_Template
62
63 - Sender_Tspec
64
65 - The previous hop IP address and the Logical Interface
66 Handle (LIH) from a PHOP object
67
68 - The remaining IP TTL
69
70 - POLICY_DATA and/or ADSPEC objects (optional)
71
72 - Non_RSVP flag
73
74 - E_Police flag
75
76 - Local_Only flag
77
78 In addition, the PSB contains the following information provided
79 by routing: OutInterface_list, which is the list of outgoing
80 interfaces for this (sender, destination), and IncInterface,
81 which is the expected incoming interface. For a unicast
82 destination, OutInterface_list contains one entry and
83 IncInterface is undefined.
84
85 Note that there may be more than one PSB for the same (session,
86 sender) pair but different incoming interfaces. At most one of
87 these, which will have the Local_Only flag off, will be the PSB
88 used for forwarding PATH messages downstream; we will refer to
89 it as the "forwarding PSB" in the following. The other PSB's
90 will have the Local_Only flag on and an empty
91 OutInterface_list.h The Local_Only flag is needed to correctly
92 match PSB's against RSB's, by the rules of [<a href="./rfc2205">RFC 2205</a>].
93
94 o RSB -- Reservation State Block
95
96 Each RSB holds a reservation request that arrived in a
97 particular RESV message, corresponding to the triple: (session,
98 next hop, Filter_spec_list). Here "Filter_spec_list" may be a
99 list of FILTER_SPECs (for SE style), a single FILTER_SPEC (FF
100 style), or empty (WF style). We define the virtual object type
101 "FILTER_SPEC*" for such a data structure.
102
103
104
105
106
107
108 <span class="grey">Braden &amp; Zhang Informational [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc2209">RFC 2209</a> RSVP-Message Processing September 1997</span>
111
112
113 RSB contents include:
114
115 - Session specification
116
117 - Next hop IP address
118
119 - Filter_spec_list
120
121 - The outgoing (logical) interface OI on which the
122 reservation is to be made or has been made.
123
124 - Style
125
126 - Flowspec
127
128 - A SCOPE object (optional, depending upon style)
129
130 - RESV_CONFIRM object that was received (optional)
131
132 o TCSB -- Traffic Control State Block
133
134 Each TCSB holds the reservation specification that has been
135 handed to traffic control for a specific outgoing interface. In
136 general, TCSB information is derived from RSB's for the same
137 outgoing interface. Each TCSB defines a single reservation for
138 a particular triple: (session, OI, Filter_spec_list). TCSB
139 contents include:
140
141 - Session
142
143 - OI (Outgoing Interface)
144
145 - Filter_spec_list
146
147 - TC_Flowspec, the effective flowspec, i.e., the LUB over the
148 corresponding FLOWSPEC values from matching RSB's.
149 TC_Flowspec is passed to traffic control to make the actual
150 reservation.
151
152 - Fwd_Flowspec, the updated object to be forwarded
153 after merging.
154
155 - TC_Tspec, equal to Path_Te, the effective sender Tspec.
156
157 - Police Flags
158
159 The flags are E_Police_Flag, M_Police_Flag, and
160 B_Police_Flag.
161
162
163
164 <span class="grey">Braden &amp; Zhang Informational [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc2209">RFC 2209</a> RSVP-Message Processing September 1997</span>
167
168
169 - Rhandle, F_Handle_list
170
171 Handles returned by the traffic control interface,
172 corresponding to a flowspec and perhaps a list of filter
173 specs.
174
175 - A RESV_CONFIRM object to be forwarded.
176
177 o BSB -- Blockade State Block
178
179 Each BSB contains an element of blockade state. Depending upon
180 the reservation style in use, the BSB's may be per (session,
181 sender_template) pair or per (session, PHOP) pair. In practice,
182 an implementation might embed a BSB within a PSB; however, for
183 clarity we describe BSB's independently.
184
185 The contents of a BSB include:
186
187 - Session
188
189 - Sender_Template (which is also a filter spec)
190
191 - PHOP
192
193 - FLOWSPEC Qb
194
195 - Blockade timer Tb
196
197 The following Boolean Flag variables are used in this section:
198 Path_Refresh_Needed, Resv_Refresh_Needed, Tear_Needed,
199 Need_Scope, B_Merge, and NeworMod. Refresh_PHOP_list is a
200 variable-length list of PHOPs to be refreshed.
201
202 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. PROCESSING RULES</span>
203
204 MESSAGE ARRIVES
205
206 Verify version number and RSVP checksum, and discard message if any
207 mismatch is found.
208
209 If the message type is not PATH or PTEAR or RACK and if the IP
210 destination address does not match any of the addresses of the local
211 interfaces, then forward the message to IP destination address and
212 return.
213
214 Parse the sequence of objects in the message. If any required
215 objects are missing or the length field of the common header does not
216 match an object boundary, discard the message and return.
217
218
219
220 <span class="grey">Braden &amp; Zhang Informational [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc2209">RFC 2209</a> RSVP-Message Processing September 1997</span>
223
224
225 Verify the INTEGRITY object, if any. If the check fails, discard the
226 message and return.
227
228 Verify the consistent use of port fields. If the DstPort in the
229 SESSION object is zero but the SrcPort in a SENDER_TEMPLATE or
230 FILTER_SPEC object is non-zero, then the message has a "conflicting
231 source port" error; silently discard the message and return.
232
233 Processing of POLICY_DATA objects will be specified in the future.
234
235 Further processing depends upon message type.
236
237 PATH MESSAGE ARRIVES
238
239 Assume the PATH message arrives on interface InIf.
240
241 Process the sender descriptor object sequence in the message as
242 follows. The Path_Refresh_Needed and Resv_Refresh_Needed flags are
243 initially off.
244
245 o Search for a path state block (PSB) whose (session,
246 sender_template) pair matches the corresponding objects in the
247 message, and whose IncInterface matches InIf.
248
249 During this search:
250
251 1. If a PSB is found whose session matches the
252 DestAddress and Protocol Id fields of the received
253 SESSION object, but the DstPorts differ and one is
254 zero, then build and send a "Conflicting Dst Port"
255 PERR message, drop the PATH message, and return.
256
257 2. If a PSB is found with a matching sender host but the
258 Src Ports differ and one of the SrcPorts is zero, then
259 build and send an "Ambiguous Path" PERR message, drop
260 the PATH message, and return.
261
262 3. If a forwarding PSB is found, i.e., a PSB that matches
263 the (session, sender_template) pair and whose
264 Local_Only flag is off, save a pointer to it in the
265 variable fPSB. If none is found, set fPSB to NULL.
266
267 o If there was no matching PSB, then:
268
269 1. Create a new PSB.
270
271 2. Copy contents of the SESSION, SENDER_TEMPLATE,
272 SENDER_TSPEC, and PHOP (IP address and LIH) objects
273
274
275
276 <span class="grey">Braden &amp; Zhang Informational [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc2209">RFC 2209</a> RSVP-Message Processing September 1997</span>
279
280
281 into the PSB.
282
283 3. If the sender is from the local API, set
284 OutInterface_List to the single interface whose
285 address matches the sender address, and make
286 IncInterface undefined. Otherwise, turn on the
287 Local_Only flag.
288
289 4. Turn on the Path_Refresh_Needed flag.
290
291 o Otherwise (there is a matching PSB):
292
293 - If the PHOP IP address, the LIH, or Sender_Tspec
294 differs between the message and the PSB, copy the new
295 value into the PSB and turn on the Path_Refresh_Needed
296 flag. If the PHOP IP address or the LIH differ, also
297 turn on the Resv_Refresh_Needed flag.
298
299 o Call the resulting PSB the "current PSB" (cPSB). Update
300 the cPSB, as follows:
301
302 - Start or Restart the cleanup timer for the PSB.
303
304 - If the message contains an ADSPEC object, copy it into
305 the PSB.
306
307 - Copy E_Police flag from SESSION object into PSB.
308
309 - Store the received TTL into the PSB.
310 If the received TTL differs from Send_TTL in the RSVP
311 common header, set the Non_RSVP flag on in the PSB.
312
313 o If the PSB is new or if there is no route change
314 notification in place, then perform the following routing
315 manipulations, but not if the cPSB is from the local API.
316
317 1. Invoke the appropriate Route_Query routine using
318 DestAddress from SESSION and (for multicast routing)
319 SrcAddress from Sender_Template.
320
321 Call the results (Rt_OutL, Rt_InIf).
322
323 2. If the destination is multicast and Rt_InIf differs
324 from IncInterface in the cPSB, but fPSB points to the
325 cPSB, then do the following.
326
327 - Turn on the Local_Only flag and clear the
328 OutInterface_list of the fPSB. Set the fPSB
329
330
331
332 <span class="grey">Braden &amp; Zhang Informational [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc2209">RFC 2209</a> RSVP-Message Processing September 1997</span>
335
336
337 pointer to NULL.
338
339 - Search for a PSB for the same (session,
340 sender_template) pair whose IncInterface matches
341 Rt_InIf. If one is found, set fPSB to point to
342 it.
343
344 3. If the destination is multicast and Rt_InIf is the
345 same as IncInterface in the cPSB, but fPSB does not
346 point to the cPSB, then do the following.
347
348 - Copy into the cPSB the OutInterface_list from the
349 PSB, if any, pointed to by fPSB. Clear
350 OutInterface_list and turn on the Local_Only flag
351 in the PSB pointed to by fPSB, if any.
352
353 - Turn off the Local_Only flag in the cPSB and set
354 fPSB to point to cPSB.
355
356 4. If Rt_OutL differs from OutInterface_list of the PSB
357 pointed to by fPSB, then:
358
359 - Update the OutInterface_list of the PSB from
360 Rt_OutL, and then execute the PATH LOCAL REPAIR
361 event sequence below.
362
363 o If the Path_Refresh_Needed flag is now off, drop the PATH
364 message and return.
365
366 Otherwise (the path state is new or modified), do
367 refreshes, upcalls, and state updates as follows.
368
369 1. If this PATH message came from a network interface and
370 not from a local application, make a Path Event upcall
371 for each local application for this session:
372
373 Call: &lt;Upcall_Proc&gt;( session-id, PATH_EVENT,
374 flags, sender_tspec, sender_template
375 [ , ADSPEC] [ , POLICY_DATA] )
376
377 2. If OutInterface_list is not empty, execute the PATH
378 REFRESH event sequence (below) for the sender defined
379 by the PSB.
380
381 3. Search for any matching reservation state, i.e., an
382 RSB whose Filter_spec_list includes a FILTER_SPEC
383 matching the SENDER_TEMPLATE and whose OI appears in
384 the OutInterface_list, and make this the `active RSB'.
385
386
387
388 <span class="grey">Braden &amp; Zhang Informational [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc2209">RFC 2209</a> RSVP-Message Processing September 1997</span>
391
392
393 If none is found, drop the PATH message and return.
394
395 4. Execute the RESV REFRESH sequence (below) for the PHOP
396 in the PSB.
397
398 5. Execute the event sequence UPDATE TRAFFIC CONTROL to
399 update the local traffic control state if necessary.
400 This sequence will turn on the Resv_Refresh_Needed
401 flag if the traffic control state has been modified in
402 a manner that should trigger a reservation refresh.
403 If so, execute the RESV REFRESH sequence for the PHOP
404 in the PSB.
405
406 o Drop the PATH message and return.
407
408 PTEAR MESSAGE ARRIVES
409
410 o Search for a PSB whose (Session, Sender_Template) pair
411 matches the corresponding objects in the message. If no
412 matching PSB is found, drop the PTEAR message and return.
413
414 o Forward a copy of the PTEAR message to each outgoing
415 interface listed in OutInterface_list of the PSB.
416
417 o Find each RSB that matches this PSB, i.e., whose
418 Filter_spec_list matches Sender_Template in the PSB and
419 whose OI is included in OutInterface_list.
420
421 1. If the RSB style is explicit, then:
422 - Delete from Filter_spec_list the FILTER_SPEC that
423 matches the PSB.
424
425 - if Filter_spec_list is now empty, delete the RSB.
426
427 2. Otherwise (RSB style is wildcard) then:
428
429 - If this RSB matches no other PSB, then delete the
430 RSB.
431
432 3. If an RSB was found, execute the event sequence UPDATE
433 TRAFFIC CONTROL (below) to update the traffic control
434 state to be consistent with the current reservation
435 and path state.
436
437 o Delete the PSB.
438
439 o Drop the PTEAR message and return.
440
441
442
443
444 <span class="grey">Braden &amp; Zhang Informational [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc2209">RFC 2209</a> RSVP-Message Processing September 1997</span>
447
448
449 PERR MESSAGE ARRIVES
450
451 o Search for a PSB whose (SESSION, SENDER_TEMPLATE) pair
452 matches the corresponding objects in the message. If no
453 matching PSB is found, drop the PERR message and return.
454
455 o If the previous hop address in the PSB is the local API,
456 make an error upcall to the application:
457
458 Call: &lt;Upcall_Proc&gt;( session-id, PATH_ERROR,
459 Error_code, Error_value, Node_Addr,
460 Sender_Template [ , Policy_Data] )
461
462 Any SENDER_TSPEC or ADSPEC object in the message is
463 ignored.
464
465 Otherwise, send a copy of the PERR message to the PHOP IP
466 address.
467
468 o Drop the PERR message and return.
469
470 RESV MESSAGE ARRIVES
471
472 Initially, Refresh_PHOP_list is empty and the
473 Resv_Refresh_Needed and NeworMod flags are off. These variables
474 are used to control immediate reservation refreshes.
475
476 o Determine the Outgoing Interface OI
477
478 The logical outgoing interface OI is taken from the LIH in
479 the NHOP object. (If the physical interface is not implied
480 by the LIH, it can be learned from the interface matching
481 the IP destination address).
482
483 o Check the path state
484
485 1. If there are no existing PSB's for SESSION then build
486 and send a RERR message (as described later)
487 specifying "No path information", drop the RESV
488 message, and return.
489
490 2. If a PSB is found with a matching sender host but the
491 SrcPorts differ and one of the SrcPorts is zero, then
492 build and send an "Ambiguous Path" PERR message, drop
493 the RESV message, and return.
494
495
496
497
498
499
500 <span class="grey">Braden &amp; Zhang Informational [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc2209">RFC 2209</a> RSVP-Message Processing September 1997</span>
503
504
505 o Check for incompatible styles.
506
507 If any existing RSB for the session has a style that is
508 incompatible with the style of the message, build and send
509 a RERR message specifying "Conflicting Style", drop the
510 RESV message, and return.
511
512 Process the flow descriptor list to make reservations, as
513 follows, depending upon the style. The following uses a filter
514 spec list struct Filtss of type FILTER_SPEC* (defined earlier).
515
516 For FF style: execute the following steps independently for each
517 flow descriptor in the message, i.e., for each (FLOWSPEC,
518 Filtss) pair. Here the structure Filtss consists of the
519 FILTER_SPEC from the flow descriptor.
520
521 For SE style, execute the following steps once for (FLOWSPEC,
522 Filtss), with Filtss consisting of the list of FILTER_SPEC
523 objects from the flow descriptor.
524
525 For WF style, execute the following steps once for (FLOWSPEC,
526 Filtss), with Filtss an empty list.
527
528 o Check the path state, as follows.
529
530 1. Locate the set of PSBs (senders) that route to OI and
531 whose SENDER_TEMPLATEs match a FILTER_SPEC in Filtss.
532
533 If this set is empty, build and send an error message
534 specifying "No sender information", and continue with
535 the next flow descriptor in the RESV message.
536
537 2. If the style has explicit sender selection (e.g., FF
538 or SE) and if any FILTER_SPEC included in Filtss
539 matches more than one PSB, build and send a RERR
540 message specifying "Ambiguous filter spec" and
541 continue with the next flow descriptor in the RESV
542 message.
543
544 3. If the style is SE and if some FILTER_SPEC included in
545 Filtss matches no PSB, delete that FILTER_SPEC from
546 Filtss.
547
548 4. Add the PHOP from the PSB to Refresh_PHOP_list, if the
549 PHOP is not already on the list.
550
551
552
553
554
555
556 <span class="grey">Braden &amp; Zhang Informational [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc2209">RFC 2209</a> RSVP-Message Processing September 1997</span>
559
560
561 o Find or create a reservation state block (RSB) for
562 (SESSION, NHOP). If the style is distinct, Filtss is also
563 used in the selection. Call this the "active RSB".
564
565 o If the active RSB is new:
566
567 1. Set the session, NHOP, OI and style of the RSB from
568 the message.
569
570 2. Copy Filtss into the Filter_spec_list of the RSB.
571
572 3. Copy the FLOWSPEC and any SCOPE object from the
573 message into the RSB.
574
575 4. Set NeworMod flag on.
576
577 o If the active RSB is not new, check whether Filtss from the
578 message contains FILTER_SPECs that are not in the RSB; if
579 so, add the new FILTER_SPECs and turn on the NeworMod flag.
580
581 o Start or restart the cleanup timer on the active RSB, or,
582 in the case of SE style, on each FILTER_SPEC of the RSB
583 that also appears in Filtss.
584
585 o If the active RSB is not new, check whether STYLE, FLOWSPEC
586 or SCOPE objects have changed; if so, copy changed object
587 into RSB and turn on the NeworMod flag.
588
589 o If the message contained a RESV_CONFIRM object, copy it
590 into the RSB and turn on NeworMod flag.
591
592 o If the NeworMod flag is off, continue with the next flow
593 descriptor in the RESV message, if any.
594
595 o Otherwise (the NeworMod flag is on, i.e., the active RSB is
596 new or modified), execute the UPDATE TRAFFIC CONTROL event
597 sequence (below). If the result is to modify the traffic
598 control state, this sequence will turn on the
599 Resv_Refresh_Needed flag and make a RESV_EVENT upcall to
600 any local application.
601
602 If the UPDATE TRAFFIC CONTROL sequence fails with an error,
603 then delete a new RSB but restore the original reservation
604 in an old RSB.
605
606 o Continue with the next flow descriptor.
607
608
609
610
611
612 <span class="grey">Braden &amp; Zhang Informational [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc2209">RFC 2209</a> RSVP-Message Processing September 1997</span>
615
616
617 o When all flow descriptors have been processed, check the
618 Resv_Refresh_Needed flag. If it is now on, execute the
619 RESV REFRESH sequence (below) for each PHOP in
620 Refresh_PHOP_list.
621
622 o Drop the RESV message and return.
623
624 If processing a RESV message finds an error, a RERR message
625 is created containing flow descriptor and an ERRORS object.
626 The Error Node field of the ERRORS object is set to the IP
627 address of OI, and the message is sent unicast to NHOP.
628
629 RTEAR MESSAGE ARRIVES
630
631 Processing of a RTEAR message roughly parallels the processing
632 of the corresponding RESV message
633
634 A RTEAR message arrives with an IP destination address matching
635 outgoing interface OI. Flag Resv_Refresh_Needed is initially
636 off and Refresh_PHOP_list is empty.
637
638 o Determine the Outgoing Interface OI
639
640 The logical outgoing interface OI is taken from the LIH in
641 the NHOP object. (If the physical interface is not implied
642 by the LIH, it can be learned from the interface matching
643 the IP destination address).
644
645 o Process the flow descriptor list in the RTEAR message to
646 tear down local reservation state, as follows, depending
647 upon the style. The following uses a filter spec list
648 struct Filtss of type FILTER_SPEC* (defined earlier).
649
650 For FF style: execute the following steps independently for
651 each flow descriptor in the message, i.e., for each
652 (FLOWSPEC, Filtss) pair. Here the structure Filtss
653 consists of the FILTER_SPEC from the flow descriptor.
654
655 For SE style, execute the following steps once for
656 (FLOWSPEC, Filtss), with Filtss consisting of the list of
657 FILTER_SPEC objects from the flow descriptor.
658
659 For WF style, execute the following steps once for
660 (FLOWSPEC, Filtss), with Filtss an empty list.
661
662
663
664
665
666
667
668 <span class="grey">Braden &amp; Zhang Informational [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc2209">RFC 2209</a> RSVP-Message Processing September 1997</span>
671
672
673 1. Find an RSB matching (SESSION, NHOP). If the style is
674 distinct, Filtss is also used in the selection. Call
675 this the "active RSB". If no active RSB is found,
676 continue with next flow descriptor.
677
678 2. Check the style
679
680 If the active RSB has a style that is incompatible
681 with the style of the message, drop the RTEAR message
682 and return.
683
684 3. Delete from the active RSB each FILTER_SPEC that
685 matches a FILTER_SPEC in Filtss.
686
687 4. If all FILTER_SPECs have now been deleted from the
688 active RSB, delete the active RSB.
689
690 5. Execute the UPDATE TRAFFIC CONTROL event sequence
691 (below) to update the traffic control state to be
692 consistent with the reservation state. If the result
693 is to modify the traffic control state, the
694 Resv_Refresh_Needed flag will be turned on and a
695 RESV_EVENT upcall will be made to any local
696 application.
697
698 6. Continue with the next flow descriptor.
699
700 o All flow descriptors have been processed.
701
702 Build and send any RTEAR messages to be forwarded, in the
703 following manner.
704
705 1. Select each PSB that routes to the outgoing interface
706 OI, and, for distinct style, that has a
707 SENDER_TEMPLATE matching Filtss.
708
709 2. Select a flow descriptor (Qj,Fj) (where Fj may be a
710 list) in the RTEAR message whose FILTER_SPEC matches
711 the SENDER_TEMPLATE in the PSB. If not match is
712 found, return for next PSB.
713
714 - Search for an RSB (for any outgoing interface) to
715 which the PSB routes and whose Filter_spec_list
716 includes the SENDER_TEMPLATE from the PSB.
717
718 - If an RSB is found, add the PHOP of the PSB to
719 the Refresh_PHOP_list.
720
721
722
723
724 <span class="grey">Braden &amp; Zhang Informational [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc2209">RFC 2209</a> RSVP-Message Processing September 1997</span>
727
728
729 - Otherwise (no RSB is found), add the flow
730 descriptor (Qj,Fj) to the new RTEAR message being
731 built, in a manner appropriate to the style.
732
733 - Continue with the next PSB.
734
735 3. If the next PSB is for a different PHOP or the last
736 PSB has been processed, forward any RTEAR message that
737 has been built.
738
739 o If any PSB's were found in the preceding step, and if the
740 Resv_Refresh_Needed flag is now on, execute the RESV
741 REFRESH sequence (below) for each PHOP in
742 Refresh_PHOP_list.
743
744 o Drop the RTEAR message and return.
745
746 RERR MESSAGE ARRIVES
747
748 A RERR message arrives through the (real) incoming interface
749 In_If.
750
751 o If there is no path state for SESSION, drop the RERR
752 message and return.
753
754 o If the Error Code = 01 (Admission Control failure), do
755 special processing as follows:
756
757 1. Find or create a Blockade State Block (BSB), in the
758 following style-dependent manner.
759
760 For WF (wildcard) style, there will be one BSB per
761 (session, PHOP) pair.
762
763 For FF style, there will be one BSB per (session,
764 filter_spec) pair. Note that an FF style RERR message
765 carries only one flow descriptor.
766
767 For SE style, there will be one BSB per (session,
768 filter_spec), for each filter_spec contained in the
769 filter spec list of the flow descriptor.
770
771 2. For each BSB in the preceding step, set (or replace)
772 its FLOWSPEC Qb with FLOWSPEC from the message, and
773 set (or reset) its timer Tb to Kb*R seconds. If the
774 BSB is new, set its PHOP value, and set its
775 Sender_Template equal to the appropriate filter_spec
776 from the message.
777
778
779
780 <span class="grey">Braden &amp; Zhang Informational [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc2209">RFC 2209</a> RSVP-Message Processing September 1997</span>
783
784
785 3. Execute the RESV REFRESH event sequence (shown below)
786 for the previous hop PHOP, but only with the B_Merge
787 flag off. That is, if processing in the RESV REFRESH
788 sequence reaches the point of turning the B_Merge flag
789 on (because all matching reservations are blockaded),
790 do not turn it on but instead exit the REFRESH
791 sequence and return here.
792
793 o Execute the following for each RSB for this session whose
794 OI differs from In_If and whose Filter_spec_list has at
795 least one filter spec in common with the FILTER_SPEC* in
796 the RERR message. For WF style, empty FILTER_SPEC*
797 structures are assumed to match.
798
799 1. If Error_Code = 01 and the InPlace flag in the
800 ERROR_SPEC is 1 and one or more of the BSB's
801 found/created above has a Qb that is strictly greater
802 than Flowspec in the RSB, then continue with the next
803 matching RSB, if any.
804
805 2. If NHOP in the RSB is the local API, then:
806
807 - If the FLOWSPEC in the RERR message is strictly
808 greater than the RSB Flowspec, then turn on the
809 NotGuilty flag in the ERROR_SPEC.
810
811 - Deliver an error upcall to application:
812
813 Call: &lt;Upcall_Proc&gt;( session-id, RESV_ERROR,
814 Error_code, Error_value,
815 Node_Addr, Error_flags,
816 Flowspec, Filter_Spec_List
817 [ , Policy_data] )
818
819 and continue with the next RSB.
820
821 3. If the style has wildcard sender selection, use the
822 SCOPE object SC.In from the RERR message to construct
823 a SCOPE object SC.Out to be forwarded. SC.Out should
824 contain those sender addresses that appeared in SC.In
825 and that route to OI, as determined by scanning the
826 PSB's. If SC.Out is empty, continue with the next
827 RSB.
828
829 4. Create a new RERR message containing the error flow
830 descriptor and send to the NHOP address specified by
831 the RSB. Include SC.Out if the style has wildcard
832 sender selection.
833
834
835
836 <span class="grey">Braden &amp; Zhang Informational [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc2209">RFC 2209</a> RSVP-Message Processing September 1997</span>
839
840
841 5. Continue with the next RSB.
842
843 o Drop the RERR message and return.
844
845 RESV CONFIRM ARRIVES
846
847 o If the (unicast) IP address found in the RESV_CONFIRM
848 object in the RACK message matches an interface of the
849 node, a confirmation upcall is made to the matching
850 application:
851
852 Call: &lt;Upcall_Proc&gt;( session-id, RESV_CONFIRM,
853 Error_code, Error_value, Node_Addr,
854 LUB-Used, nlist, Flowspec,
855 Filter_Spec_List, NULL, NULL )
856
857 o Otherwise, forward the RACK message to the IP address in
858 its RESV_CONFIRM object.
859
860 Drop the RACK message and return.
861
862 UPDATE TRAFFIC CONTROL
863
864 The sequence is invoked by many of the message arrival sequences
865 to set or adjust the local traffic control state in accordance
866 with the current reservation and path state. An implicit
867 parameter of this sequence is the `active' RSB.
868
869 If the result is to modify the traffic control state, this
870 sequence notifies any matching local applications with a
871 RESV_EVENT upcall. If the state change is such that it should
872 trigger immediate RESV refresh messages, it also turns on the
873 Resv_Refresh_Needed flag.
874
875 o Compute the traffic control parameters using the following
876 steps.
877
878 1. Initially the local flag Is_Biggest is off.
879
880 2. Consider the set of RSB's matching SESSION and OI from
881 the active RSB. If the style of the active RSB is
882 distinct, then the Filter_spec_list must also be
883 matched.
884
885 - Compute the effective kernel flowspec,
886 TC_Flowspec, as the LUB of the FLOWSPEC values in
887 these RSB's.
888
889
890
891
892 <span class="grey">Braden &amp; Zhang Informational [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc2209">RFC 2209</a> RSVP-Message Processing September 1997</span>
895
896
897 - Compute the effective traffic control filter spec
898 (list) TC_Filter_Spec* as the union of the
899 Filter_spec_lists from these RSB's.
900
901 - If the active RSB has a FLOWSPEC larger than all
902 the others, turn on the Is_Biggest flag.
903
904 3. Scan all RSB's matching session and Filtss, for all
905 OI. Set TC_B_Police_flag on if TC_Flowspec is smaller
906 than, or incomparable to, any FLOWSPEC in those RSB's.
907
908 4. Locate the set of PSBs (senders) whose
909 SENDER_TEMPLATEs match Filter_spec_list in the active
910 RSB and whose OutInterface_list includes OI.
911
912 5. Set TC_E_Police_flag on if any of these PSBs have
913 their E_Police flag on. Set TC_M_Police_flag on if it
914 is a shared style and there is more than one PSB in
915 the set.
916
917 6. Compute Path_Te as the sum of the SENDER_TSPEC objects
918 in this set of PSBs.
919
920 o Search for a TCSB matching SESSION and OI; for distinct
921 style (FF), it must also match Filter_spec_list.
922
923 If none is found, create a new TCSB.
924
925 o If TCSB is new:
926
927 1. Store TC_Flowspec, TC_Filter_Spec*, Path_Te, and the
928 police flags into TCSB.
929
930 2. Turn the Resv_Refresh_Needed flag on and make the
931 traffic control call:
932
933 TC_AddFlowspec( OI, TC_Flowspec,
934 Path_Te, police_flags)
935 -&gt; Rhandle, Fwd_Flowspec
936
937 3. If this call fails, build and send a RERR message
938 specifying "Admission control failed" and with the
939 InPlace flag off. Delete the TCSB, delete any
940 RESV_CONFIRM object from the active RSB, and return.
941
942
943
944
945
946
947
948 <span class="grey">Braden &amp; Zhang Informational [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc2209">RFC 2209</a> RSVP-Message Processing September 1997</span>
951
952
953 4. Otherwise (call succeeds), record Rhandle and
954 Fwd_Flowspec in the TCSB. For each filter_spec F in
955 TC_Filter_Spec*, call:
956
957 TC_AddFilter( OI, Rhandle, Session, F)
958 -&gt; Fhandle
959
960 and record the returned Fhandle in the TCSB.
961
962 o Otherwise, if TCSB is not new but no effective kernel
963 flowspec TC_Flowspec was computed earlier, then:
964
965 1. Turn on the Resv_Refresh_Needed flag.
966
967 2. Call traffic control to delete the reservation:
968
969 TC_DelFlowspec( OI, Rhandle )
970
971 3. Delete the TCSB and return.
972
973 o Otherwise, if TCSB is not new but the TC_Flowspec, Path_Te,
974 and/or police flags just computed differ from corresponding
975 values in the TCSB, then:
976
977 1. If the TC_Flowspec and/or Path_Te values differ, turn
978 the Resv_Refresh_Needed flag on.
979
980 2. Call traffic control to modify the reservation:
981
982 TC_ModFlowspec( OI, Rhandle, TC_Flowspec,
983 Path_Te, police_flags )
984 -&gt; Fwd_Flowspec
985
986 3. If this call fails, build and send a RERR message
987 specifying "Admission control failed" and with the
988 InPlace bit on. Delete any RESV_CONFIRM object from
989 the active RSB and return.
990
991 4. Otherwise (the call succeeds), update the TCSB with
992 the new values and save Fwd_Flowspec in the TCSB.
993
994 o If the TCSB is not new but the TC_Filter_Spec* just
995 computed differs from the FILTER_SPEC* in the TCSB, then:
996
997 1. Make an appropriate set of TC_DelFilter and
998 TC_AddFilter calls to transform the Filter_spec_list
999 in the TCSB into the new TC_Filter_Spec*.
1000
1001
1002
1003
1004 <span class="grey">Braden &amp; Zhang Informational [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc2209">RFC 2209</a> RSVP-Message Processing September 1997</span>
1007
1008
1009 2. Turn on the Resv_Refresh_Needed flag.
1010
1011 o If the active RSB contains a RESV_CONFIRM object, then:
1012
1013 1. If the Is_Biggest flag is on, move the RESV_CONFIRM
1014 object into the TCSB and turn on the
1015 Resv_Refresh_Needed flag. (This will later cause the
1016 RESV REFRESH sequence to be invoked, which will either
1017 forward or return the RESV_CONFIRM object, deleting it
1018 from the TCSB in either case).
1019
1020 2. Otherwise, create and send a RACK message to the
1021 address in the RESV_CONFIRM object. Include the
1022 RESV_CONFIRM object in the RACK message. The RACK
1023 message should also include an ERROR_SPEC object whose
1024 Error_Node parameter is IP address of OI from the TCSB
1025 and that specifies "No Error".
1026
1027 o If the Resv_Refresh_Needed flag is on and the RSB is not
1028 from the API, make a RESV_EVENT upcall to any matching
1029 application:
1030
1031 Call: &lt;Upcall_Proc&gt;( session-id, RESV_EVENT,
1032 style, Flowspec, Filter_spec_list [ ,
1033 POLICY_DATA] )
1034
1035 where Flowspec and Filter_spec_list come from the TCSB and
1036 the style comes from the active RSB.
1037
1038 o Return to the event sequence that invoked this one.
1039
1040 PATH REFRESH
1041
1042 This sequence sends a path refresh for a particular sender,
1043 i.e., a PSB. This sequence may be entered by either the
1044 expiration of a refresh timer or directly as the result of the
1045 Path_Refresh_Needed flag being turned on during the processing
1046 of a received PATH message.
1047
1048 o Insert TIME_VALUES object into the PATH message being
1049 built. Compute the IP TTL for the PATH message as one less
1050 than the TTL value received in the message. However, if
1051 the result is zero, return without sending the PATH
1052 message.
1053
1054 o Create a sender descriptor containing the SENDER_TEMPLATE,
1055 SENDER_TSPEC, and POLICY_DATA objects, if present in the
1056 PSB, and pack it into the PATH message being built.
1057
1058
1059
1060 <span class="grey">Braden &amp; Zhang Informational [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc2209">RFC 2209</a> RSVP-Message Processing September 1997</span>
1063
1064
1065 o Send a copy of the PATH message to each interface OI in
1066 OutInterface_list. Before sending each copy:
1067
1068 1. If the PSB has the E_Police flag on and if interface
1069 OI is not capable of policing, turn the E_Police flag
1070 on in the PATH message being built.
1071
1072 2. Pass the ADSPEC object and Non_RSVP flag present in
1073 the PSB to the traffic control call TC_Advertise.
1074 Insert the modified ADSPEC object that is returned
1075 into the PATH message being built.
1076
1077 3. Insert into its PHOP object the interface address and
1078 the LIH for the interface.
1079
1080 RESV REFRESH
1081
1082 This sequence sends a reservation refresh towards a particular
1083 previous hop with IP address PH. This sequence may be entered
1084 by the expiration of a refresh timer, or invoked from the PATH
1085 MESSAGE ARRIVES, RESV MESSAGE ARRIVES, RTEAR MESSAGE ARRIVES, or
1086 RERR MESSAGE ARRIVES sequence.
1087
1088 In general, this sequence considers each of the PSB's with PHOP
1089 address PH. For a given PSB, it scans the TCSBs for matching
1090 reservations and merges the styles, FLOWSPECs and
1091 Filter_spec_list's appropriately. It then builds a RESV message
1092 and sends it to PH. The details depend upon the attributes of
1093 the style(s) included in the reservations.
1094
1095 Initially the Need_Scope flag is off and the new_SCOPE object is
1096 empty.
1097
1098 o Create an output message containing INTEGRITY (if
1099 configured), SESSION, RSVP_HOP, and TIME_VALUES objects.
1100
1101 o Determine the style for these reservations from the first
1102 RSB for the session, and move the STYLE object into the
1103 proto-message. (Note that the present set of styles are
1104 never themselves merged; if future styles can be merged,
1105 these rules will become more complex).
1106
1107 o If style is wildcard and if there are PSB's from more than
1108 one PHOP and if the multicast routing protocol does not use
1109 shared trees, set the Need_Scope flag on.
1110
1111
1112
1113
1114
1115
1116 <span class="grey">Braden &amp; Zhang Informational [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc2209">RFC 2209</a> RSVP-Message Processing September 1997</span>
1119
1120
1121 o Select each sender PSB whose PHOP has address PH. Set the
1122 local flag B_Merge off and execute the following steps.
1123
1124 1. Select all TCSB's whose Filter_spec_list's match the
1125 SENDER_TEMPLATE object in the PSB and whose OI appears
1126 in the OutInterface_list of the PSB.
1127
1128 2. If the PSB is from the API, then:
1129
1130 - If TCSB contains a CONFIRM object, then create
1131 and send a RACK message containing the object and
1132 delete the CONFIRM object from the TCSB.
1133
1134 - Continue with next PSB.
1135
1136 3. If B_Merge flag is off then ignore a blockaded TCSB,
1137 as follows.
1138
1139 - Select BSB's that match this TCSB. If a selected
1140 BSB is expired, delete it. If any of the
1141 unexpired BSB's has a Qb that is not strictly
1142 larger than TC_Flowspec, then continue processing
1143 with the next TCSB.
1144
1145 However, if steps 1 and 2 result in finding that all
1146 TCSB's matching this PSB are blockaded, then:
1147
1148 - If this RESV REFRESH sequence was invoked from
1149 RESV ERROR RECEIVED, then return to the latter.
1150
1151 - Otherwise, turn on the B_Merge flag and restart
1152 at step 1, immediately above.
1153
1154 4. Merge the flowspecs from this set of TCSB's, as
1155 follows:
1156
1157 - If B_Merge flag is off, compute the LUB over the
1158 flowspec objects. From each TCSB, use the
1159 Fwd_Flowspec object if present, else use the
1160 normal Flowspec object.
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172 <span class="grey">Braden &amp; Zhang Informational [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc2209">RFC 2209</a> RSVP-Message Processing September 1997</span>
1175
1176
1177 While computing the LUB, check for a RESV_CONFIRM
1178 object in each TCSB. If a RESV_CONFIRM object is
1179 found:
1180
1181 - If the flowspec (Fwd_Flowspec or Flowspec)
1182 in that TCSB is larger than all other (non-
1183 blockaded) flowspecs being compared, then
1184 save this RESV_CONFIRM object for forwarding
1185 and delete from the TCSB.
1186
1187 - Otherwise (the corresponding flowspec is not
1188 the largest), create and send a RACK message
1189 to the address in the RESV_CONFIRM object.
1190 Include the RESV_CONFIRM object in the RACK
1191 message. The RACK message should also
1192 include an ERROR_SPEC object whose
1193 Error_Node parameter is IP address of OI
1194 from the TCSB and specifying "No Error".
1195
1196 - Delete the RESV_CONFIRM object from the
1197 TCSB.
1198
1199 - Otherwise (B_Merge flag is on), compute the GLB
1200 over the Flowspec objects of this set of TCSB's.
1201
1202 While computing the GLB, delete any RESV_CONFIRM
1203 object object in any of these TCSB's.
1204
1205 5. (All matching TCSB's have been processed). The next
1206 step depends upon the style attributes.
1207
1208 Distinct reservation (FF) style
1209
1210 Use the Sender_Template as the merged
1211 FILTER_SPEC. Pack the merged (FLOWSPEC,
1212 FILTER_SPEC, F_POLICY_DATA) triplet into the
1213 message as a flow descriptor.
1214
1215 Shared wildcard reservation (WF) style
1216
1217 There is no merged FILTER_SPEC. Merge (compute
1218 the LUB of) the merged FLOWSPECS from the TCSB's,
1219 across all PSB's for PH.
1220
1221
1222
1223
1224
1225
1226
1227
1228 <span class="grey">Braden &amp; Zhang Informational [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc2209">RFC 2209</a> RSVP-Message Processing September 1997</span>
1231
1232
1233 Shared distinct reservation (SE) style
1234
1235 Using the Sender_Template as the merged
1236 FILTER_SPEC, form the union of the FILTER_SPECS
1237 obtained from the TCSB's. Merge (compute the LUB
1238 of) the merged FLOWSPECS from the TCSB's, across
1239 all PSB's for PH.
1240
1241 6. If the Need_Scope flag is on and the sender specified
1242 by the PSB is not the local API:
1243
1244 - Find each RSB that matches this PSB, i.e., whose
1245 Filter_spec_list matches Sender_Template in the
1246 PSB and whose OI is included in
1247 OutInterface_list.
1248
1249 - If the RSB either has no SCOPE list or its SCOPE
1250 list includes the sender IP address from the PSB,
1251 insert the sender IP address into new_SCOPE.
1252
1253 o (All PSB's for PH have been processed). Finish the RESV
1254 message.
1255
1256 1. If Need_Scope flag is on but new_SCOPE is empty, no
1257 RESV message should be sent; return. Otherwise, if
1258 Need_Scope is on, move new_SCOPE into the message.
1259
1260 2. If a shared reservation style is being built, move the
1261 final merged FLOWSPEC object and filter spec list into
1262 the message.
1263
1264 3. If a RESV_CONFIRM object was saved earlier, move it
1265 into the new RESV message.
1266
1267 4. Set the RSVP_HOP object in the message to contain the
1268 IncInterface address through which it will be sent and
1269 the LIH from (one of) the PSB's.
1270
1271 o Send the message to the address PH.
1272
1273 ROUTE CHANGE NOTIFICATION
1274
1275 This sequence is triggered when routing sends a route change
1276 notification to RSVP.
1277
1278 o Each PSB is located whose SESSION matches the destination
1279 address and whose SENDER_TEMPLATE matches the source
1280 address (for multicast).
1281
1282
1283
1284 <span class="grey">Braden &amp; Zhang Informational [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc2209">RFC 2209</a> RSVP-Message Processing September 1997</span>
1287
1288
1289 1. If the OutInterface_list from the notification differs
1290 from that in the PSB, execute the PATH LOCAL REPAIR
1291 sequence.
1292
1293 2. If the IncInterface from the notification differs from
1294 that in the PSB, update the PSB.
1295
1296 PATH LOCAL REPAIR
1297
1298 The sequence is entered to effect local repair after a route
1299 change for a given PSB.
1300
1301 o Wait for a delay time of W seconds.
1302
1303 o Execute the PATH REFRESH event sequence (above) for the
1304 PSB.
1305
1306 References
1307
1308 [<a id="ref-Baker96">Baker96</a>] Baker, F., <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&amp;q=inurl:draft-+%22RSVP+Cryptographic+Authentication%22'>"RSVP Cryptographic Authentication"</a>, Work in
1309 Progress.
1310
1311
1312 [<a id="ref-RFC 2205">RFC 2205</a>] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and
1313 S. Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1
1314 FunctionalSpecification", <a href="./rfc2205">RFC 2205</a>, September 1997.
1315
1316 [<a id="ref-RFC 2207">RFC 2207</a>] Berger, L. and T. O'Malley, "RSVP Extensions for IPSEC
1317 IPv4 Data Flows", <a href="./rfc2207">RFC 2207</a>, September 1997.
1318
1319 [<a id="ref-RSVP93">RSVP93</a>] Zhang, L., Deering, S., Estrin, D., Shenker, S., and D.
1320 Zappala, "RSVP: A New Resource ReSerVation Protocol", IEEE
1321 Network, September 1993.
1322
1323 Security Considerations
1324
1325 Processing the RSVP INTEGRITY object [<a href="#ref-Baker96" title="&quot;RSVP Cryptographic Authentication&quot;">Baker96</a>] is only mentioned in
1326 this memo, because the processing rules are described here only in
1327 general terms. The RSVP support for IPSEC [<a href="./rfc2207">RFC 2207</a>] will imply
1328 modifications that have not yet been incorporated into these
1329 processing rules.
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340 <span class="grey">Braden &amp; Zhang Informational [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc2209">RFC 2209</a> RSVP-Message Processing September 1997</span>
1343
1344
1345 Authors' Addresses
1346
1347 Bob Braden
1348 USC Information Sciences Institute
1349 4676 Admiralty Way
1350 Marina del Rey, CA 90292
1351
1352 Phone: (310) 822-1511
1353 EMail: [email protected]
1354
1355
1356 Lixia Zhang
1357 UCLA Computer Science Department
1358 4531G Boelter Hall
1359 Los Angeles, CA 90095-1596 USA
1360
1361 Phone: 310-825-2695
1362 EMail: [email protected]
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396 Braden &amp; Zhang Informational [Page 25]
1397 </pre>