Signaling TO Prevent SPIT (SPITSTOP) Reference Scenario
draft-niccolini-sipping-spitstop-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Saverio Niccolini , Jan Seedorf | ||
| Last updated | 2008-02-15 (Latest revision 2007-01-11) | ||
| RFC stream | (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 discusses the need for standards that support SPam over Internet Telephony (SPIT) prevention applications. After explaining the general need for SPIT prevention applications the memo provides a reference scenario for potential communication between entities that may be involved in SPIT prevention. Within this scenario the need for standardizing communication is analyzed for each pair of communicating entities. The analysis is intended to serve as a starting point for discussing the requirements for signaling standards as well as for architectural considerations, that support SPIT prevention applications. This memo is not intended to suggest any solution of SPIT signaling issues. Such work, if necessary at all, should be object of separate documents.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)