# US 2015/0103835 A1 · System and Method for Routing Using Path Identifiers

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2015/0103835 A1
- Document ID: US20150103835A1
- Status: Published application
- Kind: A1
- Application number: 14/575,196
- Filed: 2014-12-18
- Published: 2015-04-16
- Earliest claimed: 2012-08-28
- Assignees: Cisco Technology, Inc.
- Applicants: Cisco Technology, Inc.
- Inventors: Michael P. Hammer; Ashish Dalela; Monique J. Morrow; Peter C. Tomsu
- Web page: https://patentgrep.com/patent/US20150103835A1

## CPC

- H04L 45/741: Routing in networks with a plurality of addressing schemes, e.g. with both IPv4 and IPv6
- H04L 45/74: Address processing for routing
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

In one embodiment, a method includes receiving a first packet sent by a first node. The packet includes a first Layer 3 source address, a first Layer 3 destination address, a first Layer 2 source hardware identifier, a first Layer 2 destination hardware identifier, and a first path identifier. The first path identifier is situated between a Layer 2 header of the first packet and a Layer 3 header of the first packet. The method includes automatically determining a first port of the first network element associated with a second node. The second node is associated with the first Layer 2 destination hardware identifier. A second path identifier is automatically determined based on the first port. The first packet is prevented from being delivered to the second node in response to determining that the first path identifier and the second path identifier are different.

## Claims

### Claim at position 1

1-20. (canceled)

### Claim 21

A method executed by at least one processor comprising:
receiving, at a first network element, a first packet sent by a first node, the packet comprising a first source address, a first destination address, a first source hardware identifier, a first destination hardware identifier, and a first path identifier;
in response to receiving the first packet, automatically determining a first port of the first network element associated with a second node, the second node associated with the first destination hardware identifier;
automatically determining a second path identifier based on the first port; and
automatically preventing the first packet from being delivered to the second node associated with the first destination hardware identifier in response to determining that the first path identifier and the second path identifier are different.

### Claim 22 (depends on 21)

The method of claim 21, wherein the first network element comprises a switch.

### Claim 23 (depends on 21)

The method of claim 21, further comprising:
determining, at a second network element, the first path identifier based on a port of the second network element that received the first packet; and
inserting, by the second network element, the first path identifier into the first packet.

### Claim 24 (depends on 23)

The method of claim 23, wherein inserting the first path identifier into the first packet comprises adding a header to the first packet, the header comprising the first path identifier.

### Claim 25 (depends on 21)

The method of claim 21, further comprising:
receiving, at the first network element, a second packet after receiving the first packet, the second packet comprising a second source address, a second destination address, a second source hardware identifier, a second destination hardware identifier, and a third path identifier;
automatically determining a fourth path identifier based on a second port of the first network element associated with the second destination hardware identifier; and
automatically causing the first packet to be delivered to a third node associated with the second destination hardware identifier in response to determining that the third path identifier and the fourth path identifier are the same.

### Claim 26 (depends on 21)

The method of claim 21, wherein:
the first destination address is an Internet Protocol (IP) address; and
the first destination hardware identifier is a Media Access Control (MAC) address.

### Claim 27 (depends on 21)

The method of claim 21, wherein the first path identifier is associated with a first service provider and the second path identifier is associated with a second service provider, the first service provider providing a first service using a first data center, the second service provider providing a second service using the first data center.

### Claim 28

Non-transitory computer-readable media comprising instructions that, when executed by a processor, are configured to:
receive a first packet sent by a first node, the packet comprising a first source address, a first destination address, a first source hardware identifier, a first destination hardware identifier, and a first path identifier;
in response to receiving the first packet, automatically determine a first port of a first network element associated with a second node, the second node associated with the first destination hardware identifier;
automatically determine a second path identifier based on the first port; and
automatically prevent the first packet from being delivered to the second node associated with the first destination hardware identifier in response to determining that the first path identifier and the second path identifier are different.

### Claim 29 (depends on 28)

The media of claim 28, wherein the instructions are further configured to:
determine the first path identifier based on a port of the second network element that received the first packet; and
insert the first path identifier into the first packet.

### Claim 30 (depends on 29)

The media of claim 29, wherein the instructions are configured to insert the first path identifier into the first packet by adding a header to the first packet, the header comprising the first path identifier.

### Claim 31 (depends on 28)

The media of claim 28, wherein the instructions are further configured to:
receive a second packet after receiving the first packet, the second packet comprising a second source address, a second destination address, a second source hardware identifier, a second destination hardware identifier, and a third path identifier;
automatically determine a fourth path identifier based on a second port of the first network element associated with the second destination hardware identifier; and
automatically causing the first packet to be delivered to a third node associated with the second destination hardware identifier in response to determining that the third path identifier and the fourth path identifier are the same.

### Claim 32 (depends on 28)

The media of claim 28, wherein:
the first destination address is an Internet Protocol (IP) address; and
the first destination hardware identifier is a Media Access Control (MAC) address.

### Claim 33 (depends on 28)

The media of claim 28, wherein the first path identifier is associated with a first service provider and the second path identifier is associated with a second service provider, the first service provider providing a first service using a first data center, the second service provider providing a second service using the first data center.

### Claim 34

A system comprising:
a first network element configured to receive a first packet sent by a first node, the packet comprising a first source address, a first destination address, a first source hardware identifier, a first destination hardware identifier, and a first path identifier;
wherein the first network element comprises a processor configured to:
in response to receiving the first packet, automatically determine a first port of the first network element associated with a second node, the second node associated with the first destination hardware identifier;
automatically determine a second path identifier based on the first port; and
automatically prevent the first packet from being delivered to the second node associated with the first destination hardware identifier in response to determining that the first path identifier and the second path identifier are different.

### Claim 35 (depends on 34)

The system of claim 34 further comprising:
a second network element comprising a second port configured to receive the first packet, the second network element configured to:
determine the first path identifier based on the second port; and
insert the first path identifier into the first packet.

### Claim 36 (depends on 35)

The system of claim 35, wherein the second network element is configured to insert the first path identifier into the first packet by adding a header to the first packet, the header comprising the first path identifier.

### Claim 37 (depends on 34)

The system of claim 34, wherein:
the first network element comprises a second port;
the first network element is further configured to receive a second packet after receiving the first packet, the second packet comprising a second source address, a second 3 destination address, a second source hardware identifier, a second destination hardware identifier, and a third path identifier; and
wherein the processor is further configured to:
automatically determine a fourth path identifier based on the second port being associated with the second destination hardware identifier; and
automatically cause the first packet to be delivered to a third node associated with the second destination hardware identifier in response to determining that the third path identifier and the fourth path identifier are the same.

### Claim 38 (depends on 34)

The system of claim 34, wherein the first destination address is an Internet Protocol (IP) address and the first destination hardware identifier is a Media Access Control (MAC) address.

### Claim 39 (depends on 34)

The system of claim 34, wherein the first path identifier is associated with a first service provider and the second path identifier is associated with a second service provider, the first service provider providing a first service using a first data center, the second service provider providing a second service using the first data center.
