Juniper Networks, Inc.

Srihari Ramachandra Sangli

Jonathan C Barth

Chandrasekar Ramachandran

Shraddha Hegde

Tarek Saad

Vishnu Pavan Beeram

Kireeti Kompella

Zhaohui Zhang

Swamy Sadashivaiah Renu Kananda

Jeffrey M Haas

Raveendra Torvi

Ashish Kumar

Ronald P Bonica

Kaliraj Vairavakkalai

Sandip Kumar Ghosh

Sri Karthik Goud Gadela

Harmeet Singh

Jimmy Jose

Rajesh Shetty Manur

Amit Arora

Swamy Sadashivaiah Kananda

Vishnu Pavan Kumar Beeram

Rafal Jan Szarecki

Santosh S Kolenchery

Wai Tong Louis Chan

Vasudevan Navaneetha Krishnan

Krzysztof Grzegorz Szarkowicz

Srikanth Venakta Gandiboyina

A network device may receive an MPLS packet destined for a destination via a label-switched path (LSP), and may determine whether to apply a first special purpose label (SPL) option or a second SPL option for a label stack of the MPLS packet. The network device may apply, when the first SPL option is determined to be applied, one of a first type of the first SPL option for the label stack via a policy data indicator (PDI) and policy data (PD), or a second type of the first SPL option for the label stack via the PDI and the PD. The network device may forward the MPLS packet to a hop of the LSP based on the first type of the first SPL option or the second type of the first SPL option applied to the MPLS packet.

Encoding forwarding policy data in multiprotocol label switching (MPLS) labels

A first network device may create a port group for a plurality of links directly connected to a second network device, and may select the first network device as a controller network device and the second network device as a worker network device. The first network device may rank the plurality of links of the port group to generate a list of ranked links, and may select, from the list of ranked links, a highest ranked link as a control channel. The first network device may power off one or more of the plurality of links, except the control channel, based on one of a configuration, a policy, or a traffic prediction, and may identify a termination of a time period associated with powering off the one or more of the plurality of links. The first network device may power on the one or more of the plurality of links based on the termination of the time period.

Power optimization using dynamic bandwidth management between connected network devices

The techniques describe network slicing in computer networks. For example, a node receives a slice policy definition. The slice policy definition comprising a slice selector to identify packets belonging to one or more network slices, referred to as a 'slice aggregate,' and one or more network resource requirements for the slice aggregate to meet one or more Service Level Objectives (SLOs). The node configures, based on the slice policy definition, a path for the slice aggregate that complies with the one or more network resource requirements. In response to receiving a packet, the node determines whether the packet is associated with the slice aggregate and, in response to determining that the packet is associated with the slice aggregate, forwards the packet along the path for the slice aggregate.

Network slicing including modeling, distribution, traffic engineering and maintenance

A network device may receive a border gateway protocol (BGP) flow specification route associated with creation of an overlay network slice in a network, and may create a new routing instance based on the BGP flow specification route. The network device may associate interfaces defined by the BGP flow specification route with virtual private network (VPN) members, and may determine VPN parameters based on the BGP flow specification route. The network device may advertise the VPN parameters within the network to cause the network to generate the overlay network slice.

Dynamic creation of overlay network slices using border gateway protocol flow specifications

Techniques are described by which a routing protocol, such as border gateway protocol (BGP), is extended to control propagation and importation of information using route targets (RTs) specified as bitmasks that encode link administrative group information. For example, a network control device (e.g., controller) is configured to allocate one or more subset of resources (e.g., nodes or links) of an underlay network to each of one or more virtual networks established over the underlay network. The controller generates a bitmask encoded with link administrative group information of the one or more links. The controller then outputs, to a plurality of provider edge (PE) routers that are participating in a respective virtual network, a routing protocol message to advertise the one or more subset of resources, wherein the routing protocol message includes a route target specified as the bitmask.

Bitmask route target in targeted distribution of information using a routing protocol

Techniques are described for using route target constraint to filter routes advertised to a node in a seamless Multiprotocol Label Switching (MPLS) network. For example, a first router of a first network may generate a first border gateway protocol (BGP) message to advertise routing information for a first node of the first network, the first BGP message indicating a transport class and specifying an address-specific route target, the transport class comprising one or more tunnels to the first node that share common characteristics. In response to receiving a second BGP message originated by second node of a second network, the second BGP message comprising the address-specific route target, the first router sends the first BGP message to a second router of the second network for sending to the second node to cause the second node to import the routing information.

Route target constraint to filter routes advertised to a node in a seamless MPLS or seamless SR network

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

In general, this disclosure describes a network device that checks consistency between routing objects in a routing information base (RIB), a forwarding information base (FIB), and packet forwarding engine (PFE) forwarding tables. A method includes generating a marker that causes a routing protocol daemon, a control plane kernel, and PFEs of a network device to calculate zonal checksums for a plurality of zones using consistency values for each routing object within a RIB, a FIB, and corresponding forwarding tables respectively. The method includes performing a consistency check on the RIB, the FIB, and the forwarding tables to determine whether the routing objects in each of the RIB, the FIB, and the forwarding tables are consistent with each other. The method includes, when the RIB, the FIB, and the forwarding tables are not consistent, performing an action related to at least one of RIB, the FIB, or the forwarding tables.

Route consistency checker for network devices

The use and processing of update messages (e.g., BGP UPDATEs) that bind (e.g., MPLS) labels to address prefixes is improved such that labels are used more efficiently, and/or such that such update messages can be processed more efficiently. A distance vector control signaling protocol (e.g., BGP) peer device receives a control plane message (e.g., BGP Update) from a downstream peer device, the control plane message including (1) a network address of the downstream device as a next hop value, (2) a prefix value, and (3) at least one label associated with the prefix value. Responsive to receiving the control plane message, the peer device generates a new control plane message including (1) a network address of the peer device as a next hop value, (2) the prefix value from the control plane message, and (3) a label stack including (i) the at least one label from the control plane message, and (ii) a local label associated with the peer device. The peer device then sends the new control plane message to an upstream peer device.

Building a label sequence in Border Gateway Protocol (BGP) labeled network layer reachability information (NLRI) on next hop (NH) attribute change

Growing community of inventors

Bengaluru, India

Srihari Ramachandra Sangli