See all Tutorials
 

Tutorial

Introduction to MPlS and GMPLS
(continued)

4) Path Management. We learned in the MPLS signaling article that MPLS can use RSVP to establish a link from end-to-end. However, if MPLS data traverses telecom networks, other protocols must be implemented, such as UNI, PNNI, or SS7.   Path management can be a challenge because several standards organizations are involved. Currently, the IETF is working on modifications to RSVP and LDP (Label Distribution Protocol) to extend the protocol to allow for GMPLS path management and control (Figure 11).


Figure 11

5) Link Management.  In MPLS, the LSP (Label Switch Path) was used to establish and tear down links and aggregate links. In GMPLS, the ability to establish and aggregate optical channels is required. LMP (Link Management Protocol) extends the MPLS functions into an optical plane where link building improves scalability (Figure 12).


Figure 12

6) Protection and Recovery.  Intelligent optical networking allows inflexible optical networks to interact with each other. With GMPLS, instead of having one ring with a backup ring for protection, the network creates a true mesh that allows for several different paths (Figure 13). Optical networking can go from a one-to-one protection method to a one-to-many protecting method.


Figure 13

<< Previous page     Next page >>

Page 5 of 7

Tutorials

Wireless LAN
1) Wireless LAN Technology and Network Implementation
2) Wireless LAN Antennas

Quality of Service
What Ever Happened to QoS?

MPLS
1) An Introduction to MPLS 
2) Introduction to MPLS Label Distribution and Signaling
3) Advanced MPLS Signaling
4) MPLS Network Reliance and Recovery
5) MPLS Traffic Engineering
6) Introduction to MPlS and GMPLS 

Ethernet  Ethernet in Metro and Long Haul Networks

Recent MPLS News

Database Results Error
Could not find file 'D:\Inetpub\www-silver\fpdb\article test.mdb'.
Guest Columns
Programmability for SIP-based Services
Michael Doerk, 
Nortel Networks
Hardening MPLS Networks
Steve Vogelsang
Laurel Networks
Exempting Packetized Traffic from Unbundling Requirements is Bad Policy  Shawn M. LewisCaerus, Inc.
Voice over Packet Protocols
VoIP and VoATM (VoAAL1, VoAAL2) 
  Michel Laurence, Octasic, Inc. 

See all Guest Columns

 

 

 

Subscription Info  |  UnSubscribe  |  Archive  | Marketing & Advertising  |  Link2Us Events  | About Us  |  Contact Us
Copyright © 2009 Converge! Media Ventures, Inc.  All rights reserved.