Abstract: A first message is sent from a first node in a network indicating that a first quantum element at the first node is entangled with a second quantum element at a second node in the network. The first message comprises a first estimate of a fidelity of entanglement between the first and second quantum elements, and a timestamp indicating a time associated with the first estimate. Based at least in part on the first message, a second estimate of a fidelity of the entanglement between the first and second quantum elements is generated, at a second time after the time indicated by the timestamp, and is compared to each of multiple thresholds. At least a first (second) action is performed in response to a result of comparing the second estimate to a first (second) threshold.

Abstract: A network device may receive an instruction to update a data structure implemented by the network device and update the data structure based on receiving the instruction. The data structure may include a routing instruction to direct the network device to provide a data flow to a server device for processing. The network device may receive the data flow destined for a destination device; determine the routing instruction based on at least a portion of an internet protocol (IP) address associated with the data flow and based on the data structure; execute the routing instruction to provide the data flow to the server device and to cause the data flow to be processed by the server device to form a processed data flow; and receive the processed data flow and provide the processed data flow towards the destination device.

Abstract: A quantum element (QE) at a network node stores a first quantum state constituent (QSC) of an entangled quantum state characterized by a non-factorable quantum relationship among QSCs comprising the first QSC and a second QSC stored at another QE at another network node. Managing one or more quantum error management (QEM) operations includes: (1) providing a schedule for the QEM operations that is based at least in part on at least a portion of a time over which the first QSC is stored at the first QE and an estimated fidelity of the entangled quantum state after at least one of the QEM operations, or (2) providing a type of one or more QEM operations selected from two or more different types based at least in part on a number of resource quantum elements available at the first node after the first QSC is stored at the first QE.

Abstract: A first message is sent from a first node in a network indicating that a first quantum element at the first node is entangled with a second quantum element at a second node in the network. The first message comprises a first estimate of a fidelity of entanglement between the first and second quantum elements, and a timestamp indicating a time associated with the first estimate. Based at least in part on the first message, a second estimate of a fidelity of the entanglement between the first and second quantum elements is generated, at a second time after the time indicated by the timestamp, and is compared to each of multiple thresholds. At least a first (second) action is performed in response to a result of comparing the second estimate to a first (second) threshold.

Abstract: A first (second) message is sent from a controller in a network to a first (second) node in the network. The first (second) message comprises at least a portion of scheduling information that specifies a procedure to be executed for scheduling entanglement swap operations associated with portions of a plurality of paths through nodes in the network. At least a portion of the procedure is executed at the first node based at least in part on the first message and information associated with one or more previous attempts to establish entanglement between nodes on a first path that includes the first node. At least a portion of the procedure is executed at the second node based at least in part on the second message and information associated with one or more previous attempts to establish entanglement between nodes on a second path that includes the second node.

Abstract: At a first node in a network, a first (second) message is received indicating that a first (second) quantum element at the first node is entangled with a quantum element at a second (third) node in the network. The first (second) message comprises a first (second) identifier that uniquely identifies one of a plurality of entanglement generation operations between the first and second (third) nodes over a first time period. At the first node, a third identifier is generated that identifies an entanglement resulting from an entanglement swap operation based on the entangled quantum elements at the first and second nodes and the entangled quantum elements at the first and third nodes. At least a portion of the first identifier is included in the third identifier, and at least a portion of the second identifier is included in the third identifier.

Abstract: A network device may receive an instruction to update a data structure implemented by the network device and update the data structure based on receiving the instruction. The data structure may include a routing instruction to direct the network device to provide a data flow to a server device for processing. The network device may receive the data flow destined for a destination device; determine the routing instruction based on at least a portion of an internet protocol (IP) address associated with the data flow and based on the data structure; execute the routing instruction to provide the data flow to the server device and to cause the data flow to be processed by the server device to form a processed data flow; and receive the processed data flow and provide the processed data flow towards the destination device.

Abstract: A network device may receive an instruction to update a data structure implemented by the network device and update the data structure based on receiving the instruction. The data structure may include a routing instruction to direct the network device to provide a data flow to a server device for processing. The network device may receive the data flow destined for a destination device; determine the routing instruction based on at least a portion of an internet protocol (IP) address associated with the data flow and based on the data structure; execute the routing instruction to provide the data flow to the server device and to cause the data flow to be processed by the server device to form a processed data flow; and receive the processed data flow and provide the processed data flow towards the destination device.

Abstract: A network device may receive an instruction to update a data structure implemented by the network device and update the data structure based on receiving the instruction. The data structure may include a routing instruction to direct the network device to provide a data flow to a server device for processing. The network device may receive the data flow destined for a destination device; determine the routing instruction based on at least a portion of an internet protocol (IP) address associated with the data flow and based on the data structure; execute the routing instruction to provide the data flow to the server device and to cause the data flow to be processed by the server device to form a processed data flow; and receive the processed data flow and provide the processed data flow towards the destination device.

