<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2995" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=663100822-19012007><FONT face=Arial
color=#0000ff size=2>Thanks, Dan.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=663100822-19012007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=663100822-19012007><FONT face=Arial
color=#0000ff size=2>Though I was proposing the alternative approach #4, this
does not mean I considered #2 as being inadequate. I can definitely see how
the BP document can also be approached and aligned with #2 to meet the
document's goals. Co-incidentally, many of the items listed below are worded
(either explicitly or implicitly) in-line with "Interface Approach"
#4.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=663100822-19012007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=663100822-19012007><FONT face=Arial
color=#0000ff size=2>One area the BP document may also want to touch is CALEA
(law enforcement).</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=663100822-19012007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=663100822-19012007><FONT face=Arial
color=#0000ff size=2>Regards,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=663100822-19012007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=663100822-19012007><FONT face=Arial
color=#0000ff size=2>Eugene Nechamkin.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=663100822-19012007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left>
<HR tabIndex=-1>
</DIV>
<DIV dir=ltr align=left><FONT face=Tahoma size=2><B>From:</B>
bestpractices-bounces@voipsa.org [mailto:bestpractices-bounces@voipsa.org] <B>On
Behalf Of </B>dan_york@Mitel.com<BR><B>Sent:</B> Friday, January 19, 2007 2:58
AM<BR><B>To:</B> bestpractices@voipsa.org<BR><B>Subject:</B> [VOIPSA Best
Practices] Best Practices document structure set - next question: are these the
appropriate areas?<BR></FONT><BR></DIV>
<DIV></DIV><BR><FONT face=sans-serif size=2>Best Practices team,</FONT>
<BR><BR><FONT face=sans-serif size=2>Thank you to those of you who sent in
comments either on the list or directly to me. A special thanks to Eugene
Nechamkin who took the time to write up a counter-proposal. Outside of his
contribution, basically all the feedback was for proposal #2, structuring the
document around functional areas, and so I'm going to say we're going with
that.</FONT> <BR><BR><FONT face=sans-serif size=2>Now, the next question - is
this list below from the wiki the appropriate list of areas for VoIP-related
best practices?</FONT> <BR><BR><FONT face=sans-serif size=2>1.
</FONT><FONT size=3>Securing Voice and Media stream
</FONT><BR><FONT face=sans-serif size=2>2.
</FONT><FONT size=3>Securing Call Control </FONT><BR><FONT face=sans-serif
size=2>3. </FONT><FONT size=3>Securing Management
Interfaces and APIs </FONT><BR><FONT face=sans-serif size=2>4.
</FONT><FONT size=3>Securing PSTN Interfaces and Traditional
Telephony Issues (i.e. don't forget toll fraud) </FONT><BR><FONT face=sans-serif
size=2>5. </FONT><FONT size=3>Securing Servers and
Operating Systems </FONT><BR><FONT face=sans-serif size=2>6.
</FONT><FONT size=3>Securing IP Endpoints (ex. sets, softphones,
etc.) </FONT><BR><FONT face=sans-serif size=2>7.
</FONT><FONT size=3>Securing the TCP/IP network (ex. VLANs, 802.1X,
wireless, etc.) </FONT><BR><FONT face=sans-serif size=2>8.
</FONT><FONT size=3>Physical Security, including backups, power, etc.
</FONT><BR><BR><FONT face=sans-serif size=2>Are we missing any major areas?
Should these be modified or tweaked?</FONT> <BR><BR><FONT face=sans-serif
size=2>It seems to me to be a complete list, but then again, I wrote it, so of
course it would. Any feedback is welcome.</FONT> <BR><BR><FONT
face=sans-serif size=2>Regards,<BR>Dan</FONT> <BR><BR><FONT face=sans-serif
size=2>-- <BR>Dan York, CISSP<BR>Dir of IP Technology, Office of the
CTO<BR>Mitel Corp. http://www.mitel.com<BR>dan_york@mitel.com
+1-613-592-2122<BR>PGP key (F7E3C3B4) available for <BR>secure
communication<BR><BR></FONT></BODY></HTML>