Infrastructure-exclusive service forwarding

Abstract

A method is provided in one example embodiment and includes receiving at a network element a packet including a Network Services Header (“NSH”), in which the NSH includes an Infrastructure (“I”) flag and a service path header comprising a Service Index (“SI”), and a Service Path ID (“SPI”) and determining whether the I flag is set to a first value. The method further includes, if the I flag is set to the first value, setting the I flag to a second value and forwarding the packet to the service function that corresponds to the SI for processing. The method still further includes, if the I flag is not set to the first value, decrementing the SI and making a forwarding decision based on a new value of the SI and the SPI.

Description

TECHNICAL FIELD

This disclosure relates in general to the field of communications networks and, more particularly, to a technique for performing infrastructure-exclusive service forwarding in such communications networks.

BACKGROUND

The delivery of end-to-end services in a communications network often requires the performance of a variety of service functions. Such service functions may include, but are not limited to, firewalls and traditional IP Network Address Translators (“NATs”), as well as application-specific functions. The definition and instantiation of an ordered set of service functions and the subsequent steering of traffic through those functions is referred to as service function chaining (“SFC”), or simply service chaining. In the process, the traffic is serviced as per policy in the service functions and the service chaining infrastructure. Existing methods of forwarding traffic through service functions suffer from various deficiencies, including but not limited to, complexity of deployment and operation due to a large number of forwarding touch points; scale challenges due to the involvement of service functions in making forwarding decisions, and violation of operational environment policies due to errors or unintentional modification of forwarding state by service functions.

BRIEF DESCRIPTION OF THE DRAWINGS

To provide a more complete understanding of the present disclosure and features and advantages thereof, reference is made to the following description, taken in conjunction with the accompanying figures, wherein like reference numerals represent like parts, in which:

FIG. 1A is an SFC-enabled domain, which may include an initial classification function as an entry point into a service function path, in accordance with embodiments described herein;

FIG. 1B illustrates a simplified block diagram of a service function chain, which may include an initial classification function as an entry point into a service function path, in accordance with embodiments described herein;

FIG. 1C illustrates a simplified block diagram of another service function chain, which may include an initial classification function as an entry point into a service function path, in accordance with embodiments described herein;

FIG. 2A is a simplified block diagram of a first type of service function chain-aware network element for prescribing a service path of a traffic flow in accordance with embodiments described herein;

FIG. 2B is a simplified block diagram of a second type of service chain function-aware network element for forwarding a traffic flow as prescribed in accordance with embodiments described herein;

FIG. 3 is a simplified block diagram of a service node in accordance with embodiments described herein;

FIG. 4 illustrates two example service paths in accordance with embodiments described herein;

FIG. 5 illustrates an example packet structure in accordance with embodiments described herein;

FIG. 6 illustrates an example arrangement of base and service headers in accordance with embodiments described herein;

FIG. 7 illustrates a revised arrangement of base and service headers in accordance with embodiments described herein;

FIG. 8 illustrates a difference between a service function overlay and a service infrastructure overlay in accordance with embodiments described herein;

FIG. 9A illustrates a flowchart showing a method that may be implemented at an initial classifier function, such as the network element of FIG. 2A, in accordance with embodiments described herein;

FIG. 9B illustrates a flowchart showing a method that may be implemented at a forwarding element, such as the network element of FIG. 2B, in accordance with embodiments described herein;

FIG. 10 is a system block diagram showing an example of a typical packet flow in accordance with embodiments described herein; and

FIG. 11 is a simplified block diagram of a machine comprising an element of a communications network in which techniques for infrastructure-exclusive service forwarding in accordance with embodiments described herein may be implemented.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

Overview

A method is provided in one example embodiment and includes receiving at a network element a packet including a Network Services Header (“NSH”), wherein the NSH includes an Infrastructure (“I”) flag and a service path header comprising a Service Index (“SI”), and a Service Path ID (“SPI”) and determining whether the I flag is set to a first value. The method further includes, if the I flag is set to the first value, setting the I flag to a second value and forwarding the packet to the service function that corresponds to the SI for processing. The method still further includes, if the I flag is not set to the first value, decrementing the SI and making a forwarding decision based on a new value of the SI and the SPI.

Example Embodiments

To accommodate agile networking and flexible provisioning of network nodes in a network, service chaining may be used to ensure an ordered set of service functions are applied to packets and/or frames of a traffic flow. Service chaining provides a method for deploying service functions in a manner that enables dynamic ordering and topological independence of the service functions. A service chain may define an ordered set of service functions to be applied to packets and/or frames of a traffic flow, where each service function of the ordered set is selected as a result of classification. The implied order may not be a linear progression, as the architecture may allow for nodes that copy to more than one branch.

Service chaining involves a classifier function that performs classification based on policies configured by a control plane element to select a service chain to process traffic and load balances the traffic among instances of the selected service chain. Once the classifier function selects a service chain instance (a.k.a. service function path or “SFP”), it forwards the traffic along a service function path (“SFP”), or simply, a service path, through one or more service-aware forwarding elements (“FEs”). In one certain embodiment, each forwarding element implements a service function forwarder (“SFF”) capability described in an IETF draft entitled “Service Function Chaining (SFC) Architecture” (IETF RFC7665—https://datatracker.ietf.org/doc/rfc7665/) (hereinafter “SFC Architecture RFC”). The forwarding elements forward the traffic to the actual service functions that are logically anchored to, and/or instantiated on, the forwarding element. Forwarding of traffic between any two components in such an architecture, and hence along the service chains, is performed over an overlay network. Overlay networks are realized via a transport header and an encapsulation header. Various network encapsulation headers have been employed to forward traffic, requiring service through the service chains. Such network encapsulation headers encapsulate the original packet, or frame, and are themselves encapsulated in an overlay transport protocol. Examples of encapsulation headers include proprietary headers, such as vPath, or proposed IETF standard headers, such as Network Service Header (“NSH”). Transport protocols used to carry such encapsulated packets may be L3- or L4-based, such as IPv4/IPv6 or GRE or UDP, VxLAN, etc. In the case of vPath, even L2-based, such as LLC SNAP.

FIG. 1A illustrates an SFC-enabled domain 10, which may include an initial service classification function (or “classifier”) 12, as an entry point to a service path. The initial service classification function 12 prescribes an instance of the service path, designated in FIG. 1A by a reference numeral 14, and encapsulates a packet or frame with service path information that identifies the service path. The classification function 12 may potentially add metadata, or shared context to the SFC encapsulation part of the packet or frame. The service path 14 may include a plurality of service functions, designated in FIG. 1A by SF1, SF2, . . . , SFN.

A service function may be responsible for specific treatment and/or processing of received packets. A service function may act at the network layer or other OSI layers (e.g., application layer, presentation layer, session layer, transport layer, data link layer, and physical link layer). A service function may be a virtual instance or be embedded in a physical network element, such as a service node. When a service function or other modules of a service node are executed by the at least one processor of the service node, the service function or other modules may be configured to implement any one of the methods described herein. Multiple service functions can be embedded in the same network element. Multiple instances of the service function can be enabled in the same administrative SFC-enabled domain. A non-exhaustive list of service functions includes firewalls, WAN and application acceleration, Deep Packet Inspection (“DPI”), server load balancers, NAT44, NAT64, HOST_ID injection, HTTP Header Enrichment functions, TCP optimizer, and others. A service function may be SFC-encapsulation aware; that is, it may receive and act on information in the SFC encapsulation, or unaware in which case data forwarded to the service does not contain the SFC encapsulation.

A service node may be a physical network element (or a virtual element embedded on a physical network element) that hosts one or more service functions and may have one or more network locators associated with it for reachability and service delivery. In many standardization documents, “service functions” can refer to the service nodes described herein as having one or more service functions hosted thereon. SFP, or simply service path, relates to the instantiation of a service chain in a network. Packets follow a service path from a classifier through the requisite service functions.

FIGS. 1B-1C illustrate different service paths that may be realized using service function chaining. These service paths may be implemented by encapsulating packets of a traffic flow with a network service header (“NSH”) or some other suitable packet header which specifies a desired service path (e.g., by identifying a particular service path using service path information in the NSH) through one or more of service nodes 16, 18, 20, and 22. In the example shown in FIG. 1B, a service path 30 may be provided between an endpoint 32 and an endpoint 34 through service node 16 and service node 20. In the example shown in FIG. 1C, a service path 40 (a different instantiation) can be provided between end point 42 and endpoint 44 through service node 16, service node 18, and service node 22.

Generally speaking, an NSH includes service path information, and NSH is added to a packet or frame. For instance, an NSH can include a data plane header added to packets or frames. Effectively, the NSH creates a service plane. The NSH includes information for service chaining, and in some cases, the NSH can include metadata added and/or consumed by service nodes or service functions. The packets and NSH are encapsulated in an outer header for transport. To implement a service path, a network element such as a service classifier (“SCL”) or some other suitable SFC-aware network element can process packets or frames of a traffic flow and performs NSH encapsulation according to a desired policy for the traffic flow.

FIG. 2A shows a system view of SFC-aware network element 50, e.g., such as an initial service classifier, for prescribing a service path of a traffic flow, according to some embodiments of the disclosure. Network element 50 includes processor 52 and (computer-readable non-transitory) memory 54 for storing data and instructions. Furthermore, network element 50 may include a service classification function 55, a service forwarding function 56, a service header encapsulator 57, and a service header decapsulator 58, all of which may be provided by processor 52 when processor 52 executes the instructions stored in memory 54. Service forwarding function 55 determines how to forward service encapsulated packets at a classifier or a forwarding network element. It also determines whether to remove or modify the service encapsulation header received. The latter is true if the network element is acting as a service forwarder as opposed to a classifier. In general, a classifier needs a service forwarding function alongside it, whereas a service forwarding function does not necessarily need a classifier.

The service classification function 55 can process a packet of a traffic flow and determine whether the packet requires servicing and correspondingly which service path to follow to apply the appropriate service. The determination can be performed based on business policies and/or rules stored in memory 54. Once the determination of the service path is made, service header encapsulator 57 generates an appropriate NSH having identification information for the service path and adds the NSH to the packet. The service header encapsulator 57 provides an outer encapsulation to forward the packet to the start of the service path. Other SFC-aware network elements are thus able to process the NSH while other non-SFC-aware network elements would simply forward the encapsulated packets as is. Besides inserting an NSH, network element 50 can also remove or not add the NSH if the service classification function 55 determines the packet does not require servicing.

FIG. 2B shows a system view of an SFC-aware network element 58, e.g., such as an SFF, for forwarding service flows to service functions and to other SFFs as prescribed, according to some embodiments of the disclosure. Network element 58 is identical in all respects to network element 50 except that network element 58 does not include service classification function 55.

An NSH may include a (e.g., 64-bit) base header, and one or more context headers. Generally speaking, the base header provides information about the service header and service path identification (e.g., an SPI), and context headers may carry opaque metadata (such as the metadata described herein reflecting the result of classification). For instance, an NSH can include a 4-byte base header, a 4-byte service path header, and optional context headers. The base header can provide information about the service header and the payload protocol. The service path header can provide path identification and location (i.e., service function) within a path. The variable length context headers can carry opaque metadata and variable length encoded information. The one or more optional context headers make up a context header section in the NSH. For instance, the context header section can include one or more context header fields having pieces of information therein, describing the packet/frame. Based on the information in the base header, a service function of a service node can, for instance, derive policy selection from the NSH. Context headers shared in the NSH can, for instance, provide a range of service-relevant information such as traffic classification, end point identification, etc. Service functions can use NSH to select local service policy.

Once properly classified and encapsulated by the classifier, the packet having the NSH may be then forwarded to one or more service nodes where service(s) can be applied to the packet/frame. FIG. 3 shows a system view of a service node, according to some embodiments of the disclosure. Service node 60, generally a network element, can include processor 62 and (computer-readable non-transitory) memory 64 for storing data and instructions. Furthermore, service node 60 may include service function(s) 66 (e.g., for applying service(s) to the packet/frame, classifying the packet/frame) and service header processor 68. The service functions(s) 66 and service header processor 68 can be provided by processor 62 when processor 62 executes the instructions stored in memory 64. Service header processor 68 can extract the NSH, and in some cases, update the NSH as needed. For instance, the service header processor 68 can decrement the service index. If the resulting service index=0, the packet is dropped. In another instance, the service header processor 68 or some other suitable module provide by the service node can update context header fields if new/updated context is available.

As previously noted, service chaining involves a classifier function performing classification based on policies configured by a control plane to select service chains and perform load balancing among instances of the service chains. The classifier function then forwards the traffic along the SFP through one or more service-aware forwarding elements. Forwarding elements implement a service function forwarder (“SFF”) capability described in the aforementioned SFC Architecture IETF Draft. The forwarding elements forward the traffic to the actual service chain nodes that are logically anchored to the forwarding element. Forwarding of traffic between any two components in such an architecture, and hence through the service chains, is performed over an overlay network. As previously noted, overlay networks are realized via a transport header and an encapsulation header. Various network encapsulation headers have been employed to forward traffic, requiring service through the service chains. Such headers encapsulate the original packet, or frame, and are themselves encapsulated in an overlay transport protocol. Examples of encapsulation headers include proprietary headers such as vPath or proposed IETF standard headers, such as Network Service Header (“NSH”). The transport protocols used to carry such encapsulations are typically L3 or L4 based, such as IPv4/IPv6 or GRE or UDP, VxLAN, etc. In the case of vPath, even L2 protocols, such as LLC SNAP, may be used.

By way of an example, a service chain SC₁ may be described in terms of service function (“SF”) types:

• • SC₁=SF_a, SF_b, SF_c

Corresponding service chain instances, i.e., the service paths (“SPs”), may be constructed from instances of the service function type:

• • SP_1.1=SF_a1, SF_b1, SF_c1
  • SP_1.2=SF_a1, SF_b3, SF_c2

As illustrated in FIG. 4, service chain SC1 maps to two service paths SP1.1 and SP1.2. Classifier selects the service chain SC1 and load balances between instances SP1.1 and SP1.2. In general, packets forwarded between the components, such as, between classifier and forwarding element or forwarding element and service function, is of the form illustrated in FIG. 5 and include an original packet/frame 70, SFC encapsulation 72, and a transport protocol header 74. The SFC encapsulation 72 may be implemented using an NSH. As previously noted, NSH includes a base header, a service header, and a fixed/variable number of metadata TLVs as described in IETF draft entitled “Network Service Header” (draft-ietf-sfc-nsh-01.txt) (hereinafter “NSH IETF Draft”).

FIG. 6 shows the format of a base header 80 and a service header 82 of a conventional NSH 84. As shown in FIG. 6, the base header 80 includes a version field 86a, a number of individual bits/flags, collectively designated by a reference numeral 86b, a length field 86c, a metadata type field 86d, and a next protocol field 86e. The services header 82 includes a Service Path ID field 88a and a Service Index field 88b. The fields and their contents are described in detail in the aforementioned NSH IETF Draft. In some cases, NSH requires that the Service Index (“SI”) must be decremented by the service functions. Also, in some cases, NSH requires that the FEs must forward NSH encapsulated traffic based Service Path ID (“SPI”) and Service Index (“SI”), as received from other components. As described above, both the SPI and the SI, which are included in the service header of an NSH, are needed to make a forwarding decision. The control plane constructs the SPIs and distributes them into the forwarding elements along with SI and decrement value (i.e., the amount by which to decrement the SI). This implies that all service functions must have the knowledge of the SPIs and the SIs and in turn manipulate them prior to forwarding a NSH encapsulated packet out.

As previously noted, SFC involves steering user/application traffic through a list of ordered service functions before forwarding onward to its destination, in the process servicing the traffic as per policy in those service functions as well as service chaining infrastructure. Existing methods to forward traffic through service functions suffer from various deficiencies including but not limited to complexity of deployment and operation due a large number of forwarding touch points; scale challenges due to the involvement of service functions in making forwarding decisions; and violation of operational environment policies due to errors or unintentional modification of forwarding-state by service functions.

Moreover, as a consequence of above assertions of NSH and service chaining, NSH uses a model in which service functions are fully trusted to maintain the integrity of the encapsulation, thereby allowing forwarding elements or service function forwarders to forward on the decisions made by service functions. This is not acceptable in all network environments. Strict infrastructure and application boundaries in operators' environments essentially disallow such a method of packet forwarding. Additionally, since forwarding decisions are made at service functions, the control plane has to program the forwarding elements with forwarding information, which includes the SPI and SI information. This approach negatively impacts scalability, as the number of service functions are significantly greater in number as compared to forwarding elements in a typical deployment. Moreover, given that service functions have to be programmed with forwarding information and the service functions may be from any vendor or third party, programming the service functions and the infrastructure may lead to very complex control plane interactions, which in turn negatively impacts scalability of the deployment and hence the architecture. The service functions may be home-grown by the operators, purchased from third parties, or downloaded freely from open source software portals. Still further, since forwarding is performed at the forwarding elements based solely on the SPI and SI fields in the NSH encapsulation header, forwarding elements are vulnerable to decisions made by service functions. If a service function is buggy, compromised, or performing incorrect manipulation of the SI, packets may be forwarded to the wrong next-hop (such as jumping over a firewall) or may continuously loop. Finally, looking at the service context header in NSH, it is not possible to determine what service function the packet is associated with and where along the path it is, due to the fact that service functions decrement the SI. As a result, additional context is required to make such an assertion.

Original vPath implementation relies on a stateful method to contain the forwarding decision to forwarding elements. However stateful methods are not cost-effective to implement in hardware and almost never implemented at any reasonable scale.

To address some of these issues, in accordance with features of embodiments described herein, a technique for infrastructure-exclusive service forwarding may be employed in service chain architecture and packet forwarding methods to perform the actual packet forwarding through the service path in a network in an intuitive, effective, hardware friendly and architecturally clean manner. In particular, the infrastructure-exclusive service forwarding method described herein is stateless and hardware friendly, and advantageously limits forwarding state manipulation to forwarding elements (switches, routers, or other network elements). The method separates the service overlays into service-function and infrastructure overlays. Further, it contains forwarding decisions and SI manipulation to forwarding elements and free the service functions from making forwarding decisions and manipulating the SI.

The method separates forwarding and servicing planes in NSH or any such encapsulations. This enables forwarding to be fully owned and controlled by the service chaining infrastructure while service delivery is fully the responsibility of the service functions. This allows for scaling the service plane independent of the forwarding plane while avoiding forwarding conflicts that may otherwise arise. Forwarding is fully controlled by the forwarding elements and any forwarding-state carried in NSH, be it NSH service context header or metadata context header, is fully opaque to the service functions. The current overlay network can be separated into infrastructure overlay and the service overlay. Infrastructure overlay extends between forwarding elements or classifier and forwarding elements, while the service overlay extends between the forwarding elements and service functions. Only the forwarding elements and classifiers make the forwarding decisions, hence limiting the forwarding decision-making to infrastructure alone. In some embodiments, the decrement operation on SI at the forwarding elements may be controlled by the presence of a signal or a flag that indicates whether the packet is on the infrastructure or the service overlay/plane.

FIG. 7 is the format of a base header 90 and a service header 92 of a modified NSH 94 for implementing features of embodiments described herein. As shown in FIG. 7, one of the bits/flags of the base header 90 (designated in FIG. 7 by a reference numeral 96) is identified as an Infrastructure Overlay, or “I,” bit or flag. In operation, as will be described in greater detail below, when the I bit is set to 1, the packet/frame is deemed to be on the service-infrastructure overlay; when the I bit is set to 0, the packet/frame is deemed to be on the service-function overlay. The “service infrastructure overlay” comprises communications between the classifier and a forwarding element or between forwarding elements. The “service function overlay” comprises communications between forwarding elements and service functions. This concept is illustrated in FIG. 8.

The following rules are observed by the SFC components in updating the ‘I’ flag and the SI field of the modified NSH 94 shown in FIG. 7:

• • 1. a classifier must set an infrastruture (“I”) flag in the NSH to 1 when sending an NSH encapsulated packet/frame to the next forwarding element or service function forwarder;
  • 2. a forwarding element (or SFF) must set the I flag to 1 when sending an NSH encapsulated packet to the next forwarding element or service function forwarder;
  • 3. a classifier and a forwarding element (SFF) must set the I flag to 0 in all other circumstances when forwarding an NSH encapsulated packet;
  • 4. a service function or service function proxy must not set the I flag;
  • 5. a forwarding element (or SFF) must update the service index in NSH only when a packet with NSH is received with the I flag set to 0 before making the next forwarding decision; and
  • 6. a service function is never permitted to decrement or update the service index; this is controlled by a one-time static configuration at the service functions and is preferably the default behavior of the service functions.

It will be noted that in certain embodiments, classifiers are expected to have embedded therein a forwarding element (or service forwarding function) and to display all of the behaviors of a forwarding element.

FIG. 9A is a flowchart illustrating a method that may be implemented at an initial classifier function, such as network element 50 (FIG. 2), in accordance with embodiments described herein. In step 100, a packet is received. In step 102, the packet is classified. Additionally, the service chain is identified in accordance with policy and a service chain instance is selected. In step 104, the packet is encapsulated with an NSH, which includes setting the SPI and SI fields and setting the I flag. As previously noted, in accordance with features of embodiments described herein, the I flag will be set to 1 if the packet is to be forwarded to a forwarding element (SFF) and to 0 if the packet is to be forwarded to a service function. In step 106, tunnel encapsulation is performed. In step 108, the packet is forwarded on the service chain identified in the SPI to the service function identified in the SI, via the forwarding element anchoring the service function.

FIG. 9B is a flowchart illustrating a method that may be implemented at a forwarding element, such as network element 50 (FIG. 2), in accordance with embodiments described herein. In step 110, a packet is received. In step 112, the I flag of the NSH of the packet is checked. If the I flag is set to 1, meaning that the packet was received on the infrastructure overlay (e.g., from a classifier or forwarding element), execution proceeds to step 114, in which the I flag is set to 0, and then to step 116, in which the packet is forwarded to the identified service function via the service function overlay. If in step 112, the I flag is determined to be set to 0, meaning that the packet was received on the service function overlay (e.g., from a service function), in step 118, the SI is decremented (or updated). In step 120, a forwarding decision is made based on the new value of the SI. The forwarding decision may result in the packet being sent to a service node anchored at the same forwarding element, in which case execution proceeds to step 114 (described above), or may result in the packet being sent to a service node anchored at a different forwarding element, in which case execution proceeds to step 121. In step 121, the I flag is set to 1, and in step 122, the packet is forwarded via the infrastructure overlay in accordance with the forwarding decision made in step 120.

In certain embodiments, the forwarding element, or SFF, may verify the integrity of the service path header every time an NSH packet is received from a service function. This verification may be implemented as follows.

The separation of service function and forwarding function responsibilities with respect to forwarding state allows the service function forwarders to enforce integrity checks to verify the immutable aspect of the service path header. In certain embodiments, it is recommended to use an appropriate method to verity the integrity of the service path header. There are many approaches to performing the integrity checks; a few are briefly summarized below as examples.

In one embodiment, every NSH packet received from a SF (i.e., 1=0 in NSH base header) is checked against the three tuple: <SF-Transport-Address, SPI, SI> programmed in the SFF by the control plane for that SF. This method is simple and works well when a SF appears only once across all service paths.

In another embodiment, SFFs compute a hash of an n-tuple or a pseudo header and transport this hash as opaque metadata in NSH through the SFs on a service path. When an SFF receives the opaque metadata back (post servicing of the packet), it re-computes the hash of the same n-tuple and checks against the hash received in NSH. The n-tuple may include inner payload, outer transport, service path header and SFF local data among others. Implementations must determine the n-tuple based on the SFC deployment requirements.

In another embodiment, SFFs that are stateful use flow state to record SPI and SIs and validate the same when the packet is received back from a SF. This works well as long as an SF appears only once in a given SPI. If multiple instances of the same SF within the same SPI are needed, additional checks to protect the SI must be performed.

In yet another embodiment, as a generalized approach, the control plane programs a mask to be applied to the NSH header to select the bits against which to perform integrity checks. In the simplest case, the mask represents just the service path header.

The service header integrity check techniques described above do not protect against such threats as packet replay or spoofing attacks, which do not violate the integrity of the service path header; rather, they protect only against modification of the NSH service path header accidentally or otherwise thus ensuring the integrity of the same.

FIG. 10 illustrates an example of a typical packet flow through an example SPI1=SFa@SFF1,SFb@SFF1,SFc@SFF2 with the topology shown in FIG. 10. As shown in FIG. 10, a packet enters the system 124 via an SFC ingress network 125 reaching a classifier function 126. The classifier function 126 determines the SPI and SI of the packet as part of the classification. The classifier function 126 formulates the NSH infrastructure overlay packet, sets the I flag, among other header updates, and forwards the packet onward to SFF1. SFF1 receives the NSH infrastructure overlay packet, omits performing the SI decrement operation due to I=1, performs a forwarding lookup to determine the next hop. SFF1 determines SFa as the next hop, formulates the NSH service overlay packet, clears the I flag among other header updates, and forward the packet to SFa on service function overlay. SFa services the packet by consuming and/or producing metadata and forwards the packet back to SFF1. Upon receipt by SFF1 of the returned packet, SFF1 decrements the SI, due to I=0, before performing a forwarding lookup. SFF1 determines the next-hop as SFb and the process repeats with SFb as before with SFa. SFF1 receives the SFb serviced packet, decrements the SI and determines the next-hop to be SFc and forwards the packet to SFF2 on the infrastructure overlay (I=1). SFF2 repeats the process with respect to SFc similarly. SFF2 receives the SFc serviced packet, decrements the SI and determines SPI1 is fully executed and proceeds with forwarding on an SFC egress network 128.

Turning to FIG. 11, FIG. 11 illustrates a simplified block diagram of an example machine (or apparatus) 130, which in certain embodiments may be a classifier or a forwarding element, that may be implemented in embodiments described herein. The example machine 130 corresponds to network elements and computing devices that may be deployed in a communications network, such as a classifier or a forwarding element. In particular, FIG. 11 illustrates a block diagram representation of an example form of a machine within which software and hardware cause machine 130 to perform any one or more of the activities or operations discussed herein. As shown in FIG. 11, machine 130 may include a processor 132, a main memory 133, secondary storage 134, a wireless network interface 135, a wired network interface 136, a user interface 137, and a removable media drive 138 including a computer-readable medium 139. A bus 131, such as a system bus and a memory bus, may provide electronic communication between processor 132 and the memory, drives, interfaces, and other components of machine 130.

Processor 132, which may also be referred to as a central processing unit (“CPU”), can include any general or special-purpose processor capable of executing machine readable instructions and performing operations on data as instructed by the machine readable instructions. Main memory 133 may be directly accessible to processor 132 for accessing machine instructions and may be in the form of random access memory (“RAM”) or any type of dynamic storage (e.g., dynamic random access memory (“DRAM”)). Secondary storage 134 can be any non-volatile memory such as a hard disk, which is capable of storing electronic data including executable software files. Externally stored electronic data may be provided to computer 130 through one or more removable media drives 138, which may be configured to receive any type of external media such as compact discs (“CDs”), digital video discs (“DVDs”), flash drives, external hard drives, etc.

Wireless and wired network interfaces 135 and 136 can be provided to enable electronic communication between machine 130 and other machines, or nodes. In one example, wireless network interface 135 could include a wireless network controller (“WNIC”) with suitable transmitting and receiving components, such as transceivers, for wirelessly communicating within a network. Wired network interface 136 can enable machine 130 to physically connect to a network by a wire line such as an Ethernet cable. Both wireless and wired network interfaces 135 and 136 may be configured to facilitate communications using suitable communication protocols such as, for example, Internet Protocol Suite (“TCP/IP”). Machine 130 is shown with both wireless and wired network interfaces 135 and 136 for illustrative purposes only. While one or more wireless and hardwire interfaces may be provided in machine 130, or externally connected to machine 130, only one connection option is needed to enable connection of machine 130 to a network.

A user interface 137 may be provided in some machines to allow a user to interact with the machine 130. User interface 137 could include a display device such as a graphical display device (e.g., plasma display panel (“PDP”), a liquid crystal display (“LCD”), a cathode ray tube (“CRT”), etc.). In addition, any appropriate input mechanism may also be included such as a keyboard, a touch screen, a mouse, a trackball, voice recognition, touch pad, etc.

Removable media drive 138 represents a drive configured to receive any type of external computer-readable media (e.g., computer-readable medium 139). Instructions embodying the activities or functions described herein may be stored on one or more external computer-readable media. Additionally, such instructions may also, or alternatively, reside at least partially within a memory element (e.g., in main memory 133 or cache memory of processor 132) of machine 130 during execution, or within a non-volatile memory element (e.g., secondary storage 134) of machine 130. Accordingly, other memory elements of machine 130 also constitute computer-readable media. Thus, “computer-readable medium” is meant to include any medium that is capable of storing instructions for execution by machine 130 that cause the machine to perform any one or more of the activities disclosed herein.

Not shown in FIG. 11 is additional hardware that may be suitably coupled to processor 132 and other components in the form of memory management units (“MMU”), additional symmetric multiprocessing (“SMP”) elements, physical memory, peripheral component interconnect (“PCI”) bus and corresponding bridges, small computer system interface (“SCSI”)/integrated drive electronics (“IDE”) elements, etc. Machine 130 may include any additional suitable hardware, software, components, modules, interfaces, or objects that facilitate the operations thereof. This may be inclusive of appropriate algorithms and communication protocols that allow for the effective protection and communication of data. Furthermore, any suitable operating system may also be configured in machine 130 to appropriately manage the operation of the hardware components therein.

The elements, shown and/or described with reference to machine 130, are intended for illustrative purposes and are not meant to imply architectural limitations of machines such as those utilized in accordance with the present disclosure. In addition, each machine may include more or fewer components where appropriate and based on particular needs. As used herein in this Specification, the term “machine” is meant to encompass any computing device or network element such as servers, routers, personal computers, client computers, network appliances, switches, bridges, gateways, processors, load balancers, wireless LAN controllers, firewalls, or any other suitable device, component, element, or object operable to affect or process electronic information in a network environment.

In example implementations, at least some portions of the activities described herein may be implemented in software in. In some embodiments, this software could be received or downloaded from a web server, provided on computer-readable media, or configured by a manufacturer of a particular element in order to implement the embodiments described herein. In some embodiments, one or more of these features may be implemented in hardware, provided external to these elements, or consolidated in any appropriate manner to achieve the intended functionality.

In one example implementation, classifier and forwarding elements, which may include any suitable hardware, software, components, modules, or objects that facilitate the operations thereof, as well as suitable interfaces for receiving, transmitting, and/or otherwise communicating data or information in a network environment. This may be inclusive of appropriate algorithms and communication protocols that allow for the effective exchange of data or information.

Furthermore, in the embodiments described and illustrated herein, some of the processors and memory elements associated with the various network elements may be removed, or otherwise consolidated such that a single processor and a single memory location are responsible for certain activities. Alternatively, certain processing functions could be separated and separate processors and/or physical machines could implement various functionalities. In a general sense, the arrangements depicted in the FIGURES may be more logical in their representations, whereas a physical architecture may include various permutations, combinations, and/or hybrids of these elements. It is imperative to note that countless possible design configurations can be used to achieve the operational objectives outlined here. Accordingly, the associated infrastructure has a myriad of substitute arrangements, design choices, device possibilities, hardware configurations, software implementations, equipment options, etc.

In some of the example embodiments, one or more memory elements (e.g., main memory 133, secondary storage 134, computer-readable medium 139) can store data used in implementing embodiments described and illustrated herein. This includes at least some of the memory elements being able to store instructions (e.g., software, logic, code, etc.) that are executed to carry out the activities described in this Specification. A processor can execute any type of instructions associated with the data to achieve the operations detailed herein in this Specification. In one example, one or more processors (e.g., processor 132) could transform an element or an article (e.g., data) from one state or thing to another state or thing. In another example, the activities outlined herein may be implemented with fixed logic or programmable logic (e.g., software/computer instructions executed by a processor) and the elements identified herein could be some type of a programmable processor, programmable digital logic (e.g., a field programmable gate array (“FPGA”), an erasable programmable read only memory (“EPROM”), an electrically erasable programmable read only memory (“EEPROM”)), an ASIC that includes digital logic, software, code, electronic instructions, flash memory, optical disks, CD-ROMs, DVD ROMs, magnetic or optical cards, other types of machine-readable mediums suitable for storing electronic instructions, or any suitable combination thereof.

Components of communications network described herein may keep information in any suitable type of memory (e.g., random access memory (“RAM”), read-only memory (“ROM”), erasable programmable ROM (“EPROM”), electrically erasable programmable ROM (“EEPROM”), etc.), software, hardware, or in any other suitable component, device, element, or object where appropriate and based on particular needs. Any of the memory items discussed herein should be construed as being encompassed within the broad term “memory element.” The information being read, used, tracked, sent, transmitted, communicated, or received by network environment, could be provided in any database, register, queue, table, cache, control list, or other storage structure, all of which can be referenced at any suitable timeframe. Any such storage options may be included within the broad term “memory element” as used herein. Similarly, any of the potential processing elements and modules described in this Specification should be construed as being encompassed within the broad term “processor.”

Certain embodiments described herein separate the overlay in service function chaining into an infrastructure overlay and a service function overlay, allowing additional security policies to be enforced between the two. Certain embodiments described herein provide a stateless, hardware friendly method for decrementing the NSH service index without requiring any state at the forwarding element or sender awareness. Additionally, certain embodiments described herein restrict the forwarding decisions (in updating the service index) to the forwarding elements alone and frees the service functions to focus purely on service delivery and avoid dealing with complexities associated with forwarding decisions. Still further, certain embodiments described herein enable the service chaining control plane to scale independently of the number of service functions and prevent issues that may arise due to incorrect manipulation of the service index by limiting manipulation of the service index to forwarding elements.

Certain embodiments described herein allow snooping tools or any type of intermediate nodes to clearly determine whether the NSH encapsulated packet is going between forwarding elements or between a forwarding element and a service function without relying on the source and destination locators, which is useful in tracing and debugging, especially in cloud deployments. Certain embodiments described herein allow the service index on an NSH packet to be always associated with the service function as indicated by the service index whether the packet is in transit from a forwarding element to the service function or from the service function to a forwarding element.

Note that with the example provided above, as well as numerous other examples provided herein, interaction may be described in terms of two, three, or four network elements. However, this has been done for purposes of clarity and example only. In certain cases, it may be easier to describe one or more of the functionalities of a given set of flows by only referencing a limited number of network elements. It should be appreciated that topologies illustrated in and described with reference to the accompanying FIGURES (and their teachings) are readily scalable and can accommodate a large number of components, as well as more complicated/sophisticated arrangements and configurations. Accordingly, the examples provided should not limit the scope or inhibit the broad teachings of the illustrated topologies as potentially applied to myriad other architectures.

It is also important to note that the steps in the preceding flow diagrams illustrate only some of the possible signaling scenarios and patterns that may be executed by, or within, communication systems shown in the FIGURES. Some of these steps may be deleted or removed where appropriate, or these steps may be modified or changed considerably without departing from the scope of the present disclosure. In addition, a number of these operations have been described as being executed concurrently with, or in parallel to, one or more additional operations. However, the timing of these operations may be altered considerably. The preceding operational flows have been offered for purposes of example and discussion. Substantial flexibility is provided by communication systems shown in the FIGURES in that any suitable arrangements, chronologies, configurations, and timing mechanisms may be provided without departing from the teachings of the present disclosure.

Although the present disclosure has been described in detail with reference to particular arrangements and configurations, these example configurations and arrangements may be changed significantly without departing from the scope of the present disclosure. For example, although the present disclosure has been described with reference to particular communication exchanges, embodiments described herein may be applicable to other architectures.

Numerous other changes, substitutions, variations, alterations, and modifications may be ascertained to one skilled in the art and it is intended that the present disclosure encompass all such changes, substitutions, variations, alterations, and modifications as falling within the scope of the appended claims. In order to assist the United States Patent and Trademark Office (USPTO) and, additionally, any readers of any patent issued on this application in interpreting the claims appended hereto, Applicant wishes to note that the Applicant: (a) does not intend any of the appended claims to invoke paragraph six (6) of 35 U.S.C. section 142 as it exists on the date of the filing hereof unless the words “means for” or “step for” are specifically used in the particular claims; and (b) does not intend, by any statement in the specification, to limit this disclosure in any way that is not otherwise reflected in the appended claims.

Claims

1. A method comprising: receiving at a network element a packet including a Network Services Header (“NSH”), wherein the NSH includes an Infrastructure (“I”) flag and a service path header comprising a Service Index (“SI”), and a Service Path ID (“SPI”);determining whether the I flag is set to a first value;if the I flag is set to the first value: setting the I flag to a second value; andforwarding the packet to a service function that corresponds to the SI for processing;if the I flag is not set to the first value:decrementing the SI; andmaking a forwarding decision based on a new value of the SI and the SPI;wherein the I flag will be set to the first value when the packet is to be forwarded to a forwarding element and to the second value when the packet is to be forwarded to the service function.

2. The method of claim 1 further comprising, if the forwarding decision comprises forwarding the packet to a second service function anchored to the network element: setting the I flag to the second value; andforwarding the packet to the second service function anchored to the network element.

3. The method of claim 1 further comprising, if the forwarding decision comprises forwarding the packet to a second service function anchored at a different network element: setting the I flag to the first value; andforwarding the packet to the different network element.

4. The method of claim 1, wherein the network element comprises at least one of a forwarding element and a classifier.

5. The method of claim 1 further comprising performing an integrity check on the service header upon receipt of the packet from the service function.

6. The method of claim 5, wherein the integrity check comprises at least one of: checking the packet against a three tuple programmed into the network element by a control plane for the service function;computing a hash of an n-tuple or pseudo header and transporting the hash as opaque metadata in the NSH through the service function on a service path;recording the SPI and the SI and validating them when the packet is received from the service function; andapplying a mask programmed by the control plane to the NSH to select bits against which to perform integrity checks.

7. The method claim 1, wherein the NSH includes a decrement value and wherein the decrementing comprises reducing the value of the SI by an amount equal to the decrement value.

8. The method of claim 1, wherein the service function does not alter the service path header.

9. The method of claim 1 further comprising: receiving at the network element a second packet, wherein the second packet does not include an NSH;classifying the second packet at the network element to select a service chain for processing the second packet;adding to the second packet an NSH, wherein a service header of the NSH added to the second packet identifies the service chain;setting an I bit of the NSH header added to the second packet to 1; andmaking a forwarding decision based on the service chain of the NSH header added to the second packet.

10. One or more non-transitory tangible media having encoded thereon logic that includes code for execution and when executed by a processor is operable to perform operations comprising: receiving at a network element a packet including a Network Services Header (“NSH”), wherein the NSH includes an Infrastructure (“I”) flag and a service path header comprising a Service Index (“SI”), and a Service Path ID (“SPI”);determining whether the I flag is set to a first value;if the I flag is set to the first value: setting the I flag to a second value; andforwarding the packet to a service function that corresponds to the SI for processing;if the I flag is not set to the first value: decrementing the SI; andmaking a forwarding decision based on a new value of the SI and the SPI;wherein the I flag will be set to the first value when the packet is to be forwarded to a forwarding element and to the second value when the packet is to be forwarded to a service function.

11. The media of claim 10 wherein the operations further comprise, if the forwarding decision comprises forwarding the packet to a second service function anchored to the network element: setting the I flag to the second value; andforwarding the packet to the second service function anchored to the network element.

12. The media of claim 10 wherein the operations further comprise, if the forwarding decision comprises forwarding the packet to a second service function anchored at a different network element: setting the I flag to the first value; andforwarding the packet to the different network element.

13. The media of claim 10 wherein the operations further comprise performing an integrity check on the service header upon receipt of the packet from the service function, wherein the integrity check comprises at least one of: checking the packet against a three tuple programmed into the network element by a control plane for the service function;computing a hash of an n-tuple or pseudo header and transporting the hash as opaque metadata in the NSH through the service function on a service path;recording the SPI and the SI and validating them when the packet is received from the service function; andapplying a mask programmed by the control plane to the NSH to select bits against which to perform integrity checks.

14. The media of claim 10, wherein the service function does not alter the service path header.

15. The media of claim 10 wherein the instructions further comprise: receiving at the network element a second packet, wherein the second packet does not include an NSH;classifying the second packet at the network element to select a service chain for processing the second packet;adding to the second packet an NSH, wherein a service header of the NSH added to the second packet identifies the service chain;setting an I bit of the NSH header added to the second packet to 1; andmaking a forwarding decision based on the service chain of the NSH header added to the second packet.

16. An apparatus comprising: a memory element configured to store data;a processor operable to execute instructions associated with the data; anda service forwarding function module configured to: receive at a network element a packet including a Network Services Header (“NSH”), wherein the NSH includes an Infrastructure (“I”) flag and a service path header comprising a Service Index (“SI”), and a Service Path ID (“SPI”);determine whether the I flag is set to a first value;if the I flag is set to the first value: set the I flag to a second value; andforward the packet to a service function that corresponds to the SI for processing;if the I flag is not set to the first value: decrement the SI; andmake a forwarding decision based on a new value of the SI and the SPI;wherein the I flag will be set to the first value when the packet is to be forwarded to a forwarding element and to the second value when the packet is to be forwarded to a service function.

17. The apparatus of claim 16, wherein the service forwarding function module is further configured to: if the forwarding decision comprises forwarding the packet to a second service function anchored to the network element: set the I flag to the second value; andforward the packet to the second service function anchored to the network element; andif the forwarding decision comprises forwarding the packet to a second service function anchored at a different network element: set the I flag to the first value; andforward the packet to the different network element.

18. The apparatus of claim 16, wherein the service forwarding function module is further configured to, perform an integrity check on the service header upon receipt of the packet from the service function, wherein the integrity check comprises at least one of: checking the packet against a three tuple programmed into the network element by a control plane for the service function;computing a hash of an n-tuple or pseudo header and transporting the hash as opaque metadata in the NSH through the service function on a service path;recording the SPI and the SI and validating them when the packet is received from the service function; andapplying a mask programmed by the control plane to the NSH to select bits against which to perform integrity checks.

19. The apparatus of claim 16, wherein the service function does not alter the service path header.

20. The apparatus of claim 16, wherein the service forwarding module is further configured to: receive at the network element a second packet, wherein the second packet does not include an NSH;classify the second packet at the network element to select a service chain for processing the second packet;add to the second packet an NSH, wherein a service header of the NSH added to the second packet identifies the service chain;set an I bit of the NSH header added to the second packet to 1; andmake a forwarding decision based on the service chain of the NSH header added to the second packet.