API Build-data JSON Resources
Theme

Choose how MSRBot.io looks on this device.

Auto (match system) Light mode Dark mode

Preference is stored in this browser only.

IETF RFC 4453
[ACTIVE]

Requirements for Consent-Based Communications in the Session Initiation Protocol (SIP)

Metadata

Publisher
IETF
Doc Type
Informational
Pages
8
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. This memo provides information for the Internet community.
Publication Date
2006-04-01
Status Note
Informational
DOI
10.17487/RFC4453
Link
https://doi.org/10.17487/RFC4453
Author(s)
Jonathan Rosenberg
Gonzalo Camarillo
Dean Willis
Keyword(s)
SIP
Latest version of IETF RFC 4453

Document Versions — IETF RFC 4453

  • ▶ IETF RFC 4453 (2006-04-01)
    THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

  • Camarillo, G. and A. Johnston, "Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP)", Work in Progress, February 2006. EXTERNAL
  • Garcia-Martin, M. and G. Camarillo, "Multiple-Recipient MESSAGE Requests in the Session Initiation Protocol (SIP)", Work in Progress, February 2006. EXTERNAL
  • Rosenberg, J., "The Session Initiation Protocol (SIP) and Spam" , Work in Progress, July 2005. EXTERNAL
  • Roach, A.B., Rosenberg, J., and B. Campbell, "A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists", Work in Progress, January 2005. EXTERNAL
  • Camarillo, G. and A.B. Roach, "Framework and Security Considerations for Session Initiation Protocol (SIP) Uniform Resource Identifier (URI)-List Services", Work in Progress, January 2006. EXTERNAL
  • IETF RFC 3261 [Active*]
  • IETF RFC 3263 [Active*]
  • IETF RFC 3265 [Superseded*]
  • IETF RFC 3428 [Active*]
Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC4453.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 4453, Requirements for Consent-Based Communications in the Session Initiation Protocol (SIP). Available at https://doi.org/10.17487/RFC4453
Snippet:
IETF RFC 4453, Requirements for Consent-Based Communications in the Session Initiation Protocol (SIP). Available at https://doi.org/10.17487/RFC4453

HTML (ISO 690 compliant)

Preview:
IETF RFC 4453, Requirements for Consent-Based Communications in the Session Initiation Protocol (SIP). Available at https://doi.org/10.17487/RFC4453
Snippet:
<span class="citation"><cite>IETF RFC 4453</cite>, Requirements for Consent-Based Communications in the Session Initiation Protocol (SIP). Available at <a href="https://doi.org/10.17487/RFC4453" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4453</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 4453, Requirements for Consent-Based Communications in the Session Initiation Protocol (SIP)
doi: 10.17487/RFC4453
url: https://doi.org/10.17487/RFC4453
Snippet:
<li>
<cite id="bib-rfc4453">IETF RFC 4453</cite>, Requirements for Consent-Based Communications in the Session Initiation Protocol (SIP)
<span class="doi">10.17487/RFC4453</span>
</li>

Referenced By