Root Identifier

Abstract: Methods and systems anchor hypertext transfer protocol (HTTP) level communication in an information-centric networking (ICN) network. Both content requests and responses to servers within the ICN network and to servers located outside the ICN network, in an IP network for example, are disclosed. Communication may be between two IP capable only devices at the HTTP level, one connected to an ICN network while the other one is connected either to an ICN or IP network. The disclosed namespace 200 enables IP based HTTP communication within the ICN network. An information-centric networking (ICN) network attachment point (NAP) or border gateway (BGW) may receive an HTTP request packet and encapsulate the received HTTP request packet. The ICN NAP/BGW may then forward the HTTP request packet towards the local ICN network servers. The HTTP request packet may be published to a named content identifier (CID) that may be determined through a hash function of a fully qualified domain name (FQDN). The ICN NAP may receive a HTTP response packet for a subscribed information item, which may be included in a named rCID. The named rCID may be determined through a hash function of a uniform resource locator (URL). Instead of using the hash of a URL and an FQDN directly, a separate scope identifier, which may be a root identifier, may be chosen for HTTP-over-ICN communication for the overall ICN namespace. The scope identifier may include a particular structure for the ICN namespace being built up. Using a root identifier may allow for separating HTTP-over-ICN communication from other ICN communication, for example, for operational or migration reasons. Under the root scope identifier, there may be two sub-scope identifiers, a first sub-scope identifier (I) for communication within the ICN network and a second sub-scope identifier (O) for communication to IP addresses outside the ICN network. The ICN may be based on the PURSUIT publish-subscribe architecture or on the Named Data Networking (NDN) project and the like.

Abstract: A method and a bridge operative to notify other bridges connected to a network of a root bridge failure by detecting a failure in a connection to the root bridge and generating a root failure suspicion notification (RFSN) bridge protocol data unit (BPDU) that includes a standard Rapid Spanning Tree BPDU portion and a failed root identifier portion uniquely identifying the root bridge which is suspected of failing. The bridge propagates the RFSN BPDU to adjacent bridges in the network to notify them of the failure.

Abstract: FIELD: radio engineering, communication.SUBSTANCE: system includes at least one first area connected through at least one area border node ("ABN") to a second area; each ABN has a first level port connected to each first area and a second level port connected to the second area; each multicast packet forwarded includes a header having a root identifier identifying a root of a multicast tree; a data packet is received at an ABN; in response to receiving a multicast packet at a second level port of an area border node, the root identifier of the multicast packet is analysed and if the multicast packet is to be forwarded to at least one of the first level ports, a different root identifier is inserted into the packet before the packet is forwarded to the first level port.EFFECT: reduced probability of looping when forwarding packets in a network with multiple areas.20 cl, 7 dwg

Abstract: The invention relates to a computer-implemented method for user authentication using a cryptographically secured register. An authentication request for authenticating the user is received. The user is authenticated using a root identity of the user. A successful authentication requires receiving a credential assigned to a root identifier of the root identity of the user. An authentication context of the requested authentication is identified. One of the one or more delegated identities assigned to the root identity of the user and assigned to the identified authentication context is identified. In response to a successful authentication of the user, an authentication token is issued confirming the successful user authentication and identifying the successfully authenticated user by the delegated identifier of the identified delegated identity.