Service Function Chaining Service, Subscriber and Host Identification Use Cases and Metadata
draft-sarikaya-sfc-hostid-serviceheader-05
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-07-20
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
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)
|
Network Working Group M. Boucadair
Internet-Draft Orange
Intended status: Standards Track D. von Hugo
Expires: January 21, 2018 Telekom Innovation Laboratories
B. Sarikaya
Huawei
July 20, 2017
Service Function Chaining Service, Subscriber and Host Identification
Use Cases and Metadata
draft-sarikaya-sfc-hostid-serviceheader-05.txt
Abstract
This document discusses considerations related to passing service-,
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 January 21, 2018.
Copyright Notice
Copyright (c) 2017 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 January 21, 2018 [Page 1]
Internet-Draft Service, Subscriber and Hostid in SFC July 2017
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. Problem Space and Sample Use Cases . . . . . . . . . . . . . 4
3.1. Parental Control Use Case . . . . . . . . . . . . . . . . 5
3.2. Traffic Offload Use Case . . . . . . . . . . . . . . . . 6
3.3. Mobile Network Use Cases . . . . . . . . . . . . . . . . 6
3.4. Extreme Low Latency Service Use Cases . . . . . . . . . . 7
3.5. High Reliability Applications Use Cases . . . . . . . . . 7
4. Host and Subscriber Identification SFC Meta Data . . . . . . 7
5. Slice and Service Identification SFC Meta Data . . . . . . . 10
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
7. Security Considerations . . . . . . . . . . . . . . . . . . . 13
8. Privacy Considerations . . . . . . . . . . . . . . . . . . . 13
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
10.1. Normative References . . . . . . . . . . . . . . . . . . 14
10.2. Informative References . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction
This document focuses on aspects related to passing service-, 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.
In addition further service- and policy-specific information
regarding handling of packet flows according to agreed quality and
performance requests - such as denoted by Quality of Service (QoS) or
Quality of Experience (QoE) parameters - may be needed, e.g. for
Show full document text