%% You should probably cite draft-ietf-pcn-encoding-comparison instead of this I-D.
@techreport{chan-pcn-encoding-comparison-04,
    number =    {draft-chan-pcn-encoding-comparison-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-chan-pcn-encoding-comparison/04/},
    author =    {Kwok Chan and Georgios Karagiannis and T Moncaster and Michael Menth and Philip Eardley and Bob Briscoe},
    title =     {{Pre-Congestion Notification Encoding Comparison}},
    pagetotal = 34,
    year =      2009,
    month =     mar,
    day =       8,
    abstract =  {A number of mechanisms have been proposed to support differential Qualiy of Service for packets in the Internet. DiffServ is an example of such a mechanism. However, the level of assurance that can be provided with DiffServ without substantial over-provisioning is limited. Pre-Congestion Notification (PCN) uses path congestion information across a PCN region to enable per-flow admission control to provide the required service guarantees for the admitted traffic. While admission control will protect the QoS under normal operating conditions, an additional flow termination mechanism is necessary to cope with extreme events (e.g. route changes due to link or node failure). In order to allow the PCN mechanisms to work it is necessary for IP packets to be able to carry the pre-congestion information to the PCN egress nodes. This document explores different ways in which this information can be encoded into IP packets. This document does not choose the encoding but provide guidance and recommendation based on different criteria. This document also provides a historical trace of the consideration on different encoding alternatives for Pre- Congestion Notification.},
}