idnits 2.17.1 draft-ietf-sip-rfc2543bis-09.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 3261 5 Title: SIP: Session Initiation Protocol 6 Author(s): J. Rosenberg, H. Schulzrinne, G. Camarillo, 7 A. Johnston, J. Peterson, R. Sparks, M. Handley, 8 E. Schooler 9 Status: Standards Track 10 Date: June 2002 11 Mailbox: jdrosen@dynamicsoft.com, 12 schulzrinne@cs.columbia.edu, 13 Gonzalo.Camarillo@ericsson.com, 14 alan.johnston@wcom.com, jon.peterson@neustar.com, 15 rsparks@dynamicsoft.com, mjh@icir.org, 16 schooler@research.att.com 17 Pages: 266 18 Characters: 647976 19 Obsoletes: 2543 21 I-D Tag: draft-ietf-sip-rfc2543bis-09.txt 23 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3261.txt 25 This document describes Session Initiation Protocol (SIP), an 26 application-layer control (signaling) protocol for creating, 27 modifying, and terminating sessions with one or more 28 participants. These sessions include Internet telephone calls, 29 multimedia distribution, and multimedia conferences. 31 SIP invitations used to create sessions carry session descriptions 32 that allow participants to agree on a set of compatible media types. 33 SIP makes use of elements called proxy servers to help route requests 34 to the user's current location, authenticate and authorize users for 35 services, implement provider call-routing policies, and provide 36 features to users. SIP also provides a registration function that 37 allows users to upload their current locations for use by proxy 38 servers. SIP runs on top of several different transport protocols. 40 This document is a product of the Session Initiation Protocol Working 41 Group of the IETF. 43 This is now a Proposed Standard Protocol. 45 This document specifies an Internet standards track protocol for 46 the Internet community, and requests discussion and suggestions 47 for improvements. Please refer to the current edition of the 48 "Internet Official Protocol Standards" (STD 1) for the 49 standardization state and status of this protocol. Distribution 50 of this memo is unlimited. 52 This announcement is sent to the IETF list and the RFC-DIST list. 53 Requests to be added to or deleted from the IETF distribution list 54 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 55 added to or deleted from the RFC-DIST distribution list should 56 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 58 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 59 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 60 help: ways_to_get_rfcs. For example: 62 To: rfc-info@RFC-EDITOR.ORG 63 Subject: getting rfcs 65 help: ways_to_get_rfcs 67 Requests for special distribution should be addressed to either the 68 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 69 specifically noted otherwise on the RFC itself, all RFCs are for 70 unlimited distribution.echo 71 Submissions for Requests for Comments should be sent to 72 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 73 Authors, for further information.