idnits 2.17.1 draft-ietf-sip-refer-07.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 3515 5 Title: The Session Initiation Protocol (SIP) Refer Method 6 Author(s): R. Sparks 7 Status: Standards Track 8 Date: April 2003 9 Mailbox: rsparks@dynamicsoft.com 10 Pages: 23 11 Characters: 47788 12 Updates/Obsoletes/SeeAlso: None 14 I-D Tag: draft-ietf-sip-refer-07.txt 16 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3515.txt 18 This document defines the REFER method. This Session Initiation 19 Protocol (SIP) extension requests that the recipient REFER to a 20 resource provided in the request. It provides a mechanism allowing 21 the party sending the REFER to be notified of the outcome of the 22 referenced request. This can be used to enable many applications, 23 including call transfer. 25 In addition to the REFER method, this document defines the the refer 26 event package and the Refer-To request header. 28 This document is a product of the Session Initiation Protocol Working 29 Group of the IETF. 31 This is now a Proposed Standard Protocol. 33 This document specifies an Internet standards track protocol for 34 the Internet community, and requests discussion and suggestions 35 for improvements. Please refer to the current edition of the 36 "Internet Official Protocol Standards" (STD 1) for the 37 standardization state and status of this protocol. Distribution 38 of this memo is unlimited. 40 This announcement is sent to the IETF list and the RFC-DIST list. 41 Requests to be added to or deleted from the IETF distribution list 42 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 43 added to or deleted from the RFC-DIST distribution list should 44 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 46 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 47 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 48 help: ways_to_get_rfcs. For example: 50 To: rfc-info@RFC-EDITOR.ORG 51 Subject: getting rfcs 53 help: ways_to_get_rfcs 55 Requests for special distribution should be addressed to either the 56 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 57 specifically noted otherwise on the RFC itself, all RFCs are for 58 unlimited distribution.echo 59 Submissions for Requests for Comments should be sent to 60 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 61 Authors, for further information.