H04L12/745

Directory Assisted Routing of Content in an Information Centric Network
20210099536 · 2021-04-01 · ·

A method is disclosed. The method includes: obtaining, by an authoritative directory router in an information centric network (ICN), a publish message associated with a publisher node and including: an identifier associated with a content item; and a first anchor prefix for a first anchor directory router for the publisher node; determining that a bidirectional code for the identifier falls within an authoritative code range assigned to the authoritative directory router; and updating, in response to the bidirectional code falling within the authoritative code range, a local code repository associated with the authoritative directory router with the first anchor prefix and the identifier.

METHODS AND DEVICES FOR BLOCKING, DETECTING, AND/OR PREVENTING MALICIOUS TRAFFIC
20210136075 · 2021-05-06 ·

A network device obtains information, associated with blacklisted domains, that includes blacklisted domain identifiers, and sinkhole server identifiers associated with the blacklisted domain identifiers. The network device obtains a set of rules that specify match criteria, associated with the blacklisted domains, that include source network addresses and/or destination network addresses for comparison to packet source network addresses and/or packet destination network addresses associated with incoming packets. The set of rules specify actions to perform based on a result of comparing the match criteria and the packet source network addresses and/or the packet destination network addresses for the incoming packets. The network device receives packets, examines a packet source network address and/or a packet destination network address associated with the packets, compares the packet source network address and/or the packet destination network address to the match criteria, and performs an action based on a result of the comparison.

ADDRESS PROCESSING METHOD AND NETWORK DEVICE
20210144093 · 2021-05-13 ·

This application provides an address processing method and a network device. The method includes: obtaining, by a first network device, an address; determining, by the first network device, a length of a valid address of the address, where the valid address of the address is a 1.sup.st bit, whose bit value is 1, of the address to a last bit of the address; and adding, by the first network device when the length of the valid address of the address is less than a table width of a target table, S zeros before the valid address of the address to obtain an adjusted address, and processing the adjusted address based on the adjusted address and the target table, where S is a difference between the table width of the target table and the length of the valid address of the address.

LABEL FORWARDING ENTRY GENERATION METHOD AND APPARATUS, PACKET SENDING METHOD AND APPARATUS, AND DEVICE
20210119917 · 2021-04-22 ·

This application provides an example label forwarding entry generation method, applied to a first network device. The method includes obtaining a first packet sent by a second network device, where the first packet carries an address of a third network device and a prefix segment identifier of the third network device, the first network device and the second network device belong to a first area, and the third network device belongs to a second area. The method also includes determining a routing entry that matches the address of the third network device, where the routing entry includes an address of a next-hop network device of the first network device. The method further includes generating a label forwarding entry based on the prefix segment identifier and the address of the next-hop network device.

Forwarding table management
11012358 · 2021-05-18 · ·

Disclosed herein are system, method, and computer program product embodiments for representing a forwarding information base (FIB) in a database. An embodiment operates by organizing forwarding entries of the FIB in a trie data structure. The embodiment determines that a first routing prefix of a first forwarding entry in the trie data structure is a less specific routing prefix than a second routing prefix in a second forwarding entry in the trie data structure based on the first forwarding entry being a parent of the second forwarding entry. The embodiment determines that a first next hop of the first routing prefix is equal to a second next hop of the second routing prefix. The embodiment removes the second forwarding entry from the trie data structure. The embodiment then inserts the first forwarding entry into the database based on a prefix length of the first routing prefix.

ASSOCIATING ROUTE TABLES WITH INGRESS TRAFFIC TO LOGICALLY ISOLATED NETWORKS
20210135991 · 2021-05-06 · ·

Route tables may be associated with ingress traffic for logically isolated networks. A routing device at the edge of a logically isolated network may receive a route to include in a route table that is associated with ingress traffic to the logically isolated network to forward the ingress traffic to a network appliance hosted in the logically isolated network. Network packets received at the edge routing device may have a destination of a computing resource hosted in the logically isolated network. The edge routing device may identify the route in the route table to override the destination in the network packet with the network appliance and forward the network packet to the network appliance according to the route.

TUNNEL-BASED ROUTING CALCULATION WITH ADDRESS EXCLUSION IN SOFTWARE DEFINED NETWORKING (SDN) ENVIRONMENTS
20210144083 · 2021-05-13 ·

Example methods and network devices for tunnel-based routing calculation. One example method may comprise establishing a tunnel between a first tunnel interface and a second tunnel interface; establishing a first session for routing information exchange between a first tunnel endpoint and an underlay network device; establishing a second session for routing information exchange between the first tunnel interface and the second tunnel interface over the tunnel. In response to receiving first routing information over the first session, the underlay network device may be configured to be a next hop to reach the second tunnel endpoint by updating a routing table to include a first entry. In response to receiving second routing information from the second tunnel interface over the second session, the underlay network device may be retained as the next hop based on an excluded address specified in the second routing information.

Content delivery from home networks

A method for retrieving content on a network comprising a first device and a second device is described. The method includes receiving in the network a request for content from the first device, the request identifying the content using an IPv6 address for the content, and determining whether the content is stored in a cache of the second device. Upon determining the content is stored in the cache of the second device, a request is sent to the second device for the content using the IPv6 address of the content. The content is forwarded to the first device from the second device, wherein the first and second devices are part of the same layer 2 domain. Methods of injecting content to a home network and packaging content are also described.

Generating a hash table in accordance with a prefix length

Examples herein disclose a generation of a hash table. The examples identify a prefix length from a routing table of various prefix lengths and corresponding distribution of entries. The identified prefix length corresponds to a larger distribution of entries in the routing table. The examples generate the hash table in accordance with the identified prefix length.

Communication between distinct network domains

A system may include a first border network device located between a first network domain and a third network domain, and a first edge network device in the first network domain, where the first edge network device may be configured to receive a packet. The packet may be directed to a second edge network device in a second network domain. The first edge network device may also be configured to add a second label to the packet that identifies a second border network device located at the border of a second network domain and the third network domain. The third network domain may be located between the first network domain and the second network domain. The first edge network device may additionally be configured to add a first label to the packet that identifies the first border network device, and route the packet to the first border network device.