Service Function Chaining: Subscriber and Service Identification Use Cases and Variable-Length NSH Context Headers
draft-sarikaya-sfc-hostid-serviceheader-06

Document Type Active Internet-Draft (candidate for sfc WG)
Last updated 2018-02-13 (latest revision 2018-01-17)
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state Call For Adoption By WG Issued
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
SFC                                                         M. Boucadair
Internet-Draft                                                    Orange
Intended status: Standards Track                             D. von Hugo
Expires: July 20, 2018                   Telekom Innovation Laboratories
                                                             B. Sarikaya
                                                                  Huawei
                                                        January 16, 2018

  Service Function Chaining: Subscriber and Service Identification Use
             Cases and Variable-Length NSH Context Headers
               draft-sarikaya-sfc-hostid-serviceheader-06

Abstract

   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.

Status of This Memo

   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 20, 2018.

Copyright Notice

   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

Boucadair, et al.         Expires July 20, 2018                 [Page 1]
Internet-Draft    Service, Subscriber and Hostid in SFC     January 2018

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions and Terminology . . . . . . . . . . . . . . . . .   4
   3.  Problem Space and Sample Use Cases  . . . . . . . . . . . . .   4
     3.1.  Parental Control Use Case . . . . . . . . . . . . . . . .   5
     3.2.  Traffic Offload Use Case  . . . . . . . . . . . . . . . .   6
     3.3.  Mobile Network Use Cases  . . . . . . . . . . . . . . . .   6
     3.4.  Extreme Low Latency Service Use Cases . . . . . . . . . .   7
     3.5.  High Reliability Applications Use Cases . . . . . . . . .   7
   4.  Subscriber Identification NSH Variable-Length Context Header    7
   5.  Slice and Service Identification NSH Variable-Length Context
       Headers . . . . . . . . . . . . . . . . . . . . . . . . . . .   9
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   8.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  12
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  13
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  13
     10.2.  Informative References . . . . . . . . . . . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  15

1.  Introduction

   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
Show full document text