<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ivov-rtcweb-noplan" target="https://datatracker.ietf.org/doc/html/draft-ivov-rtcweb-noplan-01">
   <front>
      <title>No Plan: Economical Use of the Offer/Answer Model in WebRTC Sessions with Multiple Media Sources</title>
      <author initials="E." surname="Ivov" fullname="Emil Ivov">
         <organization>Jitsi</organization>
      </author>
      <author initials="E." surname="Marocco" fullname="Enrico Marocco">
         <organization>Telecom Italia</organization>
      </author>
      <author initials="P." surname="Thatcher" fullname="Peter Thatcher">
         <organization>Google</organization>
      </author>
      <date month="June" day="17" year="2013" />
      <abstract>
	 <t>   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.

   The model described here is similar to the one employed by the data
   channel JavaScript APIs in WebRTC, where methods are supported on
   PeerConnection without being reflected in SDP.

   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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ivov-rtcweb-noplan-01" />
   
</reference>
