The Experts below are selected from a list of 3273 Experts worldwide ranked by ideXlab platform
George Swallow - One of the best experts on this subject based on the ideXlab platform.
-
label switched path (LSP) Ping and Traceroute Multipath Support for Link Aggregation Group (LAG) Interfaces
2019Co-Authors: Nobo Akiya, John Drake, George Swallow, Stephane Litkowski, Bruno Decraene, Mach ChenAbstract:This document defines extensions to the MPLS label switched path (LSP) Ping and Traceroute mechanisms as specified in RFC 8029. The extensions allow the MPLS LSP Ping and Traceroute mechanisms to discover and exercise specific paths of Layer 2 (L2) Equal-Cost Multipath (ECMP) over Link Aggregation Group (LAG) interfaces. Additionally, a mechanism is defined to enable determination of the capabilities of an LSR supported. This document updates RFC8029.
-
label switched path (LSP) Ping/Traceroute for Segment Routing (SR) IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data Planes
2017Co-Authors: Mach Chen, George Swallow, Carlos M. Pignataro, Sriganesh Kini, Nagendra Kumar, Nobo AkiyaAbstract:A Segment Routing (SR) architecture leverages source routing and tunneling paradigms and can be directly applied to the use of a Multiprotocol label Switching (MPLS) data plane. A node steers a packet through a controlled set of instructions called "segments" by prepending the packet with an SR header. The segment assignment and forwarding semantic nature of SR raises additional considerations for connectivity verification and fault isolation for a label switched path (LSP) within an SR architecture. This document illustrates the problem and defines extensions to perform LSP Ping and Traceroute for Segment Routing IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with an MPLS data plane.
-
label switched path lsp ping traceroute for segment routing sr igp prefix and igp adjacency segment identifiers sids with mpls data planes
RFC, 2017Co-Authors: Mach Chen, George Swallow, Carlos M. Pignataro, Sriganesh Kini, Nagendra Kumar, Nobo AkiyaAbstract:A Segment Routing (SR) architecture leverages source routing and tunneling paradigms and can be directly applied to the use of a Multiprotocol label Switching (MPLS) data plane. A node steers a packet through a controlled set of instructions called "segments" by prepending the packet with an SR header. The segment assignment and forwarding semantic nature of SR raises additional considerations for connectivity verification and fault isolation for a label switched path (LSP) within an SR architecture. This document illustrates the problem and defines extensions to perform LSP Ping and Traceroute for Segment Routing IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with an MPLS data plane.
-
MPLS label switched path (LSP) Pseudowire (PW) Status Refresh Reduction for Static PWs
2017Co-Authors: George Swallow, Elisa Bellagamba, Luca MartiniAbstract:This document describes a method for generating an aggregated pseudowire (PW) status message transmitted for a statically configured PW on a Multiprotocol label Switching (MPLS) label switched path (LSP) to indicate the status of one or more PWs carried on the LSP. The method for transmitting the PW status information is not new; however, this protocol extension allows a Service Provider (SP) to reliably monitor the individual PW status while not overwhelming the network with multiple periodic status messages. This is achieved by sending a single cumulative summary status verification message for all the PWs grouped in the same LSP.
-
label switched path (LSP) and Pseudowire (PW) Ping/Trace over MPLS Networks Using Entropy labels (ELs)
2016Co-Authors: George Swallow, Carlos M. Pignataro, Nobo Akiya, Sam Aldrin, Andrew MalisAbstract:Multiprotocol label Switching (MPLS) label switched path (LSP) ping and traceroute are methods used to test Equal-Cost Multipath (ECMP) paths. Ping is known as a connectivity-verification method and traceroute is known as a fault-isolation method, as described in RFC 4379. When an LSP is signaled using the Entropy label (EL) described in RFC 6790, the ability for LSP ping and traceroute operations to discover and exercise ECMP paths is lost for scenarios where label Switching Routers (LSRs) apply different load-balancing techniques. One such scenario is when some LSRs apply EL-based load balancing while other LSRs apply load balancing that is not EL based (e.g., IP). Another scenario is when an EL-based LSP is stitched with another LSP that can be EL based or not EL based. This document extends the MPLS LSP ping and traceroute multipath mechanisms in RFC 6424 to allow the ability of exercising LSPs that make use of the EL. This document updates RFC 6790.
Mach Chen - One of the best experts on this subject based on the ideXlab platform.
-
label switched path (LSP) Ping and Traceroute Multipath Support for Link Aggregation Group (LAG) Interfaces
2019Co-Authors: Nobo Akiya, John Drake, George Swallow, Stephane Litkowski, Bruno Decraene, Mach ChenAbstract:This document defines extensions to the MPLS label switched path (LSP) Ping and Traceroute mechanisms as specified in RFC 8029. The extensions allow the MPLS LSP Ping and Traceroute mechanisms to discover and exercise specific paths of Layer 2 (L2) Equal-Cost Multipath (ECMP) over Link Aggregation Group (LAG) interfaces. Additionally, a mechanism is defined to enable determination of the capabilities of an LSR supported. This document updates RFC8029.
-
label switched path (LSP) Ping/Traceroute for Segment Routing (SR) IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data Planes
2017Co-Authors: Mach Chen, George Swallow, Carlos M. Pignataro, Sriganesh Kini, Nagendra Kumar, Nobo AkiyaAbstract:A Segment Routing (SR) architecture leverages source routing and tunneling paradigms and can be directly applied to the use of a Multiprotocol label Switching (MPLS) data plane. A node steers a packet through a controlled set of instructions called "segments" by prepending the packet with an SR header. The segment assignment and forwarding semantic nature of SR raises additional considerations for connectivity verification and fault isolation for a label switched path (LSP) within an SR architecture. This document illustrates the problem and defines extensions to perform LSP Ping and Traceroute for Segment Routing IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with an MPLS data plane.
-
label switched path lsp ping traceroute for segment routing sr igp prefix and igp adjacency segment identifiers sids with mpls data planes
RFC, 2017Co-Authors: Mach Chen, George Swallow, Carlos M. Pignataro, Sriganesh Kini, Nagendra Kumar, Nobo AkiyaAbstract:A Segment Routing (SR) architecture leverages source routing and tunneling paradigms and can be directly applied to the use of a Multiprotocol label Switching (MPLS) data plane. A node steers a packet through a controlled set of instructions called "segments" by prepending the packet with an SR header. The segment assignment and forwarding semantic nature of SR raises additional considerations for connectivity verification and fault isolation for a label switched path (LSP) within an SR architecture. This document illustrates the problem and defines extensions to perform LSP Ping and Traceroute for Segment Routing IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with an MPLS data plane.
-
label switched path (LSP) Ping and Traceroute Reply Mode Simplification
2016Co-Authors: Mach Chen, George Swallow, Carlos M. Pignataro, Nobo Akiya, Loa AnderssonAbstract:The Multiprotocol label Switching (MPLS) label switched path (LSP) Ping and Traceroute use the Reply Mode field to signal the method to be used in the MPLS echo reply. This document updates the procedures for the "Reply via Specified path" Reply Mode. The value of this Reply Mode is 5. The update creates a simple way to indicate that the reverse LSP should be used as the return path. This document also adds an optional TLV that can carry an ordered list of Reply Mode values.
-
label switched path (LSP) Ping/Traceroute Reply Mode Simplification
2014Co-Authors: George Swallow, Mach Chen, Carlos M. Pignataro, Nobo Akiya, Loa AnderssonAbstract:The Multiprotocol label Switching (MPLS) label switched path (LSP) Ping and Traceroute use the Reply Mode field to signal the method to be used in the MPLS echo reply. This document adds one value to the Reply Mode field to indicate reverse LSP. This document also adds an optional TLV which can carry ordered list of Reply Mode values. This document updates RFC4379.
Yakov Rekhter - One of the best experts on this subject based on the ideXlab platform.
-
RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol label Switching (GMPLS) Recovery
2007Co-Authors: Yakov Rekhter, Dimitri PapadimitriouAbstract:This document describes protocol-specific procedures and extensions for Generalized Multi-Protocol label Switching (GMPLS) Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE) signaling to support end-to-end label switched path (LSP) recovery that denotes protection and restoration. A generic functional description of GMPLS recovery can be found in a companion document, RFC 4426. [STANDARDS- TRACK]
-
label switched paths lsp hierarchy with generalized multi protocol label switching gmpls traffic engineering te
RFC, 2005Co-Authors: Yakov Rekhter, Kireeti KompellaAbstract:To improve scalability of Generalized Multi-Protocol label Switching (GMPLS) it may be useful to aggregate label switched paths (LSPs) by creating a hierarchy of such LSPs. A way to create such a hierarchy is by (a) a label Switching Router (LSR) creating a Traffic Engineering label switched path (TE LSP), (b) the LSR forming a forwarding adjacency (FA) out of that LSP (by advertising this LSP as a Traffic Engineering (TE) link into the same instance of ISIS/OSPF as the one that was used to create the LSP), (c) allowing other LSRs to use FAs for their path computation, and (d) nesting of LSPs originated by other LSRs into that LSP (by using the label stack construct). This document describes the mechanisms to accomplish this.
-
link bundling in mpls traffic engineering te
RFC, 2005Co-Authors: Kireeti Kompella, Lou Berger, Yakov RekhterAbstract:For the purpose of Generalized Multi-Protocol label Switching (GMPLS) signaling, in certain cases a combination of label> is not sufficient to unambiguously identify the appropriate resource used by a label switched path (LSP). Such cases are handled by using the link bundling construct, which is described in this document. This document updates the interface identification TLVs, which are defined in the GMPLS Signaling Functional Description. [STANDARDS-TRACK]
-
Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE)
2003Co-Authors: Kireeti Kompella, Yakov RekhterAbstract:Current signalling used by Multi-Protocol label Switching Traffic Engineering (MPLS TE) does not provide support for unnumbered links. This document defines procedures and extensions to Resource ReSerVation Protocol (RSVP) for label switched path (LSP) Tunnels (RSVP-TE), one of the MPLS TE signalling protocols, that are needed in order to support unnumbered links.
-
generalized multiprotocol label switching an overview of routing and management enhancements
IEEE Communications Magazine, 2001Co-Authors: Ayan Banerjee, Jonathan P Lang, John Drake, K. Kompella, B. Turner, Yakov RekhterAbstract:Generalized multiprotocol label switching, also referred to as multiprotocol lambda switching, supports not only devices that perform packet switching, but also those that perform switching in the time, wavelength, and space domains. The development of GMPLS requires modifications to current signaling and routing protocols. It has also triggered the development of new protocols such as the Link Management protocol. We present the traffic engineering enhancements to the Open Shortest path First Internet routing protocol and ISIS Intradomain Routing Protocol, two popular routing protocols, to support GMPLS. We present the concepts of generalized interfaces, label-switched path hierarchy, and link bundling intended to improve GMPLS scalability. We also discuss the Link Management Protocol which can be used to make the underlying links more manageable.
Nobo Akiya - One of the best experts on this subject based on the ideXlab platform.
-
label switched path (LSP) Ping and Traceroute Multipath Support for Link Aggregation Group (LAG) Interfaces
2019Co-Authors: Nobo Akiya, John Drake, George Swallow, Stephane Litkowski, Bruno Decraene, Mach ChenAbstract:This document defines extensions to the MPLS label switched path (LSP) Ping and Traceroute mechanisms as specified in RFC 8029. The extensions allow the MPLS LSP Ping and Traceroute mechanisms to discover and exercise specific paths of Layer 2 (L2) Equal-Cost Multipath (ECMP) over Link Aggregation Group (LAG) interfaces. Additionally, a mechanism is defined to enable determination of the capabilities of an LSR supported. This document updates RFC8029.
-
label switched path (LSP) Ping/Traceroute for Segment Routing (SR) IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data Planes
2017Co-Authors: Mach Chen, George Swallow, Carlos M. Pignataro, Sriganesh Kini, Nagendra Kumar, Nobo AkiyaAbstract:A Segment Routing (SR) architecture leverages source routing and tunneling paradigms and can be directly applied to the use of a Multiprotocol label Switching (MPLS) data plane. A node steers a packet through a controlled set of instructions called "segments" by prepending the packet with an SR header. The segment assignment and forwarding semantic nature of SR raises additional considerations for connectivity verification and fault isolation for a label switched path (LSP) within an SR architecture. This document illustrates the problem and defines extensions to perform LSP Ping and Traceroute for Segment Routing IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with an MPLS data plane.
-
label switched path lsp ping traceroute for segment routing sr igp prefix and igp adjacency segment identifiers sids with mpls data planes
RFC, 2017Co-Authors: Mach Chen, George Swallow, Carlos M. Pignataro, Sriganesh Kini, Nagendra Kumar, Nobo AkiyaAbstract:A Segment Routing (SR) architecture leverages source routing and tunneling paradigms and can be directly applied to the use of a Multiprotocol label Switching (MPLS) data plane. A node steers a packet through a controlled set of instructions called "segments" by prepending the packet with an SR header. The segment assignment and forwarding semantic nature of SR raises additional considerations for connectivity verification and fault isolation for a label switched path (LSP) within an SR architecture. This document illustrates the problem and defines extensions to perform LSP Ping and Traceroute for Segment Routing IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with an MPLS data plane.
-
label switched path (LSP) and Pseudowire (PW) Ping/Trace over MPLS Networks Using Entropy labels (ELs)
2016Co-Authors: George Swallow, Carlos M. Pignataro, Nobo Akiya, Sam Aldrin, Andrew MalisAbstract:Multiprotocol label Switching (MPLS) label switched path (LSP) ping and traceroute are methods used to test Equal-Cost Multipath (ECMP) paths. Ping is known as a connectivity-verification method and traceroute is known as a fault-isolation method, as described in RFC 4379. When an LSP is signaled using the Entropy label (EL) described in RFC 6790, the ability for LSP ping and traceroute operations to discover and exercise ECMP paths is lost for scenarios where label Switching Routers (LSRs) apply different load-balancing techniques. One such scenario is when some LSRs apply EL-based load balancing while other LSRs apply load balancing that is not EL based (e.g., IP). Another scenario is when an EL-based LSP is stitched with another LSP that can be EL based or not EL based. This document extends the MPLS LSP ping and traceroute multipath mechanisms in RFC 6424 to allow the ability of exercising LSPs that make use of the EL. This document updates RFC 6790.
-
label switched path (LSP) Ping and Traceroute Reply Mode Simplification
2016Co-Authors: Mach Chen, George Swallow, Carlos M. Pignataro, Nobo Akiya, Loa AnderssonAbstract:The Multiprotocol label Switching (MPLS) label switched path (LSP) Ping and Traceroute use the Reply Mode field to signal the method to be used in the MPLS echo reply. This document updates the procedures for the "Reply via Specified path" Reply Mode. The value of this Reply Mode is 5. The update creates a simple way to indicate that the reverse LSP should be used as the return path. This document also adds an optional TLV that can carry an ordered list of Reply Mode values.
Weiqiang Sun - One of the best experts on this subject based on the ideXlab platform.
-
label switched path (LSP) Data path Delay Metrics in Generalized MPLS and MPLS Traffic Engineering (MPLS-TE) Networks
2012Co-Authors: Guoying Zhang, Weiqiang SunAbstract:When setting up a label switched path (LSP) in Generalized MPLS (GMPLS) and MPLS Traffic Engineering (MPLS-TE) networks, the completion of the signaling process does not necessarily mean that the cross-connection along the LSP has been programmed accordingly and in a timely manner. Meanwhile, the completion of the signaling process may be used by LSP users or applications that control their use as an indication that the data path has become usable. The existence of the inconsistency between the signaling messages and cross-connection programming, and the possible failure of cross- connection programming, if not properly treated, will result in data loss or even application failure. Characterization of this performance can thus help designers to improve the way in which LSPs are used and to make applications or tools that depend on and use LSPs more robust. This document defines a series of performance metrics to evaluate the connectivity of the data path in the signaling process. [STANDARDS- TRACK]
-
Performance of label switched path dynamic provisioning in GMPLS networks
IEEE Communications Magazine, 2012Co-Authors: Weiqiang Sun, Guoying Zhang, Zijie Xing, Yaohui Jin, Wei Guo, Kai Kang, Rajiv PapnejaAbstract:Given the fact that control channels in GMPLS/MPLS-TE networks use packet-based forwarding, and the processing of control messages may be subject to various factors, the provisioning delay of an LSP could be highly random. To bridge the gap between the variable performance and demanding application needs, it is imperative to measure and characterize the LSP provisioning performance. In this article, we introduce the ongoing activities in IETF on defining standardized metrics and measurement methodologies for GMPLS/MPLS-TE performance. We also present our experiences in testing a number of GMPLS networks. The results can be seen as a sketch of performances of current state-of-the-art GMPLS implementations. We further point out possible future work in this area.
-
label switched path (LSP) Dynamic Provisioning Performance Metrics in Generalized MPLS Networks
2010Co-Authors: Weiqiang Sun, Guoying ZhangAbstract:Generalized Multi-Protocol label Switching (GMPLS) is one of the most promising candidate technologies for future data transmission network. GMPLS has been developed to control and operate different kinds of network elements, such as conventional routers, switches, Dense Wavelength Division Multiplexing (DWDM) systems, Add- Drop Multiplexors (ADMs), photonic cross-connects (PXCs), optical cross- connects (OXCs), etc. Dynamic provisioning ability of these physically diverse devices differs from each other drastically. At the same time, the need for Dynamicly provisioned connections is increasing because optical networks are being deployed in metro areas. As different applications have varied requirements in the provisioning performance of optical networks, it is imperative to define standardized metrics and procedures such that the performance of networks and application needs can be mapped to each other. This document provides a series of performance metrics to evaluate the dynamic LSP provisioning performance in GMPLS networks, specifically the Dynamic LSP setup/release performance. These metrics can depict the features of GMPLS networks in LSP dynamic provisioning. They can also be used in operational networks for carriers to monitor the control plane performance in realtime.
-
label switched path (LSP) Data path Delay Metric in Generalized MPLS/ MPLS-TE Networks
2009Co-Authors: Tomohiro Otani, Weiqiang Sun, Guoying Zhang, Xueqing Wei, Rajiv Papneja, Jianhua Gao, Guowu Xie, Ruiquan JingAbstract:When setting up a label switched path (LSP) in Generalized MPLS and MPLS/TE networks, the completion of the signaling process does not necessarily mean that the cross connection along the LSP have been programmed accordingly and in a timely manner. Meanwhile, the completion of signaling process may be used by applications as indication that data path has become usable. The existence of this delay and the possible failure of cross connection programming, if not properly treated, will result in data loss or even application failure. Characterization of this performance can thus help designers to improve the application model and to build more robust applications. This document defines a series of performance metrics to evaluate the availability of data path in the signaling process.
-
Dynamic label switched path provisioning performance in GMPLS networks
2009 14th OptoElectronics and Communications Conference, 2009Co-Authors: Zijie Xing, Weiqiang Sun, Yaohui Jin, Wei GuoAbstract:We introduce the recent standardization activities for GMPLS/MPLS-TE performance. We argue defining performance metrics is important to bridge the gap between network performance and application requirements. Testing results are also reported.