[Pce] Update and request for adoption : draft-li-pce-pcep-flowspec-03.txt

"Adrian Farrel" <adrian@olddog.co.uk> Fri, 29 December 2017 18:08 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD71F12D775 for <pce@ietfa.amsl.com>; Fri, 29 Dec 2017 10:08:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level:
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GPm4dhVXMYqM for <pce@ietfa.amsl.com>; Fri, 29 Dec 2017 10:08:52 -0800 (PST)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81A57126DFB for <pce@ietf.org>; Fri, 29 Dec 2017 10:08:52 -0800 (PST)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id vBTI8ngX020082 for <pce@ietf.org>; Fri, 29 Dec 2017 18:08:49 GMT
Received: from 950129200 ([193.56.242.126]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id vBTI8lTG020062 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <pce@ietf.org>; Fri, 29 Dec 2017 18:08:48 GMT
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: pce@ietf.org
Date: Fri, 29 Dec 2017 18:08:50 -0000
Message-ID: <009801d380d0$15818900$40849b00$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdOA0BKuZov6aC+UQlqqWm9PfujIgQ==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.2.0.1013-23562.002
X-TM-AS-Result: No--16.136-10.0-31-10
X-imss-scan-details: No--16.136-10.0-31-10
X-TMASE-MatchedRID: SOu9lCwgpT6TT50vRhVUoPW4u6dw4YBZI0ZIn3NG5Q3jsTquy0JRi83q hpIE26kvwAbihnyeD/BSFJg1tzrrohNKnD37eC8/SEQN/D/3cG696iJ9CCuHwsGQEnQwhjvzf/b TCoZRptJNYvDaO9t+nPE/T9QKeKEbyDB9HAjqDp2VUcz8XpiS9HJrB0Cu3DDnRjHvrQ40NxZZ11 ijMqwnmry+K0fDzPdzXGDsFfPF2wJRYoxf6NUOycWUKBjERoYTMMr4GuNHX1qsafcFLFlU1CzyX B0IS0ld7LAHNqUbR+yoVGBXm1c2KYWDz7mPxd0pJYOiNDWD6sF6PxDI06UtHcj0QMA/92m2DJtp S9qt+hgM60Cmg6+iOu3hgE8lR8EHH6jxW2TDeuSdVNZaI2n6/4N12XKYbuJLDO+DX+rUwfZncpG Qs7S9GTRzIRIo4G/0Bc5l05FO6qvk18JBpE0OqjAoNxJKRrVrfS0Ip2eEHny+qryzYw2E8M8943 oc3p3sq7rFUcuGp/Hfd+P6wwCt84RtqopBKUBlN9slGu+P3f6TCh2RnyTmUSn78susVj0KBAHhP HWPy8jkFFV6SJfFEQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/G1YtEV2max81qMgs8yKflbeUjKM>
Subject: [Pce] Update and request for adoption : draft-li-pce-pcep-flowspec-03.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Dec 2017 18:08:54 -0000

Hi PCE,

This is mainly a keep-alive revision with a little housekeeping (it's amazing
how much of the referenced work has been published as RFCs in the last few
months).

Chatting with Dhruv and our recollection is that there was general support for
this work (specifically for a PCE to be able to tell a headend what traffic to
put on an LSP or SR path). 

Since we have implementations "in the pipe", now would be a really good time for
the WG to think about adopting the work. Over to the chairs for a
decision/action.

Thanks,
Adrian

> -----Original Message-----
> From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of
> internet-drafts@ietf.org
> Sent: 29 December 2017 18:02
> To: i-d-announce@ietf.org
> Subject: I-D Action: draft-li-pce-pcep-flowspec-03.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
directories.
> 
> 
>         Title           : PCEP Extension for Flow Specification
>         Authors         : Dhruv Dhody
>                           Adrian Farrel
>                           Zhenbin Li
> 	Filename        : draft-li-pce-pcep-flowspec-03.txt
> 	Pages           : 25
> 	Date            : 2017-12-29
> 
> 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 directions 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 it 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-li-pce-pcep-flowspec/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-li-pce-pcep-flowspec-03
> https://datatracker.ietf.org/doc/html/draft-li-pce-pcep-flowspec-03
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-li-pce-pcep-flowspec-03
> 
> 
> 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-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt