%% You should probably cite draft-ietf-pce-pcep-stateful-pce-gmpls instead of this I-D.
@techreport{zhang-pce-pcep-stateful-pce-gmpls-01,
    number =    {draft-zhang-pce-pcep-stateful-pce-gmpls-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-zhang-pce-pcep-stateful-pce-gmpls/01/},
    author =    {Xian Zhang and Young Lee and Ramon Casellas and Oscar Gonzalez de Dios},
    title =     {{Path Computation Element (PCE) Protocol Extension for Stateful PCE Usage in GMPLS Networks}},
    pagetotal = 15,
    year =      2012,
    month =     oct,
    day =       18,
    abstract =  {The Path Computation Element (PCE) facilitates Traffic Engineering (TE) based path calculation in large, multi-domain, multi-region, or multi-layer networks. PCE can be stateless or stateful. With the LSP state information acquired from the network, a stateful PCE enables a wide variety of applications, especially in GMPLS networks, such as impairment-aware routing and wavelength assignment in wavelength- switched optical networks (WSON), time-based scheduling applications. This memo provides extensions required for PCE communication protocol (i.e. PCEP) so as to enable the usage of a stateful PCE capability in GMPLS networks. To be more specific, the PCEP extensions specified in this memo include not only new objects but also modification of existing objects in PCEP messages.},
}