idnits 2.17.1 draft-tsvarea-sipchange-03.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 BCP 67 4 RFC 3427 6 Title: Change Process for the Session Initiation Protocol 7 (SIP) 8 Author(s): A. Mankin, S. Bradner, R. Mahy, D. Willis, J. Ott, 9 B. Rosen 10 Status: Best Current Practice 11 Date: December 2002 12 Mailbox: mankin@psg.com, sob@harvard.edu, rohan@cisco.com, 13 dean.willis@softarmor.com, 14 brian.rosen@marconi.com, jo@ipdialog.com 15 Pages: 12 16 Characters: 26234 17 SeeAlso: BCP 67 19 I-D Tag: draft-tsvarea-sipchange-03.txt 21 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3427.txt 23 This memo documents a process intended to apply architectural 24 discipline to the future development of the Session Initiation 25 Protocol (SIP). There have been concerns with regards to new SIP 26 proposals. Specifically, that the addition of new SIP features can be 27 damaging towards security and/or greatly increase the complexity of 28 the protocol. The Transport Area directors, along with the SIP and 29 Session Initiation Proposal Investigation (SIPPING) working group 30 chairs, have provided suggestions for SIP modifications and 31 extensions. 33 This document specifies an Internet Best Current Practices for the 34 Internet Community, and requests discussion and suggestions for 35 improvements. Distribution of this memo is unlimited. 37 This announcement is sent to the IETF list and the RFC-DIST list. 38 Requests to be added to or deleted from the IETF distribution list 39 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 40 added to or deleted from the RFC-DIST distribution list should 41 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 43 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 44 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 45 help: ways_to_get_rfcs. For example: 47 To: rfc-info@RFC-EDITOR.ORG 48 Subject: getting rfcs 50 help: ways_to_get_rfcs 52 Requests for special distribution should be addressed to either the 53 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 54 specifically noted otherwise on the RFC itself, all RFCs are for 55 unlimited distribution.echo 56 Submissions for Requests for Comments should be sent to 57 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 58 Authors, for further information.