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

Document Type Active Internet-Draft (sfc WG)
Authors Behcet Sarikaya  , Dirk Hugo  , Mohamed Boucadair 
Last updated 2020-11-15
Replaces draft-sfc-serviceid-header
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Greg Mirsky
Shepherd write-up Show (last changed 2020-05-17)
IESG IESG state IESG Evaluation::AD Followup
Consensus Boilerplate Yes
Telechat date
Has 2 DISCUSSes. Has enough positions to pass once DISCUSS positions are resolved.
Responsible AD Martin Vigoureux
Send notices to Greg Mirsky <gregimirsky@gmail.com>
IANA IANA review state Version Changed - Review Needed
SFC                                                          B. Sarikaya
Internet-Draft
Intended status: Standards Track                             D. von Hugo
Expires: May 19, 2021                                   Deutsche Telekom
                                                            M. Boucadair
                                                                  Orange
                                                       November 15, 2020

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

Abstract

   This document defines two Variable-Length Context Headers that can be
   carried in the Network Service Header: the Subscriber and Performance
   Policy Identifiers.  These Context Headers are used to inform Service
   Functions of subscriber- and performance-related information for the
   sake of policy enforcement and appropriate service function chaining
   operations.  The structure of each Context Header, and their use and
   processing by NSH-aware nodes, are described.

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 May 19, 2021.

Copyright Notice

   Copyright (c) 2020 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

Sarikaya, et al.          Expires May 19, 2021                  [Page 1]
Internet-Draft   NSH Subscriber/Performance Policy TLVs    November 2020

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions and Terminology . . . . . . . . . . . . . . . . .   4
   3.  Subscriber Identification NSH Variable-Length Context Header    4
   4.  Performance Policy Identification NSH Variable-Length Context
       Headers . . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   5.  MTU Considerations  . . . . . . . . . . . . . . . . . . . . .   8
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  11
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   This document discusses how to inform Service Functions (SFs)
   [RFC7665] about subscriber and service policy information, when
   required for the sake of policy enforcement within a single
   administrative domain.  In particular, subscriber-related information
   may be required to enforce subscriber-specific SFC-based traffic
   policies.  However, 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
   within the boundaries of a single administrative domain.  As
   discussed in Section 3, the use of obfuscated and non-persistent
   identifiers is recommended.

   Also, traffic steering by means of SFC may be driven, for example, by
   QoS (Quality of Service) considerations.  Typically, QoS information
   may serve as an input for the computation, establishment, and
   selection of the Service Function Path (SFP).  Furthermore, the
   dynamic structuring of service function chains and their subsequent
   SFPs may be conditioned by QoS requirements that will affect SF
   instance(s) identification, location, and sequencing.  Hence, the
   need arises to provide downstream SFs with a performance policy
Show full document text