Juniper Networks, Inc.

Abhishek Deshmukh

Raveendra Torvi

Kireeti Kompella

Tarek Saad

Vishnu Pavan Beeram

Ravi I Singh

Ronald P Bonica

Alia Karin Atlas

Markus Jork

Zhaohui Zhang

The same prefix segment identifier (SID) may be configured and/or used for either (A) more than one prefix within an interior gateway protocol (IGP) domain, or (B) one prefix with more than one path computation algorithm within the IGP domain by: (a) receiving, by a node in the IGP domain, an IGP advertisement including both (1) a prefix SID and a segment routing global block (SRGB) slice identifier; (b) determining whether or not the SRGB slice identified by the SRGB slice identifier is provisioned on the node; and (c) responsive to a determination that the SRGB slice identified by the SRGB slice identifier is not provisioned on the node, not processing the prefix SID included in the received IGP advertisement, and otherwise responsive to a determination that the SRGB slice identified by the SRGB slice identifier is provisioned on the node, (1) processing the prefix SID and SRGB slice to generate a unique, per SRGB slice, MPLS label for the prefix, and (2) updating a label forwarding information base (LFIB) for the node using the unique, per SRGB slice, label for the prefix and the prefix.

Using and processing per slice segment identifiers in a network employing segment routing

A ring node N belonging to a resilient MPLS ring (RMR) provisions and/or configures clockwise (CW) and anti-clockwise (AC) paths on the RMR by: (a) configuring two ring node segment identifiers (Ring-SIDs) on the ring node, wherein a first of the two Ring-SIDs (CW-Ring-SID) is to reach N in a clockwise direction on the ring and a second of the two Ring-SIDs (AC-Ring-SID) is to reach N in an anti-clockwise direction on the ring, and wherein the CW-Ring-SID and AC-Ring-SID are unique within a source packet routing in networking (SPRING) domain including the ring; (b) generating a message including the ring node's CW-Ring-SID and AC-Ring-SID; and (c) advertising the message, via an interior gateway protocol, for receipt by other ring nodes belonging to the ring such that (1) a clockwise multipoint-to-point path (CWP) is defined such that every other one of the ring nodes belonging to the ring can be an ingress for the CWP and such that only the node is an egress for the CWP, and (2) an anti-clockwise multipoint-to-point path (ACP) is defined such that every other one of the ring nodes belonging to the ring can be an ingress for the ACP and such that only the node is an egress for the ACP.

Resilient multiprotocol label switching (MPLS) rings using segment routing

Techniques are described for managing a plurality of requests for a change in bandwidth for a resource reservation label switched path ('LSP') of a ring network. For example, a method may include receiving, by a network device and from an egress network device of a ring network, a resource reservation request message to establish a multipoint-to-point (MP2P) ring label switched path (LSP). The method may also include modifying, by the network device, the resource reservation request message to specify a request for a change in bandwidth for a segment from the network device to the egress network device of the MP2P ring LSP. The method may also include sending, by the network device and to a downstream network device along the MP2P ring LSP, the modified resource reservation request message.

Bandwidth management for resource reservation label switched path of a ring network

Techniques are described for signaling a resource reservation point-to-multipoint (P2MP) label switched path (LSP) in a ring network. For example, the techniques include sending a single resource reservation request message without the ingress needing to send multiple resource reservation request messages, one for each leaf network device of the P2MP ring LSP. The resource reservation request message includes a leaf identification object from which network devices of a P2MP ring LSP may explicitly or implicitly identify themselves as prospective leaf network devices of the P2MP ring LSP. A network device determined to be a leaf network device may send a resource reservation response message back to the ingress network device of the P2MP ring LSP and send a modified resource reservation request message (if explicit) and/or the same resource reservation request message (if implicit) to a next hop network device along the P2MP ring LSP.

Resource reservation techniques for point-to-multipoint tunnels on a ring network

In one example, a merge point network device (MP) receives a plurality of resource reservation request messages for establishing a plurality of label switched paths (LSPs), wherein each of the plurality of LSPs has a common point of local repair network device (PLR) and has the MP as a common MP, wherein each of the resource reservation request messages identifies a common bypass tunnel that extends between the PLR and the MP and avoids a protected resource. The MP stores an association between the bypass tunnel and each of the plurality of LSPs. The MP receives a single message to trigger creation at the merge point network device of backup LSP state information for all of the plurality of LSPs. In response to receiving the single message, the MP installs state information for all of the LSPs that correspond to the bypass tunnel according to the stored association.

RSVP local protection signaling reduction

Techniques are described for varying a bandwidth constraint at one or more hops along a path of a sub-label-switched path (sub-LSP) of a multi-path label-switched path (MP-LSP). The techniques include computing, by an ingress router, a plurality of paths for a plurality of sub-LSPs of a MP-LSP and outputting, by the ingress router, for each path of the plurality of paths, a respective resource reservation request message to establish a respective sub-LSP of the plurality of sub-LSPs, each respective resource reservation request message including an indication of an explicit route, a tunnel identifier indicating the MP-LSP, an identifier for the respective sub-LSP, an indication of a per-hop bandwidth constraint that corresponds to a respective incoming per-hop bandwidth constraint of the plurality of incoming per-hop bandwidth constraints, and one or more instructions to modify the indication of the per-hop bandwidth constraint.

Growing community of inventors

Wilmington, MA, United States of America

Abhishek Deshmukh