Oh and a separate tcptype attribute seems fine. Not so sure about ice-lite yet...
Sent from mobile, might be terse > On Dec 17, 2015, at 5:49 AM, Philipp Hancke <fi...@goodadvice.pages.de> wrote: > > oh... just noticed this introduces types for tcp-active etc. > This is rather unfortunate as there can be candidates of type host with > protocol udp and a tcptype active. Mapping this seems complicated, i'd prefer > to have a separate tcptype attribute. > > Also, the 6544 reference is not work in progress ;-) > > And since i'm currently dealing with ice-lite: > For the purposes of the Jingle ICE-UDP Transport Method, both > parties are full ICE implementations and therefore the > controlling role MUST be assumed by the initiator and the > controlled role MUST be assumed by the responder. > We might want to introduce a way to use ice-lite. > _______________________________________________ > Standards mailing list > Info: http://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: standards-unsubscr...@xmpp.org > _______________________________________________ _______________________________________________ Standards mailing list Info: http://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________