[hydra-dev] Networking stack (NAT, Firewall, IPv6)

[Nick Lewis]

>I think the role of the server outside a
>NAT will be more important, and in that 
>role Hydra should be able to assist 
>clients that are behind NATs to perform 
>their NAT traversal. I'm thinking of the 
>following features:
>- ICE-lite
>- STUN server
>- TURN server

I think that STUN/TURN/ICE is an area where rfc theory and real world
practice diverge. I am not sure that hydra needs to bother with any of
it except port-muxed stun keep-alives as per RFC5626 section 8

-- N_L


_____________________________________________________________________
This message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Control Centre.
_____________________________________________________________________
Disclaimer of Liability
ATL Telecom Ltd shall not be held liable for any improper or incorrect use of the  information described and/or contained herein and assumes no responsibility for anyones use  of the information. In no event shall ATL Telecom Ltd be liable for any direct, indirect,  incidental, special, exemplary, or consequential damages (including, but not limited to,  procurement or substitute goods or services; loss of use, data, or profits; or business  interruption) however caused and on any theory of liability, whether in contract, strict  liability, or tort (including negligence or otherwise) arising in any way out of the use of  this system, even if advised of the possibility of such damage.

Registered Office: ATL Telecom Ltd, Fountain Lane, St. Mellons Cardiff, CF3 0FB
Registered in Wales Number 4335781

All goods and services supplied by ATL Telecom Ltd are supplied subject to ATL Telecom Ltd standard terms and conditions, available upon request.