idnits 2.17.00 (12 Aug 2021) /tmp/idnits53050/draft-ietf-mmusic-sdp-offer-answer-02.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 3264 5 Title: An Offer/Answer Model with Session Description 6 Protocol (SDP) 7 Author(s): J. Rosenberg, H. Schulzrinne 8 Status: Standards Track 9 Date: June 2002 10 Mailbox: jdrosen@dynamicsoft.com, 11 schulzrinne@cs.columbia.edu 12 Pages: 25 13 Characters: 60854 14 Obsoletes: 2543 16 I-D Tag: draft-ietf-mmusic-sdp-offer-answer-02.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3264.txt 20 This document defines a mechanism by which two entities can make use 21 of the Session Description Protocol (SDP) to arrive at a common view 22 of a multimedia session between them. In the model, one participant 23 offers the other a description of the desired session from their 24 perspective, and the other participant answers with the desired 25 session from their perspective. This offer/answer model is most 26 useful in unicast sessions where information from both participants is 27 needed for the complete view of the session. The offer/answer model 28 is used by protocols like the Session Initiation Protocol (SIP). 30 This document is a product of the Session Initiation Protocol Working 31 Group of the IETF. 33 This is now a Proposed Standard Protocol. 35 This document specifies an Internet standards track protocol for 36 the Internet community, and requests discussion and suggestions 37 for improvements. Please refer to the current edition of the 38 "Internet Official Protocol Standards" (STD 1) for the 39 standardization state and status of this protocol. Distribution 40 of this memo is unlimited. 42 This announcement is sent to the IETF list and the RFC-DIST list. 43 Requests to be added to or deleted from the IETF distribution list 44 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 45 added to or deleted from the RFC-DIST distribution list should 46 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 48 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 49 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 50 help: ways_to_get_rfcs. For example: 52 To: rfc-info@RFC-EDITOR.ORG 53 Subject: getting rfcs 55 help: ways_to_get_rfcs 57 Requests for special distribution should be addressed to either the 58 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 59 specifically noted otherwise on the RFC itself, all RFCs are for 60 unlimited distribution.echo 61 Submissions for Requests for Comments should be sent to 62 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 63 Authors, for further information.