idnits 2.17.1 draft-lennox-sip-cgi-04.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 3050 5 Title: Common Gateway Interface for SIP 6 Author(s): J. Lennox, H. Schulzrinne, J. Rosenberg 7 Status: Informational 8 Date: January 2001 9 Mailbox: lennox@cs.columbia.edu, 10 schulzrinne@cs.columbia.edu, 11 jdrosen@dynamicsoft.com 12 Pages: 35 13 Characters: 76652 14 Updates/Obsoletes/SeeAlso: None 16 I-D Tag: draft-lennox-sip-cgi-04.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3050.txt 20 In Internet telephony, there must be a means by which new services are 21 created and deployed rapidly. In the World Wide Web, the Common 22 Gateway Interface (CGI) has served as popular means towards 23 programming web services. Due to the similarities between the Session 24 Initiation Protocol (SIP) and the Hyper Text Transfer Protocol (HTTP), 25 CGI is a good candidate for service creation in a SIP environment. 26 This document defines a SIP CGI interface for providing SIP services 27 on a SIP server. 29 This memo provides information for the Internet community. It does 30 not specify an Internet standard of any kind. Distribution of this 31 memo is unlimited. 33 This announcement is sent to the IETF list and the RFC-DIST list. 34 Requests to be added to or deleted from the IETF distribution list 35 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 36 added to or deleted from the RFC-DIST distribution list should 37 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 39 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 40 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 41 help: ways_to_get_rfcs. For example: 43 To: rfc-info@RFC-EDITOR.ORG 44 Subject: getting rfcs 46 help: ways_to_get_rfcs 48 Requests for special distribution should be addressed to either the 49 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 50 specifically noted otherwise on the RFC itself, all RFCs are for 51 unlimited distribution.echo 52 Submissions for Requests for Comments should be sent to 53 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 54 Authors, for further information.