[VOIPSA Best Practices] Welcome to the VOIPSA Best Practices project... and some weekend reading for you all (if you get this)

[Dustin D. Trammell]

On Fri, 2006-12-01 at 23:37 -0500, dan_york at Mitel.com wrote:
> 2. What do people think about how we should best structure the
> document?  (See my notes on the Development Process page.) 

I prefer "2. SEGMENT INTO FUNCTIONAL(?) AREAS"

> 3. Do you agree with what I identified as the target audience?   

Looks comprehensive to me.

> 4. I've identified about 10 potential volunteer roles... do you agree
> with my thoughts?  
> 5. If so,  anyone already willing to step forward and say how they'll
> contribute? 

I would like to volunteer for an Editor role as well as an SME role.

> 6. Any thoughts on the questions I raise at the bottom of the
> Development Process page? 

2. I think that a single document can likely address both Enterprise and
Carrier concerns, however the document may require some internal
structuring in various areas to address both.

4. We should include compliance issues when the subject-matter relates
to VoIP security in some way.  We shouldn't stray too far from our
core-purpose.  I can see where privacy issues such as media
eavesdropping relate to security, but how do E911 services apply?  Are
you asking if we should include best practices for securing E911
services themselves?

5. For version 1 of the document let's stick to voice unless it becomes
clear that we have extra time and resources to add other mediums to the
document.

Thanks for leading this project,

-- 
Dustin D. Trammell
VoIP Security Research
TippingPoint, a division of 3Com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 191 bytes
Desc: This is a digitally signed message part
URL: <http://voipsa.org/pipermail/bestpractices_voipsa.org/attachments/20061207/cfa12cc8/attachment.sig>