Service Function Chaining: Subscriber and Policy Identification Variable-Length NSH Context Headers
draft-sfc-serviceid-header-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2018-10-15
Replaced by draft-ietf-sfc-serviceid-header
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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)
SFC                                                          B. Sarikaya
Internet-Draft                                       Denpel Informatique
Intended status: Standards Track                            M. Boucadair
Expires: April 18, 2019                                           Orange
                                                             D. von Hugo
                                                        Deutsche Telekom
                                                        October 15, 2018

    Service Function Chaining: Subscriber and Policy Identification
                  Variable-Length NSH Context Headers
                     draft-sfc-serviceid-header-00

Abstract

   This document discusses how to inform Service Functions (SFs) about
   subscriber- and service-related information for the sake of policy
   enforcement and appropriate SFC-inferred forwarding.

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 April 18, 2019.

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

Sarikaya, et al.         Expires April 18, 2019                 [Page 1]
Internet-Draft    Service, Subscriber and Hostid in SFC     October 2018

   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.  Subscriber Identification NSH Variable-Length Context Header    4
   4.  Policy Identification NSH Variable-Length Context Headers . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   8
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   This document discusses how to inform Service Functions about
   subscriber- and service-related information when required for the
   sake of policy enforcement.  Indeed, subscriber-related information
   may be required to enforce subscriber-specific, SFC-based traffic
   forwarding policies, since the information carried in packets may not
   be sufficient.

   The enforcement of SFC-based differentiated traffic forwarding
   policies may also be inferred by QoS considerations.  QoS information
   may serve as an input to classification of the Service Function Path
   (SFP) for path computation and establishment.

   The dynamic structuring of service function chains and their
   subsequent enforcement may be conditioned by QoS requirements that
   will affect SF instance identification, location, and sequencing.

   Since network and path conditions may change dynamically based on
   e.g. traffic load and radio path variations the path decision and
   configuration mechanisms have to reflect the potentially changing
   context and consider corresponding information network.

   SFs and SF Forwarders (SFFs) involved in an SFC have to contribute to
   the respective QoS requirements 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 in some contexts, (e.g., in networks where resources

Sarikaya, et al.         Expires April 18, 2019                 [Page 2]
Show full document text