Skip to main content

Requirements for Consent-Based Communications in the Session Initiation Protocol (SIP)
draft-rosenberg-sipping-consent-reqs-00

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Jonathan Rosenberg , Jonathan Rosenberg , Gonzalo Camarillo
Last updated 2004-07-13
RFC stream (None)
Intended RFC status (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

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.

Authors

Jonathan Rosenberg
Jonathan Rosenberg
Gonzalo Camarillo

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)