Re: [Pce] FW: I-D Action: draft-ietf-pce-pcep-flowspec-11.txt

Hi Adrian,

It turns out that the tapes were still in the local safe awaiting transfer
to Utah.  Nonessential travel still restricted, and whatnot...

Thanks for the updates in the -11; I've change my position to No Objection.

Deborah: if I understand correctly, this one is ready to be approved.

-Ben

On Mon, Oct 05, 2020 at 03:34:28PM +0100, Adrian Farrel wrote:
> 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
> 