RTCWeb Offer/Answer Protocol (ROAP)

Document Type Expired Internet-Draft (individual)
Last updated 2012-05-02 (latest revision 2011-10-30)
Stream (None)
Intended RFC status (None)
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


This document describes an protocol used to negotiate media between browsers or other compatible devices. This protocol provides the state machinery needed to implement the offer/answer model (RFC 3264), and defines the semantics and necessary attributes of messages that must be exchanged. The protocol uses an abstract transport in that it does not actually define how these messages are exchanged. Rather, such exchanges are handled through web-based transports like HTTP or WebSockets. The protocol focuses solely on media negotiation and does not handle call control, call processing, or other functions.


Cullen Jennings (fluffy@cisco.com)
Jonathan Rosenberg (jdrosen@jdrosen.net)
Randell Jesup (randell-ietf@jesup.org)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)