Browse Prior Art Database

The Session Initiation Protocol (SIP) "Replaces" Header (RFC3891)

IP.com Disclosure Number: IPCOM000031541D
Original Publication Date: 2004-Sep-01
Included in the Prior Art Database: 2004-Sep-29
Document File: 17 page(s) / 34K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Mahy: AUTHOR [+3]

Abstract

This document defines a new header for use with Session Initiation Protocol (SIP) multi-party applications and call control. The Replaces header is used to logically replace an existing SIP dialog with a new SIP dialog. This primitive can be used to enable a variety of features, for example: "Attended Transfer" and "Call Pickup". Note that the definition of these example features is non- normative.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 8% of the total text.

Network Working Group                                            R. Mahy

Request for Comments: 3891                           Cisco Systems, Inc.

Category: Standards Track                                       B. Biggs

                                                                 R. Dean

                                                          September 2004

        The Session Initiation Protocol (SIP) "Replaces" Header

Status of this Memo

   This document specifies an Internet standards track protocol for the

   Internet community, and requests discussion and suggestions for

   improvements.  Please refer to the current edition of the "Internet

   Official Protocol Standards" (STD 1) for the standardization state

   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2004).

Abstract

   This document defines a new header for use with Session Initiation

   Protocol (SIP) multi-party applications and call control.  The

   Replaces header is used to logically replace an existing SIP dialog

   with a new SIP dialog.  This primitive can be used to enable a

   variety of features, for example: "Attended Transfer" and "Call

   Pickup".  Note that the definition of these example features is non-

   normative.

Mahy, et al.                Standards Track                     [Page 1]

RFC 3891               The SIP "Replaces" Header          September 2004

Table of Contents

   1.  Overview. . . . . . . . . . . . . . . . . . . . . . . . . . .   2

   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   4

   3.  User Agent Server Behavior: Receiving a Replaces Header . . .   4

   4.  User Agent Client Behavior: Sending a Replaces Header . . . .   6

   5.  Proxy Behavior. . . . . . . . . . . . . . . . . . . . . . . .   7

   6.  Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . .   7

       6.1.  The Replaces Header . . . . . . . . . . . . . . . . . .   7

       6.2.  New Option Tag for Require and Supported Headers. . . .   8

   7.  Usage Examples. . . . . . . . . . . . . . . . . . . . . . . .   9

       7.1.  Replacing an Early Dialog at the Originator . . . . . .   9

   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  11

   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13

       9.1.  Registration of "Replaces" SIP Header . . . . . . . . .  13

       9.2.  Registration of "replaces" SIP Option-tag . . . . . . .  13

   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  13

   11. References. . ....