Introducing MPLS: First Chunk

We use MPLS as a running example throughout the book. Deployment of MPLS in the enterprise core is likely to occur only in extremely large organizations. Typically, such organizations have global reach and may already use a lot of ATM. Service providers are already deploying MPLS. Enterprises may initially deploy MPLS on WAN backbones and later on, they may move MPLS into the network core . In fact, the expansion of MPLS to the enterprise premises (via the MPLS UNI) is part of the work of the MPLS Forum.

On a more general note, a good understanding of MPLS is important for appreciating issues such as traffic engineering, network-QoS, and connection-oriented IP networks.

This section introduces the first chunk of MPLS [DavieRehkter2000] technology presented in this book. MPLS is essentially quite simple, but the building blocks are a little difficult to learn because they span both layers 2 and 3 and require some understanding of signaling and IP routing protocols. For this reason, the discussion is split into easy-to-understand, bite- sized chunks , ^[1] starting here and finishing up with the case study on some aspects of MPLS network management in chapters 8 and 9.

^[1] This is in keeping with our concepts of learning about network management and creating NMS solutions. These ideas are introduced in later chapters, but for now we say that a given technology must be understood before an attempt is made to manage it. This is obvious enough, but the depth of understanding is the key. In many cases, a good overview is all that is needed to get started on producing an NMS solution. This is the model we use with MPLS.