%% You should probably cite draft-elkins-v6ops-ipv6-packet-sequence-needed-01 instead of this revision.
@techreport{elkins-v6ops-ipv6-packet-sequence-needed-00,
    number =    {draft-elkins-v6ops-ipv6-packet-sequence-needed-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-elkins-v6ops-ipv6-packet-sequence-needed/00/},
    author =    {Nalini Elkins and Michael Ackermann and Keven Haining and Sigfrido Perdomo and William Jouris and David Boyes},
    title =     {{IPv6 Packet Sequence Number Needed}},
    pagetotal = 14,
    year =      2013,
    month =     may,
    day =       31,
    abstract =  {For a number of Enterprise Data Center Operators (EDCO) both real- time and after the fact problem resolution is critical. Two metrics are critical for timely end-to-end problem resolution, without impacting an operational production network. They are: packet sequence number and packet timestamp. Packet sequence number is required for diagnostics. Packet timestamp is required to calculate end-to-end response time. Current methods are inadequate for these purposes because they assume unreasonable access to intermediate devices, are cost prohibitive, require infeasible changes to a running production network, or do not provide timely data. This document provides the background and rationale for the packet sequence number which is a part of the IPv6 Performance and Diagnostic Metrics Destination Option (PDM).},
}