Re: [SAFE] nat-control-stun-usage-04

On 11-Oct-07, at 06:57 , Rémi Denis-Courmont wrote:

> Le Wednesday 10 October 2007 22:32:37 ext Dan Wing, vous avez écrit :
>> We just submitted a new version of STUN Control,
>> http://www.ietf.org/internet-drafts/draft-wing-behave-nat-control- 
>> stun-usag
>> e-0 4.txt
>>
>> The changes were mostly organizational and editorial, and included:
>>
>>    o  Clarified that all existing bindings, for that source IP  
>> address
>>       and UDP port, are controlled with STUN Control.
>>
>>    o  Introduction now concentrates on the primary purpose of STUN
>>       Control, namely reducing keepalive traffic for SIP-Outbound.
>
> As far as I understand, STUN in general, and STUN in particular,  
> can be used
> for any UDP-based always-on protocol. ESP-in-UDP, TEREDO, perhaps  
> some long
> usages of RTP (such as MIDI-over-RTP(?) or RTSP-based streaming),  
> proprietary
> UDP overlays (not giving any names)...
>
> And then, there is the relation to ICE in finding "intermediary"  
> NAT mappings
> in nested NATs scenarios.

This remains a big interest of mine, though increasing the lifetime  
of UDP mapping and filtering entries is also a big win. I am not sure  
why the focus is SIP-Outbound as opposed to other UDP uses.

>
> At the same time, I thought SIP Outbound was going to recommend  
> TCP, so that
> it could end up being a less likely "customer" of STUN control??
>
> -- 
> Rémi Denis-Courmont
>
>
> _______________________________________________
> SAFE mailing list
> SAFE@ietf.org
> https://www1.ietf.org/mailman/listinfo/safe
>

_______________________________________________
SAFE mailing list
SAFE@ietf.org
https://www1.ietf.org/mailman/listinfo/safe