Service Function Chaining: Subscriber and Policy Identification Variable-Length Network Service Header (NSH) Context Headers
draft-sfc-serviceid-header-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2018-10-25 (latest revision 2018-10-16)
Replaces draft-sarikaya-sfc-hostid-serviceheader
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 19, 2019                                           Orange
                                                             D. von Hugo
                                                        Deutsche Telekom
                                                        October 16, 2018

    Service Function Chaining: Subscriber and Policy Identification
      Variable-Length Network Service Header (NSH) Context Headers
                     draft-sfc-serviceid-header-01

Abstract

   This document discusses how to inform Service Functions about
   subscriber- and service-related information for the sake of policy
   enforcement and appropriate service function chaining operations.

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 19, 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 19, 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 . . . . . . . . . . . . . . . . .   3
   3.  Subscriber Identification NSH Variable-Length Context Header    4
   4.  Policy Identification NSH Variable-Length Context Headers . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   This document discusses how to inform Service Functions (SFs) about
   subscriber- and service-related information when required for the
   sake of policy enforcement within a single administrative domain.
   Particularly, subscriber-related information may be required to
   enforce subscriber-specific SFC-based traffic forwarding policies.
   Nevertheless, the information carried in packets may not be
   sufficient to unambiguously identify a subscriber.  This document
   fills this void by specifying a new Network Service Header (NSH)
   [RFC8300] context header to convey and disseminate such information.

   Also, the enforcement of SFC-based differentiated traffic forwarding
   policies may be inferred by QoS considerations.  Typically, QoS
   information may serve as an input to classification of the Service
   Function Path (SFP) for path computation, establishment, and
   selection.  Furthermore, 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.  Hence, the need to supply a policy identifier to
   upstream SFs to appropriately meet the service requirements.

   SFs and SF Forwarders (SFFs) involved in a service chain have to
   contribute to the respective service policy (QoS, for example)
   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
Show full document text