Draft: rtcweb-overview

Commentary: This deals with some of Meral 's GEN - ART comments . 
 I can see putting it back , but we should be consistent there were two e.g. and two for examples . My matchy - matchy tendencies getting to me . 
 :-) I can flip it in the other direction . Sometimes I show off my English skills , othertimes I want to write simple English . Trapped by my own filters .... the review ended up in my gen - art inbox , which I stopped reading years ago when I left the gen - art team .... 
 No worries . I would go with whatever the RFC editor is going to end up doing , but to be honest I do n’t know which they ’d prefer . spt
As the available bandwidth has increased, and as processors an 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.
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.
By reading this document and the documents it refers to, it should be
possible to have all information needed to implement an WebRTC
compatible implementation.
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.
An implementation of the Interactive Connectivty Establishment
(ICE) I-D.ietf-ice-rfc5245bis 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 XEP-0166).
An implementation of the Interactive Connectivity Establishment
(ICE) I-D.ietf-ice-rfc5245bis 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 XEP-0166).
The protocol implementation involved in the SDP offer/answer
exchange, as defined in RFC3264 section 3.
The protocol implementation involved in the Session Description
Protocol (SDP) offer/answer exchange, as defined in RFC3264
section 3.
A commonly imagined model of deployment is the one depicted below.
A commonly imagined model of deployment is the one depicted below.
In the figure below JS is Javascript.
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
(for example SIP RFC3261 or XMPP RFC6120) could be used between
servers, while either a standards-based or proprietary protocol could
be used between the browser and the web server.
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 XMPP, XMPP could be used for communication between
XMPP servers, with either a standardized signaling mechanism (e.g.
XMPP over WebSockets or BOSH) or a proprietary signaling mechanism
used between the application running in the browser and the web
server.
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 RFC3261 or XMPP RFC6120) could be used between servers,
while either a standards-based or proprietary protocol could be used
between the browser and the web server.
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) or a proprietary signaling mechanism used between the
application running in the browser and the web server.
WebRTC endpoints MUST implement the functions described in that
document that relate to the network layer (for example Bundle I-
D.ietf-mmusic-sdp-bundle-negotiation, RTCP-mux RFC5761 and Trickle
ICE I-D.ietf-ice-trickle), but do not need to support the API
functionality described there.
WebRTC endpoints MUST implement the functions described in that
document that relate to the network layer (e.g.  Bundle I-D.ietf-
mmusic-sdp-bundle-negotiation, RTCP-mux RFC5761 and Trickle ICE I-
D.ietf-ice-trickle), but do not need to support the API functionality
described there.