{"draft":"draft-ietf-pce-pcep-flowspec-13","doc_id":"RFC9168","title":"Path Computation Element Communication Protocol (PCEP) Extension for Flow Specification","authors":["D. Dhody","A. Farrel","Z. Li"],"format":["HTML","TEXT","PDF","XML"],"page_count":"29","pub_status":"PROPOSED STANDARD","status":"PROPOSED STANDARD","source":"Path Computation Element","abstract":"The Path Computation Element (PCE) is a functional component capable\r\nof selecting paths through a traffic engineering (TE) network.  These\r\npaths may be supplied in response to requests for computation or may\r\nbe unsolicited requests issued by the PCE to network elements.  Both\r\napproaches use the PCE Communication Protocol (PCEP) to convey the\r\ndetails of the computed path.\r\n\r\nTraffic flows may be categorized and described using \"Flow\r\nSpecifications\".  RFC 8955 defines the Flow Specification and\r\ndescribes how Flow Specification components are used to describe\r\ntraffic flows.  RFC 8955 also defines how Flow Specifications may be\r\ndistributed in BGP to allow specific traffic flows to be associated\r\nwith routes.\r\n\r\nThis document specifies a set of extensions to PCEP to support\r\ndissemination of Flow Specifications.  This allows a PCE to indicate\r\nwhat traffic should be placed on each path that it is aware of.\r\n\r\nThe extensions defined in this document include the creation, update,\r\nand withdrawal of Flow Specifications via PCEP and can be applied to\r\ntunnels initiated by the PCE or to tunnels where control is delegated\r\nto the PCE by the Path Computation Client (PCC). Furthermore, a PCC\r\nrequesting a new path can include Flow Specifications in the request\r\nto indicate the purpose of the tunnel allowing the PCE to factor this\r\ninto the path computation.","pub_date":"January 2022","keywords":["PCE","FlowSpec","Flow Spec"],"obsoletes":[],"obsoleted_by":[],"updates":[],"updated_by":["RFC9756"],"see_also":[],"doi":"10.17487\/RFC9168","errata_url":null}