%% You should probably cite draft-ivov-rtcweb-noplan-01 instead of this revision.
@techreport{ivov-rtcweb-noplan-00,
    number =    {draft-ivov-rtcweb-noplan-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-ivov-rtcweb-noplan/00/},
    author =    {Emil Ivov},
    title =     {{No Plan: Economical Use of the Offer/Answer Model in WebRTC Sessions with Multiple Media Sources}},
    pagetotal = 15,
    year =      2013,
    month =     may,
    day =       29,
    abstract =  {This document describes a model for the lightweight use of SDP Offer/ Answer in WebRTC. The goal is to minimize reliance on Offer/Answer exchanges in a WebRTC session and provide applications with the tools necessary to implement the signalling that they may need in a way that best fits their custom requirements and topologies. This simplifies signalling of multiple media sources or providing RTP Synchronisation source (SSRC) identification in multi-party sessions. Another important goal of this model is to remove from clients topological constraints such as the requirement to know in advance all SSRC identifiers that they could potentially introduce in a particular session. This document does not question the use of SDP and the Offer/Answer model or the value they have in terms of interoperability with legacy or other non-WebRTC devices.},
}