%% You should probably cite draft-ietf-grow-bmp-peer-up instead of this I-D.
@techreport{scudder-grow-bmp-peer-up-00,
    number =    {draft-scudder-grow-bmp-peer-up-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-scudder-grow-bmp-peer-up/00/},
    author =    {John Scudder},
    title =     {{BMP Peer Up Message Namespace}},
    pagetotal = 5,
    year =      2018,
    month =     dec,
    day =       14,
    abstract =  {RFC 7854, BMP, uses different message types for different purposes. Most of these are Type, Length, Value (TLV) structured. One message type, the Peer Up message, lacks a set of TLVs defined for its use, instead sharing a namespace with the Initiation message. Subsequent experience has shown that this namespace sharing was a mistake, as it hampers the extension of the protocol. This document updates RFC 7854 by creating an independent namespace for the Peer Up message. The changes in this document are formal only, compliant implementations of RFC 7854 also comply with this specification.},
}