A new Request for Comments is now available in online RFC libraries.


        RFC 2543: 

        Title:	    SIP: Session Initiation Protocol
	Author(s):  M. Handley, H. Schulzrinne, E. Schooler, 
	            J. Rosenberg
	Status:     Proposed Standard
	Date:       March 1999
        Mailbox:    mjh@isi.edu, schulzrinne@cs.columbia.edu,
		    schooler@cs.caltech.edu, jdrosen@bell-labs.com
	Pages:      153
        Characters: 338861
        Updates/Obsoletes/See Also: None
        I-D Tag:    draft-ietf-mmusic-sip-12.txt


        URL:        ftp://ftp.isi.edu/in-notes/rfc2543.txt


The Session Initiation Protocol (SIP) is an application-layer control
(signaling) protocol for creating, modifying and terminating sessions
with one or more participants. These sessions include Internet
multimedia conferences, Internet telephone calls and multimedia
distribution. Members in a session can communicate via multicast or
via a mesh of unicast relations, or a combination of these.

This document is a product of the Multiparty Multimedia Session
Control Working Group of the IETF.

This is now a Proposed Standard protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  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.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute