W3C home > Mailing lists > Public > public-webrtc@w3.org > January 2013

[Bug 20808] New: "Trickle ICE" unspecified

From: <bugzilla@jessica.w3.org>
Date: Tue, 29 Jan 2013 18:09:33 +0000
To: public-webrtc@w3.org
Message-ID: <bug-20808-4991@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20808

            Bug ID: 20808
           Summary: "Trickle ICE" unspecified
    Classification: Unclassified
           Product: WebRTC Working Group
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: WebRTC API
          Assignee: public-webrtc@w3.org
          Reporter: matthew.kaufman@skype.net
                CC: public-webrtc@w3.org

In the WebRTC draft, Section 4.3.2.2, there is a method addIceCandidate() on
the RTCPeerConnection object. From the description, is appears to be possible
to add ICE candidates “late”, that is, after the initial offer/answer exchange.
In addition, it is expected to be possible to start with NO ICE candidates.
This concept is known as “trickle ICE”. There is no specification within this
document, nor any IETF RFC referenced by this document describing how “trickle
ICE” should be implemented within the RFC3264 (SDP offer/answer) offer/answer
framework, nor does RFC 5245 (ICE) allow for the addition of ICE candidates
after the ICE state machine reaches either the Failed or Succeeded state. It is
also clear that starting with no candidates should cause the ICE state machine
to immediately reach the Failed state.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
Received on Tuesday, 29 January 2013 18:09:34 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:32 UTC