Resource Reservation Protocol (RSVP) Parameters
Information on RSVP Assignment and Modification Guidelines can
be found in RFC 3936.
Message Types
- RFC 3936: Procedures for Modifying the Resource reSerVation Protocol (RSVP)
An 8-bit number that identifies the function of the RSVP message.
| Range |
Registration Procedures |
| 0-239 |
Standards Action |
| 240-255 |
Expert Review |
| Value |
Message Type |
Reference |
| 0 |
Reserved |
|
| 1 |
Path |
RFC 2205 |
| 2 |
Resv |
RFC 2205 |
| 3 |
PathErr |
RFC 2205 |
| 4 |
ResvErr |
RFC 2205 |
| 5 |
PathTear |
RFC 2205 |
| 6 |
ResvTear |
RFC 2205 |
| 7 |
ResvConf |
RFC 2205 |
| 8 |
DREQ |
RFC 2745 |
| 9 |
DREP |
RFC 2745 |
| 10 |
ResvTearConfirm |
Fred Baker |
| 11 |
Unassigned |
|
| 12 |
Bundle |
RFC 2961 |
| 13 |
ACK |
RFC 2961 |
| 14 |
Reserved |
|
| 15 |
Srefresh |
RFC 2961 |
| 16-19 |
Unassigned |
|
| 20 |
Hello |
RFC 3209 |
| 21 |
Notify Message |
RFC 3473 |
| 22-24 |
Unassigned |
|
| 25 |
Integrity Challenge |
RFC 2747; RFC 3097 |
| 26 |
Integrity Response |
RFC 2747; RFC 3097 |
| 27-29 |
Unassigned |
|
| 30 |
RecoveryPath |
RFC 5063 |
| 31-65 |
Unassigned |
|
| 66 |
DSBM_willing |
Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager): A
Proposal for Admission Control over IEEE 802-style
networks", Internet Draft, July 1997. |
| 67 |
I_AM_DSBM |
Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager): A
Proposal for Admission Control over IEEE 802-style
networks", Internet Draft, July 1997. |
| 68-255 |
Unassigned |
|
Class Names, Class Numbers, and Class Types
- RFC 3936: Procedures for Modifying the Resource reSerVation Protocol (RSVP)
Each class of data object in an RSVP message is identified by a Class
Name and an 8-bit Class Number. The Class Name is all upper-case.
Within each object class there is an 8-bit Class Type (also known as a
C-Type). The following lists shows the Class Number and Class Name for
each class, followed by the corresponding Class Types.
In general, the appropriateness of allowing assignments of Class Types
through Expert Review or Vendor Private depends on the semantics of the Class
Number itself. Thus, any new Class Number definition must specify an
appropriate IANA Considerations policy for assigning additional Class
Type values.
For Class Numbers that pre-date RFC 3936 (specifically, 0, 1, 3-25,
30-37, 42-45, 64, 65, 128-131, 161-165, 192-196, and 207), the
default assignment policy for new Class Types is Standards Action,
unless a Standards Track or Best Current Practice RFC supercedes this.
The EXPLICIT_ROUTE object RFC 3209 carries a variable length sub-
object that is identified by a 7-bit Type field. Types 0 through 119
are to be assigned by Standards Action. Types 120 through 123 are to
be assigned by Expert Review. Types 124 through 127 are to be
reserved for Vendor Private Use.
The RECORD_ROUTE object RFC 3209 carries a variable length sub-
object that is identified by an 8-bit Type field. Types 0 through
191 are to be assigned by Standards Action. Types 192 through 251
are to be assigned by Expert Review. Types 252 through 255 are to be
reserved for Vendor Private Use.
| Range |
Registration Procedures |
| 0-119 |
Standards Action |
| 120-123 |
Expert Review |
| 124-127 |
Reserved for Private Use |
| 128-183 |
Standards Action |
| 184-187 |
Expert Review |
| 188-191 |
Reserved for Private Use |
| 192-247 |
Standards Action |
| 248-251 |
Expert Review |
| 252-255 |
Reserved for Private Use |
| Class Number |
Class Name |
Reference |
| 0 |
NULL |
RFC 2205 |
| 1 |
SESSION |
RFC 2205 |
| 2 |
unassigned |
|
| 3 |
RSVP_HOP |
RFC 2205 |
| 4 |
INTEGRITY |
RFC 2205 |
| 5 |
TIME_VALUES |
RFC 2205 |
| 6 |
ERROR_SPEC |
RFC 2205 |
| 7 |
SCOPE |
RFC 2205 |
| 8 |
STYLE |
RFC 2205 |
| 9 |
FLOWSPEC |
RFC 2205 |
| 10 |
FILTER_SPEC |
RFC 2205 |
| 11 |
SENDER_TEMPLATE |
RFC 2205 |
| 12 |
SENDER_TSPEC |
RFC 2205 |
| 13 |
ADSPEC |
RFC 2205 |
| 14 |
POLICY_DATA |
RFC 2205 |
| 15 |
RESV_CONFIRM |
RFC 2205 |
| 16 |
RSVP_LABEL |
RFC 3209 |
| 17 |
HOP_COUNT |
Bruce Davie |
| 18 |
STRICT_SOURCE_ROUTE |
Fred Baker |
| 19 |
LABEL_REQUEST |
RFC 3209 |
| 20 |
EXPLICIT_ROUTE |
RFC 3209 |
| 21 |
ROUTE_RECORD
(also known as RECORD_ROUTE) |
RFC 3209 |
| 22 |
HELLO |
RFC 3209 |
| 23 |
MESSAGE_ID |
RFC 2961 |
| 24 |
MESSAGE_ID_ACK |
RFC 2961 |
| 25 |
MESSAGE_ID_LIST |
RFC 2961 |
| 26-29 |
Unassigned |
|
| 30 |
DIAGNOSTIC |
RFC 2745 |
| 31 |
ROUTE |
RFC 2745 |
| 32 |
DIAG_RESPONSE |
RFC 2745 |
| 33 |
DIAG_SELECT |
RFC 2745 |
| 34 |
RECOVERY_LABEL |
RFC 3473 |
| 35 |
UPSTREAM_LABEL |
RFC 3473 |
| 36 |
LABEL_SET |
RFC 3473 |
| 37 |
PROTECTION |
RFC 3473 |
| 38 |
PRIMARY_PATH_ROUTE |
RFC 4872 |
| 39-41 |
Unassigned |
|
| 42 |
DSBM IP ADDRESS |
Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager):
Protocol for RSVP-based Admission Control over IEEE
802-style networks", Internet Draft, November 1997. |
| 43 |
SBM_PRIORITY |
Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager):
Protocol for RSVP-based Admission Control over IEEE
802-style networks", Internet Draft, November 1997. |
| 44 |
DSBM TIMER INTERVALS |
Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager):
Protocol for RSVP-based Admission Control over IEEE
802-style networks", Internet Draft, November 1997. |
| 45 |
SBM_INFO |
Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager):
Protocol for RSVP-based Admission Control over IEEE
802-style networks", Internet Draft, November 1997. |
| 46-49 |
Unassigned |
|
| 50 |
S2L_SUB_LSP |
RFC 4875 |
| 51-62 |
Unassigned |
|
| 63 |
DETOUR |
RFC 4090 |
| 64 |
CHALLENGE |
RFC 2747 |
| 65 |
DIFF-SERV |
RFC 3270 |
| 66 |
CLASSTYPE |
RFC 4124 |
| 67 |
LSP_REQUIRED_ATTRIBUTES |
RFC 5420 |
| 68-119 |
Unassigned |
|
| 120 |
UPSTREAM_FLOWSPEC |
RFC 6387 |
| 121 |
UPSTREAM_TSPEC |
RFC 6387 |
| 122 |
UPSTREAM_ADSPEC |
RFC 6387 |
| 123-127 |
Unassigned |
|
| 128 |
NODE_CHAR |
RFC 2746 |
| 129 |
SUGGESTED_LABEL |
RFC 3473 |
| 130 |
ACCEPTABLE_LABEL_SET |
RFC 3473 |
| 131 |
RESTART_CAP |
RFC 3473 |
| 132 |
SESSION-OF-INTEREST |
RFC 4860 |
| 133 |
LINK_CAPABILITY |
RFC 4974 |
| 134 |
Capability Object |
RFC 5063 |
| 135 |
CONDITIONS |
RFC 9705 |
| 136-160 |
Unassigned |
|
| 161 |
RSVP_HOP_L2 |
Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager):
Protocol for RSVP-based Admission Control over IEEE
802-style networks", Internet Draft, November 1997. |
| 162 |
LAN_NHOP_L2 |
Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager):
Protocol for RSVP-based Admission Control over IEEE
802-style networks", Internet Draft, November 1997. |
| 163 |
LAN_NHOP_L3 |
Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager):
Protocol for RSVP-based Admission Control over IEEE
802-style networks", Internet Draft, November 1997. |
| 164 |
LAN_LOOPBACK |
Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager):
Protocol for RSVP-based Admission Control over IEEE
802-style networks", Internet Draft, November 1997. |
| 165 |
TCLASS |
Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager):
Protocol for RSVP-based Admission Control over IEEE
802-style networks", Internet Draft, November 1997. |
| 166-191 |
Unassigned |
|
| 192 |
SESSION_ASSOC |
RFC 2746 |
| 193 |
LSP_TUNNEL_INTERFACE_ID |
RFC 3477 |
| 194 |
USER_ERROR_SPEC |
RFC 5284 |
| 195 |
NOTIFY_REQUEST |
RFC 3473 |
| 196 |
ADMIN_STATUS |
RFC 3473 |
| 197 |
LSP_ATTRIBUTES |
RFC 5420 |
| 198 |
ALARM_SPEC |
RFC 4783 |
| 199 |
ASSOCIATION |
RFC 4872 |
| 200 |
SECONDARY_EXPLICIT_ROUTE |
RFC 4873 |
| 201 |
SECONDARY_RECORD_ROUTE |
RFC 4873 |
| 202 |
CALL ATTRIBUTES |
RFC 6001 |
| 203 |
REVERSE_LSP |
RFC 7551 |
| 204 |
S2L_SUB_LSP_FRAG |
RFC 8149 |
| 205 |
FAST_REROUTE |
RFC 4090 |
| 206 |
Unassigned |
|
| 207 |
SESSION_ATTRIBUTE |
RFC 3209 |
| 208-223 |
Unassigned |
|
| 224 |
Unassigned |
|
| 225 |
DCLASS |
RFC 2996 |
| 226 |
PACKETCABLE EXTENSIONS |
Anon, "PacketCable Dynamic Quality-of-Service
Specification", PKT-SP-DQOS-O01-991201, date unknown. |
| 227 |
ATM_SERVICECLASS |
RFC 3496 |
| 228 |
CALL_OPS (ASON) |
RFC 3474 |
| 229 |
GENERALIZED_UNI |
RFC 3476 |
| 230 |
CALL_ID |
RFC 3474 |
| 231 |
3GPP2_Object |
Kuntal Chowdury |
| 232 |
EXCLUDE_ROUTE |
RFC 4874 |
| 233-247 |
Unassigned |
|
| 248 |
PCN |
RFC 7417 |
| 249-251 |
Unassigned |
|
| 252-255 |
Reserved for Private Use |
RFC 3936 |
Class Types or C-Types ‒ 0 NULL
- RFC 2205: Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
Ignored.
| Value |
Description |
Reference |
| No registrations at this time. |
Class Types or C-Types ‒ 1 SESSION
- RFC 2205: Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
Class Types or C-Types ‒ 3 RSVP_HOP
- RFC 2205: Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
Class Types or C-Types ‒ 4 INTEGRITY
- RFC 2205: Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
| Value |
Description |
Reference |
| 1 |
Type 1 Integrity Value |
RFC 2747 |
Class Types or C-Types ‒ 5 TIME_VALUES
- RFC 2205: Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
| Value |
Description |
Reference |
| 1 |
Type 1 Time Value |
RFC 2205 |
Class Types or C-Types ‒ 6 ERROR_SPEC
- RFC 2205: Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
Class Types or C-Types ‒ 7 SCOPE
- RFC 2205: Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
Class Types or C-Types ‒ 8 STYLE
- RFC 2205: Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
| Value |
Description |
Reference |
| 1 |
Type 1 Style |
RFC 2205 |
Class Types or C-Types ‒ 9 FLOWSPEC
- RFC 2205: Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
Class Types or C-Types ‒ 10 FILTER_SPEC
- RFC 2205: Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
Class Types or C-Types ‒ 11 SENDER_TEMPLATE
- RFC 2205: Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
Class Types or C-Types ‒ 12 SENDER_TSPEC
- RFC 2205: Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
Class Types or C-Types ‒ 13 ADSPEC
- RFC 2205: Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
| Value |
Description |
Reference |
| 2 |
Int-serv |
RFC 2210 |
Class Types or C-Types ‒ 14 POLICY_DATA
- RFC 2205: Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
| Value |
Description |
Reference |
| 1 |
Type 1 policy data |
RFC 2205 |
Class Types or C-Types ‒ 15 RESV_CONFIRM
- RFC 2205: Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
Class Types or C-Types ‒ 16 RSVP_LABEL
- RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels
Class Types or C-Types ‒ 17 HOP_COUNT
Class Types or C-Types ‒ 18 STRICT_SOURCE_ROUTE
Class Types or C-Types ‒ 19 LABEL_REQUEST
- RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels
| Value |
Description |
Reference |
| 1 |
Without Label Range |
RFC 3209 |
| 2 |
With ATM Label Range |
RFC 3209 |
| 3 |
With Frame Relay Label Range |
RFC 3209 |
| 4 |
Generalized_Label_Request |
RFC 3473 |
| 5 |
Generalized Channel_Set |
RFC 6002 |
Class Types or C-Types ‒ 20 EXPLICIT_ROUTE
- RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels
| Value |
Description |
Reference |
| 1 |
Type 1 Explicit Route |
RFC 3209 |
Subobject type ‒ 20 EXPLICIT_ROUTE ‒ Type 1 Explicit Route
- RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels
- RFC 7571: GMPLS RSVP-TE Extensions for Lock Instruct and Loopback
Class Types or C-Types ‒ 21 ROUTE_RECORD
- RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels
| Value |
Description |
Reference |
| 1 |
Type 1 Route Record |
RFC 3209 |
Subobject type ‒ 21 ROUTE_RECORD ‒ Type 1 Route Record
- RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels
Class Types or C-Types ‒ 22 HELLO
- RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels
Class Types or C-Types ‒ 23 MESSAGE_ID
- RFC 2961: RSVP Refresh Overhead Reduction Extensions
| Value |
Description |
Reference |
| 1 |
Type 1 Message ID |
RFC 2961 |
Class Types or C-Types ‒ 24 MESSAGE_ID_ACK
- RFC 2961: RSVP Refresh Overhead Reduction Extensions
| Value |
Description |
Reference |
| 1 |
MESSAGE_ID_ACK |
RFC 2961 |
| 2 |
MESSAGE_ID_NACK |
RFC 2961 |
Class Types or C-Types ‒ 25 MESSAGE_ID_LIST
- RFC 2961: RSVP Refresh Overhead Reduction Extensions
| Value |
Description |
Reference |
| 1 |
Message ID list |
RFC 2961 |
| 2 |
IPv4 Message ID Source list |
RFC 2961 |
| 3 |
IPv6 Message ID Source list |
RFC 2961 |
| 4 |
IPv4 Message ID Multicast list |
RFC 2961 |
| 5 |
IPv6 Message ID Multicast list |
RFC 2961 |
Class Types or C-Types ‒ 30 DIAGNOSTIC
Class Types or C-Types ‒ 31 ROUTE
Class Types or C-Types ‒ 32 DIAG_RESPONSE
Class Types or C-Types ‒ 33 DIAG_SELECT
| Value |
Description |
Reference |
| 1 |
Type 1 Diagnostic Select |
RFC 2745 |
Class Types or C-Types ‒ 34 RECOVERY_LABEL
- RFC 3473: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions
Same values as RSVP_LABEL (C-Num 16)
| Value |
Description |
Reference |
| No registrations at this time. |
Class Types or C-Types ‒ 35 UPSTREAM_LABEL
- RFC 3473: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions
Same values as RSVP_LABEL (C-Num 16)
| Value |
Description |
Reference |
| No registrations at this time. |
Class Types or C-Types ‒ 36 LABEL_SET
- RFC 3473: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions
| Value |
Description |
Reference |
| 1 |
Type 1 Label_set |
RFC 3473 |
Class Types or C-Types ‒ 37 PROTECTION
- RFC 3473: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions
Subobject types - 37 PROTECTION - C-Type 3
- RFC 8400: Extensions to RSVP-TE for Label Switched Path (LSP) Egress Protection
Class Types or C-Types ‒ 38 PRIMARY_PATH_ROUTE
- RFC 4872: RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery
| Value |
Description |
Reference |
| 1 |
Type 1 Primary Path Route |
RFC 4872 |
Class Types or C-Types ‒ 42 DSBM IP ADDRESS
- Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager): Protocol for RSVP-based Admission Control over IEEE 802-style networks", Internet Draft, November 1997.
| Value |
Description |
Reference |
| 1 |
IPv4 |
Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager):
Protocol for RSVP-based Admission Control over IEEE
802-style networks", Internet Draft, November 1997. |
| 2 |
IPv6 |
Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager):
Protocol for RSVP-based Admission Control over IEEE
802-style networks", Internet Draft, November 1997. |
Class Types or C-Types ‒ 43 SBM_PRIORITY
- Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager): Protocol for RSVP-based Admission Control over IEEE 802-style networks", Internet Draft, November 1997.
| Value |
Description |
Reference |
| 1 |
default |
Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager):
Protocol for RSVP-based Admission Control over IEEE
802-style networks", Internet Draft, November 1997. |
Class Types or C-Types ‒ 44 DSBM TIMER INTERVALS
- Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager): Protocol for RSVP-based Admission Control over IEEE 802-style networks", Internet Draft, November 1997.
| Value |
Description |
Reference |
| 1 |
default |
Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager):
Protocol for RSVP-based Admission Control over IEEE
802-style networks", Internet Draft, November 1997. |
Class Types or C-Types ‒ 45 SBM_INFO
- Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager): Protocol for RSVP-based Admission Control over IEEE 802-style networks", Internet Draft, November 1997.
| Value |
Description |
Reference |
| 1 |
Media Type |
Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager):
Protocol for RSVP-based Admission Control over IEEE
802-style networks", Internet Draft, November 1997. |
Class Types or C-Types ‒ 50 S2L_SUB_LSP
- RFC 4875: Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs)
| Value |
Description |
Reference |
| 1 |
S2L_SUB_LSP_IPv4 |
RFC 4875 |
| 2 |
S2L_SUB_LSP_IPv6 |
RFC 4875 |
Class Types or C-Types ‒ 63 DETOUR
- RFC 4090: Fast Reroute Extensions to RSVP-TE for LSP Tunnels
Class Types or C-Types ‒ 64 CHALLENGE
- RFC 2747: RSVP Cryptographic Authentication
| Value |
Description |
Reference |
| 1 |
Type 1 Challenge Value |
RFC 2747 |
Class Types or C-Types ‒ 65 DIFF-SERV
- RFC 3270: Multi-Protocol Label Switching (MPLS) Support of Differentiated Services
| Value |
Description |
Reference |
| 1 |
Diff-Serv object for an E-LSP |
RFC 3270 |
| 2 |
Diff-Serv object for an L-LSP |
RFC 3270 |
Class Types or C-Types ‒ 66 CLASSTYPE
- RFC 4124: Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering
| Value |
Description |
Reference |
| 1 |
Type 1 |
RFC 4124 |
Class Types or C-Types ‒ 67 LSP_REQUIRED_ATTRIBUTES
- RFC 5420: Encoding of Attributes for MPLS LSP Establishment Using Resource Reservation Protocol Traffic Engineering (RSVP-TE)
Subobject bits are defined in RSVP TE Parameters.
| Value |
Description |
Reference |
| 1 |
LSP Required Attributes TLVs |
RFC 5420 |
Class Types or C-Types ‒ 120 UPSTREAM_FLOWSPEC
- RFC 6387: GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs)
Same values as FLOWSPEC object (C-Num 9)
| Value |
Description |
Reference |
| No registrations at this time. |
Class Types or C-Types ‒ 121 UPSTREAM_TSPEC
- RFC 6387: GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs)
Same values as SENDER_TSPEC object (C-Num 12)
| Value |
Description |
Reference |
| No registrations at this time. |
Class Types or C-Types ‒ 122 UPSTREAM_ADSPEC
- RFC 6387: GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs)
Same values as ADSPEC object (C-Num 13)
| Value |
Description |
Reference |
| No registrations at this time. |
Class Types or C-Types ‒ 128 NODE_CHAR
- RFC 2746: RSVP Operation Over IP Tunnels
Should be zero; ignored.
| Value |
Description |
Reference |
| No registrations at this time. |
Class Types or C-Types ‒ 129 SUGGESTED_LABEL
- RFC 3473: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions
Same values as RSVP_LABEL (C-Num 16)
| Value |
Description |
Reference |
| No registrations at this time. |
Class Types or C-Types ‒ 130 ACCEPTABLE_LABEL_SET
- RFC 3473: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions
Same values as LABEL_SET (C-Num 36)
| Value |
Description |
Reference |
| No registrations at this time. |
Class Types or C-Types ‒ 131 RESTART_CAP
- RFC 3473: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions
| Value |
Description |
Reference |
| 1 |
Type 1 Restart capabilities |
RFC 3473 |
Class Types or C-Types ‒ 132 SESSION-OF-INTEREST
- RFC 4860: Generic Aggregate Resource ReSerVation Protocol (RSVP) Reservations
| Value |
Description |
Reference |
| 1 |
GENERIC-AGG-IP4-SOI |
RFC 4860 |
| 2 |
GENERIC-AGG-IP6-SOI |
RFC 4860 |
Class Types or C-Types ‒ 133 LINK_CAPABILITY
- RFC 4974: Generalized MPLS (GMPLS) RSVP-TE Signaling Extensions in Support of Calls
| Value |
Description |
Reference |
| 1 |
(TE Link Capabilities) |
|
Subobject type ‒ 133 LINK_CAPABILITY ‒ TE Link Capabilities
- RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels
| Value |
Description |
Reference |
| 1 |
IPv4 address |
RFC 3209 |
| 2 |
IPv6 address |
RFC 3209 |
| 4 |
Unnumbered Interface ID |
RFC 3477 |
| 64 |
Maximum Reservable Bandwidth |
RFC 4201 |
| 65 |
Interface Switching
Capability Descriptor |
RFC 4202 |
Class Types or C-Types ‒ 134 Capability Object
- RFC 5063: Extensions to GMPLS Resource Reservation Protocol (RSVP) Graceful Restart
| Value |
Description |
Reference |
| 1 |
Capability Object |
RFC 5063 |
Class Types or C-Types ‒ 135 CONDITIONS
- RFC 9705: Refresh-Interval Independent RSVP Fast Reroute Facility Protection
| Value |
Description |
Reference |
| 1 |
CONDITIONS |
RFC 9705 |
Class Types or C-Types ‒ 161 RSVP_HOP_L2
- Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager): Protocol for RSVP-based Admission Control over IEEE 802-style networks", Internet Draft, November 1997.
| Value |
Description |
Reference |
| 1 |
IEEE Canonical Address |
Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager):
Protocol for RSVP-based Admission Control over IEEE
802-style networks", Internet Draft, November 1997. |
Class Types or C-Types ‒ 162 LAN_NHOP_L2
- Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager): Protocol for RSVP-based Admission Control over IEEE 802-style networks", Internet Draft, November 1997.
| Value |
Description |
Reference |
| 1 |
IEEE Canonical Address |
Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager):
Protocol for RSVP-based Admission Control over IEEE
802-style networks", Internet Draft, November 1997. |
Class Types or C-Types ‒ 163 LAN_NHOP_L3
- Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager): Protocol for RSVP-based Admission Control over IEEE 802-style networks", Internet Draft, November 1997.
| Value |
Description |
Reference |
| 1 |
IPv4 |
Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager):
Protocol for RSVP-based Admission Control over IEEE
802-style networks", Internet Draft, November 1997. |
| 2 |
IPv6 |
Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager):
Protocol for RSVP-based Admission Control over IEEE
802-style networks", Internet Draft, November 1997. |
Class Types or C-Types ‒ 164 LAN_LOOPBACK
- Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager): Protocol for RSVP-based Admission Control over IEEE 802-style networks", Internet Draft, November 1997.
| Value |
Description |
Reference |
| 1 |
IPv4 |
Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager):
Protocol for RSVP-based Admission Control over IEEE
802-style networks", Internet Draft, November 1997. |
| 2 |
IPv6 |
Yavatkar, R., et al, "SBM (Subnet Bandwidth Manager):
Protocol for RSVP-based Admission Control over IEEE
802-style networks", Internet Draft, November 1997. |
Class Types or C-Types ‒ 192 SESSION_ASSOC
- RFC 2746: RSVP Operation Over IP Tunnels
Should be zero, ignored.
| Value |
Description |
Reference |
| No registrations at this time. |
Class Types or C-Types ‒ 193 LSP_TUNNEL_INTERFACE_ID
- RFC 3477: Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE)
| Value |
Description |
Reference |
| 1 |
Forward/Reverse Interface ID |
RFC 3477 |
| 2 |
IPv4 interface identifier with target |
RFC 6107 |
| 3 |
IPv6 interface identifier with target |
RFC 6107 |
| 4 |
Unnumbered interface with target |
RFC 6107 |
Class Types or C-Types ‒ 194 USER_ERROR_SPEC
| Value |
Description |
Reference |
| 1 |
User-Defined Error |
RFC 5284 |
Class Types or C-Types ‒ 195 NOTIFY_REQUEST
- RFC 3473: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions
| Value |
Description |
Reference |
| 1 |
IPv4 Notify Request |
RFC 3473 |
| 2 |
IPv6 Notify Request |
RFC 3473 |
Class Types or C-Types ‒ 196 ADMIN_STATUS
- RFC 3473: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions
| Value |
Description |
Reference |
| 1 |
Type 1 Admin status |
RFC 3473 |
Class Types or C-Types ‒ 197 LSP_ATTRIBUTES
- RFC 5420: Encoding of Attributes for MPLS LSP Establishment Using Resource Reservation Protocol Traffic Engineering (RSVP-TE)
Subobject bits are defined in RSVP TE Parameters.
| Value |
Description |
Reference |
| 1 |
LSP Attributes TLVs |
RFC 5420 |
Class Types or C-Types ‒ 198 ALARM_SPEC
- RFC 4783: GMPLS - Communication of Alarm Information
Class Types or C-Types ‒ 199 ASSOCIATION
- RFC 4872: RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery
| Value |
Description |
Reference |
| 1 |
Type 1 IPv4 Association |
RFC 4872 |
| 2 |
Type 2 IPv6 Association |
RFC 4872 |
| 3 |
Type 3 IPv4 Extended Association |
RFC 6780 |
| 4 |
Type 4 IPv6 Extended Association |
RFC 6780 |
Class Types or C-Types ‒ 200 SECONDARY_EXPLICIT_ROUTE
Same C-Type values as EXPLICIT_ROUTE object
(C-Num 20) with the following additions:
| Value |
Description |
Reference |
| 2 |
P2MP SECONDARY_EXPLICIT_ROUTE |
RFC 4875 |
Subobject types ‒ 200 SECONDARY_EXPLICIT_ROUTE ‒ C-Type 1
For C-Type 1, the following additional Subobject
type is defined:
| Value |
Description |
Reference |
| 37 |
Protection |
RFC 4873 |
Class Types or C-Types ‒ 201 SECONDARY_RECORD_ROUTE
Same C-Type values as RECORD_ROUTE object
(C-Num 21) with the following additions:
| Value |
Description |
Reference |
| 2 |
P2MP SECONDARY_RECORD_ROUTE |
RFC 4875 |
Subobject types ‒ 201 SECONDARY_RECORD_ROUTE ‒ C-Type 1
For C-Type 1, the following additional
Subobject type is defined:
| Value |
Description |
Reference |
| 37 |
Protection |
RFC 4873 |
Class Types or C-Types ‒ 202 CALL ATTRIBUTES
- RFC 6001: Generalized MPLS (GMPLS) Protocol Extensions for Multi-Layer and Multi-Region Networks (MLN/MRN)
| Value |
Description |
Reference |
| 1 |
Call Attributes |
RFC 6001 |
Class Types or C-Types ‒ 203 REVERSE_LSP
- RFC 7551: RSVP-TE Extensions for Associated Bidirectional Label Switched Paths (LSPs)
| Value |
Description |
Reference |
| 1 |
REVERSE_LSP |
RFC 7551 |
Class Types or C-Types ‒ 204 S2L_SUB_LSP_FRAG
- RFC 8149: RSVP Extensions for Reoptimization of Loosely Routed Point-to-Multipoint Traffic Engineering Label Switched Paths (LSPs)
| Value |
Description |
Reference |
| 1 |
S2L_SUB_LSP_FRAG |
RFC 8149 |
Class Types or C-Types ‒ 205 FAST_REROUTE
- RFC 4090: Fast Reroute Extensions to RSVP-TE for LSP Tunnels
Class Types or C-Types ‒ 207 SESSION_ATTRIBUTE
- RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels
Class Types or C-Types ‒ 226 PACKETCABLE EXTENSIONS
| Value |
Description |
Reference |
| 1 |
Reverse-Rspec |
Anon, "PacketCable Dynamic Quality-of-Service
Specification", PKT-SP-DQOS-O01-991201, date unknown.
Available from |
| 2 |
Reverse-Session |
Anon, "PacketCable Dynamic Quality-of-Service
Specification", PKT-SP-DQOS-O01-991201, date unknown.
Available from |
| 3 |
Reverse-Sender-Template |
Anon, "PacketCable Dynamic Quality-of-Service
Specification", PKT-SP-DQOS-O01-991201, date unknown.
Available from |
| 4 |
Reverse-Sender-Tspec |
Anon, "PacketCable Dynamic Quality-of-Service
Specification", PKT-SP-DQOS-O01-991201, date unknown.
Available from |
| 5 |
Forward-Rspec |
Anon, "PacketCable Dynamic Quality-of-Service
Specification", PKT-SP-DQOS-O01-991201, date unknown.
Available from |
| 6 |
Component-Tspec |
Anon, "PacketCable Dynamic Quality-of-Service
Specification", PKT-SP-DQOS-O01-991201, date unknown.
Available from |
| 7 |
Resource-ID |
Anon, "PacketCable Dynamic Quality-of-Service
Specification", PKT-SP-DQOS-O01-991201, date unknown.
Available from |
| 8 |
Gate-ID |
Anon, "PacketCable Dynamic Quality-of-Service
Specification", PKT-SP-DQOS-O01-991201, date unknown.
Available from |
| 9 |
Commit-Entity |
Anon, "PacketCable Dynamic Quality-of-Service
Specification", PKT-SP-DQOS-O01-991201, date unknown.
Available from |
Class Types or C-Types ‒ 227 ATM_SERVICECLASS
- RFC 3496: Protocol Extension for Support of Asynchronous Transfer Mode (ATM) Service Class-aware Multiprotocol Label Switching (MPLS) Traffic Engineering
| Value |
Description |
Reference |
| 1 |
ATM Service class |
RFC 3496 |
Class Types or C-Types ‒ 228 CALL_OPS (ASON)
- RFC 3474: Documentation of IANA assignments for Generalized MultiProtocol Label Switching (GMPLS) Resource Reservation Protocol - Traffic Engineering (RSVP-TE) Usage and Extensions for Automatically Switched Optical Network (ASON)
| Value |
Description |
Reference |
| 1 |
Type 1 CALL_OPS |
RFC 3474 |
Class Types or C-Types ‒ 229 GENERALIZED_UNI
- RFC 3476: Documentation of IANA Assignments for Label Distribution Protocol (LDP), Resource ReSerVation Protocol (RSVP), and Resource ReSerVation Protocol-Traffic Engineering (RSVP-TE) Extensions for Optical UNI Signaling
| Value |
Description |
Reference |
| 1 |
Type 1 Generalized UNI |
RFC 3476 |
Subobject types
- RFC 3476: Documentation of IANA Assignments for Label Distribution Protocol (LDP), Resource ReSerVation Protocol (RSVP), and Resource ReSerVation Protocol-Traffic Engineering (RSVP-TE) Extensions for Optical UNI Signaling
Subobject subtypes ‒ 1 Source TNA
- RFC 3476: Documentation of IANA Assignments for Label Distribution Protocol (LDP), Resource ReSerVation Protocol (RSVP), and Resource ReSerVation Protocol-Traffic Engineering (RSVP-TE) Extensions for Optical UNI Signaling
Subobject subtypes ‒ 2 Destination TNA
Subobject subtypes ‒ 3 Diversity
- RFC 3476: Documentation of IANA Assignments for Label Distribution Protocol (LDP), Resource ReSerVation Protocol (RSVP), and Resource ReSerVation Protocol-Traffic Engineering (RSVP-TE) Extensions for Optical UNI Signaling
| Value |
Description |
Reference |
| 1 |
Diversity |
RFC 3476 |
Subobject subtypes ‒ 4 Egress Label
- RFC 3476: Documentation of IANA Assignments for Label Distribution Protocol (LDP), Resource ReSerVation Protocol (RSVP), and Resource ReSerVation Protocol-Traffic Engineering (RSVP-TE) Extensions for Optical UNI Signaling
Subobject subtypes ‒ 5 Service level
- RFC 3476: Documentation of IANA Assignments for Label Distribution Protocol (LDP), Resource ReSerVation Protocol (RSVP), and Resource ReSerVation Protocol-Traffic Engineering (RSVP-TE) Extensions for Optical UNI Signaling
| Value |
Description |
Reference |
| 1 |
Service level |
RFC 3476 |
Class Types or C-Types ‒ 230 CALL_ID
- RFC 3474: Documentation of IANA assignments for Generalized MultiProtocol Label Switching (GMPLS) Resource Reservation Protocol - Traffic Engineering (RSVP-TE) Usage and Extensions for Automatically Switched Optical Network (ASON)
| Value |
Description |
Reference |
| 1 |
Operator specific |
RFC 3474 |
| 2 |
Globally unique |
RFC 3474 |
Subobject types ‒ 2 Globally unique
- RFC 3474: Documentation of IANA assignments for Generalized MultiProtocol Label Switching (GMPLS) Resource Reservation Protocol - Traffic Engineering (RSVP-TE) Usage and Extensions for Automatically Switched Optical Network (ASON)
| Value |
Description |
Reference |
| 0x01 |
Source LSR address is 4-bytes |
RFC 3474 |
| 0x02 |
Source LSR address is 16-bytes |
RFC 3474 |
| 0x03 |
Source LSR address is 20-bytes |
RFC 3474 |
| 0x04 |
Source LSR address is 6-bytes |
RFC 3474 |
| 0x7f |
the source LSR address has the
length defined by the vendor |
RFC 3474 |
Class Types or C-Types ‒ 231 3GPP2_Object
Class Types or C-Types ‒ 232 EXCLUDE_ROUTE
- RFC 4874: Exclude Routes - Extension to Resource ReserVation Protocol-Traffic Engineering (RSVP-TE)
| Value |
Description |
Reference |
| 1 |
EXCLUDE_ROUTE |
|
Class Types or C-Types ‒ 248 PCN
- RFC 7417: Extensions to Generic Aggregate RSVP for IPv4 and IPv6 Reservations over Pre-Congestion Notification (PCN) Domains
| Value |
Description |
Reference |
| 1 |
RSVP-AGGREGATE-IPv4-PCN-request |
RFC 7417 |
| 2 |
RSVP-AGGREGATE-IPv6-PCN-request |
RFC 7417 |
| 3 |
RSVP-AGGREGATE-IPv4-PCN-response |
RFC 7417 |
| 4 |
RSVP-AGGREGATE-IPv6-PCN-response |
RFC 7417 |
Virtual Destination Ports
- RFC 2207: RSVP Extensions for IPSEC Data Flows
| Range |
Registration Procedures |
Note |
| 0 |
Reserved |
Illegal Value |
| 1-10 |
Reserved |
Contact RFC 2207 Authors |
| 11-8191 |
Not Defined |
See Section 5 of RFC 2207 |
| 8192-65535 |
Dynamic |
|
| Value |
Name |
Description |
Reference |
| No registrations at this time. |
Error Codes and Globally-Defined Error Value Sub-Codes
- RFC 3936: Procedures for Modifying the Resource reSerVation Protocol (RSVP)
An Error Code is an 8-bit quantity that appears in an ERROR_SPEC
object to broadly define an error condition. With each Error Code
there may be a 16-bit Error Value that further specifies the cause
of the error. Error Values may be globally defined, in which case
the sub-code component is assigned by IANA RFC 2205.
Globally defined Error Values are assigned by Standards Action.
The following list extends the basic list of Error Codes and Values that
are defined in RFC 2205.
| Range |
Registration Procedures |
| 0-239 |
Standards Action |
| 240-251 |
Expert Review |
| 252-255 |
Reserved for Private Use |
Sub-Codes ‒ 1 Admission Control Failure
- RFC 2205: Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
- RFC 5946: Resource Reservation Protocol (RSVP) Extensions for Path-Triggered RSVP Receiver Proxy
The sixteen bits of the Error Value field are
ssur cccc cccc cccc
as defined in RFC 2205
The following globally-defined sub-codes may appear in the low-
order 12 bits when ssur = 0000:
| Value |
Description |
Reference |
| 1 |
Delay bound cannot be met |
RFC 2205 |
| 2 |
Requested bandwidth unavailable |
RFC 2205 |
| 3 |
MTU in flowspec larger than
interface MTU |
RFC 2205 |
| 4 |
LSP Admission Failure |
RFC 4872 |
| 5 |
Bad Association Type |
RFC 4872 |
| 6 |
Reverse LSP Failure |
RFC 7551 |
Sub-Codes ‒ 2 Policy Control Failure
- RFC 2205: Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
- RFC 5946: Resource Reservation Protocol (RSVP) Extensions for Path-Triggered RSVP Receiver Proxy
This Error Code has the following globally-defined Error Value sub-codes:
| Value |
Description |
Reference |
| 0 |
Information reporting |
RFC 2750 |
| 1 |
Warning |
RFC 2750 |
| 2 |
Reason unknown |
RFC 2750 |
| 3 |
Generic Policy Rejection |
RFC 2750 |
| 4 |
Quota or Accounting violation |
RFC 2750 |
| 5 |
Flow was preempted |
RFC 2750 |
| 6 |
Previously installed policy expired
(not refreshed) |
RFC 2750 |
| 7 |
Previous policy data was replaced &
caused rejection |
RFC 2750 |
| 8 |
Policies could not be merged
(multicast) |
RFC 2750 |
| 9 |
PDP down or non functioning |
RFC 2750 |
| 10 |
Third Party Server (e.g., Kerberos)
unavailable |
RFC 2750 |
| 11 |
POLICY_DATA object has bad syntax |
RFC 2750 |
| 12 |
POLICY_DATA object failed Integrity
Check |
RFC 2750 |
| 13 |
POLICY_ELEMENT object has bad syntax |
RFC 2750 |
| 14 |
Mandatory PE Missing (Empty PE is in
the PD object) |
RFC 2750 |
| 15 |
PEP Out of resources to handle
policies. |
RFC 2750 |
| 16 |
PDP encountered bad RSVP objects or
syntax |
RFC 2750 |
| 17 |
Service type was rejected |
RFC 2750 |
| 18 |
Reservation Style was rejected |
RFC 2750 |
| 19 |
FlowSpec was rejected (too large) |
RFC 2750 |
| 20 |
Hard Pre-empted |
RFC 4872 |
| 21 |
SRLG Recording Rejected |
RFC 8001 |
| 22-99 |
Unassigned |
|
| 100 |
Unauthorized sender |
RFC 3476 |
| 101 |
Unauthorized receiver |
RFC 3476 |
| 102 |
ERR_PARTIAL_PREEMPT |
RFC 4495 |
| 103 |
Inter-domain policy failure |
RFC 5151 |
| 104 |
Inter-domain explicit route rejected |
RFC 5151 |
Sub-Codes ‒ 12 Service preempted
- RFC 2205: Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
For this Error Code, the 16 bits of the Error Value field are:
ssur cccc cccc cccc
Here the high-order bits ssur are as defined under Error Code
01. The globally-defined sub-codes that may appear in the low-
order 12 bits when ssur = 0000 are to be defined in the future.
| Value |
Description |
Reference |
| No registrations at this time. |
Sub-Codes ‒ 21 Traffic Control Error
- RFC 2205: Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
For this Error Code, the 16 bits of the Error Value field are:
ss00 cccc cccc cccc
Here the high-order bits ss are as defined under Error Code 01.
The following globally-defined sub-codes may appear in the low
order 12 bits (cccc cccc cccc) when ss = 00:
Sub-Codes ‒ 24 Routing Problem
- RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels
This Error Code has the following globally-defined Error Value sub-codes:
| Value |
Description |
Reference |
| 1 |
Bad EXPLICIT_ROUTE object |
RFC 3209 |
| 2 |
Bad strict node |
RFC 3209 |
| 3 |
Bad loose node |
RFC 3209 |
| 4 |
Bad initial subobject |
RFC 3209 |
| 5 |
No route available toward destination |
RFC 3209 |
| 6 |
Unacceptable label value |
RFC 3209 |
| 7 |
RRO indicated routing loops |
RFC 3209 |
| 8 |
MPLS being negotiated, but a non-RSVP-capable router stands in the path |
RFC 3209 |
| 9 |
MPLS label allocation failure |
RFC 3209 |
| 10 |
Unsupported L3PID |
RFC 3209 |
| 11 |
Label Set |
RFC 3473 |
| 12 |
Switching Type |
RFC 3473 |
| 13 |
Unassigned |
RFC 3473 |
| 14 |
Unsupported Encoding |
RFC 3473 |
| 15 |
Unsupported Link Protection |
RFC 3473 |
| 16 |
Unknown Interface Index |
RFC 3477 |
| 17 |
Unsupported LSP Protection |
RFC 4872 |
| 18 |
PROTECTION object not applicable |
RFC 4872 |
| 19 |
Bad PRIMARY_PATH_ROUTE object |
RFC 4872 |
| 20 |
PRIMARY_PATH_ROUTE object not applicable |
RFC 4872 |
| 21 |
LSP Segment Protection Failed |
RFC 4873 |
| 22 |
Re-routing limit exceeded |
RFC 4920 |
| 23 |
Unable to Branch |
RFC 4875 |
| 24 |
Unsupported LSP Integrity |
RFC 4875 |
| 25 |
P2MP Re-Merge Detected |
RFC 4875 |
| 26 |
P2MP Re-Merge Parameter Mismatch |
RFC 4875 |
| 27 |
ERO Resulted in Re-Merge |
RFC 4875 |
| 28 |
Contiguous LSP type not supported |
RFC 5151 |
| 29 |
ERO conflicts with inter-domain signaling method |
RFC 5151 |
| 30 |
Stitching unsupported |
RFC 5150 |
| 31 |
Unknown PCE-ID for PKS expansion |
RFC 5553 |
| 32 |
Unreachable PCE for PKS expansion |
RFC 5553 |
| 33 |
Unknown Path Key for PKS expansion |
RFC 5553 |
| 34 |
ERO too large for MTU |
RFC 5553 |
| 35 |
Unknown Endpoint |
RFC 6005 |
| 36 |
Unsupported Diversity Identifier Type |
RFC 8390 |
| 37-63 |
Unassigned |
|
| 64 |
Unsupported Exclude Route Subobject Type |
RFC 4874 |
| 65 |
Inconsistent Subobject |
RFC 4874 |
| 66 |
Local Node in Exclude Route |
RFC 4874 |
| 67 |
Route Blocked by Exclude Route |
RFC 4874 |
| 68 |
XRO Too Complex |
RFC 4874 |
| 69 |
EXRS Too Complex |
RFC 4874 |
| 70 |
TE link label usage failure |
RFC 8577 |
| 71 |
Label stack imposition failure |
RFC 8577 |
| 72-99 |
Unassigned |
|
| 100 |
Diversity not available |
RFC 3476 |
| 101 |
Service level not available |
RFC 3476 |
| 102 |
Invalid/Unknown connection ID |
RFC 3476 |
| 103 |
No route available toward
source (ASON) |
RFC 3474 |
| 104 |
Unacceptable interface ID (ASON) |
RFC 3474 |
| 105 |
Invalid/unknown call ID (ASON) |
RFC 3474 |
| 106 |
Invalid SPC interface ID/label (ASON) |
RFC 3474 |
| 107 |
Unsupported WavelengthSelection symmetry value |
RFC 7689 |
| 108 |
Unsupported Wavelength Assignment value |
RFC 7689 |
Sub-Codes ‒ 25 Notify Error
- RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels
This Error Code has the following globally-defined Error Value sub-codes:
Sub-Codes ‒ 27 Diffserv Error
- RFC 3270: Multi-Protocol Label Switching (MPLS) Support of Differentiated Services
This Error Code has the following globally-defined Error Value sub-codes:
| Value |
Description |
Reference |
| 1 |
Unexpected DIFFSERV object |
RFC 3270 |
| 2 |
Unsupported PHB |
RFC 3270 |
| 3 |
Invalid EXP<-->PHB mapping |
RFC 3270 |
| 4 |
Unsupported PSC |
RFC 3270 |
| 5 |
Per-LSP context allocation failure |
RFC 3270 |
Sub-Codes ‒ 28 Diff-Serv-aware TE Error
- RFC 4124: Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering
This Error Code has the following globally-defined Error Value sub-codes:
| Value |
Description |
Reference |
| 1 |
Unexpected CLASSTYPE object |
RFC 4124 |
| 2 |
Unsupported Class-Type |
RFC 4124 |
| 3 |
Invalid Class-Type value |
RFC 4124 |
| 4 |
Class-Type and setup priority do
not form a configured TE-Class |
RFC 4124 |
| 5 |
Class-Type and holding priority
do not form a configured TE-Class |
RFC 4124 |
| 6 |
Class-Type and setup priority do
not form a configured TE-Class AND
Class-Type and holding priority do
not form a configured TE-Class |
RFC 4124 |
| 7 |
Inconsistency between signaled
PSC and signaled Class-Type |
RFC 4124 |
| 8 |
Inconsistency between signaled
PHBs and signaled Class-Type |
RFC 4124 |
Sub-Codes ‒ 31 Alarms
- RFC 4783: GMPLS - Communication of Alarm Information
The Error Value sub-codes for this Error Code
have values and meanings identical to the values
and meanings defined in the IANAItuProbableCause
Textual Convention of IANA-ITU-ALARM-TC-MIB
in the Alarm MIB RFC 3877.
| Value |
Description |
Reference |
| No registrations at this time. |
Sub-Codes ‒ 32 Call Management
- RFC 4974: Generalized MPLS (GMPLS) RSVP-TE Signaling Extensions in Support of Calls
This Error Code has the following globally-defined Error Value sub-codes:
Sub-Codes ‒ 33 User Error Spec
This Error Code has the following globally-defined Error Value sub-codes:
| Value |
Description |
Reference |
| 0 |
Further details in User Error Spec |
RFC 5284 |
Sub-Codes ‒ 34 Reroute
- RFC 5710: PathErr Message Triggered MPLS and GMPLS LSP Reroutes
This Error Code has the following globally-defined Error Value sub-codes:
| Value |
Description |
Reference |
| 0 |
Generic LSP reroute request |
RFC 5710 |
| 1 |
Reroute Request Soft Preemption |
RFC 5712 |
| 2-32767 |
Unassigned |
|
| 32768-65535 |
Reserved for Private Use |
RFC 5710 |
Sub-Codes ‒ 35 Handover Procedure Failure
- RFC 5852: RSVP-TE Signaling Extension for LSP Handover from the Management Plane to the Control Plane in a GMPLS-Enabled Transport Network
This Error Code has the following globally-defined Error Value sub-codes:
| Value |
Description |
Reference |
| 0 |
Unassigned |
|
| 1 |
Cross-connection mismatch |
RFC 5852 |
| 2 |
Other failure |
RFC 5852 |
| 3-65535 |
Unassigned |
|
Sub-Codes ‒ 36 Unrecoverable Receiver Proxy Error
- RFC 5946: Resource Reservation Protocol (RSVP) Extensions for Path-Triggered RSVP Receiver Proxy
The sixteen bits of the Error Value field are defined in RFC 5946
| Value |
Description |
Reference |
| No registrations at this time. |
Sub-Codes ‒ 37 RSVP over MPLS Problem
- RFC 6016: Support for the Resource Reservation Protocol (RSVP) in Layer 3 VPNs
This Error Code has the following globally-defined Error Value sub-codes:
| Value |
Description |
Reference |
| 1 |
RSVP_HOP not reachable across VPN |
RFC 6016 |
Sub-Codes ‒ 38 LSP Hierarchy Issue
- RFC 6107: Procedures for Dynamically Signaled Hierarchical Label Switched Paths
This Error Code has the following globally-defined Error Value sub-codes:
| Value |
Description |
Reference |
| 1 |
Link advertisement not supported |
RFC 6107 |
| 2 |
Link advertisement not allowed by policy |
RFC 6107 |
| 3 |
TE link creation not supported |
RFC 6107 |
| 4 |
TE link creation not allowed by policy |
RFC 6107 |
| 5 |
Routing adjacency creation not supported |
RFC 6107 |
| 6 |
Routing adjacency creation not allowed by policy |
RFC 6107 |
| 7 |
Bundle creation not supported |
RFC 6107 |
| 8 |
Bundle creation not allowed by policy |
RFC 6107 |
| 9 |
Hierarchical LSP not supported |
RFC 6107 |
| 10 |
LSP stitching not supported |
RFC 6107 |
| 11 |
Link address type or family not supported |
RFC 6107 |
| 12 |
IGP instance unknown |
RFC 6107 |
| 13 |
IGP instance advertisement not allowed by policy |
RFC 6107 |
| 14 |
Component link identifier not valid |
RFC 6107 |
| 15 |
Unsupported component link identifier address
family |
RFC 6107 |
| 16 |
Component link identifier missing |
RFC 6107 |
Sub-Codes ‒ 39 VCAT Call Management
- RFC 6344: Operating Virtual Concatenation (VCAT) and the Link Capacity Adjustment Scheme (LCAS) with Generalized Multi-Protocol Label Switching (GMPLS)
This Error Code has the following globally-defined Error Value sub-codes:
| Value |
Description |
Reference |
| 0 |
Unassigned |
|
| 1 |
VCG signal type not supported |
RFC 6344 |
| 2 |
LCAS option not supported |
RFC 6344 |
| 3 |
Max number of VCGs exceeded |
RFC 6344 |
| 4 |
Max number of VCG members exceeded |
RFC 6344 |
| 5 |
LSP Type incompatible with VCAT call |
RFC 6344 |
| 6 |
Unknown LCR (LCAS required) value |
RFC 6344 |
| 7 |
Unknown or unsupported ACTION |
RFC 6344 |
| 8-65535 |
Unassigned |
|
Sub-Codes ‒ 40 OAM Problem
- RFC 7260: GMPLS RSVP-TE Extensions for Operations, Administration, and Maintenance (OAM) Configuration
This Error Code has the following globally-defined Error Value sub-codes:
Sub-Codes ‒ 44 FRR Bypass Assignment Error
- RFC 8271: Updates to the Resource Reservation Protocol for Fast Reroute of Traffic Engineering GMPLS Label Switched Paths (LSPs)
This Error Code has the following globally-defined Error Value sub-codes:
| Value |
Description |
Reference |
| 0 |
Bypass Assignment Cannot Be Used |
RFC 8271 |
| 1 |
Bypass Tunnel Not Found |
RFC 8271 |
| 2 |
One-to-one Bypass Already In-use |
RFC 8271 |
| 3-65535 |
Unassigned |
|
Capability Object values
- RFC 5063: Extensions to GMPLS Resource Reservation Protocol (RSVP) Graceful Restart
| Bit Number |
Hex Value |
Name |
Reference |
| 31 |
0x0001 |
RecoveryPath Srefresh Capable (S) |
RFC 5063 |
| 30 |
0x0002 |
RecoveryPath Desired (R) |
RFC 5063 |
| 29 |
0x0004 |
RecoveryPath Transmit Enabled (T) |
RFC 5063 |
| 28 |
0x0008 |
RI-RSVP Capable (I) |
RFC 8370, Section 3 |
| 27 |
0x0010 |
Per-Peer Flow-Control Capable (F) |
RFC 8370, Section 4 |
| 26-0 |
|
Unassigned |
|
Call Attributes TLV
- RFC 6001: Generalized MPLS (GMPLS) Protocol Extensions for Multi-Layer and Multi-Region Networks (MLN/MRN)
Call Attributes Flags
- RFC 6001: Generalized MPLS (GMPLS) Protocol Extensions for Multi-Layer and Multi-Region Networks (MLN/MRN)
| Bit Number |
32-Bit Value |
Name |
Reference |
| 0 |
0x80000000 |
Call Inheritance Flag |
RFC 6001 |
| 1-31 |
|
Unassigned |
|
VCAT Elementary Signal Registry
- RFC 6344: Operating Virtual Concatenation (VCAT) and the Link Capacity Adjustment Scheme (LCAS) with Generalized Multi-Protocol Label Switching (GMPLS)
VCAT VCG Operation Actions
- RFC 6344: Operating Virtual Concatenation (VCAT) and the Link Capacity Adjustment Scheme (LCAS) with Generalized Multi-Protocol Label Switching (GMPLS)
| Value |
Meaning |
Reference |
| 0 |
No VCG ID (set up call prior to VCG creation) |
RFC 6344 |
| 1 |
New VCG for Call |
RFC 6344 |
| 2 |
Modification of Number of Members (no change in VCG ID) |
RFC 6344 |
| 3 |
Remove VCG from Call |
RFC 6344 |
| 4-255 |
Unassigned |
|
CONDITIONS Object Flags
- RFC 9705: Refresh-Interval Independent RSVP Fast Reroute Facility Protection
| Bit Number |
32-Bit Value |
Name |
Reference |
| 0-30 |
|
Unassigned |
|
| 31 |
0x0001 |
Merge-point |
RFC 9705 |
Contact Information