@techreport{alvarez-pce-path-profiles-04,
    number =    {draft-alvarez-pce-path-profiles-04},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-alvarez-pce-path-profiles/04/},
    author =    {Santiago Alvarez and Siva Sivabalan and Zafar Ali and Luis Tomotaki and Victor Lopez and Rob Shakir and Jeff Tantsura},
    title =     {{PCE Path Profiles}},
    pagetotal = 13,
    year =      2014,
    month =     nov,
    day =       9,
    abstract =  {This document describes extensions to the Path Computation Element (PCE) Communication Protocol (PCEP) to signal path profile identifiers. A profile represents a list of path parameters or policies that a PCEP peer may invoke on a remote peer using an opaque identifier. When a path computation client (PCC) initiates a path computation request, the PCC can signal profile identifiers to invoke path parameters or policies defined on the PCE which would influence the path computation. Similarly, when a PCE initiates or updates a path, the PCE can signal profile identifiers to invoke path parameters or policies defined on the PCC which would influence the path setup.},
}