<p>If an entity supports the SDP offer / answer model described in <cite>RFC 3264</cite> and therefore prefers to receive one "transport-info" action with multiple candidates, it MUST advertise support for the "urn:ietf:rfc:3264" feature.</p>
<p>The registry submission is as follows.</p>
<codecaption='Registry Submission'><![CDATA[
<var>
<name>urn:ietf:rfc:3264</name>
<desc>Signals support for the SDP offer / answer model described in RFC 3264</desc>
<doc>XEP-0176</doc>
</var>
]]></code>
</section2>
<section2topic='Jingle Transport Methods'anchor='registrar-transports'>
<p>The XMPP Registrar shall include "ice-udp" in its registry of Jingle transport methods. The registry submission is as follows:</p>
<code><![CDATA[
@ -979,6 +990,6 @@ INITIATOR NAT RESPONDER
]]></code>
</section1>
<section1topic='Acknowledgements'anchor='ack'>
<p>Thanks to Steffen Larsen and Paul Witty for their comments.</p>
<p>Thanks to Olivier Crête, Tim Julien, Steffen Larsen, Robert McQueen, Mike Ruprecht, and Paul Witty for their feedback.</p>