idnits 2.17.1 draft-garcia-sipping-3gpp-p-headers-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 3455 5 Title: Private Header (P-Header) Extensions to the 6 Session Initiation Protocol (SIP) for the 7 3rd-Generation Partnership Project (3GPP) 8 Author(s): M. Garcia-Martin, E. Henrikson, D. Mills 9 Status: Informational 10 Date: January 2003 11 Mailbox: miguel.a.garcia@ericsson.com, 12 ehenrikson@lucent.com, 13 duncan.mills@vf.vodafone.co.uk 14 Pages: 34 15 Characters: 79620 16 Updates/Obsoletes/SeeAlso: None 18 I-D Tag: draft-garcia-sipping-3gpp-p-headers-02.txt 20 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3455.txt 22 This document describes a set of private Session Initiation Protocol 23 (SIP) headers (P-headers) used by the 3rd-Generation Partnership 24 Project (3GPP), along with their applicability, which is limited to 25 particular environments. The P-headers are for a variety of purposes 26 within the networks that the partners use, including charging and 27 information about the networks a call traverses. 29 This memo provides information for the Internet community. It does 30 not specify an Internet standard of any kind. Distribution of this 31 memo is unlimited. 33 This announcement is sent to the IETF list and the RFC-DIST list. 34 Requests to be added to or deleted from the IETF distribution list 35 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 36 added to or deleted from the RFC-DIST distribution list should 37 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 39 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 40 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 41 help: ways_to_get_rfcs. For example: 43 To: rfc-info@RFC-EDITOR.ORG 44 Subject: getting rfcs 46 help: ways_to_get_rfcs 48 Requests for special distribution should be addressed to either the 49 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 50 specifically noted otherwise on the RFC itself, all RFCs are for 51 unlimited distribution.echo 52 Submissions for Requests for Comments should be sent to 53 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 54 Authors, for further information.