From: The IESG To: IETF-Announce Subject: Document Action: 'The Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header)' to Informational RFC Message-Id: <20081031144705.0CCBA3A6A15@core3.amsl.com> Date: Fri, 31 Oct 2008 07:47:05 -0700 (PDT) Cc: Internet Architecture Board , RFC Editor The IESG has approved the following document: - 'The Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header)' as an Informational RFC This document has been reviewed in the IETF but is not the product of an IETF Working Group. The IESG contact person is Jon Peterson. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-hautakorpi-sipping-uri-list-handling-refused-03.txt Technical Summary This document specifies the Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header). This P-Header is used in the Open Mobile Alliance's (OMA) Pust to talk over Cellular (PoC) system. Working Group Summary This document was reviewed by the SIPPING WG per the stipulations of RFC3427 for the review of SIP P- headers. Document Quality An RFC3427 review was provided by Jon Peterson. Expert review in SIPPING was performed by Tom Hiller. Gen-ART review was provided by Eric Gray. Personnel Who is the Document Shepherd for this document? Who is the Responsible Area Director? If the document requires IANA experts(s), insert 'The IANA Expert(s) for the registries in this document are .' RFC Editor Note The following URIs should be changed on Section 7: "sip:bill@example3.com" -> "sip:bill@example.org" "sip:randy@example2.net" -> "sip:randy@example.com" "sip:eddy@example4.com" -> "sip:eddy@example.com" "sip:joe@example3.org" -> "sip:joe@example.org" "sip:carol@example5.net" -> "sip:carol@example.com" Also OLD: encrypted. Therefore it is RECOMMENDED that either hop-by-hop or end-to-end encryption is used. NEW: encrypted. Therefore it is RECOMMENDED that either hop-by-hop or end-to-end encryption (e.g., using TLS or S/MIME respectively) is used.