<br><br><div><span class="gmail_quote">2008/1/10, Robert Moskowitz <<a href="mailto:rgm@htt-consult.com">rgm@htt-consult.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Olivier wrote:<br>><br>><br>> 2008/1/10, Robert Moskowitz <<a href="mailto:rgm@htt-consult.com">rgm@htt-consult.com</a><br>> <mailto:<a href="mailto:rgm@htt-consult.com">rgm@htt-consult.com</a>>>:<br>
><br>> Jeronimo Romero wrote:<br>> ><br>> > Does anyone know if sip phones from any of the major IP phone<br>> vendors<br>> > support 802.1x authentication? Any feedback would be greatly
<br>> appreciated.<br>> ><br>> This is so unlikely. I worked on 802.1X and 802.11i. There is<br>> just too<br>> much overhead there. No way to meet the ITU 50ms disruption<br>> requirement.
<br>><br>><br>> Do you mean ITU is asking phone to authenticate within a 50ms time frame ?<br>> Or do you mean, RTP flow encryption shouldn't exceed 50ms ?<br>The later. So an authenticate while a flow is in process can kill the
<br>call. This is what can happen during a roam (or a re-key).</blockquote><div><br>OK : now I understand what you meant .<br>Myself, I was thinking about desktop hardphones so I didn't why this authentication process duration would matter.
<br><br>Have you looked at Meru or Extricom stuff ?<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Cellular phone authentication can take a REAL long time! You see this
<br>when the phone is 'discoverying' your network.<br><br><br><br>_______________________________________________<br>-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com">http://www.api-digital.com
</a> --<br><br>asterisk-users mailing list<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
</blockquote></div><br>