RFC 3603 (rfc3603) - Page 1 of 28

Private Session Initiation Protocol (SIP) Proxy-to-Proxy Extensions for Supporting the PacketCable Distributed Call Signaling Architecture

Alternative Format: Original Text Document
Next >
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) (RFC 3261) 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
Next >