Re: [Wish] WG Last Call for draft-ietf-wish-whip

[Juliusz Chroboczek <[e-mail]>]

> We have already discussed about this in here:
> https://github.com/wish-wg/webrtc-http-ingest-protocol/issues/66

Sorry to bring it up again.

> Basically, the suggested proposal is to use this code flow:
> offer = pc.createOffer();
> [answer,iceServers] = POST(offer)
> pc.setConfigutation({iceServers});
> pc.setLocalDescription(offer);
> pc.setRemoteDescription(answer);

I don't understand how that can work.  By the time ICE gathering is
started (by createOffer), it is too late to change the ICE configuration.

> This is guaranteed to work on all JSEP compatible clients.

I'm probably mistaken, but I was under the impression that you need an ICE
restart for the new configuration to have any effect.  Could you please
present your evidence that that is not the case?

>     2. No way to discover whether Trickle ICE is available

[...]

> Even if the media server doesn't support ICE trickle candidate signaling, the
> ICE connection may still be successful, as the media server should support
> receiving STUN binding requests from unknown ips:ports as long as the ice
> username/fragments are correct.
> 
> Trickle ICE is only needed in case that the media server is behind a NAT
> and we need to do nat hole punching.

Could you please explain what happens if the client is behind a firewall
that only allows outgoing TCP traffic, and only to a small set of
well-known ports, which is sadly the case in many university networks?

-- Juliusz