| SFC | M. Boucadair |
| Internet-Draft | Orange |
| Intended status: Standards Track | D. von Hugo |
| Expires: July 21, 2018 | Telekom Innovation Laboratories |
| B. Sarikaya | |
| Huawei | |
| January 17, 2018 |
Service Function Chaining: Subscriber and Service Identification Use Cases and Variable-Length NSH Context Headers
draft-sarikaya-sfc-hostid-serviceheader-06
This document discusses considerations related to passing service- and subscriber-related information to upstream Service Functions for the sake of policy enforcement and appropriate SFC-inferred forwarding. Once the information is consumed by SFC-aware elements of an SFC-enabled domain, the information is stripped from packets so that privacy-sensitive information is not leaked outside an SFC-enabled domain.
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 21, 2018.
Copyright (c) 2018 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
This document focuses on aspects related to passing service- and subscriber-related information to upstream Service Functions (SFs) when required for the sake of policy enforcement. Indeed, subscriber-related information may be needed for upstream SFs when per-subscriber policies are to be enforced upstream in the network while the information conveyed by the original packets does not allow for uniquely identifying a subscriber.
In addition further service- and policy-specific information regarding handling of packet flows according to agreed quality and performance requests - such as denoted by Quality of Service (QoS) or Quality of Experience (QoE) parameters - may be needed, e.g. for prioritization of packet forwarding with respect to latency demands or required high reliability. Such features would ask for preferred assignment of specific network function locations during construction of a constrained service function path (SFP), and for computation of a concrete Rendered Service Path (RSP) i.e. the actual sequence of SFs and SF Forwarders (SFFs), e.g. by a service classification function according to [RFC7665], which can be executed as described in [I-D.ietf-sfc-control-plane] and *. SFs and SFFs involved honor their part of the service or slice ID contained assurance contract by being e.g. characterized by low transmission delay between each other, by exposing a high availability of resources to process function tasks, or by redundancy provided by stand-by machines for seamless execution continuation in case of failures. These requirements may be satisfied by means of control protocols, but there might be some value to convey such signal to SFC-aware nodes in data packets to simplify state that would be required to check whether a packet is to be granted a given service.
This document adheres to the architecture defined in [RFC7665]. This document assumes the reader is familiar with [RFC7665] and [I-D.ietf-sfc-control-plane].
Subscriber-related information may be required to implement services such as, but not limited to, traffic policy control, or parental control and traffic offload that are commonly used by operators to enable added value services to their customers in typical network architectures [I-D.liu-sfc-use-cases].
Another typical example is the applicability of service chaining in the context of mobile networks (typically, in the 3GPP defined (S)Gi Interface) [I-D.ietf-sfc-use-case-mobility]. Because of the widespread use of private addressing in those networks, if advanced SFs to be invoked are located after a NAT device (that can reside in the Packet Data Network (PDN) Gateway (PGW) or in a distinct operator-specific node), the identification based on the internal IP address is not anymore possible once the NAT has been crossed. As such, means to allow passing the internal information may ease the operation of an SFC-enabled domain. Furthermore, some SFs that are not enabled on the PGW may require a subscriber identifier e.g., International Mobile Subscriber Identity (IMSI), to execute their function. Other use cases that suffer from identification problems further are discussed in [RFC7620].
Unless the information contained within such subscriber identifiers already allows for deriving service specific requirements (e.g. of services to which the hosts are subscribed to or which the subscribers are expected to consume according to their contract) and which may impact the choice of optimum specific service function locations (placement and service function path constrains) then also additional service or slice identifiers will be required.
Service-related information may be required to ensure specific service quality and performance such as granted low latency or extreme high reliability as, e.g., demanded for future 'tactile internet' applications or eHealth and industry control as typical examples for expected vertical use cases to be deployed in the framework of logically separated network slices.
This document does not make any assumption about the structure of service identifiers; each information is treated as an opaque value. The meaning and validation of each of these identifiers can be the responsibility of the control plane [I-D.ietf-sfc-control-plane].
Subscriber- and service-related information is stripped from packets exiting an SFC-enabled domain so that privacy-sensitive information is not leaked outside the domain. See Section 8 for more discussion on privacy.
The use cases discussed in this document assume the NSH is used exclusively within a single administrative domain.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
The reader should be familiar with the terms defined in [RFC7665].
Enforcing Policies based on an internal IP address:
Enforcing Policies based on a subscriber identifier:
Enforcing Policies based on a service specific identifier:
Below we present some use cases where problems related to enforcing policies based on subscriber identifiers and those based on service and/or slice identifiers currently cannot be achieved in service function chaining. It is important to note that subscriber identification due to address and prefix sharing is not specific to the service function chaining. This problem occurs in many other use cases as discussed in [RFC7620].
Parental control service function searches each packet for certain content, e.g. destination addresses corresponding to certain URL like 'www.thisbizarresite.com'. Parental control function should keep this information (URL and source IP address) in its cache so that all subsequent packets can be filtered for certain users from the Web server [WT317].
Parental control function receives next packet from the recorded URL. Enforcing the parental control policies may depend on the internal IP address, i.e., the address of the subscriber's host that is being subject to the parental control. Parental control function must be able to identify incoming traffic to be filtered, e.g., specific URL information. All other traffic is not subject to filtering. Parental control function filters all traffic coming from indicated URL only for the specific subscriber' hosts identified by the service logic.
For the virtual CPE case, the access node will receive privately-addressed packets. Because private addresses are overlapping between several subscribers, the internal IP address will need to be copied into a dedicated header in the NSH packet so that upstream SFs responsible for parental control can process the packets appropriately. Furthermore, the subscriber identifier may also be required for authorization purposes.
Traffic offload service function works on each flow/service originated from mobile terminal and decides if it should be offloaded to the broadband network or sent back to the mobile network. In this use case policy enforcement is based on the subscriber identifier. The broadband network must obtain the subscription profile from the mobile network and decide if the traffic coming from this subscriber needs to be offloaded or not. If offloading is needed, this usually means that the subscriber identifier needs to be known on the SFC-aware forwarders.
Many SFs can be executed in different combinations in a mobile network [I-D.ietf-sfc-use-case-mobility]. Placement of NAT function plays an important role if it is used.
If a NAT function is collocated with P-GW as in [TR23.975] or is located right after the P-GW then all service functions located upstream can only see the translated address as the source address from all User Equipments (UEs). Internal IP address-related part of their policy set won't be able to execute their service logic. As a consequence, means to pass the internal IP address (i.e., the original one before executing the NAT function) through the service chain may be needed.
Note that the same problem occurs in case IPv6 is being used by UEs, but UEs need to communicate with an external legacy server which is IPv4-only. This can be made possible with NAT64 as described in [RFC6146]. NAT64 uses IPv4 address on its outgoing interface which is shared by all UEs. So in the case of NAT64 UE identification also becomes an issue in service chaining.
[I-D.ietf-sfc-use-case-mobility] identifies the following information:
Several other use cases where support of traffic classification with respect to service chain selection to achieve efficient and flexible mobile service steering are described in [TR22.808]. A set of potential solutions are proposed and discussed in [TR23.718] where partly the SFC approach, and NSH, for traffic steering are already referenced.
Extreme or ultra-low latency Use Case as foreseen for so-called '5G' system of next generation (not only) mobile networks, e.g. by 3GPP [TR22.862] requires specific architectural and protocol characteristics to allow for rapid execution and low transmission delay of packets within services as for example medical, industrial, or vehicular applications. This can be granted by forwarding all packets via the shortest paths only and/or via the service functions granting lowest processing delay.
Another set of use cases within the critical communications family demands for very (or ultra-) high reliability of services as defined by 3GPP in [TR22.862] by 'High Reliable communication services are characterized by the service layer need of committed QoS targets and its possibility to act upon an expected change of the network fulfillment of the QoS targets.' This can be granted by forwarding all packets via the most reliable and secure paths only.
Subscriber Identifier is defined as optional variable-length NSH context header. Its structure is shown in Figure 1.
The subscriber identifier is used to convey an identifier already assigned by the service provider to uniquely identify a subscriber or an information that is required to enforce per-subscriber policies, the structure of the identifier is deployment-specific. Typically, this header may convey the IMSI, an opaque subscriber Identifier, an IP address, etc.
The classifier and SFC-aware Service Functions MAY be instructed via a control interface to inject or strip a subscriber identifier context header. Also, the data to be injected in such header SHOULD be configured to nodes authorized to inject such headers. Failures to inject such headers SHOULD be logged locally while a notification alarm MAY be sent to a Control Element. The level of sending notification alarms SHOULD be configurable by the control plane.
This document adheres to the recommendations in [RFC8300] for handling the context headers at both ingress and egress SFC boundary nodes. That is, to strip such context headers.
SFC-aware SFs and proxies MAY be instructed to strip a subscriber identifier from the packet or to pass the data to the next SF in the chain after consuming the content of the headers. If no instruction is provided, the default behavior is to maintain such context headers so that the information can be passed to next SFC-aware hops.
SFC-aware functions MAY be instructed via the control plane about the validation checks to follow on the content of these context headers (e.g., accept only some lengths, accept some subtypes) and the behavior to follow. For example, SFC-aware nodes may be instructed to ignore the context header, to remove the context header from the packet, etc. Nevertheless, this specification does not require nor preclude such additional validation checks. These validation checks are deployment-specific. If validation checks fail on a context header, an SFC-aware node ignores that context header. The event SHOULD be logged locally while a notification alarm MAY be sent to a control element if the SFC-aware node is instructed to do so.
Multiple subscriber Identifier context TLVs MAY be present in the NSH each conveying a distinct sub-type.
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Metadata Class | Type |U| Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SubT | |
+-+-+-+-+-+-+-+-+
~ Subscriber Identifier ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Subscriber Identifier Variable-Length Context Header
The description of the fields is as follows:
Dedicated service- and slice specific performance Identifiers are defined to differentiate between services requiring specific treatment to exhibit a performance characterized by, e.g., ultra-low latency (ULL) or ultra-high reliability (UHR). These parameters are related to slice and service identifiers and (among potentially others) are contained and transported within the service Identifier. The service Identifier thus allows for enforcement of a per service policy such as a service classification function to only consider dedicated Service Functions during service function path construction. Details of this process are implementation specific. For illustration, the classifier may retrieve via the corresponding service or slice ID from a data base of the details of usable service functions. Exemplary characteristics of specific service function instantiations may be location or distance from service session endpoints or processing speed in case of ULL. For UHR the stand-by operation of back-up capacity or a redundant deployment of service function instantiations may be requested for all Service Functions selectable by the classifier when applying for a service denoted by this ID. In other words the classifier uses this kind of information to decide about the set of SFFs to invoke to honor the latency or reliability requirement (e.g., compute an RSP or insert a pointer to be shared with involved SFFs).
Slice and Service Identifiers are defined as optional variable length context headers. Their structure is shown in Figure 2 and Figure 3, respectively.
Service/Slice Identifier context header MAY convey a user or service provider defined unique identity which can be described by an opaque value.
The service requirements in terms of, e.g., but not limited to, parameters as maximum latency or minimum outrage probability are to be specified by service providers and not in scope of this document.
General considerations as mentioned above for subscriber identifier correspondingly apply here (see Section 4).
Only one Slice Identifier context header MUST be present in the NSH.
Multiple Service Identifier context headers MAY be present in the NSH; each conveying a distinct sub-type.
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Metadata Class | Type |U| Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Slice Identifier ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: Slice Identifier Variable-Length Context Header
The description of the fields is as follows:
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Metadata Class | Type |U| Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SubT | |
+-+-+-+-+-+-+-+-+
~ Service Identifier ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: Service Identifier Variable-Length Context Header
The description of the fields is as follows:
This document requests IANA to assign the followiing types from the "NSH IETF- Assigned Optional Variable-Length Metadata Types" (0x0000 IETF Base NSH MD Class) registry available at: https://www.iana.org/assignments/nsh/nsh.xhtml#optional-variable-length-metadata-types.
| C1 | C2 | |
|---|---|---|
| TBD1 | Subscriber Identifier | [ThisDocument] |
| TBD2 | Slice Identifier | [ThisDocument] |
| TBD3 | Service Identifier | [ThisDocument] |
Data plane SFC-related security considerations are discussed in [RFC7665] and [RFC8300].
A misbehaving node can inject subscriber Identifiers to disturb the service offered to some subscribers. Also, a misbehaving node can inject subscriber identifiers as an attempt to be granted access to some services. To prevent such misbehavior, only trusted nodes MUST be able to inject such context headers. Nodes that are involved in a SFC-enabled domain are asumed to be trusted ([RFC8300]). Means to check that only authorized nodes are solicited when a packet is crossing an SFC-enabled domain.
The metadata defined in this document for subscriber identifiers may reveal private information about the subscriber. Some privacy-related considerations for Internet Protocols are discussed in [RFC6973] and [RFC6967]. In the light of these privacy considerations, it is important to state that the subscriber metadata MUST NOT be exposed outside the operator's domain. This requirement is already supported by the NSH [RFC8300]. That is, NSH is stripped systimaticlaly at the egress of a service chain.
The information conveyed in subscriber identifiers is already known to an administrative entity managing an SFC-enabled domain. Some of that information is already conveyed in the original packets from a host (e.g., internal IP address) while other information is collected from various sources (e.g., GTP tunnel, line identifier, etc.). Conveying such sensitive information in packets may expose subscribers' sensitive data to entities that are not allowed to receive such information. Misbehaving SFC egress nodes is a threat that may have negative impacts on privacy (e.g., some operational networks leak the MSISDN outside). Operators MUST ensure their SFC-enabled domain is appropriately conforming to the NSH specification so that any privacy-related information is not exposed outside the SFC-enabled domain.
Some use cases that rely upon the solution defined in this document may disclose some additional privacy-related information (e.g., a host identifier of a terminal within a customer premises for the parental control case). It is assumed that this information is provided upon approval from a subscriber [RFC8165]. For example, a customer may provide the information as part of its service management interface or as part of explicit subscription form.
Comments from Joel Halpern on a previous version are appreciated.
This work has been partially performed in the framework of the EU-funded H2020-ICT-2014-2 project 5G NORMA. Contributions of the project partners are gratefully acknowledged. The project consortium is not liable for any use that may be made of any of the information contained therein.
| [RFC2119] | Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997. |
| [RFC7665] | Halpern, J. and C. Pignataro, "Service Function Chaining (SFC) Architecture", RFC 7665, DOI 10.17487/RFC7665, October 2015. |
| [RFC8300] | Quinn, P., Elzur, U. and C. Pignataro, "Network Service Header (NSH)", RFC 8300, DOI 10.17487/RFC8300, January 2018. |