%% You should probably cite rfc3759 instead of this I-D.
@techreport{ietf-rohc-terminology-and-examples-02,
    number =    {draft-ietf-rohc-terminology-and-examples-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-ietf-rohc-terminology-and-examples/02/},
    author =    {Lars-Erik Jonsson},
    title =     {{RObust Header Compression (ROHC): Terminology and Channel Mapping Examples}},
    pagetotal = 20,
    year =      2003,
    month =     feb,
    day =       13,
    abstract =  {This document aims to clarify terms and concepts presented in RFC 3095. RFC 3095 defines a Proposed Standard framework with profiles for RObust Header Compression (ROHC). The standard introduces various concepts which might be difficult to understand and especially to relate correctly to the surrounding environments where header compression may be used. This document aims at clarifying these aspects of ROHC, discussing terms such as ROHC instances, ROHC channels, ROHC feedback, and ROHC contexts, and how these terms relate to other terms, like network elements and IP interfaces, commonly used, for example, when addressing MIB issues. This memo provides information for the Internet community.},
}