Synonymous Flow Label Framework
draft-ietf-mpls-sfl-framework-11
MPLS Working Group S. Bryant
Internet-Draft Futurewei Technologies Inc
Intended status: Standards Track M. Chen
Expires: April 5, 2021 Huawei
G. Swallow
Southend Technical Center
S. Sivabalan
Ciena Corporation
G. Mirsky
ZTE Corp.
October 02, 2020
Synonymous Flow Label Framework
draft-ietf-mpls-sfl-framework-11
Abstract
RFC 8372 (MPLS Flow Identification Considerations) describes the
requirement for introducing flow identities within the MPLS
architecture. This document describes a method of accomplishing this
by using a technique called Synonymous Flow Labels in which labels
which mimic the behaviour of other labels provide the identification
service. These identifiers can be used to trigger per-flow
operations on the packet at the receiving label switching router.
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 5, 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
Bryant, et al. Expires April 5, 2021 [Page 1]
Internet-Draft MPLS FL October 2020
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
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 2
3. Synonymous Flow Labels . . . . . . . . . . . . . . . . . . . 3
4. User Service Traffic in the Data Plane . . . . . . . . . . . 4
4.1. Application Label Present . . . . . . . . . . . . . . . . 4
4.1.1. Setting TTL and the Traffic Class Bits . . . . . . . 5
4.2. Single Label Stack . . . . . . . . . . . . . . . . . . . 5
4.2.1. Setting TTL and the Traffic Class Bits . . . . . . . 6
4.3. Aggregation of SFL Actions . . . . . . . . . . . . . . . 6
5. Equal Cost Multipath Considerations . . . . . . . . . . . . . 7
6. Privacy Considerations . . . . . . . . . . . . . . . . . . . 8
7. Security Considerations . . . . . . . . . . . . . . . . . . . 8
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
9. Contributing Authors . . . . . . . . . . . . . . . . . . . . 8
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
10.1. Normative References . . . . . . . . . . . . . . . . . . 8
10.2. Informative References . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
[RFC8372] (MPLS Flow Identification Considerations) describes the
requirement for introducing flow identities within the MPLS
architecture. This document describes a method of providing the
required identification by using a technique called Synonymous Flow
Labels (SFL) in which labels which mimic the behaviour of other MPLS
labels provide the identification service. These identifiers can be
used to trigger per-flow operations on the packet at the receiving
label switching router.
2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
Show full document text