idnits 2.17.1 draft-ietf-sip-reason-01.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 3326 5 Title: The Reason Header Field for the Session Initiation 6 Protocol (SIP) 7 Author(s): H. Schulzrinne, D. Oran, G. Camarillo 8 Status: Standards Track 9 Date: December 2002 10 Mailbox: schulzrinne@cs.columbia.edu, oran@cisco.com, 11 Gonzalo.Camarillo@ericsson.com 12 Pages: 8 13 Characters: 15695 14 Updates/Obsoletes/SeeAlso: None 16 I-D Tag: draft-ietf-sip-reason-01.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3326.txt 20 For creating services, it is often useful to know why a Session 21 Initiation Protocol (SIP) request was issued. This document defines 22 a header field, Reason, that provides this information. The Reason 23 header field is also intended to be used to encapsulate a final 24 status code in a provisional response. This functionality is needed 25 to resolve the "Heterogeneous Error Response Forking Problem", or 26 HERFP. 28 This document is a product of the Session Initiation Protocol and the 29 Session Initiation Proposal Investigation Working Groups of the IETF. 31 This is now a Proposed Standard Protocol. 33 This document specifies an Internet standards track protocol for the 34 Internet community, and requests discussion and suggestions for 35 improvements. Please refer to the current edition of the "Internet 36 Official Protocol Standards" (STD 1) for the standardization state 37 and status of this protocol. Distribution of this memo is unlimited. 39 This announcement is sent to the IETF list and the RFC-DIST list. 40 Requests to be added to or deleted from the IETF distribution list 41 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 42 added to or deleted from the RFC-DIST distribution list should 43 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 45 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 46 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 47 help: ways_to_get_rfcs. For example: 49 To: rfc-info@RFC-EDITOR.ORG 50 Subject: getting rfcs 52 help: ways_to_get_rfcs 54 Requests for special distribution should be addressed to either the 55 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 56 specifically noted otherwise on the RFC itself, all RFCs are for 57 unlimited distribution.echo 58 Submissions for Requests for Comments should be sent to 59 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 60 Authors, for further information.