Interface discovery and authentication in a name-based network

• US 10,212,196 B2
• Filed: 03/16/2016
• Issued: 02/19/2019
• Est. Priority Date: 03/16/2016
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Fox, Kevin C., Scott, Glenn C.
• Primary Examiner(s): Fan, Hua
• Application Number:
  US15/072,230
• Publication Number:
  US 20170272473A1
• Time in Patent Office: 1,070 Days
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

One embodiment provides an interface discovery system that facilitates interface discovery and authentication. During operation, the system receives a message from an unregistered interface via a local interface of a link adapter. The message can include a name. If the system determines that a source identifier of the message is not configured for a channel, the system generates a control message comprising the source identifier and an identifier of the local interface and sends the control message via a transport stack of the system.

Claims

1. A computer-implemented method, comprising:

receiving, by a local interface of a link adapter of a node, a message from an unregistered interface, wherein the message includes a name, a source identifier indicating the unregistered interface, and a destination identifier indicating a destination interface for the message;

determining whether the destination identifier is assigned to the local interface;

determining whether the source identifier is known to the link adapter; and

in response to determining that the destination identifier is assigned to the local interface and the source identifier is unknown to the link adapter;

discarding the message at the link adapter;

generating a control message comprising the source identifier and an identifier of the local interface; and

sending the control message via a transport stack of the node to configure a channel with the source identifier.

2. The method of claim 1, further comprising:

authenticating the source identifier; and

configuring the channel between the local interface and the unregistered interface associated with the source identifier.

3. The method of claim 1, wherein the name in the message is based on one or more of:

a hierarchically structured variable-length identifier (HSVLI), which comprises contiguous name components ordered from a most general level to a most specific level, wherein the HSVLI is applicable in a portal instance corresponding to the stack;

a flat name that does not indicate any hierarchy;

a role of a component of the stack; and

a unique identifier, which is specific to the component of the stack.

4. The method of claim 1, further comprising logging contents of the control message in an activity log of the node.

5. The method of claim 4, further comprising receiving an administrative command based on the activity log, wherein the administrative command includes authenticating the source identifier and configuring the channel with the source identifier.

6. The method of claim 1, wherein the message is a request for establishing a tunnel as the channel;

wherein the method further comprises;

authenticating a tunnel between the local interface and the unregistered interface; and

configuring the tunnel as the channel.

7. The method of claim 1, wherein the source identifier is one or more of:

a media access control (MAC) address, an Internet Protocol (IP) address, a network label, and a name.

8. A non-transitory computer-readable storage medium storing instructions that when executed by a computer cause the computer to perform a method, the method comprising:

receiving, by a local interface of a link adapter of a node, a message from an unregistered interface, wherein the message includes a name, a source identifier indicating the unregistered interface, and a destination identifier indicating a destination interface for the message;

determining whether the destination identifier is assigned to the local interface;

determining whether the source identifier is known to the link adapter; and

in response to determining that the destination identifier is assigned to the local interface and the source identifier is unknown to the link adapter;

discarding the message at the link adapter;

generating a control message comprising the source identifier and an identifier of the local interface; and

sending the control message via a transport stack of the node to configure a channel with the source identifier.

9. The storage medium of claim 8, wherein the method further comprises:

authenticating the source identifier; and

configuring the channel between the local interface and the unregistered interface associated with the source identifier.

10. The storage medium of claim 8, wherein the name in the message is based on one or more of:

a hierarchically structured variable-length identifier (HSVLI), which comprises contiguous name components ordered from a most general level to a most specific level, wherein the HSVLI is applicable in a portal instance corresponding to the stack;

a flat name that does not indicate any hierarchy;

a role of a component of the stack; and

a unique identifier, which is specific to the component of the stack.

11. The storage medium of claim 8, wherein the method further comprises logging contents of the control message in an activity log of the node.

12. The storage medium of claim 11, wherein the method further comprises receiving an administrative command based on the activity log, wherein the administrative command includes authenticating the source identifier and configuring the channel with the source identifier.

13. The storage medium of claim 8, wherein the message is a request for establishing a tunnel as the channel;

wherein the method further comprises;

authenticating a tunnel between the local interface and the unregistered interface; and

configuring the tunnel as the channel.

14. The storage medium of claim 8, wherein the source identifier is one or more of:

a media access control (MAC) address, an Internet Protocol (IP) address, a network label, and a name.

15. A computer system for facilitating forwarding of packets, the system comprising:

a processor; and

a storage device storing instructions that when executed by the processor cause the processor to perform a method, the method comprising;

receiving, by a local interface of a link adapter of a node, a message from an unregistered interface, wherein the message includes a name, a source identifier indicating the unregistered interface, and a destination identifier indicating a destination interface for the message;

determining whether the destination identifier is assigned to the local interface;

determining whether the source identifier is known to the link adapter; and

in response to determining that the destination identifier is assigned to the local interface and the source identifier is unknown to the link adapter;

discarding the message at the link adapter;

generating a control message comprising the source identifier and an identifier of the local interface; and

sending the control message via a transport stack of the node to configure a channel with the source identifier.

16. The computer system of claim 15, wherein the method further comprises:

authenticating the source identifier; and

configuring the channel between the local interface and the unregistered interface associated with the source identifier.

17. The computer system of claim 15, wherein the name in the message is based on one or more of:

a hierarchically structured variable-length identifier (HSVLI), which comprises contiguous name components ordered from a most general level to a most specific level, wherein the HSVLI is applicable in a portal instance corresponding to the stack;

a flat name that does not indicate any hierarchy;

a role of a component of the stack; and

a unique identifier, which is specific to the component of the stack.

18. The computer system of claim 15, wherein the method further comprises logging contents of the control message in an activity log of the node.

19. The computer system of claim 18, wherein the method further comprises receiving an administrative command based on the activity log, wherein the administrative command includes authenticating the source identifier and configuring the channel with the source identifier.

20. The computer system of claim 15, wherein the message is a request for establishing a tunnel as the channel;

wherein the method further comprises;

authenticating a tunnel between the local interface and the unregistered interface; and

configuring the tunnel as the channel.