RFC 3265:Session Initiation Protocol (SIP)-Specifi...
RFC-Ref

Session Initiation Protocol (SIP)-Specific Event Notification


1. Introduction
1.1. Overview of Operation
1.2. Documentation Conventions
2. Definitions
3. Node Behavior
3.1. Description of SUBSCRIBE Behavior
3.1.1. Subscription Duration
3.1.2. Identification of Subscribed Events and Event Classes
3.1.3. Additional SUBSCRIBE Header Values
3.1.4. Subscriber SUBSCRIBE Behavior
3.1.4.1. Requesting a Subscription
3.1.4.2. Refreshing of Subscriptions
3.1.4.3. Unsubscribing
3.1.4.4. Confirmation of Subscription Creation
3.1.5. Proxy SUBSCRIBE Behavior
3.1.6. Notifier SUBSCRIBE Behavior
3.1.6.1. Initial SUBSCRIBE Transaction Processing
3.1.6.2. Confirmation of Subscription Creation/Refreshing
3.1.6.3. Authentication/Authorization of SUBSCRIBE requests
3.1.6.4. Refreshing of Subscriptions
3.2. Description of NOTIFY Behavior
3.2.1. Identification of Reported Events, Event Classes, and Current State
3.2.2. Notifier NOTIFY Behavior
3.2.3. Proxy NOTIFY Behavior
3.2.4. Subscriber NOTIFY Behavior
3.3. General
3.3.1. Detecting support for SUBSCRIBE and NOTIFY
3.3.2. CANCEL requests
3.3.3. Forking
3.3.4. Dialog creation and termination
3.3.5. State Agents and Notifier Migration
3.3.6. Polling Resource State
3.3.7. Allow-Events header usage
3.3.8. PINT Compatibility
4. Event Packages
4.1. Appropriateness of Usage
4.2. Event Template-packages
4.3. Amount of State to be Conveyed
4.3.1. Complete State Information
4.3.2. State Deltas
4.4. Event Package Responsibilities
4.4.1. Event Package Name
4.4.2. Event Package Parameters
4.4.3. SUBSCRIBE Bodies
4.4.4. Subscription Duration
4.4.5. NOTIFY Bodies
4.4.6. Notifier processing of SUBSCRIBE requests
4.4.7. Notifier generation of NOTIFY requests
4.4.8. Subscriber processing of NOTIFY requests
4.4.9. Handling of forked requests
4.4.10. Rate of notifications
4.4.11. State Agents
4.4.12. Examples
4.4.13. Use of URIs to Retrieve State
5. Security Considerations
5.1. Access Control
5.2. Notifier Privacy Mechanism
5.3. Denial-of-Service attacks
5.4. Replay Attacks
5.5. Man-in-the middle attacks
5.6. Confidentiality
6. IANA Considerations
6.1. Registration Information
6.2. Registration Template
6.3. Header Field Names
6.4. Response Codes
7. Syntax
7.1. New Methods
7.1.1. SUBSCRIBE method
7.1.2. NOTIFY method
7.2. New Headers
7.2.1. Event" header
7.2.2. Allow-Events" Header
7.2.3. Subscription-State" Header
7.3. New Response Codes
7.3.1. Accepted" Response Code
7.3.2. Bad Event" Response Code
7.4. Augmented BNF Definitions
8. References
8.1. Normative References
8.2. Informative References
9. Acknowledgements
10. Notice Regarding Intellectual Property Rights
11. Author's Address
12. Full Copyright Statement
13. Acknowledgement

Google
Web
RFC-Ref
RFC-Ref.org
Frontpage
Global Index
RFC
Sister Sites
Chess-Ref.org
Law-Ref.org
InChI.info
Zvon.org