A Framework for Consent-Based Communications in the Session Initiation Protocol (SIP), October 2008
- Canonical URL:
- File formats:
- PROPOSED STANDARD
- Updated by:
- RFC 8217
- J. Rosenberg
G. Camarillo, Ed.
- sip (rai)
Discuss this RFC: Send questions or comments to email@example.com
SIP supports communications for several services, 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 amplification and DoS (Denial of Service) attacks. This document identifies a framework for consent-based communications in SIP. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 4844.