Juniper Networks, Inc.

Ronald P Bonica

Kireeti Kompella

Reji Thomas

Shraddha Hegde

Zhaohui Zhang

Rajesh Shetty Manur

Raveendra Torvi

Tarek Saad

Vishnu Pavan Beeram

Ramakrishna Manjunath

Parag Kaneriya

Swamy Sadashivaiah Renu Kananda

Yimin Shen

Sri Karthik Goud Gadela

Abhishek Deshmukh

William Britto Arimboor Joseph

Prashanth Ramaprasad

Madhu Byrapura Doddegowda

Alexander Arseniev

Jonathan C Barth

Manoj Nayak

Rafik Puttur

Ajay Kachrani

Srihari Ramachandra Sangli

Manish Talwar

Salih K A

Jonathan T Looney

Deepti Nirmalkumarji Rathi

A network node may receive a packet that originated from a root network node and may process the packet to determine segment identifier (SID) information associated with a point-to-multipoint transport chain. The network node may determine, based on the SID information, that the network node is a transit leaf node in the point-to-multipoint transport chain. The network node may generate, based on determining that the network node is a transit leaf node in the point-to-multipoint transport chain, a copy of the packet and may process the copy of the packet to perform one or more actions. The network node may update, based on determining that the network node is a transit leaf node in the point-to-multipoint transport chain, the SID information and may send, after updating the SID information, the packet, with the updated SID information, to another network node.

Point-to-multipoint transport chain

In some implementations, a first network device may receive an advertisement from a second network device. The advertisement may be associated with indicating that the second network device is configured to support a particular flex-algorithm. The first network device may identify, in the advertisement, an address of the second network device. The first network device may configure a routing table of the first network device to indicate that the second network device is capable of receiving traffic associated with the particular flex-algorithm based on the address. The first network device may perform, using the routing table, an action associated with routing the traffic associated with the particular flex-algorithm.

Configuration of a network using a flex-algorithm routing mechanism

A network device may receive a non-Internet protocol (non-IP) frame with a particular size and may compare the particular size to a maximum transmission unit (MTU) associated with a path between the network device and another network device. The network device may divide the non-IP frame into fragments, based on the particular size being greater than the MTU and may prepend generic fragmentation headers to the fragments to generate fragments with headers, based on the particular size being greater than the MTU. The network device may add generic fragmentation header labels and transport labels to the fragments with the headers to generate fragments with headers and labels, based on the particular size being greater than the MTU. The network device may transmit the fragments with the headers and the labels to the other network device, via the path, based on the particular size being greater than the MTU.

Generic layer independent fragmentation of non-internet protocol frames

In some implementations, a network device may determine, based on a routing table, a plurality of routing paths from the network device to another network device, wherein the plurality of routing paths are respectively associated with a plurality of security classifications. The network device may receive network traffic that is destined for the other network device and that is associated with a particular security classification of the plurality of security classifications. The network device may forward the network traffic based on a particular routing path, of the plurality of routing paths, that is associated with the other network device and the particular security classification.

Forwarding network traffic associated with a security classification via a routing path associated with the security classification

A network device may receive an internet protocol (IP) packet that includes an IP packet header. The IP packet may include at least one extension header, which includes at least one of: a hop-by-hop options header, a first destination options header that precedes a routing header, or a second destination options header that precedes an upper-layer header. The network device may determine that: the hop-by-hop options header includes an Operations and Management capabilities (OAM) option, the first destination options header includes the OAM option and an IP address of the network device matches a destination IP address or a routing IP address identified in the routing header, or the second destination options header includes the OAM option and the IP address of the network device matches the destination IP address. The network device may perform one or more actions indicated by the OAM option.

Internet protocol operations and management option

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

A node receives an internet protocol (IP) payload packet that includes an IPv6 transport header that has been extended with a compressed routing header (CRH). The CRH includes a list of segment identifiers (SIDs) that identify nodes that the IP payload packet is to traverse. The node determines, by referencing the list of SIDs, a next segment for the IP payload packet. The node updates a destination IP address that is included in the IPv6 transport header to a particular destination IP address of a next-hop node. The node updates a remaining segments value, included in the CRH, that identifies a number of segments left in a route of the IP payload packet. The node provides the IP payload packet to the next-hop node to allow the next-hop node to route the IP payload packet to another node in the network or to a destination device.

Compressed routing header

This disclosure describes techniques relating to assigning unique segment identifiers (SIDs) in a segment routing network. In one example, this disclosure describes a method that includes receiving, by a computing system and from a node on a network, a request to allocate a segment identifier for use in a segment routing network; allocating, by the computing system and from a block of addresses, an assigned segment identifier; responding to the request by outputting, by the computing system and over the network to the node, information about the assigned segment identifier; and maintaining the assigned segment identifier.

Assignment of segment identifiers in segment routing

A network device may receive a message. The network device may determine that the message includes return information indicating a path to an initial device that generated the message. The network device may modify the message by adding an upstream device identifier, wherein the upstream device identifier identifies a device from which the message is received. The network device may modify the message by adding an indication of whether the initial device is reachable by the network device using a segment identifier. The network device may provide the modified message to a downstream device.

Inter-autonomous system trace route message

This disclosure describes techniques that include determining, at an egress node in an SRm6 network, how to process a packet that may arrive without a segment routing header and/or a compressed routing header. In one example, this disclosure describes a method that includes receiving, by an egress node of a segment routing network, segment routing advertisements; configuring, by the egress node and based on the segment routing advertisements, information enabling the egress node to recognize encapsulated packets arriving at the egress node without a compressed routing header; receiving, by the egress node, a packet that does not have a compressed routing header; and de-encapsulating, by the egress node and based on the stored information, the packet.

Processing a flow at the egress node in segment routing

A tactical solution to network congestion is provided by a data forwarding device having (1) a first interface with a first link to a downstream data forwarding device and (2) second interface with a second link to a downstream data forwarding device, and executing a method comprising: (a) configuring the second interface as part of a loop-free alternate (LFA) path to a destination device, wherein the first interface is part of a shortest/preferred path to the destination device; (b) monitoring congestion at the first interface to determine whether or not the congestion exceeds a first threshold; and (c) responsive to a determination that the congestion exceeds the first threshold, forwarding at least some data addressed to the destination device, over the LFA path via the second interface instead of over the shortest/preferred path via the first interface, thereby alleviating congestion at the first interface, and otherwise, responsive to a determination that the congestion does not exceed the first threshold, not forwarding at least some data addressed to the destination device, over the LFA path via the second interface instead of over the shortest/preferred path via the first interface.

Distributed tactical traffic engineering (TE) using loop free alternative (LFA), remote-LFA (R-LFA) and/or topology independent-LFA (TI-LFA) secondary paths

A node may receive a network topology message that identifies a first association of a first segment identifier (SID), relating to a loosely routed segment of a network, and an address of a first terminal interface associated with the loosely routed segment, or a second association of a second SID, relating to a strictly routed segment of the network, and an address of a second terminal interface associated with the strictly routed segment. The node may generate an entry in a segment translation table based on the first association or the second association. The node may route, according to the segment translation table, an internet protocol (IP) payload packet that has been encapsulated using an IPv6 transport header that has been extended with a compressed routing header of variable length.

Growing community of inventors

Sterling, VA, United States of America

Ronald P Bonica