Avoidance of Security Issues in SIP and Internet
draft-srivastava-dispatch-avoidance-of-threats-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Samir Srivastava | ||
| Last updated | 2012-04-07 (Latest revision 2011-10-05) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This memo lists the security issues not addressed by SIPS and other drafts in progress. It provides two solutions to it. First solution calls for fixing issues one by one. The second solution avoids the security issues altogether. It has potential to obviate the need of 'Security Consideration' section from IETF documents. It requires wider acceptance from the community. Author is requesting IETF community to voice it's opinion and share the second solution with non-IETF members also to have their opinion.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)