Service Function Chaining (SFC): Subscriber and Host Identification Considerations
draft-sarikaya-sfc-hostid-serviceheader-02

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-06-01
Replaced by draft-sfc-serviceid-header
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                       M. Boucadair
Internet-Draft                                                    Orange
Intended status: Standards Track                             D. von Hugo
Expires: December 3, 2016                Telekom Innovation Laboratories
                                                             B. Sarikaya
                                                                  Huawei
                                                            June 1, 2016

  Service Function Chaining (SFC): Subscriber and Host Identification
                             Considerations
             draft-sarikaya-sfc-hostid-serviceheader-02.txt

Abstract

   This document discusses considerations related to passing host- 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 http://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 December 3, 2016.

Copyright Notice

   Copyright (c) 2016 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
   (http://trustee.ietf.org/license-info) in effect on the date of

Boucadair, et al.       Expires December 3, 2016                [Page 1]
Internet-Draft        Subscriber and Hostid in SFC             June 2016

   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 . . . . . . . . . . . . . . . . .   3
   3.  Problem Space and Sample Use Cases  . . . . . . . . . . . . .   3
     3.1.  Parental Control Use Case . . . . . . . . . . . . . . . .   4
     3.2.  Traffic Offload Use Case  . . . . . . . . . . . . . . . .   5
     3.3.  Mobile Network Use Cases  . . . . . . . . . . . . . . . .   5
   4.  Host and Subscriber Identification SFC Meta Data  . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   9
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   This document focuses on aspects related to passing host- 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 host or a subscriber.

   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].

   Host-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

Boucadair, et al.       Expires December 3, 2016                [Page 2]
Show full document text