<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><base href="x-msg://979/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 21/01/2013, at 5:28 PM, Michael Andreas Schipp <<a href="mailto:MSchipp@a10networks.com">MSchipp@a10networks.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div lang="EN-AU" link="blue" vlink="purple" style="font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div class="WordSection1" style="page: WordSection1; "><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="color: rgb(31, 73, 125); font-family: Calibri, sans-serif; font-size: 11pt; ">Note : Not all protocols “just work”, I work for a vendor that does a *</span><b style="color: rgb(31, 73, 125); font-family: Calibri, sans-serif; font-size: 11pt; ">lot</b><span style="color: rgb(31, 73, 125); font-family: Calibri, sans-serif; font-size: 11pt; ">* of CGN/LSN and for some protocols we needed to create ALGs (Application Layer Gateways) to be able to make things like FTP work via CGN, same for SIP. </span></div></div></div></blockquote><div><br></div>Even with ALG, SIP via NAT is fragile and fraught with hard to diagnose issues. I am quite disappointed with how few SIP phones support ipv6 (Snom almost does it right)</div><div><br><blockquote type="cite"><div lang="EN-AU" link="blue" vlink="purple" style="font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div class="WordSection1" style="page: WordSection1; "><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "> </span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">Also I would like to point out that NAT and CGN is not a security measure – only a IPv4 preservation technology.<o:p></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "> </span></div></div></div></blockquote></div><br><div>I wonder how long until you have to pay an extra $5 pm to get more NAT translations on the CGN. </div></body></html>