Common Gateway Interface for SIP
draft-lennox-sip-cgi-04

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3050.
Authors Henning Schulzrinne , Jonathan Rosenberg , Jonathan Lennox
Last updated 2013-03-02 (Latest revision 2000-06-06)
RFC stream Legacy stream
Intended RFC status Informational
Formats
txt htmlized pdf bibtex bibxml
Stream Legacy state (None)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Became RFC 3050 (Informational)
Telechat date (None)
Responsible AD (None)
Send notices to (None)
Email authors IPR References Referenced by Nits Search email archive
draft-lennox-sip-cgi-04 
A new Request for Comments is now available in online RFC libraries.

        RFC 3050

        Title:      Common Gateway Interface for SIP
        Author(s):  J. Lennox, H. Schulzrinne, J. Rosenberg
        Status:     Informational
        Date:       January 2001
        Mailbox:    lennox@cs.columbia.edu,
                    schulzrinne@cs.columbia.edu,
                    jdrosen@dynamicsoft.com 
        Pages:      35
        Characters: 76652
        Updates/Obsoletes/SeeAlso:    None        

        I-D Tag:    draft-lennox-sip-cgi-04.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3050.txt

In Internet telephony, there must be a means by which new services are
created and deployed rapidly.  In the World Wide Web, the Common
Gateway Interface (CGI) has served as popular means towards
programming web services.  Due to the similarities between the Session
Initiation Protocol (SIP) and the Hyper Text Transfer Protocol (HTTP),
CGI is a good candidate for service creation in a SIP environment.
This document defines a SIP CGI interface for providing SIP services
on a SIP server.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.