The Resource Reservation Protocol (RSVP) is designed for the integrated services model, and reserves resources for nodes along a path. This bandwidth reservation capability makes RSVP-TE a suitable signaling protocol for establishing MPLS TE paths.
RSVP supports the following resource reservation styles:
- Fixed Filter (FF) style: creates an exclusive reservation for each sender. A sender does not share its resource reservation with other senders, and each CR-LSP on a link has a separate resource reservation.
- Shared Explicit (SE) style: creates a single reservation for a series of selected upstream senders. CR-LSPs on a link share the same resource reservation.
RSVP key authentication can prohibit an unauthorized node from setting up the RSVP neighbor relationship with the local node and prevent packet spoofing. Key authentication cannot prevent replay attacks. Authentication enhancements are used to prevent replay attacks. RSVP authentication enhancements add the authentication lifetime, handshake, and message window mechanisms to enhance RSVP security. The enhancements also improve RSVP's capability to verify neighbor relationships in a harsh network environment, such as a congested network.
In MSDP, the unicast route for the RPF check can be an IGP route or a BGP route. MBGP only separates the unicast routing table and the multicast routing table through the related address family to support different unicast topologies and multicast topologies. Unicast and multicast can adopt the same topology.
Compared with conventional Extract-Transform-Load (ETL), Loader has the following advantage and disadvantage:
1. Advantage:
Loader uses a MapReduce-based parallel computing architecture as the underlying architecture, which delivers a faster data processing speed than ETL.
2. Disadvantage:
Compared with ETL, Loader focuses more on the data import and export function of FusionInsight Hadoop and is weak in data conversion.
If you have more questions, you can seek help from following ways:
