Last Modified:
2002-09-24
Aricent MPLS
MPLS (Multi Protocol Label Switching)software from Aricent is an efficient
and portable implementation of the label switching capability mechanism as required
by industry standards. It supports RSVP extensions for traffic engineering (RSVP-TE),
Label Distribution Protocol (LDP) with Constraint-based Routed Label Switched
Paths (CR-LSP), MPLS Forwarding Module and Diff-Serv aware signaling.
Figure 1. Aricent MPLS Architecture
Aricent MPLS Features:
Configurable as LER or LSR.
Traffic Engineering (TE) tunnels using RSVP-TE.
Basic and extended Label Distribution Protocol (LDP) mechanisms.
Diff-Serv aware E-LSP and L-LSP signaling.
Constraint-based routed LSP (CR-LSP).
RSVP-TE and CR-LSP tunnel modifications.
Multiple FEC classifications based on:
IP Address Prefix.
Host Address.
Downstream On Demand Independent and Ordered control label distribution modes.
Conservative Label Retention mode.
Loop detection using path vectors and hop counts (CR-LDP).
Stacked LSPs.
Provides Loop detection using RRO (RSVP-TE).
RSVP-TE Hello message extensions for rapid detection of node failures.
LSP Preemption (Setup and Holding).
Resource Class Affinity Attribute handling.
Ethernet and ATM interface.
Pre-integrated with Aricent IP, Aricent RIP, Aricent TCP, Aricent
OSPF, Aricent QoS and Aricent SNMP.
Dynamic trace level configuration.
Completely configurable through SNMP and CLI.
Conforms to Aricent Architecture for Portability Release (FSAP2), thus ensuring
highly portable code, which uses flexible buffer and timer management libraries.
Aricent MPLS Benefits
Aricent MPLS reduces the time to market for OEMs and VARs who wish to incorporate
the MPLS functionality into their switching/routing devices.
The initial goals of the working group have been largely completed. In particular, it has produced a number of RFCs (see list below) that define the base Label Distribution Protocol (LDP), the basic MPLS architecture and encapsulations, and definitions for how MPLS runs over ATM and Frame Relay links.
The current goals of the working group are:
1. Complete outstanding items from the original MPLS effort:
Informational:
(6/12) Applicability Statement for Extensions to RSVP for LSP-Tunnels (8/08) Applicability Statement for CR-LDP (6/12) LDP State Machine
Experimental:
(10/19/99) MPLS Loop Prevention Mechanism
Standards Track:
(8/08) Constraint-Based LSP Setup using LDP (2/07) Carrying Label Information in BGP-4 (8/29) Extensions to RSVP for LSP Tunnels (8/29) MPLS Support of Differentiated Services (6/27) LSP Modification Using CR-LDP (9/01) Definitions of Managed Objects for LDP (8/29) MPLS Label Switch Router Management Information Base
2. Advance the Proposed Standards developed by the MPLS WG to Draft Standard. This includes the LDP, CR-LDP, and RSVP-TE signaling specifications as well as the encapsulations.
3. Specify appropriate extensions to LDP and RSVP for authentication of LSP originators.
4. Complete work on the MPLS-TE MIB.
5. Specify improved fault tolerance mechanisms for LDP
6. Specify MPLS-specific recovery mechanisms to allow one label-switched path to be used as backup for a set of other label-switched paths, including cases which permit local repair. What constitutes the necessary set of MPLS-specific recovery mechanism should be ascertained through cooperation with the CCAMP and TE working groups.
7. Document additional MPLS encapsulations to allow the operation of label-switched paths over additional lower-layer technologies, such as time-division (e.g. SONET ADMs), wavelength (optical lambdas) and spatial switching (e.g. incoming fiber to outgoing fiber).
8. Complete work in progress for specifying the framework for IP multicast over label switched paths.
| Done |    | Submit documents from original MPLS effort to IESG |
| JAN 01 |    | Shepherd completed MPLS specifications through IESG review and RFC editor processing |
| FEB 01 |    | MPLS-TE MIB ready for advancement to Proposed Standard |
| MAR 01 |    | Framework for IP multicast over label-switched paths ready for advancement. |
| JUN 01 |    | LDP fault tolerance specification ready for advancement to Proposed Standard. |
| AUG 01 |    | Specification for MPLS-specific recovery ready for advancement. |
| NOV 01 |    | Base MPLS Proposed Standard RFCs ready for advancement to Draft Standard. |
| DEC 01 |    | LDP end-to-end LSP authentication ready for advancement to Proposed Standard. |
Requirements for Traffic Engineering Over MPLS (RFC 2702) (68386 bytes)
Multiprotocol Label Switching Architecture (RFC 3031) (147175 bytes)
MPLS Label Stack Encoding (RFC 3032) (48314 bytes)
Use of Label Switching on Frame Relay Networks
Specification (RFC 3034) (53176 bytes)
MPLS using LDP and ATM VC Switching (RFC 3035) (46463 bytes)
LDP Specification (RFC 3036) (274855 bytes)
LDP Applicability (RFC 3037) (13601 bytes)
VCID Notification over ATM link for LDP (RFC 3038) (39134 bytes)
The Assignment of the Information Field and Protocol
Identifier in the Q.2941 Generic Identifier and Q.2957 User-to-user Signaling for the Internet Protocol (RFC 3033) (52188 bytes)
MPLS Loop Prevention Mechanism (RFC 3063) (93523 bytes)
Carrying Label Information in BGP-4 (RFC 3107) (16442 bytes)
RSVP-TE: Extensions to RSVP for LSP Tunnels (RFC 3209) (132264 bytes)
Applicability Statement for Extensions to RSVP for
LSP-Tunnels (RFC 3210) (17691 bytes)
Constraint-Based LSP Setup using LDP (RFC 3212) (87591 bytes)
Applicability Statement for CR-LDP (RFC 3213) (14489 bytes)
LSP Modification Using CR-LDP (RFC 3214) (25453 bytes)
LDP State Machine (RFC 3215) (117278 bytes)
MPLS Support of Differentiated Services (RFC 3270) (137960 bytes)
Framework for IP Multicast in MPLS (RFC 3353) (65860 bytes)
Cable & Wireless Further Extends OC-192 Using MPLS Across Global IP Network
Marconi Details IP / MPLS Infrastructure Solutions for Small and Medium Networks