@techreport{rosenberg-sipping-consent-reqs-00,
    number =    {draft-rosenberg-sipping-consent-reqs-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-rosenberg-sipping-consent-reqs/00/},
    author =    {Jonathan Rosenberg and Jonathan Rosenberg and Gonzalo Camarillo},
    title =     {{Requirements for Consent-Based Communications in the Session Initiation Protocol (SIP)}},
    pagetotal = 8,
    year =      2004,
    month =     jul,
    day =       13,
    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.},
}