Method for performing protocol translation in a network switch

1. A method, comprising:

receiving, by a network device comprising at least one processor, a packet via an ingress link interface of the network device; and

converting, by the network device, the packet from a protocol-specific format, of a set of protocol-specific formats supported by the network device, to a canonical packet format yielding a canonical packet,

wherein the canonical packet format is configured to be translated to any of the set of protocol-specific formats and comprises at least a multiple protocol-specific field associated with a first field that is common to multiple protocol-specific formats of the set and a protocol-specific field associated with a second field that is specific exclusively to one protocol-specific format of the set.

2. The method of claim 1 , wherein the canonical packet further comprises a shared field configured to contain at least a first value associated with a third field of one of the protocol-specific formats and a second value associated with a fourth field of another of the protocol-specific formats, wherein the first field is different than the second field.

3. The method of claim 2 , wherein the converting comprises:

in response to determining that the protocol-specific format comprises the third field, copying the first value of the third field from the packet to the shared field of the canonical packet; and

in response to determining that the protocol-specific format comprises the fourth field, copying the second value of the fourth field from the packet to the shared field of the canonical packet.

4. The method of claim 1 , wherein the set of protocol-specific formats comprises at least one of an asynchronous transfer mode format, a frame relay format, an Ethernet format, or a multi-protocol label switching format.

5. The method of claim 1 , wherein the converting comprises:

in response to determining that the protocol-specific format is one of the multiple protocol-specific formats, writing first information from the first field of the packet to the multiple protocol-specific field of the canonical packet; and

in response to determining that the protocol-specific format is the one protocol-specific format, writing second information from the second field of the packet to the protocol-specific field of the canonical packet.

6. The method of claim 2 , wherein the converting comprises:

in response to determining that the protocol-specific format is the one of the protocol-specific formats, copying the first value from the third field of the packet to the shared field of the canonical packet; and

in response to determining that the protocol-specific format is the other of the protocol-specific formats, copying the second value from the fourth field of the packet to the shared field of the canonical packet.

7. The method of claim 1 , wherein the protocol-specific format comprises a first protocol-specific format, and the method further comprises converting the canonical packet from the canonical packet format to a second protocol-specific format of the set of protocol-specific formats yielding a converted packet.

8. The method of claim 7 , further comprising forwarding the converted packet to an egress link interface of the network device.

9. A device, comprising:

an ingress interface configured to receive a packet in a protocol-specific format of a plurality of protocol-specific formats supported by the device; and

an ingress processing engine configured to convert the packet from the protocol-specific format to a generic packet format to yield a generic packet configured to be translated from the generic packet format to any of the plurality of protocol-specific formats,

wherein the generic packet format comprises at least a multiple protocol-specific field corresponding to a first field that is common to more than one of the plurality of protocol-specific formats, and a protocol-specific field corresponding to a second field that is specific to only one of the plurality of protocol-specific formats.

10. The device of claim 9 , further comprising a pooling switch configured to communicatively couple the ingress interface to the ingress processing engine.

11. The device of claim 9 , further comprising a fabric switch configured to communicatively connect the ingress processing engine with another processing engine of the device.

12. The device of claim 9 , wherein the generic packet format further comprises a common field configured to be shared between a third field of a first protocol-specific format of the plurality of protocol-specific formats and a fourth field of a second protocol-specific format of the plurality of protocol-specific formats.

13. The device of claim 12 , wherein the ingress processing engine is configured to convert the packet by:

in response to determining that the protocol-specific format is the first protocol-specific format, writing a first value of the third field of the packet to the common field of the generic packet; and

in response to determining that the protocol-specific format is the second protocol-specific format, writing a second value of the fourth field of the packet to the common field of the generic packet.

14. The device of claim 9 , wherein the plurality of protocol-specific formats comprise at least one of an asynchronous transfer mode format, a frame relay format, an Ethernet format, or a multi-protocol label switching format.

15. The device of claim 9 , wherein the ingress processing engine is configured to

in response to determining that the protocol-specific format comprises the first field, write a first value of the first field of the packet to the multiple protocol-specific field of the generic packet; and

in response to determining that the protocol-specific format comprises the second field, write a second value of the second field of the packet to the protocol-specific field of the generic packet.

16. The device of claim 9 , further comprising an egress processing engine configured to convert the generic packet from the generic packet format to one of the plurality of protocol-specific formats to yield a converted packet.

17. A non-transitory computer-readable medium having stored thereon instructions that, in response to execution, cause a network device to perform operations, comprising:

receiving a packet via an ingress link interface of the network device; and

translating a packet from a protocol-specific format, of a set of protocol-specific formats supported by the network device, to a canonical packet format to yield a canonical packet configured to be translated to any of the set of protocol-specific formats,

wherein the canonical packet format comprises at least a multiple protocol-specific field corresponding to a first field that is common to multiple protocol-specific formats of the set and a protocol-specific field corresponding to a second field that is specific exclusively to one protocol-specific format of the set.

18. The non-transitory computer-readable medium of claim 17 , wherein the operations further comprise:

in response to determining that the packet comprises the first field, writing first information from the first field of the packet to the multiple protocol-specific field; and

in response to determining that the packet comprises the second field, writing second information from the second field of the packet to the protocol-specific field.

19. The non-transitory computer-readable medium of claim 17 , wherein the protocol-specific format is a first protocol-specific format, and the operations further comprise translating the canonical packet from the canonical packet format to a second protocol-specific format of the set of protocol-specific formats to yield a converted packet.

20. The non-transitory computer-readable medium of claim 17 , wherein the set of protocol-specific formats comprises at least one of an asynchronous transfer mode format, a frame relay format, an Ethernet format, or a multi-protocol label switching format.