RFC 3680: A Session Initiation Protocol (SIP) Event Package for Registrations
In plain English — editorial summary, not part of the RFC
This document defines a Session Initiation Protocol (SIP) event package for registrations. Through its REGISTER method, SIP allows a user agent to create, modify, and delete registrations. Registrations can also be altered by administrators in order to enforce policy. As a result, these registrations represent a piece of state in the network that can change dynamically. There are many cases where a user agent would like to be notified of changes in this state. This event package defines a mechanism by which those user agents can request and obtain such notifications. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3680
- Published
- March 2004
- Authors
- J. Rosenberg
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 26
- Also known as
- —
- Updated by:
- RFC 6140
Topics
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.
- RFC 3608Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During RegistrationUpdated
October 2003
- RFC 3327Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent ContactsUpdated
December 2002
- RFC 3725Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP)Current
April 2004
- RFC 3764enumservice registration for Session Initiation Protocol (SIP) Addresses-of-RecordUpdated
April 2004
- RFC 3581An Extension to the Session Initiation Protocol (SIP) for Symmetric Response RoutingCurrent
August 2003
- RFC 3578Mapping of Integrated Services Digital Network (ISDN) User Part (ISUP) Overlap Signalling to the Session Initiation Protocol (SIP)Current
August 2003
- RFC 3840Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)Current
August 2004
- RFC 3841Caller Preferences for the Session Initiation Protocol (SIP)Current
August 2004
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?