?  search:
summary | log | graphiclog1 | graphiclog2 | commit | commitdiff | tree | refs | edit | fork
blame | history | raw | HEAD
Assertting on session is not valid. A route addition that is
[mpls-ldp-portable.git] / rsvpte / rsvpte_struct.h
blob71d19d13c12e0f3c7767e5f0eda05c9a28aa4139
1 /*
2 * Copyright (C) James R. Leu 2003
3 * jleu@mindspring.com
4 *
5 * This software is covered under the LGPL, for more
6 * info check out http://www.gnu.org/copyleft/lgpl.html
7 */
8
9 #ifndef RSVPTE_STRUCT_H
10 #define RSVPTE_STRUCT_H
11
12 #include "mpls_struct.h"
13 #include "mpls_list.h"
14 #include "mpls_refcnt.h"
15 #include "mpls_bitfield.h"
16
17 MPLS_LIST_ROOT(rsvpte_if_list, rsvpte_if);
18
19 typedef struct rsvpte_global {
20 struct rsvpte_if_list iff;
21
22 struct mpls_inet_addr lsr_identifier;
23 mpls_admin_state_enum admin_state;
24
25 mpls_lock_handle global_lock;
26 mpls_instance_handle user_data;
27
28 mpls_tree_handle addr_tree;
29
30 mpls_socket_handle ra_socket;
31
32 mpls_timer_mgr_handle timer_handle;
33 mpls_socket_mgr_handle socket_handle;
34 mpls_fib_handle fib_handle;
35 mpls_ifmgr_handle ifmgr_handle;
36
37 #if MPLS_USE_LSR
38 mpls_cfg_handle lsr_handle;
39 #else
40 mpls_mpls_handle mpls_handle;
41 #endif
42 } rsvpte_global;
43
44 typedef struct rsvpte_if {
45 MPLS_REFCNT_FIELD;
46 MPLS_LIST_ELEM(rsvpte_if) _global;
47 int label_space;
48 uint32_t index;
49 mpls_if_handle handle;
50
51 mpls_oper_state_enum oper_state;
52 mpls_admin_state_enum admin_state;
53 } rsvpte_if;
54
55 #define RSSPV_RSVP_ENC_OBJECTERROR -1
56 #define RSSPV_RSVP_DEC_OBJECTERROR -2
57
58 #define RSVP_IPV4_ADDR_LEN 4
59 #define RSVP_IPV6_ADDR_LEN 16
60
61 /**********************************************************************
62 RSVP Objects
63
64 Every object consists of one or more 32-bit words with a one-
65 word header, with the following format:
66
67 0 1 2 3
68 +-------------+-------------+-------------+-------------+
69 | Length (bytes) | Class-Num | C-Type |
70 +-------------+-------------+-------------+-------------+
71 | |
72 // (Object contents) //
73 | |
74 +-------------+-------------+-------------+-------------+
75
76 An object header has the following fields:
77
78 Length
79
80 A 16-bit field containing the total object length in
81 bytes. Must always be a multiple of 4, and at least 4.
82
83 Class-Num
84
85 Identifies the object class; values of this field are
86 defined in Appendix A. Each object class has a name,
87 which is always capitalized in this document. An RSVP
88 implementation must recognize the following classes:
89
90 NULL
91
92 A NULL object has a Class-Num of zero, and its C-Type
93 is ignored. Its length must be at least 4, but can
94 be any multiple of 4. A NULL object may appear
95 anywhere in a sequence of objects, and its contents
96 will be ignored by the receiver.
97
98 SESSION
99
100 Contains the IP destination address (DestAddress),
101 the IP protocol id, and some form of generalized
102 destination port, to define a specific session for
103 the other objects that follow. Required in every
104 RSVP message.
105
106 RSVP_HOP
107
108 Carries the IP address of the RSVP-capable node that
109 sent this message and a logical outgoing interface
110 handle (LIH; see Section 3.3). This document refers
111 to a RSVP_HOP object as a PHOP ("previous hop")
112 object for downstream messages or as a NHOP (" next
113 hop") object for upstream messages.
114
115 TIME_VALUES
116
117 Contains the value for the refresh period R used by
118 the creator of the message; see Section 3.7.
119 Required in every Path and Resv message.
120
121 STYLE
122
123 Defines the reservation style plus style-specific
124 information that is not in FLOWSPEC or FILTER_SPEC
125 objects. Required in every Resv message.
126
127 FLOWSPEC
128
129 Defines a desired QoS, in a Resv message.
130
131 FILTER_SPEC
132
133 Defines a subset of session data packets that should
134 receive the desired QoS (specified by a FLOWSPEC
135 object), in a Resv message.
136
137 SENDER_TEMPLATE
138
139 Contains a sender IP address and perhaps some
140 additional demultiplexing information to identify a
141 sender. Required in a Path message.
142
143 SENDER_TSPEC
144
145 Defines the traffic characteristics of a sender's
146 data flow. Required in a Path message.
147
148 ADSPEC
149
150 Carries OPWA data, in a Path message.
151
152 ERROR_SPEC
153
154 Specifies an error in a PathErr, ResvErr, or a
155 confirmation in a ResvConf message.
156
157 POLICY_DATA
158
159 Carries information that will allow a local policy
160 module to decide whether an associated reservation is
161 administratively permitted. May appear in Path,
162 Resv, PathErr, or ResvErr message.
163
164 The use of POLICY_DATA objects is not fully specified
165 at this time; a future document will fill this gap.
166
167 INTEGRITY
168
169 Carries cryptographic data to authenticate the
170 originating node and to verify the contents of this
171 RSVP message. The use of the INTEGRITY object is
172 described in [Baker96].
173
174 SCOPE
175
176 Carries an explicit list of sender hosts towards
177 which the information in the message is to be
178 forwarded. May appear in a Resv, ResvErr, or
179 ResvTear message. See Section 3.4.
180
181 RESV_CONFIRM
182
183 Carries the IP address of a receiver that requested a
184 confirmation. May appear in a Resv or ResvConf
185 message.
186
187 **********************************************************************/
188
189 #define RSVP_OBJECT_HDRSIZE 4
190
191 typedef struct rsvpObjectHeader_s {
192 u_short length;
193 u_char class;
194 u_char cType;
195 } rsvpObjectHeader_t;
196
197
198 #define RSVP_SESSION_CLASS 1
199 #define RSVP_SESSION_CTYPE_IPV4 1
200 #define RSVP_SESSION_CTYPE_IPV6 2
201 #define RSVP_SESSION_CTYPE_TUNNEL4 7
202 #define RSVP_SESSION_CTYPE_TUNNEL6 8
203
204 /**********************************************************************
205 RSVP SESSION Object
206
207 o IPv4/UDP SESSION object: Class = 1, C-Type = 1
208
209 0 1 2 3
210 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
211 +---------------+---------------+---------------+---------------+
212 | IPv4 DestAddress (4 bytes) |
213 +---------------+---------------+---------------+---------------+
214 | Protocol Id | Flags | DstPort |
215 +---------------+---------------+---------------+---------------+
216
217 o IPv6/UDP SESSION object: Class = 1, C-Type = 2
218
219 0 1 2 3
220 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
221 +---------------+---------------+---------------+---------------+
222 | |
223 + +
224 | |
225 + IPv6 DestAddress (16 bytes) +
226 | |
227 + +
228 | |
229 +---------------+---------------+---------------+---------------+
230 | Protocol Id | Flags | DstPort |
231 +---------------+---------------+---------------+---------------+
232
233 DestAddress
234
235 The IP unicast or multicast destination address of the
236 session. This field must be non-zero.
237
238 Protocol Id
239
240 The IP Protocol Identifier for the data flow. This field
241 must be non-zero.
242 Flags
243
244 0x01 = E_Police flag
245
246 The E_Police flag is used in Path messages to determine
247 the effective "edge" of the network, to control traffic
248 policing. If the sender host is not itself capable of
249 traffic policing, it will set this bit on in Path
250 messages it sends. The first node whose RSVP is capable
251 of traffic policing will do so (if appropriate to the
252 service) and turn the flag off.
253
254 DstPort
255
256 The UDP/TCP destination port for the session. Zero may be
257 used to indicate `none'.
258
259 Other SESSION C-Types could be defined in the future to
260 support other demultiplexing conventions in the transport-
261 layer or application layer.
262
263 LSP_TUNNEL_IPv4 Session Object
264
265 Class = SESSION, LSP_TUNNEL_IPv4 C-Type = 7
266
267 0 1 2 3
268 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
269 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
270 | IPv4 tunnel end point address |
271 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
272 | MUST be zero | Tunnel ID |
273 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
274 | Extended Tunnel ID |
275 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
276
277 IPv4 tunnel end point address
278
279 IPv4 address of the egress node for the tunnel.
280
281 Tunnel ID
282
283 A 16-bit identifier used in the SESSION that remains constant
284 over the life of the tunnel.
285
286 Extended Tunnel ID
287
288 A 32-bit identifier used in the SESSION that remains constant
289 over the life of the tunnel. Normally set to all zeros.
290 Ingress nodes that wish to narrow the scope of a SESSION to the
291 ingress-egress pair may place their IPv4 address here as a
292 globally unique identifier.
293
294
295 LSP_TUNNEL_IPv6 Session Object
296
297 Class = SESSION, LSP_TUNNEL_IPv6 C_Type = 8
298
299 0 1 2 3
300 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
301 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
302 | |
303 + +
304 | IPv6 tunnel end point address |
305 + +
306 | (16 bytes) |
307 + +
308 | |
309 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
310 | MUST be zero | Tunnel ID |
311 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
312 | |
313 + +
314 | Extended Tunnel ID |
315 + +
316 | (16 bytes) |
317 + +
318 | |
319 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
320
321 IPv6 tunnel end point address
322
323 IPv6 address of the egress node for the tunnel.
324
325 Tunnel ID
326
327 A 16-bit identifier used in the SESSION that remains constant
328 over the life of the tunnel.
329
330 Extended Tunnel ID
331
332 A 16-byte identifier used in the SESSION that remains constant
333 over the life of the tunnel. Normally set to all zeros.
334 Ingress nodes that wish to narrow the scope of a SESSION to the
335 ingress-egress pair may place their IPv6 address here as a
336 globally unique identifier.
337
338 **********************************************************************/
339
340 #define RSVP_SESSION4_SIZE 8
341
342 typedef struct rsvpSession4_s {
343 u_int destAddr;
344 u_char protocolId;
345 u_char flags;
346 u_short destPort;
347 } rsvpSession4_t;
348
349 #define RSVP_SESSION6_SIZE 20
350
351 typedef struct rsvpSession6_s {
352 u_char destAddr[16];
353 u_char protocolId;
354 u_char flags;
355 u_short destPort;
356 } rsvpSession6_t;
357
358 #define RSVP_SESSION_TUNNEL4_SIZE 12
359
360 typedef struct rsvpSessionTunnel4_s {
361 u_int endPointAddress;
362 u_short reserved;
363 u_short tunnelId;
364 u_int extentedTunnelId;
365 } rsvpSessionTunnel4_t;
366
367 #define RSVP_SESSION_TUNNEL6_SIZE 36
368
369 typedef struct rsvpSessionTunnel6_s {
370 u_char endPointAddress[16];
371 u_short reserved;
372 u_short tunnelId;
373 u_char extentedTunnelId[16];
374 } rsvpSessionTunnel6_t;
375
376 typedef struct rsvpSessionObject_s {
377 struct rsvpObjectHeader_s hdr;
378 union {
379 struct rsvpSession4_s ipv4;
380 struct rsvpSession6_s ipv6;
381 struct rsvpSessionTunnel4_s tunnel4;
382 struct rsvpSessionTunnel6_s tunnel6;
383 } u;
384 } rsvpSessionObject_t;
385
386 #define RSVP_HOP_CLASS 3
387 #define RSVP_HOP_CTYPE_IPV4 1
388 #define RSVP_HOP_CTYPE_IPV6 2
389
390 /**********************************************************************
391 RSVP HOP Object
392
393 o IPv4 RSVP_HOP object: Class = 3, C-Type = 1
394
395 0 1 2 3
396 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
397
398 +---------------+---------------+---------------+---------------+
399 | IPv4 Next/Previous Hop Address |
400 +---------------+---------------+---------------+---------------+
401 | Logical Interface Handle |
402 +---------------+---------------+---------------+---------------+
403
404 o IPv6 RSVP_HOP object: Class = 3, C-Type = 2
405
406 0 1 2 3
407 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
408
409 +---------------+---------------+---------------+---------------+
410 | |
411 + +
412 | |
413 + IPv6 Next/Previous Hop Address +
414 | |
415 + +
416 | |
417 +---------------+---------------+---------------+---------------+
418 | Logical Interface Handle |
419 +---------------+---------------+---------------+---------------+
420
421 This object carries the IP address of the interface through which
422 the last RSVP-knowledgeable hop forwarded this message. The
423 Logical Interface Handle (LIH) is used to distinguish logical
424 outgoing interfaces, as discussed in Sections 3.3 and 3.9. A node
425 receiving an LIH in a Path message saves its value and returns it
426 in the HOP objects of subsequent Resv messages sent to the node
427 that originated the LIH. The LIH should be identically zero if
428 there is no logical interface handle.
429
430 **********************************************************************/
431
432 #define RSVP_HOP4_SIZE 8
433
434 typedef struct rsvpHop4_s {
435 u_int hopAddr;
436 u_int logicalIfHandle;
437 } rsvpHop4_t;
438
439 #define RSVP_HOP6_SIZE 20
440
441 typedef struct rsvpHop6_s {
442 u_char hopAddr[16];
443 u_int logicalIfHandle;
444 } rsvpHop6_t;
445
446 typedef struct rsvpHopObject_s {
447 struct rsvpObjectHeader_s hdr;
448 union {
449 struct rsvpHop4_s ipv4;
450 struct rsvpHop6_s ipv6;
451 } u;
452 } rsvpHopObject_t;
453
454 #define RSVP_TIME_CLASS 5
455 #define RSVP_TIME_CTYPE 1
456
457 /**********************************************************************
458 RSVP TIME Object
459
460 o TIME_VALUES Object: Class = 5, C-Type = 1
461
462 0 1 2 3
463 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
464 +---------------+---------------+---------------+---------------+
465 | Refresh Period R |
466 +---------------+---------------+---------------+---------------+
467
468 Refresh Period
469
470 The refresh timeout period R used to generate this message;
471 in milliseconds.
472
473 **********************************************************************/
474
475 #define RSVP_TIME_SIZE 4
476
477 typedef struct rsvpTimeObject_s {
478 struct rsvpObjectHeader_s hdr;
479 u_int refresh;
480 } rsvpTimeObject_t;
481
482 #define RSVP_ERROR_SPEC_CLASS 6
483 #define RSVP_ERROR_SPEC_CTYPE_IPV4 1
484 #define RSVP_ERROR_SPEC_CTYPE_IPV6 2
485
486 /**********************************************************************
487 RSVP ERROR_SPEC Object
488
489 o IPv4 ERROR_SPEC object: Class = 6, C-Type = 1
490
491 0 1 2 3
492 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
493 +---------------+---------------+---------------+---------------+
494 | IPv4 Error Node Address (4 bytes) |
495 +---------------+---------------+---------------+---------------+
496 | Flags | Error Code | Error Value |
497 +---------------+---------------+---------------+---------------+
498
499
500 o IPv6 ERROR_SPEC object: Class = 6, C-Type = 2
501
502 0 1 2 3
503 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
504 +---------------+---------------+---------------+---------------+
505 | |
506 + +
507 | |
508 + IPv6 Error Node Address (16 bytes) +
509 | |
510 + +
511 | |
512 +---------------+---------------+---------------+---------------+
513 | Flags | Error Code | Error Value |
514 +---------------+---------------+---------------+---------------+
515
516 Error Node Address
517
518 The IP address of the node in which the error was detected.
519
520 Flags
521
522 0x01 = InPlace
523
524 This flag is used only for an ERROR_SPEC object in a
525 ResvErr message. If it on, this flag indicates that
526 there was, and still is, a reservation in place at the
527 failure point.
528
529 0x02 = NotGuilty
530
531 This flag is used only for an ERROR_SPEC object in a
532 ResvErr message, and it is only set in the interface to
533 the receiver application. If it on, this flag indicates
534 that the FLOWSPEC that failed was strictly greater than
535 the FLOWSPEC requested by this receiver.
536
537 Error Code
538
539 A one-octet error description.
540
541 Error Value
542
543 A two-octet field containing additional information about the
544 error. Its contents depend upon the Error Type.
545
546 The values for Error Code and Error Value are defined in Appendix
547 B.
548
549 ***********************************************************************/
550
551 typedef struct rsvpErrorSpec4_s {
552 u_int hopAddr;
553 u_char flag;
554 u_char code;
555 u_short value;
556 } rsvpErrorSpec4_t;
557
558 typedef struct rsvpErrorSpec6_s {
559 u_char hopAddr[16];
560 u_char flag;
561 u_char code;
562 u_short value;
563 } rsvpErrorSpec6_t;
564
565 typedef struct rsvpErrorSpecObject_s {
566 struct rsvpObjectHeader_s hdr;
567 union {
568 struct rsvpErrorSpec4_s ipv4;
569 struct rsvpErrorSpec6_s ipv6;
570 } u;
571 } rsvpErrorSpecObject_t;
572
573 #define RSVP_SCOPE_LIST_CLASS 7
574 #define RSVP_SCOPE_LIST_CTYPE_IPV4 1
575 #define RSVP_SCOPE_LIST_CTYPE_IPV6 2
576
577 #define RSVP_MAX_SCOPE_LIST 16
578
579 /***********************************************************************
580
581 RSVP SCOPE LIST Object
582
583 This object contains a list of IP addresses, used for routing
584 messages with wildcard scope without loops. The addresses must be
585 listed in ascending numerical order.
586
587 o IPv4 SCOPE List object: Class = 7, C-Type = 1
588
589 0 1 2 3
590 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
591 +-------------+-------------+-------------+-------------+
592 | IPv4 Src Address (4 bytes) |
593 +-------------+-------------+-------------+-------------+
594 // //
595 +-------------+-------------+-------------+-------------+
596 | IPv4 Src Address (4 bytes) |
597 +-------------+-------------+-------------+-------------+
598
599
600 o IPv6 SCOPE list object: Class = 7, C-Type = 2
601
602 0 1 2 3
603 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
604 +-------------+-------------+-------------+-------------+
605 | |
606 + +
607 | |
608 + IPv6 Src Address (16 bytes) +
609 | |
610 + +
611 | |
612 +-------------+-------------+-------------+-------------+
613 // //
614 +-------------+-------------+-------------+-------------+
615 | |
616 + +
617 | |
618 + IPv6 Src Address (16 bytes) +
619 | |
620 + +
621 | |
622 +-------------+-------------+-------------+-------------+
623
624 ***********************************************************************/
625
626 typedef struct rsvpScopeList4_s {
627 u_int addr[RSVP_MAX_SCOPE_LIST];
628 } rsvpScopeList4_t;
629
630 typedef struct rsvpScopeList6_s {
631 u_char addr[RSVP_MAX_SCOPE_LIST][16];
632 } rsvpScopeList6_t;
633
634 typedef struct rsvpScopListObject_s {
635 struct rsvpObjectHeader_s hdr;
636 union {
637 struct rsvpScopeList4_s ipv4;
638 struct rsvpScopeList6_s ipv6;
639 } u;
640 } rsvpScopListObject_t;
641 #define RSVP_STYLE_CLASS 8
642 #define RSVP_STYLE_CTYPE 1
643
644 /***********************************************************************
645
646 STYLE class = 8.
647
648 o STYLE object: Class = 8, C-Type = 1
649
650 0 1 2 3
651 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
652 +-----------------+---------------+---------------+-------------+
653 | Flags | Option Vector |
654 +-----------------+---------------+---------------+-------------+
655
656
657
658 Flags: 8 bits
659
660 (None assigned yet)
661
662 Option Vector: 24 bits
663
664 A set of bit fields giving values for the reservation
665 options. If new options are added in the future,
666 corresponding fields in the option vector will be assigned
667 from the least-significant end. If a node does not recognize
668 a style ID, it may interpret as much of the option vector as
669 it can, ignoring new fields that may have been defined.
670
671 The option vector bits are assigned (from the left) as
672 follows:
673
674 19 bits: Reserved
675
676 2 bits: Sharing control
677
678 00b: Reserved
679
680 01b: Distinct reservations
681
682 10b: Shared reservations
683
684 11b: Reserved
685
686 3 bits: Sender selection control
687
688 000b: Reserved
689
690 001b: Wildcard
691
692 010b: Explicit
693
694 011b - 111b: Reserved
695
696 The low order bits of the option vector are determined by the
697 style, as follows:
698
699 WF 10001b
700 FF 01010b
701 SE 10010b
702
703 ***********************************************************************/
704
705 typedef struct rsvpStyleFlag_s {
706 BITFIELDS_ASCENDING_4(u_int flag:8, /* flags */
707 u_int reserved:19, /* reserved */
708 u_int shareControl:2, /* sharing control */
709 u_int senderSelectionControl:3); /* sender selection control */
710 } rsvpStyleFlag_t;
711
712 typedef struct rsvpStyleObject_s {
713 struct rsvpObjectHeader_s hdr;
714
715 union {
716 struct rsvpStyleFlag_s flag;
717 u_int mark;
718 } flag;
719 } rsvpStyleObject_t;
720
721 #define RSVP_FILTER_SPEC_CLASS 10
722 #define RSVP_FILTER_SPEC_CTYPE_IPV4 1
723 #define RSVP_FILTER_SPEC_CTYPE_IPV6 2
724 #define RSVP_FILTER_SPEC_CTYPE_FLOW 3
725 #define RSVP_FILTER_SPEC4_SIZE 8
726 #define RSVP_FILTER_SPEC6_SIZE 20
727 #define RSVP_FILTER_SPEC_FLOW_SIZE 20
728
729 /***********************************************************************
730
731 FILTER_SPEC class = 10.
732
733 o IPv4 FILTER_SPEC object: Class = 10, C-Type = 1
734
735 0 1 2 3
736 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
737 +---------------+---------------+---------------+---------------+
738 | IPv4 SrcAddress (4 bytes) |
739 +---------------+---------------+---------------+---------------+
740 | ////// | ////// | SrcPort |
741 +---------------+---------------+---------------+---------------+
742
743
744 o IPv6 FILTER_SPEC object: Class = 10, C-Type = 2
745
746 0 1 2 3
747 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
748 +---------------+---------------+---------------+---------------+
749 | |
750 + +
751 | |
752 + IPv6 SrcAddress (16 bytes) +
753 | |
754 + +
755 | |
756 +---------------+---------------+---------------+---------------+
757 | ////// | ////// | SrcPort |
758 +---------------+---------------+---------------+---------------+
759
760
761 o IPv6 Flow-label FILTER_SPEC object: Class = 10, C-Type = 3
762
763 0 1 2 3
764 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
765 +---------------+---------------+---------------+---------------+
766 | |
767 + +
768 | |
769 + IPv6 SrcAddress (16 bytes) +
770 | |
771 + +
772 | |
773 +---------------+---------------+---------------+---------------+
774 | /////// | Flow Label (24 bits) |
775 +---------------+---------------+---------------+---------------+
776
777 SrcAddress
778
779 The IP source address for a sender host. Must be non-zero.
780
781 SrcPort
782
783 The UDP/TCP source port for a sender, or zero to indicate
784 `none'.
785
786 Flow Label
787
788 A 24-bit Flow Label, defined in IPv6. This value may be used
789 by the packet classifier to efficiently identify the packets
790 belonging to a particular (sender->destination) data flow.
791
792 ***********************************************************************/
793
794 typedef struct rsvpFilterSpec4_s {
795 u_int sourceAddr;
796 u_short reserved;
797 u_short sourcePort;
798 } rsvpFilterSpec4_t;
799
800 typedef struct rsvpFilterSpec6_s {
801 u_char sourceAddr[RSVP_IPV6_ADDR_LEN];
802 u_short reserved;
803 u_short sourcePort;
804 } rsvpFilterSpec6_t;
805
806 typedef struct rsvpFilterSpecFlags_s {
807 BITFIELDS_ASCENDING_2(u_int reserved:8,
808 u_int flowLabel:24);
809 } rsvpFilterSpecFlags_t;
810
811 typedef struct rsvpFilterSpecFlow6_s {
812 u_char sourceAddr[RSVP_IPV6_ADDR_LEN];
813 union {
814 u_int mark;
815 struct rsvpFilterSpecFlags_s flowLabel;
816 } flag;
817 } rsvpFilterSpecFlow6_t;
818
819 typedef struct rsvpFilterSpecObject_s {
820 struct rsvpObjectHeader_s hdr;
821 union {
822 struct rsvpFilterSpec4_s ipv4;
823 struct rsvpFilterSpec6_s ipv6;
824 struct rsvpFilterSpecFlow6_s flow;
825 } u;
826 } rsvpFilterSpecObject_t;
827
828 #define RSVP_SENDER_TEMPLATE_CLASS 11
829 #define RSVP_SENDER_TEMPLATE_CTYPE_IPV4 1
830 #define RSVP_SENDER_TEMPLATE_CTYPE_IPV6 2
831 #define RSVP_SENDER_TEMPLATE_CTYPE_FLOW 3
832 #define RSVP_SENDER_TEMPLATE_CTYPE_TUNNEL4 7
833 #define RSVP_SENDER_TEMPLATE_CTYPE_TUNNEL6 8
834 #define RSVP_SENDER_TEMPLATE_TUNNEL4_SIZE 8
835 #define RSVP_SENDER_TEMPLATE_TUNNEL6_SIZE 20
836
837 /**********************************************************************
838 SENDER_TEMPLATE Class
839
840 SENDER_TEMPLATE class = 11.
841
842 o IPv4 SENDER_TEMPLATE object: Class = 11, C-Type = 1
843
844 Definition same as IPv4/UDP FILTER_SPEC object.
845
846 o IPv6 SENDER_TEMPLATE object: Class = 11, C-Type = 2
847
848 Definition same as IPv6/UDP FILTER_SPEC object.
849
850 o IPv6 Flow-label SENDER_TEMPLATE object: Class = 11, C-Type = 3
851
852
853 LSP_TUNNEL_IPv4 Sender Template Object
854
855 Class = SENDER_TEMPLATE, LSP_TUNNEL_IPv4 C-Type = 7
856
857 0 1 2 3
858 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
859 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
860 | IPv4 tunnel sender address |
861 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
862 | MUST be zero | LSP ID |
863 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
864
865 IPv4 tunnel sender address
866
867 IPv4 address for a sender node
868
869 LSP ID
870
871 A 16-bit identifier used in the SENDER_TEMPLATE and the
872 FILTER_SPEC that can be changed to allow a sender to share
873 resources with itself.
874
875 LSP_TUNNEL_IPv6 Sender Template Object
876
877 Class = SENDER_TEMPLATE, LSP_TUNNEL_IPv6 C_Type = 8
878
879 0 1 2 3
880 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
881 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
882 | |
883 + +
884 | IPv6 tunnel sender address |
885 + +
886 | (16 bytes) |
887 + +
888 | |
889 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
890 | MUST be zero | LSP ID |
891 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
892
893 IPv6 tunnel sender address
894
895 IPv6 address for a sender node
896
897 LSP ID
898
899 A 16-bit identifier used in the SENDER_TEMPLATE and the
900 FILTER_SPEC that can be changed to allow a sender to share
901 resources with itself.
902 **********************************************************************/
903
904 #define rsvpSenderTemplate4_s rsvpFilterSpec4_s
905 #define rsvpSenderTemplate4_t rsvpFilterSpec4_t
906
907 #define rsvpSenderTemplate6_s rsvpFilterSpec6_s
908 #define rsvpSenderTemplate6_t rsvpFilterSpec6_t
909
910 #define rsvpSenderTemplateFlow6_s rsvpFilterSpecFlow6_s
911 #define rsvpSenderTemplateFlow6_t rsvpFilterSpecFlow6_t
912
913 #define rsvpteEncodeSenderTemplate4 rsvpteEncodeFilterSpec4
914 #define rsvpteEncodeSenderTemplate6 rsvpteEncodeFilterSpec6
915 #define rsvpteEncodeSenderTemplateFlow rsvpteEncodeFilterSpecFlow
916
917 #define rsvpteDecodeSenderTemplate4 rsvpteDecodeFilterSpec4
918 #define rsvpteDecodeSenderTemplate6 rsvpteDecodeFilterSpec6
919 #define rsvpteDecodeSenderTemplateFlow rsvpteDecodeFilterSpecFlow
920
921 typedef struct rsvpSenderTemplateTunnel4_s {
922 u_int sender;
923 u_short reserved;
924 u_short lspId;
925 } rsvpSenderTemplateTunnel4_t;
926
927 typedef struct rsvpSenderTemplateTunnel6_s {
928 u_char sender[RSVP_IPV6_ADDR_LEN];
929 u_short reserved;
930 u_short lspId;
931 } rsvpSenderTemplateTunnel6_t;
932
933 typedef struct rsvpSenderTemplateObject_s {
934 struct rsvpObjectHeader_s hdr;
935 union {
936 struct rsvpSenderTemplate4_s ipv4;
937 struct rsvpSenderTemplate6_s ipv6;
938 struct rsvpSenderTemplateFlow6_s flow;
939 struct rsvpSenderTemplateTunnel4_s tunnel4;
940 struct rsvpSenderTemplateTunnel6_s tunnel6;
941 } u;
942 } rsvpSenderTemplateObject_t;
943
944 #define RSVP_SENDER_TSPEC_CLASS 12
945 #define RSVP_SENDER_TSPEC_CTYPE_INTSRV 2
946
947 /**********************************************************************
948 SENDER_TSPEC Class
949
950 SENDER_TSPEC class = 12.
951
952 o Intserv SENDER_TSPEC object: Class = 12, C-Type = 2
953
954 The RSVP SENDER_TSPEC object carries information about a data
955 source's generated traffic. The required RSVP SENDER_TSPEC object
956 contains a global Token_Bucket_TSpec parameter (service_number 1,
957 parameter 127, as defined in [RFC 2215]). This TSpec carries traffic
958 information usable by either the Guaranteed or Controlled-Load QoS
959 control services.
960
961 31 24 23 16 15 8 7 0
962 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
963 1 | 0 (a) | reserved | 7 (b) |
964 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
965 2 | 1 (c) |0| reserved | 6 (d) |
966 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
967 3 | 127 (e) | 0 (f) | 5 (g) |
968 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
969 4 | Token Bucket Rate [r] (32-bit IEEE floating point number) |
970 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
971 5 | Token Bucket Size [b] (32-bit IEEE floating point number) |
972 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
973 6 | Peak Data Rate [p] (32-bit IEEE floating point number) |
974 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
975 7 | Minimum Policed Unit [m] (32-bit integer) |
976 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
977 8 | Maximum Packet Size [M] (32-bit integer) |
978 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
979
980 (a) - Message format version number (0)
981 (b) - Overall length (7 words not including header)
982 (c) - Service header, service number 1 (default/global information)
983 (d) - Length of service 1 data, 6 words not including header
984 (e) - Parameter ID, parameter 127 (Token_Bucket_TSpec)
985 (f) - Parameter 127 flags (none set)
986 (g) - Parameter 127 length, 5 words not including header
987
988
989 In this TSpec, the parameters [r] and [b] are set to reflect the
990 sender's view of its generated traffic. The peak rate parameter [p]
991 may be set to the sender's peak traffic generation rate (if known and
992 controlled), the physical interface line rate (if known), or positive
993 infinity (if no better value is available). Positive infinity is
994 represented as an IEEE single-precision floating-point number with an
995 exponent of all ones (255) and a sign and mantissa of all zeros. The
996 format of IEEE floating-point numbers is further summarized in [RFC
997 1832].
998
999 The minimum policed unit parameter [m] should generally be set equal
1000 to the size of the smallest packet generated by the application. This
1001 packet size includes the application data and all protocol headers at
1002 or above the IP level (IP, TCP, UDP, RTP, etc.). The size given does
1003 not include any link-level headers, because these headers will change
1004 as the packet crosses different portions of the internetwork.
1005
1006
1007 The [m] parameter is used by nodes within the network to compute the
1008 maximum bandwidth overhead needed to carry a flow's packets over the
1009 particular link-level technology, based on the ratio of [m] to the
1010 link-level header size. This allows the correct amount of bandwidth
1011 to be allocated to the flow at each point in the net. Note that
1012 smaller values of this parameter lead to increased overhead
1013 estimates, and thus increased likelyhood of a reservation request
1014 being rejected by the node. In some cases, an application
1015 transmitting a low percentage of very small packets may therefore
1016 choose to set the value of [m] larger than the actual minimum
1017 transmitted packet size. This will increase the likelyhood of the
1018 reservation succeeding, at the expense of policing packets of size
1019 less than [m] as if they were of size [m].
1020
1021 Note that the an [m] value of zero is illegal. A value of zero would
1022 indicate that no data or IP headers are present, and would give an
1023 infinite amount of link-level overhead.
1024
1025 The maximum packet size parameter [M] should be set to the size of
1026 the largest packet the application might wish to generate, as
1027 described in Section 2.3.2. This value must, by definition, be equal
1028 to or larger than the value of [m].
1029
1030
1031 **********************************************************************/
1032 typedef struct rsvpSenderTSpecObject_s {
1033 struct rsvpObjectHeader_s hdr;
1034 } rsvpSenderTSpecObject_t;
1035
1036
1037 #define RSVP_ADSPEC_CLASS 13
1038 #define RSVP_ADSPEC_CTYPE_INTSRV 2
1039 /**********************************************************************
1040 ADSPEC Class
1041
1042 ADSPEC class = 13.
1043
1044 o Intserv ADSPEC object: Class = 13, C-Type = 2
1045
1046 The basic ADSPEC format is shown below. The message header and the
1047 default general parameters fragment are always present. The fragments
1048 for Guaranteed or Controlled-Load service may be omitted if the
1049 service is not to be used by the RSVP session. Additional data
1050 fragments will be added if new services are defined.
1051
1052 31 24 23 16 15 8 7 0
1053 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1054 | 0 (a) | reserved | Msg length - 1 (b) |
1055 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1056 | |
1057 | Default General Parameters fragment (Service 1) (c) |
1058 | (Always Present) |
1059 | |
1060 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1061 | |
1062 | Guaranteed Service Fragment (Service 2) (d) |
1063 | (Present if application might use Guaranteed Service) |
1064 | |
1065 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1066 | |
1067 | Controlled-Load Service Fragment (Service 5) (e) |
1068 | (Present if application might use Controlled-Load Service) |
1069 | |
1070 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1071
1072 (a) - Message format version number (0)
1073 (b) - Overall message length not including header word
1074 (c, d, e) - Data fragments
1075
1076 3.3.2. Default General Characterization Parameters ADSPEC data fragment
1077
1078 All RSVP ADSPECs carry the general characterization parameters
1079 defined in [RFC 2215]. Values for global or default general
1080 parameters (values which apply to the all services or the path
1081 itself) are carried in the per-service data fragment for service
1082 number 1, as shown in the picture above. This fragment is always
1083 present, and always first in the message.
1084
1085 31 24 23 16 15 8 7 0
1086 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1087 1 | 1 (c) |x| reserved | 8 (d) |
1088 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1089 2 | 4 (e) | (f) | 1 (g) |
1090 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1091 3 | IS hop cnt (32-bit unsigned integer) |
1092 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1093 4 | 6 (h) | (i) | 1 (j) |
1094 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1095 5 | Path b/w estimate (32-bit IEEE floating point number) |
1096 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1097 6 | 8 (k) | (l) | 1 (m) |
1098 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1099 7 | Minimum path latency (32-bit integer) |
1100 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1101 8 | 10 (n) | (o) | 1 (p) |
1102 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1103 9 | Composed MTU (32-bit unsigned integer) |
1104 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1105
1106 (c) - Per-Service header, service number 1 (Default General
1107 Parameters)
1108 (d) - Global Break bit ([RFC 2215], Parameter 2) (marked x) and
1109 length of General Parameters data block.
1110 (e) - Parameter ID, parameter 4 (Number-of-IS-hops param from
1111 [RFC 2215])
1112 (f) - Parameter 4 flag byte
1113 (g) - Parameter 4 length, 1 word not including header
1114 (h) - Parameter ID, parameter 6 (Path-BW param from [RFC 2215])
1115 (i) - Parameter 6 flag byte
1116 (j) - Parameter 6 length, 1 word not including header
1117 (k) - Parameter ID, parameter 8 (minimum path latency from [RFC
1118 2215])
1119 (l) - Parameter 8 flag byte
1120 (m) - Parameter 8 length, 1 word not including header
1121 (n) - Parameter ID, parameter 10 (composed path MTU from [RFC 2215])
1122 (o) - Parameter 10 flag byte
1123 (p) - Parameter 10 length, 1 word not including header
1124
1125 **********************************************************************/
1126 typedef struct rsvpAdSpecObject_s {
1127 struct rsvpObjectHeader_s hdr;
1128 } rsvpAdSpecObject_t;
1129
1130 /**********************************************************************
1131
1132 3.2. RSVP FLOWSPEC Object
1133
1134 The RSVP FLOWSPEC object carries information necessary to make
1135 reservation requests from the receiver(s) into the network. This
1136 includes an indication of which QoS control service is being
1137 requested, and the parameters needed for that service.
1138
1139 The QoS control service requested is indicated by the service_number
1140 in the FLOWSPEC's per-service header.
1141
1142 3.2.1 FLOWSPEC object when requesting Controlled-Load service
1143
1144 The format of an RSVP FLOWSPEC object originating at a receiver
1145 requesting Controlled-Load service is shown below. Each of the TSpec
1146 fields is represented using the preferred concrete representation
1147 specified in the 'Invocation Information' section of [RFC 2211]. The
1148 value of 5 in the per-service header (field (c), below) indicates
1149 that Controlled-Load service is being requested.
1150
1151 31 24 23 16 15 8 7 0
1152 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1153 1 | 0 (a) | reserved | 7 (b) |
1154 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1155 2 | 5 (c) |0| reserved | 6 (d) |
1156 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1157 3 | 127 (e) | 0 (f) | 5 (g) |
1158 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1159 4 | Token Bucket Rate [r] (32-bit IEEE floating point number) |
1160 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1161 5 | Token Bucket Size [b] (32-bit IEEE floating point number) |
1162 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1163 6 | Peak Data Rate [p] (32-bit IEEE floating point number) |
1164 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1165 7 | Minimum Policed Unit [m] (32-bit integer) |
1166 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1167 8 | Maximum Packet Size [M] (32-bit integer) |
1168 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1169
1170 (a) - Message format version number (0)
1171 (b) - Overall length (7 words not including header)
1172 (c) - Service header, service number 5 (Controlled-Load)
1173 (d) - Length of controlled-load data, 6 words not including
1174 per-service header
1175 (e) - Parameter ID, parameter 127 (Token Bucket TSpec)
1176 (f) - Parameter 127 flags (none set)
1177 (g) - Parameter 127 length, 5 words not including per-service
1178 header
1179
1180 In this object, the TSpec parameters [r], [b], and [p] are set to
1181 reflect the traffic parameters of the receiver's desired reservation
1182 (the Reservation TSpec). The meaning of these fields is discussed
1183 fully in [RFC 2211]. Note that it is unlikely to make sense for the
1184 [p] term to be smaller than the [r] term.
1185
1186 The maximum packet size parameter [M] should be set to the value of
1187 the smallest path MTU, which the receiver learns from information in
1188 arriving RSVP ADSPEC objects. Alternatively, if the receiving
1189 application has built-in knowledge of the maximum packet size in use
1190 within the RSVP session, and this value is smaller than the smallest
1191 path MTU, [M] may be set to this value. Note that requesting a value
1192 of [M] larger than the service modules along the data path can
1193 support will cause the reservation to fail. See section 2.3.2 for
1194 further discussion of the MTU value.
1195
1196 The value of [m] can be chosen in several ways. Recall that when a
1197 resource reservation is installed at each intermediate node, the
1198 value used for [m] is the smaller of the receiver's request and the
1199 values in each sender's SENDER_TSPEC.
1200
1201 If the application has a fixed, known minimum packet size, than that
1202 value should be used for [m]. This is the most desirable case.
1203
1204 For a shared reservation style, the receiver may choose between two
1205 options, or pick some intermediate point between them.
1206
1207 - if the receiver chooses a large value for [m], then the
1208 reservation will allocate less overhead for link-level headers.
1209 However, if a new sender with a smaller SENDER_TSPEC [m] joins the
1210 session later, an already-installed reservation may fail at that
1211 time.
1212
1213 - if the receiver chooses a value of [m] equal to the smallest
1214 value which might be used by any sender, then the reservation will
1215 be forced to allocate more overhead for link-level headers.
1216 However it will not fail later if a new sender with a smaller
1217 SENDER_TSPEC [m] joins the session.
1218
1219 For a FF reservation style, if no application-specific value is known
1220 the receiver should simply use the value of [m] arriving in each
1221 sender's SENDER_TSPEC for its reservation request to that sender.
1222
1223 **********************************************************************/
1224 typedef struct rsvpFlowSpecObject_s {
1225 struct rsvpObjectHeader_s hdr;
1226 } rsvpFlowSpecObject_t;
1227
1228 #define RSVP_POLICY_DATA_CLASS 14
1229 #define RSVP_POLICY_DATA_CTYPE 1
1230
1231 /**********************************************************************
1232 POLICY_DATA Class
1233
1234 POLICY_DATA class = 14.
1235
1236 o Type 1 POLICY_DATA object: Class = 14, C-Type = 1
1237
1238 The contents of this object are for further study.
1239
1240 **********************************************************************/
1241 typedef struct rsvpPolicyDataObject_s {
1242 struct rsvpObjectHeader_s hdr;
1243 } rsvpPolicyDataObject_t;
1244
1245 #define RSVP_RESV_CONFIRM_CLASS 15
1246 #define RSVP_RESV_CONFIRM_CTYPE_IPV4 1
1247 #define RSVP_RESV_CONFIRM_CTYPE_IPV6 2
1248
1249 /**********************************************************************
1250 Resv_CONFIRM Class
1251
1252 RESV_CONFIRM class = 15.
1253
1254 o IPv4 RESV_CONFIRM object: Class = 15, C-Type = 1
1255
1256 +-------------+-------------+-------------+-------------+
1257 | IPv4 Receiver Address (4 bytes) |
1258 +-------------+-------------+-------------+-------------+
1259
1260
1261 o IPv6 RESV_CONFIRM object: Class = 15, C-Type = 2
1262
1263 +-------------+-------------+-------------+-------------+
1264 | |
1265 + +
1266 | |
1267 + IPv6 Receiver Address (16 bytes) +
1268 | |
1269 + +
1270 | |
1271 +-------------+-------------+-------------+-------------+
1272 **********************************************************************/
1273
1274 typedef struct rsvpResvConfirmObject_s {
1275 struct rsvpObjectHeader_s hdr;
1276 union {
1277 u_int ipv4;
1278 u_char ipv6[16];
1279 } u;
1280 } rsvpResvConfirmObject_t;
1281
1282
1283 #define RSVP_LABEL_CLASS 16
1284 #define RSVP_LABEL_CTYPE 1
1285
1286 /**********************************************************************
1287
1288 LABEL class = 16, C_Type = 1
1289
1290 0 1 2 3
1291 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1292 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1293 | (top label) |
1294 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1295
1296 The contents of a LABEL is a single label, encoded in 4 octets. Each
1297 generic MPLS label is an unsigned integer in the range 0 through
1298 1048575. Generic MPLS labels and FR labels are encoded right aligned
1299 in 4 octets. ATM labels are encoded with the VPI right justified in
1300 bits 0-15 and the VCI right justified in bits 16-31.
1301
1302 **********************************************************************/
1303
1304 typedef struct rsvpLabelObject_s {
1305 struct rsvpObjectHeader_s hdr;
1306 u_int label;
1307 } rsvpLabelObject_t;
1308
1309 #define RSVP_LABEL_REQUEST_CLASS 19
1310 #define RSVP_LABEL_REQUEST_CTYPE_GENERIC 1
1311 #define RSVP_LABEL_REQUEST_CTYPE_ATM 2
1312 #define RSVP_LABEL_REQUEST_CTYPE_FR 3
1313
1314 /**********************************************************************
1315
1316 Label Request without Label Range Class = 19, C_Type = 1
1317
1318 0 1 2 3
1319 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1320 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1321 | Reserved | L3PID |
1322 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1323
1324 Reserved
1325
1326 This field is reserved. It MUST be set to zero on transmission
1327 and MUST be ignored on receipt.
1328
1329 L3PID
1330
1331 an identifier of the layer 3 protocol using this path.
1332 Standard Ethertype values are used.
1333
1334
1335 Label Request with ATM Label Range Class = 19, C_Type = 2
1336
1337 0 1 2 3
1338 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1339 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1340 | Reserved | L3PID |
1341 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1342 |M| Res | Minimum VPI | Minimum VCI |
1343 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1344 | Res | Maximum VPI | Maximum VCI |
1345 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1346
1347 Reserved (Res)
1348
1349 This field is reserved. It MUST be set to zero on transmission
1350 and MUST be ignored on receipt.
1351
1352 L3PID
1353
1354 an identifier of the layer 3 protocol using this path.
1355 Standard Ethertype values are used.
1356
1357 M
1358
1359 Setting this bit to one indicates that the node is capable of
1360 merging in the data plane
1361
1362 Minimum VPI (12 bits)
1363
1364 This 12 bit field specifies the lower bound of a block of
1365 Virtual Path Identifiers that is supported on the originating
1366 switch. If the VPI is less than 12-bits it MUST be right
1367 justified in this field and preceding bits MUST be set to zero.
1368
1369 Minimum VCI (16 bits)
1370
1371 This 16 bit field specifies the lower bound of a block of
1372 Virtual Connection Identifiers that is supported on the
1373 originating switch. If the VCI is less than 16-bits it MUST be
1374 right justified in this field and preceding bits MUST be set to
1375 zero.
1376
1377 Maximum VPI (12 bits)
1378
1379 This 12 bit field specifies the upper bound of a block of
1380 Virtual Path Identifiers that is supported on the originating
1381 switch. If the VPI is less than 12-bits it MUST be right
1382 justified in this field and preceding bits MUST be set to zero.
1383
1384 Maximum VCI (16 bits)
1385
1386 This 16 bit field specifies the upper bound of a block of
1387 Virtual Connection Identifiers that is supported on the
1388 originating switch. If the VCI is less than 16-bits it MUST be
1389 right justified in this field and preceding bits MUST be set to
1390 zero.
1391
1392
1393 Label Request with Frame Relay Label Range Class = 19, C_Type = 3
1394
1395 0 1 2 3
1396 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1397 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1398 | Reserved | L3PID |
1399 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1400 | Reserved |DLI| Minimum DLCI |
1401 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1402 | Reserved | Maximum DLCI |
1403 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1404
1405 Reserved
1406
1407 This field is reserved. It MUST be set to zero on transmission
1408 and ignored on receipt.
1409
1410 L3PID
1411
1412 an identifier of the layer 3 protocol using this path.
1413 Standard Ethertype values are used.
1414
1415 DLI
1416
1417 DLCI Length Indicator. The number of bits in the DLCI. The
1418 following values are supported:
1419
1420 Len DLCI bits
1421
1422 0 10
1423 2 23
1424
1425 Minimum DLCI
1426
1427 This 23-bit field specifies the lower bound of a block of Data
1428 Link Connection Identifiers (DLCIs) that is supported on the
1429 originating switch. The DLCI MUST be right justified in this
1430 field and unused bits MUST be set to 0.
1431
1432 Maximum DLCI
1433
1434 This 23-bit field specifies the upper bound of a block of Data
1435 Link Connection Identifiers (DLCIs) that is supported on the
1436 originating switch. The DLCI MUST be right justified in this
1437 field and unused bits MUST be set to 0.
1438 **********************************************************************/
1439
1440 #define RSVP_LABELREQ_GENERIC_SIZE 4
1441
1442 typedef struct rsvpLabelReqGeneric_s {
1443 u_short reserved;
1444 u_short l3pid;
1445 } rsvpLabelReqGeneric_t;
1446
1447 #define RSVP_LABELREQ_ATM_SIZE 12
1448
1449 typedef struct rsvpLabelReqAtmMinFlag_s {
1450 BITFIELDS_ASCENDING_3(u_short M:1,
1451 u_short reserved:3,
1452 u_short vpi:12);
1453 } rsvpLabelReqAtmMinFlag_t;
1454
1455 typedef struct rsvpLabelReqAtmMaxFlag_s {
1456 BITFIELDS_ASCENDING_2(u_short reserved:4,
1457 u_short vpi:12);
1458 } rsvpLabelReqAtmMaxFlag_t;
1459
1460 typedef struct rsvpLabelReqAtm_s {
1461 u_short reserved;
1462 u_short l3pid;
1463
1464 union {
1465 struct rsvpLabelReqAtmMinFlag_s flags;
1466 u_short mark;
1467 } minFlags;
1468 u_short minVci;
1469
1470 union {
1471 struct rsvpLabelReqAtmMaxFlag_s flags;
1472 u_short mark;
1473 } maxFlags;
1474 u_short maxVci;
1475 } rsvpLabelRequestAtm_t;
1476
1477 #define RSVP_LABELREQ_FR_SIZE 12
1478
1479 #define RSVP_LABEL_REQUEST_FR_LEN_10 0
1480 #define RSVP_LABEL_REQUEST_FR_LEN_23 2
1481
1482 typedef struct rsvpLabelReqFrMinFlag_s {
1483 BITFIELDS_ASCENDING_3(u_int reserved:6,
1484 u_int dli:2,
1485 u_int min:12);
1486 } rsvpLabelReqFrMinFlag_t;
1487
1488 typedef struct rsvpLabelReqFrMaxFlag_s {
1489 BITFIELDS_ASCENDING_2(u_int reserved:8,
1490 u_int max:24);
1491 } rsvpLabelReqFrMaxFlag_t;
1492
1493 typedef struct rsvpLabelReqFr_s {
1494 u_short reserved;
1495 u_short l3pid;
1496 union {
1497 struct rsvpLabelReqFrMinFlag_s flags;
1498 u_int mark;
1499 } minFlags;
1500 union {
1501 struct rsvpLabelReqFrMaxFlag_s flags;
1502 u_int mark;
1503 } maxFlags;
1504 } rsvpLabelRequestFr_t;
1505
1506 typedef struct rsvpLabelRequestObject_s {
1507 struct rsvpObjectHeader_s hdr;
1508 union {
1509 struct rsvpLabelReqGeneric_s generic;
1510 struct rsvpLabelReqAtm_s atm;
1511 struct rsvpLabelReqFr_s fr;
1512 } u;
1513 } rsvpLabelRequestObject_t;
1514
1515
1516 #define RSVP_EXPLICIT_ROUTE_CLASS 20
1517 #define RSVP_EXPLICIT_ROUTE_CTYPE 1
1518
1519 #define RSVP_ERO_TYPE_IPV4 1
1520 #define RSVP_ERO_TYPE_IPV6 2
1521 #define RSVP_ERO_TYPE_ASN 32
1522
1523 #define RSVP_MAX_ERO 16
1524
1525 /**********************************************************************
1526 Explicit Route Object Class = 20, C_Type = 1
1527
1528 Explicit routes are specified via the EXPLICIT_ROUTE object (ERO).
1529 The Explicit Route Class is 20. Currently one C_Type is defined,
1530 Type 1 Explicit Route. The EXPLICIT_ROUTE object has the following
1531 format:
1532
1533
1534 0 1 2 3
1535 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1536 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1537 | |
1538 // (Subobjects) //
1539 | |
1540 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1541
1542 The contents of an EXPLICIT_ROUTE object are a series of variable-
1543 length data items called subobjects. The subobjects are defined in
1544 section 4.3.3 below.
1545
1546 If a Path message contains multiple EXPLICIT_ROUTE objects, only the
1547 first object is meaningful. Subsequent EXPLICIT_ROUTE objects MAY be
1548 ignored and SHOULD NOT be propagated.
1549
1550 Subobjects
1551
1552 The contents of an EXPLICIT_ROUTE object are a series of variable-
1553 length data items called subobjects. Each subobject has the form:
1554
1555 0 1
1556 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
1557 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-------------//----------------+
1558 |L| Type | Length | (Subobject contents) |
1559 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-------------//----------------+
1560
1561 L
1562
1563 The L bit is an attribute of the subobject. The L bit is set
1564 if the subobject represents a loose hop in the explicit route.
1565 If the bit is not set, the subobject represents a strict hop in
1566 the explicit route.
1567
1568 Type
1569
1570 The Type indicates the type of contents of the subobject.
1571 Currently defined values are:
1572
1573 1 IPv4 prefix
1574 2 IPv6 prefix
1575 32 Autonomous system number
1576
1577 Length
1578
1579 The Length contains the total length of the subobject in bytes,
1580 including the L, Type and Length fields. The Length MUST be at
1581 least 4, and MUST be a multiple of 4
1582
1583 Subobject 1: IPv4 prefix
1584
1585 0 1 2 3
1586 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1587 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1588 |L| Type | Length | IPv4 address (4 bytes) |
1589 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1590 | IPv4 address (continued) | Prefix Length | Resvd |
1591 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1592
1593 L
1594
1595 The L bit is an attribute of the subobject. The L bit is set
1596 if the subobject represents a loose hop in the explicit route.
1597 If the bit is not set, the subobject represents a strict hop in
1598 the explicit route.
1599
1600 Type
1601
1602 0x01 IPv4 address
1603
1604 Length
1605
1606 The Length contains the total length of the subobject in bytes,
1607 including the Type and Length fields. The Length is always 8.
1608
1609 IPv4 address
1610
1611 An IPv4 address. This address is treated as a prefix based on
1612 the prefix length value below. Bits beyond the prefix are
1613 ignored on receipt and SHOULD be set to zero on transmission.
1614
1615 Prefix length
1616
1617 Length in bits of the IPv4 prefix
1618
1619 Padding
1620
1621 Zero on transmission. Ignored on receipt.
1622
1623 The contents of an IPv4 prefix subobject are a 4-octet IPv4 address,
1624 a 1-octet prefix length, and a 1-octet pad. The abstract node
1625 represented by this subobject is the set of nodes that have an IP
1626 address which lies within this prefix. Note that a prefix length of
1627 32 indicates a single IPv4 node.
1628
1629 Subobject 2: IPv6 Prefix
1630
1631 0 1 2 3
1632 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1633 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1634 |L| Type | Length | IPv6 address (16 bytes) |
1635 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1636 | IPv6 address (continued) |
1637 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1638 | IPv6 address (continued) |
1639 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1640 | IPv6 address (continued) |
1641 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1642 | IPv6 address (continued) | Prefix Length | Resvd |
1643 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1644
1645 L
1646
1647 The L bit is an attribute of the subobject. The L bit is set
1648 if the subobject represents a loose hop in the explicit route.
1649 If the bit is not set, the subobject represents a strict hop in
1650 the explicit route.
1651
1652 Type
1653
1654 0x02 IPv6 address
1655
1656 Length
1657
1658 The Length contains the total length of the subobject in bytes,
1659 including the Type and Length fields. The Length is always 20.
1660
1661 IPv6 address
1662
1663 An IPv6 address. This address is treated as a prefix based on
1664 the prefix length value below. Bits beyond the prefix are
1665 ignored on receipt and SHOULD be set to zero on transmission.
1666
1667 Prefix Length
1668
1669 Length in bits of the IPv6 prefix.
1670
1671 Padding
1672
1673 Zero on transmission. Ignored on receipt.
1674
1675 The contents of an IPv6 prefix subobject are a 16-octet IPv6 address,
1676 a 1-octet prefix length, and a 1-octet pad. The abstract node
1677 represented by this subobject is the set of nodes that have an IP
1678 address which lies within this prefix. Note that a prefix length of
1679 128 indicates a single IPv6 node.
1680
1681 Subobject 32: Autonomous System Number
1682
1683 The contents of an Autonomous System (AS) number subobject are a 2-
1684 octet AS number. The abstract node represented by this subobject is
1685 the set of nodes belonging to the autonomous system.
1686
1687 The length of the AS number subobject is 4 octets.
1688 **********************************************************************/
1689
1690 typedef struct rsvpExplicitRouteFlag_s {
1691 BITFIELDS_ASCENDING_3(u_short L:1,
1692 u_short type:3,
1693 u_short len:4);
1694 } rsvpExplicitRouteFlag_t;
1695
1696 #define RSVP_ER4_SIZE 8
1697
1698 typedef struct rsvpExplicitRoute4_s {
1699 union {
1700 struct rsvpExplicitRouteFlag_s flags;
1701 u_short mark;
1702 } flags;
1703 u_char address[RSVP_IPV4_ADDR_LEN];
1704 u_char prefixLen;
1705 u_char reserved;
1706
1707 /* used only for easy access to contents of 'address' */
1708 u_int uIntAddress;
1709 } rsvpExplicitRoute4_t;
1710
1711 #define RSVP_ER6_SIZE 8
1712
1713 typedef struct rsvpExplicitRoute6_s {
1714 union {
1715 struct rsvpExplicitRouteFlag_s flags;
1716 u_short mark;
1717 } flags;
1718 u_char address[RSVP_IPV6_ADDR_LEN];
1719 u_char prefixLen;
1720 u_char reserved;
1721 } rsvpExplicitRoute6_s;
1722
1723 #define RSVP_ERASN_SIZE 4
1724
1725 typedef struct rsvpExplicitRouteAsn_s {
1726 union {
1727 struct rsvpExplicitRouteFlag_s flags;
1728 u_short mark;
1729 } flags;
1730 u_short asn;
1731 } rsvpExplicitRouteAsn_t;
1732
1733 typedef struct rsvpExplicitRouteObject_s {
1734 struct rsvpObjectHeader_s hdr;
1735 union {
1736 struct rsvpExplicitRoute4_s ipv4;
1737 struct rsvpExplicitRoute6_s ipv6;
1738 struct rsvpExplicitRouteAsn_s asn;
1739 } ero[RSVP_MAX_ERO];
1740 int eroType[RSVP_MAX_ERO];
1741 int eroLength;
1742 } rsvpExplicitRouteObject_t;
1743
1744 #define RSVP_RECORD_ROUTE_CLASS 21
1745 #define RSVP_RECORD_ROUTE_CTYPE 1
1746
1747 #define RSVP_RECORD_ROUTE_TYPE_IPV4 1
1748 #define RSVP_RECORD_ROUTE_TYPE_IPV6 2
1749 #define RSVP_RECORD_ROUTE_TYPE_LABEL 3
1750
1751 #define RSVP_RECORD_ROUTE_FLAG_LOCOL_PROT_AVAIL 0x1
1752 #define RSVP_RECORD_ROUTE_FLAG_LOCOL_PROT_INUSE 0x2
1753
1754 #define RSVP_RECORD_ROUTE4_SIZE 8
1755 #define RSVP_RECORD_ROUTE6_SIZE 20
1756 #define RSVP_RECORD_ROUTE_LABEL_SIZE 20
1757
1758 #define RSVP_MAX_RR 16
1759
1760 /**********************************************************************
1761
1762 Record Route Object Class = 21, C_Type = 1
1763
1764 Routes can be recorded via the RECORD_ROUTE object (RRO).
1765 Optionally, labels may also be recorded. The Record Route Class is
1766 21. Currently one C_Type is defined, Type 1 Record Route. The
1767 RECORD_ROUTE object has the following format:
1768
1769
1770 0 1 2 3
1771 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1772 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1773 | |
1774 // (Subobjects) //
1775 | |
1776 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1777
1778 Subobjects
1779
1780 The contents of a RECORD_ROUTE object are a series of
1781 variable-length data items called subobjects. The subobjects
1782 are defined in section 4.4.1 below.
1783
1784 The RRO can be present in both RSVP Path and Resv messages. If a
1785 Path message contains multiple RROs, only the first RRO is
1786 meaningful. Subsequent RROs SHOULD be ignored and SHOULD NOT be
1787 propagated. Similarly, if in a Resv message multiple RROs are
1788 encountered following a FILTER_SPEC before another FILTER_SPEC is
1789 encountered, only the first RRO is meaningful. Subsequent RROs
1790 SHOULD be ignored and SHOULD NOT be propagated.
1791
1792
1793
1794 Subobject 1: IPv4 address
1795
1796 0 1 2 3
1797 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1798 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1799 | Type | Length | IPv4 address (4 bytes) |
1800 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1801 | IPv4 address (continued) | Prefix Length | Flags |
1802 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1803
1804 Type
1805
1806 0x01 IPv4 address
1807
1808 Length
1809
1810 The Length contains the total length of the subobject in bytes,
1811 including the Type and Length fields. The Length is always 8.
1812
1813 IPv4 address
1814
1815 A 32-bit unicast, host address. Any network-reachable
1816 interface address is allowed here. Illegal addresses, such as
1817 certain loopback addresses, SHOULD NOT be used.
1818
1819 Prefix length
1820
1821 32
1822
1823 Flags
1824
1825 0x01 Local protection available
1826
1827 Indicates that the link downstream of this node is
1828 protected via a local repair mechanism. This flag can
1829 only be set if the Local protection flag was set in the
1830 SESSION_ATTRIBUTE object of the corresponding Path
1831 message.
1832
1833 0x02 Local protection in use
1834
1835 Indicates that a local repair mechanism is in use to
1836 maintain this tunnel (usually in the face of an outage
1837 of the link it was previously routed over).
1838
1839
1840 Subobject 2: IPv6 address
1841
1842 0 1 2 3
1843 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1844 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1845 | Type | Length | IPv6 address (16 bytes) |
1846 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1847 | IPv6 address (continued) |
1848 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1849 | IPv6 address (continued) |
1850 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1851 | IPv6 address (continued) |
1852 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1853 | IPv6 address (continued) | Prefix Length | Flags |
1854 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1855
1856 Type
1857
1858 0x02 IPv6 address
1859
1860 Length
1861
1862 The Length contains the total length of the subobject in bytes,
1863 including the Type and Length fields. The Length is always 20.
1864
1865 IPv6 address
1866
1867 A 128-bit unicast host address.
1868
1869 Prefix length
1870
1871 128
1872
1873 Flags
1874
1875 0x01 Local protection available
1876
1877 Indicates that the link downstream of this node is
1878 protected via a local repair mechanism. This flag can
1879 only be set if the Local protection flag was set in the
1880 SESSION_ATTRIBUTE object of the corresponding Path
1881 message.
1882
1883
1884 0x02 Local protection in use
1885
1886 Indicates that a local repair mechanism is in use to
1887 maintain this tunnel (usually in the face of an outage
1888 of the link it was previously routed over).
1889
1890 Subobject 3, Label
1891
1892 0 1 2 3
1893 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1894 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1895 | Type | Length | Flags | C-Type |
1896 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1897 | Contents of Label Object |
1898 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1899
1900 Type
1901
1902 0x03 Label
1903
1904 Length
1905
1906 The Length contains the total length of the subobject in bytes,
1907 including the Type and Length fields.
1908
1909 Flags
1910
1911 0x01 = Global label
1912 This flag indicates that the label will be understood
1913 if received on any interface.
1914
1915 C-Type
1916
1917 The C-Type of the included Label Object. Copied from the Label
1918 Object.
1919
1920 Contents of Label Object
1921
1922 The contents of the Label Object. Copied from the Label Object
1923 **********************************************************************/
1924
1925 typedef struct rsvpRecordRoute4_s {
1926 u_char type;
1927 u_char length;
1928 u_short addressMsb;
1929 u_short addressLsb;
1930 u_char prefixLen;
1931 u_char flags;
1932 } rsvpRecordRoute4_t;
1933
1934 typedef struct rsvpRecordRoute6_s {
1935 u_char type;
1936 u_char length;
1937 u_short addressMsb;
1938 u_char addressMid[12];
1939 u_short addressLsb;
1940 u_char prefixLen;
1941 u_char flags;
1942 } rsvpRecordRoute6_t;
1943
1944 typedef struct rsvpRecordRouteLabel_s {
1945 u_char type;
1946 u_char length;
1947 u_char flags;
1948 u_char cType;
1949 struct rsvpLabelObject_s label;
1950 } rsvpRecordRouteLabel_t;
1951
1952 typedef struct rsvpRecordRouteObject_s {
1953 struct rsvpObjectHeader_s hdr;
1954 union {
1955 struct rsvpRecordRoute4_s ipv4;
1956 struct rsvpRecordRoute6_s ipv6;
1957 struct rsvpRecordRouteLabel_s label;
1958 } rr[RSVP_MAX_RR];
1959 int rrType[RSVP_MAX_RR];
1960 int rrLen;
1961 } rsvpRecordRouteObject_t;
1962
1963
1964
1965
1966
1967 #define RSVP_SESSION_ATTRIB_CLASS 207
1968 #define RSVP_SESSION_ATTRIB_CTYPE_LSP_TUNNEL 7
1969 #define RSVP_SESSION_ATTRIB_CLASS_LSP_TUNNEL_RA 1
1970
1971 #define RSVP_MAX_SESSION_NAME 64
1972
1973 #define RSVP_SESSION_ATTRIB_FLAGS_LOCAL_PROTECT 0x1
1974 #define RSVP_SESSION_ATTRIB_FLAGS_LABEL_RECORD 0x2
1975 #define RSVP_SESSION_ATTRIB_FLAGS_SE_STYLE 0x4
1976
1977 #define RSVP_SESSION_ATTRIB_LSP_TUNNEL_BASE_SIZE 4
1978 #define RSVP_SESSION_ATTRIB_LSP_TUNNEL_RA_BASE_SIZE 16
1979
1980 /**********************************************************************
1981
1982 Session Attribute Object
1983
1984 The Session Attribute Class is 207. Two C_Types are defined,
1985 LSP_TUNNEL, C-Type = 7 and LSP_TUNNEL_RA, C-Type = 1. The
1986 LSP_TUNNEL_RA C-Type includes all the same fields as the LSP_TUNNEL
1987 C-Type. Additionally it carries resource affinity information. The
1988 formats are as follows:
1989
1990 Format without resource affinities
1991
1992 SESSION_ATTRIBUTE class = 207, LSP_TUNNEL C-Type = 7
1993
1994 0 1 2 3
1995 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1996 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1997 | Setup Prio | Holding Prio | Flags | Name Length |
1998 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1999 | |
2000 // Session Name (NULL padded display string) //
2001 | |
2002 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2003
2004 Setup Priority
2005
2006 The priority of the session with respect to taking resources,
2007 in the range of 0 to 7. The value 0 is the highest priority.
2008 The Setup Priority is used in deciding whether this session can
2009 preempt another session.
2010
2011 Holding Priority
2012
2013 The priority of the session with respect to holding resources,
2014 in the range of 0 to 7. The value 0 is the highest priority.
2015 Holding Priority is used in deciding whether this session can
2016 be preempted by another session.
2017
2018 Flags
2019
2020 0x01 Local protection desired
2021
2022 This flag permits transit routers to use a local repair
2023 mechanism which may result in violation of the explicit
2024 route object. When a fault is detected on an adjacent
2025 downstream link or node, a transit router can reroute
2026 traffic for fast service restoration.
2027
2028 0x02 Label recording desired
2029
2030 This flag indicates that label information should be
2031 included when doing a route record.
2032
2033 0x04 SE Style desired
2034
2035 This flag indicates that the tunnel ingress node may
2036 choose to reroute this tunnel without tearing it down.
2037 A tunnel egress node SHOULD use the SE Style when
2038 responding with a Resv message.
2039
2040 Name Length
2041
2042 The length of the display string before padding, in bytes.
2043
2044 Session Name
2045
2046 A null padded string of characters.
2047
2048
2049 Format with resource affinities
2050
2051 SESSION_ATTRIBUTE class = 207, LSP_TUNNEL_RA C-Type = 1
2052
2053 0 1 2 3
2054 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2055 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2056 | Exclude-any |
2057 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2058 | Include-any |
2059 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2060 | Include-all |
2061 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2062 | Setup Prio | Holding Prio | Flags | Name Length |
2063 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2064 | |
2065 // Session Name (NULL padded display string) //
2066 | |
2067 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2068
2069 Exclude-any
2070
2071 A 32-bit vector representing a set of attribute filters
2072 associated with a tunnel any of which renders a link
2073 unacceptable.
2074
2075 Include-any
2076
2077 A 32-bit vector representing a set of attribute filters
2078 associated with a tunnel any of which renders a link acceptable
2079 (with respect to this test). A null set (all bits set to zero)
2080 automatically passes.
2081
2082 Include-all
2083
2084 A 32-bit vector representing a set of attribute filters
2085 associated with a tunnel all of which must be present for a
2086 link to be acceptable (with respect to this test). A null set
2087 (all bits set to zero) automatically passes.
2088
2089 Setup Priority
2090
2091 The priority of the session with respect to taking resources,
2092 in the range of 0 to 7. The value 0 is the highest priority.
2093 The Setup Priority is used in deciding whether this session can
2094 preempt another session.
2095
2096 Holding Priority
2097
2098 The priority of the session with respect to holding resources,
2099 in the range of 0 to 7. The value 0 is the highest priority.
2100 Holding Priority is used in deciding whether this session can
2101 be preempted by another session.
2102
2103 Flags
2104
2105 0x01 Local protection desired
2106
2107 This flag permits transit routers to use a local repair
2108 mechanism which may result in violation of the explicit
2109 route object. When a fault is detected on an adjacent
2110 downstream link or node, a transit router can reroute
2111 traffic for fast service restoration.
2112
2113 0x02 Label recording desired
2114
2115 This flag indicates that label information should be
2116 included when doing a route record.
2117
2118 0x04 SE Style desired
2119
2120 This flag indicates that the tunnel ingress node may
2121 choose to reroute this tunnel without tearing it down.
2122 A tunnel egress node SHOULD use the SE Style when
2123 responding with a Resv message.
2124
2125 Name Length
2126
2127 The length of the display string before padding, in bytes.
2128
2129 Session Name
2130
2131 A null padded string of characters.
2132 **********************************************************************/
2133
2134 typedef struct rsvpSessionAttribLspTunnel_s {
2135 u_char setupPrio;
2136 u_char holdPrio;
2137 u_char flags;
2138 u_char nameLen;
2139 u_char name[RSVP_MAX_SESSION_NAME];
2140 } rsvpSessionAttribLspTunnel_t;
2141
2142 typedef struct rsvpSessionAttribLspTunnelRa_s {
2143 u_int excludeAny;
2144 u_int includeAny;
2145 u_int includeAll;
2146 u_char setupPrio;
2147 u_char holdPrio;
2148 u_char flags;
2149 u_char nameLen;
2150 u_char name[RSVP_MAX_SESSION_NAME];
2151 } rsvpSessionAttribLspTunnelRa_t;
2152
2153 typedef struct rsvpSessionAttibObject_s {
2154 struct rsvpObjectHeader_s hdr;
2155 union {
2156 struct rsvpSessionAttribLspTunnel_s tunnel;
2157 struct rsvpSessionAttribLspTunnelRa_s tunnelRa;
2158 } u;
2159 } rsvpSessionAttibObject_t;
2160
2161 /**********************************************************************
2162
2163 HELLO REQUEST object
2164
2165 Class = HELLO Class, C_Type = 1
2166
2167 0 1 2 3
2168 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2169 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2170 | Src_Instance |
2171 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2172 | Dst_Instance |
2173 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2174
2175 HELLO ACK object
2176
2177 Class = HELLO Class, C_Type = 2
2178
2179 0 1 2 3
2180 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2181 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2182 | Src_Instance |
2183 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2184 | Dst_Instance |
2185 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2186
2187 Src_Instance: 32 bits
2188
2189 a 32 bit value that represents the sender's instance. The
2190 advertiser maintains a per neighbor representation/value. This
2191 value MUST change when the sender is reset, when the node reboots,
2192 or when communication is lost to the neighboring node and
2193 otherwise remains the same. This field MUST NOT be set to zero
2194 (0).
2195
2196 Dst_Instance: 32 bits
2197
2198 The most recently received Src_Instance value received from the
2199 neighbor. This field MUST be set to zero (0) when no value has
2200 ever been seen from the neighbor.
2201
2202 **********************************************************************/
2203
2204 typedef struct rsvpHelloObject_s {
2205 struct rsvpObjectHeader_s hdr;
2206 u_int src;
2207 u_int dst;
2208 } rsvpHelloObject_t;
2209
2210 /**********************************************************************
2211 RSVP Header
2212
2213 0 1 2 3
2214 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2215 +---------------+---------------+---------------+---------------+
2216 | Vers | Flags | Msg Type | RSVP Checksum |
2217 +---------------+---------------+---------------+---------------+
2218 | Send_TTL | (Reserved) | RSVP Length |
2219 +---------------+---------------+---------------+---------------+
2220
2221
2222 The fields in the common header are as follows:
2223
2224 Vers: 4 bits
2225
2226 Protocol version number. This is version 1.
2227
2228 Flags: 4 bits
2229
2230 0x01-0x08: Reserved
2231
2232 No flag bits are defined yet.
2233
2234 Msg Type: 8 bits
2235
2236 1 = Path
2237
2238 2 = Resv
2239
2240 3 = PathErr
2241
2242 4 = ResvErr
2243
2244 5 = PathTear
2245
2246 6 = ResvTear
2247
2248 7 = ResvConf
2249
2250 RSVP Checksum: 16 bits
2251
2252 The one's complement of the one's complement sum of the
2253 message, with the checksum field replaced by zero for the
2254 purpose of computing the checksum. An all-zero value
2255 means that no checksum was transmitted.
2256
2257 Send_TTL: 8 bits
2258
2259 The IP TTL value with which the message was sent. See
2260 Section 3.8.
2261
2262 RSVP Length: 16 bits
2263
2264 The total length of this RSVP message in bytes, including
2265 the common header and the variable-length objects that
2266 follow.
2267
2268
2269 **********************************************************************/
2270
2271 typedef struct rsvpHeaderFlag_s {
2272 BITFIELDS_ASCENDING_2(u_char version:4,
2273 u_char flags:4);
2274 } rsvpHeaderFlag_s;
2275
2276 #define RSVP_HDRSIZE 8
2277 #define RSVP_PDUMAXLEN 4096
2278
2279 typedef struct rsvpHeader_s {
2280 union {
2281 u_char mark;
2282 struct rsvpHeaderFlag_s flag;
2283 } flag;
2284 u_char messageType;
2285 u_short checksum;
2286 u_char ttl;
2287 u_char resserved;
2288 u_short length;
2289 } rsvpHeader_t;
2290
2291 /**********************************************************************
2292
2293 The format of a Path message is as follows:
2294
2295 <Path Message> ::= <Common Header> [ <INTEGRITY> ]
2296 <SESSION> <RSVP_HOP> <TIME_VALUES>
2297 [ <EXPLICIT_ROUTE> ] <LABEL_REQUEST>
2298 [ <SESSION_ATTRIBUTE> ]
2299 [ <POLICY_DATA> ... ]
2300 <sender descriptor>
2301
2302 <sender descriptor> ::= <SENDER_TEMPLATE> <SENDER_TSPEC>
2303 [ <ADSPEC> ] [ <RECORD_ROUTE> ]
2304
2305 **********************************************************************/
2306
2307 #define RSVP_PATH_MSG 1
2308
2309 typedef struct rsvpPathMsg_s {
2310 struct rsvpHeader_s header;
2311 struct rsvpSessionObject_s session;
2312 struct rsvpHopObject_s hop;
2313 struct rsvpTimeObject_s time;
2314 struct rsvpExplicitRouteObject_s ero;
2315 struct rsvpLabelRequestObject_s labelRequest;
2316 struct rsvpSessionAttibObject_s sessionAttrib;
2317 struct rsvpPolicyDataObject_s policyData;
2318 struct rsvpSenderTemplateObject_s senderTemplate;
2319 struct rsvpSenderTSpecObject_s senderTSpec;
2320 struct rsvpAdSpecObject_s adSpec;
2321 struct rsvpRecordRouteObject_s recordRoute;
2322
2323 u_short sessionExists:1;
2324 u_short hopExists:1;
2325 u_short timeExists:1;
2326 u_short eroExists:1;
2327 u_short labelRequestExists:1;
2328 u_short sessionAttribExists:1;
2329 u_short policyDataExists:1;
2330 u_short senderTemplateExists:1;
2331 u_short senderTSpecExists:1;
2332 u_short adSpecExists:1;
2333 u_short recordRouteExists:1;
2334
2335 } rsvpPathMsg_t;
2336
2337 /**********************************************************************
2338 The Resv message format is as follows:
2339
2340 <Resv Message> ::= <Common Header> [ <INTEGRITY> ]
2341 <SESSION> <RSVP_HOP> <TIME_VALUES>
2342 [ <RESV_CONFIRM> ] [ <SCOPE> ]
2343 [ <POLICY_DATA> ... ]
2344 <STYLE> <flow descriptor list>
2345
2346 <flow descriptor list> ::= <FF flow descriptor list> | <SE flow descriptor>
2347
2348 <FF flow descriptor list> ::= <FLOWSPEC> <FILTER_SPEC> <LABEL>
2349 [ <RECORD_ROUTE> ] | <FF flow descriptor list>
2350 <FF flow descriptor>
2351
2352 <FF flow descriptor> ::= [ <FLOWSPEC> ] <FILTER_SPEC> <LABEL>
2353 [ <RECORD_ROUTE> ]
2354
2355 <SE flow descriptor> ::= <FLOWSPEC> <SE filter spec list>
2356
2357 <SE filter spec list> ::= <SE filter spec> |
2358 <SE filter spec list> <SE filter spec>
2359
2360 <SE filter spec> ::= <FILTER_SPEC> <LABEL> [ <RECORD_ROUTE> ]
2361
2362 Note: LABEL and RECORD_ROUTE (if present), are bound to the
2363 preceding FILTER_SPEC. No more than one LABEL and/or
2364 RECORD_ROUTE may follow each FILTER_SPEC.
2365
2366 **********************************************************************/
2367
2368 #define RSVP_REV_MSG 2
2369
2370 typedef struct rsvpResvMsg_s {
2371 struct rsvpHeader_s header;
2372 struct rsvpSessionObject_s session;
2373 struct rsvpHopObject_s hop;
2374 struct rsvpTimeObject_s time;
2375 // struct rsvpResvConfirm_s resvConfirm;
2376 // struct rsvpScopeObject_s scope;
2377 struct rsvpPolicyDataObject_s policyData;
2378 struct rsvpStyleObject_s style;
2379
2380 union {
2381 struct {
2382 struct {
2383 // struct rsvpFlowSpecObject_s flowSpec;
2384 // struct rsvpFilterSpecObject_s filterSpec;
2385 struct rsvpLabelObject_s label;
2386 struct rsvpRecordRouteObject_s recordRoute;
2387 u_char flowSpecExists:1;
2388 u_char filterSpecExists:1;
2389 u_char labelExists:1;
2390 u_char recordRouteExits:1;
2391 } ffEntry[16];
2392 u_char numberFfEntry;
2393 } ff;
2394 struct {
2395 // struct rsvpFlowSpecObject_s flowSpec;
2396 struct {
2397 // struct rsvpFilterSpecObject_s filterSpec;
2398 struct rsvpLabelObject_s label;
2399 struct rsvpRecordRouteObject_s recordRoute;
2400 u_char filterSpecExists:1;
2401 u_char labelExists:1;
2402 u_char recordRouteExits:1;
2403 } seEntry[16];
2404 u_char numberSeEntry;
2405 } se;
2406 } flowDescr;
2407
2408 u_short sessionExists:1;
2409 u_short hopExists:1;
2410 u_short timeExists:1;
2411 u_short eroExists:1;
2412 u_short resvConfirmExists:1;
2413 u_short scopeExists:1;
2414 u_short policyDataExists:1;
2415 u_short flowDescrExists:1;
2416 u_short senderTSpecExists:1;
2417 u_short adSpecExists:1;
2418 u_short recordRouteExists:1;
2419
2420 } rsvpResvMsg_t;
2421 /**********************************************************************
2422 The Path Tear message format is as follows:
2423
2424 <PathTear Message> ::= <Common Header> [ <INTEGRITY> ]
2425 <SESSION> <RSVP_HOP>
2426 [ <sender descriptor> ]
2427
2428 <sender descriptor> ::= (see earlier definition)
2429
2430
2431 **********************************************************************/
2432 /**********************************************************************
2433 The Resv Tear message format is as follows:
2434
2435 <ResvTear Message> ::= <Common Header> [<INTEGRITY>]
2436 <SESSION> <RSVP_HOP> [ <SCOPE> ] <STYLE>
2437 <flow descriptor list>
2438
2439 <flow descriptor list> ::= (see earlier definition)
2440
2441 **********************************************************************/
2442
2443 /**********************************************************************
2444
2445 The Path Error message format is as follows:
2446
2447 <PathErr message> ::= <Common Header> [ <INTEGRITY> ]
2448 <SESSION> <ERROR_SPEC> [ <POLICY_DATA> ...]
2449 [ <sender descriptor> ]
2450
2451 <sender descriptor> ::= (see earlier definition)
2452
2453 **********************************************************************/
2454 /**********************************************************************
2455
2456 The Resv Error message format is as follows:
2457
2458 <ResvErr Message> ::= <Common Header> [ <INTEGRITY> ]
2459 <SESSION> <RSVP_HOP> <ERROR_SPEC> [ <SCOPE> ]
2460 [ <POLICY_DATA> ...] <STYLE>
2461 [ <error flow descriptor> ]
2462
2463 o FF style:
2464 <error flow descriptor> ::= <FF flow descriptor>
2465
2466 o SE style:
2467 <error flow descriptor> ::= <SE flow descriptor>
2468
2469 **********************************************************************/
2470 /**********************************************************************
2471
2472 The Resv Conf message format is as follows:
2473
2474 <ResvConf message> ::= <Common Header> [ <INTEGRITY> ]
2475 <SESSION> <ERROR_SPEC> <RESV_CONFIRM>
2476 <STYLE> <flow descriptor list>
2477
2478 <flow descriptor list> ::= (see earlier definition)
2479
2480 **********************************************************************/
2481
2482 #endif /* RSVPTE_STRUCT_H */
Portable Implementation of RFC3036