idnits 2.17.1 draft-ietf-sipping-sigcomp-sip-dictionary-05.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 3485 5 Title: The Session Initiation Protocol (SIP) and Session 6 Description Protocol (SDP) Static Dictionary for 7 Signaling Compression (SigComp) 8 Author(s): M. Garcia-Martin, C. Bormann, J. Ott, R. Price, 9 A. B. Roach 10 Status: Standards Track 11 Date: February 2003 12 Mailbox: miguel.a.garcia@ericsson.com, cabo@tzi.org, 13 jo@tzi.org, richard.price@roke.co.uk, 14 adam@dynamicsoft.com 15 Pages: 30 16 Characters: 80195 17 Updates/Obsoletes/SeeAlso: None 19 I-D Tag: draft-ietf-sipping-sigcomp-sip-dictionary-05.txt 21 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3485.txt 23 The Session Initiation Protocol (SIP) is a text-based protocol for 24 initiating and managing communication sessions. The protocol can be 25 compressed by using Signaling Compression (SigComp). Similarly, the 26 Session Description Protocol (SDP) is a text-based protocol intended 27 for describing multimedia sessions for the purposes of session 28 announcement, session invitation, and other forms of multimedia 29 session initiation. This memo defines the SIP/SDP-specific static 30 dictionary that SigComp may use in order to achieve higher efficiency. 31 The dictionary is compression algorithm independent. 33 This document is a product of the Session Initiation Proposal 34 Investigation Working Group and the Session Initiation Working Group 35 of the IETF. 37 This is now a Proposed Standard Protocol. 39 This document specifies an Internet standards track protocol for 40 the Internet community, and requests discussion and suggestions 41 for improvements. Please refer to the current edition of the 42 "Internet Official Protocol Standards" (STD 1) for the 43 standardization state and status of this protocol. Distribution 44 of this memo is unlimited. 46 This announcement is sent to the IETF list and the RFC-DIST list. 47 Requests to be added to or deleted from the IETF distribution list 48 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 49 added to or deleted from the RFC-DIST distribution list should 50 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 52 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 53 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 54 help: ways_to_get_rfcs. For example: 56 To: rfc-info@RFC-EDITOR.ORG 57 Subject: getting rfcs 59 help: ways_to_get_rfcs 61 Requests for special distribution should be addressed to either the 62 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 63 specifically noted otherwise on the RFC itself, all RFCs are for 64 unlimited distribution.echo 65 Submissions for Requests for Comments should be sent to 66 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 67 Authors, for further information.