%% You should probably cite rfc6128 instead of this I-D.
@techreport{ietf-avt-rtcp-port-for-ssm-04,
    number =    {draft-ietf-avt-rtcp-port-for-ssm-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-ietf-avt-rtcp-port-for-ssm/04/},
    author =    {Ali C. Begen},
    title =     {{RTP Control Protocol (RTCP) Port for Source-Specific Multicast (SSM) Sessions}},
    pagetotal = 6,
    year =      2010,
    month =     dec,
    day =       15,
    abstract =  {The Session Description Protocol (SDP) has an attribute that allows RTP applications to specify an address and a port associated with the RTP Control Protocol (RTCP) traffic. In RTP-based source-specific multicast (SSM) sessions, the same attribute is used to designate the address and the RTCP port of the Feedback Target in the SDP description. However, the RTCP port associated with the SSM session itself cannot be specified by the same attribute to avoid ambiguity, and thus, is required to be derived from the "m=" line of the media description. Deriving the RTCP port from the "m=" line imposes an unnecessary restriction. This document removes this restriction by introducing a new SDP attribute. {[}STANDARDS-TRACK{]}},
}