%% You should probably cite rfc3551 instead of this I-D.
@techreport{ietf-avt-profile-new-13,
    number =    {draft-ietf-avt-profile-new-13},
    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-avt-profile-new/13/},
    author =    {Stephen L. Casner and Henning Schulzrinne},
    title =     {{RTP Profile for Audio and Video Conferences with Minimal Control}},
    pagetotal = 44,
    year =      2003,
    month =     mar,
    day =       7,
    abstract =  {This document describes a profile called "RTP/AVP" for the use of the real-time transport protocol (RTP), version 2, and the associated control protocol, RTCP, within audio and video multiparticipant conferences with minimal control. It provides interpretations of generic fields within the RTP specification suitable for audio and video conferences. In particular, this document defines a set of default mappings from payload type numbers to encodings. This document also describes how audio and video data may be carried within RTP. It defines a set of standard encodings and their names when used within RTP. The descriptions provide pointers to reference implementations and the detailed standards. This document is meant as an aid for implementors of audio, video and other real-time multimedia applications. This memorandum obsoletes RFC 1890. It is mostly backwards-compatible except for functions removed because two interoperable implementations were not found. The additions to RFC 1890 codify existing practice in the use of payload formats under this profile and include new payload formats defined since RFC 1890 was published. {[}STANDARDS-TRACK{]}},
}