[rfc-dist] RFC 5002 on The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)
rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Fri, 24 August 2007 22:55 UTC
From: "rfc-editor at rfc-editor.org"
Date: Fri, 24 Aug 2007 15:55:47 -0700
Subject: [rfc-dist] RFC 5002 on The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)
Message-ID: <20070824225547.C259EE0089@bosco.isi.edu>
A new Request for Comments is now available in online RFC libraries. RFC 5002 Title: The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header) Author: G. Camarillo, G. Blanco Status: Informational Date: August 2007 Mailbox: Gonzalo.Camarillo at ericsson.com, German.Blanco at ericsson.com Pages: 7 Characters: 15137 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-camarillo-sipping-profile-key-02.txt URL: http://www.rfc-editor.org/rfc/rfc5002.txt This document specifies the SIP P-Profile-Key P-header. This header field is used in the 3rd-Generation Partnership Project (3GPP) IMS (IP Multimedia Subsystem) to provide SIP registrars and SIP proxy servers with the key of the profile corresponding to the destination SIP URI of a particular SIP request. This memo provides information for the Internet community. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ...
- [rfc-dist] RFC 5002 on The Session Initiation Pro… rfc-editor@rfc-editor.org