Abstract:
A computer-implemented method, in a content delivery (CD) network. The method includes: receiving a request regarding a first hostname including at least one tag and an encoding of the at least one address; removing the tag and the encoding of the address to form a second hostname; resolving the second hostname to obtain a set of one or more addresses, wherein the set does not include the at least one address; and returning the address set. On a client, the method includes: making a request for resolution of a first hostname; receiving one or more addresses; attempting to connect to at least one of the addresses; generating a modified hostname including at least one tag and an encoding of the at least one address; and requesting resolution of the modified hostname.
Abstract:
The present invention is directed to a method for providing secure dynamic address resolution and communication directly between two nodes, without communication to third party DNS and/or MX server (s). A first a second node are initially paired, which may include the identification of an authentication scheme and creating a DNS record with the current address of the other node, the address of the other node may be dynamically updated. Further secure transmission of messages may be implemented, which include first resolving based on the DNS record a current address of the other node, authentication the destination node, and transmitting a message upon successful authentication. Dynamic message encryption and the provision of a DNS cache may further be implemented.
Abstract:
One embodiment provides Subnet administrator (SA) proxy logic to be executed by a computer network node. The SA proxy logic includes provider logic that includes path record information of an associated subnet in communication with the computer network node; and provider interface logic to receive an address resolution request from at least one application that includes partial address information. The provider interface logic is also to determine at least one local port of the computer network node to enable packet routing associated with the address resolution request. The provider logic is also to determine at least one subnet associated with the address resolution request. The provider interface logic is also to determine at least one provider logic to utilize to obtain the path record information for at least one subnet associated with the address resolution request. The provider interface logic is also to generate an address resolution response that includes a resolved address, that includes the path record information, and the identity of at least one local port to enable the at least one application to route data packets through the at least one determined subnet.
Abstract:
A network controller may rewrite an address resolution request and an address resolution response. The address resolution request may be rewritten by changing a request source link address to a link address of a first switch. The address resolution response may be rewritten by changing a response source link address to a link address of a second switch.
Abstract:
A method in gateway node (100) for handling an address of a resource of a device (110) in a communications network, the method comprising: generating a first alias representing the address of the device (110) resource,storing the generated alias, in association with the address, receiving a request from an application (120) including the address of the device (110) resource,translating the address to the stored alias, and forwarding the request including the alias to the device (110), thereby enabling the device to resolve the request by use of the alias in said request.
Abstract:
For routing a data unit through a chain of nodes (101, 102, 103, 104, 105, 106, 10i,..., 10N), the nodes are assigned addresses (1, 2, 3, 4, 5, 6, i, N) that are increasing in one direction of appearance of the nodes in the chain. For routing the data unit, the receiving node (103) first verifies if the destination address of the data unit corresponds with the address (2, 4, 1, 5) of its first hop neighbour (102, 104) or its second hop neighbour (101, 105), and the node (103) routes the data unit directly to its first hop neighbour (102, 104) or its second hop neighbour (101, 105) if this is the case. Otherwise, the node (103) determines the difference between the destination address of the data unit and its own address (3) or the difference between the source and destination address of the data unit, selects a routing direction depending on the sign of this difference, and selects a first hop link (132, 134) when the difference is in magnitude below a threshold value or a second hop link (131, 135) when the difference is above the threshold value.
Abstract:
Data traffic between a user at a user equipment (10) and a network resource (80) is preceded by a lookup procedure for obtaining a network address of the network resource (80). A message (203) of the lookup procedure is processed depending on a class of users to which the user belongs. If the user belongs to a first class of users, the message (203) of the lookup procedure is processed for adapting the lookup procedure to return a first network address of a replacement network resource (60) capable of handling the data traffic. If the user belongs to a second class of users, the message (203) of the lookup procedure is processed for adapting the lookup procedure to return a second network address of a replacement network resource (60) capable of handling the data traffic. The second network address is different from the first network address. The first network address matches a packet filter for directing the data traffic to a bearer and the second network address does not match this packet filter, but may rather match another packet filter.