Forwarding plane configuration for separation of services and forwarding in an integrated services router

A network device comprising:

• a line interface, the line interface being in a forwarding plane and including:
• a processor to:
• receive a packet at the line interface,
• determine whether an existing flow can be identified for the packet by conducting a flow table lookup for the packet,
• determine whether a predicted flow can be identified for the packet when the existing flow cannot be identified for the packet,
• conduct an access control list (ACL) lookup when the predicted flow cannot be identified for the packet,
• determine whether the flow table lookup, the predicted flow, or the ACL lookup indicates a need for service processing for the packet, and
• forward the packet to an egress line interface of the forwarding plane when the flow table lookup, the predicted flow, or the ACL lookup does not indicate the need for service processing for the packet,
• the egress line interface determining whether the predicted flow or another predicted flow can be determined for the packet.

A network element comprising:

• one or more processors to:
• receive a packet at an egress line interface of a forwarding plane;
• determine that a service has not been performed on the packet in a services plane;
• determine whether an existing flow can be identified for the packet;
• determine whether a predicted flow can be determined for the packet when the existing flow cannot be identified for the packet;
• conduct an egress services policy lookup for the packet when the predicted flow cannot be determined for the packet;
• and
• forward, after determining that the service has not been performed on the packet, the packet to a services plane based on the existing flow, the predicted flow, or the egress services policy lookup.

A method comprising:

• receiving, by a network device, a packet at an egress line interface in the forwarding plane of the network device;
• determining, by the network device, that a service has not been performed on the packet in a services plane of the network device;
• determining, by the network device, whether an existing flow can be identified for the packet by conducting a flow table lookup;
• determining, by the network device and when the existing flow cannot be identified for the packet, whether a predicted flow can be determined for the packet;
• conducting, by the network device, an egress services policy lookup when the predicted flow cannot be determined for the packet;
• and
• forwarding, by the network device and after determining that the service has not been performed on the packet, the packet to a service engine distributor based on the flow table lookup, the predicted flow, or the egress services policy lookup.

A network device comprising:

• a services plane;
• and
• a forwarding plane comprising:
• an egress line interface to:
• receive a packet from an ingress line interface,
• determine that a service has not been performed on the packet in the services plane,
• determine whether an existing flow can be identified for the packet by conducting a flow table lookup,
• determine whether a predicted flow can be identified for the packet when the existing flow cannot be identified,
• perform a service access control list (ACL) lookup when the predicted flow cannot be identified, and
• forward, after determining that the service has not been performed, the packet to the services plane based on the existing flow, the predicted flow, or the service ACL lookup.