diff --git a/index.html b/index.html index f162562..5d06bb0 100644 --- a/index.html +++ b/index.html @@ -123,7 +123,7 @@

Terminology

[[!ECMASCRIPT-6.0]].

In this specification the term user agent refers to any implementation; the term browser specifically refers to browser - implementations.

+ implementations.

Scope

@@ -2485,7 +2485,7 @@

Attributes

This event handler, of event handler event type error, MUST be fired after a DTLS error. An implementation SHOULD provide more details on DTLS errors as follows: + "SHOULD">SHOULD provide more details on DTLS errors as follows:

  1. A fingerprint validation failure is indicated by setting error.name to "fingerprint-failure".
    2. @@ -2493,7 +2493,7 @@

    Attributes

    error.name to "dtls-alert-received".
  2. Sending of a DTLS alert is indicated by setting error.name to "dtls-alert-sent".
    3. -
  3. The DTLS alert value is provided by setting error.message +
  4. The DTLS alert value is provided by setting error.message (defined in [[!HTML5]] Section 6.1.3.6.2) to "DTLS Alert: ".
@@ -2580,7 +2580,7 @@

Methods

If all of the values of remoteParameters.fingerprints[j].algorithm are unsupported, where j goes from 0 to the number of fingerprints. - throw a NotSupportedError.

+ throw a NotSupportedError.

@@ -4634,7 +4634,7 @@

RTP matching rules

share a single SSRC numbering space [[!RFC3550]]. The restrictions arising from this are described in [[!BUNDLE]] Sections 10.1 and 10.1.1.

-

ORTC routing rules

+

ORTC routing rules

[[!BUNDLE]] Section 10.2 describes how RTP packets are routed to the RTCRtpSender/RTCRtpReceiver pair representing an SDP m-line. Since ORTC does not utilize SDP, @@ -6108,7 +6108,7 @@

Dictionary RTCRtpEncodingParameters Members

maxBitrate of type unsigned long
-

Ramp up resolution/quality/framerate until this bitrate, +

Ramp up resolution/quality/framerate until this bitrate, if set; if unset, there is no maximum bitrate. maxBitrate is computed the same way as the Transport Independent Application Specific Maximum (TIAS) @@ -7066,7 +7066,7 @@

Methods

InvalidStateError and abort these steps. -
  • If sender.send has not been called, +
  • If sender.send has not been called, throw an InvalidStateError and abort these steps.
    • @@ -7079,7 +7079,7 @@

    Methods

    not equal to "telephone-event" for any value of j, throw an InvalidStateError and abort these steps. - +
  • Let tones be the method's first argument.
  • If tones contains any unrecognized characters, throw an InvalidCharacterError @@ -7130,7 +7130,7 @@

    Methods

    it is necessary to call insertDTMF with a string containing both the remaining tones (stored in toneBuffer) and the new tones appended - together.

    + together.

    Calling insertDTMF with an empty tones parameter can be used to cancel all tones queued to play after the currently playing tone.

    @@ -7303,7 +7303,7 @@

    DTMF Example

    if (sender.canInsertDTMF) { var duration = 500; sender.insertDTMF("1234", duration); -} else +} else trace("DTMF function not available");

    Send the DTMF signal "123" and abort after sending "2".

    @@ -7338,8 +7338,8 @@

    DTMF Example

    sender.insertDTMF(sender.toneBuffer + "1234"); } else trace("DTMF function not available"); - - + +

    It is always safe to append to the tone buffer. This example appends before any tone playout has started as well as during playout.

    @@ -7355,9 +7355,9 @@ 
    DTMF Example
    
           sender.insertDTMF(sender.toneBuffer + "789");
   };
 } else
-    trace("DTMF function not available");    
+    trace("DTMF function not available");
    - +

    Send a 1-second "1" tone followed by a 2-second "2" tone:

     var sender = new RTCDtmfSender(sendObject);
@@ -7370,7 +7370,7 @@ 
    DTMF Example
    
 } else
     trace("DTMF function not available");
    - +
    • @@ -7384,7 +7384,7 @@

    Overview

    Operation

    An RTCDataChannel object is constructed from a RTCDataTransport object (providing the transport for the - data channel) and an RTCDataChannelParameters object. + data channel) and an RTCDataChannelParameters object. An RTCDataChannel object can be garbage-collected once readyState is closed and it is no longer referenced.

    When the constructor is invoked, the following steps MUST be run:

    @@ -7407,7 +7407,7 @@

    Operation

    existing RTCDataChannel, throw an OperationError.
  • If parameters.id is equal to 65535, - which is greater than the maximum allowed ID of 65534, + which is greater than the maximum allowed ID of 65534, throw a TypeError.
    • @@ -7428,7 +7428,7 @@

    Interface Definition

    (including retransmissions) are allowed (maxPacketLifeTime). These properties can not be used simultaneously and an attempt to do so will result in an error. Not setting any of these properties results in - a reliable channel.

    + a reliable channel.

    There are two ways to establish a connection with RTCDataChannel. The first way is to construct an RTCDataChannel at one of the peers with the @@ -8033,8 +8033,11 @@

    Overview

    Operation

    An RTCSctpTransport is constructed from an RTCDtlsTransport object, and optionally a port number (with a - default of 5000, or the next unused port). If a port already in use is provided in - the constructor, throw an InvalidParameters. + default of 5000, or the next unused port). If an attempt is made to construct an + RTCSctpTransport object with transport.state + closed, throw an InvalidStateError.

    If a port + already in use is provided in the constructor, throw an + InvalidParameters. An RTCSctpTransport object can be garbage-collected once stop() is called and it is no longer referenced.

    @@ -8047,6 +8050,7 @@

    Interface Definition

    readonly attribute RTCDtlsTransport transport; readonly attribute RTCSctpTransportState state; readonly attribute unsigned short port; + void setTransport (RTCDtlsTransport transport); static RTCSctpCapabilities getCapabilities (); void start (RTCSctpCapabilities remoteCaps, optional unsigned short remotePort); void stop (); @@ -8138,6 +8142,62 @@

    Attributes

    Methods

    +
    setTransport
    +
    +

    setTransport() + attempts to replace the SCTP RTCDtlsTransport + transport with the transport provided.

    +

    When the setTransport() method is invoked, the user + agent MUST run the following steps:

    +
      +
    1. +

      If state is closed, throw + an InvalidStateError.

      +
      2. +
    2. +

      Let withTransport be the argument to this method.

      +
      3. +
    3. +

      If setTransport() is called with no arguments, + or if withTransport is unset, throw an + InvalidParameters.

      +
      4. +
    4. +

      If withTransport.state is + closed, throw an InvalidStateError.

      +
      5. +
    5. +

      Set transport to withTransport and + seamlessly send and receive over the new transport.

      +
      6. +
    +
    + + + + + + + + + + + + + + + + +
    ParameterTypeNullableOptionalDescription
    transportRTCDtlsTransport✘✘
    +
    + Return type: void +
    + + + +
    getCapabilities, static

    getCapabilities()