metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 6665: SIP-Specific Event Notification

Still current, but amended. Parts of this document are changed or extended by RFC 7621. Read both.

In plain English — editorial summary, not part of the RFC

This document describes an extension to the Session Initiation Protocol (SIP) defined by RFC 3261. The purpose of this extension is to provide an extensible framework by which SIP nodes can request notification from remote nodes indicating that certain events have occurred. Note that the event notification mechanisms defined herein are NOT intended to be a general-purpose infrastructure for all classes of event subscription and notification. This document represents a backwards-compatible improvement on the original mechanism described by RFC 3265, taking into account several years of implementation experience. Accordingly, this document obsoletes RFC 3265. This document also updates RFC 4660 slightly to accommodate some small changes to the mechanism that were discussed in that document. [STANDARDS-TRACK]

Document record

Document ID
RFC6665
Published
July 2012
Authors
A.B. Roach
Status
PROPOSED STANDARD
Stream
IETF
Area
art
Pages
53
Also known as
—
Obsoletes:
RFC 3265
Updates:
RFC 3261, RFC 4660
Updated by:
RFC 7621

Topics

Standards lineage

This document is one revision in a chain of 7 RFCs, each formally replacing the one before it.

  1. RFC 2543 (1999)
  2. RFC 3261 (2002)
  3. RFC 3262 (2002)
  4. RFC 3263 (2002)
  5. RFC 3264 (2002)
  6. RFC 3265 (2002)
  7. RFC 6665 (2012)

Read the full history of SIP-Specific Event Notification →

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/6665-sip-specific-event-notification