RFC 5039: The Session Initiation Protocol (SIP) and Spam
In plain English — editorial summary, not part of the RFC
Spam, defined as the transmission of bulk unsolicited messages, has plagued Internet email. Unfortunately, spam is not limited to email. It can affect any system that enables user-to-user communications. The Session Initiation Protocol (SIP) defines a system for user-to- user multimedia communications. Therefore, it is susceptible to spam, just as email is. In this document, we analyze the problem of spam in SIP. We first identify the ways in which the problem is the same and the ways in which it is different from email. We then examine the various possible solutions that have been discussed for email and consider their applicability to SIP. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5039
- Published
- January 2008
- Authors
- J. Rosenberg; C. Jennings
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 28
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5028A Telephone Number Mapping (ENUM) Service Registration for Instant Messaging (IM) ServicesUpdated
October 2007
- RFC 5025Presence Authorization RulesCurrent
December 2007
- RFC 5057Multiple Dialog Usages in the Session Initiation ProtocolCurrent
November 2007
- RFC 5018Connection Establishment in the Binary Floor Control Protocol (BFCP)Updated
September 2007
- RFC 5067Infrastructure ENUM RequirementsCurrent
November 2007
- RFC 5076ENUM Validation Information Mapping for the Extensible Provisioning ProtocolCurrent
December 2007
- RFC 5079Rejecting Anonymous Requests in the Session Initiation Protocol (SIP)Current
December 2007
- RFC 4979IANA Registration for Enumservice 'XMPP'Updated
August 2007
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?