How do you secure RSVP-TE messages and reservations against attacks and misconfigurations in IP networks?

1 RSVP-TE Basics

RSVP-TE stands for Resource Reservation Protocol-Traffic Engineering. It is an extension of the RSVP protocol, which is used to request and allocate resources for specific traffic flows in IP networks. RSVP-TE adds traffic engineering capabilities, such as explicit route selection, constraint-based path computation, and fast rerouting. RSVP-TE works by sending messages along the path of a traffic flow, called a label switched path (LSP), to reserve bandwidth and establish labels for forwarding packets. The messages include PATH, RESV, PATHERR, RESVERR, PATHTEAR, and RESVTEAR.

2 RSVP-TE Security Risks

RSVP-TE messages and reservations are vulnerable to various attacks and misconfigurations that can affect the network's availability, integrity, and confidentiality. Common risks include denial of service (DoS) attacks, reservation hijacking, reservation tampering, and information disclosure. An attacker can flood the network with fake or excessive RSVP-TE messages to consume bandwidth and processing resources, or modify or spoof messages to divert traffic to a malicious node. Additionally, an attacker can alter or delete RSVP-TE messages to disrupt the normal operation of RSVP-TE, or intercept messages to obtain sensitive information about the network topology, traffic patterns, or resource availability.

3 RSVP-TE Security Measures

To protect RSVP-TE messages and reservations from attacks and misconfigurations, you need to implement security measures at different layers of the network. At the network layer, IPsec can be used to encrypt and authenticate RSVP-TE messages between routers, while firewalls or access control lists (ACLs) can be used to filter and limit the source and destination of RSVP-TE messages. At the MPLS layer, MPLS Transport Profile (MPLS-TP) can provide protection against link or node failures, isolation of traffic flows, and end-to-end integrity checks. Additionally, MPLS security labels can be used to identify and classify the LSPs. At the application layer, authentication, authorization, and accounting (AAA) mechanisms can be used to control and monitor access and usage of RSVP-TE. Network management systems (NMS) or traffic engineering tools can also be used to configure and verify RSVP-TE parameters and reservations.

4 RSVP-TE Security Best Practices

In addition to security measures, you can also follow best practices to enhance the security of RSVP-TE messages and reservations in your network. These include using strong and consistent encryption and authentication methods, such as IPsec with AES and HMAC-SHA; using separate and dedicated LSPs for RSVP-TE control traffic and data traffic; employing dynamic and adaptive routing algorithms for RSVP-TE path computation, like CSPF or TE-FRR; refreshing and tearing down RSVP-TE messages and reservations periodically; and implementing auditing and logging mechanisms to keep track of the origin, destination, duration, and status of each traffic flow, alerting any suspicious or abnormal events.

5 RSVP-TE Security Challenges

Despite the security measures and best practices that can be applied to RSVP-TE messages and reservations, there are still some challenges that must be addressed in your network. For example, as the size and complexity of your network grows, so does the number and frequency of RSVP-TE messages and reservations - leading to increased overhead and latency of the protocol, as well as more resources and coordination among routers. Additionally, when connecting with other networks that use different protocols or standards for traffic engineering or security (e.g. DiffServ or GMPLS), it is important to ensure compatibility and coordination of RSVP-TE with them in order to prevent conflicts or inefficiencies. Finally, when adapting your network to changing traffic demands or requirements (e.g. new applications or services), it is essential to ensure the flexibility and robustness of RSVP-TE, allowing dynamic and efficient allocation and adjustment of resources.

6 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?