PCEP Extension for Flow Specification
draft-ietf-pce-pcep-flowspec-08
|
| Document |
Type |
|
Active Internet-Draft (pce WG)
|
|
Last updated |
|
2020-03-04
|
|
Replaces |
|
draft-li-pce-pcep-flowspec
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
plain text
xml
pdf
htmlized (tools)
htmlized
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
Waiting for WG Chair Go-Ahead
Doc Shepherd Follow-up Underway, Other - see Comment Log
|
|
Document shepherd |
|
Julien Meuric
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
Julien Meuric <julien.meuric@orange.com>
|
Network Working Group D. Dhody
Internet-Draft Huawei Technologies
Intended status: Standards Track A. Farrel
Expires: September 5, 2020 Old Dog Consulting
Z. Li
Huawei Technologies
March 4, 2020
PCEP Extension for Flow Specification
draft-ietf-pce-pcep-flowspec-08
Abstract
The Path Computation Element (PCE) is a functional component capable
of selecting paths through a traffic engineering network. These
paths may be supplied in response to requests for computation, or may
be unsolicited instructions issued by the PCE to network elements.
Both approaches use the PCE Communication Protocol (PCEP) to convey
the details of the computed path.
Traffic flows may be categorized and described using "Flow
Specifications". RFC XXXX defines the Flow Specification and
describes how Flow Specification Components are used to describe
traffic flows. RFC XXXX also defines how Flow Specifications may be
distributed in BGP to allow specific traffic flows to be associated
with routes.
This document specifies a set of extensions to PCEP to support
dissemination of Flow Specifications. This allows a PCE to indicate
what traffic should be placed on each path that it is aware of.
RFC Editor Note: Please replace XXXX in the Abstract with the RFC
number assigned to draft-ietf-idr-rfc5575bis when it is published.
Please remove this note.
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
Dhody, et al. Expires September 5, 2020 [Page 1]
Internet-Draft PCEP-FlowSpec March 2020
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 September 5, 2020.
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
(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 . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Procedures for PCE Use of Flow Specifications . . . . . . . . 5
3.1. Context for PCE Use of Flow Specifications . . . . . . . 5
3.2. Elements of Procedure . . . . . . . . . . . . . . . . . . 6
3.2.1. Capability Advertisement . . . . . . . . . . . . . . 6
3.2.2. Dissemination Procedures . . . . . . . . . . . . . . 7
3.2.3. Flow Specification Synchronization . . . . . . . . . 8
4. PCE FlowSpec Capability TLV . . . . . . . . . . . . . . . . . 9
5. PCEP FLOWSPEC Object . . . . . . . . . . . . . . . . . . . . 9
6. Flow Filter TLV . . . . . . . . . . . . . . . . . . . . . . . 11
7. Flow Specification TLVs . . . . . . . . . . . . . . . . . . . 12
8. Detailed Procedures . . . . . . . . . . . . . . . . . . . . . 15
8.1. Default Behavior and Backward Compatibility . . . . . . . 16
8.2. Composite Flow Specifications . . . . . . . . . . . . . . 16
8.3. Modifying Flow Specifications . . . . . . . . . . . . . . 16
8.4. Multiple Flow Specifications . . . . . . . . . . . . . . 16
8.5. Adding and Removing Flow Specifications . . . . . . . . . 17
8.6. VPN Identifiers . . . . . . . . . . . . . . . . . . . . . 17
8.7. Priorities and Overlapping Flow Specifications . . . . . 17
9. PCEP Messages . . . . . . . . . . . . . . . . . . . . . . . . 18
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
Show full document text