Abstract:
A method implemented by a network element (NE), comprising receiving a classification message comprising a classification rule for identifying a service function chain (SFC) in a network, wherein the SFC comprises an ordered set of service functions (SFs) that provides services to an application, and a dynamic application-specific contextual data associated with an operation of the application, receiving a first of a plurality of application data packets, determining that the first of the application data packets matches the classification rule, generating a first SFC packet by adding the dynamic application-specific contextual data to the first of the application data packets according to the classification rule to enable communication of the dynamic application-specific contextual data to at least one of the SFs in the SFC, and sending the first SFC packet towards a next NE according to an SF path in the network associated with the SFC.
Abstract:
Metadata may be embedded in a service chain header (SCH) appended to a packet that is forwarded over a service chain path. The metadata may include information that is used to process the packet at a downstream service function chain (SFC) entity on the service chain path. The metadata TLV field may identify a service action to be performed by a downstream SFC entity. For example, the metadata TLV field may instruct the downstream SFC entity to drop the packet, to redirect the packet (or a traffic flow associated with the packet), to mirror a traffic flow, to terminate a communication connection, to start or stop a packet accounting, and/or to apply a higher grade of service. In another embodiment, the metadata TLV field specifies an OAM service action list that identifies service actions that have been performed on the packet.
Abstract:
Packets of data can be processed by a chain or sequence of service functions which include both virtual and physical service functions. In one approach, the original header and/or payload of a packet is analyzed at a software switch to determine whether the packet should be processed by the chain. If such processing is indicated, a next service function to process the packet is identified. The packet is then forwarded to a virtualized or physical device which implements the next service function. A portion of the header, such as a MAC destination address, may be modified to direct the packet to the next function. Further, in some cases, a service function chain (SFC) header with a chain identifier may be added to, or removed from, the packet.
Abstract:
A method implemented by a path computation element (PCE), comprising receiving a path computation request to compute a network path for a source-destination pair in a service chain (SC) network, wherein the path computation request comprises at least one network routing constraint and a service function (SF) input associated with a plurality of SFs, computing a plurality of network paths through the network for the source-destination pair according to the network routing constraint, selecting at least a first of the network paths according to the SF input, and sending a path computation response indicating at least the first network path in response to the received path computation request.
Abstract:
A method implemented by a path computation element (PCE), comprising receiving a path computation request to compute a network path for a source-destination pair in a service chain (SC) network, wherein the path computation request comprises at least one network routing constraint and a service function (SF) input associated with a plurality of SFs, computing a plurality of network paths through the network for the source-destination pair according to the network routing constraint, selecting at least a first of the network paths according to the SF input, and sending a path computation response indicating at least the first network path in response to the received path computation request.
Abstract:
A method for bridging communication between a plurality of Virtual eXtensible Local Area Network (VXLAN) networks, wherein the method comprises joining the VXLAN networks, obtaining a forwarding entry table that associates a plurality of endpoints with a plurality of VXLAN tunnel endpoints (VTEPs) within the VXLAN networks, receiving a VXLAN encapsulated data packet from one of the VXLAN networks, and transmitting the VXLAN encapsulated data packet using the forwarding entry table to a different VXLAN network.
Abstract:
Dynamically by-passing a service function instance on a service chain after the service function instance has processed the first few packets of a traffic flow may improve the overall processing efficiency of the service chain. When using a control plane mechanism, a service function instance communicates a by-pass indication to a control plane entity to prompt the control plane entity to re-route remaining portions of the traffic flow around the service function instance. When using a data plane mechanism, a service function instance includes a by-pass indication in a service chain header (SCH) of a packet in a traffic flow, and forwards the packet to a data plane entity. The by-pass indication will prompt the data plane entity to re-route remaining portions of the traffic flow around the service function instance.
Abstract:
Metadata may be embedded in a service chain header (SCH) appended to a packet that is forwarded over a service chain path. The metadata may include information that is used to process the packet at a downstream service function chain (SFC) entity on the service chain path. The metadata TLV field may identify a service action to be performed by a downstream SFC entity. For example, the metadata TLV field may instruct the downstream SFC entity to drop the packet, to redirect the packet (or a traffic flow associated with the packet), to mirror a traffic flow, to terminate a communication connection, to start or stop a packet accounting, and/or to apply a higher grade of service. In another embodiment, the metadata TLV field specifies an OAM service action list that identifies service actions that have been performed on the packet.
Abstract:
In a network switch of a software-defined network (SDN) architecture, a method for improving cache replacement (CR) efficiency implemented therein, the method comprising maintaining a flow table comprising a plurality of flow entries, computing a replacement index (RI) value for each of the plurality of flow entries resulting in a plurality of RI values, wherein computing an RI value for a flow entry is at least partially based on latency sensitivity of a forwarding path specified by the flow entry, and generating, based on at least some of the computed RI values, an eviction list comprising a number of list entries, wherein each of the list entries points to one of at least a fraction of the flow entries.
Abstract:
System and method embodiments are disclosed here to resolve Internet Protocol (IP) address overlap of Virtual eXtensible Local Area Network (VXLAN) endpoints in packets forwarded between the VXLAN and an external or public network. An embodiment method includes assigning different port number ranges to different virtual private networks of the VXLAN, mapping private IP addresses for endpoints at the virtual private networks to corresponding public IP addresses known to a public network, and mapping local ports of the endpoints to corresponding port numbers from the port number ranges assigned to the virtual private networks, wherein each of the endpoints at the virtual private networks is assigned to a unique combination of public IP address and port number. The mapping can be done at a VXLAN gateway or at the endpoints on physical servers of the virtual private networks.