Service Function Chaining: Subscriber and Performance Policy Identification Variable-Length Network Service Header (NSH) Context Headers
draft-ietf-sfc-serviceid-header-03
SFC B. Sarikaya
Internet-Draft Denpel Informatique
Intended status: Standards Track D. von Hugo
Expires: February 9, 2020 Deutsche Telekom
M. Boucadair
Orange
August 8, 2019
Service Function Chaining: Subscriber and Performance Policy
Identification Variable-Length Network Service Header (NSH) Context
Headers
draft-ietf-sfc-serviceid-header-03
Abstract
This document defines Subscriber and Performance Policy Identifiers
Network Service Header Variable-Length Context Headers to inform
Service Functions about subscriber- and service-related information
for the sake of policy enforcement and appropriate service function
chaining operations. The structure of each context header is
defined, their use and processing instructions by SFC-aware nodes are
explained.
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 February 9, 2020.
Copyright Notice
Copyright (c) 2019 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 February 9, 2020 [Page 1]
Internet-Draft NSH Subscriber/Performance Policy TLVs August 2019
(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 . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
8. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 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 (SFs,
[RFC7665]) 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
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
within the boundaries of a single administrative domain.
Also, the enforcement of SFC-based differentiated traffic policies
may be inferred, for example, by QoS (Quality of Service)
considerations. Typically, QoS information may serve as an input to
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 performance
policy identifier to upstream SFs to appropriately meet the service
Show full document text