Abstract: A method of establishing streams within a QUIC connection implemented by a first network device, comprising: transmitting a first open message through the QUIC connection to a second network device, the first open message identifying a protocol; receiving a second open message through the QUIC connection from the second network device in response to transmitting the first open message, the second open message identifying the protocol; and establishing a first stream between the first network device and the second network device within the QUIC connection for the protocol identified in the first open message and in the second open message.

Abstract: A method performed by a network node of a receiving autonomous system (AS) for verifying that a sending AS is authorized to issue a Border Gateway Protocol (BGP) flow specification (FlowSpec). The network node receives a BGP update message from a sending AS. The BGP update message includes a FlowSpec associated with a prefix of an AS. The network node obtains an out-of-band Flowspec AS authorization list indicating autonomous systems (ASes) that are authorized to issue the FlowSpec for the prefix of the AS. The network node determines whether the sending AS is included on the out-of-band Flowspec AS authorization list for the prefix of the AS. The network node rejects the FlowSpec when the sending AS is not on the out-of-band FlowSpec AS authorization list for the prefix of the AS.

Abstract: A method implemented by a network element (NE) in a network, comprising receiving, by the NE, preferred path route (PPR) information comprising a PPR identifier (PPR-ID) and a plurality of PPR-Path Description Elements (PPR-PDEs), wherein a PPR-PDE describing the egress NE comprises a destination flag, an anycast PPR-ID, and an anycast group PPR-ID associated with the egress NE, and updating, by the NE, a forwarding database to include a forwarding entry for the egress NE, wherein the forwarding entry includes the PPR-ID, the anycast PPR-ID, and the anycast group PPR-ID, and wherein the forwarding entry indicates a next element on the PPR graph by which to forward an anycast data packet comprising the anycast PPR-ID.

Abstract: This disclosure relates to transmitting data packets from a source to a destination within a communications network. A data packet is received from the source located in a local sub-network of the network. The data packet includes a first network layer protocol header having a source address containing the local sub-network address of the source, a destination address of the destination, a first field indicating a length of the source address and a second field indicating a length of the destination address. The first network layer protocol header is transformed by modifying the source address and the first field indicating the length of the source address, such that the modifying includes appending to the local sub-network address a prefix of the sub-network to make the source address an address of a higher-level network. The data packet is then forwarded toward the destination in the higher-level network.

Abstract: A method performed by a first node of a first autonomous system (AS) for verifying that a second node of a second AS is authorized to issue a Border Gateway Protocol (BGP) flow specification (FlowSpec). The first node receives from a third node of third AS a first BGP update message that includes a FlowSpec AS authorization list indicating autonomous systems (ASes) that are authorized to issue a FlowSpec for the prefix of the third AS. The first node receives, from the second node of the second AS, a second BGP update message that includes a FlowSpec associated with the prefix of the third AS. The first node determines whether the FlowSpec AS authorization list includes the second AS. The network node rejects the FlowSpec when the FlowSpec AS authorization list does not include the second AS.

Abstract: An edge routing device at an edge of a network including a memory storing instructions one or more processors. The one or more processors are configured to execute the instructions to determine that an edge routing capability of the edge routing device has been updated, encode an updated edge routing capability into a type length value (TLV) structure of a link state message, and flood the link state message including the TLV structure having the updated edge routing capability to other edge routing devices at the edge of the network.

Abstract: A method implemented by a network element (NE) in a network, comprising receiving, by the NE, an advertisement comprising preferred path route (PPR) information representing a PPR from a source to a destination in the network, the PPR information comprising a PPR identifier (PPR-ID) and a plurality of PPR description elements (PPR-PDEs) each representing an element on the PPR, receiving, by the NE, a data packet comprising the PPR-ID, and forwarding, by the NE, the data packet having the PPR-ID to a next element on the PPR based on the plurality of PPR-PDEs.

Abstract: A method used by a domain name system (DNS) server is disclosed. The DNS server receives a DNS request containing a host name and a resource record specifying data. The DNS server resolves an internet protocol (IP) address based on the host name. The DNS server resolves a server address of a resource server containing the data specified in the resource record. The DNS server transmits a DNS response including the IP address and the server address.

Abstract: A method implemented by a network element (NE) in a network, comprising receiving, by the NE, preferred path route (PPR) information describing a PPR graph, the PPR graph representing a plurality of PPRs between an ingress NE and an egress NE in the network, and updating, by the NE, a forwarding database to include a forwarding entry for the egress NE in response to identifying the NE in the plurality of PPR-PDEs, the forwarding entry indicating a next hop by which to forward a data packet comprising the PPR-ID.

Abstract: A method of establishing streams within a QUIC connection implemented by a first network device, comprising: transmitting a first open message through the QUIC connection to a second network device, the first open message identifying a protocol; receiving a second open message through the QUIC connection from the second network device in response to transmitting the first open message, the second open message identifying the protocol; and establishing a first stream between the first network device and the second network device within the QUIC connection for the protocol identified in the first open message and in the second open message.

Abstract: A DNS server comprises: a receiver configured to receive a registration request comprising a domain name, a local address, and a scope, the registration request requests registration of the domain name; a processor coupled to the receiver and configured to execute computer instructions that cause the processor to: assign an address to the domain name based on the local address and the scope, and generate a registration response comprising the address; and a transmitter coupled to the processor and configured to transmit the registration response towards an endpoint. The processor may be further configured to cache a correspondence among the domain name, the address, and the scope.

