idnits 2.17.1 draft-ietf-sip-events-05.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3265 5 Title: Session Initiation Protocol (SIP)-Specific Event 6 Notification 7 Author(s): A. B. Roach 8 Status: Standards Track 9 Date: June 2002 10 Mailbox: adam@dynamicsoft.com 11 Pages: 38 12 Characters: 89005 13 Obsoletes: 2543 15 I-D Tag: draft-ietf-sip-events-05.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3265.txt 19 This document describes an extension to the Session Initiation 20 Protocol (SIP). The purpose of this extension is to provide an 21 extensible framework by which SIP nodes can request notification 22 from remote nodes indicating that certain events have occurred. 24 Concrete uses of the mechanism described in this document may be 25 standardized in the future. 27 Note that the event notification mechanisms defined herein are 28 NOT intended to be a general-purpose infrastructure for all 29 classes of event subscription and notification. 31 This document is a product of the Session Initiation Protocol Working 32 Group of the IETF. 34 This is now a Proposed Standard Protocol. 36 This document specifies an Internet standards track protocol for 37 the Internet community, and requests discussion and suggestions 38 for improvements. Please refer to the current edition of the 39 "Internet Official Protocol Standards" (STD 1) for the 40 standardization state and status of this protocol. Distribution 41 of this memo is unlimited. 43 This announcement is sent to the IETF list and the RFC-DIST list. 44 Requests to be added to or deleted from the IETF distribution list 45 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 46 added to or deleted from the RFC-DIST distribution list should 47 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 49 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 50 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 51 help: ways_to_get_rfcs. For example: 53 To: rfc-info@RFC-EDITOR.ORG 54 Subject: getting rfcs 56 help: ways_to_get_rfcs 58 Requests for special distribution should be addressed to either the 59 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 60 specifically noted otherwise on the RFC itself, all RFCs are for 61 unlimited distribution.echo 62 Submissions for Requests for Comments should be sent to 63 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 64 Authors, for further information.