|
Jonathan, On Feb 24, 2008, at 5:16 PM, Jonathan Rosenberg wrote:
DY> One other suggestion - I realize it's not a *specification*, but RFC 5039 by you and Cullen about the issues around the potential of spam for SIP is one that I would add to the "security" section. While it doesn't go into detail on specific solutions, it does make people aware of the issues they need to be thinking about when implementing SIP solutions. I would suggest that RFC 5039 could be added now and then replaced later as RFCs emerge with actual solutions (or steps toward solutions). Just a thought. Thanks for your work on this, Dan -- Dan York, CISSP, Director of Emerging Communication Technology Bring your web applications to the phone. Find out how at http://evolution.voxeo.com |
_______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors at cs.columbia.edu for questions on current sip Use sipping at ietf.org for new developments on the application of sip