gmpls-13070799751567-phpapp01-110603005638-phpapp01

3
GMPLS: Generalized Multiprotocol Label Switching Generalized Multiprotocol Label Switching (GMPLS) enhances MPLS architecture by the complete separation of the control and data planes (See C onnection l ess N etwork P rotocol —CLNP) of various networking layers. GMPLS enables a seamless interconnection and convergence of new and legacy networks by allowing end-to-end provisioning, control and traffic engineering even when the start and the end nodes belong to heterogeneous networks. GMPLS is based on the IP routing and addressing models. This assumes that IPv4 and/or IPv6 addresses are used to identify interfaces but also that traditional (distributed) IP routing protocols are reused. The common control plane promises to simplify network operation and management by automating end-to-end provisioning of connections, managing network resources, and providing the level of QoS that is expected in the new applications. While the technology used by the GMPLS control plane remains IP-based, the data plane (traffic plane) can now diversify to include more varieties of traffic (TDM, Lambda, packet, and fiber, etc). Generalized MPLS (GMPLS) supports multiple types of switching, i.e., the addition of support for TDM, lambda, and fiber (port) switching. In summary, GMPLS extends MPLS functionality by establishing and provisioning paths for: TDM paths, where time slots are the labels (SONET). FDM paths, where electromagnetic frequency is the label (light waves). Space division multiplexed paths, where the label indicates the physical position of data (Photonic Cross-connect). GMPLS is based on the Traffic Engineering (TE) extensions to MPLS (MPLS- TE). The biggest addition in the GMPLS protocol suite is a new signaling protocol, Link Management Protocol (LMP), to establish, release and manage connections between two adjacent GMPLS-capable nodes. Other protocols RSVP-TE, OSPF-TE, CR-LDP and IS-IS-TE, where OSPF-TE and IS-IS-TE are extended from the original protocols for GMPLS, are used in the GMPLS architecture. 1

description

mpls

Transcript of gmpls-13070799751567-phpapp01-110603005638-phpapp01

GMPLS: Generalized Multiprotocol Label SwitchingGeneralized Multiprotocol Label Switching (GMPLS) enhances MPLS architecture by the complete separation of the control and data planes (See Connectionless Network Protocol CLNP) of various networking layers. GMPLS enables a seamless interconnection and convergence of new and legacy networks by allowing end-to-end provisioning, control and traffic engineering even when the start and the end nodes belong to heterogeneous networks.

GMPLS is based on the IP routing and addressing models. This assumes that IPv4 and/or IPv6 addresses are used to identify interfaces but also that traditional (distributed) IP routing protocols are reused. The common control plane promises to simplify network operation and management by automating end-to-end provisioning of connections, managing network resources, and providing the level of QoS that is expected in the new applications.

While the technology used by the GMPLS control plane remains IP-based, the data plane (traffic plane) can now diversify to include more varieties of traffic (TDM, Lambda, packet, and fiber, etc). Generalized MPLS (GMPLS) supports multiple types of switching, i.e., the addition of support for TDM, lambda, and fiber (port) switching. In summary, GMPLS extends MPLS functionality by establishing and provisioning paths for:

TDM paths, where time slots are the labels (SONET).

FDM paths, where electromagnetic frequency is the label (light waves).

Space division multiplexed paths, where the label indicates the physical position of data (Photonic Cross-connect).

GMPLS is based on the Traffic Engineering (TE) extensions toMPLS (MPLS-TE). The biggest addition in the GMPLS protocol suite is a new signaling protocol, Link Management Protocol (LMP), to establish, release and manage connections between two adjacent GMPLS-capable nodes. Other protocols RSVP-TE, OSPF-TE, CR-LDP and IS-IS-TE, where OSPF-TE and IS-IS-TE are extended from the original protocols for GMPLS, are used in the GMPLS architecture.

Network Monitoring and TroubleshootingEasy to use tool with comprehensive features at a fraction of the cost of others.Click here for free demo.Technical books, quick guides and postersNetworking, telecom, computing, wireless, information technologies, security and much more ...Click here for details.

Protocol Structure - Generalized Multiprotocol Label Switching (MPLS)

GMPLS Protocol Suite Overview

ProtocolsDescription

RoutingOSPF - TE, IS - IS - TERouting protocols for the auto-discovery of network topology, advertise resource availability.

SignalingRSVP - TE, CR - LDPSignaling protocols for the establishment of traffic-engineered LSPs.

Link ManagementLMP Control-Channel Management

Link-Connectivity Verification

Link-Property Correlation

Fault Isolation

Related ProtocolsLDP,CR-LDP,RSVP-TE,IP,ATM,RSVP,OSPF,BGP,IS-IS,MPLS

Sponsor Source

GMPLS architecture arcis defined by IETF (http://www.ietf.org) RFC 3945.Referencehttp://www.ietf.org/html.charters/ccamp-charter.html: GMPLS Charter http://www.javvin.com/protocol/rfc3031.pdf: Multiprotocol Label Switching Architecture

http://www.javvin.com/protocol/rfc3945.pdf:Generalized Multi-Protocol Label Switching (GMPLS) Architecture

1