Abstract: In general, techniques are described for defining an interface to a network router software infrastructure that allows developers to dynamically extend a routing protocol executed by the network router to distribute data throughout the routing domain for use with custom applications. In some examples, a routing protocol process executing on a control plane of a network device may expose an interface, such as an Application Programming Interface (API), that defines methods and parameters for extending the operation of a routing protocol executed by the routing protocol process.

Abstract: A network device may receive information regarding a service set identifying service to apply to a data flow received via a particular interface of the network device; receive the data flow via the particular interface; identify a service to provide to the data flow based on the information regarding the service set; identify a processing device to process the data flow; and provide the data flow to the processing device. The processing device may be different than the network device and may process the data flow, on behalf of the network device, to form a processed data flow. The processed data flow may include the data flow with the service applied to the data flow. The network device may further receive the processed data flow from the processing device and transmit the processed data flow toward a destination device.

Abstract: A distributed computing system includes a primary device and one or more backend devices. The primary device provides a management interface for the distributed computing system. A plurality of applications may be installed on the backend devices for execution. The primary device generates registration data that associates the applications with management interface commands or configuration parameters in response to messages received from the applications. Subsequently, when the primary device receives a particular command at the management interface, the primary device identifies, based on the registration data, a particular application from among the plurality of applications. In response to identifying the application, the primary device may send to the application an outgoing message.

Abstract: A network device may receive information regarding a service set identifying service to apply to a data flow received via a particular interface of the network device; receive the data flow via the particular interface; identify a service to provide to the data flow based on the information regarding the service set; identify a processing device to process the data flow; and provide the data flow to the processing device. The processing device may be different than the network device and may process the data flow, on behalf of the network device, to form a processed data flow. The processed data flow may include the data flow with the service applied to the data flow. The network device may further receive the processed data flow from the processing device and transmit the processed data flow toward a destination device.

Abstract: A device may be configured to receive information regarding one or more ports associated with a routing device; output, to the routing device, filter information associated with at least a particular port, of the one or more ports associated with the routing device, the filter information specifying one or more conditions associated with traffic of interest; receive, from the routing device, and based on the outputted filter information, information regarding traffic of interest received or sent by the routing device via the particular port, the traffic of interest being less than or equal to all traffic received or sent by the routing device via the particular port; and store or output a representation of at least a portion of the received information regarding the traffic of interest.

Abstract: A network device may receive information regarding a service set identifying service to apply to a data flow received via a particular interface of the network device; receive the data flow via the particular interface; identify a service to provide to the data flow based on the information regarding the service set; identify a processing device to process the data flow; and provide the data flow to the processing device. The processing device may be different than the network device and may process the data flow, on behalf of the network device, to form a processed data flow. The processed data flow may include the data flow with the service applied to the data flow. The network device may further receive the processed data flow from the processing device and transmit the processed data flow toward a destination device.

Abstract: A device may be configured to receive information regarding one or more ports associated with a routing device; output, to the routing device, filter information associated with at least a particular port, of the one or more ports associated with the routing device, the filter information specifying one or more conditions associated with traffic of interest; receive, from the routing device, and based on the outputted filter information, information regarding traffic of interest received or sent by the routing device via the particular port, the traffic of interest being less than or equal to all traffic received or sent by the routing device via the particular port; and store or output a representation of at least a portion of the received information regarding the traffic of interest.

Abstract: A device may be configured to receive information regarding one or more ports associated with a routing device; output, to the routing device, filter information associated with at least a particular port, of the one or more ports associated with the routing device, the filter information specifying one or more conditions associated with traffic of interest; receive, from the routing device, and based on the outputted filter information, information regarding traffic of interest received or sent by the routing device via the particular port, the traffic of interest being less than or equal to all traffic received or sent by the routing device via the particular port; and store or output a representation of at least a portion of the received information regarding the traffic of interest.

Abstract: In general, techniques are described for defining an interface to a network router software infrastructure that allows developers to dynamically extend a routing protocol executed by the network router to distribute data throughout the routing domain for use with custom applications. In some examples, a routing protocol process executing on a control plane of a network device may expose an interface, such as an Application Programming Interface (API), that defines methods and parameters for extending the operation of a routing protocol executed by the routing protocol process.

Abstract: A network device may receive information regarding a service set identifying service to apply to a data flow received via a particular interface of the network device; receive the data flow via the particular interface; identify a service to provide to the data flow based on the information regarding the service set; identify a processing device to process the data flow; and provide the data flow to the processing device. The processing device may be different than the network device and may process the data flow, on behalf of the network device, to form a processed data flow. The processed data flow may include the data flow with the service applied to the data flow. The network device may further receive the processed data flow from the processing device and transmit the processed data flow toward a destination device.

Abstract: A distributed computing system includes a primary device and one or more backend devices. The primary device provides a management interface for the distributed computing system. A plurality of applications may be installed on the backend devices for execution. The primary device generates registration data that associates the applications with management interface commands or configuration parameters in response to messages received from the applications. Subsequently, when the primary device receives a particular command at the management interface, the primary device identifies, based on the registration data, a particular application from among the plurality of applications. In response to identifying the application, the primary device may send to the application an outgoing message.