Handling of received implicit null packets
View Patent ↗A router includes a network ingress processor and a network egress processor. The network ingress processor is configured for modifying a received MPLS packet such that an internal header thereof includes a pre-configured IP flow identifier therein in place of an as-received MPLS flow identifier. Such modifying is performed in response to the network ingress processor parsing a MPLS label stack of the received MPLS packet to determine if an existing MPLS label of the label stack needs to be replaced with an Implicit Null label and in response to determining that there is no other label in the MPLS label stack. The network egress processor includes a flow selector configured for directing packets dependent upon a type of flow identifier included in an internal header thereof, for receiving the modified MPLS packet, and for replacing the internal header with a port-specific header.
1. A method, comprising:
a network ingress processor parsing an Multi-Protocol Label Switching (MPLS) label stack of a received MPLS packet to determine if an existing MPLS label of the MPLS label stack of the received MPLS packet needs to be replaced with an Implicit Null label;
the network ingress processor checking to determine if there is any other MPLS label in the MPLS label stack, wherein said checking is performed in response to the network ingress processor determining that replacement of the existing MPLS label of the existing MPLS label with the Implicit Null label is required;
the network ingress processor providing the received MPLS packet with an internal header including a pre-configured Internet Protocol (IP) flow identifier and thereafter sending said packet to a network egress processor in response to the network ingress processor determining that there is no other MPLS label in the MPLS label stack.
2. The method of claim 1 wherein:
the pre-configured IP flow identifier provides information causing a Layer 2 header configured in accordance with a type of port over which said received MPLS packet is transmitted from a routing apparatus comprising the network egress processor to be appended to the received MPLS packet.
3. The method of claim 2 , further comprising:
providing the network ingress processor with information defining the pre-configured IP flow identifier prior to the network ingress processor performing said parsing.
4. The method of claim 1 , further comprising:
providing the network ingress processor with information defining the pre-configured IP flow identifier prior to the network ingress processor performing said parsing.
5. A network having a plurality of distributed architecture routers therein, comprising:
at least a first one of said plurality of distributed architecture routers configured for modifying a received Multi-Protocol Label Switching (MPLS) packet such that an internal header thereof includes a pre-configured Internet Protocol (IP) flow identifier therein in place of an as-received MPLS flow identifier, wherein said modifying is performed in response to the network ingress processor parsing a MPLS label stack of the received MPLS packet to determine if an existing MPLS label of the MPLS label stack needs to be replaced with an Implicit Null label and in response to determining that there is no other label in the MPLS label stack.
6. The network of claim 5 wherein the pre-configured IP flow identifier information causing a Layer 2 header configured in accordance with a type of port over which said received MPLS packet is transmitted from a second one of said plurality of distributed architecture routers to be appended to said received MPLS packet.
7. The network of claim 6 wherein the first one of said plurality of distributed architecture routers includes information stored thereon that defines the pre-configured IP flow identifier.
8. The network of claim 5 wherein the first one of said plurality of distributed architecture routers includes information stored thereon that defines the pre-configured IP flow identifier.
9. The network of claim 5 , wherein the first one of said plurality of distributed architecture routers is further configured to provide the MPLS packet with a port-specific Layer 2 header dependent on the IP flow identifier.
10. The network of claim 9 , wherein the first one of said plurality of distributed architecture routers is further configured to select routing parameters for the MPLS packet dependent upon the IP flow identifier.
11. A routing apparatus, comprising:
a network ingress processor configured for modifying a received Multi-Protocol Label Switching (MPLS) packet such that an internal header thereof includes a Internet Protocol (IP) flow identifier therein in place of an as-received MPLS flow identifier, wherein said modifying is performed in response to the network ingress processor parsing a MPLS label stack of the received MPLS packet to determine if an existing MPLS label of the MPLS label stack needs to be replaced with an Implicit Null label.
12. The routing apparatus of claim 11 wherein the IP flow identifier provides information causing a Layer 2 header configured in accordance with a type of port over which the packet is transmitted from the routing apparatus to be appended to the received MPLS packet.
13. The routing apparatus of claim 12 wherein the network ingress processor includes information stored thereon that defines the IP flow identifier.
14. The routing apparatus of claim 11 wherein the network ingress processor includes information stored thereon that defines the IP flow identifier.
15. A routing apparatus, comprising:
a network egress processor having a flow selector configured for replacing an internal header of a Multi-Protocol Label Switching (MPLS) with a port-specific Layer 2 header in response to determining that said modified MPLS packet includes an Internet Protocol (IP) flow identifier within its internal header, wherein the IP flow identifier is in place of an as-received MPLS flow identifier of said MPLS packet.
16. The routing apparatus of claim 15 wherein:
said replacing includes selecting routing parameters for said MPLS packet dependent upon the IP flow identifier.
17. The routing apparatus of claim 16 wherein said selecting includes determining that the internal header of said MPLS packet includes the IP flow identifier.
18. The routing apparatus of claim 17 wherein the port-specific Layer 2 header is configured in accordance with a type of port over which said MPLS packet is transmitted from the routing apparatus.