I-D Action: draft-ietf-pce-pcep-flowspec-05.txt
internet-drafts@ietf.org Thu, 15 August 2019 21:54 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: i-d-announce@ietf.org
Delivered-To: i-d-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 881C61200C7; Thu, 15 Aug 2019 14:54:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: pce@ietf.org
Subject: I-D Action: draft-ietf-pce-pcep-flowspec-05.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.100.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: pce@ietf.org
Message-ID: <156590606246.15865.2578461785759764862@ietfa.amsl.com>
Date: Thu, 15 Aug 2019 14:54:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/i-d-announce/pQHlcVsbUgzGcNuagvJTiC-PPIs>
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Internet Draft Announcements only <i-d-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i-d-announce/>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2019 21:54:22 -0000
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Path Computation Element WG of the IETF. Title : PCEP Extension for Flow Specification Authors : Dhruv Dhody Adrian Farrel Zhenbin Li Filename : draft-ietf-pce-pcep-flowspec-05.txt Pages : 32 Date : 2019-08-15 Abstract: The Path Computation Element (PCE) is a functional component capable of selecting the paths through a traffic engineered 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 5575 defines the Flow Specification and describes how Flow Specification Components are used to describe traffic flows. RFC 5575 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. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-flowspec/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-pce-pcep-flowspec-05 https://datatracker.ietf.org/doc/html/draft-ietf-pce-pcep-flowspec-05 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-pcep-flowspec-05 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/
- I-D Action: draft-ietf-pce-pcep-flowspec-05.txt internet-drafts