idnits 2.17.1 draft-campbell-sip-service-control-03.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 3087 5 Title: Control of Service Context using SIP Request-URI 6 Author(s): B. Campbell, R. Sparks 7 Status: Informational 8 Date: April 2001 9 Mailbox: bcampbell@dynamicsoft.com, rsparks@dynamicsoft.com 10 Pages: 39 11 Characters: 83612 12 Updates/Obsoletes/SeeAlso: None 14 I-D Tag: draft-campbell-sip-service-control-03.txt 16 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3087.txt 18 This memo provides information for the Internet community. It 19 describes a useful way to conceptualize the use of the standard SIP 20 (Session Initiation Protocol) Request-URI (Uniform Resource 21 Identifier) that the authors and many members of the SIP community 22 think is suitable as a convention. It does not define any new 23 protocol with respect to RFC 2543. 25 In a conventional telephony environment, extended service 26 applications often use call state information, such as calling 27 party, called party, reason for forward, etc, to infer application 28 context. In a SIP/2.0 call, much of this information may be either 29 non-existent or unreliable. This document proposes a mechanism to 30 communicate context information to an application. Under this 31 proposal, a client or proxy can communicate context through the use 32 of a distinctive Request-URI. This document continues with examples 33 of how this mechanism could be used in a voice mail application. 35 This memo provides information for the Internet community. It does 36 not specify an Internet standard of any kind. Distribution of this 37 memo is unlimited. 39 This announcement is sent to the IETF list and the RFC-DIST list. 40 Requests to be added to or deleted from the IETF distribution list 41 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 42 added to or deleted from the RFC-DIST distribution list should 43 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 45 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 46 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 47 help: ways_to_get_rfcs. For example: 49 To: rfc-info@RFC-EDITOR.ORG 50 Subject: getting rfcs 52 help: ways_to_get_rfcs 54 Requests for special distribution should be addressed to either the 55 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 56 specifically noted otherwise on the RFC itself, all RFCs are for 57 unlimited distribution.echo 58 Submissions for Requests for Comments should be sent to 59 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 60 Authors, for further information.