[Pce] FW: I-D Action: draft-ietf-pce-pcep-flowspec-11.txt
Adrian Farrel <adrian@olddog.co.uk> Mon, 05 October 2020 14:35 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 C3BF23A0B23; Mon, 5 Oct 2020 07:35:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] 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 fSpwvG9xKGtn; Mon, 5 Oct 2020 07:35:18 -0700 (PDT)
Received: from mta5.iomartmail.com (mta5.iomartmail.com [62.128.193.155]) (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 AFEE33A0C4A; Mon, 5 Oct 2020 07:34:38 -0700 (PDT)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta5.iomartmail.com (8.14.4/8.14.4) with ESMTP id 095EYWFq028600; Mon, 5 Oct 2020 15:34:32 +0100
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 09C132204A; Mon, 5 Oct 2020 15:34:32 +0100 (BST)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs1.iomartmail.com (Postfix) with ESMTPS id EF5EC22048; Mon, 5 Oct 2020 15:34:31 +0100 (BST)
Received: from LAPTOPK7AS653V ([213.205.192.60]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id 095EYTjE010877 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 5 Oct 2020 15:34:30 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Alvaro Retana' <alvaro.retana@futurewei.com>, 'Benjamin Kaduk' <kaduk@mit.edu>
Cc: pce@ietf.org, draft-ietf-pce-pcep-flowspec.all@ietf.org
References: <160190801030.30135.3157548145763161216@ietfa.amsl.com>
In-Reply-To: <160190801030.30135.3157548145763161216@ietfa.amsl.com>
Date: Mon, 05 Oct 2020 15:34:28 +0100
Organization: Old Dog Consulting
Message-ID: <025f01d69b24$a2968630$e7c39290$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-gb
Thread-Index: AQJO2DPuiFXpQQMbgjGSfN9xAMtx0qiYlxjQ
X-Originating-IP: 213.205.192.60
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-25706.007
X-TM-AS-Result: No--23.098-10.0-31-10
X-imss-scan-details: No--23.098-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-25706.007
X-TMASE-Result: 10--23.098100-10.000000
X-TMASE-MatchedRID: 4UuLw6eavcJB0jhVMKrChXFPUrVDm6jtrkGhd90/DD6mff+97VoHWXoF iw0nfs0u3ypCQAt/sUBAEhf7NmOM0V451c3VQH3aem6WLgiP1LeVq+okl1rYDwg2kgWdt3qaggd 4VfTBE92xMJ5xZ0J5p2cDAouApUYAGvrGmKKpCuxZMZ6MZ0H1UsQYGgcp3dr53PShNosIMB595E epdMBiBqyyBD+iCWcdKUxV/pukgbAAP4qmkeEV8MzWN98iBBeGSqUiK/0JE/nExrYTAUEIESTCV wyY5KnUqjtz90j0VPm3JvBH0Duz9CKSpG+tIlC/UPktDdOX0fshauGyjTkf9Z4jWPBZdp4jK2y2 JriWXWOfTcakW7K3Sabdy+VRalbbkxWCkRXTjWL9CtRM0nKOKQoXSOLC5a44zpFggQI5ZKqzH1Q OVV9gxo05+NqVZISjB3VSDyZ06aEW5GQtBQ2cquCdOJAyA+r+guwtqyXlE6FTq//rncsNWfU9QW n2RfXfA3GvyENlx3s0S0/W73mBUepgIzDCH485ypiC33/79mfg02I3oyGU8AzhqO1r19zyc2uUR v2pMpRPp0HKBj4EXwGgqRQZQsCiN2GXzj6bC8I14ETxvAKbskKOGTgHJV9S5kyJys6UhUmB+duJ cV6+5aqOgXCvJP4WlPDcOEV7JP148YB5KfXbgsn9tWHiLD2GQutb7tNByL9psnGGIgWMmWyHarF SgTJkfW39y7WGAbbvUgEi1slrvx2qKsO3soOMwrUhv0kAAvFTbzA1C0+Yc1qEAQv2j5Nb9xu1Zb 5VzUtag8dnetN8+KxyDkM+AFlZcpBwVWvgqp2eAiCmPx4NwLTrdaH1ZWqCpvI8UZOf47hcRgd0H R6VpXQdJ7XfU86ekGUtrowrXLg=
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/EL9qcDzOf3m7p0yH__fUIqWNfhc>
Subject: [Pce] FW: I-D Action: draft-ietf-pce-pcep-flowspec-11.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: Mon, 05 Oct 2020 14:35:22 -0000
Alvaro and Ben, Very sorry for delaying this progress so much and possibly causing your cache not only to be flushed, but the archive tapes sent to the fire-vault in Utah. The last issue you had remaining was that 5575bis has removed the possibility of multiple Flow Specification components of the same type being present in one flow specification. We have aligned with this with two changes: - Added text to Section 7 saying: As described in [I-D.ietf-idr-rfc5575bis] where it says "A given component type MAY (exactly once) be present in the Flow Specification," a Flow Filter TLV MUST NOT contain more than one Flow Specification TLV of the same type: an implementation that receives a PCEP message with a Flow Filter TLV that contains more than one Flow Specification TLV of the same type MUST respond with a PCErr message with error-type TBD8 (FlowSpec Error), error-value 2 (Malformed FlowSpec) and MUST NOT install the Flow Specification. - Section 8.4 has been rewritten to mainly say "use separate Flow Specification Objects for separate flow specifications" This -11 revision picks up all other outstanding comments and nits. Best, Adrian -----Original Message----- From: I-D-Announce <i-d-announce-bounces@ietf.org> On Behalf Of internet-drafts@ietf.org Sent: 05 October 2020 15:27 To: i-d-announce@ietf.org Cc: pce@ietf.org Subject: I-D Action: draft-ietf-pce-pcep-flowspec-11.txt 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-11.txt Pages : 37 Date : 2020-10-05 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 requests 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. The extensions defined in this document include the creation, update, and withdrawal of Flow Specifications via PCEP, and can be applied to tunnels initiated by the PCE or to tunnels where control is delegated to the PCE by the PCC. Furthermore, a PCC requesting a new path can include Flow Specifications in the request to indicate the purpose of the tunnel allowing the PCE to factor this into the path computation. 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. 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-11 https://datatracker.ietf.org/doc/html/draft-ietf-pce-pcep-flowspec-11 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-pcep-flowspec-11 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
- [Pce] I-D Action: draft-ietf-pce-pcep-flowspec-11… internet-drafts
- [Pce] FW: I-D Action: draft-ietf-pce-pcep-flowspe… Adrian Farrel
- Re: [Pce] FW: I-D Action: draft-ietf-pce-pcep-flo… Alvaro Retana
- Re: [Pce] FW: I-D Action: draft-ietf-pce-pcep-flo… Benjamin Kaduk
- Re: [Pce] FW: I-D Action: draft-ietf-pce-pcep-flo… Benjamin Kaduk