A Framework for Consent-Based Communications in the Session Initiation Protocol
RFC 5360, “A Framework for Consent-Based Communications in the Session Initiation Protocol”, is a Proposed Standard document published in October 2008 by J. Rosenberg, G. Camarillo, D. Willis. It has since been updated by RFC 8217. The canonical text is published by the RFC Editor.
Abstract
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 5360 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5359 Session Initiation Protocol Service Examples
- RFC 5361 A Document Format for Requesting Consent
- RFC 5358 Preventing Use of Recursive Nameservers in Reflector Attacks
- RFC 5362 The Session Initiation Protocol Pending Additions Event Package
- RFC 5357 A Two-Way Active Measurement Protocol
- RFC 5363 Framework and Security Considerations for Session Initiation Protocol URI-List Services
- RFC 5356 Reliable Server Pooling Policies
- RFC 5364 Extensible Markup Language Format Extension for Representing Copy Control Attributes in Resource Lists