RFC 3209:RSVP-TE: Extensions to RSVP for LSP Tunne...
RFC-Ref

network


Click on the red underlined text to get to the source

... RSVP for establishing label switched paths (LSPs) in MPLS networks. Several of the new features described in this document were motivated ...
... LSP tunnels allow the implementation of a variety of policies related to network performance optimization. For example, LSP tunnels can be ...
... performance optimization. For example, LSP tunnels can be automatically or manually routed away from network failures, congestion, and bottlenecks. Furthermore, multiple parallel LSP tunnels ...
... traffic engineering (that is, performance optimization of operational networks) is expected to be an important application of this specification, the extended RSVP protocol can be ...
... QoS and policy requirements, taking into consideration the prevailing network state. In general, path computation can be control-driven or data-driven. The mechanisms, ...
... domain can control the path through which traffic traverses from itself, through the MPLS network, to an egress node. Explicit routing ...
... node. Explicit routing can be used to optimize the utilization of network resources and enhance traffic oriented performance characteristics ...


... LABEL_REQUEST object indicates that a label binding for this path is requested and also provides an indication of the network layer protocol that is to be carried over this path. The reason for this is that the network layer protocol sent down an LSP ...
... requested and also provides an indication of the network layer protocol that is to be carried over this path. The reason for this is that the network layer protocol sent down an LSP cannot be assumed to be IP ...
... QoS requirements, or that makes efficient use of network resources, or that satisfies some policy criteria, the node can decide to use the route ...
... notification from the network concerning changes to the routing path. The RECORD_ROUTE ...
... and the paths taken by the senders can converge and diverge at any point in the network topology. When Path messages have differing EXPLICIT_ROUTE objects ...
... In general, it is highly desirable not to disrupt traffic, or adversely impact network operations while TE tunnel rerouting is in ...
... arise because the old and new LSP tunnels might compete with each other for resources on network segments which they have in common. Depending on availability of resources, this competition can cause ...


... label binding for this path is requested and provides an indication of the network layer protocol that is to be carried over this path. This permits non-IP network layer protocols ...
... of the network layer protocol that is to be carried over this path. This permits non-IP network layer protocols to be sent down an LSP. ...
... An explicit route is a particular path in the network topology. Typically, the explicit route is determined by a node ...
... node and its preceding node MUST include only network nodes from the strict node and its preceding abstract ...
... node and its preceding node MAY include other network nodes that are not part of the strict node or its ...
... unicast, host address. Any network-reachable interface address ...
... sender or receiver. Any path change (due to network topology changes) will be reported. ...
... node to the destination. This is useful for network management. A received Path message ...
... destinations. The second class of forwarding loop is the permanent loop, which normally results from network mis- configuration. ...


... Wroclawski, J., "Specification of the Controlled-Load Network Element Service", RFC 2211prop, September 1997. ...


... Daniel O. Awduche Movaz Networks, Inc. 7926 Jones Branch Drive, Suite 615 McLean, VA 22102 ...
... Lou Berger Movaz Networks, Inc. 7926 Jones Branch Drive, Suite 615 McLean, VA 22102 ...
... Der-Hwa Gan Juniper Networks, Inc. 385 Ravendale Drive Mountain View, CA ...
... Tony Li Procket Networks 3910 Freedom Circle, Ste. 102A Santa Clara CA ...



Google
Web
RFC-Ref