Private Session Initiation Protocol (SIP) Proxy-to-Proxy Extensions for Supporting the PacketCable Distributed Call Signaling Architecture
RFC 3603
Document | Type |
RFC - Informational
(October 2003; No errata)
Obsoleted by RFC 5503
|
|
---|---|---|---|
Authors | Bill Marshall , Flemming Andreasen | ||
Last updated | 2015-10-14 | ||
Stream | ISE | ||
Formats | plain text html pdf htmlized bibtex | ||
Stream | ISE state | (None) | |
Consensus Boilerplate | Unknown | ||
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 3603 (Informational) | |
Telechat date | |||
Responsible AD | Allison Mankin | ||
IESG note | The rev was great. I requested one more change - RFC Ed note to cite that IPSec minimum mand to implement was the Cablelabs Sec Spec ref. We should publish asap now. | ||
Send notices to | (None) |
Network Working Group W. Marshall, Ed. Request for Comments: 3603 AT&T Category: Informational F. Andreasen, Ed. Cisco October 2003 Private Session Initiation Protocol (SIP) Proxy-to-Proxy Extensions for Supporting the PacketCable Distributed Call Signaling Architecture Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2003). All Rights Reserved. Abstract In order to deploy a residential telephone service at very large scale across different domains, it is necessary for trusted elements owned by different service providers to exchange trusted information that conveys customer-specific information and expectations about the parties involved in the call. This document describes private extensions to the Session Initiation Protocol (SIP) (RFC3261) for supporting the exchange of customer information and billing information between trusted entities in the PacketCable Distributed Call Signaling Architecture. These extensions provide mechanisms for access network coordination to prevent theft of service, customer originated trace of harassing calls, support for operator services and emergency services, and support for various other regulatory issues. The use of the extensions is only applicable within closed administrative domains, or among federations of administrative domains with previously agreed-upon policies where coordination of charging and other functions is required. Table of Contents 1. Applicability Statement . . . . . . . . . . . . . . . . . . . 3 2. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Trust Boundary. . . . . . . . . . . . . . . . . . . . . . . . 5 4. Conventions used in this document . . . . . . . . . . . . . . 6 Marshall & Andreasen Informational [Page 1] RFC 3603 SIP Proxy-to-Proxy Extensions October 2003 5. P-DCS-TRACE-PARTY-ID. . . . . . . . . . . . . . . . . . . . . 6 5.1. Syntax. . . . . . . . . . . . . . . . . . . . . . . . . 7 5.2. Procedures at an Untrusted User Agent Client (UAC). . . 7 5.3. Procedures at a Trusted User Agent Client (UAC) . . . . 7 5.4. Procedures at an Untrusted User Agent Server (UAS). . . 7 5.5. Procedures at a Trusted User Agent Server (UAS) . . . . 7 5.6. Procedures at Proxy . . . . . . . . . . . . . . . . . . 8 5.6.1. Procedures at Originating Proxy . . . . . . . . 8 5.6.2. Procedures at Terminating Proxy . . . . . . . . 8 6. P-DCS-OSPS. . . . . . . . . . . . . . . . . . . . . . . . . . 8 6.1. Syntax. . . . . . . . . . . . . . . . . . . . . . . . . 9 6.2. Procedures at an Untrusted User Agent Client (UAC). . . 9 6.3. Procedures at a Trusted User Agent Client (UAC) . . . . 10 6.4. Procedures at an Untrusted User Agent Server (UAS). . . 10 6.5. Procedures at a Trusted User Agent Server (UAS) . . . . 11 6.6. Procedures at Proxy . . . . . . . . . . . . . . . . . . 11 7. P-DCS-BILLING-INFO. . . . . . . . . . . . . . . . . . . . . . 11 7.1. Syntax. . . . . . . . . . . . . . . . . . . . . . . . . 13 7.2. Procedures at an Untrusted User Agent Client (UAC). . . 14 7.3. Procedures at a Trusted User Agent Client (UAC) . . . . 14 7.4. Procedures at an Untrusted User Agent Server (UAS). . . 15 7.5. Procedures at a Trusted User Agent Server (UAS) . . . . 15 7.6. Procedures at Proxy . . . . . . . . . . . . . . . . . . 16 7.6.1. Procedures at Originating Proxy . . . . . . . . 16 7.6.2. Procedures at Terminating Proxy . . . . . . . . 17 7.6.3. Procedures at Tandem Proxy. . . . . . . . . . . 18 8. P-DCS-LAES and P-DCS-REDIRECT . . . . . . . . . . . . . . . . 18 8.1. Syntax. . . . . . . . . . . . . . . . . . . . . . . . . 19 8.2. Procedures at an Untrusted User Agent Client (UAC). . . 20 8.3. Procedures at a Trusted User Agent Client (UAC) . . . . 20 8.4. Procedures at an Untrusted User Agent Server (UAS). . . 21 8.5. Procedures at a Trusted User Agent Server (UAS) . . . . 21 8.6. Procedures at Proxy . . . . . . . . . . . . . . . . . . 21 8.6.1. Procedures at Originating Proxy . . . . . . . . 22 8.6.2. Procedures at Terminating Proxy . . . . . . . . 23 9. Security Considerations . . . . . . . . . . . . . . . . . . . 24 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25Show full document text