@techreport{aboba-avtcore-sfu-rtp-00,
    number =    {draft-aboba-avtcore-sfu-rtp-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-aboba-avtcore-sfu-rtp/00/},
        author =    {Dr. Bernard D. Aboba},
    title =     {{Codec-Independent Selective Forwarding}},
    pagetotal = 15,
    year =      2015,
    month =     jul,
    day =       6,
    abstract =  {Selective Forwarding Units (SFUs) supporting Scalable Video Coding (SVC) typically parse the RTP payload in the forwarding plane, and often utilize codec-specific control messages within the control plane. As a result, the control and/or forwarding planes of these implementations need to be modified (sometimes substantially) in order to support additional video codecs. With SFUs now supporting VP8 in addition to H.264/SVC, and with additional video codecs expected to become popular, the inflexibility of SFU designs that depend on RTP payload parsing has become increasingly apparent. In addition, these designs cannot function where the RTP payload is inaccessible, such as when it is encrypted with a key not available to the SFU. Based on a summary of SFU implementation practice, this document develops requirements for codec-independent SFUs.},
}