Abstract: A routing device including a memory and a processor. The memory stores instructions. The processor is configured to execute the instructions to receive a signed route origin authorization (ROA), which includes a blockchain hash, and a border gateway protocol (BGP) update message, which includes one or more routes. The processor is further configured to implement a Route Origin Validation (ROV) process using the blockchain hash in the signed ROA to determine whether the one or more routes in the BGP update message are valid; update a routing table to include the one or more routes from the BGP update message when the one or more routes are determined to be valid by the ROV process; and refrain from updating the routing table with the one or more routes from the BGP update message when the one or more routes are determined to be invalid by the ROV process.

Abstract: This disclosure relates to transmitting data packets from a source to a destination within a communications network. A data packet is received from the source located in a local sub-network of the network. The data packet includes a first network layer protocol header having a source address containing the local sub-network address of the source, a destination address of the destination, a first field indicating a length of the source address and a second field indicating a length of the destination address. The first network layer protocol header is transformed by modifying the source address and the first field indicating the length of the source address, such that the modifying includes appending to the local sub-network address a prefix of the sub-network to make the source address an address of a higher-level network. The data packet is then forwarded toward the destination in the higher-level network.

Abstract: A Self-Describing Packet block (SDPB) is defined that allows concurrent processing of various fixed headers in a packet block defined to take advantage of multiple cores in a networking node forwarding path architecture. SPDB allows concurrent processing of various pieces of header data, metadata, and conditional commands carried in the same data packet by checking a serialization flag set upon creation of the data packet, without needing to serialize the processing or even parsing of the packet. When one or h more commands in one or more sub-blocks may be processed concurrently, the one or more commands are distributed to multiple processing resources for processing the commands in parallel. This architecture allows multiple unique functionalities each with their own separate outcome (execution of commands, doing service chaining, performing telemetry, allows virtualization and path steering) to be performed concurrently with simplified packet architecture without incurring additional encapsulation overhead.

Abstract: The disclosure includes a method of performing congestion control by a server device in a network. The method includes setting an effective window equal to a congestion window; sending traffic including the effective window to a client device; receiving an acknowledgment (ACK) from the client device; incrementing the congestion window if the ACK is not a duplicate; and updating the effective window based at least partly on the incremented congestion window.

Abstract: A method implemented by a network element (NE) in a network, comprising receiving, by the NE, an advertisement comprising preferred path route (PPR) information and backup PPR information, the PPR information describing a PPR between a source and a destination in the network, the backup PPR information describing a backup PPR between the source and the destination, the PPR information comprising a PPR identifier (PPR-ID) and a plurality of PPR description elements (PPR-PDEs) each representing an element on the PPR, updating, by the NE, a local forwarding database to include the PPR information and the backup PPR information in association with a destination address of the destination, and transmitting, by the NE, a data packet based on the backup PPR information instead of the PPR information in response to an element on the PPR being unavailable due to a failure of an element along the PPR.

Abstract: A method implemented by a network element (NE) in a network receiving, by the NE, an advertisement comprising preferred path route (PPR) information describing a path from an ingress NE to an egress NE in the network, the PPR information comprising a PPR identifier (PPR-ID) and an attribute associated with a resource to be reserved on the PPR, transmitting, by the NE, the advertisement comprising the PPR-ID and the attribute associated with the resource to be reserved on the PPR to another NE in the network, and updating, by the NE, a local forwarding database to include the PPR information in association with the egress NE in response to the NE being identified in the PPR information.

Abstract: A method of routing a data packet through a network comprises updating at least one router local forwarding table to include path IDs of network segments defining paths between network nodes and network function bit encoding/decoding information. In response to a data packet arriving at an ingress network node, an encapsulation header including a path ID identifying at least one network segment of an explicit routing path and a bit encoding specifying network functions to be performed on the data packet are encapsulated in unused portions of the source address and/or the destination address in the encapsulation header. A network node in the explicit routing path performs a network function encoded in the source address and/or the destination address of the encapsulation header of the data packet and forwards the data packet based on network function bit encoding/decoding and path ID information in the network node's local updated local forwarding table.

Abstract: A method implemented by an end user device in a network, comprises transmitting user service expectation data to a network element (NE) in the network, the user service expectation data describing an expected network attribute of a path between the end user device and a destination, receiving path aware network data from the NE in response to transmitting the user service expectation data describing the expected network attribute to the NE, the path aware network data comprising a path index, path quality information, and data plane information, the path index identifying the path, the path quality information describing a network attribute supported by the NE on the path, and the data plane information comprising information associated with a protocol by which to transmit a data packet along the path, and transmitting the data packet along the path based on the data plane information.

Abstract: An apparatus includes a network interface for connection to a network and a database configured to store traffic shaping parameters for a traffic shaping scheme for a plurality of classes of data packets. A database loading circuit is configured to obtain the traffic shaping parameters from in-band communication received in a data packet by the network interface and load the traffic shaping parameters into the database. One or more traffic shapers are configured to access the traffic shaping parameters in the database and apply the traffic shaping scheme according to the traffic shaping parameters to the plurality of classes of data packets received by the network interface.