32 bit words in a TLV are numbered starting from 0, in increasing
order. Bits in a 32 bit word are
numbered from 0 to 32, where bit 0 is the most significant bit and
is pictured on the left. When
consecutive 32 bit words are used to represent a number, the lower
32 bit word has the most
significant value.
Each SIBBS PDU is an SIBBS header followed by one or more SIBBS
messages. The SIBBS PDU
header is shown in figure 1:
0
1
2
3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version |
Reserved
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
|
|
|
Sender ID
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
+
+
|
Sender Signature
|
+
+
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
PDU length
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
SIBBS message
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: SIBBS PDU header
Version (8 bit)
One octet unsigned integer containing the version number of the protocol.
00000001
SIBBS version 1 PDU.
All other settings are reserved
for future use.
Reserved (24 bit)
Reserved for future use
Sender ID (64 bit)
ASCII string identifying
the DS domain that sent the PDU.
Sender Signature
TBD octet string based on
the certificates exchanged during the start of operations.
PDU length (32 bit)
32 bit unsigned integer
specifying the total length of this PDU in 32 bit words, excluding the
Version, Sender ID, and
PDU length fields. The maximum PDU Length is 64 kbytes.
SIBBS message
Integer multiple of
32 bits field containing the SIBBS message.
All inter domain bandwidth broker messages have format shown in
figure
0
1
2
3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U| Message Type|
Message Length
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
+
+
|
Mandatory Parameters
|
+
+
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
+
+
|
Optional Parameters
|
+
+
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: Inter domain bandwidth broker message format
U bit
Unknown message bit. Upon
receipt of an unknown message, if U is clear (=0), a notification is
returned to the message
originator; if U is set (=1), the unknown message is silently ignored.
The sections following that
define messages specify a value for the U- bit.
Message Type
Identifies the type of message
Message Length
Specifies the cumulative
length in 32 bit words of the Message ID, Mandatory Parameters, and
Optional Parameters. The
maximum message length is 64 kbytes.
Mandatory Parameters
Variable length set of required
message parameters. Some messages have no required
parameters.
For messages that contain required parameters, the required parameters
MUST appear in the order
specified by the individual message specifications in the section Messages.
Optional Parameters
Variable length set of optional
message parameters. Many messages have no optional
parameters. For messages
that have optional parameters, the optional parameters may appear
in any order.
0
1
2
3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U|F| TLV ID
| Type |
Length
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Value
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3 - Encoding of SIBBS TLVs
U bit
Unknown TLV bit. Upon
receipt of an unknown TLV, if U is clear (=0), a notification must be
returned to the message
originator and the entire message must be ignored; if U is set (=1), the
unknown TLV is silently
ignored and the rest of the message is processed as if the unknown
TLV did not exist. The sections
following that define TLVs specify a value for the U-bit.
F bit
Forward unknown TLV bit.
This bit applies only when the U bit is set and the inter domain
bandwidth broker message
containing the unknown TLV is to be forwarded. If F is clear (=0),
the unknown TLV is not forwarded
with the containing message; if F is set (=1), the unknown
TLV is forwarded with the
containing message. The sections following that define TLVs
specify a value for the
F-bit.
TLV ID (8 bit)
The 8 bit TLV identifier
specifies the TLV.
Type (6 bit)
The 6 bit type field specifies
a type of a TLV. May be used to indicate a context (e.g. IPv4
or IPv6 or Core Tunnel related
message).
Length (16 bit)
Indicates the cumulative
length of a TLV (including U-bit, F-bit, TLV-ID, Type and Length and
Value) as an integer number
of 32 bit words. The maximum length is 64 kbyte.
Value
The information transported
by a TLV coded in 32 bit words.
In general, an inter domain bandwidth broker message may contain multiple
variable length fields.
Except where explicitly stated otherwise, these variable length fields
may occur in any order.
0
1
2
3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0| RAR ID (05) | Type
| Length
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
:
Originating BB-IP Address
:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Sequence Number
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Extension
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
:
Source Address Prefix
:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
:
Destination Address Prefix
:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type (6 bit)
Default
000000
IPv4 Reservation by an IPv4 BB.
100000 IPv6 Reservation by an IPv6 BB.
000001
ReSynch an IPv4 Reservation by an IPv4 BB. The sequence Number/Extension
field
may be out of sequence due to the local loss of state.
100001
ReSynch an IPv6 Reservation by an IPv6 BB. The sequence Number/Extension
field
may be out of sequence due to the local loss of state.
All other settings are reserved.
Note 2: Defining a reservation to be IPvX doesn't necessarily require
an originating BB to be
addressed by an IPvX address. While an originating BB-IP Address may
be IPv4, a reservation
may very well be made for an IPv6 source-destination relation. The
definition for a proper Type
remains for further study.
Length (16 bit)
Variable.
Originating BB-IP Address
Case Type 000000
4 octet field containing
the full IPv4 address of the Bandwidth Broker initially originating the
Resource Allocation Request.
Case Type 100000
32 octet field containing
the full IPv6 address of the Bandwidth Broker initially originating the
Resource Allocation Request.
Sequence number
4 octet field containing
a sequence number created by the originating Bandwidth Broker.
Extension
4 octet wrap around counter
used for any follow up message referring to the reservation
identified by the RAR containing
the Originating BB-address and the Seqence-number. In
cases of collisions of messages
bearing the same RAR ID, the message received from the
sender with the numerically
higher Sender ID (taken as binary code) is processed further. The
not processed message is
discarded without further notice.
Source Address-Prefix
Case Type 000000
4 octet field containing
the full IPv4 address or address prefix of the source of a reservation.
Case Type 100000
32 octet field containing
the full IPv6 address or address prefix of the source of a reservation.
Destination Address-Prefix
Case Type 000000
4 octet field containing
the full IPv4 address or address prefix of the destination of a reservation.
Case Type 100000
32 octet field containing
the full IPv6 address or address prefix of the destination of a
reservation.
0
1
2
3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0| IRI (15) |
Type |
Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
:
Ingress Router Address
:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type (6 bit)
000000
IPv4 Address
100000
IPv6 Address
All other settings are reserved.
Length (16 bit)
Variable.
Ingress Router Address
Case Type 000000
4 octet field containing
the IPv4 address of the interface between two domains for which the
sending domain is requesting
service.
Case Type 100000
32 octet field containing
the IPv6 address of the interface between two domains for which the
sending domain is requesting
service.
This field is replaced in the message by each sending bandwidth broker.
When sent by an
end-system, this field contains the IP address of the access router
interface through which the flow
will pass en route to the destination. When sent from a bandwidth broker
to an end system, it
contains the IP address of the access router interface over which the
flow will be forwarded.
0
1
2
3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0| SPO (31) |
Type |
Length
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
ServiceType |P|
Reserved
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
:
Service Specific Parameters
:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type (6 bit)
Reserved.
Length (16 bit)
14 octets.
Service Type (15 bit)
Default: 00...01 QBone Premium Service. Service Specific parameters are present.
All other settings are reserved.
The service type describes wh
P-Bit
0 Globally
defined service
1 Privately
defined service
Reserved (16 bit)
Reserved for future use
0
1
2
3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
0..01 |0|
00...0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
PHB ID Code
| DSCP |CU | Resv
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
|
QPS-Peak Rate
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
|
|
+
Experimental
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PHB ID Code (16 bit)
Default
101110...0
As specified by RFC 2836. The six most significant bits of the PHB ID Code
MUST be set to the EF DSCP as specified by RFC2598
DSCP (6 bit)
Default: 101110
This field MUST indicate
the DSCP used by the sending domain coded according to RFC 2474.
The field should be set
to the DSCP value 101110 as recommended by RFC 2598.
CU (2bit)
Currently Unused. Any settings
of this field are ignored by a SIBBS version 1 Bandwidth
Broker.
Resv (8 bit)
Reserved for future use.
QPS Peak Rate
32-bit IEEE floating point
number indicating the QPS Peak Rate in Bytes per second. The
format of IEEE floating-point
numbers is further summarized in RFC 1832.
Experimental
The 8 octet Experimental
Field should allow for extensions of the SPO to other service specific
parameters allowed for negotiation
at reservation set up. Examples would be MTU size or burst
size.
A SIBBS version 1 Bandwidth
Broker MUST insert an "Unknown Parameters" TLV if the
Experimental field contains
any unknown settings. The RAR is otherwise processed according
to the specifications of
this document.
0
1
2
3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0| SAT (20) |
Type |
Length
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Start-Time
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
It is mandatory to support advance reservations by version1 implementations
of SIBBS. If the Start
Time TLV is present, a Bandwidth Broker MUST be able to perform an
advance reservation as
specified. Absence of the Start Time TLV indicates an immediate resource
reservation.
Type (6 bit)
Reserved.
Length (16 bit)
4 octets.
Start Time (4 octet)
Default:
Start Time in 32 bit unix
timeval format. The bits represent the seconds since
00:00 UTC, January 1, 1970.
Note: If felt to be more
appropriate, the value could also indicate the seconds
since 00:00 UTC, January
1, 2000. This remains for further study.
0
1
2
3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0| SOT (21) |
Type |
Length
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Stop-Time
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
It is mandatory to support reservation terminations with pre-determined
end time by version1
implementations of SIBBS. If the Stop Time TLV is present, a Bandwidth
Broker MUST be able
to terminate a reservation as specified. Absence of the Stop Time TLV
indicates an indefinite
resource reservation.
Remark of the author: By this construction an "As long as possible"
Stop Time indication is not
supported!
Type (6 bit)
Reserved.
Length (16 bit)
4 octets.
Stop Time
Default:
Stop Time in 32 bit unix
timeval format. The bits represent the seconds since
00:00 UTC, January 1, 1970.
Note: If felt to be more
appropriate, the value could also indicate the seconds
since 00:00 UTC, January
1, 2000. This remains for further study.
0
1
2
3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0| RARF(25) |
Type |
Length
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CT | CRes |P| DS|C| Res
| Reserved
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
It is mandatory to support the RAR Flags TLV by version1 implementations
of SIBBS. Any SIBBS
version 1 MUST interpret the RAR Flags TLV as specified by this document.
The absence of the RAR Flags TLV indicates that all RARF parameters
are set to default.
Type (6 bit)
Default
000000
Standard Reservation.
000001 RAR relates to a pre-established Core Tunnel.
All other settings are reserved.
Length (16 bit)
4 octets.
CT Flag (Core Tunnel indication, 4 bit)
A SIBBS version 1 Bandwidth Broker
MUST support the Core Tunnel indication flag:
Default
0000 Standard
reservation
0001 Enable
as Core Tunnel
0011 Enable
as Core Tunnel. Core Tunnel Destination Information (CTI) is attached to
the
RAR.
Note: this is an action required by the penultimate BB.
CRes (Core Tunnel Reserved, 4 bit)
Reserved.
P-Flag (Probe, 1 bit)
Default
0
Reserve the requested resources.
1
Probe. Don't reserve any resources.
DS-Flag (Delta, 2 bit)
Default
00
SPO indicates absolute values for all SPO parameters.
10
SPO indicates a delta value for the QPS-Peak Rate with positive sign (may
be used when
a reservation is changed or negotiated).
11
SPO indicates a delta value for the QPS-Peak Rate with negative sign (may
be used when
a reservation is changed or negotiated).
Note: Care must be taken with the definition of delta reservations
instead of absolute reservations.
Should the SPO indicate more than a single parameter, a Delta Flag
for each individual parameter
is preferrable. This SPO parameter individual Delta Flag must indicate
which parameter is indicated
by this delta flag and the sign of this parameter. This is is only
way to operate a change in a
reservation where a SPO parameter A is increased (by a delta Value
of positive sign) while a SPO
parameter B is decreased (by a Delta value of negative sign) with a
single RAR-RAA sequence.
C-Flag (Collect-Call, Receiver pays, 1 bit)
Default
0
Sender pays.
1 Receiver Pays.
Res (4 bit)
Reserved.
Reserved (16 bit)
This field is reserved for
future extensions. Any settings MUST be ignored by a SIBBS
version 1 Bandwidth Broker.
0
1
2
3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0| AAF (26) |
Type |
Length
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A|H|Res|EE |EtE|FE | Res
| Reserved
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
It is mandatory to support the RAR Flags TLV by version1 implementations
of SIBBS. Any SIBBS
version 1 MUST interpret the RAR Flags TLV as specified by this document.
The absence of the RAR Flags TLV indicates that all RARF parameters
are set to default.
Type (6 bits)
Default
000000
Standard Reservation.
000001
RAA relates to a pre-established Core Tunnel. Core Tunnel Resource Reservation
Identifier (CTR) is attached.
Length (16 bits)
4 octets.
A-Flag (RAR Acceptance, 1 bit)
A SIBBS version 1 Bandwidth
Broker MUST support the RAR Acceptance indication flag:
Default
0 RAR
accepted.
1 RAR rejected.
H-Flag (Hint-Flag, 1 bit)
Default
0 SPO
is not rewritten.
1 SPO is rewritten with values hinting on a reservation parametrization which would succeed.
Note: Currently there's no Start/Stop Time negotiation mechanism. This
would require some extra
flags to be set in the RARF and AAF.
Res (2 bit)
Reserved.
EE-Flag (Edge to Edge-Flag, 2 bits)
A SIBBS version 1 Bandwidth
Broker MUST support the Edge to Edge-Flag:
Default
00 Standard
RAR.
01 Core Tunnel set up successful.
All other settings are reserved.
Note: A transit Bandwidth Broker MUST ignore the EE-Flag setting.
EtE (2 bits)
Reserved for extension of
the Edge to Edge-Flag.
FE-Flag (Failure/Error-Flag, 2 bit)
A SIBBS version 1 Bandwidth
Broker MUST support the Failure/Error-Flag:
Default
00 No error
occured.
01 Error during Reservation set-up. No further information on the Error is provided.
A SIBBS version 1 Bandwidth
Broker SHOULD support the following Error/Failure-Flag:
11 Error Code
TLV is attached.
Res (6 bit)
Reserved.
Reserved (16 bit)
This field is reserved for
future extensions. Any settings MUST be ignored by a SIBBS
version 1 Bandwidth Broker.
0
1
2
3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0| CTI (10) |
Type |
Length
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
:
Destination BB-IP Address
:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
:
Destination Ingress-Router Address
:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
It is mandatory to support Core Tunnels by version1 implementations
of SIBBS. If resources to set
up a requested Core Tunnel are available by the penultimate destination,
the Core Tunnel
Destination Information TLV MUST be added to a RAR and the destination
Ingress Router Address
must be set. The destination domain BB MUST on set up of the Core Tunnel
insert the Destination
BB IP Adress and attach the CTI TLV to the RAA corresponding to the
Core Tunnel.
Type (6 bit)
Default
000000
IPv4 Reservation by an IPv4 BB.
100000
IPv6 Reservation by an IPv6 BB.
All other settings are reserved.
Note: Defining a reservation to be IPvX doesn't necessarily require
an originating BB to be addressed
by an IPvX address. While an originating BB-IP Address may be IPv4,
a reservation may very well
be made for an IPv6 source-destination relation. The definition for
a proper Type remains for further
study.
Length (16 bit)
Variable.
Destination BB-IP Address
Case Type 000000
4 octet field containing
the full IPv4 address of the Bandwidth Broker terminating the Core
Tunnel.
Case Type 100000
32 octet field containing
the full IPv6 address of the Bandwidth Broker terminating the Core
Tunnel.
Destination Ingress Router Address
Case Type 000000
4 octet field containing
the IPv4 address of the interface from which a Core Tunnel of the
sending domain is requesting
service. This router identifies the first upstream router adjacent to
the Core Tunnel destination
domain.
Case Type 100000
32 octet field containing
the IPv6 address of the interface from which a Core Tunnel of the
sending domain is requesting
service. This router identifies the first upstream router adjacent to
the Core Tunnel destination
domain.
Note: The Destination Ingress Router Address may be stored in a destination
BB data base. By the
non ambiguos Core Tunnel Resource Reservation Identifier linked to
each individual core tunnel, the
Destination Ingress Router Address may be retrieved from the destination
BB data base.
0
1
2
3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0| CTR (11) |
Type |
Length
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Sequence Number
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Extension
|PA | Reserved
|E|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
It is mandatory to support Core Tunnels by version1 implementations
of SIBBS. If resources within
a Core Tunnel are reserved by a RAR or confirmed or rejected by a RAA,
the Core Tunnel
Resource Reservation Identifier TLV MUST be attached to the corresponding
RAR or RAA.
Length
Variable. (Minimum 8 octets.)
Sequence number
4 octet field containing
a sequence number created by the originating Bandwidth Broker.
Extension
2 octet wrap around counter
used for any follow up CTR referring to the reservation identified
by the CTR containing the
Seqence-number. In cases of collisions of CTRs bearing the same
CTR ID, the CTR received
from the sender with the numerically higher Sender ID (taken as
binary code) is processed
further. The not processed CTR is discarded without further notice.
PA-Flags (Policy Request Flags, 2 bits)
Default
00 No
policy information requested.
10 Policy
Information required.
11 Policy
Information attached.
01 No
Policy Information available.
Reserved
13 bit field reserved for
future use
Extension indicator (1 bit)
1
Another parameter is following
0
End of TLV.
0
1
2
3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0| Error(27) |
Type |
Length
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
:
Location IP Address
:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error
Reasons |
Reserved
|E|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type (6 bit)
Default
000000
IPv4 Reservation by an IPv4 BB.
100000
IPv6 Reservation by an IPv6 BB.
All other settings are reserved.
Note: Defining a reservation to be IPvX doesn't necessarily require
an originating BB to be addressed
by an IPvX address. While an originating BB-IP Address may be IPv4,
a reservation may very well
be made for an IPv6 source-destination relation. The definition for
a proper Type remains for further
study.
Length (16 bit)
Variable.
Location BB-IP Address
Case Type 000000
4 octet field containing
the full IPv4 address of the Bandwidth Broker reporting an error.
Case Type 100000
32 octet field containing
the full IPv6 address of the Bandwidth Broker reporting an error.
Error Reasons
2 octet field containing
information on the problem leading to the rejection of a reservation.
0..0000000
Unknown Problem.
0..0000001
Unexpected TLV.
0..1000001
Unexpected TLV. Unexpected TLV is attached.
0..0100000
Unknown TLV.
0..0100001
Unknown TLV. Unknown TLV attached.
0..1100000
Unexpected Meassage.
0..0000010
No SLS to downstream domain.
0..0000100
SPO resources not available.
0..0000011
Service identified by GSID not supported.
Reserved (15 bit)
Reserved for future use.
Extension indicator (1 bit)
1
Another parameter is following.
0
End of TLV
0
1
2
3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0| UI(28)
| Type |
Length
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|M|
Reserved
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Unrecognized TLV Header
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
:
Reporting Node IP Address
:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type (6 bit)
Default
000000
Reporting node IPv4 address.
100000 Reporting node IPv6 address.
All other settings are reserved.
Note: Defining a reservation to be IPvX doesn't necessarily require
an originating BB to be addressed
by an IPvX address. While an originating BB-IP Address may be IPv4,
a reservation may very well
be made for an IPv6 source-destination relation. The definition for
a proper Type remains for further
study.
Length (16 bit)
Variable.
M-Flag (1 bit)
0 Unknown TLV contained in RAR message.
1 Unknown TLV contained in RAA message.
Reserved (31 bit)
Reserved for future use.
Unrecognized TLV Header (32 bit)
Contains the first 32 bits
of the unrecognized TLV (U-bit, F-bit, TLV ID, Type, Length)
Reporting Node IP Address
Case Type 000000
4 octet field containing
the full IPv4 address of the Bandwidth Broker reporting an
unrecognized TLV.
Case Type 100000
32 octet field containing
the full IPv6 address of the Bandwidth Broker reporting an
unrecognized TLV.
0
1
2
3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0| Cancel(32) | Type
| Length
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
:
Cancel Originator IP Address
:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
NRAR IDs
| Reserved
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
:
Canceled RAR IDs
:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Originator Signature
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type (6 bit)
Default
000000
Canceling node identified by IPv4 address.
100000 Canceling node identified by IPv6 address.
All other settings are reserved.
Note: Defining a reservation to be IPvX doesn't necessarily require
an originating BB to be addressed
by an IPvX address. While an originating BB-IP Address may be IPv4,
a reservation may very well
be made for an IPv6 source-destination relation. The definition for
a proper Type remains for further
study.
Length (16 bit)
Variable.
Cancel Originator IP Address
Case Type 000000
4 octet field containing
the full IPv4 address of the Bandwidth Broker canceling the indicated
set of reservations.
Case Type 100000
32 octet field containing
the full IPv6 address of the Bandwidth Broker canceling the indicated
set of reservations.
NRAR IDs (Number of RAR IDs, 16 bit)
Number of RAR IDs to be
canceled. must at least be one.
Canceled RAR IDs
A list of the RAR IDs canceled
by this message. MUST at least contain one RAR ID.
Originator Signature
Public Key of the Bandwidth
Broker originating the Cancel message.
0
1
2
3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0| KA ID (01) | Type
| Length
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
:
Originating BB-IP Address
:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Sequence Count
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type (6 bit)
Default
000000
Originating Bandwidth Broker uses IPv4 address.
100000
Originating Bandwidth Broker uses IPv6 address.
All other settings are reserved.
Length (16 bit)
Variable.
Originating BB-IP Address
Case Type 000000
4 octet field containing
the full IPv4 address of the Bandwidth Broker originating the
Keep Alive message.
Case Type 100000
32 octet field containing
the full IPv6 address of the Bandwidth Broker originating the
Keep Alive message.
Sequence Count
4 octet wrap around counter
used for any follow up Keep Alive message by the Bandwidth
Broker originating the Keep
Alive message.
0
1
2
3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0| Policy (08) | Type
|
Length
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
:
Policy Information
:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type (6 bit)
Default
000000
All other settings are reserved.
Length (16 bit)
Variable.
Policy Information (n * 32 bit)
Contains policy information.
Details TBA.
0
1
2
3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| RAR (03) |
Message Length
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
RAR ID
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Ingress Router ID
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Service Parameterization Object
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Optional Parameters
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0
1
2
3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| RAA (04) |
Message Length
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
RAR ID
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Ingress Router ID
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Service Parameterization Object
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Optional Parameters
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0
1
2
3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| Cancel(32) |
Message Length
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Cancel Range
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0
1
2
3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| Ref (11) |
Message Length
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
RAR ID
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0
1
2
3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| KA (01) |
Message Length
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Keep Alive ID
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
[QBBA] "QBone Bandwidth Broker Architecture", work in progress.
[RFC2119] "Key words for use in RFCs to indicate requirement levels", IETF RFC2119, March 1997.