@techreport{many-pce-pcep-bcp-02,
    number =    {draft-many-pce-pcep-bcp-02},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-many-pce-pcep-bcp/02/},
    author =    {Ramon Casellas and Oscar Gonzalez de Dios and Adrian Farrel and Cyril Margaria and Dhruv Dhody and Xian Zhang},
    title =     {{PCEP Best Current Practices - Message formats and extensions}},
    pagetotal = 21,
    year =      2015,
    month =     apr,
    day =       27,
    abstract =  {A core standards track RFC defines the main underlying mechanisms, basic object format and message structure of the Path Computation Element (PCE) Communications Protocol (PCEP). PCEP has been later extended in several RFCs, focusing on specific functionalities. The proliferation of such companion RFCs may cause ambiguity when implementing a PCE based solution. This document aims at documenting best current practices and at providing a reference RBNF grammar for PCEP messages, including object ordering and precedence rules.},
}