[Standards] XEP-0371 (Jingle ICE): update RFC 5245 -> RFC 8445

Jonathan Lennox lennox at cs.columbia.edu
Thu Mar 12 21:47:48 UTC 2020


One major comment:

1. There is (and has always been) a semantic hole in ICE restart with
Jingle, because transport-info is a unilateral message, unlike SDP
offer/answer which is transactional.

Specifically, there's no way for a Jingle endpoint to know for certain which
generation of its local candidates should be matched with a set of
candidates received in a transport-info message.

Perhaps some sort of remote-generation attribute is necessary for candidates
sent in response to a peer's candidates?

On Friday, March 13 2020, "Sergey Ilinykh" wrote to "XMPP Standards" saying:

> https://github.com/xsf/xeps/pull/905
> 
> PR Changes:
> 
>  1. RFC 5245 is replaced with RFC 8445
>  2. Aggressive nomination is not supported anymore
>  3. remote-candidate is now MUST to mimic ICE SDP RFC
>  4. Now remote-candidate has to be send for all components at once when ICE for
>     media stream has completed
>  5. Namespace version was updated because of incompatible changes
>  6. Wrong reference to RFC 6455 was replaced with correct one: RFC 6544
> 
> Let's review / discuss / fix / merge.
> 
> Best Regards,
> Sergey
> _______________________________________________
> Standards mailing list
> Info: https://mail.jabber.org/mailman/listinfo/standards
> Unsubscribe: Standards-unsubscribe at xmpp.org
> _______________________________________________

-- 
Jonathan Lennox
lennox at cs.columbia.edu


More information about the Standards mailing list