1<?xml version='1.0' encoding='utf-8'?>
2<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
3<rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="std" number="0000" ipr="trust200902" obsoletes="" updates="" consensus="true" submissionType="IETF" xml:lang="en" tocInclude="true" symRefs="true" sortRefs="true" version="3">
4  <!-- xml2rfc v2v3 conversion 2.23.1 -->
5  <front>
6    <title abbrev="WebRTC Overview">Overview: Real Time Protocols for
7    Browser-based Applications</title>
8    <seriesInfo name="RFC" value="0000"/>
9    <author fullname="Harald T. Alvestrand" initials="H. T." surname="Alvestrand">
10      <organization>Google</organization>
11      <address>
12        <postal>
13          <street>Kungsbron 2</street>
14          <city>Stockholm</city>
15          <region/>
16          <code>11122</code>
17          <country>Sweden</country>
18        </postal>
19        <email>harald@alvestrand.no</email>
20      </address>
21    </author>
22    <date month="July" year="2019"/>
23    <abstract>
24      <t>This document gives an overview and context of a protocol suite
25      intended for use with real-time applications that can be deployed in
26      browsers - "real time communication on the Web".</t>
27      <t>It intends to serve as a starting and coordination point to make sure
28      all the parts that are needed to achieve this goal are findable, and
29      that the parts that belong in the Internet protocol suite are fully
30      specified and on the right publication track.</t>
31      <t>This document is an Applicability Statement - it does not itself
32      specify any protocol, but specifies which other specifications WebRTC
33      compliant implementations are supposed to follow.</t>
34      <t>This document is a work item of the RTCWEB working group.</t>
35    </abstract>
36  </front>
37  <middle>
38    <section numbered="true" toc="default" anchor="Intro">
39      <name>Introduction</name>
40      <t>The Internet was, from very early in its lifetime, considered a
41      possible vehicle for the deployment of real-time, interactive
42      applications - with the most easily imaginable being audio conversations
43      (aka "Internet telephony") and video conferencing.</t>
44      <t>The first attempts to build this were dependent on special networks,
45      special hardware and custom-built software, often at very high prices or
46      at low quality, placing great demands on the infrastructure.</t>
47      <t>As the available bandwidth has increased, and as processors and other
48      hardware has become ever faster, the barriers to participation have
49      decreased, and it has become possible to deliver a satisfactory
50      experience on commonly available computing hardware.</t>
51      <t>Still, there are a number of barriers to the ability to communicate
52      universally - one of these is that there is, as of yet, no single set of
53      communication protocols that all agree should be made available for
54      communication; another is the sheer lack of universal identification
55      systems (such as is served by telephone numbers or email addresses in
56      other communications systems).</t>
57      <t>Development of The Universal Solution has, however, proved hard.</t>
58      <t>The last few years have also seen a new platform rise for deployment
59      of services: The browser-embedded application, or "Web application". It
60      turns out that as long as the browser platform has the necessary
61      interfaces, it is possible to deliver almost any kind of service on
62      it.</t>
63      <t>Traditionally, these interfaces have been delivered by plugins, which
64      had to be downloaded and installed separately from the browser; in the
65      development of HTML5, application developers see much promise in the
66      possibility of making those interfaces available in a standardized way
67      within the browser.</t>
68      <t>This memo describes a set of building blocks that can be made
69      accessible and controllable through a Javascript API in a browser, and
70      which together form a sufficient set of functions to allow the use of
71      interactive audio and video in applications that communicate directly
72      between browsers across the Internet. The resulting protocol suite is
73      intended to enable all the applications that are described as required
74      scenarios in the use cases document <xref target="RFC7478" format="default"/>.</t>
75      <t>Other efforts, for instance the W3C Web Real-Time Communications,
76      Web Applications Security, and Device and Sensor working groups, focus
77      on making standardized APIs and interfaces available, within or
78      alongside the HTML5 effort, for those functions.  This memo concentrates
79      on specifying the protocols and subprotocols that are needed to specify
80      the interactions over the network.</t>
81      <t>Operators should note that deployment of WebRTC will result in a
82      change in the nature of signaling for real time media on the network,
83      and may result in a shift in the kinds of devices used to create and
84      consume such media. In the case of signaling, WebRTC session setup
85      will typically occur over TLS-secured web technologies using
86      application-specific protocols.  Operational techniques that involve
87      inserting network elements to interpret SDP -- either through endpoint
88      cooperation <xref target="RFC3361" format="default"/> or through the transparent
89      insertion of SIP Application Level Gateways (ALGs) -- will not work
90      with such signaling. In the case of networks using cooperative
91      endpoints, the approaches defined in <xref target="RFC8155" format="default"/> may serve
92      as a suitable replacement for <xref target="RFC3361" format="default"/>. The increase in
93      browser-based communications may also lead to a shift away from
94      dedicated real-time-communications hardware, such as SIP
95      desk phones. This will diminish the efficacy of operational
96      techniques that place dedicated real-time devices on their own
97      network segment, address range, or VLAN for purposes such as
98      applying traffic filtering and QoS. Applying the markings
99      described in <xref target="I-D.ietf-tsvwg-rtcweb-qos" format="default"/> may be
100      appropriate replacements for such techniques.</t>
101      <t>This memo uses the term "WebRTC" (note the case used) to refer to the
102      overall effort consisting of both IETF and W3C efforts.</t>
103    </section>
104    <section numbered="true" toc="default">
105      <name>Principles and Terminology</name>
106      <section numbered="true" toc="default">
107        <name>Goals of this document</name>
108        <t>The goal of the WebRTC protocol specification is to specify a set
109        of protocols that, if all are implemented, will allow an
110        implementation to communicate with another implementation using audio,
111        video and data sent along the most direct possible path between the
112        participants.</t>
113        <t>This document is intended to serve as the roadmap to the WebRTC
114        specifications. It defines terms used by other parts of the WebRTC
115        protocol specifications, lists references to other specifications that
116        don't need further elaboration in the WebRTC context, and gives
117        pointers to other documents that form part of the WebRTC suite.</t>
118        <t>By reading this document and the documents it refers to, it should
119        be possible to have all information needed to implement a WebRTC
120        compatible implementation.</t>
121      </section>
122      <section numbered="true" toc="default">
123        <name>Relationship between API and protocol</name>
124        <t>The total WebRTC effort consists of two major parts, each
125        consisting of multiple documents:</t>
126        <ul spacing="normal">
127          <li>A protocol specification, done in the IETF</li>
128          <li>A Javascript API specification, defined in a series of W3C
129            documents <xref target="W3C.WD-webrtc-20120209" format="default"/><xref target="W3C.WD-mediacapture-streams-20120628" format="default"/></li>
130        </ul>
131        <t>Together, these two specifications aim to provide an
132        environment where Javascript embedded in any page, when suitably
133        authorized by its user, is able to set up communication using audio,
134        video and auxiliary data, as long as the browser supports this
135        specification. The browser environment does not constrain the types of
136        application in which this functionality can be used.</t>
137        <t>The protocol specification does not assume that all implementations
138        implement this API; it is not intended to be necessary for
139        interoperation to know whether the entity one is communicating with is
140        a browser or another device implementing this specification.</t>
141        <t>The goal of cooperation between the protocol specification and the
142        API specification is that for all options and features of the protocol
143        specification, it should be clear which API calls to make to exercise
144        that option or feature; similarly, for any sequence of API calls, it
145        should be clear which protocol options and features will be invoked.
146        Both subject to constraints of the implementation, of course.</t>
147        <t>The following terms are used across the documents specifying the
148        WebRTC suite, in the specific meanings given here. Not all terms are
149        used in this document. Other terms are used in their commonly used
150        meaning.</t>
151
152<dl newline="false" spacing="normal">
153          <dt>Agent:</dt>
154          <dd>Undefined term. See "SDP Agent" and "ICE
155            Agent".</dd>
156          <dt>Application Programming Interface (API):</dt>
157          <dd>A
158            specification of a set of calls and events, usually tied to a
159            programming language or an abstract formal specification such as
160            WebIDL, with its defined semantics.</dd>
161          <dt>Browser:</dt>
162          <dd>Used synonymously with "Interactive User
163            Agent" as defined in the HTML specification <xref target="W3C.WD-html5-20110525" format="default"/>. See also "WebRTC User
164            Agent".</dd>
165          <dt>Data Channel:</dt>
166          <dd>An abstraction that allows data to be
167            sent between WebRTC endpoints in the form of messages. Two
168            endpoints can have multiple data channels between them.</dd>
169          <dt>ICE Agent:</dt>
170          <dd>An implementation of the Interactive
171            Connectivity Establishment (ICE) <xref target="RFC5245" format="default"/> protocol. An ICE Agent may also
172            be an SDP Agent, but there exist ICE Agents that do not use SDP
173            (for instance those that use Jingle <xref target="XEP-0166" format="default">
174            </xref>).</dd>
175          <dt>Interactive:</dt>
176          <dd>Communication between multiple parties,
177            where the expectation is that an action from one party can cause a
178            reaction by another party, and the reaction can be observed by the
179            first party, with the total time required for the
180            action/reaction/observation is on the order of no more than
181            hundreds of milliseconds.</dd>
182          <dt>Media:</dt>
183          <dd>Audio and video content. Not to be confused
184            with "transmission media" such as wires.</dd>
185          <dt>Media Path:</dt>
186          <dd>The path that media data follows from
187            one WebRTC endpoint to another.</dd>
188          <dt>Protocol:</dt>
189          <dd>A specification of a set of data units,
190            their representation, and rules for their transmission, with their
191            defined semantics. A protocol is usually thought of as going
192            between systems.</dd>
193          <dt>Real-time Media:</dt>
194          <dd>Media where generation of content
195            and display of content are intended to occur closely together in
196            time (on the order of no more than hundreds of milliseconds).
197            Real-time media can be used to support interactive
198            communication.</dd>
199          <dt>SDP Agent:</dt>
200          <dd>The protocol implementation involved in
201            the Session Description Protocol (SDP) offer/answer exchange, as
202            defined in <xref target="RFC3264" sectionFormat="comma" section="3"/></dd>
203          <dt>Signaling:</dt>
204          <dd>Communication that happens in order to
205            establish, manage and control media paths and data paths.</dd>
206          <dt>Signaling Path:</dt>
207          <dd>The communication channels used
208            between entities participating in signaling to transfer signaling.
209            There may be more entities in the signaling path than in the media
210            path.</dd>
211          <dt>WebRTC Browser:</dt>
212          <dd>(also called a WebRTC User Agent
213            or WebRTC UA) Something that conforms to both the protocol
214            specification and the Javascript API cited above.</dd>
215          <dt>WebRTC non-Browser:</dt>
216          <dd> Something that conforms to
217            the protocol specification, but does not claim to implement the
218            Javascript API.  This can also be called a "WebRTC device" or
219            "WebRTC native application".</dd>
220          <dt>WebRTC Endpoint:</dt>
221          <dd> Either a WebRTC browser or a
222            WebRTC non-browser. It conforms to the protocol specification.</dd>
223          <dt>WebRTC-compatible Endpoint:</dt>
224          <dd> An endpoint that is able
225            to successfully communicate with a WebRTC endpoint, but may fail to
226            meet some requirements of a WebRTC endpoint. This may limit where
227            in the network such an endpoint can be attached, or may limit the
228            security guarantees that it offers to others. It is not
229            constrained by this specification; when it is mentioned at all, it
230            is to note the implications on WebRTC-compatible endpoints of the
231            requirements placed on WebRTC endpoints.</dd>
232          <dt>WebRTC Gateway:</dt>
233          <dd> A WebRTC-compatible endpoint that
234            mediates media traffic to non-WebRTC entities.</dd>
235        </dl>
236
237
238        <t>All WebRTC browsers are WebRTC endpoints, so any requirement
239        on a WebRTC endpoint also applies to a WebRTC browser.</t>
240        <t>A WebRTC non-browser may be capable of hosting applications in a
241        similar way to the way in which a browser can host Javascript
242        applications, typically by offering APIs in other languages. For
243        instance it may be implemented as a library that offers a C++ API
244        intended to be loaded into applications. In this case, similar
245        security considerations as for Javascript may be needed; however,
246        since such APIs are not defined or referenced here, this document
247        cannot give any specific rules for those interfaces.</t>
248        <t>WebRTC gateways are described in a separate document, <xref target="I-D.ietf-rtcweb-gateways" format="default"/>.</t>
249      </section>
250      <section numbered="true" toc="default">
251        <name>On interoperability and innovation</name>
252        <t>The "Mission statement of the IETF" <xref target="RFC3935" format="default"/> states
253        that "The benefit of a standard to the Internet is in interoperability
254        - that multiple products implementing a standard are able to work
255        together in order to deliver valuable functions to the Internet's
256        users."</t>
257        <t>Communication on the Internet frequently occurs in two phases:</t>
258        <ul spacing="normal">
259          <li>Two parties communicate, through some mechanism, what
260            functionality they both are able to support</li>
261          <li>They use that shared communicative functionality to
262            communicate, or, failing to find anything in common, give up on
263            communication.</li>
264        </ul>
265        <t>There are often many choices that can be made for
266        communicative functionality; the history of the Internet is rife with
267        the proposal, standardization, implementation, and success or failure
268        of many types of options, in all sorts of protocols.</t>
269        <t>The goal of having a mandatory to implement function set is to
270        prevent negotiation failure, not to preempt or prevent
271        negotiation.</t>
272        <t>The presence of a mandatory to implement function set serves as a
273        strong changer of the marketplace of deployment - in that it gives a
274        guarantee that, as long as you conform to a specification, and the
275        other party is willing to accept communication at the base level of
276        that specification, you can communicate successfully.</t>
277        <t>The alternative, that is having no mandatory to implement, does
278        not mean that you cannot communicate, it merely means that in order to
279        be part of the communications partnership, you have to implement the
280        standard "and then some".  The "and then some" is usually called a
281        profile of some sort; in the version most antithetical to the Internet
282        ethos, that "and then some" consists of having to use a specific
283        vendor's product only.</t>
284      </section>
285      <section numbered="true" toc="default">
286        <name>Terminology</name>
287        <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>",
288    "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
289    NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>",
290    "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
291    "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are
292    to be interpreted as described in BCP&nbsp;14 <xref target="RFC2119"/>
293    <xref target="RFC8174"/> when, and only when, they appear in all capitals,
294    as shown here. 
295</t>
296      </section>
297    </section>
298    <section numbered="true" toc="default">
299      <name>Architecture and Functionality groups</name>
300      <t>For browser-based applications, the model for real-time support does
301     not assume that the browser will contain all the functions needed for
302     an application such as a telephone or a video conference.  The vision is
303     that the browser will have the functions needed for a Web application,
304     working in conjunction with its backend servers, to implement these
305     functions.</t>
306      <t>This means that two vital interfaces need specification: The
307      protocols that browsers use to talk to each other, without any
308      intervening servers, and the APIs that are offered for a Javascript
309      application to take advantage of the browser's functionality.</t>
310      <figure anchor="fig-browser-model">
311        <name>Browser Model</name>
312        <artwork name="" type="" align="left" alt=""><![CDATA[
313
314                                                                          
315                     +------------------------+  On-the-wire              
316                     |                        |  Protocols                
317                     |      Servers           |--------->                 
318                     |                        |                           
319                     |                        |                           
320                     +------------------------+                           
321                                 ^                                        
322                                 |                                        
323                                 |                                        
324                                 | HTTPS/                                  
325                                 | WebSockets                             
326                                 |                                              
327                                 |                                        
328                   +----------------------------+                         
329                   |    Javascript/HTML/CSS     |                         
330                   +----------------------------+                         
331                Other  ^                 ^ RTC                             
332                APIs   |                 | APIs                            
333                   +---|-----------------|------+                         
334                   |   |                 |      |                         
335                   |                 +---------+|                         
336                   |                 | Browser ||  On-the-wire            
337                   | Browser         | RTC     ||  Protocols              
338                   |                 | Function|----------->              
339                   |                 |         ||                         
340                   |                 |         ||                         
341                   |                 +---------+|                         
342                   +---------------------|------+                         
343                                         |                                
344                                         V                                
345                                    Native OS Services
346]]></artwork>
347      </figure>
348      <t>Note that HTTPS and WebSockets are also offered to the Javascript
349      application through browser APIs.</t>
350      <t>As for all protocol and API specifications, there is no restriction
351      that the protocols can only be used to talk to another browser; since
352      they are fully specified, any endpoint that implements the protocols
353      faithfully should be able to interoperate with the application running
354      in the browser.</t>
355      <t>A commonly imagined model of deployment is the one depicted
356      below.  In <xref target="fig-webtrapezoid"/> below, JS is Javascript.</t>
357      <figure anchor="fig-webtrapezoid">
358        <name>Browser RTC Trapezoid</name>
359        <artwork name="" type="" align="left" alt=""><![CDATA[                                                                  
360                                                                          
361             +-----------+             +-----------+                      
362             |   Web     |             |   Web     |                      
363             |           |  Signaling  |           |                      
364             |           |-------------|           |                      
365             |  Server   |   path      |  Server   |                      
366             |           |             |           |                      
367             +-----------+             +-----------+                      
368                  /                           \                           
369                 /                             \ Application-defined      
370                /                               \ over       
371               /                                 \ HTTPS/WebSockets                    
372              /  Application-defined over         \                       
373             /   HTTPS/WebSockets                  \                      
374            /                                       \                     
375      +-----------+                           +-----------+               
376      |JS/HTML/CSS|                           |JS/HTML/CSS|               
377      +-----------+                           +-----------+               
378      +-----------+                           +-----------+               
379      |           |                           |           |               
380      |           |                           |           |               
381      |  Browser  | ------------------------- |  Browser  |               
382      |           |          Media path       |           |               
383      |           |                           |           |               
384      +-----------+                           +-----------+]]></artwork>
385      </figure>
386      <t>On this drawing, the critical part to note is that the media path
387      ("low path") goes directly between the browsers, so it has to be
388      conformant to the specifications of the WebRTC protocol suite; the
389      signaling path ("high path") goes via servers that can modify, translate
390      or manipulate the signals as needed.</t>
391      <t>If the two Web servers are operated by different entities, the
392      inter-server signaling mechanism needs to be agreed upon, either by
393      standardization or by other means of agreement. Existing protocols
394      (e.g. SIP <xref target="RFC3261" format="default"/> or XMPP <xref target="RFC6120" format="default"/>)
395      could be used between servers, while either a standards-based or
396      proprietary protocol could be used between the browser and the web
397      server.</t>
398      <t>For example, if both operators' servers implement SIP, SIP could be
399      used for communication between servers, along with either a standardized
400      signaling mechanism (e.g. SIP over WebSockets) or a proprietary
401      signaling mechanism used between the application running in the browser
402      and the web server. Similarly, if both operators' servers implement
403      Extensible Messaging and Presence Protocol (XMPP), XMPP could be used
404      for communication between XMPP servers, with either a standardized
405      signaling mechanism (e.g. XMPP over WebSockets or BOSH <xref target="XEP-0124" format="default"/> or a proprietary signaling mechanism used between the
406      application running in the browser and the web server.</t>
407      <t>The choice of protocols for client-server and inter-server
408      signalling, and definition of the translation between them, is outside
409      the scope of the WebRTC protocol suite described in the document.</t>
410      <t>The functionality groups that are needed in the browser can be
411      specified, more or less from the bottom up, as:</t>
412      <ul spacing="normal">
413        <li>Data transport: such as TCP, UDP and the means to securely set up
414          connections between entities, as well as the functions for deciding
415          when to send data: congestion management, bandwidth estimation and
416          so on.</li>
417        <li>Data framing: RTP, SCTP, DTLS, and other data formats that serve
418          as containers, and their functions for data confidentiality and
419          integrity.</li>
420        <li>Data formats: Codec specifications, format specifications and
421          functionality specifications for the data passed between systems.
422          Audio and video codecs, as well as formats for data and document
423          sharing, belong in this category. In order to make use of data
424          formats, a way to describe them, a session description, is
425          needed.</li>
426        <li>Connection management: Setting up connections, agreeing on data
427          formats, changing data formats during the duration of a call; SDP,
428          SIP, and Jingle/XMPP belong in this category.</li>
429        <li>Presentation and control: What needs to happen in order to ensure
430          that interactions behave in a non-surprising manner. This can
431          include floor control, screen layout, voice activated image
432          switching and other such functions - where part of the system
433          require the cooperation between parties. XCON and Cisco/Tandberg's
434          TIP were some attempts at specifying this kind of functionality;
435          many applications have been built without standardized interfaces to
436          these functions.</li>
437        <li>Local system support functions: These are things that need not be
438          specified uniformly, because each participant may choose to do these
439          in a way of the participant's choosing, without affecting the bits
440          on the wire in a way that others have to be cognizant of. Examples
441          in this category include echo cancellation (some forms of it), local
442          authentication and authorization mechanisms, OS access control and
443          the ability to do local recording of conversations.</li>
444      </ul>
445      <t>Within each functionality group, it is important to preserve
446      both freedom to innovate and the ability for global communication.
447      Freedom to innovate is helped by doing the specification in terms of
448      interfaces, not implementation; any implementation able to communicate
449      according to the interfaces is a valid implementation. Ability to
450      communicate globally is helped both by having core specifications be
451      unencumbered by IPR issues and by having the formats and protocols be
452      fully enough specified to allow for independent implementation.</t>
453      <t>One can think of the three first groups as forming a "media transport
454      infrastructure", and of the three last groups as forming a "media
455      service". In many contexts, it makes sense to use a common specification
456      for the media transport infrastructure, which can be embedded in
457      browsers and accessed using standard interfaces, and "let a thousand
458      flowers bloom" in the "media service" layer; to achieve interoperable
459      services, however, at least the first five of the six groups need to be
460      specified.</t>
461    </section>
462    <section anchor="ch-transport" numbered="true" toc="default">
463      <name>Data transport</name>
464      <t>Data transport refers to the sending and receiving of data over the
465      network interfaces, the choice of network-layer addresses at each end of
466      the communication, and the interaction with any intermediate entities
467      that handle the data, but do not modify it (such as TURN relays).</t>
468      <t>It includes necessary functions for congestion control,
469      retransmission, and in-order delivery.</t>
470      <t>WebRTC endpoints <bcp14>MUST</bcp14> implement the transport protocols described in
471      <xref target="RFCZZZZ" format="default"/>.</t>
472    </section>
473    <section numbered="true" toc="default">
474      <name>Data framing and securing</name>
475      <t>The format for media transport is RTP <xref target="RFC3550" format="default"/>.
476      Implementation of SRTP <xref target="RFC3711" format="default"/> is <bcp14>REQUIRED</bcp14> for all
477      implementations.</t>
478      <t>The detailed considerations for usage of functions from RTP and SRTP
479      are given in <xref target="RFCAAAA" format="default"/>. The security
480      considerations for the WebRTC use case are in <xref target="RFCYYYY" format="default"/>, and the resulting security
481      functions are described in <xref target="RFCDDDD" format="default"/>.</t>
482      <t>Considerations for the transfer of data that is not in RTP format is
483      described in <xref target="RFCBBBB" format="default"/>, and a
484      supporting protocol for establishing individual data channels is
485      described in <xref target="RFCCCCC" format="default"/>. WebRTC
486      endpoints <bcp14>MUST</bcp14> implement these two specifications.</t>
487      <t>WebRTC endpoints <bcp14>MUST</bcp14> implement <xref target="RFCAAAA" format="default"/>, <xref target="RFCYYYY" format="default"/>, <xref target="RFCDDDD" format="default"/>, and the requirements they
488      include.</t>
489    </section>
490    <section anchor="ch-data" numbered="true" toc="default">
491      <name>Data formats</name>
492      <t>The intent of this specification is to allow each communications
493      event to use the data formats that are best suited for that particular
494      instance, where a format is supported by both sides of the connection.
495      However, a minimum standard is greatly helpful in order to ensure that
496      communication can be achieved. This document specifies a minimum
497      baseline that will be supported by all implementations of this
498      specification, and leaves further codecs to be included at the will of
499      the implementor.</t>
500      <t>WebRTC endpoints that support audio and/or video <bcp14>MUST</bcp14> implement the
501      codecs and profiles required in <xref target="RFC7874" format="default"/> and <xref target="RFC7742" format="default"/>.</t>
502    </section>
503    <section numbered="true" toc="default">
504      <name>Connection management</name>
505      <t>The methods, mechanisms and requirements for setting up, negotiating
506      and tearing down connections is a large subject, and one where it is
507      desirable to have both interoperability and freedom to innovate.</t>
508      <t>The following principles apply:</t>
509      <ol spacing="normal" type="1">
510        <li>The WebRTC media negotiations will be capable of representing the
511          same SDP offer/answer semantics <xref target="RFC3264" format="default"/> that are
512          used in SIP, in such a way that it is possible to build a
513          signaling gateway between SIP and the WebRTC media negotiation.</li>
514        <li>It will be possible to gateway between legacy SIP devices that
515          support ICE and appropriate RTP / SDP mechanisms, codecs and
516          security mechanisms without using a media gateway. A signaling
517          gateway to convert between the signaling on the web side to the SIP
518          signaling may be needed.</li>
519        <li>When an SDP for a new codec is specified, no other standardization
520          should be required for it to be possible to use that in the web
521          browsers. Adding new codecs which might have new SDP parameters should
522          not change the APIs between the browser and Javascript application. As
523          soon as the browsers support the new codecs, old applications
524          written before the codecs were specified should automatically be
525          able to use the new codecs where appropriate with no changes to the
526          JS applications.</li>
527      </ol>
528      <t>The particular choices made for WebRTC, and their implications
529      for the API offered by a browser implementing WebRTC, are described in
530      <xref target="RFCEEEE" format="default"/>.</t>
531      <t>WebRTC browsers <bcp14>MUST</bcp14> implement <xref target="RFCEEEE" format="default"/>.</t>
532      <t>WebRTC endpoints <bcp14>MUST</bcp14> implement the functions described in that
533      document that relate to the network layer (e.g. Bundle <xref target="I-D.ietf-mmusic-sdp-bundle-negotiation" format="default"/>, RTCP-mux <xref target="RFC5761" format="default"/> and Trickle ICE <xref target="I-D.ietf-ice-trickle" format="default"/>), but do not need to support the API
534      functionality described there.</t>
535    </section>
536    <section numbered="true" toc="default">
537      <name>Presentation and control</name>
538      <t>The most important part of control is the user's control over the
539      browser's interaction with input/output devices and communications
540      channels. It is important that the user have some way of figuring out
541      where his audio, video or texting is being sent, for what purported
542      reason, and what guarantees are made by the parties that form part of
543      this control channel. This is largely a local function between the
544      browser, the underlying operating system and the user interface; this is
545      specified in the peer connection API <xref target="W3C.WD-webrtc-20120209" format="default"/>, and the media capture API <xref target="W3C.WD-mediacapture-streams-20120628" format="default"/>.</t>
546      <t>WebRTC browsers <bcp14>MUST</bcp14> implement these two specifications.</t>
547    </section>
548    <section numbered="true" toc="default">
549      <name>Local system support functions</name>
550      <t>These are characterized by the fact that the quality of these
551      functions strongly influence the user experience, but the exact
552      algorithm does not need coordination. In some cases (for instance echo
553      cancellation, as described below), the overall system definition may
554      need to specify that the overall system needs to have some
555      characteristics for which these facilities are useful, without requiring
556      them to be implemented a certain way.</t>
557      <t>Local functions include echo cancellation, volume control, camera
558      management including focus, zoom, pan/tilt controls (if available), and
559      more.</t>
560      <t>One would want to see certain parts of the system conform to certain
561      properties, for instance:</t>
562      <ul spacing="normal">
563        <li>Echo cancellation should be good enough to achieve the
564          suppression of acoustical feedback loops below a perceptually
565          noticeable level.</li>
566        <li>Privacy concerns <bcp14>MUST</bcp14> be satisfied; for instance, if remote
567          control of camera is offered, the APIs should be available to let
568          the local participant figure out who's controlling the camera, and
569          possibly decide to revoke the permission for camera usage.</li>
570        <li>Automatic gain control, if present, should normalize a speaking
571          voice into a reasonable dB range.</li>
572      </ul>
573      <t>The requirements on WebRTC systems with regard to audio
574      processing are found in <xref target="RFC7874" format="default"/> and includes more
575      guidance about echo cancellation and AGC; the proposed API for control
576      of local devices are found in <xref target="W3C.WD-mediacapture-streams-20120628" format="default"/>.</t>
577      <t>WebRTC endpoints <bcp14>MUST</bcp14> implement the processing functions in <xref target="RFC7874" format="default"/>. (Together with the requirement in <xref target="ch-data" format="default"/>, this means that WebRTC endpoints <bcp14>MUST</bcp14> implement the
578      whole document.)</t>
579    </section>
580    <section anchor="IANA" numbered="true" toc="default">
581      <name>IANA Considerations</name>
582      <t>This document makes no request of IANA.</t>
583      <t>Note to RFC Editor: this section may be removed on publication as an
584      RFC.</t>
585    </section>
586    <section anchor="Security" numbered="true" toc="default">
587      <name>Security Considerations</name>
588      <t>Security of the web-enabled real time communications comes in several
589      pieces:</t>
590      <ul spacing="normal">
591        <li>Security of the components: The browsers, and other servers
592          involved. The most target-rich environment here is probably the
593          browser; the aim here should be that the introduction of these
594          components introduces no additional vulnerability.</li>
595        <li>Security of the communication channels: It should be easy for a
596          participant to reassure himself of the security of his communication
597          - by verifying the crypto parameters of the links he himself
598          participates in, and to get reassurances from the other parties to
599          the communication that they promise that appropriate measures are
600          taken.</li>
601        <li>Security of the partners' identity: verifying that the
602          participants are who they say they are (when positive identification
603          is appropriate), or that their identity cannot be uncovered (when
604          anonymity is a goal of the application).</li>
605      </ul>
606      <t>The security analysis, and the requirements derived from that
607      analysis, is contained in <xref target="RFCYYYY" format="default"/>.</t>
608      <t>It is also important to read the security sections of <xref target="W3C.WD-mediacapture-streams-20120628" format="default"/> and <xref target="W3C.WD-webrtc-20120209" format="default"/>.</t>
609    </section>
610    <section anchor="Acknowledgements" numbered="true" toc="default">
611      <name>Acknowledgements</name>
612      <t>The number of people who have taken part in the discussions
613      surrounding this draft are too numerous to list, or even to identify.
614      The ones below have made special, identifiable contributions; this does
615      not mean that others' contributions are less important.</t>
616      <t>Thanks to Cary Bran, Cullen Jennings, Colin Perkins, Magnus
617      Westerlund and Joerg Ott, who offered technical contributions on various
618      versions of the draft.</t>
619      <t>Thanks to Jonathan Rosenberg, Matthew Kaufman and others at Skype for
620      the ASCII drawings in <xref target="Intro"/>.</t>
621      <t>Thanks to Alissa Cooper, Bjoern Hoehrmann, Colin Perkins,
622      Colton Shields, Eric Rescorla, Heath Matlock, Henry Sinnreich,
623      Justin Uberti, Keith Drage, Magnus Westerlund, Olle E. Johansson,
624      Sean Turner and Simon Leinen for document review.</t>
625    </section>
626  </middle>
627  <back>
628    <references>
629      <name>References</name>
630      <references>
631        <name>Normative References</name>
632
633<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
634<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3264.xml"/>
635<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3550.xml"/>
636<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3711.xml"/>
637<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5245.xml"/>
638<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7742.xml"/>
639<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7874.xml"/>
640
641   
642    
643        <reference anchor="RFCYYYY" target="https://www.rfc-editor.org/info/rfcYYYY">
644          <front>
645            <title>Security Considerations for WebRTC</title>
646            <seriesInfo name="RFC" value="YYYY"/>
647            <seriesInfo name="DOI" value="10.17487/RFCYYYY"/>
648            <author initials="E" surname="Rescorla" fullname="Eric Rescorla">
649              <organization/>
650            </author>
651            <date month="August" year="2019"/>
652            <abstract>
653              <t>WebRTC is a protocol suite for use with real-time applications that can be deployed in browsers - "real time communication on the Web". This document defines the WebRTC threat model and analyzes the security threats of WebRTC in that model.</t>
654            </abstract>
655          </front>
656        </reference>
657
658        <reference anchor="RFCZZZZ" target="https://www.rfc-editor.org/info/rfcZZZZ">
659          <front>
660            <title>Transports for WebRTC</title>
661            <seriesInfo name="RFC" value="ZZZZ"/>
662            <seriesInfo name="DOI" value="10.17487/RFCZZZZ"/>
663            <author initials="H" surname="Alvestrand" fullname="Harald Alvestrand">
664              <organization/>
665            </author>
666            <date month="August" year="2019"/>
667            <abstract>
668              <t>This document describes the data transport protocols used by WebRTC, including the protocols used for interaction with intermediate boxes such as firewalls, relays and NAT boxes.</t>
669            </abstract>
670          </front>
671        </reference>
672
673        <reference anchor="RFCAAAA" target="https://www.rfc-editor.org/info/rfcAAAA">
674          <front>
675            <title>Web Real-Time Communication (WebRTC): Media Transport and Use of RTP</title>
676            <seriesInfo name="RFC" value="AAAA"/>
677            <seriesInfo name="DOI" value="10.17487/RFCAAAA"/>
678            <author initials="C" surname="Perkins" fullname="Colin Perkins">
679              <organization/>
680            </author>
681            <author initials="M" surname="Westerlund" fullname="Magnus Westerlund">
682              <organization/>
683            </author>
684            <author initials="J" surname="Ott" fullname="Joerg Ott">
685              <organization/>
686            </author>
687            <date month="August" year="2019"/>
688            <abstract>
689              <t>The Web Real-Time Communication (WebRTC) framework provides support for direct interactive rich communication using audio, video, text, collaboration, games, etc. between two peers' web-browsers.  This memo describes the media transport aspects of the WebRTC framework. It specifies how the Real-time Transport Protocol (RTP) is used in the WebRTC context, and gives requirements for which RTP features, profiles, and extensions need to be supported.</t>
690            </abstract>
691          </front>
692        </reference>
693
694        <reference anchor="RFCBBBB" target="https://www.rfc-editor.org/info/rfcBBBB">
695          <front>
696            <title>WebRTC Data Channels</title>
697            <seriesInfo name="RFC" value="BBBB"/>
698            <seriesInfo name="DOI" value="10.17487/RFCBBBB"/>
699            <author initials="R" surname="Jesup" fullname="Randell Jesup">
700              <organization/>
701            </author>
702            <author initials="S" surname="Loreto" fullname="Salvatore Loreto">
703              <organization/>
704            </author>
705            <author initials="M" surname="Tuexen" fullname="Michael Tuexen">
706              <organization/>
707            </author>
708            <date month="August" year="2019"/>
709            <abstract>
710              <t>The WebRTC framework specifies protocol support for direct interactive rich communication using audio, video, and data between two peers' web-browsers.  This document specifies the non-media data transport aspects of the WebRTC framework.  It provides an architectural overview of how the Stream Control Transmission Protocol (SCTP) is used in the WebRTC context as a generic transport service allowing WEB-browsers to exchange generic data from peer to peer.</t>
711            </abstract>
712          </front>
713        </reference>
714
715        <reference anchor="RFCCCCC" target="https://www.rfc-editor.org/info/rfcCCCC">
716          <front>
717            <title>WebRTC Data Channel Establishment Protocol</title>
718             <seriesInfo name="RFC" value="CCCC"/>
719            <seriesInfo name="DOI" value="10.17487/RFCCCCC"/>
720            <author initials="R" surname="Jesup" fullname="Randell Jesup">
721              <organization/>
722            </author>
723            <author initials="S" surname="Loreto" fullname="Salvatore Loreto">
724              <organization/>
725            </author>
726            <author initials="M" surname="Tuexen" fullname="Michael Tuexen">
727              <organization/>
728            </author>
729            <date month="August" year="2019"/>
730            <abstract>
731              <t>The WebRTC framework specifies protocol support for direct interactive rich communication using audio, video, and data between two peers' web-browsers.  This document specifies a simple protocol for establishing symmetric Data Channels between the peers.  It uses a two way handshake and allows sending of user data without waiting for the handshake to complete.</t>
732            </abstract>
733          </front>
734        </reference>
735
736        <reference anchor="RFCDDDD" target="https://www.rfc-editor.org/info/rfcDDDD">
737          <front>
738            <title>WebRTC Security Architecture</title>
739            <seriesInfo name="RFC" value="DDDD"/>
740            <seriesInfo name="DOI" value="10.17487/RFCDDDD"/>
741            <author initials="E" surname="Rescorla" fullname="Eric Rescorla">
742              <organization/>
743            </author>
744            <date month="August" year="2019"/>
745            <abstract>
746              <t>This document defines the security architecture for WebRTC, a protocol suite intended for use with real-time applications that can be deployed in browsers - "real time communication on the Web".</t>
747            </abstract>
748          </front>
749        </reference>
750
751        <reference anchor="RFCEEEE" target="https://www.rfc-editor.org/info/rfcEEEE">
752          <front>
753            <title>JavaScript Session Establishment Protocol</title>
754            <seriesInfo name="RFC" value="EEEE"/>
755            <seriesInfo name="DOI" value="10.17487/RFCEEEE"/>
756            <author initials="J" surname="Uberti" fullname="Justin Uberti">
757              <organization/>
758            </author>
759            <author initials="C" surname="Jennings" fullname="Cullen Jennings">
760              <organization/>
761            </author>
762            <author initials="E" surname="Rescorla" fullname="Eric Rescorla">
763              <organization/>
764            </author>
765            <date month="August" year="2019"/>
766            <abstract>
767              <t>This document describes the mechanisms for allowing a JavaScript application to control the signaling plane of a multimedia session via the interface specified in the W3C RTCPeerConnection API, and discusses how this relates to existing signaling protocols.</t>
768            </abstract>
769          </front>
770        </reference>
771
772
773
774        <reference anchor="W3C.WD-webrtc-20120209" target="http://www.w3.org/TR/2012/WD-webrtc-20120209" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml4/reference.W3C.WD-webrtc-20120209.xml">
775          <front>
776            <title>WebRTC 1.0: Real-time Communication Between Browsers</title>
777            <seriesInfo name="World Wide Web Consortium WD" value="WD-webrtc-20120209"/>
778            <author initials="A." surname="Bergkvist" fullname="Adam Bergkvist">
779              <organization/>
780            </author>
781            <author initials="D." surname="Burnett" fullname="Daniel C. Burnett">
782              <organization/>
783            </author>
784            <author initials="C." surname="Jennings" fullname="Cullen Jennings">
785              <organization/>
786            </author>
787            <author initials="A." surname="Narayanan" fullname="Anant Narayanan">
788              <organization/>
789            </author>
790            <date month="February" year="2012"/>
791          </front>
792        </reference>
793        <reference anchor="W3C.WD-mediacapture-streams-20120628" target="http://www.w3.org/TR/2012/WD-mediacapture-streams-20120628" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml4/reference.W3C.WD-mediacapture-streams-20120628.xml">
794          <front>
795            <title>Media Capture and Streams</title>
796            <seriesInfo name="World Wide Web Consortium WD" value="WD-mediacapture-streams-20120628"/>
797            <author initials="D." surname="Burnett" fullname="Daniel C. Burnett">
798              <organization/>
799            </author>
800            <author initials="A." surname="Narayanan" fullname="Anant Narayanan">
801              <organization/>
802            </author>
803            <date month="June" year="2012"/>
804          </front>
805        </reference>
806      </references>
807      <references>
808        <name>Informative References</name>
809
810<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3261.xml"/>
811<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3361.xml"/>
812<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3935.xml"/>
813<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5761.xml"/>
814<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6120.xml"/>
815<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7478.xml"/>
816<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8155.xml"/>
817<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
818
819        
820        <reference anchor="W3C.WD-html5-20110525" target="http://www.w3.org/TR/2011/WD-html5-20110525" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml4/reference.W3C.WD-html5-20110525.xml">
821          <front>
822            <title>HTML5</title>
823            <seriesInfo name="World Wide Web Consortium LastCall," value="WD-html5-20110525"/>
824            <author initials="I." surname="Hickson" fullname="Ian Hickson">
825              <organization/>
826            </author>
827            <date month="May" year="2011"/>
828          </front>
829        </reference>
830        <reference anchor="I-D.ietf-ice-trickle">
831          <front>
832            <title>Trickle ICE: Incremental Provisioning of Candidates for the Interactive Connectivity Establishment (ICE) Protocol</title>
833            <seriesInfo name="Work in Progress," value="draft-ietf-ice-trickle-21"/>
834            <author initials="E" surname="Ivov" fullname="Emil Ivov">
835              <organization/>
836            </author>
837            <author initials="E" surname="Rescorla" fullname="Eric Rescorla">
838              <organization/>
839            </author>
840            <author initials="J" surname="Uberti" fullname="Justin Uberti">
841              <organization/>
842            </author>
843            <author initials="P" surname="Saint-Andre" fullname="Peter Saint-Andre">
844              <organization/>
845            </author>
846            <date month="April" year="2018"/>
847            <abstract>
848              <t>This document describes "Trickle ICE", an extension to the Interactive Connectivity Establishment (ICE) protocol that enables ICE agents to begin connectivity checks while they are still gathering candidates, by incrementally exchanging candidates over time instead of all at once.  This method can considerably accelerate the process of establishing a communication session.</t>
849            </abstract>
850          </front>
851        </reference>
852
853        <reference anchor="I-D.ietf-mmusic-sdp-bundle-negotiation">
854          <front>
855            <title>Negotiating Media Multiplexing Using the Session Description Protocol (SDP)</title>
856            <seriesInfo name="Work in Progress," value="draft-ietf-mmusic-sdp-bundle-negotiation-54"/>
857            <author initials="C" surname="Holmberg" fullname="Christer Holmberg">
858              <organization/>
859            </author>
860            <author initials="H" surname="Alvestrand" fullname="Harald Alvestrand">
861              <organization/>
862            </author>
863            <author initials="C" surname="Jennings" fullname="Cullen Jennings">
864              <organization/>
865            </author>
866            <date month="December" year="2018"/>
867            <abstract>
868              <t>This specification defines a new Session Description Protocol (SDP) Grouping Framework extension, 'BUNDLE'.  The extension can be used with the SDP Offer/Answer mechanism to negotiate the usage of a single transport (5-tuple) for sending and receiving media described by multiple SDP media descriptions ("m=" sections).  Such transport is referred to as a BUNDLE transport, and the media is referred to as bundled media.  The "m=" sections that use the BUNDLE transport form a BUNDLE group.  This specification updates RFC 3264, to also allow assigning a zero port value to a "m=" section in cases where the media described by the "m=" section is not disabled or rejected.  This specification updates RFC 5888, to also allow an SDP 'group' attribute to contain an identification-tag that identifies a "m=" section with the port set to zero.  This specification defines a new RTP Control Protocol (RTCP) source description (SDES) item and a new RTP header extension that can be used to correlate bundled RTP/RTCP packets with their appropriate "m=" section.  This specification updates RFC 7941, by adding an exception, for the MID RTP header extension, to the requirement regarding protection of an SDES RTP header extension carrying an SDES item for the MID RTP header extension.</t>
869            </abstract>
870          </front>
871        </reference>
872
873        <reference anchor="I-D.ietf-rtcweb-gateways">
874          <front>
875            <title>WebRTC Gateways</title>
876            <seriesInfo name="Work in Progress," value="draft-ietf-rtcweb-gateways-02"/>
877            <author initials="H" surname="Alvestrand" fullname="Harald T. Alvestrand">
878              <organization/>
879            </author>
880            <author initials="U" surname="Rauschenbach" fullname="Uwe Rauschenbach">
881              <organization/>
882            </author>
883            <date month="January" year="2016"/>
884            <abstract>
885              <t>This document describes interoperability considerations for a class of WebRTC-compatible endpoints called "WebRTC gateways", which interconnect between WebRTC endpoints and devices that are not WebRTC endpoints.</t>
886            </abstract>
887          </front>
888        </reference>
889
890        <reference anchor="I-D.ietf-tsvwg-rtcweb-qos" >
891          <front>
892            <title>DSCP Packet Markings for WebRTC QoS</title>
893            <seriesInfo name="Work in Progress," value="draft-ietf-tsvwg-rtcweb-qos-18"/>
894            <author initials="P" surname="Jones" fullname="Paul Jones">
895              <organization/>
896            </author>
897            <author initials="S" surname="Dhesikan" fullname="Subha Dhesikan">
898              <organization/>
899            </author>
900            <author initials="C" surname="Jennings" fullname="Cullen Jennings">
901              <organization/>
902            </author>
903            <author initials="D" surname="Druta" fullname="Dan Druta">
904              <organization/>
905            </author>
906            <date month="August" year="2016"/>
907            <abstract>
908              <t>Many networks, such as service provider and enterprise networks, can provide different forwarding treatments for individual packets based on Differentiated Services Code Point (DSCP) values on a per-hop basis.  This document provides the recommended DSCP values for web browsers to use for various classes of WebRTC traffic.</t>
909            </abstract>
910          </front>
911        </reference>
912
913        <reference anchor="XEP-0166" target="http://xmpp.org/extensions/xep-0166.html">
914          <front>
915            <title>Jingle</title>
916            <seriesInfo name="XSF XEP" value="0166"/>
917            <author fullname="Scott Ludwig" initials="S." surname="Ludwig">
918              <organization/>
919              <address>
920                <email>scottlu@google.com</email>
921              </address>
922            </author>
923            <author fullname="Joe Beda" initials="J." surname="Beda">
924              <organization/>
925              <address>
926                <email>jbeda@google.com</email>
927              </address>
928            </author>
929            <author fullname="Peter Saint-Andre" initials="P." surname="Saint-Andre">
930              <organization/>
931              <address>
932                <email>stpeter@jabber.org</email>
933              </address>
934            </author>
935            <author fullname="Robert McQueen" initials="R." surname="McQueen">
936              <organization/>
937              <address>
938                <email>robert.mcqueen@collabora.co.uk</email>
939              </address>
940            </author>
941            <author fullname="Sean Egan" initials="S." surname="Egan">
942              <organization/>
943              <address>
944                <email>seanegan@google.com</email>
945              </address>
946            </author>
947            <author fullname="Joe Hildebrand" initials="J." surname="Hildebrand">
948              <organization/>
949              <address>
950                <email>jhildebr@cisco.com</email>
951              </address>
952            </author>
953            <date month="June" year="2007"/>
954          </front>
955        </reference>
956
957        <reference anchor="XEP-0124" target="http://xmpp.org/extensions/xep-0124.html">
958          <front>
959            <title>BOSH</title>
960            <seriesInfo name="XSF XEP" value="0124"/>
961            <author fullname="Ian Paterson" initials="I." surname="Paterson">
962              <organization/>
963              <address>
964                <email>ian.paterson@clientside.co.uk</email>
965              </address>
966            </author>
967            <author fullname="Dave Smith" initials="D." surname="Smith">
968              <organization/>
969              <address>
970                <email>dizzyd@jabber.org</email>
971              </address>
972            </author>
973            <author fullname="Peter Saint-Andre" initials="P." surname="Saint-Andre">
974              <organization/>
975              <address>
976                <email>stpeter@jabber.org</email>
977              </address>
978            </author>
979            <author fullname="Jack Moffitt" initials="J." surname="Moffitt">
980              <organization/>
981              <address>
982                <email>jack@chesspark.com</email>
983              </address>
984            </author>
985            <author fullname="Lance Stout" initials="L." surname="Stout">
986              <organization/>
987              <address>
988                <email>lance@andyet.com</email>
989              </address>
990            </author>
991            <author fullname="Winifried Tilanus" initials="W." surname="Tilanus">
992              <organization/>
993              <address>
994                <email>winfried@tilanus.com</email>
995              </address>
996            </author>
997            <date month="November" year="2016"/>
998          </front>
999        </reference>
1000      </references>
1001    </references>
1002  </back>
1003</rfc>
1<reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml">
2<front>
3<title>Key words for use in RFCs to Indicate Requirement Levels</title>
4<author initials="S." surname="Bradner" fullname="S. Bradner"><organization/></author>
5<date year="1997" month="March"/>
6<abstract><t>In many standards track documents several words are used to signify the requirements in the specification.  These words are often capitalized. This document defines these words as they should be interpreted in IETF documents.  This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t></abstract>
7</front>
8<seriesInfo name="BCP" value="14"/>
9<seriesInfo name="RFC" value="2119"/>
10<seriesInfo name="DOI" value="10.17487/RFC2119"/>
11</reference>
1<reference anchor="RFC3264" target="https://www.rfc-editor.org/info/rfc3264" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3264.xml">
2<front>
3<title>An Offer/Answer Model with Session Description Protocol (SDP)</title>
4<author initials="J." surname="Rosenberg" fullname="J. Rosenberg"><organization/></author>
5<author initials="H." surname="Schulzrinne" fullname="H. Schulzrinne"><organization/></author>
6<date year="2002" month="June"/>
7<abstract><t>This document defines a mechanism by which two entities can make use of the Session Description Protocol (SDP) to arrive at a common view of a multimedia session between them.  In the model, one participant offers the other a description of the desired session from their perspective, and the other participant answers with the desired session from their perspective.  This offer/answer model is most useful in unicast sessions where information from both participants is needed for the complete view of the session.  The offer/answer model is used by protocols like the Session Initiation Protocol (SIP).  [STANDARDS-TRACK]</t></abstract>
8</front>
9<seriesInfo name="RFC" value="3264"/>
10<seriesInfo name="DOI" value="10.17487/RFC3264"/>
11</reference>
1<reference anchor="RFC3550" target="https://www.rfc-editor.org/info/rfc3550" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3550.xml">
2<front>
3<title>RTP: A Transport Protocol for Real-Time Applications</title>
4<author initials="H." surname="Schulzrinne" fullname="H. Schulzrinne"><organization/></author>
5<author initials="S." surname="Casner" fullname="S. Casner"><organization/></author>
6<author initials="R." surname="Frederick" fullname="R. Frederick"><organization/></author>
7<author initials="V." surname="Jacobson" fullname="V. Jacobson"><organization/></author>
8<date year="2003" month="July"/>
9<abstract><t>This memorandum describes RTP, the real-time transport protocol.  RTP provides end-to-end network transport functions suitable for applications transmitting real-time data, such as audio, video or simulation data, over multicast or unicast network services.  RTP does not address resource reservation and does not guarantee quality-of- service for real-time services.  The data transport is augmented by a control protocol (RTCP) to allow monitoring of the data delivery in a manner scalable to large multicast networks, and to provide minimal control and identification functionality.  RTP and RTCP are designed to be independent of the underlying transport and network layers.  The protocol supports the use of RTP-level translators and mixers. Most of the text in this memorandum is identical to RFC 1889 which it obsoletes.  There are no changes in the packet formats on the wire, only changes to the rules and algorithms governing how the protocol is used. The biggest change is an enhancement to the scalable timer algorithm for calculating when to send RTCP packets in order to minimize transmission in excess of the intended rate when many participants join a session simultaneously.  [STANDARDS-TRACK]</t></abstract>
10</front>
11<seriesInfo name="STD" value="64"/>
12<seriesInfo name="RFC" value="3550"/>
13<seriesInfo name="DOI" value="10.17487/RFC3550"/>
14</reference>
1<reference anchor="RFC3711" target="https://www.rfc-editor.org/info/rfc3711" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3711.xml">
2<front>
3<title>The Secure Real-time Transport Protocol (SRTP)</title>
4<author initials="M." surname="Baugher" fullname="M. Baugher"><organization/></author>
5<author initials="D." surname="McGrew" fullname="D. McGrew"><organization/></author>
6<author initials="M." surname="Naslund" fullname="M. Naslund"><organization/></author>
7<author initials="E." surname="Carrara" fullname="E. Carrara"><organization/></author>
8<author initials="K." surname="Norrman" fullname="K. Norrman"><organization/></author>
9<date year="2004" month="March"/>
10<abstract><t>This document describes the Secure Real-time Transport Protocol (SRTP), a profile of the Real-time Transport Protocol (RTP), which can provide confidentiality, message authentication, and replay protection to the RTP traffic and to the control traffic for RTP, the Real-time Transport Control Protocol (RTCP).   [STANDARDS-TRACK]</t></abstract>
11</front>
12<seriesInfo name="RFC" value="3711"/>
13<seriesInfo name="DOI" value="10.17487/RFC3711"/>
14</reference>
1<?xml version='1.0' encoding='UTF-8'?>
2
3<reference  anchor='RFC5245' target='https://www.rfc-editor.org/info/rfc5245'>
4<front>
5<title>Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols</title>
6<author initials='J.' surname='Rosenberg' fullname='J. Rosenberg'><organization /></author>
7<date year='2010' month='April' />
8<abstract><t>This document describes a protocol for Network Address Translator (NAT) traversal for UDP-based multimedia sessions established with the offer/answer model.  This protocol is called Interactive Connectivity Establishment (ICE).  ICE makes use of the Session Traversal Utilities for NAT (STUN) protocol and its extension, Traversal Using Relay NAT (TURN).  ICE can be used by any protocol utilizing the offer/answer model, such as the Session Initiation Protocol (SIP).  [STANDARDS-TRACK]</t></abstract>
9</front>
10<seriesInfo name='RFC' value='5245'/>
11<seriesInfo name='DOI' value='10.17487/RFC5245'/>
12</reference>
1<?xml version='1.0' encoding='UTF-8'?>
2
3<reference  anchor='RFC7742' target='https://www.rfc-editor.org/info/rfc7742'>
4<front>
5<title>WebRTC Video Processing and Codec Requirements</title>
6<author initials='A.B.' surname='Roach' fullname='A.B. Roach'><organization /></author>
7<date year='2016' month='March' />
8<abstract><t>This specification provides the requirements and considerations for WebRTC applications to send and receive video across a network.  It specifies the video processing that is required as well as video codecs and their parameters.</t></abstract>
9</front>
10<seriesInfo name='RFC' value='7742'/>
11<seriesInfo name='DOI' value='10.17487/RFC7742'/>
12</reference>
1<?xml version='1.0' encoding='UTF-8'?>
2
3<reference  anchor='RFC7874' target='https://www.rfc-editor.org/info/rfc7874'>
4<front>
5<title>WebRTC Audio Codec and Processing Requirements</title>
6<author initials='JM.' surname='Valin' fullname='JM. Valin'><organization /></author>
7<author initials='C.' surname='Bran' fullname='C. Bran'><organization /></author>
8<date year='2016' month='May' />
9<abstract><t>This document outlines the audio codec and processing requirements for WebRTC endpoints.</t></abstract>
10</front>
11<seriesInfo name='RFC' value='7874'/>
12<seriesInfo name='DOI' value='10.17487/RFC7874'/>
13</reference>
1<?xml version='1.0' encoding='UTF-8'?>
2
3<reference anchor='W3C.WD-webrtc-20120209'
4           target='http://www.w3.org/TR/2012/WD-webrtc-20120209'>
5<front>
6<title>WebRTC 1.0: Real-time Communication Between Browsers</title>
7
8<author initials='A.' surname='Bergkvist' fullname='Adam Bergkvist'>
9    <organization />
10</author>
11
12<author initials='D.' surname='Burnett' fullname='Daniel C. Burnett'>
13    <organization />
14</author>
15
16<author initials='C.' surname='Jennings' fullname='Cullen Jennings'>
17    <organization />
18</author>
19
20<author initials='A.' surname='Narayanan' fullname='Anant Narayanan'>
21    <organization />
22</author>
23
24<date month='February' day='9' year='2012' />
25</front>
26
27<seriesInfo name='World Wide Web Consortium WD' value='WD-webrtc-20120209' />
28<format type='HTML' target='http://www.w3.org/TR/2012/WD-webrtc-20120209' />
29</reference>
1<?xml version='1.0' encoding='UTF-8'?>
2
3<reference anchor='W3C.WD-mediacapture-streams-20120628'
4           target='http://www.w3.org/TR/2012/WD-mediacapture-streams-20120628'>
5<front>
6<title>Media Capture and Streams</title>
7
8<author initials='D.' surname='Burnett' fullname='Daniel C. Burnett'>
9    <organization />
10</author>
11
12<author initials='A.' surname='Narayanan' fullname='Anant Narayanan'>
13    <organization />
14</author>
15
16<date month='June' day='28' year='2012' />
17</front>
18
19<seriesInfo name='World Wide Web Consortium WD' value='WD-mediacapture-streams-20120628' />
20<format type='HTML' target='http://www.w3.org/TR/2012/WD-mediacapture-streams-20120628' />
21</reference>
1<?xml version='1.0' encoding='UTF-8'?>
2
3<reference  anchor='RFC3261' target='https://www.rfc-editor.org/info/rfc3261'>
4<front>
5<title>SIP: Session Initiation Protocol</title>
6<author initials='J.' surname='Rosenberg' fullname='J. Rosenberg'><organization /></author>
7<author initials='H.' surname='Schulzrinne' fullname='H. Schulzrinne'><organization /></author>
8<author initials='G.' surname='Camarillo' fullname='G. Camarillo'><organization /></author>
9<author initials='A.' surname='Johnston' fullname='A. Johnston'><organization /></author>
10<author initials='J.' surname='Peterson' fullname='J. Peterson'><organization /></author>
11<author initials='R.' surname='Sparks' fullname='R. Sparks'><organization /></author>
12<author initials='M.' surname='Handley' fullname='M. Handley'><organization /></author>
13<author initials='E.' surname='Schooler' fullname='E. Schooler'><organization /></author>
14<date year='2002' month='June' />
15<abstract><t>This document describes Session Initiation Protocol (SIP), an application-layer control (signaling) protocol for creating, modifying, and terminating sessions with one or more participants.  These sessions include Internet telephone calls, multimedia distribution, and multimedia conferences.  [STANDARDS-TRACK]</t></abstract>
16</front>
17<seriesInfo name='RFC' value='3261'/>
18<seriesInfo name='DOI' value='10.17487/RFC3261'/>
19</reference>
1<?xml version='1.0' encoding='UTF-8'?>
2
3<reference  anchor='RFC3361' target='https://www.rfc-editor.org/info/rfc3361'>
4<front>
5<title>Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation Protocol (SIP) Servers</title>
6<author initials='H.' surname='Schulzrinne' fullname='H. Schulzrinne'><organization /></author>
7<date year='2002' month='August' />
8</front>
9<seriesInfo name='RFC' value='3361'/>
10<seriesInfo name='DOI' value='10.17487/RFC3361'/>
11</reference>
1<?xml version='1.0' encoding='UTF-8'?>
2
3<reference  anchor='RFC3935' target='https://www.rfc-editor.org/info/rfc3935'>
4<front>
5<title>A Mission Statement for the IETF</title>
6<author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'><organization /></author>
7<date year='2004' month='October' />
8<abstract><t>This memo gives a mission statement for the IETF, tries to define the terms used in the statement sufficiently to make the mission statement understandable and useful, argues why the IETF needs a mission statement, and tries to capture some of the debate that led to this point.  This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t></abstract>
9</front>
10<seriesInfo name='BCP' value='95'/>
11<seriesInfo name='RFC' value='3935'/>
12<seriesInfo name='DOI' value='10.17487/RFC3935'/>
13</reference>
1<?xml version='1.0' encoding='UTF-8'?>
2
3<reference  anchor='RFC5761' target='https://www.rfc-editor.org/info/rfc5761'>
4<front>
5<title>Multiplexing RTP Data and Control Packets on a Single Port</title>
6<author initials='C.' surname='Perkins' fullname='C. Perkins'><organization /></author>
7<author initials='M.' surname='Westerlund' fullname='M. Westerlund'><organization /></author>
8<date year='2010' month='April' />
9<abstract><t>This memo discusses issues that arise when multiplexing RTP data packets and RTP Control Protocol (RTCP) packets on a single UDP port. It updates RFC 3550 and RFC 3551 to describe when such multiplexing is and is not appropriate, and it explains how the Session Description Protocol (SDP) can be used to signal multiplexed sessions.  [STANDARDS-TRACK]</t></abstract>
10</front>
11<seriesInfo name='RFC' value='5761'/>
12<seriesInfo name='DOI' value='10.17487/RFC5761'/>
13</reference>
1<?xml version='1.0' encoding='UTF-8'?>
2
3<reference  anchor='RFC6120' target='https://www.rfc-editor.org/info/rfc6120'>
4<front>
5<title>Extensible Messaging and Presence Protocol (XMPP): Core</title>
6<author initials='P.' surname='Saint-Andre' fullname='P. Saint-Andre'><organization /></author>
7<date year='2011' month='March' />
8<abstract><t>The Extensible Messaging and Presence Protocol (XMPP) is an application profile of the Extensible Markup Language (XML) that enables the near-real-time exchange of structured yet extensible data between any two or more network entities.  This document defines XMPP's core protocol methods: setup and teardown of XML streams, channel encryption, authentication, error handling, and communication primitives for messaging, network availability (&quot;presence&quot;), and request-response interactions.  This document obsoletes RFC 3920.  [STANDARDS-TRACK]</t></abstract>
9</front>
10<seriesInfo name='RFC' value='6120'/>
11<seriesInfo name='DOI' value='10.17487/RFC6120'/>
12</reference>
1<?xml version='1.0' encoding='UTF-8'?>
2
3<reference  anchor='RFC7478' target='https://www.rfc-editor.org/info/rfc7478'>
4<front>
5<title>Web Real-Time Communication Use Cases and Requirements</title>
6<author initials='C.' surname='Holmberg' fullname='C. Holmberg'><organization /></author>
7<author initials='S.' surname='Hakansson' fullname='S. Hakansson'><organization /></author>
8<author initials='G.' surname='Eriksson' fullname='G. Eriksson'><organization /></author>
9<date year='2015' month='March' />
10<abstract><t>This document describes web-based real-time communication use cases. Requirements on the browser functionality are derived from the use cases.</t><t>This document was developed in an initial phase of the work with rather minor updates at later stages.  It has not really served as a tool in deciding features or scope for the WG's efforts so far.  It is being published to record the early conclusions of the WG.  It will not be used as a set of rigid guidelines that specifications and implementations will be held to in the future.</t></abstract>
11</front>
12<seriesInfo name='RFC' value='7478'/>
13<seriesInfo name='DOI' value='10.17487/RFC7478'/>
14</reference>
1<?xml version='1.0' encoding='UTF-8'?>
2
3<reference  anchor='RFC8155' target='https://www.rfc-editor.org/info/rfc8155'>
4<front>
5<title>Traversal Using Relays around NAT (TURN) Server Auto Discovery</title>
6<author initials='P.' surname='Patil' fullname='P. Patil'><organization /></author>
7<author initials='T.' surname='Reddy' fullname='T. Reddy'><organization /></author>
8<author initials='D.' surname='Wing' fullname='D. Wing'><organization /></author>
9<date year='2017' month='April' />
10<abstract><t>Current Traversal Using Relays around NAT (TURN) server discovery mechanisms are relatively static and limited to explicit configuration.  These are usually under the administrative control of the application or TURN service provider, and not the enterprise, ISP, or the network in which the client is located.  Enterprises and ISPs wishing to provide their own TURN servers need auto-discovery mechanisms that a TURN client could use with minimal or no configuration.  This document describes three such mechanisms for TURN server discovery.</t><t>This document updates RFC 5766 to relax the requirement for mutual authentication in certain cases.</t></abstract>
11</front>
12<seriesInfo name='RFC' value='8155'/>
13<seriesInfo name='DOI' value='10.17487/RFC8155'/>
14</reference>
1<reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml">
2<front>
3<title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
4<author initials="B." surname="Leiba" fullname="B. Leiba"><organization/></author>
5<date year="2017" month="May"/>
6<abstract><t>RFC 2119 specifies common key words that may be used in protocol  specifications.  This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the  defined special meanings.</t></abstract>
7</front>
8<seriesInfo name="BCP" value="14"/>
9<seriesInfo name="RFC" value="8174"/>
10<seriesInfo name="DOI" value="10.17487/RFC8174"/>
11</reference>
1<?xml version='1.0' encoding='UTF-8'?>
2
3<reference anchor='W3C.WD-html5-20110525'
4           target='http://www.w3.org/TR/2011/WD-html5-20110525'>
5<front>
6<title>HTML5</title>
7
8<author initials='I.' surname='Hickson' fullname='Ian Hickson'>
9    <organization />
10</author>
11
12<date month='May' day='25' year='2011' />
13</front>
14
15<seriesInfo name='World Wide Web Consortium LastCall' value='WD-html5-20110525' />
16<format type='HTML' target='http://www.w3.org/TR/2011/WD-html5-20110525' />
17</reference>
  • <?xml version="1.0" encoding="utf-8"?>
  • <!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
  • <rfc category="std" number="0000" ipr="trust200902" obsoletes="" updates="" consensus="true" submissionType="IETF" xml:lang="en" tocInclude="true" symRefs="true" sortRefs="true" version="3">
    • <-- xml2rfc v2v3 conversion 2.23.1 -->
    • <front>
      • <title abbrev="WebRTC Overview">
        • Overview: Real Time Protocols for Browser-based Applications
        • </title>
      • <seriesInfo name="RFC" value="0000"/>
      • <author fullname="Harald T. Alvestrand" initials="H. T." surname="Alvestrand">
        • <organization>
          • Google
          • </organization>
        • <address>
          • <postal>
            • <street>
              • Kungsbron 2
              • </street>
            • <city>
              • Stockholm
              • </city>
            • <region/>
            • <code>
              • 11122
              • </code>
            • <country>
              • Sweden
              • </country>
            • </postal>
          • <email>
            • harald@alvestrand.no
            • </email>
          • </address>
        • </author>
      • <date month="July" year="2019"/>
      • <abstract>
        • <t>
          • This document gives an overview and context of a protocol suite intended for use with real-time applications that can be deployed in browsers - "real time communication on the Web".
          • </t>
        • <t>
          • It intends to serve as a starting and coordination point to make sure all the parts that are needed to achieve this goal are findable, and that the parts that belong in the Internet protocol suite are fully specified and on the right publication track.
          • </t>
        • <t>
          • This document is an Applicability Statement - it does not itself specify any protocol, but specifies which other specifications WebRTC compliant implementations are supposed to follow.
          • </t>
        • <t>
          • This document is a work item of the RTCWEB working group.
          • </t>
        • </abstract>
      • </front>
    • <middle>
      • <section numbered="true" toc="default" anchor="Intro">
        • <name>
          • Introduction
          • </name>
        • <t>
          • The Internet was, from very early in its lifetime, considered a possible vehicle for the deployment of real-time, interactive applications - with the most easily imaginable being audio conversations (aka "Internet telephony") and video conferencing.
          • </t>
        • <t>
          • The first attempts to build this were dependent on special networks, special hardware and custom-built software, often at very high prices or at low quality, placing great demands on the infrastructure.
          • </t>
        • <t>
          • As the available bandwidth has increased, and as processors and other hardware has become ever faster, the barriers to participation have decreased, and it has become possible to deliver a satisfactory experience on commonly available computing hardware.
          • </t>
        • <t>
          • Still, there are a number of barriers to the ability to communicate universally - one of these is that there is, as of yet, no single set of communication protocols that all agree should be made available for communication; another is the sheer lack of universal identification systems (such as is served by telephone numbers or email addresses in other communications systems).
          • </t>
        • <t>
          • Development of The Universal Solution has, however, proved hard.
          • </t>
        • <t>
          • The last few years have also seen a new platform rise for deployment of services: The browser-embedded application, or "Web application". It turns out that as long as the browser platform has the necessary interfaces, it is possible to deliver almost any kind of service on it.
          • </t>
        • <t>
          • Traditionally, these interfaces have been delivered by plugins, which had to be downloaded and installed separately from the browser; in the development of HTML5, application developers see much promise in the possibility of making those interfaces available in a standardized way within the browser.
          • </t>
        • <t>
          • This memo describes a set of building blocks that can be made accessible and controllable through a Javascript JavaScript API in a browser, and which together form a sufficient set of functions to allow the use of interactive audio and video in applications that communicate directly between browsers across the Internet. The resulting protocol suite is intended to enable all the applications that are described as required scenarios in the use cases document <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFC7478" format="default"/>.
          • </t>
        • <t>
          • Other efforts, for instance the W3C Web Real-Time Communications, Web Applications Security, and Device and Sensor working groups, focus on making standardized APIs and interfaces available, within or alongside the HTML5 effort, for those functions. This memo concentrates on specifying the protocols and subprotocols sub-protocols that are needed to specify the interactions over the network.
          • </t>
        • <t>
          • Operators should note that deployment of WebRTC will result in a change in the nature of signaling for real time media on the network, and may result in a shift in the kinds of devices used to create and consume such media. In the case of signaling, WebRTC session setup will typically occur over TLS-secured web technologies using application-specific protocols. Operational techniques that involve inserting network elements to interpret SDP -- either through endpoint cooperation <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFC3361" format="default"/> or through the transparent insertion of SIP Application Level Gateways (ALGs) -- will not work with such signaling. In the case of networks using cooperative endpoints, the approaches defined in <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFC8155" format="default"/> may serve as a suitable replacement for <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFC3361" format="default"/>. The increase in browser-based communications may also lead to a shift away from dedicated real-time-communications hardware, such as SIP desk phones. This will diminish the efficacy of operational techniques that place dedicated real-time devices on their own network segment, address range, or VLAN for purposes such as applying traffic filtering and QoS. Applying the markings described in <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="I-D.ietf-tsvwg-rtcweb-qos" format="default"/> may be appropriate replacements for such techniques.
          • </t>
        • <t>
          • This memo uses the term "WebRTC" (note the case used) to refer to the overall effort consisting of both IETF and W3C efforts.
          • </t>
        • </section>
      • <section numbered="true" toc="default">
        • <name>
          • Principles and Terminology
          • </name>
        • <section numbered="true" toc="default">
          • <name>
            • Goals of this document
            • </name>
          • <t>
            • The goal of the WebRTC protocol specification is to specify a set of protocols that, if all are implemented, will allow an implementation to communicate with another implementation using audio, video and data sent along the most direct possible path between the participants.
            • </t>
          • <t>
            • This document is intended to serve as the roadmap to the WebRTC specifications. It defines terms used by other parts of the WebRTC protocol specifications, lists references to other specifications that don't need further elaboration in the WebRTC context, and gives pointers to other documents that form part of the WebRTC suite.
            • </t>
          • <t>
            • By reading this document and the documents it refers to, it should be possible to have all information needed to implement a WebRTC compatible implementation.
            • </t>
          • </section>
        • <section numbered="true" toc="default">
          • <name>
            • Relationship between API and protocol
            • </name>
          • <t>
            • The total WebRTC effort consists of two major parts, each consisting of multiple documents:
            • </t>
          • <ul spacing="normal">
            • <li>
              • A protocol specification, done in the IETF
              • </li>
            • <li>
              • A Javascript JavaScript API specification, defined in a series of W3C documents <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="W3C.WD-webrtc-20120209" format="default"/><xref xmlns:xi="http://www.w3.org/2001/XInclude" target="W3C.WD-mediacapture-streams-20120628" format="default"/>
              • </li>
            • </ul>
          • <t>
            • Together, these two specifications aim to provide an environment where Javascript JavaScript embedded in any page, when suitably authorized by its user, is able to set up communication using audio, video and auxiliary data, as long as the browser supports this specification. The browser environment does not constrain the types of application in which this functionality can be used.
            • </t>
          • <t>
            • The protocol specification does not assume that all implementations implement this API; it is not intended to be necessary for interoperation to know whether the entity one is communicating with is a browser or another device implementing this specification.
            • </t>
          • <t>
            • The goal of cooperation between the protocol specification and the API specification is that for all options and features of the protocol specification, it should be clear which API calls to make to exercise that option or feature; similarly, for any sequence of API calls, it should be clear which protocol options and features will be invoked. Both subject to constraints of the implementation, of course.
            • </t>
          • <t>
            • The following terms are used across the documents specifying the WebRTC suite, in the specific meanings given here. Not all terms are used in this document. Other terms are used in their commonly used meaning.
            • </t>
          • <dl newline="false" spacing="normal">
            • <dt>
              • Agent:
              • </dt>
            • <dd>
              • Undefined term. See "SDP Agent" and "ICE Agent".
              • </dd>
            • <dt>
              • Application Programming Interface (API):
              • </dt>
            • <dd>
              • A specification of a set of calls and events, usually tied to a programming language or an abstract formal specification such as WebIDL, with its defined semantics.
              • </dd>
            • <dt>
              • Browser:
              • </dt>
            • <dd>
              • Used synonymously with "Interactive User Agent" as defined in the HTML specification <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="W3C.WD-html5-20110525" format="default"/>. See also "WebRTC User Agent".
              • </dd>
            • <dt>
              • Data Channel:
              • </dt>
            • <dd>
              • An abstraction that allows data to be sent between WebRTC endpoints in the form of messages. Two endpoints can have multiple data channels between them.
              • </dd>
            • <dt>
              • ICE Agent:
              • </dt>
            • <dd>
              • An implementation of the Interactive Connectivity Establishment (ICE) <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFC5245" format="default"/> protocol. An ICE Agent may also be an SDP Agent, but there exist ICE Agents that do not use SDP (for instance those that use Jingle <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="XEP-0166" format="default"></xref>).
              • </dd>
            • <dt>
              • Interactive:
              • </dt>
            • <dd>
              • Communication between multiple parties, where the expectation is that an action from one party can cause a reaction by another party, and the reaction can be observed by the first party, with the total time required for the action/reaction/observation is on the order of no more than hundreds of milliseconds.
              • </dd>
            • <dt>
              • Media:
              • </dt>
            • <dd>
              • Audio and video content. Not to be confused with "transmission media" such as wires.
              • </dd>
            • <dt>
              • Media Path:
              • </dt>
            • <dd>
              • The path that media data follows from one WebRTC endpoint to another.
              • </dd>
            • <dt>
              • Protocol:
              • </dt>
            • <dd>
              • A specification of a set of data units, their representation, and rules for their transmission, with their defined semantics. A protocol is usually thought of as going between systems.
              • </dd>
            • <dt>
              • Real-time Media:
              • </dt>
            • <dd>
              • Media where generation of content and display of content are intended to occur closely together in time (on the order of no more than hundreds of milliseconds). Real-time media can be used to support interactive communication.
              • </dd>
            • <dt>
              • SDP Agent:
              • </dt>
            • <dd>
              • The protocol implementation involved in the Session Description Protocol (SDP) offer/answer exchange, as defined in <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFC3264" sectionFormat="comma" section="3"/>
              • </dd>
            • <dt>
              • Signaling:
              • </dt>
            • <dd>
              • Communication that happens in order to establish, manage and control media paths and data paths.
              • </dd>
            • <dt>
              • Signaling Path:
              • </dt>
            • <dd>
              • The communication channels used between entities participating in signaling to transfer signaling. There may be more entities in the signaling path than in the media path.
              • </dd>
            • <dt>
              • WebRTC Browser:
              • </dt>
            • <dd>
              • (also called a WebRTC User Agent or WebRTC UA) Something that conforms to both the protocol specification and the Javascript JavaScript API cited above.
              • </dd>
            • <dt>
              • WebRTC non-Browser:
              • </dt>
            • <dd>
              • Something that conforms to the protocol specification, but does not claim to implement the Javascript JavaScript API. This can also be called a "WebRTC device" or "WebRTC native application".
              • </dd>
            • <dt>
              • WebRTC Endpoint:
              • </dt>
            • <dd>
              • Either a WebRTC browser or a WebRTC non-browser. It conforms to the protocol specification.
              • </dd>
            • <dt>
              • WebRTC-compatible Endpoint:
              • </dt>
            • <dd>
              • An endpoint that is able to successfully communicate with a WebRTC endpoint, but may fail to meet some requirements of a WebRTC endpoint. This may limit where in the network such an endpoint can be attached, or may limit the security guarantees that it offers to others. It is not constrained by this specification; when it is mentioned at all, it is to note the implications on WebRTC-compatible endpoints of the requirements placed on WebRTC endpoints.
              • </dd>
            • <dt>
              • WebRTC Gateway:
              • </dt>
            • <dd>
              • A WebRTC-compatible endpoint that mediates media traffic to non-WebRTC entities.
              • </dd>
            • </dl>
          • <t>
            • All WebRTC browsers are WebRTC endpoints, so any requirement on a WebRTC endpoint also applies to a WebRTC browser.
            • </t>
          • <t>
            • A WebRTC non-browser may be capable of hosting applications in a similar way to the way in which a browser can host Javascript JavaScript applications, typically by offering APIs in other languages. For instance it may be implemented as a library that offers a C++ API intended to be loaded into applications. In this case, similar security considerations as for Javascript JavaScript may be needed; however, since such APIs are not defined or referenced here, this document cannot give any specific rules for those interfaces.
            • </t>
          • <t>
            • WebRTC gateways are described in a separate document, <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="I-D.ietf-rtcweb-gateways" format="default"/>.
            • </t>
          • </section>
        • <section numbered="true" toc="default">
          • <name>
            • On interoperability and innovation
            • </name>
          • <t>
            • The "Mission statement of the IETF" <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFC3935" format="default"/> states that "The benefit of a standard to the Internet is in interoperability - that multiple products implementing a standard are able to work together in order to deliver valuable functions to the Internet's users."
            • </t>
          • <t>
            • Communication on the Internet frequently occurs in two phases:
            • </t>
          • <ul spacing="normal">
            • <li>
              • Two parties communicate, through some mechanism, what functionality they both are able to support
              • </li>
            • <li>
              • They use that shared communicative functionality to communicate, or, failing to find anything in common, give up on communication.
              • </li>
            • </ul>
          • <t>
            • There are often many choices that can be made for communicative functionality; the history of the Internet is rife with the proposal, standardization, implementation, and success or failure of many types of options, in all sorts of protocols.
            • </t>
          • <t>
            • The goal of having a mandatory to implement function set is to prevent negotiation failure, not to preempt or prevent negotiation.
            • </t>
          • <t>
            • The presence of a mandatory to implement function set serves as a strong changer of the marketplace of deployment - in that it gives a guarantee that, as long as you conform to a specification, and the other party is willing to accept communication at the base level of that specification, you can communicate successfully.
            • </t>
          • <t>
            • The alternative, that is having no mandatory to implement, does not mean that you cannot communicate, it merely means that in order to be part of the communications partnership, you have to implement the standard "and then some". The "and then some" is usually called a profile of some sort; in the version most antithetical to the Internet ethos, that "and then some" consists of having to use a specific vendor's product only.
            • </t>
          • </section>
        • <section numbered="true" toc="default">
          • <name>
            • Terminology
            • </name>
          • <t>
            • The key words "<bcp14 xmlns:xi="http://www.w3.org/2001/XInclude">MUST</bcp14>", "<bcp14 xmlns:xi="http://www.w3.org/2001/XInclude">MUST NOT</bcp14>", "<bcp14 xmlns:xi="http://www.w3.org/2001/XInclude">REQUIRED</bcp14>", "<bcp14 xmlns:xi="http://www.w3.org/2001/XInclude">SHALL</bcp14>", "<bcp14 xmlns:xi="http://www.w3.org/2001/XInclude">SHALL NOT</bcp14>", "<bcp14 xmlns:xi="http://www.w3.org/2001/XInclude">SHOULD</bcp14>", "<bcp14 xmlns:xi="http://www.w3.org/2001/XInclude">SHOULD NOT</bcp14>", "<bcp14 xmlns:xi="http://www.w3.org/2001/XInclude">RECOMMENDED</bcp14>", "<bcp14 xmlns:xi="http://www.w3.org/2001/XInclude">NOT RECOMMENDED</bcp14>", "<bcp14 xmlns:xi="http://www.w3.org/2001/XInclude">MAY</bcp14>", and "<bcp14 xmlns:xi="http://www.w3.org/2001/XInclude">OPTIONAL</bcp14>" in this document are to be interpreted as described in BCP 14 <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFC2119"/> <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFC8174"/> when, and only when, they appear in all capitals, as shown here.
            • </t>
          • </section>
        • </section>
      • <section numbered="true" toc="default">
        • <name>
          • Architecture and Functionality groups
          • </name>
        • <t>
          • For browser-based applications, the model for real-time support does not assume that the browser will contain all the functions needed for an application such as a telephone or a video conference. The vision is that the browser will have the functions needed for a Web application, working in conjunction with its backend servers, to implement these functions.
          • </t>
        • <t>
          • This means that two vital interfaces need specification: The protocols that browsers use to talk to each other, without any intervening servers, and the APIs that are offered for a Javascript JavaScript application to take advantage of the browser's functionality.
          • </t>
        • <figure anchor="fig-browser-model">
          • <name>
            • Browser Model
            • </name>
          • <artwork name="" type="" align="left" alt="">


            •                                                                           
                                   +------------------------+  On-the-wire              
                                   |                        |  Protocols                
                                   |      Servers           |--------->                 
                                   |                        |                           
                                   |                        |                           
                                   +------------------------+                           
                                               ^                                        
                                               |                                        
                                               |                                        
                                               | HTTPS/                                  
                                               | WebSockets                             
                                               |                                              
                                               |                                        
                                 +----------------------------+                         
                                 |                  Javascript/HTML/CSS JavaScript/HTML/CSS      |                         
                                 +----------------------------+                         
                              Other  ^                 ^ RTC                             
                              APIs   |                 | APIs                            
                                 +---|-----------------|------+                         
                                 |   |                 |      |                         
                                 |                 +---------+|                         
                                 |                 | Browser ||  On-the-wire            
                                 | Browser         | RTC     ||  Protocols              
                                 |                 | Function|----------->              
                                 |                 |         ||                         
                                 |                 |         ||                         
                                 |                 +---------+|                         
                                 +---------------------|------+                         
                                                       |                                
                                                       V                                
                                                  Native OS Services
            • </artwork>
          • </figure>
        • <t>
          • Note that HTTPS and WebSockets are also offered to the Javascript JavaScript application through browser APIs.
          • </t>
        • <t>
          • As for all protocol and API specifications, there is no restriction that the protocols can only be used to talk to another browser; since they are fully specified, any endpoint that implements the protocols faithfully should be able to interoperate with the application running in the browser.
          • </t>
        • <t>
          • A commonly imagined model of deployment is the one depicted below. In <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="fig-webtrapezoid"/> below, JS is Javascript. JavaScript.
          • </t>
        • <figure anchor="fig-webtrapezoid">
          • <name>
            • Browser RTC Trapezoid
            • </name>
          • <artwork name="" type="" align="left" alt="">
            •                                                                   
                                                                                        
                           +-----------+             +-----------+                      
                           |   Web     |             |   Web     |                      
                           |           |  Signaling  |           |                      
                           |           |-------------|           |                      
                           |  Server   |   path      |  Server   |                      
                           |           |             |           |                      
                           +-----------+             +-----------+                      
                                /                           \                           
                               /                             \ Application-defined      
                              /                               \ over       
                             /                                 \ HTTPS/WebSockets                    
                            /  Application-defined over         \                       
                           /   HTTPS/WebSockets                  \                      
                          /                                       \                     
                    +-----------+                           +-----------+               
                    |JS/HTML/CSS|                           |JS/HTML/CSS|               
                    +-----------+                           +-----------+               
                    +-----------+                           +-----------+               
                    |           |                           |           |               
                    |           |                           |           |               
                    |  Browser  | ------------------------- |  Browser  |               
                    |           |          Media path       |           |               
                    |           |                           |           |               
                    +-----------+                           +-----------+
            • </artwork>
          • </figure>
        • <t>
          • On this drawing, the critical part to note is that the media path ("low path") goes directly between the browsers, so it has to be conformant to the specifications of the WebRTC protocol suite; the signaling path ("high path") goes via servers that can modify, translate or manipulate the signals as needed.
          • </t>
        • <t>
          • If the two Web servers are operated by different entities, the inter-server signaling mechanism needs to be agreed upon, either by standardization or by other means of agreement. Existing protocols (e.g. SIP <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFC3261" format="default"/> or XMPP <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFC6120" format="default"/>) could be used between servers, while either a standards-based or proprietary protocol could be used between the browser and the web server.
          • </t>
        • <t>
          • For example, if both operators' servers implement SIP, SIP could be used for communication between servers, along with either a standardized signaling mechanism (e.g. SIP over WebSockets) or a proprietary signaling mechanism used between the application running in the browser and the web server. Similarly, if both operators' servers implement Extensible Messaging and Presence Protocol (XMPP), XMPP could be used for communication between XMPP servers, with either a standardized signaling mechanism (e.g. XMPP over WebSockets or BOSH <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="XEP-0124" format="default"/> or a proprietary signaling mechanism used between the application running in the browser and the web server.
          • </t>
        • <t>
          • The choice of protocols for client-server and inter-server signalling, signaling, and definition of the translation between them, is outside the scope of the WebRTC protocol suite described in the document.
          • </t>
        • <t>
          • The functionality groups that are needed in the browser can be specified, more or less from the bottom up, as:
          • </t>
        • <ul spacing="normal">
          • <li>
            • Data transport: such as TCP, UDP and the means to securely set up connections between entities, as well as the functions for deciding when to send data: congestion management, bandwidth estimation and so on.
            • </li>
          • <li>
            • Data framing: RTP, SCTP, DTLS, and other data formats that serve as containers, and their functions for data confidentiality and integrity.
            • </li>
          • <li>
            • Data formats: Codec specifications, format specifications and functionality specifications for the data passed between systems. Audio and video codecs, as well as formats for data and document sharing, belong in this category. In order to make use of data formats, a way to describe them, a session description, is needed.
            • </li>
          • <li>
            • Connection management: Setting up connections, agreeing on data formats, changing data formats during the duration of a call; SDP, SIP, and Jingle/XMPP belong in this category.
            • </li>
          • <li>
            • Presentation and control: What needs to happen in order to ensure that interactions behave in a non-surprising manner. This can include floor control, screen layout, voice activated image switching and other such functions - where part of the system require the cooperation between parties. XCON and Cisco/Tandberg's TIP were some attempts at specifying this kind of functionality; many applications have been built without standardized interfaces to these functions.
            • </li>
          • <li>
            • Local system support functions: These are things that need not be specified uniformly, because each participant may choose to do these in a way of the participant's choosing, without affecting the bits on the wire in a way that others have to be cognizant of. Examples in this category include echo cancellation (some forms of it), local authentication and authorization mechanisms, OS access control and the ability to do local recording of conversations.
            • </li>
          • </ul>
        • <t>
          • Within each functionality group, it is important to preserve both freedom to innovate and the ability for global communication. Freedom to innovate is helped by doing the specification in terms of interfaces, not implementation; any implementation able to communicate according to the interfaces is a valid implementation. Ability to communicate globally is helped both by having core specifications be unencumbered by IPR issues and by having the formats and protocols be fully enough specified to allow for independent implementation.
          • </t>
        • <t>
          • One can think of the three first groups as forming a "media transport infrastructure", and of the three last groups as forming a "media service". In many contexts, it makes sense to use a common specification for the media transport infrastructure, which can be embedded in browsers and accessed using standard interfaces, and "let a thousand flowers bloom" in the "media service" layer; to achieve interoperable services, however, at least the first five of the six groups need to be specified.
          • </t>
        • </section>
      • <section anchor="ch-transport" numbered="true" toc="default">
        • <name>
          • Data transport
          • </name>
        • <t>
          • Data transport refers to the sending and receiving of data over the network interfaces, the choice of network-layer addresses at each end of the communication, and the interaction with any intermediate entities that handle the data, but do not modify it (such as TURN relays).
          • </t>
        • <t>
          • It includes necessary functions for congestion control, retransmission, and in-order delivery.
          • </t>
        • <t>
          • WebRTC endpoints <bcp14 xmlns:xi="http://www.w3.org/2001/XInclude">MUST</bcp14> implement the transport protocols described in <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFCZZZZ" format="default"/>.
          • </t>
        • </section>
      • <section numbered="true" toc="default">
        • <name>
          • Data framing and securing
          • </name>
        • <t>
          • The format for media transport is RTP <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFC3550" format="default"/>. Implementation of SRTP <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFC3711" format="default"/> is <bcp14 xmlns:xi="http://www.w3.org/2001/XInclude">REQUIRED</bcp14> for all implementations.
          • </t>
        • <t>
          • The detailed considerations for usage of functions from RTP and SRTP are given in <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFCAAAA" format="default"/>. The security considerations for the WebRTC use case are in <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFCYYYY" format="default"/>, and the resulting security functions are described in <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFCDDDD" format="default"/>.
          • </t>
        • <t>
          • Considerations for the transfer of data that is not in RTP format is described in <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFCBBBB" format="default"/>, and a supporting protocol for establishing individual data channels is described in <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFCCCCC" format="default"/>. WebRTC endpoints <bcp14 xmlns:xi="http://www.w3.org/2001/XInclude">MUST</bcp14> implement these two specifications.
          • </t>
        • <t>
          • WebRTC endpoints <bcp14 xmlns:xi="http://www.w3.org/2001/XInclude">MUST</bcp14> implement <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFCAAAA" format="default"/>, <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFCYYYY" format="default"/>, <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFCDDDD" format="default"/>, and the requirements they include.
          • </t>
        • </section>
      • <section anchor="ch-data" numbered="true" toc="default">
        • <name>
          • Data formats
          • </name>
        • <t>
          • The intent of this specification is to allow each communications event to use the data formats that are best suited for that particular instance, where a format is supported by both sides of the connection. However, a minimum standard is greatly helpful in order to ensure that communication can be achieved. This document specifies a minimum baseline that will be supported by all implementations of this specification, and leaves further codecs to be included at the will of the implementor.
          • </t>
        • <t>
          • WebRTC endpoints that support audio and/or video <bcp14 xmlns:xi="http://www.w3.org/2001/XInclude">MUST</bcp14> implement the codecs and profiles required in <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFC7874" format="default"/> and <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFC7742" format="default"/>.
          • </t>
        • </section>
      • <section numbered="true" toc="default">
        • <name>
          • Connection management
          • </name>
        • <t>
          • The methods, mechanisms and requirements for setting up, negotiating and tearing down connections is a large subject, and one where it is desirable to have both interoperability and freedom to innovate.
          • </t>
        • <t>
          • The following principles apply:
          • </t>
        • <ol spacing="normal" type="1">
          • <li>
            • The WebRTC media negotiations will be capable of representing the same SDP offer/answer semantics <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFC3264" format="default"/> that are used in SIP, in such a way that it is possible to build a signaling gateway between SIP and the WebRTC media negotiation.
            • </li>
          • <li>
            • It will be possible to gateway between legacy SIP devices that support ICE and appropriate RTP / SDP mechanisms, codecs and security mechanisms without using a media gateway. A signaling gateway to convert between the signaling on the web side to the SIP signaling may be needed.
            • </li>
          • <li>
            • When an SDP for a new codec is specified, no other standardization should be required for it to be possible to use that in the web browsers. Adding new codecs which might have new SDP parameters should not change the APIs between the browser and Javascript JavaScript application. As soon as the browsers support the new codecs, old applications written before the codecs were specified should automatically be able to use the new codecs where appropriate with no changes to the JS applications.
            • </li>
          • </ol>
        • <t>
          • The particular choices made for WebRTC, and their implications for the API offered by a browser implementing WebRTC, are described in <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFCEEEE" format="default"/>.
          • </t>
        • <t>
          • WebRTC browsers <bcp14 xmlns:xi="http://www.w3.org/2001/XInclude">MUST</bcp14> implement <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFCEEEE" format="default"/>.
          • </t>
        • <t>
          • WebRTC endpoints <bcp14 xmlns:xi="http://www.w3.org/2001/XInclude">MUST</bcp14> implement the functions described in that document that relate to the network layer (e.g. Bundle <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="I-D.ietf-mmusic-sdp-bundle-negotiation" format="default"/>, RTCP-mux <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFC5761" format="default"/> and Trickle ICE <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="I-D.ietf-ice-trickle" format="default"/>), but do not need to support the API functionality described there.
          • </t>
        • </section>
      • <section numbered="true" toc="default">
        • <name>
          • Presentation and control
          • </name>
        • <t>
          • The most important part of control is the user's control over the browser's interaction with input/output devices and communications channels. It is important that the user have some way of figuring out where his audio, video or texting is being sent, for what purported reason, and what guarantees are made by the parties that form part of this control channel. This is largely a local function between the browser, the underlying operating system and the user interface; this is specified in the peer connection API <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="W3C.WD-webrtc-20120209" format="default"/>, and the media capture API <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="W3C.WD-mediacapture-streams-20120628" format="default"/>.
          • </t>
        • <t>
          • WebRTC browsers <bcp14 xmlns:xi="http://www.w3.org/2001/XInclude">MUST</bcp14> implement these two specifications.
          • </t>
        • </section>
      • <section numbered="true" toc="default">
        • <name>
          • Local system support functions
          • </name>
        • <t>
          • These are characterized by the fact that the quality of these functions strongly influence the user experience, but the exact algorithm does not need coordination. In some cases (for instance echo cancellation, as described below), the overall system definition may need to specify that the overall system needs to have some characteristics for which these facilities are useful, without requiring them to be implemented a certain way.
          • </t>
        • <t>
          • Local functions include echo cancellation, volume control, camera management including focus, zoom, pan/tilt controls (if available), and more.
          • </t>
        • <t>
          • One would want to see certain parts of the system conform to certain properties, for instance:
          • </t>
        • <ul spacing="normal">
          • <li>
            • Echo cancellation should be good enough to achieve the suppression of acoustical feedback loops below a perceptually noticeable level.
            • </li>
          • <li>
            • Privacy concerns <bcp14 xmlns:xi="http://www.w3.org/2001/XInclude">MUST</bcp14> be satisfied; for instance, if remote control of camera is offered, the APIs should be available to let the local participant figure out who's controlling the camera, and possibly decide to revoke the permission for camera usage.
            • </li>
          • <li>
            • Automatic gain control, if present, should normalize a speaking voice into a reasonable dB range.
            • </li>
          • </ul>
        • <t>
          • The requirements on WebRTC systems with regard to audio processing are found in <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFC7874" format="default"/> and includes more guidance about echo cancellation and AGC; the proposed API for control of local devices are found in <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="W3C.WD-mediacapture-streams-20120628" format="default"/>.
          • </t>
        • <t>
          • WebRTC endpoints <bcp14 xmlns:xi="http://www.w3.org/2001/XInclude">MUST</bcp14> implement the processing functions in <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFC7874" format="default"/>. (Together with the requirement in <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="ch-data" format="default"/>, this means that WebRTC endpoints <bcp14 xmlns:xi="http://www.w3.org/2001/XInclude">MUST</bcp14> implement the whole document.)
          • </t>
        • </section>
      • <section anchor="IANA" numbered="true" toc="default">
        • <name>
          • IANA Considerations
          • </name>
        • <t>
          • This document makes no request of IANA.
          • </t>
        • <t>
          • Note to RFC Editor: this section may be removed on publication as an RFC.
          • </t>
        • </section>
      • <section anchor="Security" numbered="true" toc="default">
        • <name>
          • Security Considerations
          • </name>
        • <t>
          • Security of the web-enabled real time communications comes in several pieces:
          • </t>
        • <ul spacing="normal">
          • <li>
            • Security of the components: The browsers, and other servers involved. The most target-rich environment here is probably the browser; the aim here should be that the introduction of these components introduces no additional vulnerability.
            • </li>
          • <li>
            • Security of the communication channels: It should be easy for a participant to reassure himself of the security of his communication - by verifying the crypto parameters of the links he himself participates in, and to get reassurances from the other parties to the communication that they promise that appropriate measures are taken.
            • </li>
          • <li>
            • Security of the partners' identity: verifying that the participants are who they say they are (when positive identification is appropriate), or that their identity cannot be uncovered (when anonymity is a goal of the application).
            • </li>
          • </ul>
        • <t>
          • The security analysis, and the requirements derived from that analysis, is contained in <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="RFCYYYY" format="default"/>.
          • </t>
        • <t>
          • It is also important to read the security sections of <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="W3C.WD-mediacapture-streams-20120628" format="default"/> and <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="W3C.WD-webrtc-20120209" format="default"/>.
          • </t>
        • </section>
      • <section anchor="Acknowledgements" numbered="true" toc="default">
        • <name>
          • Acknowledgements
          • </name>
        • <t>
          • The number of people who have taken part in the discussions surrounding this draft are too numerous to list, or even to identify. The ones below have made special, identifiable contributions; this does not mean that others' contributions are less important.
          • </t>
        • <t>
          • Thanks to Cary Bran, Cullen Jennings, Colin Perkins, Magnus Westerlund and Joerg Ott, who offered technical contributions on various versions of the draft.
          • </t>
        • <t>
          • Thanks to Jonathan Rosenberg, Matthew Kaufman and others at Skype for the ASCII drawings in <xref xmlns:xi="http://www.w3.org/2001/XInclude" target="Intro"/>.
          • </t>
        • <t>
          • Thanks to Alissa Cooper, Bjoern Hoehrmann, Colin Perkins, Colton Shields, Eric Rescorla, Heath Matlock, Henry Sinnreich, Justin Uberti, Keith Drage, Magnus Westerlund, Olle E. Johansson, Sean Turner and Simon Leinen for document review.
          • </t>
        • </section>
      • </middle>
    • <back>
      • <references>
        • <name>
          • References
          • </name>
        • <references>
          • <name>
            • Normative References
            • </name>
          • <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml">
            • <front>
              • <title>
                • Key words for use in RFCs to Indicate Requirement Levels
                • </title>
              • <author initials="S." surname="Bradner" fullname="S. Bradner">
                • <organization/>
                • </author>
              • <date year="1997" month="March"/>
              • <abstract>
                • <t>
                  • In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
                  • </t>
                • </abstract>
              • </front>
            • <seriesInfo name="BCP" value="14"/>
            • <seriesInfo name="RFC" value="2119"/>
            • <seriesInfo name="DOI" value="10.17487/RFC2119"/>
            • </reference>
          • <reference anchor="RFC3264" target="https://www.rfc-editor.org/info/rfc3264" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3264.xml">
            • <front>
              • <title>
                • An Offer/Answer Model with Session Description Protocol (SDP)
                • </title>
              • <author initials="J." surname="Rosenberg" fullname="J. Rosenberg">
                • <organization/>
                • </author>
              • <author initials="H." surname="Schulzrinne" fullname="H. Schulzrinne">
                • <organization/>
                • </author>
              • <date year="2002" month="June"/>
              • <abstract>
                • <t>
                  • This document defines a mechanism by which two entities can make use of the Session Description Protocol (SDP) to arrive at a common view of a multimedia session between them. In the model, one participant offers the other a description of the desired session from their perspective, and the other participant answers with the desired session from their perspective. This offer/answer model is most useful in unicast sessions where information from both participants is needed for the complete view of the session. The offer/answer model is used by protocols like the Session Initiation Protocol (SIP). [STANDARDS-TRACK]
                  • </t>
                • </abstract>
              • </front>
            • <seriesInfo name="RFC" value="3264"/>
            • <seriesInfo name="DOI" value="10.17487/RFC3264"/>
            • </reference>
          • <reference anchor="RFC3550" target="https://www.rfc-editor.org/info/rfc3550" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3550.xml">
            • <front>
              • <title>
                • RTP: A Transport Protocol for Real-Time Applications
                • </title>
              • <author initials="H." surname="Schulzrinne" fullname="H. Schulzrinne">
                • <organization/>
                • </author>
              • <author initials="S." surname="Casner" fullname="S. Casner">
                • <organization/>
                • </author>
              • <author initials="R." surname="Frederick" fullname="R. Frederick">
                • <organization/>
                • </author>
              • <author initials="V." surname="Jacobson" fullname="V. Jacobson">
                • <organization/>
                • </author>
              • <date year="2003" month="July"/>
              • <abstract>
                • <t>
                  • This memorandum describes RTP, the real-time transport protocol. RTP provides end-to-end network transport functions suitable for applications transmitting real-time data, such as audio, video or simulation data, over multicast or unicast network services. RTP does not address resource reservation and does not guarantee quality-of- service for real-time services. The data transport is augmented by a control protocol (RTCP) to allow monitoring of the data delivery in a manner scalable to large multicast networks, and to provide minimal control and identification functionality. RTP and RTCP are designed to be independent of the underlying transport and network layers. The protocol supports the use of RTP-level translators and mixers. Most of the text in this memorandum is identical to RFC 1889 which it obsoletes. There are no changes in the packet formats on the wire, only changes to the rules and algorithms governing how the protocol is used. The biggest change is an enhancement to the scalable timer algorithm for calculating when to send RTCP packets in order to minimize transmission in excess of the intended rate when many participants join a session simultaneously. [STANDARDS-TRACK]
                  • </t>
                • </abstract>
              • </front>
            • <seriesInfo name="STD" value="64"/>
            • <seriesInfo name="RFC" value="3550"/>
            • <seriesInfo name="DOI" value="10.17487/RFC3550"/>
            • </reference>
          • <reference anchor="RFC3711" target="https://www.rfc-editor.org/info/rfc3711" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3711.xml">
            • <front>
              • <title>
                • The Secure Real-time Transport Protocol (SRTP)
                • </title>
              • <author initials="M." surname="Baugher" fullname="M. Baugher">
                • <organization/>
                • </author>
              • <author initials="D." surname="McGrew" fullname="D. McGrew">
                • <organization/>
                • </author>
              • <author initials="M." surname="Naslund" fullname="M. Naslund">
                • <organization/>
                • </author>
              • <author initials="E." surname="Carrara" fullname="E. Carrara">
                • <organization/>
                • </author>
              • <author initials="K." surname="Norrman" fullname="K. Norrman">
                • <organization/>
                • </author>
              • <date year="2004" month="March"/>
              • <abstract>
                • <t>
                  • This document describes the Secure Real-time Transport Protocol (SRTP), a profile of the Real-time Transport Protocol (RTP), which can provide confidentiality, message authentication, and replay protection to the RTP traffic and to the control traffic for RTP, the Real-time Transport Control Protocol (RTCP). [STANDARDS-TRACK]
                  • </t>
                • </abstract>
              • </front>
            • <seriesInfo name="RFC" value="3711"/>
            • <seriesInfo name="DOI" value="10.17487/RFC3711"/>
            • </reference>
          • <reference anchor="RFC5245" target="https://www.rfc-editor.org/info/rfc5245" xml:base="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5245.xml" "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5245.xml" >
            • <front>
              • <title>
                • Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols
                • </title>
              • <author initials="J." surname="Rosenberg" fullname="J. Rosenberg">
                • <organization/>
                • </author>
              • <date year="2010" month="April"/>
              • <abstract>
                • <t>
                  • This document describes a protocol for Network Address Translator (NAT) traversal for UDP-based multimedia sessions established with the offer/answer model. This protocol is called Interactive Connectivity Establishment (ICE). ICE makes use of the Session Traversal Utilities for NAT (STUN) protocol and its extension, Traversal Using Relay NAT (TURN). ICE can be used by any protocol utilizing the offer/answer model, such as the Session Initiation Protocol (SIP). [STANDARDS-TRACK]
                  • </t>
                • </abstract>
              • </front>
            • <seriesInfo name="RFC" value="5245"/>
            • <seriesInfo name="DOI" value="10.17487/RFC5245"/>
            • </reference>
          • <reference anchor="RFC7742" target="https://www.rfc-editor.org/info/rfc7742" xml:base="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7742.xml" "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.7742.xml" >
            • <front>
              • <title>
                • WebRTC Video Processing and Codec Requirements
                • </title>
              • <author initials="A.B." surname="Roach" fullname="A.B. Roach">
                • <organization/>
                • </author>
              • <date year="2016" month="March"/>
              • <abstract>
                • <t>
                  • This specification provides the requirements and considerations for WebRTC applications to send and receive video across a network. It specifies the video processing that is required as well as video codecs and their parameters.
                  • </t>
                • </abstract>
              • </front>
            • <seriesInfo name="RFC" value="7742"/>
            • <seriesInfo name="DOI" value="10.17487/RFC7742"/>
            • </reference>
          • <reference anchor="RFC7874" target="https://www.rfc-editor.org/info/rfc7874" xml:base="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7874.xml" "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.7874.xml" >
            • <front>
              • <title>
                • WebRTC Audio Codec and Processing Requirements
                • </title>
              • <author initials="JM." surname="Valin" fullname="JM. Valin">
                • <organization/>
                • </author>
              • <author initials="C." surname="Bran" fullname="C. Bran">
                • <organization/>
                • </author>
              • <date year="2016" month="May"/>
              • <abstract>
                • <t>
                  • This document outlines the audio codec and processing requirements for WebRTC endpoints.
                  • </t>
                • </abstract>
              • </front>
            • <seriesInfo name="RFC" value="7874"/>
            • <seriesInfo name="DOI" value="10.17487/RFC7874"/>
            • </reference>
          • <reference anchor="RFCYYYY" target="https://www.rfc-editor.org/info/rfcYYYY">
            • <front>
              • <title>
                • Security Considerations for WebRTC
                • </title>
              • <seriesInfo name="RFC" value="YYYY"/>
              • <seriesInfo name="DOI" value="10.17487/RFCYYYY"/>
              • <author initials="E" surname="Rescorla" fullname="Eric Rescorla">
                • <organization/>
                • </author>
              • <date month="August" year="2019"/>
              • <abstract>
                • <t>
                  • WebRTC is a protocol suite for use with real-time applications that can be deployed in browsers - "real time communication on the Web". This document defines the WebRTC threat model and analyzes the security threats of WebRTC in that model.
                  • </t>
                • </abstract>
              • </front>
            • </reference>
          • <reference anchor="RFCZZZZ" target="https://www.rfc-editor.org/info/rfcZZZZ">
            • <front>
              • <title>
                • Transports for WebRTC
                • </title>
              • <seriesInfo name="RFC" value="ZZZZ"/>
              • <seriesInfo name="DOI" value="10.17487/RFCZZZZ"/>
              • <author initials="H" surname="Alvestrand" fullname="Harald Alvestrand">
                • <organization/>
                • </author>
              • <date month="August" year="2019"/>
              • <abstract>
                • <t>
                  • This document describes the data transport protocols used by WebRTC, including the protocols used for interaction with intermediate boxes such as firewalls, relays and NAT boxes.
                  • </t>
                • </abstract>
              • </front>
            • </reference>
          • <reference anchor="RFCAAAA" target="https://www.rfc-editor.org/info/rfcAAAA">
            • <front>
              • <title>
                • Web Real-Time Communication (WebRTC): Media Transport and Use of RTP
                • </title>
              • <seriesInfo name="RFC" value="AAAA"/>
              • <seriesInfo name="DOI" value="10.17487/RFCAAAA"/>
              • <author initials="C" surname="Perkins" fullname="Colin Perkins">
                • <organization/>
                • </author>
              • <author initials="M" surname="Westerlund" fullname="Magnus Westerlund">
                • <organization/>
                • </author>
              • <author initials="J" surname="Ott" fullname="Joerg Ott">
                • <organization/>
                • </author>
              • <date month="August" year="2019"/>
              • <abstract>
                • <t>
                  • The Web Real-Time Communication (WebRTC) framework provides support for direct interactive rich communication using audio, video, text, collaboration, games, etc. between two peers' web-browsers. This memo describes the media transport aspects of the WebRTC framework. It specifies how the Real-time Transport Protocol (RTP) is used in the WebRTC context, and gives requirements for which RTP features, profiles, and extensions need to be supported.
                  • </t>
                • </abstract>
              • </front>
            • </reference>
          • <reference anchor="RFCBBBB" target="https://www.rfc-editor.org/info/rfcBBBB">
            • <front>
              • <title>
                • WebRTC Data Channels
                • </title>
              • <seriesInfo name="RFC" value="BBBB"/>
              • <seriesInfo name="DOI" value="10.17487/RFCBBBB"/>
              • <author initials="R" surname="Jesup" fullname="Randell Jesup">
                • <organization/>
                • </author>
              • <author initials="S" surname="Loreto" fullname="Salvatore Loreto">
                • <organization/>
                • </author>
              • <author initials="M" surname="Tuexen" fullname="Michael Tuexen">
                • <organization/>
                • </author>
              • <date month="August" year="2019"/>
              • <abstract>
                • <t>
                  • The WebRTC framework specifies protocol support for direct interactive rich communication using audio, video, and data between two peers' web-browsers. This document specifies the non-media data transport aspects of the WebRTC framework. It provides an architectural overview of how the Stream Control Transmission Protocol (SCTP) is used in the WebRTC context as a generic transport service allowing WEB-browsers to exchange generic data from peer to peer.
                  • </t>
                • </abstract>
              • </front>
            • </reference>
          • <reference anchor="RFCCCCC" target="https://www.rfc-editor.org/info/rfcCCCC">
            • <front>
              • <title>
                • WebRTC Data Channel Establishment Protocol
                • </title>
              • <seriesInfo name="RFC" value="CCCC"/>
              • <seriesInfo name="DOI" value="10.17487/RFCCCCC"/>
              • <author initials="R" surname="Jesup" fullname="Randell Jesup">
                • <organization/>
                • </author>
              • <author initials="S" surname="Loreto" fullname="Salvatore Loreto">
                • <organization/>
                • </author>
              • <author initials="M" surname="Tuexen" fullname="Michael Tuexen">
                • <organization/>
                • </author>
              • <date month="August" year="2019"/>
              • <abstract>
                • <t>
                  • The WebRTC framework specifies protocol support for direct interactive rich communication using audio, video, and data between two peers' web-browsers. This document specifies a simple protocol for establishing symmetric Data Channels between the peers. It uses a two way handshake and allows sending of user data without waiting for the handshake to complete.
                  • </t>
                • </abstract>
              • </front>
            • </reference>
          • <reference anchor="RFCDDDD" target="https://www.rfc-editor.org/info/rfcDDDD">
            • <front>
              • <title>
                • WebRTC Security Architecture
                • </title>
              • <seriesInfo name="RFC" value="DDDD"/>
              • <seriesInfo name="DOI" value="10.17487/RFCDDDD"/>
              • <author initials="E" surname="Rescorla" fullname="Eric Rescorla">
                • <organization/>
                • </author>
              • <date month="August" year="2019"/>
              • <abstract>
                • <t>
                  • This document defines the security architecture for WebRTC, a protocol suite intended for use with real-time applications that can be deployed in browsers - "real time communication on the Web".
                  • </t>
                • </abstract>
              • </front>
            • </reference>
          • <reference anchor="RFCEEEE" target="https://www.rfc-editor.org/info/rfcEEEE">
            • <front>
              • <title>
                • JavaScript Session Establishment Protocol
                • </title>
              • <seriesInfo name="RFC" value="EEEE"/>
              • <seriesInfo name="DOI" value="10.17487/RFCEEEE"/>
              • <author initials="J" surname="Uberti" fullname="Justin Uberti">
                • <organization/>
                • </author>
              • <author initials="C" surname="Jennings" fullname="Cullen Jennings">
                • <organization/>
                • </author>
              • <author initials="E" surname="Rescorla" fullname="Eric Rescorla">
                • <organization/>
                • </author>
              • <date month="August" year="2019"/>
              • <abstract>
                • <t>
                  • This document describes the mechanisms for allowing a JavaScript application to control the signaling plane of a multimedia session via the interface specified in the W3C RTCPeerConnection API, and discusses how this relates to existing signaling protocols.
                  • </t>
                • </abstract>
              • </front>
            • </reference>
          • <reference anchor="W3C.WD-webrtc-20120209" target="http://www.w3.org/TR/2012/WD-webrtc-20120209" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml4/reference.W3C.WD-webrtc-20120209.xml">
            • <front>
              • <title>
                • WebRTC 1.0: Real-time Communication Between Browsers
                • </title>
              • <seriesInfo name="World Wide Web Consortium WD" value="WD-webrtc-20120209"/>
              • <author initials="A." surname="Bergkvist" fullname="Adam Bergkvist">
                • <organization/>
                • </author>
              • <author initials="D." surname="Burnett" fullname="Daniel C. Burnett">
                • <organization/>
                • </author>
              • <author initials="C." surname="Jennings" fullname="Cullen Jennings">
                • <organization/>
                • </author>
              • <author initials="A." surname="Narayanan" fullname="Anant Narayanan">
                • <organization/>
                • </author>
              • <date month="February" year="2012"/>
              • </front>
            • </reference>
          • <reference anchor="W3C.WD-mediacapture-streams-20120628" target="http://www.w3.org/TR/2012/WD-mediacapture-streams-20120628" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml4/reference.W3C.WD-mediacapture-streams-20120628.xml">
            • <front>
              • <title>
                • Media Capture and Streams
                • </title>
              • <seriesInfo name="World Wide Web Consortium WD" value="WD-mediacapture-streams-20120628"/>
              • <author initials="D." surname="Burnett" fullname="Daniel C. Burnett">
                • <organization/>
                • </author>
              • <author initials="A." surname="Narayanan" fullname="Anant Narayanan">
                • <organization/>
                • </author>
              • <date month="June" year="2012"/>
              • </front>
            • </reference>
          • </references>
        • <references>
          • <name>
            • Informative References
            • </name>
          • <reference anchor="RFC3261" target="https://www.rfc-editor.org/info/rfc3261" xml:base="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3261.xml" "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3261.xml" >
            • <front>
              • <title>
                • SIP: Session Initiation Protocol
                • </title>
              • <author initials="J." surname="Rosenberg" fullname="J. Rosenberg">
                • <organization/>
                • </author>
              • <author initials="H." surname="Schulzrinne" fullname="H. Schulzrinne">
                • <organization/>
                • </author>
              • <author initials="G." surname="Camarillo" fullname="G. Camarillo">
                • <organization/>
                • </author>
              • <author initials="A." surname="Johnston" fullname="A. Johnston">
                • <organization/>
                • </author>
              • <author initials="J." surname="Peterson" fullname="J. Peterson">
                • <organization/>
                • </author>
              • <author initials="R." surname="Sparks" fullname="R. Sparks">
                • <organization/>
                • </author>
              • <author initials="M." surname="Handley" fullname="M. Handley">
                • <organization/>
                • </author>
              • <author initials="E." surname="Schooler" fullname="E. Schooler">
                • <organization/>
                • </author>
              • <date year="2002" month="June"/>
              • <abstract>
                • <t>
                  • This document describes Session Initiation Protocol (SIP), an application-layer control (signaling) protocol for creating, modifying, and terminating sessions with one or more participants. These sessions include Internet telephone calls, multimedia distribution, and multimedia conferences. [STANDARDS-TRACK]
                  • </t>
                • </abstract>
              • </front>
            • <seriesInfo name="RFC" value="3261"/>
            • <seriesInfo name="DOI" value="10.17487/RFC3261"/>
            • </reference>
          • <reference anchor="RFC3361" target="https://www.rfc-editor.org/info/rfc3361" xml:base="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3361.xml" "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3361.xml" >
            • <front>
              • <title>
                • Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation Protocol (SIP) Servers
                • </title>
              • <author initials="H." surname="Schulzrinne" fullname="H. Schulzrinne">
                • <organization/>
                • </author>
              • <date year="2002" month="August"/>
              • </front>
            • <seriesInfo name="RFC" value="3361"/>
            • <seriesInfo name="DOI" value="10.17487/RFC3361"/>
            • </reference>
          • <reference anchor="RFC3935" target="https://www.rfc-editor.org/info/rfc3935" xml:base="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3935.xml" "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3935.xml" >
            • <front>
              • <title>
                • A Mission Statement for the IETF
                • </title>
              • <author initials="H." surname="Alvestrand" fullname="H. Alvestrand">
                • <organization/>
                • </author>
              • <date year="2004" month="October"/>
              • <abstract>
                • <t>
                  • This memo gives a mission statement for the IETF, tries to define the terms used in the statement sufficiently to make the mission statement understandable and useful, argues why the IETF needs a mission statement, and tries to capture some of the debate that led to this point. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
                  • </t>
                • </abstract>
              • </front>
            • <seriesInfo name="BCP" value="95"/>
            • <seriesInfo name="RFC" value="3935"/>
            • <seriesInfo name="DOI" value="10.17487/RFC3935"/>
            • </reference>
          • <reference anchor="RFC5761" target="https://www.rfc-editor.org/info/rfc5761" xml:base="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5761.xml" "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5761.xml" >
            • <front>
              • <title>
                • Multiplexing RTP Data and Control Packets on a Single Port
                • </title>
              • <author initials="C." surname="Perkins" fullname="C. Perkins">
                • <organization/>
                • </author>
              • <author initials="M." surname="Westerlund" fullname="M. Westerlund">
                • <organization/>
                • </author>
              • <date year="2010" month="April"/>
              • <abstract>
                • <t>
                  • This memo discusses issues that arise when multiplexing RTP data packets and RTP Control Protocol (RTCP) packets on a single UDP port. It updates RFC 3550 and RFC 3551 to describe when such multiplexing is and is not appropriate, and it explains how the Session Description Protocol (SDP) can be used to signal multiplexed sessions. [STANDARDS-TRACK]
                  • </t>
                • </abstract>
              • </front>
            • <seriesInfo name="RFC" value="5761"/>
            • <seriesInfo name="DOI" value="10.17487/RFC5761"/>
            • </reference>
          • <reference anchor="RFC6120" target="https://www.rfc-editor.org/info/rfc6120" xml:base="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6120.xml" "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.6120.xml" >
            • <front>
              • <title>
                • Extensible Messaging and Presence Protocol (XMPP): Core
                • </title>
              • <author initials="P." surname="Saint-Andre" fullname="P. Saint-Andre">
                • <organization/>
                • </author>
              • <date year="2011" month="March"/>
              • <abstract>
                • <t>
                  • The Extensible Messaging and Presence Protocol (XMPP) is an application profile of the Extensible Markup Language (XML) that enables the near-real-time exchange of structured yet extensible data between any two or more network entities. This document defines XMPP's core protocol methods: setup and teardown of XML streams, channel encryption, authentication, error handling, and communication primitives for messaging, network availability ("presence"), and request-response interactions. This document obsoletes RFC 3920. [STANDARDS-TRACK]
                  • </t>
                • </abstract>
              • </front>
            • <seriesInfo name="RFC" value="6120"/>
            • <seriesInfo name="DOI" value="10.17487/RFC6120"/>
            • </reference>
          • <reference anchor="RFC7478" target="https://www.rfc-editor.org/info/rfc7478" xml:base="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7478.xml" "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.7478.xml" >
            • <front>
              • <title>
                • Web Real-Time Communication Use Cases and Requirements
                • </title>
              • <author initials="C." surname="Holmberg" fullname="C. Holmberg">
                • <organization/>
                • </author>
              • <author initials="S." surname="Hakansson" fullname="S. Hakansson">
                • <organization/>
                • </author>
              • <author initials="G." surname="Eriksson" fullname="G. Eriksson">
                • <organization/>
                • </author>
              • <date year="2015" month="March"/>
              • <abstract>
                • <t>
                  • This document describes web-based real-time communication use cases. Requirements on the browser functionality are derived from the use cases.
                  • </t>
                • <t>
                  • This document was developed in an initial phase of the work with rather minor updates at later stages. It has not really served as a tool in deciding features or scope for the WG's efforts so far. It is being published to record the early conclusions of the WG. It will not be used as a set of rigid guidelines that specifications and implementations will be held to in the future.
                  • </t>
                • </abstract>
              • </front>
            • <seriesInfo name="RFC" value="7478"/>
            • <seriesInfo name="DOI" value="10.17487/RFC7478"/>
            • </reference>
          • <reference anchor="RFC8155" target="https://www.rfc-editor.org/info/rfc8155" xml:base="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8155.xml" "https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8155.xml" >
            • <front>
              • <title>
                • Traversal Using Relays around NAT (TURN) Server Auto Discovery
                • </title>
              • <author initials="P." surname="Patil" fullname="P. Patil">
                • <organization/>
                • </author>
              • <author initials="T." surname="Reddy" fullname="T. Reddy">
                • <organization/>
                • </author>
              • <author initials="D." surname="Wing" fullname="D. Wing">
                • <organization/>
                • </author>
              • <date year="2017" month="April"/>
              • <abstract>
                • <t>
                  • Current Traversal Using Relays around NAT (TURN) server discovery mechanisms are relatively static and limited to explicit configuration. These are usually under the administrative control of the application or TURN service provider, and not the enterprise, ISP, or the network in which the client is located. Enterprises and ISPs wishing to provide their own TURN servers need auto-discovery mechanisms that a TURN client could use with minimal or no configuration. This document describes three such mechanisms for TURN server discovery.
                  • </t>
                • <t>
                  • This document updates RFC 5766 to relax the requirement for mutual authentication in certain cases.
                  • </t>
                • </abstract>
              • </front>
            • <seriesInfo name="RFC" value="8155"/>
            • <seriesInfo name="DOI" value="10.17487/RFC8155"/>
            • </reference>
          • <reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml">
            • <front>
              • <title>
                • Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
                • </title>
              • <author initials="B." surname="Leiba" fullname="B. Leiba">
                • <organization/>
                • </author>
              • <date year="2017" month="May"/>
              • <abstract>
                • <t>
                  • RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.
                  • </t>
                • </abstract>
              • </front>
            • <seriesInfo name="BCP" value="14"/>
            • <seriesInfo name="RFC" value="8174"/>
            • <seriesInfo name="DOI" value="10.17487/RFC8174"/>
            • </reference>
          • <reference anchor="W3C.WD-html5-20110525" target="http://www.w3.org/TR/2011/WD-html5-20110525" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml4/reference.W3C.WD-html5-20110525.xml">
            • <front>
              • <title>
                • HTML5
                • </title>
              • <seriesInfo name="World Wide Web Consortium LastCall," value="WD-html5-20110525"/>
              • <author initials="I." surname="Hickson" fullname="Ian Hickson">
                • <organization/>
                • </author>
              • <date month="May" year="2011"/>
              • </front>
            • </reference>
          • <reference anchor="I-D.ietf-ice-trickle">
            • <front>
              • <title>
                • Trickle ICE: Incremental Provisioning of Candidates for the Interactive Connectivity Establishment (ICE) Protocol
                • </title>
              • <seriesInfo name="Work in Progress," value="draft-ietf-ice-trickle-21"/>
              • <author initials="E" surname="Ivov" fullname="Emil Ivov">
                • <organization/>
                • </author>
              • <author initials="E" surname="Rescorla" fullname="Eric Rescorla">
                • <organization/>
                • </author>
              • <author initials="J" surname="Uberti" fullname="Justin Uberti">
                • <organization/>
                • </author>
              • <author initials="P" surname="Saint-Andre" fullname="Peter Saint-Andre">
                • <organization/>
                • </author>
              • <date month="April" year="2018"/>
              • <abstract>
                • <t>
                  • This document describes "Trickle ICE", an extension to the Interactive Connectivity Establishment (ICE) protocol that enables ICE agents to begin connectivity checks while they are still gathering candidates, by incrementally exchanging candidates over time instead of all at once. This method can considerably accelerate the process of establishing a communication session.
                  • </t>
                • </abstract>
              • </front>
            • </reference>
          • <reference anchor="I-D.ietf-mmusic-sdp-bundle-negotiation">
            • <front>
              • <title>
                • Negotiating Media Multiplexing Using the Session Description Protocol (SDP)
                • </title>
              • <seriesInfo name="Work in Progress," value="draft-ietf-mmusic-sdp-bundle-negotiation-54"/>
              • <author initials="C" surname="Holmberg" fullname="Christer Holmberg">
                • <organization/>
                • </author>
              • <author initials="H" surname="Alvestrand" fullname="Harald Alvestrand">
                • <organization/>
                • </author>
              • <author initials="C" surname="Jennings" fullname="Cullen Jennings">
                • <organization/>
                • </author>
              • <date month="December" year="2018"/>
              • <abstract>
                • <t>
                  • This specification defines a new Session Description Protocol (SDP) Grouping Framework extension, 'BUNDLE'. The extension can be used with the SDP Offer/Answer mechanism to negotiate the usage of a single transport (5-tuple) for sending and receiving media described by multiple SDP media descriptions ("m=" sections). Such transport is referred to as a BUNDLE transport, and the media is referred to as bundled media. The "m=" sections that use the BUNDLE transport form a BUNDLE group. This specification updates RFC 3264, to also allow assigning a zero port value to a "m=" section in cases where the media described by the "m=" section is not disabled or rejected. This specification updates RFC 5888, to also allow an SDP 'group' attribute to contain an identification-tag that identifies a "m=" section with the port set to zero. This specification defines a new RTP Control Protocol (RTCP) source description (SDES) item and a new RTP header extension that can be used to correlate bundled RTP/RTCP packets with their appropriate "m=" section. This specification updates RFC 7941, by adding an exception, for the MID RTP header extension, to the requirement regarding protection of an SDES RTP header extension carrying an SDES item for the MID RTP header extension.
                  • </t>
                • </abstract>
              • </front>
            • </reference>
          • <reference anchor="I-D.ietf-rtcweb-gateways">
            • <front>
              • <title>
                • WebRTC Gateways
                • </title>
              • <seriesInfo name="Work in Progress," value="draft-ietf-rtcweb-gateways-02"/>
              • <author initials="H" surname="Alvestrand" fullname="Harald T. Alvestrand">
                • <organization/>
                • </author>
              • <author initials="U" surname="Rauschenbach" fullname="Uwe Rauschenbach">
                • <organization/>
                • </author>
              • <date month="January" year="2016"/>
              • <abstract>
                • <t>
                  • This document describes interoperability considerations for a class of WebRTC-compatible endpoints called "WebRTC gateways", which interconnect between WebRTC endpoints and devices that are not WebRTC endpoints.
                  • </t>
                • </abstract>
              • </front>
            • </reference>
          • <reference anchor="I-D.ietf-tsvwg-rtcweb-qos">
            • <front>
              • <title>
                • DSCP Packet Markings for WebRTC QoS
                • </title>
              • <seriesInfo name="Work in Progress," value="draft-ietf-tsvwg-rtcweb-qos-18"/>
              • <author initials="P" surname="Jones" fullname="Paul Jones">
                • <organization/>
                • </author>
              • <author initials="S" surname="Dhesikan" fullname="Subha Dhesikan">
                • <organization/>
                • </author>
              • <author initials="C" surname="Jennings" fullname="Cullen Jennings">
                • <organization/>
                • </author>
              • <author initials="D" surname="Druta" fullname="Dan Druta">
                • <organization/>
                • </author>
              • <date month="August" year="2016"/>
              • <abstract>
                • <t>
                  • Many networks, such as service provider and enterprise networks, can provide different forwarding treatments for individual packets based on Differentiated Services Code Point (DSCP) values on a per-hop basis. This document provides the recommended DSCP values for web browsers to use for various classes of WebRTC traffic.
                  • </t>
                • </abstract>
              • </front>
            • </reference>
          • <reference anchor="XEP-0166" target="http://xmpp.org/extensions/xep-0166.html">
            • <front>
              • <title>
                • Jingle
                • </title>
              • <seriesInfo name="XSF XEP" value="0166"/>
              • <author fullname="Scott Ludwig" initials="S." surname="Ludwig">
                • <organization/>
                • <address>
                  • <email>
                    • scottlu@google.com
                    • </email>
                  • </address>
                • </author>
              • <author fullname="Joe Beda" initials="J." surname="Beda">
                • <organization/>
                • <address>
                  • <email>
                    • jbeda@google.com
                    • </email>
                  • </address>
                • </author>
              • <author fullname="Peter Saint-Andre" initials="P." surname="Saint-Andre">
                • <organization/>
                • <address>
                  • <email>
                    • stpeter@jabber.org
                    • </email>
                  • </address>
                • </author>
              • <author fullname="Robert McQueen" initials="R." surname="McQueen">
                • <organization/>
                • <address>
                  • <email>
                    • robert.mcqueen@collabora.co.uk
                    • </email>
                  • </address>
                • </author>
              • <author fullname="Sean Egan" initials="S." surname="Egan">
                • <organization/>
                • <address>
                  • <email>
                    • seanegan@google.com
                    • </email>
                  • </address>
                • </author>
              • <author fullname="Joe Hildebrand" initials="J." surname="Hildebrand">
                • <organization/>
                • <address>
                  • <email>
                    • jhildebr@cisco.com
                    • </email>
                  • </address>
                • </author>
              • <date month="June" year="2007"/>
              • </front>
            • </reference>
          • <reference anchor="XEP-0124" target="http://xmpp.org/extensions/xep-0124.html">
            • <front>
              • <title>
                • BOSH
                • </title>
              • <seriesInfo name="XSF XEP" value="0124"/>
              • <author fullname="Ian Paterson" initials="I." surname="Paterson">
                • <organization/>
                • <address>
                  • <email>
                    • ian.paterson@clientside.co.uk
                    • </email>
                  • </address>
                • </author>
              • <author fullname="Dave Smith" initials="D." surname="Smith">
                • <organization/>
                • <address>
                  • <email>
                    • dizzyd@jabber.org
                    • </email>
                  • </address>
                • </author>
              • <author fullname="Peter Saint-Andre" initials="P." surname="Saint-Andre">
                • <organization/>
                • <address>
                  • <email>
                    • stpeter@jabber.org
                    • </email>
                  • </address>
                • </author>
              • <author fullname="Jack Moffitt" initials="J." surname="Moffitt">
                • <organization/>
                • <address>
                  • <email>
                    • jack@chesspark.com
                    • </email>
                  • </address>
                • </author>
              • <author fullname="Lance Stout" initials="L." surname="Stout">
                • <organization/>
                • <address>
                  • <email>
                    • lance@andyet.com
                    • </email>
                  • </address>
                • </author>
              • <author fullname="Winifried Tilanus" initials="W." surname="Tilanus">
                • <organization/>
                • <address>
                  • <email>
                    • winfried@tilanus.com
                    • </email>
                  • </address>
                • </author>
              • <date month="November" year="2016"/>
              • </front>
            • </reference>
          • </references>
        • </references>
      • </back>
    • </rfc>
1<?xml version='1.0' encoding='utf-8'?>
2<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
3<rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="std" number="0000" ipr="trust200902" obsoletes="" updates="" consensus="true" submissionType="IETF" xml:lang="en" tocInclude="true" symRefs="true" sortRefs="true" version="3">
4  <!-- xml2rfc v2v3 conversion 2.23.1 -->
5  <front>
6    <title abbrev="WebRTC Overview">Overview: Real Time Protocols for
7    Browser-based Applications</title>
8    <seriesInfo name="RFC" value="0000"/>
9    <author fullname="Harald T. Alvestrand" initials="H. T." surname="Alvestrand">
10      <organization>Google</organization>
11      <address>
12        <postal>
13          <street>Kungsbron 2</street>
14          <city>Stockholm</city>
15          <region/>
16          <code>11122</code>
17          <country>Sweden</country>
18        </postal>
19        <email>harald@alvestrand.no</email>
20      </address>
21    </author>
22    <date month="July" year="2019"/>
23    <abstract>
24      <t>This document gives an overview and context of a protocol suite
25      intended for use with real-time applications that can be deployed in
26      browsers - "real time communication on the Web".</t>
27      <t>It intends to serve as a starting and coordination point to make sure
28      all the parts that are needed to achieve this goal are findable, and
29      that the parts that belong in the Internet protocol suite are fully
30      specified and on the right publication track.</t>
31      <t>This document is an Applicability Statement - it does not itself
32      specify any protocol, but specifies which other specifications WebRTC
33      compliant implementations are supposed to follow.</t>
34      <t>This document is a work item of the RTCWEB working group.</t>
35    </abstract>
36  </front>
37  <middle>
38    <section numbered="true" toc="default" anchor="Intro">
39      <name>Introduction</name>
40      <t>The Internet was, from very early in its lifetime, considered a
41      possible vehicle for the deployment of real-time, interactive
42      applications - with the most easily imaginable being audio conversations
43      (aka "Internet telephony") and video conferencing.</t>
44      <t>The first attempts to build this were dependent on special networks,
45      special hardware and custom-built software, often at very high prices or
46      at low quality, placing great demands on the infrastructure.</t>
47      <t>As the available bandwidth has increased, and as processors and other
48      hardware has become ever faster, the barriers to participation have
49      decreased, and it has become possible to deliver a satisfactory
50      experience on commonly available computing hardware.</t>
51      <t>Still, there are a number of barriers to the ability to communicate
52      universally - one of these is that there is, as of yet, no single set of
53      communication protocols that all agree should be made available for
54      communication; another is the sheer lack of universal identification
55      systems (such as is served by telephone numbers or email addresses in
56      other communications systems).</t>
57      <t>Development of The Universal Solution has, however, proved hard.</t>
58      <t>The last few years have also seen a new platform rise for deployment
59      of services: The browser-embedded application, or "Web application". It
60      turns out that as long as the browser platform has the necessary
61      interfaces, it is possible to deliver almost any kind of service on
62      it.</t>
63      <t>Traditionally, these interfaces have been delivered by plugins, which
64      had to be downloaded and installed separately from the browser; in the
65      development of HTML5, application developers see much promise in the
66      possibility of making those interfaces available in a standardized way
67      within the browser.</t>
68      <t>This memo describes a set of building blocks that can be made
69      accessible and controllable through a JavaScript API in a browser, and
70      which together form a sufficient set of functions to allow the use of
71      interactive audio and video in applications that communicate directly
72      between browsers across the Internet. The resulting protocol suite is
73      intended to enable all the applications that are described as required
74      scenarios in the use cases document <xref target="RFC7478" format="default"/>.</t>
75      <t>Other efforts, for instance the W3C Web Real-Time Communications,
76      Web Applications Security, and Device and Sensor working groups, focus
77      on making standardized APIs and interfaces available, within or
78      alongside the HTML5 effort, for those functions.  This memo concentrates
79      on specifying the protocols and  sub-protocols that are needed to specify
80      the interactions over the network.</t>
81      <t>Operators should note that deployment of WebRTC will result in a
82      change in the nature of signaling for real time media on the network,
83      and may result in a shift in the kinds of devices used to create and
84      consume such media. In the case of signaling, WebRTC session setup
85      will typically occur over TLS-secured web technologies using
86      application-specific protocols.  Operational techniques that involve
87      inserting network elements to interpret SDP -- either through endpoint
88      cooperation <xref target="RFC3361" format="default"/> or through the transparent
89      insertion of SIP Application Level Gateways (ALGs) -- will not work
90      with such signaling. In the case of networks using cooperative
91      endpoints, the approaches defined in <xref target="RFC8155" format="default"/> may serve
92      as a suitable replacement for <xref target="RFC3361" format="default"/>. The increase in
93      browser-based communications may also lead to a shift away from
94      dedicated real-time-communications hardware, such as SIP
95      desk phones. This will diminish the efficacy of operational
96      techniques that place dedicated real-time devices on their own
97      network segment, address range, or VLAN for purposes such as
98      applying traffic filtering and QoS. Applying the markings
99      described in <xref target="I-D.ietf-tsvwg-rtcweb-qos" format="default"/> may be
100      appropriate replacements for such techniques.</t>
101      <t>This memo uses the term "WebRTC" (note the case used) to refer to the
102      overall effort consisting of both IETF and W3C efforts.</t>
103    </section>
104    <section numbered="true" toc="default">
105      <name>Principles and Terminology</name>
106      <section numbered="true" toc="default">
107        <name>Goals of this document</name>
108        <t>The goal of the WebRTC protocol specification is to specify a set
109        of protocols that, if all are implemented, will allow an
110        implementation to communicate with another implementation using audio,
111        video and data sent along the most direct possible path between the
112        participants.</t>
113        <t>This document is intended to serve as the roadmap to the WebRTC
114        specifications. It defines terms used by other parts of the WebRTC
115        protocol specifications, lists references to other specifications that
116        don't need further elaboration in the WebRTC context, and gives
117        pointers to other documents that form part of the WebRTC suite.</t>
118        <t>By reading this document and the documents it refers to, it should
119        be possible to have all information needed to implement a WebRTC
120        compatible implementation.</t>
121      </section>
122      <section numbered="true" toc="default">
123        <name>Relationship between API and protocol</name>
124        <t>The total WebRTC effort consists of two major parts, each
125        consisting of multiple documents:</t>
126        <ul spacing="normal">
127          <li>A protocol specification, done in the IETF</li>
128          <li>A JavaScript API specification, defined in a series of W3C
129            documents <xref target="W3C.WD-webrtc-20120209" format="default"/><xref target="W3C.WD-mediacapture-streams-20120628" format="default"/></li>
130        </ul>
131        <t>Together, these two specifications aim to provide an
132        environment where JavaScript embedded in any page, when suitably
133        authorized by its user, is able to set up communication using audio,
134        video and auxiliary data, as long as the browser supports this
135        specification. The browser environment does not constrain the types of
136        application in which this functionality can be used.</t>
137        <t>The protocol specification does not assume that all implementations
138        implement this API; it is not intended to be necessary for
139        interoperation to know whether the entity one is communicating with is
140        a browser or another device implementing this specification.</t>
141        <t>The goal of cooperation between the protocol specification and the
142        API specification is that for all options and features of the protocol
143        specification, it should be clear which API calls to make to exercise
144        that option or feature; similarly, for any sequence of API calls, it
145        should be clear which protocol options and features will be invoked.
146        Both subject to constraints of the implementation, of course.</t>
147        <t>The following terms are used across the documents specifying the
148        WebRTC suite, in the specific meanings given here. Not all terms are
149        used in this document. Other terms are used in their commonly used
150        meaning.</t>
151
152<dl newline="false" spacing="normal">
153          <dt>Agent:</dt>
154          <dd>Undefined term. See "SDP Agent" and "ICE
155            Agent".</dd>
156          <dt>Application Programming Interface (API):</dt>
157          <dd>A
158            specification of a set of calls and events, usually tied to a
159            programming language or an abstract formal specification such as
160            WebIDL, with its defined semantics.</dd>
161          <dt>Browser:</dt>
162          <dd>Used synonymously with "Interactive User
163            Agent" as defined in the HTML specification <xref target="W3C.WD-html5-20110525" format="default"/>. See also "WebRTC User
164            Agent".</dd>
165          <dt>Data Channel:</dt>
166          <dd>An abstraction that allows data to be
167            sent between WebRTC endpoints in the form of messages. Two
168            endpoints can have multiple data channels between them.</dd>
169          <dt>ICE Agent:</dt>
170          <dd>An implementation of the Interactive
171            Connectivity Establishment (ICE) <xref target="RFC5245" format="default"/> protocol. An ICE Agent may also
172            be an SDP Agent, but there exist ICE Agents that do not use SDP
173            (for instance those that use Jingle <xref target="XEP-0166" format="default">
174            </xref>).</dd>
175          <dt>Interactive:</dt>
176          <dd>Communication between multiple parties,
177            where the expectation is that an action from one party can cause a
178            reaction by another party, and the reaction can be observed by the
179            first party, with the total time required for the
180            action/reaction/observation is on the order of no more than
181            hundreds of milliseconds.</dd>
182          <dt>Media:</dt>
183          <dd>Audio and video content. Not to be confused
184            with "transmission media" such as wires.</dd>
185          <dt>Media Path:</dt>
186          <dd>The path that media data follows from
187            one WebRTC endpoint to another.</dd>
188          <dt>Protocol:</dt>
189          <dd>A specification of a set of data units,
190            their representation, and rules for their transmission, with their
191            defined semantics. A protocol is usually thought of as going
192            between systems.</dd>
193          <dt>Real-time Media:</dt>
194          <dd>Media where generation of content
195            and display of content are intended to occur closely together in
196            time (on the order of no more than hundreds of milliseconds).
197            Real-time media can be used to support interactive
198            communication.</dd>
199          <dt>SDP Agent:</dt>
200          <dd>The protocol implementation involved in
201            the Session Description Protocol (SDP) offer/answer exchange, as
202            defined in <xref target="RFC3264" sectionFormat="comma" section="3"/></dd>
203          <dt>Signaling:</dt>
204          <dd>Communication that happens in order to
205            establish, manage and control media paths and data paths.</dd>
206          <dt>Signaling Path:</dt>
207          <dd>The communication channels used
208            between entities participating in signaling to transfer signaling.
209            There may be more entities in the signaling path than in the media
210            path.</dd>
211          <dt>WebRTC Browser:</dt>
212          <dd>(also called a WebRTC User Agent
213            or WebRTC UA) Something that conforms to both the protocol
214            specification and the JavaScript API cited above.</dd>
215          <dt>WebRTC non-Browser:</dt>
216          <dd> Something that conforms to
217            the protocol specification, but does not claim to implement the
218            JavaScript API.  This can also be called a "WebRTC device" or
219            "WebRTC native application".</dd>
220          <dt>WebRTC Endpoint:</dt>
221          <dd> Either a WebRTC browser or a
222            WebRTC non-browser. It conforms to the protocol specification.</dd>
223          <dt>WebRTC-compatible Endpoint:</dt>
224          <dd> An endpoint that is able
225            to successfully communicate with a WebRTC endpoint, but may fail to
226            meet some requirements of a WebRTC endpoint. This may limit where
227            in the network such an endpoint can be attached, or may limit the
228            security guarantees that it offers to others. It is not
229            constrained by this specification; when it is mentioned at all, it
230            is to note the implications on WebRTC-compatible endpoints of the
231            requirements placed on WebRTC endpoints.</dd>
232          <dt>WebRTC Gateway:</dt>
233          <dd> A WebRTC-compatible endpoint that
234            mediates media traffic to non-WebRTC entities.</dd>
235        </dl>
236
237
238        <t>All WebRTC browsers are WebRTC endpoints, so any requirement
239        on a WebRTC endpoint also applies to a WebRTC browser.</t>
240        <t>A WebRTC non-browser may be capable of hosting applications in a
241        similar way to the way in which a browser can host JavaScript
242        applications, typically by offering APIs in other languages. For
243        instance it may be implemented as a library that offers a C++ API
244        intended to be loaded into applications. In this case, similar
245        security considerations as for JavaScript may be needed; however,
246        since such APIs are not defined or referenced here, this document
247        cannot give any specific rules for those interfaces.</t>
248        <t>WebRTC gateways are described in a separate document, <xref target="I-D.ietf-rtcweb-gateways" format="default"/>.</t>
249      </section>
250      <section numbered="true" toc="default">
251        <name>On interoperability and innovation</name>
252        <t>The "Mission statement of the IETF" <xref target="RFC3935" format="default"/> states
253        that "The benefit of a standard to the Internet is in interoperability
254        - that multiple products implementing a standard are able to work
255        together in order to deliver valuable functions to the Internet's
256        users."</t>
257        <t>Communication on the Internet frequently occurs in two phases:</t>
258        <ul spacing="normal">
259          <li>Two parties communicate, through some mechanism, what
260            functionality they both are able to support</li>
261          <li>They use that shared communicative functionality to
262            communicate, or, failing to find anything in common, give up on
263            communication.</li>
264        </ul>
265        <t>There are often many choices that can be made for
266        communicative functionality; the history of the Internet is rife with
267        the proposal, standardization, implementation, and success or failure
268        of many types of options, in all sorts of protocols.</t>
269        <t>The goal of having a mandatory to implement function set is to
270        prevent negotiation failure, not to preempt or prevent
271        negotiation.</t>
272        <t>The presence of a mandatory to implement function set serves as a
273        strong changer of the marketplace of deployment - in that it gives a
274        guarantee that, as long as you conform to a specification, and the
275        other party is willing to accept communication at the base level of
276        that specification, you can communicate successfully.</t>
277        <t>The alternative, that is having no mandatory to implement, does
278        not mean that you cannot communicate, it merely means that in order to
279        be part of the communications partnership, you have to implement the
280        standard "and then some".  The "and then some" is usually called a
281        profile of some sort; in the version most antithetical to the Internet
282        ethos, that "and then some" consists of having to use a specific
283        vendor's product only.</t>
284      </section>
285      <section numbered="true" toc="default">
286        <name>Terminology</name>
287        <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>",
288    "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
289    NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>",
290    "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
291    "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are
292    to be interpreted as described in BCP 14 <xref target="RFC2119"/>
293    <xref target="RFC8174"/> when, and only when, they appear in all capitals,
294    as shown here. 
295</t>
296      </section>
297    </section>
298    <section numbered="true" toc="default">
299      <name>Architecture and Functionality groups</name>
300      <t>For browser-based applications, the model for real-time support does
301     not assume that the browser will contain all the functions needed for
302     an application such as a telephone or a video conference.  The vision is
303     that the browser will have the functions needed for a Web application,
304     working in conjunction with its backend servers, to implement these
305     functions.</t>
306      <t>This means that two vital interfaces need specification: The
307      protocols that browsers use to talk to each other, without any
308      intervening servers, and the APIs that are offered for a JavaScript
309      application to take advantage of the browser's functionality.</t>
310      <figure anchor="fig-browser-model">
311        <name>Browser Model</name>
312        <artwork name="" type="" align="left" alt="">
313
314                                                                          
315                     +------------------------+  On-the-wire              
316                     |                        |  Protocols                
317                     |      Servers           |---------&gt;                 
318                     |                        |                           
319                     |                        |                           
320                     +------------------------+                           
321                                 ^                                        
322                                 |                                        
323                                 |                                        
324                                 | HTTPS/                                  
325                                 | WebSockets                             
326                                 |                                              
327                                 |                                        
328                   +----------------------------+                         
329                   |    JavaScript/HTML/CSS     |                         
330                   +----------------------------+                         
331                Other  ^                 ^ RTC                             
332                APIs   |                 | APIs                            
333                   +---|-----------------|------+                         
334                   |   |                 |      |                         
335                   |                 +---------+|                         
336                   |                 | Browser ||  On-the-wire            
337                   | Browser         | RTC     ||  Protocols              
338                   |                 | Function|-----------&gt;              
339                   |                 |         ||                         
340                   |                 |         ||                         
341                   |                 +---------+|                         
342                   +---------------------|------+                         
343                                         |                                
344                                         V                                
345                                    Native OS Services
346</artwork>
347      </figure>
348      <t>Note that HTTPS and WebSockets are also offered to the JavaScript
349      application through browser APIs.</t>
350      <t>As for all protocol and API specifications, there is no restriction
351      that the protocols can only be used to talk to another browser; since
352      they are fully specified, any endpoint that implements the protocols
353      faithfully should be able to interoperate with the application running
354      in the browser.</t>
355      <t>A commonly imagined model of deployment is the one depicted
356      below.  In <xref target="fig-webtrapezoid"/> below, JS is JavaScript.</t>
357      <figure anchor="fig-webtrapezoid">
358        <name>Browser RTC Trapezoid</name>
359        <artwork name="" type="" align="left" alt=""><![CDATA[                                                                  
360                                                                          
361             +-----------+             +-----------+                      
362             |   Web     |             |   Web     |                      
363             |           |  Signaling  |           |                      
364             |           |-------------|           |                      
365             |  Server   |   path      |  Server   |                      
366             |           |             |           |                      
367             +-----------+             +-----------+                      
368                  /                           \                           
369                 /                             \ Application-defined      
370                /                               \ over       
371               /                                 \ HTTPS/WebSockets                    
372              /  Application-defined over         \                       
373             /   HTTPS/WebSockets                  \                      
374            /                                       \                     
375      +-----------+                           +-----------+               
376      |JS/HTML/CSS|                           |JS/HTML/CSS|               
377      +-----------+                           +-----------+               
378      +-----------+                           +-----------+               
379      |           |                           |           |               
380      |           |                           |           |               
381      |  Browser  | ------------------------- |  Browser  |               
382      |           |          Media path       |           |               
383      |           |                           |           |               
384      +-----------+                           +-----------+]]></artwork>
385      </figure>
386      <t>On this drawing, the critical part to note is that the media path
387      ("low path") goes directly between the browsers, so it has to be
388      conformant to the specifications of the WebRTC protocol suite; the
389      signaling path ("high path") goes via servers that can modify, translate
390      or manipulate the signals as needed.</t>
391      <t>If the two Web servers are operated by different entities, the
392      inter-server signaling mechanism needs to be agreed upon, either by
393      standardization or by other means of agreement. Existing protocols
394      (e.g. SIP <xref target="RFC3261" format="default"/> or XMPP <xref target="RFC6120" format="default"/>)
395      could be used between servers, while either a standards-based or
396      proprietary protocol could be used between the browser and the web
397      server.</t>
398      <t>For example, if both operators' servers implement SIP, SIP could be
399      used for communication between servers, along with either a standardized
400      signaling mechanism (e.g. SIP over WebSockets) or a proprietary
401      signaling mechanism used between the application running in the browser
402      and the web server. Similarly, if both operators' servers implement
403      Extensible Messaging and Presence Protocol (XMPP), XMPP could be used
404      for communication between XMPP servers, with either a standardized
405      signaling mechanism (e.g. XMPP over WebSockets or BOSH <xref target="XEP-0124" format="default"/> or a proprietary signaling mechanism used between the
406      application running in the browser and the web server.</t>
407      <t>The choice of protocols for client-server and inter-server
408       signaling, and definition of the translation between them, is outside
409      the scope of the WebRTC protocol suite described in the document.</t>
410      <t>The functionality groups that are needed in the browser can be
411      specified, more or less from the bottom up, as:</t>
412      <ul spacing="normal">
413        <li>Data transport: such as TCP, UDP and the means to securely set up
414          connections between entities, as well as the functions for deciding
415          when to send data: congestion management, bandwidth estimation and
416          so on.</li>
417        <li>Data framing: RTP, SCTP, DTLS, and other data formats that serve
418          as containers, and their functions for data confidentiality and
419          integrity.</li>
420        <li>Data formats: Codec specifications, format specifications and
421          functionality specifications for the data passed between systems.
422          Audio and video codecs, as well as formats for data and document
423          sharing, belong in this category. In order to make use of data
424          formats, a way to describe them, a session description, is
425          needed.</li>
426        <li>Connection management: Setting up connections, agreeing on data
427          formats, changing data formats during the duration of a call; SDP,
428          SIP, and Jingle/XMPP belong in this category.</li>
429        <li>Presentation and control: What needs to happen in order to ensure
430          that interactions behave in a non-surprising manner. This can
431          include floor control, screen layout, voice activated image
432          switching and other such functions - where part of the system
433          require the cooperation between parties. XCON and Cisco/Tandberg's
434          TIP were some attempts at specifying this kind of functionality;
435          many applications have been built without standardized interfaces to
436          these functions.</li>
437        <li>Local system support functions: These are things that need not be
438          specified uniformly, because each participant may choose to do these
439          in a way of the participant's choosing, without affecting the bits
440          on the wire in a way that others have to be cognizant of. Examples
441          in this category include echo cancellation (some forms of it), local
442          authentication and authorization mechanisms, OS access control and
443          the ability to do local recording of conversations.</li>
444      </ul>
445      <t>Within each functionality group, it is important to preserve
446      both freedom to innovate and the ability for global communication.
447      Freedom to innovate is helped by doing the specification in terms of
448      interfaces, not implementation; any implementation able to communicate
449      according to the interfaces is a valid implementation. Ability to
450      communicate globally is helped both by having core specifications be
451      unencumbered by IPR issues and by having the formats and protocols be
452      fully enough specified to allow for independent implementation.</t>
453      <t>One can think of the three first groups as forming a "media transport
454      infrastructure", and of the three last groups as forming a "media
455      service". In many contexts, it makes sense to use a common specification
456      for the media transport infrastructure, which can be embedded in
457      browsers and accessed using standard interfaces, and "let a thousand
458      flowers bloom" in the "media service" layer; to achieve interoperable
459      services, however, at least the first five of the six groups need to be
460      specified.</t>
461    </section>
462    <section anchor="ch-transport" numbered="true" toc="default">
463      <name>Data transport</name>
464      <t>Data transport refers to the sending and receiving of data over the
465      network interfaces, the choice of network-layer addresses at each end of
466      the communication, and the interaction with any intermediate entities
467      that handle the data, but do not modify it (such as TURN relays).</t>
468      <t>It includes necessary functions for congestion control,
469      retransmission, and in-order delivery.</t>
470      <t>WebRTC endpoints <bcp14>MUST</bcp14> implement the transport protocols described in
471      <xref target="RFCZZZZ" format="default"/>.</t>
472    </section>
473    <section numbered="true" toc="default">
474      <name>Data framing and securing</name>
475      <t>The format for media transport is RTP <xref target="RFC3550" format="default"/>.
476      Implementation of SRTP <xref target="RFC3711" format="default"/> is <bcp14>REQUIRED</bcp14> for all
477      implementations.</t>
478      <t>The detailed considerations for usage of functions from RTP and SRTP
479      are given in <xref target="RFCAAAA" format="default"/>. The security
480      considerations for the WebRTC use case are in <xref target="RFCYYYY" format="default"/>, and the resulting security
481      functions are described in <xref target="RFCDDDD" format="default"/>.</t>
482      <t>Considerations for the transfer of data that is not in RTP format is
483      described in <xref target="RFCBBBB" format="default"/>, and a
484      supporting protocol for establishing individual data channels is
485      described in <xref target="RFCCCCC" format="default"/>. WebRTC
486      endpoints <bcp14>MUST</bcp14> implement these two specifications.</t>
487      <t>WebRTC endpoints <bcp14>MUST</bcp14> implement <xref target="RFCAAAA" format="default"/>, <xref target="RFCYYYY" format="default"/>, <xref target="RFCDDDD" format="default"/>, and the requirements they
488      include.</t>
489    </section>
490    <section anchor="ch-data" numbered="true" toc="default">
491      <name>Data formats</name>
492      <t>The intent of this specification is to allow each communications
493      event to use the data formats that are best suited for that particular
494      instance, where a format is supported by both sides of the connection.
495      However, a minimum standard is greatly helpful in order to ensure that
496      communication can be achieved. This document specifies a minimum
497      baseline that will be supported by all implementations of this
498      specification, and leaves further codecs to be included at the will of
499      the implementor.</t>
500      <t>WebRTC endpoints that support audio and/or video <bcp14>MUST</bcp14> implement the
501      codecs and profiles required in <xref target="RFC7874" format="default"/> and <xref target="RFC7742" format="default"/>.</t>
502    </section>
503    <section numbered="true" toc="default">
504      <name>Connection management</name>
505      <t>The methods, mechanisms and requirements for setting up, negotiating
506      and tearing down connections is a large subject, and one where it is
507      desirable to have both interoperability and freedom to innovate.</t>
508      <t>The following principles apply:</t>
509      <ol spacing="normal" type="1">
510        <li>The WebRTC media negotiations will be capable of representing the
511          same SDP offer/answer semantics <xref target="RFC3264" format="default"/> that are
512          used in SIP, in such a way that it is possible to build a
513          signaling gateway between SIP and the WebRTC media negotiation.</li>
514        <li>It will be possible to gateway between legacy SIP devices that
515          support ICE and appropriate RTP / SDP mechanisms, codecs and
516          security mechanisms without using a media gateway. A signaling
517          gateway to convert between the signaling on the web side to the SIP
518          signaling may be needed.</li>
519        <li>When an SDP for a new codec is specified, no other standardization
520          should be required for it to be possible to use that in the web
521          browsers. Adding new codecs which might have new SDP parameters should
522          not change the APIs between the browser and JavaScript application. As
523          soon as the browsers support the new codecs, old applications
524          written before the codecs were specified should automatically be
525          able to use the new codecs where appropriate with no changes to the
526          JS applications.</li>
527      </ol>
528      <t>The particular choices made for WebRTC, and their implications
529      for the API offered by a browser implementing WebRTC, are described in
530      <xref target="RFCEEEE" format="default"/>.</t>
531      <t>WebRTC browsers <bcp14>MUST</bcp14> implement <xref target="RFCEEEE" format="default"/>.</t>
532      <t>WebRTC endpoints <bcp14>MUST</bcp14> implement the functions described in that
533      document that relate to the network layer (e.g. Bundle <xref target="I-D.ietf-mmusic-sdp-bundle-negotiation" format="default"/>, RTCP-mux <xref target="RFC5761" format="default"/> and Trickle ICE <xref target="I-D.ietf-ice-trickle" format="default"/>), but do not need to support the API
534      functionality described there.</t>
535    </section>
536    <section numbered="true" toc="default">
537      <name>Presentation and control</name>
538      <t>The most important part of control is the user's control over the
539      browser's interaction with input/output devices and communications
540      channels. It is important that the user have some way of figuring out
541      where his audio, video or texting is being sent, for what purported
542      reason, and what guarantees are made by the parties that form part of
543      this control channel. This is largely a local function between the
544      browser, the underlying operating system and the user interface; this is
545      specified in the peer connection API <xref target="W3C.WD-webrtc-20120209" format="default"/>, and the media capture API <xref target="W3C.WD-mediacapture-streams-20120628" format="default"/>.</t>
546      <t>WebRTC browsers <bcp14>MUST</bcp14> implement these two specifications.</t>
547    </section>
548    <section numbered="true" toc="default">
549      <name>Local system support functions</name>
550      <t>These are characterized by the fact that the quality of these
551      functions strongly influence the user experience, but the exact
552      algorithm does not need coordination. In some cases (for instance echo
553      cancellation, as described below), the overall system definition may
554      need to specify that the overall system needs to have some
555      characteristics for which these facilities are useful, without requiring
556      them to be implemented a certain way.</t>
557      <t>Local functions include echo cancellation, volume control, camera
558      management including focus, zoom, pan/tilt controls (if available), and
559      more.</t>
560      <t>One would want to see certain parts of the system conform to certain
561      properties, for instance:</t>
562      <ul spacing="normal">
563        <li>Echo cancellation should be good enough to achieve the
564          suppression of acoustical feedback loops below a perceptually
565          noticeable level.</li>
566        <li>Privacy concerns <bcp14>MUST</bcp14> be satisfied; for instance, if remote
567          control of camera is offered, the APIs should be available to let
568          the local participant figure out who's controlling the camera, and
569          possibly decide to revoke the permission for camera usage.</li>
570        <li>Automatic gain control, if present, should normalize a speaking
571          voice into a reasonable dB range.</li>
572      </ul>
573      <t>The requirements on WebRTC systems with regard to audio
574      processing are found in <xref target="RFC7874" format="default"/> and includes more
575      guidance about echo cancellation and AGC; the proposed API for control
576      of local devices are found in <xref target="W3C.WD-mediacapture-streams-20120628" format="default"/>.</t>
577      <t>WebRTC endpoints <bcp14>MUST</bcp14> implement the processing functions in <xref target="RFC7874" format="default"/>. (Together with the requirement in <xref target="ch-data" format="default"/>, this means that WebRTC endpoints <bcp14>MUST</bcp14> implement the
578      whole document.)</t>
579    </section>
580    <section anchor="IANA" numbered="true" toc="default">
581      <name>IANA Considerations</name>
582      <t>This document makes no request of IANA.</t>
583      <t>Note to RFC Editor: this section may be removed on publication as an
584      RFC.</t>
585    </section>
586    <section anchor="Security" numbered="true" toc="default">
587      <name>Security Considerations</name>
588      <t>Security of the web-enabled real time communications comes in several
589      pieces:</t>
590      <ul spacing="normal">
591        <li>Security of the components: The browsers, and other servers
592          involved. The most target-rich environment here is probably the
593          browser; the aim here should be that the introduction of these
594          components introduces no additional vulnerability.</li>
595        <li>Security of the communication channels: It should be easy for a
596          participant to reassure himself of the security of his communication
597          - by verifying the crypto parameters of the links he himself
598          participates in, and to get reassurances from the other parties to
599          the communication that they promise that appropriate measures are
600          taken.</li>
601        <li>Security of the partners' identity: verifying that the
602          participants are who they say they are (when positive identification
603          is appropriate), or that their identity cannot be uncovered (when
604          anonymity is a goal of the application).</li>
605      </ul>
606      <t>The security analysis, and the requirements derived from that
607      analysis, is contained in <xref target="RFCYYYY" format="default"/>.</t>
608      <t>It is also important to read the security sections of <xref target="W3C.WD-mediacapture-streams-20120628" format="default"/> and <xref target="W3C.WD-webrtc-20120209" format="default"/>.</t>
609    </section>
610    <section anchor="Acknowledgements" numbered="true" toc="default">
611      <name>Acknowledgements</name>
612      <t>The number of people who have taken part in the discussions
613      surrounding this draft are too numerous to list, or even to identify.
614      The ones below have made special, identifiable contributions; this does
615      not mean that others' contributions are less important.</t>
616      <t>Thanks to Cary Bran, Cullen Jennings, Colin Perkins, Magnus
617      Westerlund and Joerg Ott, who offered technical contributions on various
618      versions of the draft.</t>
619      <t>Thanks to Jonathan Rosenberg, Matthew Kaufman and others at Skype for
620      the ASCII drawings in <xref target="Intro"/>.</t>
621      <t>Thanks to Alissa Cooper, Bjoern Hoehrmann, Colin Perkins,
622      Colton Shields, Eric Rescorla, Heath Matlock, Henry Sinnreich,
623      Justin Uberti, Keith Drage, Magnus Westerlund, Olle E. Johansson,
624      Sean Turner and Simon Leinen for document review.</t>
625    </section>
626  </middle>
627  <back>
628    <references>
629      <name>References</name>
630      <references>
631        <name>Normative References</name>
632
633<reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml">
634<front>
635<title>Key words for use in RFCs to Indicate Requirement Levels</title>
636<author initials="S." surname="Bradner" fullname="S. Bradner"><organization/></author>
637<date year="1997" month="March"/>
638<abstract><t>In many standards track documents several words are used to signify the requirements in the specification.  These words are often capitalized. This document defines these words as they should be interpreted in IETF documents.  This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t></abstract>
639</front>
640<seriesInfo name="BCP" value="14"/>
641<seriesInfo name="RFC" value="2119"/>
642<seriesInfo name="DOI" value="10.17487/RFC2119"/>
643</reference>
644<reference anchor="RFC3264" target="https://www.rfc-editor.org/info/rfc3264" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3264.xml">
645<front>
646<title>An Offer/Answer Model with Session Description Protocol (SDP)</title>
647<author initials="J." surname="Rosenberg" fullname="J. Rosenberg"><organization/></author>
648<author initials="H." surname="Schulzrinne" fullname="H. Schulzrinne"><organization/></author>
649<date year="2002" month="June"/>
650<abstract><t>This document defines a mechanism by which two entities can make use of the Session Description Protocol (SDP) to arrive at a common view of a multimedia session between them.  In the model, one participant offers the other a description of the desired session from their perspective, and the other participant answers with the desired session from their perspective.  This offer/answer model is most useful in unicast sessions where information from both participants is needed for the complete view of the session.  The offer/answer model is used by protocols like the Session Initiation Protocol (SIP).  [STANDARDS-TRACK]</t></abstract>
651</front>
652<seriesInfo name="RFC" value="3264"/>
653<seriesInfo name="DOI" value="10.17487/RFC3264"/>
654</reference>
655<reference anchor="RFC3550" target="https://www.rfc-editor.org/info/rfc3550" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3550.xml">
656<front>
657<title>RTP: A Transport Protocol for Real-Time Applications</title>
658<author initials="H." surname="Schulzrinne" fullname="H. Schulzrinne"><organization/></author>
659<author initials="S." surname="Casner" fullname="S. Casner"><organization/></author>
660<author initials="R." surname="Frederick" fullname="R. Frederick"><organization/></author>
661<author initials="V." surname="Jacobson" fullname="V. Jacobson"><organization/></author>
662<date year="2003" month="July"/>
663<abstract><t>This memorandum describes RTP, the real-time transport protocol.  RTP provides end-to-end network transport functions suitable for applications transmitting real-time data, such as audio, video or simulation data, over multicast or unicast network services.  RTP does not address resource reservation and does not guarantee quality-of- service for real-time services.  The data transport is augmented by a control protocol (RTCP) to allow monitoring of the data delivery in a manner scalable to large multicast networks, and to provide minimal control and identification functionality.  RTP and RTCP are designed to be independent of the underlying transport and network layers.  The protocol supports the use of RTP-level translators and mixers. Most of the text in this memorandum is identical to RFC 1889 which it obsoletes.  There are no changes in the packet formats on the wire, only changes to the rules and algorithms governing how the protocol is used. The biggest change is an enhancement to the scalable timer algorithm for calculating when to send RTCP packets in order to minimize transmission in excess of the intended rate when many participants join a session simultaneously.  [STANDARDS-TRACK]</t></abstract>
664</front>
665<seriesInfo name="STD" value="64"/>
666<seriesInfo name="RFC" value="3550"/>
667<seriesInfo name="DOI" value="10.17487/RFC3550"/>
668</reference>
669<reference anchor="RFC3711" target="https://www.rfc-editor.org/info/rfc3711" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3711.xml">
670<front>
671<title>The Secure Real-time Transport Protocol (SRTP)</title>
672<author initials="M." surname="Baugher" fullname="M. Baugher"><organization/></author>
673<author initials="D." surname="McGrew" fullname="D. McGrew"><organization/></author>
674<author initials="M." surname="Naslund" fullname="M. Naslund"><organization/></author>
675<author initials="E." surname="Carrara" fullname="E. Carrara"><organization/></author>
676<author initials="K." surname="Norrman" fullname="K. Norrman"><organization/></author>
677<date year="2004" month="March"/>
678<abstract><t>This document describes the Secure Real-time Transport Protocol (SRTP), a profile of the Real-time Transport Protocol (RTP), which can provide confidentiality, message authentication, and replay protection to the RTP traffic and to the control traffic for RTP, the Real-time Transport Control Protocol (RTCP).   [STANDARDS-TRACK]</t></abstract>
679</front>
680<seriesInfo name="RFC" value="3711"/>
681<seriesInfo name="DOI" value="10.17487/RFC3711"/>
682</reference>
683<reference anchor="RFC5245" target="https://www.rfc-editor.org/info/rfc5245" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5245.xml">
684<front>
685<title>Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols</title>
686<author initials="J." surname="Rosenberg" fullname="J. Rosenberg"><organization/></author>
687<date year="2010" month="April"/>
688<abstract><t>This document describes a protocol for Network Address Translator (NAT) traversal for UDP-based multimedia sessions established with the offer/answer model.  This protocol is called Interactive Connectivity Establishment (ICE).  ICE makes use of the Session Traversal Utilities for NAT (STUN) protocol and its extension, Traversal Using Relay NAT (TURN).  ICE can be used by any protocol utilizing the offer/answer model, such as the Session Initiation Protocol (SIP).  [STANDARDS-TRACK]</t></abstract>
689</front>
690<seriesInfo name="RFC" value="5245"/>
691<seriesInfo name="DOI" value="10.17487/RFC5245"/>
692</reference>
693<reference anchor="RFC7742" target="https://www.rfc-editor.org/info/rfc7742" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.7742.xml">
694<front>
695<title>WebRTC Video Processing and Codec Requirements</title>
696<author initials="A.B." surname="Roach" fullname="A.B. Roach"><organization/></author>
697<date year="2016" month="March"/>
698<abstract><t>This specification provides the requirements and considerations for WebRTC applications to send and receive video across a network.  It specifies the video processing that is required as well as video codecs and their parameters.</t></abstract>
699</front>
700<seriesInfo name="RFC" value="7742"/>
701<seriesInfo name="DOI" value="10.17487/RFC7742"/>
702</reference>
703<reference anchor="RFC7874" target="https://www.rfc-editor.org/info/rfc7874" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.7874.xml">
704<front>
705<title>WebRTC Audio Codec and Processing Requirements</title>
706<author initials="JM." surname="Valin" fullname="JM. Valin"><organization/></author>
707<author initials="C." surname="Bran" fullname="C. Bran"><organization/></author>
708<date year="2016" month="May"/>
709<abstract><t>This document outlines the audio codec and processing requirements for WebRTC endpoints.</t></abstract>
710</front>
711<seriesInfo name="RFC" value="7874"/>
712<seriesInfo name="DOI" value="10.17487/RFC7874"/>
713</reference>
714
715   
716    
717        <reference anchor="RFCYYYY" target="https://www.rfc-editor.org/info/rfcYYYY">
718          <front>
719            <title>Security Considerations for WebRTC</title>
720            <seriesInfo name="RFC" value="YYYY"/>
721            <seriesInfo name="DOI" value="10.17487/RFCYYYY"/>
722            <author initials="E" surname="Rescorla" fullname="Eric Rescorla">
723              <organization/>
724            </author>
725            <date month="August" year="2019"/>
726            <abstract>
727              <t>WebRTC is a protocol suite for use with real-time applications that can be deployed in browsers - "real time communication on the Web". This document defines the WebRTC threat model and analyzes the security threats of WebRTC in that model.</t>
728            </abstract>
729          </front>
730        </reference>
731
732        <reference anchor="RFCZZZZ" target="https://www.rfc-editor.org/info/rfcZZZZ">
733          <front>
734            <title>Transports for WebRTC</title>
735            <seriesInfo name="RFC" value="ZZZZ"/>
736            <seriesInfo name="DOI" value="10.17487/RFCZZZZ"/>
737            <author initials="H" surname="Alvestrand" fullname="Harald Alvestrand">
738              <organization/>
739            </author>
740            <date month="August" year="2019"/>
741            <abstract>
742              <t>This document describes the data transport protocols used by WebRTC, including the protocols used for interaction with intermediate boxes such as firewalls, relays and NAT boxes.</t>
743            </abstract>
744          </front>
745        </reference>
746
747        <reference anchor="RFCAAAA" target="https://www.rfc-editor.org/info/rfcAAAA">
748          <front>
749            <title>Web Real-Time Communication (WebRTC): Media Transport and Use of RTP</title>
750            <seriesInfo name="RFC" value="AAAA"/>
751            <seriesInfo name="DOI" value="10.17487/RFCAAAA"/>
752            <author initials="C" surname="Perkins" fullname="Colin Perkins">
753              <organization/>
754            </author>
755            <author initials="M" surname="Westerlund" fullname="Magnus Westerlund">
756              <organization/>
757            </author>
758            <author initials="J" surname="Ott" fullname="Joerg Ott">
759              <organization/>
760            </author>
761            <date month="August" year="2019"/>
762            <abstract>
763              <t>The Web Real-Time Communication (WebRTC) framework provides support for direct interactive rich communication using audio, video, text, collaboration, games, etc. between two peers' web-browsers.  This memo describes the media transport aspects of the WebRTC framework. It specifies how the Real-time Transport Protocol (RTP) is used in the WebRTC context, and gives requirements for which RTP features, profiles, and extensions need to be supported.</t>
764            </abstract>
765          </front>
766        </reference>
767
768        <reference anchor="RFCBBBB" target="https://www.rfc-editor.org/info/rfcBBBB">
769          <front>
770            <title>WebRTC Data Channels</title>
771            <seriesInfo name="RFC" value="BBBB"/>
772            <seriesInfo name="DOI" value="10.17487/RFCBBBB"/>
773            <author initials="R" surname="Jesup" fullname="Randell Jesup">
774              <organization/>
775            </author>
776            <author initials="S" surname="Loreto" fullname="Salvatore Loreto">
777              <organization/>
778            </author>
779            <author initials="M" surname="Tuexen" fullname="Michael Tuexen">
780              <organization/>
781            </author>
782            <date month="August" year="2019"/>
783            <abstract>
784              <t>The WebRTC framework specifies protocol support for direct interactive rich communication using audio, video, and data between two peers' web-browsers.  This document specifies the non-media data transport aspects of the WebRTC framework.  It provides an architectural overview of how the Stream Control Transmission Protocol (SCTP) is used in the WebRTC context as a generic transport service allowing WEB-browsers to exchange generic data from peer to peer.</t>
785            </abstract>
786          </front>
787        </reference>
788
789        <reference anchor="RFCCCCC" target="https://www.rfc-editor.org/info/rfcCCCC">
790          <front>
791            <title>WebRTC Data Channel Establishment Protocol</title>
792             <seriesInfo name="RFC" value="CCCC"/>
793            <seriesInfo name="DOI" value="10.17487/RFCCCCC"/>
794            <author initials="R" surname="Jesup" fullname="Randell Jesup">
795              <organization/>
796            </author>
797            <author initials="S" surname="Loreto" fullname="Salvatore Loreto">
798              <organization/>
799            </author>
800            <author initials="M" surname="Tuexen" fullname="Michael Tuexen">
801              <organization/>
802            </author>
803            <date month="August" year="2019"/>
804            <abstract>
805              <t>The WebRTC framework specifies protocol support for direct interactive rich communication using audio, video, and data between two peers' web-browsers.  This document specifies a simple protocol for establishing symmetric Data Channels between the peers.  It uses a two way handshake and allows sending of user data without waiting for the handshake to complete.</t>
806            </abstract>
807          </front>
808        </reference>
809
810        <reference anchor="RFCDDDD" target="https://www.rfc-editor.org/info/rfcDDDD">
811          <front>
812            <title>WebRTC Security Architecture</title>
813            <seriesInfo name="RFC" value="DDDD"/>
814            <seriesInfo name="DOI" value="10.17487/RFCDDDD"/>
815            <author initials="E" surname="Rescorla" fullname="Eric Rescorla">
816              <organization/>
817            </author>
818            <date month="August" year="2019"/>
819            <abstract>
820              <t>This document defines the security architecture for WebRTC, a protocol suite intended for use with real-time applications that can be deployed in browsers - "real time communication on the Web".</t>
821            </abstract>
822          </front>
823        </reference>
824
825        <reference anchor="RFCEEEE" target="https://www.rfc-editor.org/info/rfcEEEE">
826          <front>
827            <title>JavaScript Session Establishment Protocol</title>
828            <seriesInfo name="RFC" value="EEEE"/>
829            <seriesInfo name="DOI" value="10.17487/RFCEEEE"/>
830            <author initials="J" surname="Uberti" fullname="Justin Uberti">
831              <organization/>
832            </author>
833            <author initials="C" surname="Jennings" fullname="Cullen Jennings">
834              <organization/>
835            </author>
836            <author initials="E" surname="Rescorla" fullname="Eric Rescorla">
837              <organization/>
838            </author>
839            <date month="August" year="2019"/>
840            <abstract>
841              <t>This document describes the mechanisms for allowing a JavaScript application to control the signaling plane of a multimedia session via the interface specified in the W3C RTCPeerConnection API, and discusses how this relates to existing signaling protocols.</t>
842            </abstract>
843          </front>
844        </reference>
845
846
847
848        <reference anchor="W3C.WD-webrtc-20120209" target="http://www.w3.org/TR/2012/WD-webrtc-20120209" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml4/reference.W3C.WD-webrtc-20120209.xml">
849          <front>
850            <title>WebRTC 1.0: Real-time Communication Between Browsers</title>
851            <seriesInfo name="World Wide Web Consortium WD" value="WD-webrtc-20120209"/>
852            <author initials="A." surname="Bergkvist" fullname="Adam Bergkvist">
853              <organization/>
854            </author>
855            <author initials="D." surname="Burnett" fullname="Daniel C. Burnett">
856              <organization/>
857            </author>
858            <author initials="C." surname="Jennings" fullname="Cullen Jennings">
859              <organization/>
860            </author>
861            <author initials="A." surname="Narayanan" fullname="Anant Narayanan">
862              <organization/>
863            </author>
864            <date month="February" year="2012"/>
865          </front>
866        </reference>
867        <reference anchor="W3C.WD-mediacapture-streams-20120628" target="http://www.w3.org/TR/2012/WD-mediacapture-streams-20120628" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml4/reference.W3C.WD-mediacapture-streams-20120628.xml">
868          <front>
869            <title>Media Capture and Streams</title>
870            <seriesInfo name="World Wide Web Consortium WD" value="WD-mediacapture-streams-20120628"/>
871            <author initials="D." surname="Burnett" fullname="Daniel C. Burnett">
872              <organization/>
873            </author>
874            <author initials="A." surname="Narayanan" fullname="Anant Narayanan">
875              <organization/>
876            </author>
877            <date month="June" year="2012"/>
878          </front>
879        </reference>
880      </references>
881      <references>
882        <name>Informative References</name>
883
884<reference anchor="RFC3261" target="https://www.rfc-editor.org/info/rfc3261" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3261.xml">
885<front>
886<title>SIP: Session Initiation Protocol</title>
887<author initials="J." surname="Rosenberg" fullname="J. Rosenberg"><organization/></author>
888<author initials="H." surname="Schulzrinne" fullname="H. Schulzrinne"><organization/></author>
889<author initials="G." surname="Camarillo" fullname="G. Camarillo"><organization/></author>
890<author initials="A." surname="Johnston" fullname="A. Johnston"><organization/></author>
891<author initials="J." surname="Peterson" fullname="J. Peterson"><organization/></author>
892<author initials="R." surname="Sparks" fullname="R. Sparks"><organization/></author>
893<author initials="M." surname="Handley" fullname="M. Handley"><organization/></author>
894<author initials="E." surname="Schooler" fullname="E. Schooler"><organization/></author>
895<date year="2002" month="June"/>
896<abstract><t>This document describes Session Initiation Protocol (SIP), an application-layer control (signaling) protocol for creating, modifying, and terminating sessions with one or more participants.  These sessions include Internet telephone calls, multimedia distribution, and multimedia conferences.  [STANDARDS-TRACK]</t></abstract>
897</front>
898<seriesInfo name="RFC" value="3261"/>
899<seriesInfo name="DOI" value="10.17487/RFC3261"/>
900</reference>
901<reference anchor="RFC3361" target="https://www.rfc-editor.org/info/rfc3361" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3361.xml">
902<front>
903<title>Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation Protocol (SIP) Servers</title>
904<author initials="H." surname="Schulzrinne" fullname="H. Schulzrinne"><organization/></author>
905<date year="2002" month="August"/>
906</front>
907<seriesInfo name="RFC" value="3361"/>
908<seriesInfo name="DOI" value="10.17487/RFC3361"/>
909</reference>
910<reference anchor="RFC3935" target="https://www.rfc-editor.org/info/rfc3935" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3935.xml">
911<front>
912<title>A Mission Statement for the IETF</title>
913<author initials="H." surname="Alvestrand" fullname="H. Alvestrand"><organization/></author>
914<date year="2004" month="October"/>
915<abstract><t>This memo gives a mission statement for the IETF, tries to define the terms used in the statement sufficiently to make the mission statement understandable and useful, argues why the IETF needs a mission statement, and tries to capture some of the debate that led to this point.  This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t></abstract>
916</front>
917<seriesInfo name="BCP" value="95"/>
918<seriesInfo name="RFC" value="3935"/>
919<seriesInfo name="DOI" value="10.17487/RFC3935"/>
920</reference>
921<reference anchor="RFC5761" target="https://www.rfc-editor.org/info/rfc5761" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5761.xml">
922<front>
923<title>Multiplexing RTP Data and Control Packets on a Single Port</title>
924<author initials="C." surname="Perkins" fullname="C. Perkins"><organization/></author>
925<author initials="M." surname="Westerlund" fullname="M. Westerlund"><organization/></author>
926<date year="2010" month="April"/>
927<abstract><t>This memo discusses issues that arise when multiplexing RTP data packets and RTP Control Protocol (RTCP) packets on a single UDP port. It updates RFC 3550 and RFC 3551 to describe when such multiplexing is and is not appropriate, and it explains how the Session Description Protocol (SDP) can be used to signal multiplexed sessions.  [STANDARDS-TRACK]</t></abstract>
928</front>
929<seriesInfo name="RFC" value="5761"/>
930<seriesInfo name="DOI" value="10.17487/RFC5761"/>
931</reference>
932<reference anchor="RFC6120" target="https://www.rfc-editor.org/info/rfc6120" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.6120.xml">
933<front>
934<title>Extensible Messaging and Presence Protocol (XMPP): Core</title>
935<author initials="P." surname="Saint-Andre" fullname="P. Saint-Andre"><organization/></author>
936<date year="2011" month="March"/>
937<abstract><t>The Extensible Messaging and Presence Protocol (XMPP) is an application profile of the Extensible Markup Language (XML) that enables the near-real-time exchange of structured yet extensible data between any two or more network entities.  This document defines XMPP's core protocol methods: setup and teardown of XML streams, channel encryption, authentication, error handling, and communication primitives for messaging, network availability ("presence"), and request-response interactions.  This document obsoletes RFC 3920.  [STANDARDS-TRACK]</t></abstract>
938</front>
939<seriesInfo name="RFC" value="6120"/>
940<seriesInfo name="DOI" value="10.17487/RFC6120"/>
941</reference>
942<reference anchor="RFC7478" target="https://www.rfc-editor.org/info/rfc7478" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.7478.xml">
943<front>
944<title>Web Real-Time Communication Use Cases and Requirements</title>
945<author initials="C." surname="Holmberg" fullname="C. Holmberg"><organization/></author>
946<author initials="S." surname="Hakansson" fullname="S. Hakansson"><organization/></author>
947<author initials="G." surname="Eriksson" fullname="G. Eriksson"><organization/></author>
948<date year="2015" month="March"/>
949<abstract><t>This document describes web-based real-time communication use cases. Requirements on the browser functionality are derived from the use cases.</t><t>This document was developed in an initial phase of the work with rather minor updates at later stages.  It has not really served as a tool in deciding features or scope for the WG's efforts so far.  It is being published to record the early conclusions of the WG.  It will not be used as a set of rigid guidelines that specifications and implementations will be held to in the future.</t></abstract>
950</front>
951<seriesInfo name="RFC" value="7478"/>
952<seriesInfo name="DOI" value="10.17487/RFC7478"/>
953</reference>
954<reference anchor="RFC8155" target="https://www.rfc-editor.org/info/rfc8155" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8155.xml">
955<front>
956<title>Traversal Using Relays around NAT (TURN) Server Auto Discovery</title>
957<author initials="P." surname="Patil" fullname="P. Patil"><organization/></author>
958<author initials="T." surname="Reddy" fullname="T. Reddy"><organization/></author>
959<author initials="D." surname="Wing" fullname="D. Wing"><organization/></author>
960<date year="2017" month="April"/>
961<abstract><t>Current Traversal Using Relays around NAT (TURN) server discovery mechanisms are relatively static and limited to explicit configuration.  These are usually under the administrative control of the application or TURN service provider, and not the enterprise, ISP, or the network in which the client is located.  Enterprises and ISPs wishing to provide their own TURN servers need auto-discovery mechanisms that a TURN client could use with minimal or no configuration.  This document describes three such mechanisms for TURN server discovery.</t><t>This document updates RFC 5766 to relax the requirement for mutual authentication in certain cases.</t></abstract>
962</front>
963<seriesInfo name="RFC" value="8155"/>
964<seriesInfo name="DOI" value="10.17487/RFC8155"/>
965</reference>
966<reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml">
967<front>
968<title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
969<author initials="B." surname="Leiba" fullname="B. Leiba"><organization/></author>
970<date year="2017" month="May"/>
971<abstract><t>RFC 2119 specifies common key words that may be used in protocol  specifications.  This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the  defined special meanings.</t></abstract>
972</front>
973<seriesInfo name="BCP" value="14"/>
974<seriesInfo name="RFC" value="8174"/>
975<seriesInfo name="DOI" value="10.17487/RFC8174"/>
976</reference>
977
978        
979        <reference anchor="W3C.WD-html5-20110525" target="http://www.w3.org/TR/2011/WD-html5-20110525" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml4/reference.W3C.WD-html5-20110525.xml">
980          <front>
981            <title>HTML5</title>
982            <seriesInfo name="World Wide Web Consortium LastCall," value="WD-html5-20110525"/>
983            <author initials="I." surname="Hickson" fullname="Ian Hickson">
984              <organization/>
985            </author>
986            <date month="May" year="2011"/>
987          </front>
988        </reference>
989        <reference anchor="I-D.ietf-ice-trickle">
990          <front>
991            <title>Trickle ICE: Incremental Provisioning of Candidates for the Interactive Connectivity Establishment (ICE) Protocol</title>
992            <seriesInfo name="Work in Progress," value="draft-ietf-ice-trickle-21"/>
993            <author initials="E" surname="Ivov" fullname="Emil Ivov">
994              <organization/>
995            </author>
996            <author initials="E" surname="Rescorla" fullname="Eric Rescorla">
997              <organization/>
998            </author>
999            <author initials="J" surname="Uberti" fullname="Justin Uberti">
1000              <organization/>
1001            </author>
1002            <author initials="P" surname="Saint-Andre" fullname="Peter Saint-Andre">
1003              <organization/>
1004            </author>
1005            <date month="April" year="2018"/>
1006            <abstract>
1007              <t>This document describes "Trickle ICE", an extension to the Interactive Connectivity Establishment (ICE) protocol that enables ICE agents to begin connectivity checks while they are still gathering candidates, by incrementally exchanging candidates over time instead of all at once.  This method can considerably accelerate the process of establishing a communication session.</t>
1008            </abstract>
1009          </front>
1010        </reference>
1011
1012        <reference anchor="I-D.ietf-mmusic-sdp-bundle-negotiation">
1013          <front>
1014            <title>Negotiating Media Multiplexing Using the Session Description Protocol (SDP)</title>
1015            <seriesInfo name="Work in Progress," value="draft-ietf-mmusic-sdp-bundle-negotiation-54"/>
1016            <author initials="C" surname="Holmberg" fullname="Christer Holmberg">
1017              <organization/>
1018            </author>
1019            <author initials="H" surname="Alvestrand" fullname="Harald Alvestrand">
1020              <organization/>
1021            </author>
1022            <author initials="C" surname="Jennings" fullname="Cullen Jennings">
1023              <organization/>
1024            </author>
1025            <date month="December" year="2018"/>
1026            <abstract>
1027              <t>This specification defines a new Session Description Protocol (SDP) Grouping Framework extension, 'BUNDLE'.  The extension can be used with the SDP Offer/Answer mechanism to negotiate the usage of a single transport (5-tuple) for sending and receiving media described by multiple SDP media descriptions ("m=" sections).  Such transport is referred to as a BUNDLE transport, and the media is referred to as bundled media.  The "m=" sections that use the BUNDLE transport form a BUNDLE group.  This specification updates RFC 3264, to also allow assigning a zero port value to a "m=" section in cases where the media described by the "m=" section is not disabled or rejected.  This specification updates RFC 5888, to also allow an SDP 'group' attribute to contain an identification-tag that identifies a "m=" section with the port set to zero.  This specification defines a new RTP Control Protocol (RTCP) source description (SDES) item and a new RTP header extension that can be used to correlate bundled RTP/RTCP packets with their appropriate "m=" section.  This specification updates RFC 7941, by adding an exception, for the MID RTP header extension, to the requirement regarding protection of an SDES RTP header extension carrying an SDES item for the MID RTP header extension.</t>
1028            </abstract>
1029          </front>
1030        </reference>
1031
1032        <reference anchor="I-D.ietf-rtcweb-gateways">
1033          <front>
1034            <title>WebRTC Gateways</title>
1035            <seriesInfo name="Work in Progress," value="draft-ietf-rtcweb-gateways-02"/>
1036            <author initials="H" surname="Alvestrand" fullname="Harald T. Alvestrand">
1037              <organization/>
1038            </author>
1039            <author initials="U" surname="Rauschenbach" fullname="Uwe Rauschenbach">
1040              <organization/>
1041            </author>
1042            <date month="January" year="2016"/>
1043            <abstract>
1044              <t>This document describes interoperability considerations for a class of WebRTC-compatible endpoints called "WebRTC gateways", which interconnect between WebRTC endpoints and devices that are not WebRTC endpoints.</t>
1045            </abstract>
1046          </front>
1047        </reference>
1048
1049        <reference anchor="I-D.ietf-tsvwg-rtcweb-qos">
1050          <front>
1051            <title>DSCP Packet Markings for WebRTC QoS</title>
1052            <seriesInfo name="Work in Progress," value="draft-ietf-tsvwg-rtcweb-qos-18"/>
1053            <author initials="P" surname="Jones" fullname="Paul Jones">
1054              <organization/>
1055            </author>
1056            <author initials="S" surname="Dhesikan" fullname="Subha Dhesikan">
1057              <organization/>
1058            </author>
1059            <author initials="C" surname="Jennings" fullname="Cullen Jennings">
1060              <organization/>
1061            </author>
1062            <author initials="D" surname="Druta" fullname="Dan Druta">
1063              <organization/>
1064            </author>
1065            <date month="August" year="2016"/>
1066            <abstract>
1067              <t>Many networks, such as service provider and enterprise networks, can provide different forwarding treatments for individual packets based on Differentiated Services Code Point (DSCP) values on a per-hop basis.  This document provides the recommended DSCP values for web browsers to use for various classes of WebRTC traffic.</t>
1068            </abstract>
1069          </front>
1070        </reference>
1071
1072        <reference anchor="XEP-0166" target="http://xmpp.org/extensions/xep-0166.html">
1073          <front>
1074            <title>Jingle</title>
1075            <seriesInfo name="XSF XEP" value="0166"/>
1076            <author fullname="Scott Ludwig" initials="S." surname="Ludwig">
1077              <organization/>
1078              <address>
1079                <email>scottlu@google.com</email>
1080              </address>
1081            </author>
1082            <author fullname="Joe Beda" initials="J." surname="Beda">
1083              <organization/>
1084              <address>
1085                <email>jbeda@google.com</email>
1086              </address>
1087            </author>
1088            <author fullname="Peter Saint-Andre" initials="P." surname="Saint-Andre">
1089              <organization/>
1090              <address>
1091                <email>stpeter@jabber.org</email>
1092              </address>
1093            </author>
1094            <author fullname="Robert McQueen" initials="R." surname="McQueen">
1095              <organization/>
1096              <address>
1097                <email>robert.mcqueen@collabora.co.uk</email>
1098              </address>
1099            </author>
1100            <author fullname="Sean Egan" initials="S." surname="Egan">
1101              <organization/>
1102              <address>
1103                <email>seanegan@google.com</email>
1104              </address>
1105            </author>
1106            <author fullname="Joe Hildebrand" initials="J." surname="Hildebrand">
1107              <organization/>
1108              <address>
1109                <email>jhildebr@cisco.com</email>
1110              </address>
1111            </author>
1112            <date month="June" year="2007"/>
1113          </front>
1114        </reference>
1115
1116        <reference anchor="XEP-0124" target="http://xmpp.org/extensions/xep-0124.html">
1117          <front>
1118            <title>BOSH</title>
1119            <seriesInfo name="XSF XEP" value="0124"/>
1120            <author fullname="Ian Paterson" initials="I." surname="Paterson">
1121              <organization/>
1122              <address>
1123                <email>ian.paterson@clientside.co.uk</email>
1124              </address>
1125            </author>
1126            <author fullname="Dave Smith" initials="D." surname="Smith">
1127              <organization/>
1128              <address>
1129                <email>dizzyd@jabber.org</email>
1130              </address>
1131            </author>
1132            <author fullname="Peter Saint-Andre" initials="P." surname="Saint-Andre">
1133              <organization/>
1134              <address>
1135                <email>stpeter@jabber.org</email>
1136              </address>
1137            </author>
1138            <author fullname="Jack Moffitt" initials="J." surname="Moffitt">
1139              <organization/>
1140              <address>
1141                <email>jack@chesspark.com</email>
1142              </address>
1143            </author>
1144            <author fullname="Lance Stout" initials="L." surname="Stout">
1145              <organization/>
1146              <address>
1147                <email>lance@andyet.com</email>
1148              </address>
1149            </author>
1150            <author fullname="Winifried Tilanus" initials="W." surname="Tilanus">
1151              <organization/>
1152              <address>
1153                <email>winfried@tilanus.com</email>
1154              </address>
1155            </author>
1156            <date month="November" year="2016"/>
1157          </front>
1158        </reference>
1159      </references>
1160    </references>
1161  </back>
1162</rfc>
1<reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml">
2<front>
3<title>Key words for use in RFCs to Indicate Requirement Levels</title>
4<author initials="S." surname="Bradner" fullname="S. Bradner"><organization/></author>
5<date year="1997" month="March"/>
6<abstract><t>In many standards track documents several words are used to signify the requirements in the specification.  These words are often capitalized. This document defines these words as they should be interpreted in IETF documents.  This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t></abstract>
7</front>
8<seriesInfo name="BCP" value="14"/>
9<seriesInfo name="RFC" value="2119"/>
10<seriesInfo name="DOI" value="10.17487/RFC2119"/>
11</reference>
1<reference anchor="RFC3264" target="https://www.rfc-editor.org/info/rfc3264" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3264.xml">
2<front>
3<title>An Offer/Answer Model with Session Description Protocol (SDP)</title>
4<author initials="J." surname="Rosenberg" fullname="J. Rosenberg"><organization/></author>
5<author initials="H." surname="Schulzrinne" fullname="H. Schulzrinne"><organization/></author>
6<date year="2002" month="June"/>
7<abstract><t>This document defines a mechanism by which two entities can make use of the Session Description Protocol (SDP) to arrive at a common view of a multimedia session between them.  In the model, one participant offers the other a description of the desired session from their perspective, and the other participant answers with the desired session from their perspective.  This offer/answer model is most useful in unicast sessions where information from both participants is needed for the complete view of the session.  The offer/answer model is used by protocols like the Session Initiation Protocol (SIP).  [STANDARDS-TRACK]</t></abstract>
8</front>
9<seriesInfo name="RFC" value="3264"/>
10<seriesInfo name="DOI" value="10.17487/RFC3264"/>
11</reference>
1<reference anchor="RFC3550" target="https://www.rfc-editor.org/info/rfc3550" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3550.xml">
2<front>
3<title>RTP: A Transport Protocol for Real-Time Applications</title>
4<author initials="H." surname="Schulzrinne" fullname="H. Schulzrinne"><organization/></author>
5<author initials="S." surname="Casner" fullname="S. Casner"><organization/></author>
6<author initials="R." surname="Frederick" fullname="R. Frederick"><organization/></author>
7<author initials="V." surname="Jacobson" fullname="V. Jacobson"><organization/></author>
8<date year="2003" month="July"/>
9<abstract><t>This memorandum describes RTP, the real-time transport protocol.  RTP provides end-to-end network transport functions suitable for applications transmitting real-time data, such as audio, video or simulation data, over multicast or unicast network services.  RTP does not address resource reservation and does not guarantee quality-of- service for real-time services.  The data transport is augmented by a control protocol (RTCP) to allow monitoring of the data delivery in a manner scalable to large multicast networks, and to provide minimal control and identification functionality.  RTP and RTCP are designed to be independent of the underlying transport and network layers.  The protocol supports the use of RTP-level translators and mixers. Most of the text in this memorandum is identical to RFC 1889 which it obsoletes.  There are no changes in the packet formats on the wire, only changes to the rules and algorithms governing how the protocol is used. The biggest change is an enhancement to the scalable timer algorithm for calculating when to send RTCP packets in order to minimize transmission in excess of the intended rate when many participants join a session simultaneously.  [STANDARDS-TRACK]</t></abstract>
10</front>
11<seriesInfo name="STD" value="64"/>
12<seriesInfo name="RFC" value="3550"/>
13<seriesInfo name="DOI" value="10.17487/RFC3550"/>
14</reference>
1<reference anchor="RFC3711" target="https://www.rfc-editor.org/info/rfc3711" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3711.xml">
2<front>
3<title>The Secure Real-time Transport Protocol (SRTP)</title>
4<author initials="M." surname="Baugher" fullname="M. Baugher"><organization/></author>
5<author initials="D." surname="McGrew" fullname="D. McGrew"><organization/></author>
6<author initials="M." surname="Naslund" fullname="M. Naslund"><organization/></author>
7<author initials="E." surname="Carrara" fullname="E. Carrara"><organization/></author>
8<author initials="K." surname="Norrman" fullname="K. Norrman"><organization/></author>
9<date year="2004" month="March"/>
10<abstract><t>This document describes the Secure Real-time Transport Protocol (SRTP), a profile of the Real-time Transport Protocol (RTP), which can provide confidentiality, message authentication, and replay protection to the RTP traffic and to the control traffic for RTP, the Real-time Transport Control Protocol (RTCP).   [STANDARDS-TRACK]</t></abstract>
11</front>
12<seriesInfo name="RFC" value="3711"/>
13<seriesInfo name="DOI" value="10.17487/RFC3711"/>
14</reference>
1<?xml version='1.0' encoding='UTF-8'?>
2
3<reference  anchor='RFC5245' target='https://www.rfc-editor.org/info/rfc5245'>
4<front>
5<title>Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols</title>
6<author initials='J.' surname='Rosenberg' fullname='J. Rosenberg'><organization /></author>
7<date year='2010' month='April' />
8<abstract><t>This document describes a protocol for Network Address Translator (NAT) traversal for UDP-based multimedia sessions established with the offer/answer model.  This protocol is called Interactive Connectivity Establishment (ICE).  ICE makes use of the Session Traversal Utilities for NAT (STUN) protocol and its extension, Traversal Using Relay NAT (TURN).  ICE can be used by any protocol utilizing the offer/answer model, such as the Session Initiation Protocol (SIP).  [STANDARDS-TRACK]</t></abstract>
9</front>
10<seriesInfo name='RFC' value='5245'/>
11<seriesInfo name='DOI' value='10.17487/RFC5245'/>
12</reference>
1<?xml version='1.0' encoding='UTF-8'?>
2
3<reference  anchor='RFC7742' target='https://www.rfc-editor.org/info/rfc7742'>
4<front>
5<title>WebRTC Video Processing and Codec Requirements</title>
6<author initials='A.B.' surname='Roach' fullname='A.B. Roach'><organization /></author>
7<date year='2016' month='March' />
8<abstract><t>This specification provides the requirements and considerations for WebRTC applications to send and receive video across a network.  It specifies the video processing that is required as well as video codecs and their parameters.</t></abstract>
9</front>
10<seriesInfo name='RFC' value='7742'/>
11<seriesInfo name='DOI' value='10.17487/RFC7742'/>
12</reference>
1<?xml version='1.0' encoding='UTF-8'?>
2
3<reference  anchor='RFC7874' target='https://www.rfc-editor.org/info/rfc7874'>
4<front>
5<title>WebRTC Audio Codec and Processing Requirements</title>
6<author initials='JM.' surname='Valin' fullname='JM. Valin'><organization /></author>
7<author initials='C.' surname='Bran' fullname='C. Bran'><organization /></author>
8<date year='2016' month='May' />
9<abstract><t>This document outlines the audio codec and processing requirements for WebRTC endpoints.</t></abstract>
10</front>
11<seriesInfo name='RFC' value='7874'/>
12<seriesInfo name='DOI' value='10.17487/RFC7874'/>
13</reference>
1<?xml version='1.0' encoding='UTF-8'?>
2
3<reference anchor='W3C.WD-webrtc-20120209'
4           target='http://www.w3.org/TR/2012/WD-webrtc-20120209'>
5<front>
6<title>WebRTC 1.0: Real-time Communication Between Browsers</title>
7
8<author initials='A.' surname='Bergkvist' fullname='Adam Bergkvist'>
9    <organization />
10</author>
11
12<author initials='D.' surname='Burnett' fullname='Daniel C. Burnett'>
13    <organization />
14</author>
15
16<author initials='C.' surname='Jennings' fullname='Cullen Jennings'>
17    <organization />
18</author>
19
20<author initials='A.' surname='Narayanan' fullname='Anant Narayanan'>
21    <organization />
22</author>
23
24<date month='February' day='9' year='2012' />
25</front>
26
27<seriesInfo name='World Wide Web Consortium WD' value='WD-webrtc-20120209' />
28<format type='HTML' target='http://www.w3.org/TR/2012/WD-webrtc-20120209' />
29</reference>
1<?xml version='1.0' encoding='UTF-8'?>
2
3<reference anchor='W3C.WD-mediacapture-streams-20120628'
4           target='http://www.w3.org/TR/2012/WD-mediacapture-streams-20120628'>
5<front>
6<title>Media Capture and Streams</title>
7
8<author initials='D.' surname='Burnett' fullname='Daniel C. Burnett'>
9    <organization />
10</author>
11
12<author initials='A.' surname='Narayanan' fullname='Anant Narayanan'>
13    <organization />
14</author>
15
16<date month='June' day='28' year='2012' />
17</front>
18
19<seriesInfo name='World Wide Web Consortium WD' value='WD-mediacapture-streams-20120628' />
20<format type='HTML' target='http://www.w3.org/TR/2012/WD-mediacapture-streams-20120628' />
21</reference>
1<?xml version='1.0' encoding='UTF-8'?>
2
3<reference  anchor='RFC3261' target='https://www.rfc-editor.org/info/rfc3261'>
4<front>
5<title>SIP: Session Initiation Protocol</title>
6<author initials='J.' surname='Rosenberg' fullname='J. Rosenberg'><organization /></author>
7<author initials='H.' surname='Schulzrinne' fullname='H. Schulzrinne'><organization /></author>
8<author initials='G.' surname='Camarillo' fullname='G. Camarillo'><organization /></author>
9<author initials='A.' surname='Johnston' fullname='A. Johnston'><organization /></author>
10<author initials='J.' surname='Peterson' fullname='J. Peterson'><organization /></author>
11<author initials='R.' surname='Sparks' fullname='R. Sparks'><organization /></author>
12<author initials='M.' surname='Handley' fullname='M. Handley'><organization /></author>
13<author initials='E.' surname='Schooler' fullname='E. Schooler'><organization /></author>
14<date year='2002' month='June' />
15<abstract><t>This document describes Session Initiation Protocol (SIP), an application-layer control (signaling) protocol for creating, modifying, and terminating sessions with one or more participants.  These sessions include Internet telephone calls, multimedia distribution, and multimedia conferences.  [STANDARDS-TRACK]</t></abstract>
16</front>
17<seriesInfo name='RFC' value='3261'/>
18<seriesInfo name='DOI' value='10.17487/RFC3261'/>
19</reference>
1<?xml version='1.0' encoding='UTF-8'?>
2
3<reference  anchor='RFC3361' target='https://www.rfc-editor.org/info/rfc3361'>
4<front>
5<title>Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation Protocol (SIP) Servers</title>
6<author initials='H.' surname='Schulzrinne' fullname='H. Schulzrinne'><organization /></author>
7<date year='2002' month='August' />
8</front>
9<seriesInfo name='RFC' value='3361'/>
10<seriesInfo name='DOI' value='10.17487/RFC3361'/>
11</reference>
1<?xml version='1.0' encoding='UTF-8'?>
2
3<reference  anchor='RFC3935' target='https://www.rfc-editor.org/info/rfc3935'>
4<front>
5<title>A Mission Statement for the IETF</title>
6<author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'><organization /></author>
7<date year='2004' month='October' />
8<abstract><t>This memo gives a mission statement for the IETF, tries to define the terms used in the statement sufficiently to make the mission statement understandable and useful, argues why the IETF needs a mission statement, and tries to capture some of the debate that led to this point.  This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t></abstract>
9</front>
10<seriesInfo name='BCP' value='95'/>
11<seriesInfo name='RFC' value='3935'/>
12<seriesInfo name='DOI' value='10.17487/RFC3935'/>
13</reference>
1<?xml version='1.0' encoding='UTF-8'?>
2
3<reference  anchor='RFC5761' target='https://www.rfc-editor.org/info/rfc5761'>
4<front>
5<title>Multiplexing RTP Data and Control Packets on a Single Port</title>
6<author initials='C.' surname='Perkins' fullname='C. Perkins'><organization /></author>
7<author initials='M.' surname='Westerlund' fullname='M. Westerlund'><organization /></author>
8<date year='2010' month='April' />
9<abstract><t>This memo discusses issues that arise when multiplexing RTP data packets and RTP Control Protocol (RTCP) packets on a single UDP port. It updates RFC 3550 and RFC 3551 to describe when such multiplexing is and is not appropriate, and it explains how the Session Description Protocol (SDP) can be used to signal multiplexed sessions.  [STANDARDS-TRACK]</t></abstract>
10</front>
11<seriesInfo name='RFC' value='5761'/>
12<seriesInfo name='DOI' value='10.17487/RFC5761'/>
13</reference>
1<?xml version='1.0' encoding='UTF-8'?>
2
3<reference  anchor='RFC6120' target='https://www.rfc-editor.org/info/rfc6120'>
4<front>
5<title>Extensible Messaging and Presence Protocol (XMPP): Core</title>
6<author initials='P.' surname='Saint-Andre' fullname='P. Saint-Andre'><organization /></author>
7<date year='2011' month='March' />
8<abstract><t>The Extensible Messaging and Presence Protocol (XMPP) is an application profile of the Extensible Markup Language (XML) that enables the near-real-time exchange of structured yet extensible data between any two or more network entities.  This document defines XMPP's core protocol methods: setup and teardown of XML streams, channel encryption, authentication, error handling, and communication primitives for messaging, network availability (&quot;presence&quot;), and request-response interactions.  This document obsoletes RFC 3920.  [STANDARDS-TRACK]</t></abstract>
9</front>
10<seriesInfo name='RFC' value='6120'/>
11<seriesInfo name='DOI' value='10.17487/RFC6120'/>
12</reference>
1<?xml version='1.0' encoding='UTF-8'?>
2
3<reference  anchor='RFC7478' target='https://www.rfc-editor.org/info/rfc7478'>
4<front>
5<title>Web Real-Time Communication Use Cases and Requirements</title>
6<author initials='C.' surname='Holmberg' fullname='C. Holmberg'><organization /></author>
7<author initials='S.' surname='Hakansson' fullname='S. Hakansson'><organization /></author>
8<author initials='G.' surname='Eriksson' fullname='G. Eriksson'><organization /></author>
9<date year='2015' month='March' />
10<abstract><t>This document describes web-based real-time communication use cases. Requirements on the browser functionality are derived from the use cases.</t><t>This document was developed in an initial phase of the work with rather minor updates at later stages.  It has not really served as a tool in deciding features or scope for the WG's efforts so far.  It is being published to record the early conclusions of the WG.  It will not be used as a set of rigid guidelines that specifications and implementations will be held to in the future.</t></abstract>
11</front>
12<seriesInfo name='RFC' value='7478'/>
13<seriesInfo name='DOI' value='10.17487/RFC7478'/>
14</reference>
1<?xml version='1.0' encoding='UTF-8'?>
2
3<reference  anchor='RFC8155' target='https://www.rfc-editor.org/info/rfc8155'>
4<front>
5<title>Traversal Using Relays around NAT (TURN) Server Auto Discovery</title>
6<author initials='P.' surname='Patil' fullname='P. Patil'><organization /></author>
7<author initials='T.' surname='Reddy' fullname='T. Reddy'><organization /></author>
8<author initials='D.' surname='Wing' fullname='D. Wing'><organization /></author>
9<date year='2017' month='April' />
10<abstract><t>Current Traversal Using Relays around NAT (TURN) server discovery mechanisms are relatively static and limited to explicit configuration.  These are usually under the administrative control of the application or TURN service provider, and not the enterprise, ISP, or the network in which the client is located.  Enterprises and ISPs wishing to provide their own TURN servers need auto-discovery mechanisms that a TURN client could use with minimal or no configuration.  This document describes three such mechanisms for TURN server discovery.</t><t>This document updates RFC 5766 to relax the requirement for mutual authentication in certain cases.</t></abstract>
11</front>
12<seriesInfo name='RFC' value='8155'/>
13<seriesInfo name='DOI' value='10.17487/RFC8155'/>
14</reference>
1<reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml">
2<front>
3<title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
4<author initials="B." surname="Leiba" fullname="B. Leiba"><organization/></author>
5<date year="2017" month="May"/>
6<abstract><t>RFC 2119 specifies common key words that may be used in protocol  specifications.  This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the  defined special meanings.</t></abstract>
7</front>
8<seriesInfo name="BCP" value="14"/>
9<seriesInfo name="RFC" value="8174"/>
10<seriesInfo name="DOI" value="10.17487/RFC8174"/>
11</reference>
1<?xml version='1.0' encoding='UTF-8'?>
2
3<reference anchor='W3C.WD-html5-20110525'
4           target='http://www.w3.org/TR/2011/WD-html5-20110525'>
5<front>
6<title>HTML5</title>
7
8<author initials='I.' surname='Hickson' fullname='Ian Hickson'>
9    <organization />
10</author>
11
12<date month='May' day='25' year='2011' />
13</front>
14
15<seriesInfo name='World Wide Web Consortium LastCall' value='WD-html5-20110525' />
16<format type='HTML' target='http://www.w3.org/TR/2011/WD-html5-20110525' />
17</reference>

mirror server hosted at Truenetwork, Russian Federation.