%% You should probably cite rfc5225 instead of this I-D.
@techreport{ietf-rohc-rfc3095bis-rohcv2-profiles-06,
    number =    {draft-ietf-rohc-rfc3095bis-rohcv2-profiles-06},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-rohc-rfc3095bis-rohcv2-profiles/06/},
    author =    {Kristofer Sandlund and Ghyslain Pelletier},
    title =     {{RObust Header Compression Version 2 (ROHCv2): Profiles for RTP, UDP, IP, ESP and UDP-Lite}},
    pagetotal = 124,
    year =      2008,
    month =     mar,
    day =       19,
    abstract =  {This document specifies ROHC (Robust Header Compression) profiles that efficiently compress RTP/UDP/IP (Real-Time Transport Protocol, User Datagram Protocol, Internet Protocol), RTP/UDP-Lite/IP (User Datagram Protocol Lite), UDP/IP, UDP-Lite/IP, IP and ESP/IP (Encapsulating Security Payload) headers. This specification defines a second version of the profiles found in RFC 3095, RFC 3843 and RFC 4019; it supersedes their definition, but does not obsolete them. The ROHCv2 profiles introduce a number of simplifications to the rules and algorithms that govern the behavior of the compression endpoints. It also defines robustness mechanisms that may be used by a compressor implementation to increase the probability of decompression success when packets can be lost and/or reordered on the ROHC channel. Finally, the ROHCv2 profiles define their own specific set of header formats, using the ROHC formal notation. {[}STANDARDS-TRACK{]}},
}