Requirements for Consent-Based Communications in the Session Initiation Protocol (SIP), April 2006
- Canonical URL:
- File formats:
- J. Rosenberg
G. Camarillo, Ed.
- sipping (rai)
Discuss this RFC: Send questions or comments to email@example.com
The Session Initiation Protocol (SIP) supports communications across many media types, including real-time audio, video, text, instant messaging, and presence. In its current form, it allows session invitations, instant messages, and other requests to be delivered from one party to another without requiring explicit consent of the recipient. Without such consent, it is possible for SIP to be used for malicious purposes, including spam and denial-of-service attacks. This document identifies a set of requirements for extensions to SIP that add consent-based communications. This memo provides information for the Internet community.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 4844.