Encapsulating data packets using an adaptive tunnelling protocol

Patent metadata

Field	Value
Publication number	US-9350657-B2
Application number	US-201314069309-A
Country	US
Kind code	B2
Filing date	Oct 31, 2013
Priority date	Jul 8, 2013
Publication date	May 24, 2016
Grant date	May 24, 2016

Abstract

Some embodiments of the invention provide a novel method of tunneling data packets. The method establishes a tunnel between a first forwarding element and a second forwarding element. For each data packet directed to the second forwarding element from the first forwarding element, the method encapsulates the data packet with a header that includes a tunnel option. The method then sends the data packet from the first forwarding element to the second forwarding element through the established tunnel. In some embodiments, the data packet is encapsulated using a protocol that is adapted to change with different control plane implementations and the implementations' varying needs for metadata.

First claim

What is claimed is:

1. For a first forwarding element, a method for processing packets using an adaptive tunnel protocol, the method comprising:
using a particular tunnel protocol to encapsulate a first packet with a first logical context tag header;
using the particular tunnel protocol to encapsulate a second packet with a second logical context tag header, the first logical context tag header having a different length than the second logical context tag header; and
forwarding the first packet to a second forwarding element and the second packet to a third forwarding element.

2. The method of claim 1 further comprising using the particular tunnel protocol to encapsulate each of the first and second packets with a base header that includes a virtual network identifier (VNI).

3. The method of claim 2 , wherein the base headers of the first and second packets have a same size and further comprise at least one of a version number field that identifies a version number of the tunnel protocol, a length field that identifies the length of one or more logical context tags, a critical option field that identifies whether a set of critical options is associated with the one or more logical context tags, and an Operations, Administration, and Management (OAM) frame.

4. The method of claim 1 , wherein at least one of the first, second, and third forwarding elements comprises a managed forwarding element that operates on a host machine and implements a set of logical forwarding elements of one or more logical networks.

5. The method of claim 1 further comprising using the particular tunnel protocol to encapsulate each of the first and second packets with an additional header that has a same size in both of the first and second packets.

6. The method of claim 1 , wherein a logical context tag comprises at least one of (i) a type field that identifies the format of the first logical context tag, (ii) a length field that identifies the length of the first logical context tag, (iii) a critical option field for dropping the packet if any of the first and second forwarding elements does not recognize the logical context tag, and (iv) a set of option control flags for processing the logical context tag.

7. The method of claim 1 , wherein a logical context tag of the first logical context tag header has a different size than a logical context tag of the second logical context tag header.

8. The method of claim 1 , wherein each logical context tag is specified in a Type-Length-Value format.

9. A non-transitory machine readable medium storing a program that when executed by at least one processing unit processes data packets sent from a first forwarding element using an adaptive tunnel protocol, the program comprising sets of instructions for:
using a particular tunnel protocol to encapsulate a first packet with a first logical context tag header;
using the particular tunnel protocol to encapsulate a second packet with a second logical context tag header, the first logical context tag header having a different length than the second logical context tag header; and
forwarding the first packet to a second forwarding element and the second packet to a third forwarding element.

10. The non-transitory machine readable of claim 9 , wherein the set of instructions for using the tunnel protocol to encapsulate the first and second packets further comprises a set of instructions for adding to each of the first and second packets a base header that includes a virtual network identifier (VNI).

11. The non-transitory machine readable of claim 10 , wherein the base headers of the first and second packets have a same size and further comprise at least one of a version number field that identifies a version number of the tunnel protocol, a length field that identifies the length of one or more logical context tags, a critical option field that identifies whether a set of critical options is associated with the one or more logical context tags, and an Operations, Administration, and Management (OAM) frame.

12. The non-transitory machine readable of claim 9 , wherein a logical context tag in each of the first and second logical context tag headers comprises a type field that identifies the format of the first logical context tag, a length field that identifies the length of the logical context tag, a critical option field for dropping the packet if an of the first and second forwarding elements does not recognize the logical context tag, and a set of option control flags for processing the logical context tag.

13. A non-transitory machine readable medium storing a program that when executed by at least one processing unit processes data packets using an adaptive tunnel protocol, the program comprising sets of instructions for:
receiving a first plurality of packets from a first end machine to be forwarded to a second end machine via a first forwarding element;
for each packet in the first plurality of packets, using the adaptive tunnel protocol to encapsulate the packet with a first logical context tag header having a first length and sending the packet to the first forwarding element;
receiving a second plurality of packets from a third end machine to be forwarded to a fourth end machine via a second forwarding element; and
for each packet in the second plurality of packets, using the adaptive tunnel protocol to encapsulate the packet with a second logical context tag header having a second length, different from the first length, and sending the packet to the second forwarding element.

14. The non-transitory machine readable of claim 13 , wherein the adaptive tunnel protocol further specifies a base header that includes a virtual network identifier (VNI).

15. The non-transitory machine readable of claim 13 , wherein each of the first, second, and third forwarding elements comprises a managed forwarding element that implements a set of logical forwarding elements, wherein the first and second end machines are logically connected by a first logical forwarding element in the set of logical forwarding elements, while the third and fourth end machines are logically connected by a second logical forwarding element in the set of logical forwarding elements.

Assignees

• Nicira Inc

Inventors

• Gross Iv Jesse E
• Koponen Teemu
• Lambeth W Andrew

Classifications

• H04L2212/00

  Encapsulation of packets · CPC title

• H04L12/4633 Primary

  Interconnection of networks using encapsulation techniques, e.g. tunneling · CPC title

• H04L12/4641

  Virtual LANs, VLANs, e.g. virtual private networks [VPN] (LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272) · CPC title

• H04L45/74 Primary

  Address processing for routing · CPC title

• H04L69/324

  in the data link layer [OSI layer 2], e.g. HDLC · CPC title