[Pce] FW: New Version Notification for draft-ietf-pce-pcep-flowspec-06.txt

"Adrian Farrel" <adrian@olddog.co.uk> Sat, 02 November 2019 23:29 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 5B3D5120072 for <pce@ietfa.amsl.com>; Sat, 2 Nov 2019 16:29:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id vtXP3nr7cCe1 for <pce@ietfa.amsl.com>; Sat, 2 Nov 2019 16:29:45 -0700 (PDT)
Received: from mta8.iomartmail.com (mta8.iomartmail.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5288120020 for <pce@ietf.org>; Sat, 2 Nov 2019 16:29:44 -0700 (PDT)
Received: from vs2.iomartmail.com (vs2.iomartmail.com []) by mta8.iomartmail.com (8.14.4/8.14.4) with ESMTP id xA2NTgwC006481 for <pce@ietf.org>; Sat, 2 Nov 2019 23:29:42 GMT
Received: from vs2.iomartmail.com (unknown []) by IMSVA (Postfix) with ESMTP id ADEE622044 for <pce@ietf.org>; Sat, 2 Nov 2019 23:29:42 +0000 (GMT)
Received: from asmtp1.iomartmail.com (unknown []) by vs2.iomartmail.com (Postfix) with ESMTPS id 995F122042 for <pce@ietf.org>; Sat, 2 Nov 2019 23:29:42 +0000 (GMT)
Received: from LAPTOPK7AS653V ([]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id xA2NTfeI020705 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <pce@ietf.org>; Sat, 2 Nov 2019 23:29:42 GMT
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
References: <157273711267.5998.5402371998822829565.idtracker@ietfa.amsl.com>
In-Reply-To: <157273711267.5998.5402371998822829565.idtracker@ietfa.amsl.com>
Date: Sat, 2 Nov 2019 23:29:42 -0000
Organization: Old Dog Consulting
Message-ID: <017e01d591d5$67a49ac0$36edd040$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQEUq+uUCIjIID7rrc6wW1wa2Yj4Q6j6UmxQ
Content-Language: en-gb
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-Product-Ver: IMSVA-
X-TM-AS-Result: No--25.172-10.0-31-10
X-imss-scan-details: No--25.172-10.0-31-10
X-TMASE-Result: 10--25.172300-10.000000
X-TMASE-MatchedRID: SpUFBS04J79B0jhVMKrChXFPUrVDm6jtIiTd2l7lf6G67Q3uPo9KI8qa e4dFK5zKSMQbWc3fWqr70SaVHefKTr7NV4PnjfmaSyH6bNPVSdvjBCVg/SxGbziDtkvCXnKtV6G JyRPLfOLQGWZ/vm5ATWc+f+DDdMtIuC0n+lGQyiMc9jA4mLo8uVHewY36PuY0lv1p334rFmNyeL PMYZH47oPnsLLWGT2+VkGKALU+28psMVyAAdvrLbYVne5VEEpVBtG6netTkaWhq7lGRkSlHXGCP Ah3PmLX+ma/pMLmPrbgxFYnLTyi+vpC5SMG+P7Xfc7cX82yHHl3G1bsm5zfjGtEzrC9eANp/4jj lDwf4f7jzUu2NznfJXaD+AlAXmEOJqcDJ9fgy4ozL6MySEJ0VnVNoFzxmabn/Nh5ZjAjQgmn2dT oezJBb4d1YGoonosK2nDxWn8ggSUBSVElkD14Js+Qb/9oChYJSuH+GfgmQGcIiUrQM7y5Avea4u H4Y9hvmU00MdK0iwGfeRswSNWh8rDceXUhrCO3BytCIW2H3sebYck3o66U7Azvg1/q1MH2wZNlF d+3wSzykzK4eLDbgmmevJVqJe6Av1l2Uvx6idoEQBSG7na3yH8DvkUabErVKrauXd3MZDUMFsa+ 1wyh/JRMZUCEHkRt
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/oWnaiuFmOiFAPpKOgYuN2f377hk>
Subject: [Pce] FW: New Version Notification for draft-ietf-pce-pcep-flowspec-06.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 02 Nov 2019 23:29:47 -0000


I think I caught all of the WG last call comments: viz. Acee's RTGDir review.

In Singapore? Need something to read?
Don't waste your time with Internet-Drafts.
Read fairy tales instead.
Fairy stories for adults of all ages
• Tales from the Wood
• More Tales from the Wood
• Tales from Beyond the Wood
• Tales from the Castle
Get them on line https://www.feedaread.com/profiles/8604/
Or buy a signed copy from me by post
*** Stop me in the corridor at IETF-106 to get a copy ***

-----Original Message-----
From: internet-drafts@ietf.org <internet-drafts@ietf.org>; 
Sent: 02 November 2019 23:25
To: Adrian Farrel <adrian@olddog.co.uk>;; Dhruv Dhody <dhruv.ietf@gmail.com>;; Zhenbin Li <lizhenbin@huawei.com>;
Subject: New Version Notification for draft-ietf-pce-pcep-flowspec-06.txt

A new version of I-D, draft-ietf-pce-pcep-flowspec-06.txt
has been successfully submitted by Adrian Farrel and posted to the
IETF repository.

Name:		draft-ietf-pce-pcep-flowspec
Revision:	06
Title:		PCEP Extension for Flow Specification
Document date:	2019-11-02
Group:		pce
Pages:		32
URL:            https://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-flowspec-06.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-flowspec/
Htmlized:       https://tools.ietf.org/html/draft-ietf-pce-pcep-flowspec-06
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-pce-pcep-flowspec
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-pcep-flowspec-06

   The Path Computation Element (PCE) is a functional component capable
   of selecting 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.


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.

The IETF Secretariat