ASM Availability state machine
ATM Asynchronous transfer mode
BIP Bit Interleaved Parity
CR-LDP constraint-based routing LDP
DLCI Data Link Connection Identifier
DoS Denial of Service
E-LSP EXP-Inferred-PSC LSP [21]
ER Explicit Routing
FEC Forwarding Equivalence Classes
FFS For Further Study
FTN FEC-To-NHLFE
LIB Label Information Bases
L-LSP Label-Only-Inferred-PSC LSP [21]
LSP Label Switched Path
LSR Label Switching Router
MIB Management Information Base
MPLS Multi Protocol Layer Switching
NHLFE Next-Hop Label Forwarding Entry
NMS Network Management System.
OAM Operation Administration and Maintenance
PDU Protocol data unit
PHB Per Hop Behavior
QoS Quality of Service
RSVP Resource ReSerVation Protocol
RSVP-TE RSVP Extensions for Traffic Engineering
SLA Service Level Agreement
SNMP Simple Network Management Protocol
TLV Type/Length/Value
TTSI Trail Termination Source Identifier
VCI virtual circuit identifier
VPI virtual path identifier
Backup entity – This is a collective term for the protection LSP of the protection switching mechanism and the backup segment for the fast rerouting mechanism.
Bi-Directional: Two LSRs that use LDP to exchange label/FEC mapping information are known as "LDP Peers" with respect to that information and we speak of there being an "LDP Session" between them. A single LDP session allows each peer to learn the other's label mappings; i.e., the protocol is bi-directional [8].
Control plane: The MPLS Control Plane is responsible for populating and maintaining the LFIB. [52]
Data-plane: See user-plane.
Dedicated OAM Cells: Packets containing OAM information that are dedicated to be sent at a periodic basis.
Egress: Point of exit from an MPLS context or domain. The egress of an LSP is the logical point at which the determination to pop a label associated with an LSP is made. The label may actually be popped at the LSR making this determination or at the one prior to it (in the penultimate hop pop case). Egress from MPLS in general is the point at which the last label is removed (resulting in removal of the label stack). [49]
Ingress: Point at which an MPLS context or domain is entered. The ingress of an LSP is the point at which a label is pushed onto the label stack (possibly resulting in the creation of the label stack). [49]
LSP Tunnel: An LSP tunnel is an LSP with a well-defined source (ingress point) and sink (egress point). From an architectural viewpoint an LSP tunnel at layer N is equivalent to an LSP trail at layer N. However, the term ‘tunnel’ implies that it is supporting some higher layer client entity, which could be either a higher level LSP trail or (for the highest level LSP trail) a higher level network layer protocol such as IP. [21a]
Label switching: Switching based on use of labels. [49]
Label Switching Router (LSR): A device that participates in one or more routing protocols and uses the route information derived from routing protocol exchanges to drive LSP setup and maintenance. Such a device typically distributes labels to peers and uses these labels (when provided as part of data presented for forwarding) to forward label-encapsulated L3 packets. In general, an LSR may or may not be able to forward non-label-encapsulated data and provide ingress/egress to LSPs (that is, to perform what is frequently referred to as the label edge router, or LER, function).
Network Management System (NMS): System responsible for managing at least part of a network (Network Cell). An NMS is generally a reasonably powerful and well-equipped computer such as an engineering workstation. NMSs communicate with agents to help keep track of network statistics and resources.
Per Hop Behavior: A Differentiated Services behavioral definition. A PHB is defined at a node by the combination of a Differentiated Services Code Point (DSCP) and a set of configured behaviors. [49]
Penultimate hop: A process by which the peer immediately upstream of the egress LSR is asked to pop a label prior to forwarding the packet to the egress LSR. Using LDP, this is done by assigning the special value of the implicit Null label. This allows the egress to push the work of popping the label to its upstream neighbor, possibly allowing for a more optimal processing of the remaining packet. Note that this can be done because once the label has been used to determine the next-hop information for the last hop, the label is no longer useful. Using PHP is helpful because it allows the packet to be treated as an unlabeled packet by the last hop. Using PHP, it is possible to implement an "LSR" that never uses labels. [49]
Redundancy: When a backbone network has more than one links between its routers, thus making different ways traffic can be sent to the same destination, we say that the backbone has link redundancy. If the backbone has one or more alternative LSP(s) between the edge routers for a given LSP, we say that the backbone has LSP redundancy. A low degree of redundancy means that the network normally uses most of its links, whilst a high degree of redundancy means that the network normally uses few of its links.
Reliability: When a backbone network has more than one links between its routers, and the network has mechanisms for detecting link errors and route around the affected area, we say that the network has high link reliability. If the backbone has one or more alternative LSP(s) between the edge routers for a given LSP and the network has mechanisms for detecting LSP errors, we say that the LSPs have high LSP reliability.
Router: A device used to forward packets at the network (L3) layer. [49]
Service Level Agreement (SLA): SLA is a contract between network providers and customers that services the providers should provide. This can be the amount of server uptime in percentage, the amount of users that can be served simultaneously or similar.
Type-Length-Value (TLV): An object description with highly intuitive meaning; that is, the object consists of three fields: type, length, and value. Type gives the semantic meaning of the value, length gives the number of bytes in the value field (that may be fixed by the type), and value consists of length bytes of data in a format consistent with type. This object format is used in LDP and several other protocols [49].
Trail: A generic transport entity at layer N which is composed of a client payload (which can be a packet from a client at higher layer N-1) with specific overhead added at layer N to ensure the forwarding integrity of the server transport entity at layer N. This is a more general term for LSP at ITU-T. [21]
Trail termination point: A source or sink point of a trail at layer N, at which the trail overhead is added or removed respectively. A trail termination point must have a unique means of identification within the layer network. [21a]
Upstream: Direction from which traffic is expected to arrive. This applies to a specific forwarding equivalence class. [49]
User-plane: This refers to the set of traffic forwarding components through which traffic flows. CV OAM packets are periodically inserted into this traffic flow to monitor the health of those forwarding components. The user-plane is also sometimes called the data-plane (especially in IETF). Note that control-plane protocols (eg for signalling or routing) and management-plane protocols will require their own user-plane, and their user-plane may or may not be congruent (to varying degrees) with the traffic bearing user-plane [21].
[1] The Franklin Institute Online
Bell’s telephone
http://sln.fi.edu/franklin/inventor/bell.html
[2] Gerd Klaasen
Das World Wide Web Museum, University of Applied Sciences Oldenburg/Ostfriesland/Wilhelmshaven, 2001
http://spot.fho-emden.de/alge/museum/
[3] ITU-T Study Group 13
ITU-T IP Project, February 2002
http://www.itu.int/ITU-T/studygroups/com13/ip/documents/ip.pdf
[4] Bill Michael
MPLS: Breaking Through, A Status Report, Computer Telephony, July
2001
http://www.cconvergence.com/article/CTM20010425S0001
[5] Network Working Group, IETF
Detecting Data Plane Liveliness in MPLS, draft, WORK IN PROGRESS,
expires September 2002, draft-ietf-mpls-lsp-ping-00.txt
[6] Uyless D. Black,
MPLS and Label Switching Networks, pages 1-18, January 2001,
Prentice Hall PTR, Upper Saddle River, New Jersey
[6a] Uyless D. Black
MPLS and Label Switching Networks, pages 60-85, January 2001,
Prentice Hall PTR, Upper Saddle River, New Jersey
[7] Vijayanand C
Fast Reroute Extensions to CRLDP, Internet Draft, WORK IN PROGRESS,
expires October 2002
http://www.ietf.org/internet-drafts/draft-vijay-mpls-crldp-fastreroute-00.txt
[8] Andersson, L., Doolan, P., Feldman, N.,
Fredette, A., Thomas, B.,
LDP Specification, RFC 3036, IETF Network Working Group, January 2001
http://www.ietf.org/rfc/rfc3036.txt
[9] Awduche, D., Malcolm, J., Agogbua, J., O'Dell,
M., McManus, J.,
Requirements for Traffic Engineering Over MPLS, RFC 2702, IETF Network
Working Group, September 1999
http://www.ietf.org/rfc/rfc2702.txt
[10] Dr. Bruce Davie
Multiprotocol Label Switching -Service Providers to Benefit from New
Functionality, Packet Magazine, Second Quarter 1999
http://www.cisco.com/warp/public/784/packet/apr99/6.html
[11] Uninett Nettstatistikk
Oslo-Bergen daily traffic in kbit/s, Uninett, December 2001
http://stasi.uninett.no/stat-q/plot-all/oslo-bergen,2001-12,day,traffic-kbit
[12] Ballew, S. M., Loukides, M.,
Managing IP Networks with Cisco Routers, Michael Loukides (editor),
O’Reilly & Associates, January1997
[13] Bruce Davie, Yakov Rekhter
MPLS Technology and Applications, pages 25 -57, Morgan Kaufmann
Publisher, May 2000
[13a] Bruce Davie, Yakov Rekhter
MPLS Technology and Applications, pages 121 -146, Morgan Kaufmann
Publisher, May 2000
[14] Nagarajan R., Qureshi M.A., Wang Y.T.
A Packet 1+1 Path Protection Service for MPLS Networks, Internet Draft,
WORK IN PROGRESS, March 2002, Expires September 2002
http://www.ietf.org/internet-drafts/draft-nagarajan-ccamp-mpls-packet-protection-00.txt
[15] Denninger, L., Mohamed-Ahmed, A., Santos, J.,
Westermark, L.,
White Paper - Using MPLS To Improve Performance, Interdisciplinary
Telecommunications Program, University of Colorado at Boulder
http://www.ispworld.com/miscellaneous/wp_mpls_121100a.htm
[16] Lynch, D.C., Rose, M.T.,
Internet System Handbook, pages 276-280, Addison-Wesley Publishing
Company, Rose, M.T. (editor), January 1993
[17] ITU-T Study Group 13
B-ISDN operation and maintenance principles and functions, ITU-T
Recommendation I.610, February 1999
[18] Larry L. Peterson and Bruce S. Davie
Computer Network, a systems approach, 2.edition, pages 171–243, Morgan
Kaufmann Publisher, David Clark, Jennifer Mann (editor), San Francisco, USA,
2000
[18a] Larry L. Peterson and Bruce S. Davie
Computer Network, a systems approach, 2.edition, pages 246 - 366, Morgan
Kaufmann Publisher, David Clark, Jennifer Mann (editor), San Francisco, USA,
2000
[18b] Larry L. Peterson and Bruce S. Davie
Computer Network, a systems approach, 2.edition, pages 2 – 66, Morgan
Kaufmann Publisher, David Clark, Jennifer Mann (editor), San Francisco, USA,
2000
[18c] Larry L. Peterson and Bruce S. Davie
Computer Network, a systems approach, 2.edition, pages 647- 649, Morgan
Kaufmann Publisher, David Clark, Jennifer Mann (editor), San Francisco, USA,
2000
[19] Postel, J.
Internet Control Message Protocol, RFC 792, IETF Network Working Group,
September 1981
http://www.ietf.org/rfc/rfc792.txt
[20] ITU-T Study Group 13
Corrigendum to Recommendation Y.1710, Temporary Document 11R2
(PLEN) concerning Recommendation Y.1710, WORK IN PROGRESS, February 2002
[21] ITU-T Study Group 13
OAM mechanism for MPLS networks, Temporary Document 19 (WP3/13)
concerning Recommendation Y.1711, WORK IN PROGRESS, January 2002
[21a] ITU-T Study Group 13
OAM mechanism for MPLS networks, Temporary Document 12R2 (PLEN) concerning
Recommendation Y.1711, WORK IN PROGRESS, February 2002
[22] E. Rosen, D. Tappan, G. Fedorkow, Y. Rekhter,
D. Farinacci, T. Li, A. Conta
MPLS Label Stack Encoding, RFC 3032, IETF Network Working Group, January
2001
http://www.ietf.org/rfc/rfc3032.txt
[23] IETF Routing Information Protocol (RIP) Working
Group
Description of Working Group, April 2002
http://www.ietf.org/html.charters/rip-charter.html
[24] KPNQuest Norway AS
The EuroRing project, May 2001
http://www.kpnqwest.no/nettverk/
[25] J. Hawkinson, BBN Planet, T. Bates
Guidelines for creation, selection, and registration of an Autonomous System
(AS), RFC 1930, Network Working Group, March 1996
http://www.ietf.org/rfc/rfc1930.txt
[26] D. Awduche, L. Berger, D. Gan, T. Li, V.
Srinivasan, G. Swallow
RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209, IETF Network
Working Group, December 2001
http://www.ietf.org/rfc/rfc3209.txt
[27] B. Jamoussi, L. Andersson, R. Callon, R. Dantu,
L. Wu, P. Doolan, T. Worster, N. Feldman, A. Fredettem, M. Girish, E. Gray, J.
Heinanen, T. Kilty, A. Malis
Constraint-Based LSP Setup using LDP, RFC 3212, IETF Network Working
Group, January 2002
http://www.ietf.org/rfc/rfc3212.txt
[28] Cheenu Srinivasan, Arun Viswanathan, Thomas D.
Nadeau
Multiprotocol Label Switching (MPLS) Traffic Engineering Management
Information Base, Internet Draft, WORK IN PROGRES, IETF Network Working
Group, January 2002, expires July 2002
http://www.ietf.org/internet-drafts/draft-ietf-mpls-te-mib-08.txt
[29] R. Hinden, S. Deering
IP Version 6 Addressing Architecture, RFC 1884, IETF Network Working Group
December 1995
http://www.ietf.org/rfc/rfc1884.txt
[30] Case, J., Fedor, M. , Schoffstall, M., and Davin, C.
A Simple
Network Management Protocol (SNMP), RFC 1098, Internet Engineering Task Force, April
1989
www.ietf.org/rfc/rfc1098.txt
[31] J. Boyle, V. Gill, A. Hannan, D. Cooper, D.
Awduche, B. Christian, W.S. Lai
Applicability Statement for Traffic Engineering with MPLS, Internet
Draft, WORK IN PROGRESS, IETF Traffic Engineering Working Group, February 2002,
Expires October 2002
http://www.ietf.org/internet-drafts/draft-ietf-tewg-te-applicability-01.txt
[32] ITU-T Study Group 13
Protection switching for MPLS networks, Temporary Document XXX
concerning Recommendation Y.1720, WORK IN PROGRESS, May 2001
[33] Rosen, E., Viswanathan, A., Callon, R.,
Multiprotocol Label Switching Architecture, RFC 3031, IETF Network Working
Group, January 2001
http://www.ietf.org/rfc/rfc3031.txt
[34] S. Deering and R. Hinden
Internet Protocol, Version 6 (IPv6) Specification, RFC 2460, Network
Working Group, December 1998
http://www.ietf.org/rfc/rfc2460.txt
[35] P.Pan, D. Gan, G. Swallow, J. P. Vasseur, D.
Cooper, A. Atlas, M. Jork
Fast Reroute Extensions to RSVP-TE for LSP Tunnels, Internet Draft,
WORKS IN PROGRESS, IETF Network Working Group, expires July 2002
http://www.ietf.org/internet-drafts/draft-ietf-mpls-rsvp-lsp-fastreroute-00.txt
[36] C. Srinivasan, A. Viswanathan, T. D. Nadeau
Multiprotocol Label Switching (MPLS) Label Switch Router (LSR) Management
Information Base, Internet Draft, WORK IN PROGRESS, IETF Network Working
Group, January 2002, expires July 2002
http://www.ietf.org/internet-drafts/draft-ietf-mpls-lsr-mib-08.txt
[37] Gundersen, H., Trydal, F.
QoS for real-time IP traffic, Graduate Thesis,
Agder University College, May 2001
http://www.siving.hia.no/ikt01/ikt6400/ftryda95/Report.doc
[38] Network Working Group, IETF
Multiprotocol Label Switching (MPLS) FEC-To-NHLFE (FTN) Management Information
Base, draft, WORK IN PROGRESS, expires July 2002, draft-ietf-mpls-ftn-mib-04.txt
[39] F. Kastenholz,
SNMP Communications Services, RFC 1270, IETF Network Working Group,
October 1991
http://www.ietf.org/rfc/rfc1270.txt
[40] ITU-T Study Group 13
Question 3/13 - OAM and Network Management in IP-Based and Other Networks,
January 2002
http://www.itu.int/ITU-T/studygroups/com13/sg13-q3.html
[41] R. Kavasseri, B. Stewart
Distributed Management Expression MIB, RFC 2982, IETF Network Working
Group, October 2000
http://www.ietf.org/rfc/rfc2982.txt
[42] ITU-T Study Group 13
Question 4/13 - Broadband and IP-Related Resource Management, January
2002
http://www.itu.int/ITU-T/studygroups/com13/sg13-q4.html
[43] D.E. Comer
Internetworking with TCP/IP, Vol.1, 4th edition., Prentice
Hall
[44] K. McCloghrie
SNMPv2
Management Information Base for the Internet Protocol using SMIv2, FC 2011, IETF Network Working Group, November 1996 http://www.ietf.org/rfc/rfc2011.txt
[45] Information Sciences Institute, University of Southern California,
Internet Protocol, Darpa internet program protocol specification, RFC
791, September 1981, http://www.ietf.org/rfc/rfc791.txt
[46] T. Socolofsky, C. Kale
A TCP/IP Tutorial, RFC 1180, IETF Network Working Group, January 1991
http://www.ietf.org/rfc/rfc1180.txt
[47] Sangoma Technologies
TCP/IP and IPX routing Tutorial, March 2002
http://www.sangoma.com/tcp2002.pdf
[48] P. Almquist, F. Kastenholz,
Towards Requirements for IP Routers, RFC 1716, IETF Network Working
Group, November 1994, http://www.ietf.org/rfc/rfc1716.txt
[49] The MPLS Resource Center
The MPLS
Resource Center, http://www.mplsrc.com/
[50] The 10 Gigabit Ethernet Alliance
FAQ, http://www.10gea.org/
[51] Cisco Systems, Inc
Open Shortest Path First, February 2002, http://www.cisco.com/univercd/cc/td/doc/cisintwk/ito_doc/ospf.htm
[52] Vivek Alwayn
Advanced MPLS Design and Implementation, pages 45 – 74, John Kane
(editor), Cisco Press, Indianapolis, USA, 2002