metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 3265: Session Initiation Protocol (SIP)-Specific Event Notification

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6665.

Current document in this lineage: RFC 3261 — SIP: Session Initiation Protocol; RFC 3262 — Reliability of Provisional Responses in Session Initiation Protocol (SIP); RFC 3263 — Session Initiation Protocol (SIP): Locating SIP Servers; RFC 3264 — An Offer/Answer Model with Session Description Protocol (SDP); RFC 6665 — SIP-Specific Event Notification

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

This document describes an extension to the Session Initiation Protocol (SIP). 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. [STANDARDS-TRACK]

Document record

Document ID
RFC3265
Published
July 2002
Authors
A. B. Roach
Status
PROPOSED STANDARD
Stream
IETF
Area
rai
Pages
38
Also known as
—
Obsoletes:
RFC 2543
Obsoleted by:
RFC 6665
Updates:
RFC 3261
Updated by:
RFC 5367, RFC 5727, RFC 6446

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

4 later RFCs formally update or obsolete 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/3265-session-initiation-protocol-sip-specific-event-notification