<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<base href="x-msg://877/">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div><br>
</div>
<div>I believe you can configure the ACMEs to limit the qty of registrations send to a downstream registrar, which limits the impacts of most re-registration floods.</div>
<div><br>
</div>
<div>It is also possible to have a 'cache-after-expires' extension to attempt to 'smooth' user-agents that skip a register or two.</div>
<div><br>
</div>
<br>
<div>
<div>On 24/02/2011, at 10:29 AM, Ujjval Karihaloo wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1" style="page: WordSection1; ">
<div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; ">
<span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">ACME DDOS BCP clearly says it has not been tested for REGISTRATION floods. Any SBC out there that can withstand a REG flood?<o:p></o:p></span></div>
<div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; ">
<span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "><o:p> </o:p></span></div>
<div>
<div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; ">
<span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">UK</span><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "><o:p></o:p></span></div>
</div>
<div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; ">
<span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "><o:p> </o:p></span></div>
<div>
<div style="border-right-style: none; border-bottom-style: none; border-left-style: none; border-width: initial; border-color: initial; border-top-style: solid; border-top-color: rgb(181, 196, 223); border-top-width: 1pt; padding-top: 3pt; padding-right: 0in; padding-bottom: 0in; padding-left: 0in; ">
<div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; ">
<b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; ">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; "><span class="Apple-converted-space"> </span>anorexicpoodle [mailto:anorexicpoodle@gmail.com]<span class="Apple-converted-space"> </span><br>
<b>Sent:</b><span class="Apple-converted-space"> </span>Wednesday, February 23, 2011 4:40 PM<br>
<b>To:</b><span class="Apple-converted-space"> </span>Ujjval Karihaloo<br>
<b>Cc:</b><span class="Apple-converted-space"> </span><a href="mailto:voiceops@voiceops.org" style="color: blue; text-decoration: underline; ">voiceops@voiceops.org</a><br>
<b>Subject:</b><span class="Apple-converted-space"> </span>Re: [VoiceOps] ACMEs SIP Dynamic HNT<o:p></o:p></span></div>
</div>
</div>
<div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; ">
<o:p> </o:p></div>
<div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; ">
I use AHNT extensively and it works extremely well. It is critical to note that if the device doesnt respect the expires= parameter than almost no nat traversal on the SBC will work.<span class="Apple-converted-space"> </span><br>
<br>
Some gotchas:<span class="Apple-converted-space"> </span><br>
<br>
1: If you aren't careful about tuning your timers you can quickly overwhelm the CPU of the SBC with a large subscriber base.<span class="Apple-converted-space"> </span><br>
<br>
2: Understand your endpoint and network behavioral patterns. Because HNT(or AHNT) on any level creates a disparity between the public UA and the UA in the softswitch it is possible to inadvertently create registration storms with poor timer and cache settings.
This will cripple and SBC faster than you could think. The more common scenario I have seen is endpoints are on a 45 second registration timer, and an equally short grace period. You experience some kind of BGP issue with a peer causing all your HNT endpoints
via that BGP session to go dead for 180 seconds (bgp failure timer). This means their public UA is removed from the SD but their softswitch registration remains (if you aren't using authentication you could use forced unregistration but thats a whole different
can of worms). When that BGP session is re-established those devices will come at you in a flood. Each of those registers MUST be challenged by the softswitch. If this flood is large enough it can edge out other traffic creating more retransmissions etc and
overall getting quite ugly. There are protections in the SD for this but they are reactionary and don't apply well to this sort of traffic.<span class="Apple-converted-space"> </span><br>
<br>
3: Watch your SD CPU usage like a hawk. On the access side this will be the single limiting factor for how far you can strech a pair of SD's<br>
<br>
4: Early registration makes AHNT much less effective. IF you have devices that regularly send early registrations this will dramatically hinder the AHNT nat discovery algorithms ability to detect the right timer. Many devices attempting to be clever will re-register
at 50% of the expires= value. This really hurts AHNT.<span class="Apple-converted-space"> </span><br>
<br>
<br>
-anorexicpoodle<br>
<br>
<br>
<br>
On Wed, 2011-02-23 at 15:12 -0800, Ujjval Karihaloo wrote:<o:p></o:p></div>
<p class="MsoNormal" style="margin-top: 0in; margin-right: 0in; margin-bottom: 12pt; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; ">
Hi Guys:<br>
<br>
<br>
<br>
We have not used the ACMEs SIP Dynamic HNT feature, where the ACME sends OPTIONS msgs to individual endpoints on its Access side and adjusts their expires times as per individual Firewalls that they are behind.<br>
<br>
<br>
<br>
While it sounds cool, I was wondering if folks have noticed issues with using it given that some endpoints out there don’t even honor the Expires header from REGISTRARs and as the ACME determines the correct NAT interval automatically, it may leave some endpoints
de-registers for small intervals (as per ACME ACLI guide).<br>
<br>
<br>
<br>
Thx for your input<br>
<br>
<br>
<br>
UK<br>
<br>
<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top: 5pt; margin-bottom: 5pt; ">
<pre style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 10pt; font-family: 'Courier New'; "><o:p> </o:p></pre>
<pre style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 10pt; font-family: 'Courier New'; ">_______________________________________________<o:p></o:p></pre>
<pre style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 10pt; font-family: 'Courier New'; ">VoiceOps mailing list<o:p></o:p></pre>
<pre style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 10pt; font-family: 'Courier New'; "><a href="mailto:VoiceOps@voiceops.org" style="color: blue; text-decoration: underline; ">VoiceOps@voiceops.org</a><o:p></o:p></pre>
<pre style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 10pt; font-family: 'Courier New'; "><a href="https://puck.nether.net/mailman/listinfo/voiceops" style="color: blue; text-decoration: underline; ">https://puck.nether.net/mailman/listinfo/voiceops</a><o:p></o:p></pre>
</blockquote>
<div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; ">
<o:p> </o:p></div>
</div>
_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" style="color: blue; text-decoration: underline; ">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" style="color: blue; text-decoration: underline; ">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
</div>
</span></blockquote>
</div>
<br>
</body>
</html>