RFC 3031:Multiprotocol Label Switching Architectur...
RFC-Ref

architecture


Click on the red underlined text to get to the source

... This document specifies the architecture for Multiprotocol Label Switching (MPLS). ...


... In the MPLS architecture, the decision to bind a particular label L to a particular FEC ...
... THE ARCHITECTURE DOES NOT ASSUME THAT THERE IS ONLY A SINGLE LABEL DISTRIBUTION PROTOCOL. In fact, a number of different label distribution protocols are being standardized. Existing protocols ...
... The MPLS architecture allows an LSR to explicitly request, from its next hop ...
... The MPLS architecture also allows an LSR to distribute bindings to ...
... binding to label distribution peer Ru2. Whether or not L1 == L2 is not determined by the architecture; this is a local matter. ...
... LABEL IS L, WHETHER THE LABEL WAS PUT THERE BY RU1 OR BY RU2, THEN THE ARCHITECTURE DOES NOT REQUIRE THAT F1 == F2. In such cases, we may say that Rd is using a different "label space" for the labels it distributes to Ru1 than for the labels it distributes to Ru2. ...
... label spaces for the same interface. This is not prohibited by the architecture. However, in such cases the LSR must have some means, not specified by the architecture ...
... architecture. However, in such cases the LSR must have some means, not specified by the architecture, of determining, for a particular incoming label, which label space that label belongs to. For example, [MPLS-SHIM ...
... This architecture allows the choice between independent control and ordered control to be a local matter. Since the two methods ...
... traffic in the union, is known as "aggregation". The MPLS architecture allows aggregation. Aggregation may reduce the number ...
... particular FEC. The proposed MPLS protocol architecture supports two options for Route Selection: (1) hop by hop routing ...
... stack it is, it is necessary to define a concrete encoding of the label stack. The architecture supports several different encoding techniques; the choice of encoding ...
... encoding when transmitting a packet P to R3. In general, the MPLS architecture supports LSPs with different label stack encodings ...
... switches have no capability for translating from one encoding technique to another. The MPLS architecture therefore requires that whenever it is possible for two ATM switches ...
... The MPLS architecture accommodates both merging and non-merging LSRs, but allows for the fact that there may be LSRs ...
... In the MPLS architecture, if a particular upstream neighbor does not ...
... The MPLS architecture supports two ways to distribute labels at different layers of the hierarchy: Explicit Peering and Implicit Peering. ...
... This architecture does not establish hard and fast rules for choosing which label distribution protocol to use in which circumstances. ...


... The MPLS architecture supports several variants of each procedure. ...
... However, the MPLS architecture does not support all possible combinations of all possible variants. The set of supported combinations will be described in section 5.2, where the ...
... binding for a particular address prefix to its label distribution peers. The architecture supports four different distribution procedures. ...
... Only the MPLS schemes which are specified below are supported by the MPLS Architecture. Other schemes may be added in the future, if a need for them is shown. ...



Google
Web
RFC-Ref