Aggregation of Resource ReSerVation Protocol (RSVP) Reservations over MPLS TE/DS-TE Tunnels

Voir toute la rfc dans une seule page

Télécharger le PDF

RFC 4804         RSVP Aggregation over MPLS TE Tunnels     February 2007


                    An E2E RSVP reservation may be a per-flow
                    reservation.  Alternatively, the E2E reservation may
                    itself be an aggregate reservation of various types
                    (e.g., Aggregate IP reservation, Aggregate IPsec
                    reservation).  See Section 5 and 6 for more details
                    on the types of E2E RSVP reservations.  As per
                    regular RSVP operations, E2E RSVP reservations are
                    unidirectional.

   Head-end         This is the Label Switch Router responsible for
                    establishing, maintaining, and tearing down a given
                    TE tunnel.

   Tail-end         This is the Label Switch Router responsible for
                    terminating a given TE tunnel.

   Transit LSR      This is a Label Switch Router that is on the path of
                    a given TE tunnel and is neither the Head-end nor
                    the Tail-end.

4.  Operations of RSVP Aggregation over TE with Pre-established Tunnels

   [RSVP-AGG] and [RSVP-GEN-AGG] support operations both in the case
   where aggregate RSVP reservations are pre-established and where
   Aggregators and Deaggregators have to dynamically discover each other
   and dynamically establish the necessary aggregate RSVP reservations.

   Similarly, RSVP Aggregation over TE tunnels could operate both in the
   case where the TE tunnels are pre-established and where the tunnels
   need to be dynamically established.

   In this document we provide a detailed description of the procedures
   in the case where TE tunnels are already established.  These
   procedures are based on those defined in [LSP-HIER].  The routing
   aspects discussed in Section 3 of [LSP-HIER] are not relevant here
   because those aim at allowing the constraint based routing of end-
   to-end TE LSPs to take into account the (aggregate) TE tunnels.  In
   the present document, the end-to-end RSVP reservations to be
   aggregated over the TE tunnels rely on regular SPF routing.  However,
   as already mentioned in [LSP-HIER], we note that a TE tunnel may be
   advertised into IS-IS or OSPF, to be used in normal SPF by nodes
   upstream of the Aggregator.  This would affect SPF routing and thus
   routing of end-to-end RSVP reservations.  The control of aggregation
   boundaries discussed in Section 6 of [LSP-HIER] is also not relevant
   here.  This uses information exchanged in GMPLS protocols to
   dynamically discover the aggregation boundary.  In this document, TE
   tunnels are pre-established, so that the aggregation boundary can be
   easily inferred.  The signaling aspects discussed in Section 6.2 of



Faucheur                    Standards Track                     [Page 8]