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

MPLS


Click on the red underlined text to get to the source

... Section 2.9 of the MPLS architecture [2] defines a label distribution protocol as a set of procedures by which one Label Switched Router ...
... LSR) informs another of the meaning of labels used to forward traffic between and through them. The MPLS architecture does not assume a single label distribution protocol. This document is a ...
... RSVP for establishing label switched paths (LSPs) in MPLS networks. Several of the new features described in this document were motivated ...
... by the requirements for traffic engineering over MPLS (see [3]). In particular, the extended RSVP ...
... 2] can associate labels with RSVP flows. When MPLS and RSVP are combined, the definition of a flow ...
... explicitly routed path. Using this object, the paths taken by label-switched RSVP-MPLS flows can be pre-determined, independent of conventional IP routing ...
... LSPs, a node at the ingress edge of an MPLS domain can control the path through which traffic ...
... domain can control the path through which traffic traverses from itself, through the MPLS network, to an egress node. Explicit routing ...
... concatenation of one or more label switched hops, allowing a packet to be forwarded by swapping labels from an MPLS node to another MPLS node ...
... labels from an MPLS node to another MPLS node. For a more precise definition see [2 ...


... transport-layer protocol." However, when RSVP and MPLS are combined, a flow or session can be defined with ...
... To create an LSP tunnel, the first MPLS node on the path -- that is, the sender ...
... header, which simply identifies the higher layer protocol as MPLS. If the sender ...


... The contents of a LABEL is a single label, encoded in 4 octets. Each generic MPLS label is an unsigned integer in the range 0 through ...
... unsigned integer in the range 0 through 1048575. Generic MPLS labels and FR labels are encoded right aligned in 4 octets ...
... In MPLS a node may support multiple label spaces, perhaps associating a unique space with each incoming interface ...
... error code "Routing problem" and the error value "MPLS label allocation failure." This includes the case where a label range has been specified and a label cannot be allocated from ...
... error code "Routing problem" and the error value "MPLS being negotiated, but a non-RSVP capable router stands in ...
... routing loops 8 MPLS being negotiated, but a non-RSVP-capable router ...
... stands in the path 9 MPLS label allocation failure 10 Unsupported L3PID ...


... RRO indicated routing loops 8 MPLS being negotiated, but a non-RSVP-capable router ...
... router stands in the path 9 MPLS label allocation failure 10 Unsupported L3PID ...


... Awduche, D., Malcolm, J., Agogbua, J., O'Dell and J. McManus, "Requirements for Traffic Engineering over MPLS", RFC 2702, September 1999. ...
... Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., Farinacci, D., Li, T. and A. Conta, "MPLS Label Stack Encoding", RFC 3032prop, January 2001. ...



Google
Web
RFC-Ref